[Q] Odd error - in RECOVERY - execute update.zip or not? - Droid Incredible Q&A, Help & Troubleshooting

So I grabbed the OTA ZIP file that was posted here - THANK YOU by the way.
I boot into recovery and I am presented with the following :
Android System Recovery (2e)
the usual 4 menu options for Reboot, Apply sdcard:Update.zip, Wipe data and wipe cache.
I get an error on the recovery screen that says :
E: Can't open /cache/recovery/command
Can i still run the update? This is a relatively stock Incredible (Rooted, S-Off then unrooted.
Thx
Ron

I got that same error, pretty sure it just has to do with the 4 recovery commands your seeing right now. It probably just recreates that file once you see the commands. I went ahead and flashed the update.zip. I got other errors as it was flashing, but I don't they're linked.

Related

[Q] Rom Manager - Failed to Seek

Anytime I try to do anything through Rom Manager (flash a ROM, nandroid backup, etc.) upon rebooting into recovery, I get a white triangle with an yellow exclamation point. After pressing the power button, the following text is revealed along with the Clockwork Recovery Menu.
Finding update package...
Opening update package...
Verifying update package...
E:failed to seek in /cache/update.zip (Invalid argument)
E:signature verification failed
Installation aborted.
If I select advanced->Reboot Recovery after receiving the error, the device reboots. After this second reboot, the process continues as it should have after the first reboot. I've tried downgrading the version of my Clockwork Recovery, but it seems to have no effect.
Any ideas?
...
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
2) Is your card FAT32 formatted
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
jdmba said:
I believe the standard array of initial questions would be:
1) Did you flash S-OFF?
Click to expand...
Click to collapse
Yes.
jdmba said:
2) Is your card FAT32 formatted
Click to expand...
Click to collapse
Yes.
jdmba said:
3) Try redownloading the file using a different browser (to ensure a cache doesn't deliver the same update.zip without trying)
Click to expand...
Click to collapse
This failure isn't specific to any one file. Besides, I don't think it's a corruption of the file since it works when I select "reboot recovery" from the first failed attempt. In fact, this even happens when choosing "Backup ROM" from ROM Manager.
On a side note, I've tried wiping cache in ROM Manager as well.
Toggle Signature Verification and/or is d/l corrupt?
In CWM, have you tried toggling the on or off setting for the signature verification, as well as the other toggle?
Also, I read some superb advice here:http://http://forum.xda-developers.com/showthread.php?t=765930
check out the advice in post # 285 and see if that fixes you up.
Everyone seems to think my downloads are corrupt. That is definitely not the problem. If they were corrupt, they wouldn't function after the first reboot. They would continue to fail. Let me try explain my problem another way...
Here's my device setup...
Radio - 2.15.00.07.28
Kernel - King's BFS #4
ROM - SR Vanilla RC 2
CWM Version - 2.5.0.5
ROM Manager Version - 2.0.2.6
Here's a process I'm following...
1. Open ROM Manager
2. Clear Download Cache (Just to be sure!)
3. Select Backup Current ROM which causes reboot into recovery.
4. Receive the error which I outlined in my first post. *NOTE* I have not downloaded nor chosen to flash ANY update.zip files. *NOTE*
5. Open the advanced menu in CMW and choose "Reboot recovery" which causes the phone to reboot into recovery.
6. The backup progresses like it should have after the first reboot.
Again, the process above does not involve the use of any downloaded update.zip files. No ROMS, no Kernels, etc.
Does ROM Manager create it's own update.zip file stored in /cache to execute whatever function it needs to after reboot? It appears that might be the case.
I've attempted to reinstall ROM Manager and downgrade to an early version of CWM in ROM Manager. Neither seem to have helped.
I had the same problem trying to flash the latest leedroid
I entered recovery, de-selected signature verification and then flashed the rom through recovery mode.
Flashed normally and up to now it looks like it worked (waiting for first boot)
Hope this helped
Both signature verification and script asserts are toggled off. This is why the update.zip will flash after the second reboot into recovery and manually.
In recovery, is cache, data, or system mounted? If so, can you unmount any/ all, and reboot?
Sent from my ADR6300 using XDA App
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
PIYIRIO said:
I just started having this problem today, at least i noticed it today. It acts as if the signature verification is enabled the first try and disabled the second time. I can't find ANY way to fix this but reboot recovery and it works... If anyone finds a solution, please post.
Click to expand...
Click to collapse
Did you change anything today? I found someone in the SR ROM thread today that started having the same problem.
No, only an app and removed it. I dont know how long it has been broke since I haven't used it since SR 3.0rc1.. got tired of the reminder for rc3 and it wouldn't automagically run the install.zip.
Interesting.... Please post as this shakes out.
Sent from my ADR6300 using XDA App
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
srt4mn said:
I have this same issue, I think it's an issue with Rom Manager. No matter what I try to do from there (Reboot to Recovery, make backup, flash zip, etc.) I get that string of messages.
If I download a file from ROM manager to be flashed, I have to move the file to the root of the sd card before booting to recovery for it to flash correctly. I have just gotten used to doing it this way.
Click to expand...
Click to collapse
Me as well
PIYIRIO said:
*edit* I also noticed the "Fix Permissions" utility doesn't work in ROM Manager. Dont know if this is related or not.
Click to expand...
Click to collapse
If you look in the OP for the SR ROMS, you'll see that a known issue. He includes a fix_permissions binary instead.
I've reached out to the developer. Hopefully we will hear from him soon.
Can you guys try clearing your download cache, and then reflashing recovery?
Possible workaround
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Cache wipe have been tried, see post #3.
I have some info that may be valuable:
This evening I rooted my Desire (SLCD) using Unrevoked 3.14 and recovery-clockwork-2.5.0.7-bravo.img I realize this is the incredible forum but hold on.. hear me out
I observed the _exact_ same behavior:
- Yellow eclamation + second reboot to recovery would run backup, also happened when selecting "Reboot Into recovery" in RomManager (RM)
- Tried DL cache wipe in RomManager,
- Tried reflash of recovery
This fixed it for me:
- Re-root via Unrevoked 3.14 using recovery-clockwork-2.5.0.1-bravo-slcd.img
- Re-flash CM (this may be optional, I don't know)
- Boot ROM and start RM just to have it tell me I need to install recovery (obviosly didn't detect my 2.5.0.1-bravo-slcd)
- Allow RM to flash 2.5.0.7-bravo via download
- Now "Backup ROM" and "Reboot to recovery" works as intended
- RM reports 2.5.0.7-bravo installed, recovery booted (via RM) is 2.5.0.7-bravo BUT recovery booted using HBOOT (back+power on Desire) is 2.5.0.1-bravo-slcd (!)
Note: Incredible users should _not_ use -bravo recovery images(!) just outlining how I made it work to help you find a solution
Koush said:
Can you guys try clearing your download cache, and then reflashing recovery?
Click to expand...
Click to collapse
Worked for me. Thanks Koush!
Sent from my ADR6300 using XDA App
Didn't work for me.. I've tried everything that I can think of. Different SD cards, i've formated /data/ /cache/ and reinstalled..
i'm using virtuous 2.7

Two issues: "Infinite Boot screen" and "Can't Mount /sdcard/" in Recovery Mode

Two issues: "Infinite Boot screen" and "Can't Mount /sdcard/" in Recovery Mode
Hi Guys I need some help,
So I rooted my tablet and installed CWM following this (I did not install CM), went ahead and rebooted the system, but it never actually boots, only displays the boot logo screen and never moves from there.
So I downloaded this rom and bootloader and pushed it to the tablet via ADB, then I go to Recovery Mode and try to flash it following the CWM menus, install zip -> choose zip from sdcard, then it tells me "E: Can't mount /sdcard/"
What should I do now? how can I fix the infinite boot screen and/or sdcard issue?
Thanks
Got everything back to normal.
Followed this to flash stock system/boot/recovery. Then flasehd TWRP and SuperSU to root the device

Boot loop after 4.4.2 update and Clockworkmod install

Stuck in a bootloop. Here's my story.
Updated to 4.4.2 earlier today.
Tried to root my Nexus 7 later after the update. Here's what I did:
rebooted into bootloader with adb (adb reboot-bootloader)
unlocked the bootloader with fastboot (fastboot oem unlock)
flashed clockworkmod using fastboot (this is the file i downloaded and flashed: -http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.3-flo.img)
rebooted into recovery
selected "install zip>choose zip from sdcard" (trying to install supersu.zip file that I had loaded onto the internal memory)
Here's where I ran into trouble. After selecting "choose zip" nothing happens, and a message shows up on botton of the screen that says "E: Can't mount /sdcard"
So I can't install anything from clockworkmod.
I rebooted into bootloader, tried to re-flash using fastboot - "device not found"
I tried to reboot the device into android - bootloop animation
I tried wiping data, cache, factory reset, dalvik chache, etc from recovery - still getting bootloop animation
Any ideas?
Ok, I wiped/deleted sdcard data from clockworkmod and I managed to get it to boot.
That's deadly but I still don't have root, which was the point of this in the first place. Anyone know where I went wrong?
Strange. I did pretty much the exact same procedure and it worked for me.
Sent from my Nexus 10 using xda app-developers app
So, I flashed TWRP.
Tried installing SuperSu from there. This worked slightly better than Clockworkmod Recovery, it at least could read the internal storage, and allowed me to select the supersu.zip file. But I get the following error when I try to install it:
E: Unable to open zip file
Error flashing zip 'sdcard/Download/UPDATE-SuperSU-v1.80.zip
Not sure what's happening here.... May have to do with the 4.4.2 update? Maybe I'll try flashing the 4.4.2 factory image and then retrying the above steps.
I also did pretty much the same. I had a new Nexus 7 2013. The very first thing I did was to update to 4.4.2 through OTA before I went to rooting procedures:
Unlock bootloader (data was wiped because of it)
Flash TWRP
Flash superuser.zip file through TWRP
Everything worked fine.

[Q] VZW HTC One - Stuck in Recovery

Team,
I've consider myself a fairly intermediate android root user. I've been doing this for many years, and have never had an issue that I was able to get out of (with the help of the xda community, of course). I've personally never had to post a question on here because I'm always able to find someone who has a similar issue to me. Today though, I am stumped...
I've been happily running Slimkat: http://forum.xda-developers.com/showthread.php?t=2590649 for the past few weeks.
This morning, I decided to try the ElementaX kernel (http://forum.xda-developers.com/showthread.php?t=2249774). After flashing the Kernel, my phone refused to boot up. Usually, I would just reboot into recovery and re-flash the ROM I've running (which includes the ROM's kernel). Every single time I've flashed an incompatible kernel in the past, this method has worked.
After choosing to flash the ROM, it got stuck while installing. The installation just sat there for at least 20 minutes.
Next step - I decided to wipe data/factory reset and then re-flash the rom. Data was able to be wiped, but then it got stuck on formatting cache....
So I hard reset, and decide to restore my nandroid backup - As soon as I boot up CWM Recovery, I get this 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
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
When I tried to restore the backup, it just timed out again...
I reflashed CMW REcovery via fastboot, and even tried TWRP Recovery. Nothing seems to work.
If I try and restore my nondroid backup now, I get an MD5 mismatch.
I'm unable to mount /system, /cache and I'm getting nothing when I try and mount USB storage.
I've soft-bricked devices before (we are all careless sometimes), but I was always able to find a solution somewhere. I think I got myself into a situation that's a bit above my paygrade.
Any help would be greatly appreciated.
Thanks.
Are you sure you reflashed the correct recovery? Try this one just for kicks http://vzw1files.dyndns.org/RECOVERIES/twrp/openrecovery-twrp-2.6.3.4-m7vzw.img If it still dosent work, i would try an ruu.
cmlusco,
Thanks for the quick reply. I flashed the recovery - Unable to mount System or Cache and PC is not detecting any devices when activating ADB sideload through TWRP.
To be honest, I never of an RUU before. I can research the topic. If you know of any threads that could help me along the process, I would definitely check them out.
thanks again.
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
OMG OMG OMG... you saved me
Pharaohnee said:
The RUU method worked! Thank you very much for suggesting that.
Here's what I did.
1. Download VZW RUU.zip from the following thread (http://forum.xda-developers.com/showthread.php?t=2428276)
2. Rename to "ruu.zip" (Optional)
3. Enter fastboot mode
4. enter "fastboot oem rebootRUU" - You should not see a silver HTC logo on your device.
5. enter "fastboot flash zip ruu.zip" - The first time you execute this command, it only prepares the flash
6. As soon as the flash is done preparing, enter the same exact command again "fastboot flash zip ruu.zip"
7. Now you'll see a little green progress bar on your phone. This does not need to reach 100%. As soon as your command window is finished, you can just "fastboot reboot".
8. You should be set back to fully stock HTC One.
Thanks again,
Click to expand...
Click to collapse
Some of the RUU's i found the download was funky but here's the one that finally worked
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
I was stuck in this situation... something with my cache got messed up when I tried to let ROM Manager update my CWMR... never again.
Glad you got it worked out, could you put solved in thread title it help others, thanks

Soft bricked Nexus7 can't get through "Can't mount" errors

Hey guys,
I was googling for the past few days who else might experience such problem, but I haven't stumbled upon such case. The problem is, I'm stuck on the bootloader part.
The initial goal was to root the device, so:
- I unlocked the bootloader,
- installed clockwork-touch-6.0.4.7
- wiped everything
- when I try to install SuperSU & new ROM I'm getting errors like
Code:
Can't mount /cache/recovery
Can't open /dev/block/platform/msm_sdcc.1/by-name/misc (No such file or directory)
Can't mount /cache/recovery/log
and a few other errors in this fashion about cache.
When I actually run the
Code:
abd sideload aicp_flo_n-12.0-UNOFFICIAL-20161020.zip
the installation tries to mount folders like /data but gets an error.
Finally it says
Code:
E1001: Failed to update system image
Installation aborted
Is there a way to re-format everything to FAT using fastboot and then begin everything from scratch? I have a feeling this is filesystem problem that it can't read properly or something... Maybe I'm wrong? What would be your suggestions?
Thanks!
I had a similar issue on mine a few days ago. I was completely stock and wanted to unlock bootloader, flash a custom recovery and then finally a custom ROM. I was successfully able to unlock the bootloader and flash the recovery (latest TWRP). But, when I tried to boot into recovery, it went past the recovery logo and then showed me errors like yours inside the recovery and rebooted. It then automatically booted into the recovery, showed the same errors and rebooted again. I wasn't able to do anything apart from booting into bootloader by sending an adb command.
Now coming to the part which fixed my errors. What I did was used the "fastboot -w" command (without the quotes) while I was in bootloader to wipe everything and after that, flashed the recovery again. Then I was able to successfully boot into recovery and everything has been fine since then.

Categories

Resources