Related
I got the Virtuous Unity 1.29.0 rom on my desire s and suddenly it just started to freeze so i took out the battery, put it back in and it's just stuck at the HTC screen. So i got in to clockwork recovery but there i get this error message
E:Can't mount /cache/recovery/command
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
i can do a "wipe data/factory reset" but i cant flash the Virtuous Unity ROM or restore to previous backups.
And CWM is running really slowly everything takes 10 times longer to do..
I guess the ROM freeze semi bricked the phone and damaged the recovery.
How can i fix this ?
Please help!
sebulba84 said:
I got the Virtuous Unity 1.29.0 rom on my desire s and suddenly it just started to freeze so i took out the battery, put it back in and it's just stuck at the HTC screen. So i got in to clockwork recovery but there i get this error message
E:Can't mount /cache/recovery/command
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
i can do a "wipe data/factory reset" but i cant flash the Virtuous Unity ROM or restore to previous backups.
And CWM is running really slowly everything takes 10 times longer to do..
I guess the ROM freeze semi bricked the phone and damaged the recovery.
How can i fix this ?
Please help!
Click to expand...
Click to collapse
Have you tried a full wip as described here? If you don't have a Nandroid Back Up, do the wipes and then try a fresh install of just the rom. If that's no better you'll need to RUU.
I tried the full wipe, but i get an error message when trying to format cache..same with data.
So how do i do this RUU ?
Thanks for your help!
Push a new recovery via Fastboot, that should sort it. I'll post instructions later.
Sent from my HTC Desire S using XDA Premium App
InfernalByte said:
Push a new recovery via Fastboot, that should sort it. I'll post instructions later.
Sent from my HTC Desire S using XDA Premium App
Click to expand...
Click to collapse
Sweet! can't wait!
Sorry it took so long to get back but I can't find the 4.0.0.4. recovery.
http://forum.xda-developers.com/showthread.php?t=1046667
ok, so it dosent work with any other recovery version ?
i have the CWM 3.0.2.6 on the phone.
i also have a nandroid backup, can't i flash the nandroid backup through the PC in some way ?
sebulba84 said:
ok, so it dosent work with any other recovery version ?
i have the CWM 3.0.2.6 on the phone.
i also have a nandroid backup, can't i flash the nandroid backup through the PC in some way ?
Click to expand...
Click to collapse
This is fixable, you have NOT bricked your phone but you'll need to RUU, and before you can do that your probably going to need to downgrade your bootloader.
What does your Hboot screen say?
There's more help here.
it says HBOOT 6.98.1002
sebulba84 said:
it says HBOOT 6.98.1002
Click to expand...
Click to collapse
You'll need to downgrade. See above.
InfernalByte said:
You'll need to downgrade. See above.
Click to expand...
Click to collapse
i tried to flash it with saga_hboot_0.98.img
sending 'hboot' (1024 KB)...
OKAY [ 0.205s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.241s
and on the phone it says "can not roll back hboot version"
what am i doing wrong ?
I got same issues and hope someone can help us out
Once I can get my adb working I will help, either way you'll need to read this.
OK I can confirm that this works! Its long winded but you will achieve what you want.
You'll need this, you need only go as far as downloading and installing, and then this.
1. Put the hboot.img you want to flash in the root of the sdcard.
2. In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot bootloader
i cant use the su command cause then i get
---------------------------------
C:\Users\Seb>adb shell
~ # su
su
/sbin/sh: su: not found
------------------------------------
so i skip it and jump to this command
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
and i get
----------------------------
dd: /dev/block/mmcblk0p18: I/O error
-------------------------
i dont have this backup.img file, maybe thats the problem.
where do i get it ?
without root (that's what the su-command is for) you'll proboably can't write the hboot...
and you don't need the backup.img since you are creating it yourself with the first command. what you need is the hboot.img. but as is said before, without root you can't dd...
Well i have root and s-off..unless the rom freeze messed that up too..
I read somewhere also that it's not necessary to type the su command
If ur already rooted. But i dont know i'm the noob here.
I'm going away for a couple of days so wont be able to do much untill i get back home.
Well, i know that in a normal linux, "sudo su" is to get root
Still pretty weird what you got there..
sebulba84 said:
1. Put the hboot.img you want to flash in the root of the sdcard.
2. In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot bootloader
i cant use the su command cause then i get
---------------------------------
C:\Users\Seb>adb shell
~ # su
su
/sbin/sh: su: not found
------------------------------------
so i skip it and jump to this command
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
and i get
----------------------------
dd: /dev/block/mmcblk0p18: I/O error
-------------------------
i dont have this backup.img file, maybe thats the problem.
where do i get it ?
Click to expand...
Click to collapse
Have you renamed your file hboot.img?
Download this extract the hboot and rename it.
sebulba84 said:
i can do a "wipe data/factory reset" but i cant flash the Virtuous Unity ROM or restore to previous backups.
Click to expand...
Click to collapse
i had the same problem.
E:Can't mount /cache/recovery/command
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
these lines scared the **** outta me. but, i was able to restore a nandroid backup.
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?
Hi All,
I have been flashing back and forth a bit from CM9 to CM10 to try things out. Today, I attempted to restore back to CM9 and it hung for over an hour, so I hard restarted it. Now, I can't restore anything, because it hangs on the /cache partition. I also receive the message while in recovery mode
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
Click to expand...
Click to collapse
I am able to get adb shell in recovery mode and I have gone through the steps to check for a bad emmc, which did not indicate badness. I have attempted to use umount from the shell on /cache, which just hangs. In recovery mode, over adb shell, I can ls and cat any of the files in /cache without apparent issue.
I have attempted Super Wipe, factory reset, manual formatting, and wipe cache, all to no avail (they all just hang).
I am running CWM 6.0.1.1.
dmesg has a message about an ext4 error, that makes me suspicious, but I don't know what to do about it.
<4>[ 8.431030] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
<4>[ 8.442413] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
<4>[ 8.462036] EXT4-fs (mmcblk0p26): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 8.475463] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 8.489562] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<6>[ 9.242095] key released
<6>[ 9.243774] key released
<6>[ 9.442749] msmsdcc_runtime_suspend: Enter WIFI suspend
<6>[ 9.542755] fsa9480 5-0025: fsa9480_init_detect
<6>[ 9.547424] fsa9480 5-0025: dev1: 0x0, dev2: 0x0
<2>[ 13.382751] EXT4-fs error (device mmcblk0p26): ext4_init_inode_table:1293: comm ext4lazyinit: Something is wrong with group 0
<2>[ 13.382751] Used itable blocks: 403itable unused count: 0
<2>[ 13.382781]
<3>[ 13.411773] Aborting journal on device mmcblk0p26-8.
<2>[ 13.429321] EXT4-fs (mmcblk0p26): Remounting filesystem read-only
Click to expand...
Click to collapse
Apparently my full dmesg output was too long, so if you need anything else please ask.
Thanks in advance for any help!
I am experiencing the same thing (I think) as the OP.
I had been running alpha2 of TeamChopsticks CM10. I installed the new recovery for the skyrocket (downloaded from teamchopsticks.org). Then rebooted into recovery. formatted /system -> installed alpha3 -> installed gapps -> installed darkside-wipe-cache-only -> rebooted. Then my phone just hung on the boot animation for 10+ minutes.
After rebooting I thought I would try to install alpha2 again. I tried to format /system, and it hung.
So I rebooted again, and tried to restore a backup. That hung on "Restoring .android_secure..."
So, I rebooted again. This time I tried a factory reset. It hung on "Wiping cache..."
After rebooting this time, I selected "show log" in CWM, which shows this (I don't know if this is helpful/related):
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I have also tried Fixing Permissions in CWM, with no apparent change.
Also, any time I perform an action in CWM (show logs, fix permissions, etc.) and select "go back" in the menu, the menu disappears. I am still in recovery (still see the CWM logo in the background, and see the text from my previous action), but buttons do nothing and there is no menu.
Any help would be appreciated.
Josh
---------- Post added at 10:58 AM ---------- Previous post was at 10:20 AM ----------
Another follow up to my previous post:
I have tried to reinstall cm9 and cm10 alpha2.
With each I format /system, then when I select "Go Back" in the CWM menu the menu disappears (as I mentioned before). So, I reboot, then install zip from SD -> select the cm zip and get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cm-9-20120715-EXPERIMENTAL-skyrocket-beta1.zip
And nothing after that. It will just sit there.
Don't use darkside wipe, reflash sk8ers recovery From his thread
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
vincom said:
Don't use darkside wipe, reflash sk8ers recovery From his thread
Click to expand...
Click to collapse
Interestingly (and perhaps ironically), looks like sk8er may be adding the Darkside Tools option in a forthcoming Recovery....
http://forum.xda-developers.com/showpost.php?p=30639023&postcount=267
That's pretty hilarious, so Darkside Wipe is apparently the way to go, except it doesn't work in my case.
So, I tried installing that recovery but it won't install (just like everything else).
I get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cwm6012touch_v11.zip
Is there a way to install his recovery that I am not aware of?
Thanks,
Josh
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
cthrax said:
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
Click to expand...
Click to collapse
Why could u install the recovery and what was the solution
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
cthrax said:
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
Click to expand...
Click to collapse
thats the way its done, i just dont understand why you couldnt do it the first place, and the cache has nothing todo with recovery just the rom
Ah, that's a confusion of terms. The original issue was that I could not restore from a backup. Or install a new rom. Apparently installing a new recovery was not an issue, I just didn't know that installing that would help at the time.
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
joshjryan said:
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
Click to expand...
Click to collapse
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
KillaT21 said:
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
Click to expand...
Click to collapse
Another no go. Cthrax, can you post or pm me exactly what you did?
KillaT21 said:
Another no go. Cthrax, can you post or pm me exactly what you did?
Click to expand...
Click to collapse
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
cthrax said:
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
Click to expand...
Click to collapse
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
KillaT21 said:
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
Click to expand...
Click to collapse
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Well, joshjryan, I hope youre reading this too.
This caught my attention after a dmesg:
<6>[ 1478.616302] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts:
So then I
~ # parted /dev/block/mmcblk0p24
parted /dev/block/mmcblk0p24
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p24
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p24: 627MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Could this be the cause??
Number Start End Size File system Flags
1 0.00B 627MB 627MB ext4
(parted)
cthrax said:
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Click to expand...
Click to collapse
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
joshjryan said:
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
Click to expand...
Click to collapse
It didnt. It installed to the right partition, but after reboot, cwmtouch5.8.1.3 is there again
Is it something in my reboot/boot that causes that?
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
RVexx said:
Hi XDA-D,
I kinda helped my tf300t over the edge. I wanted to flash the new stock rom for troubleshooting purposes. I wanted to boot into Recovery but it froze the machine. Because I had fastboot options I pushed a the newest recovery (v6.0.2.3) and all seemed well untill I rebooted. Whatever I do The device boots into Recovery. It doesn't try to load the Rom and doesn't respond to "power vol down/up)
Recovery does start but with errors:
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
and can't mount any directory (no /system, /cache, /data, /sdcard, etc)
Fast boot doesn't respond any more (keeps waiting for devices and doesn't list the tablet)
Adb recognises the tablet:
Code:
adb status-window
<-[2J<-[2HAndroid Debug Bridge
State unknown
adb devices
111111111111111111 Recovery
I think the boodloader is corrupt and the device defaults to recovery but the directories are gone, making sure that I can't install via fastboot or micro sd. Is there a way to restore this tablet with adb but without fastboot?
Click to expand...
Click to collapse
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
JoinTheRealms said:
Hmm that doesnt sound good, CWM really sucks i refuse to use it lol. Does it have a terminal you enter? and have you been able to adb push anything to the tablet?
*
im thinking if you can adb push twrp to the device and open a adb shell you could try dd if=*path-to-twrp* of=/dev/block/mmcblk0p4
*
I havnt used the above in your situation so not sure if it will work, hopefully someone else can help. Goodluck mate
Click to expand...
Click to collapse
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
RVexx said:
*
Haven't tried to push a different recovery because I'm afraid I'll break the last thing that works. I think I can get a remote shell via adb. I was hoping there is a way to push a new kernel and boot but my knowledge is lacking.
Click to expand...
Click to collapse
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
JoinTheRealms said:
Id wait for someone elses input, i dont wanna mess with your adb lol. Im not sure about the above method since adb push would need access to sdcard, dd might work if you already have twrp on the device, again if you can access adb shell and dd works you might have a few things that could work, but even if you have a bricked device its not the end of the world. Asus might repair it, if not and your willing motherboards for these devices seem quite cheap, and if so you will have access to nvflash so something like wont happen again.
Click to expand...
Click to collapse
Anyhow, thanks for thinking with me
I'll wait for someone who absolutely loves CWM
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