Develop Bugs

E:Cant mount /cache/recovery/command

Have been getting this error of late after i run unrevoked, then when i go to recovery to flash rom i get this error...is there any solution to this, or is there a new version of unrevoked to solve this porblem? Im using unrevoked v3.32.
Thank you.

Phone details? recovery version? Which Rom?

davebugyi said:
Phone details? recovery version? Which Rom?
Click to expand...
Click to collapse
Unfortunately i gave the phone back to a friend who need help, so cant provide any info

Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.

lowkey1979 said:
Hi there,
I have the same issue.
Am running the carrier ROM (Telstra - Australia), on a HTC Desire GSM. I rooted it using unrevoked 3, and the phone is working fine, except for the Clockwork Mod recovery.
When I boot into recovery mode, I'm not able to load custom roms or make nandroid backups. It just gives errors about not being able to mount CACHE or MISC partitions.
I tried updating clockwork to 3.0.0.5, but that failed to resolve it, as did another go with unrevoked. I can't even do factory wipes! Cache wipe was also ineffective.
Is there possibly a problem with the /recovery partition? Any way to correct it? I don't have s-off, as alpharev fails with some error about expecting unary operators. Otherwise I'd try pushing a new recovery image through with fastboot.
I've checked every thread where this is mentioned, no resolutions yet that don't involve using fastboot. Some help would be nice.
Click to expand...
Click to collapse
Do you have a pvt4-desire? If, you have to flash amonra-recovery, because cwm is incompatible with pvt4-desires.

or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF

ghalalb said:
or CWM 2.5.1.8 will work in addition to AmonRa. I've used both with my PVT-4.
and flash your recovery from fastboot, not by using unrevoked, it's just easier.
GL HF
Click to expand...
Click to collapse
Can you tell me how to flash recovery with fastboot?

You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/

MatDrOiD said:
You can also do it with adb:
http://www.wonderhowto.com/how-to-flash-new-recovery-image-with-adb-windows-pc-411005/
Click to expand...
Click to collapse
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?

andrew21 said:
Can you tell me total technique to flash a rom on a virgin htc desire with a non-video manual?
Click to expand...
Click to collapse
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189

hi mates,
to flash recovery with fastboot need to be s-off.
the command are really simple.
boot in hboot, select fastboot (shoul see fastbbot usb on the phone screen)
open a command line
Code:
fastboot flash recovery c:/wheretefileis/yourecovery.img

MatDrOiD said:
Do not understand why you want a non-video manual, but here you have one:
http://forum.xda-developers.com/showthread.php?t=696189
Click to expand...
Click to collapse
Sir,
I tried this method but i get a "flash_image: not found". It seems like i don't have the flash_image command on my phone. I've looked everywhere to find a way to get that command and i found this - http://www.villainrom.co.uk/forum/s...)
finished. total time: 1.094s
Thank you sir

chage a sd card for try!

zk7513153 said:
chage a sd card for try!
Click to expand...
Click to collapse
Already did change the sdcard sir.
On another note, whenever i tried remounting the /system for RW access to copy flash_image, free space drops to Zero Kb. To isolate, i tried remounting to just Read access, free space remained the same. Anything I'm missing here, or do I really have to S-OFF my phone before I can make changes on my /system ?
Thank you very much.

nonofficialcover said:
I also tried flashing via ADB and I get this:
C:\fastboot flash recovery c:\recovery-RA-desire-v2.0.1.img
sending 'recovery' (3936 KB)...
OKAY [ 0.687s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.094s
Thank you sir
Click to expand...
Click to collapse
For this part I think you need to disable signature verification in recovery.

I was able to solve my problem after I did S-OFF.

Soft bricked and can't flash any ROM

So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )

What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.

redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S

tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.

Did you fastboot erase cache before installing TWRP, as I suggested?

Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.

It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.

Unable to Flash Custom Recovery - OP3 Open Beta 30

Hi All,
I am facing issues with flashing any custom recovery on my oneplus 3 device running on open beta 30.
Everytime I flash a recovery, it says finished without an error but throw me back to stock recovery, After searching some available option I can across several links and tried following suggestions so far:
1) used "Fastboot boot recovery.img": Error "FAILED (remote: bootimage header fields are invalid)"
Thought the downloaded recovery file is corrupted, downloaded it from official site and other locations, all with same hash value and same problem
2) Searched an option to disable "update cm recovery", unable to location this setting on my device
3) Tried to flash recovery then poweroff and then reboot to recovery using power button and volume down key, did not worked.
recoveries I have tried:
blu_spark TWRP and original TWRP
device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
(bootloader) force_training: false
Anyone faced similar issue or found a way to fix this ?
Note: Device not rooted, bootloader unlocked.

You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.

oopstairs said:
You could try "fastboot format userdata" in fastboot mode. Backup your data first. I think it was something with encryption. Same case with my friend.
Click to expand...
Click to collapse
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.

Puddi_Puddin said:
Encryption is for the data partition not the recovery one. Are you using correct adb drivers? Works all fine here.
Click to expand...
Click to collapse
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.

anandpandey said:
Yes, I have verified ADB and fastboot on another device, its working fine.
I did tried two different systems for OP3 device, Ubuntu and windows. Same result in both cases, no success.
Click to expand...
Click to collapse
Which recovery are you trying to flash?

Puddi_Puddin said:
Which recovery are you trying to flash?
Click to expand...
Click to collapse
recoveries I have tried:
blu_spark TWRP and official TWRP

Try:
fastboot flash recovery recovery.img

cmnaka said:
Try:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Thanks, that was the first thing i tried.

anandpandey said:
Thanks, that was the first thing i tried.
Click to expand...
Click to collapse
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.

tnsmani said:
Did you try flashing SuperSU immediately after flashing TWRP and before booting into system?
When I flashed TWRP alone, I could boot back into TWRP but after booting into system, the next boot to recovery will take me to the stock one. I solved it by flashing SuperSu immediately after flashing TWRP.
Click to expand...
Click to collapse
The problem with this approach is that I cound never reach to TWRP so to flash SuperSu or Magisk.
Soon after I flash TWRP, the repory enters into a loop.

Still not able to flash a custom rom, any other suggested options ?

This is a nonsense answer but can try , Rename to twrp or anything else other than recovery.img ( may be stock confused with same name )

anandpandey said:
Still not able to flash a custom rom, any other suggested options ?
Click to expand...
Click to collapse
Told you already to flash SuperSu. Don't use TWRP to flash SuperSu. Use adb.
If I were you, I would wipe system, data, Dalvik and cache and flash the ROM first, all using adb. Then boot into the ROM. Then using adb, flash blu_spark's TWRP v 8.61 and immediately thereafter flash SuperSu v 2.79 SR5, again using adb. Then boot into TWRP and then into system.

I after getting the beta31 I ran out of dash charger and also could not get the recovery oos
so I went back to 5.0.1 and did not go back to giving the cherzer dash. I got now I put the beta 31 and firmware of beta 30

Could someone give me a hand installing TWRP on my Xperia S?

Hi,
I want to install TWRP so I can Install nAOSP ROM 8.1 for Xperia S on my phone.
The phone's bootloader is unlocked and the phone is rooted. I downloaded the correct version of TWRP from here (nozomi).
I tried installing via ADB (I followed the instructions here), but the command:
Code:
fastboot flash recovery twrp-3.2.3-nozomi.img
Fails with:
Code:
Sending 'recovery' (12964 KB)
(bootloader) USB download speed was 33272kB/s
OKAY [ 0.415s]
Writing 'recovery'
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: 'Partition not found')
Finished. Total time: 0.437s
I understand that this is because Sony phones don't have separate recovery partition, and that their recovery is incorporated to the boot.img (see here).
I then tried using the dd install method as described on the project's homepage.
Code:
$ ./adb shell
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
25929+1 records in
25929+1 records out
13275872 bytes transferred in 3.747 secs (3543066 bytes/sec)
Although this seems to work (i.e. I don't get an error message), I cannot, try what I might, make the phone boot into recovery.
Can anyone tell me what I'm missing?

Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.

_jack said:
Just for anyone that comes across this post, I ended up solving my problem by flashing TWRP to boot.
Don't know if this is recommended or not, but it worked like a charm. I am now running nAOSP ROM 8.1 on my Xperia S.
Click to expand...
Click to collapse
How exactly did u do that...i have spent over a week trying to do it.

sweetbanana said:
How exactly did u do that...i have spent over a week trying to do it.
Click to expand...
Click to collapse
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img

_jack said:
Just replace "recovery" with "boot".
Code:
sudo fastboot flash boot twrp-3.2.3-nozomi.img
Click to expand...
Click to collapse
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.

ZebastianJV said:
I did that to my Xperia S and it worked too, but after i reboot to system. It just puts me to Cyanogen recovery and idk how I have Cynaogen recovery but its there. And its just stuck there, and wouldnt let me boot to Android. The recovery mode for cyanogenmod is the only thing thats there. I flashed twrp to boot (when i was at the twrp fastboot) and it didnt anything at all. Which made my xperia bricked. I had to reflash the firmware 3 times to troubleshoot the problem.
Click to expand...
Click to collapse
Try flashtool to install twrp. twrp link: https://androidfilehost.com/?fid=1322778262904003720

Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.

ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
No, it won't be a problem.

ZebastianJV said:
Thx, i hope this works. Cause again, i dont like to keep reflashing the firmware cause its broken when i have the recovery.
Click to expand...
Click to collapse
i had the same issue i just flashed the firmware boot.img with flashtools 0.9.8.0

Extract with 7zip/winrar/winzip. Use this kernel via flashtool. has recovery. note for unlocked bootloaders only

How to flash a treble img without fastboot (/system wiped, twrp operational)?

I may be in a tricky spot here. I've a Palm phone which doesn't have fastboot. I flashed twrp and a replacement system image but the system image didn't boot as planned. I wiped it with the intention of replacing using dd which writes the data, but the partition is corrupt and can't be mounted.
How to recover? TWRP only has 'boot' and 'recovery' as options for the img flash, which I assume is because it's using fastboot and that isn't available.

snoopy20 said:
I may be in a tricky spot here. I've a Palm phone which doesn't have fastboot. I flashed twrp and a replacement system image but the system image didn't boot as planned. I wiped it with the intention of replacing using dd which writes the data, but the partition is corrupt and can't be mounted.
How to recover? TWRP only has 'boot' and 'recovery' as options for the img flash, which I assume is because it's using fastboot and that isn't available.
Click to expand...
Click to collapse
Try manually formatting the system partition into whatever your device has as default, ext4 for example, or alternatively reinstall the stock Rom and continue from there, also, wrong thread