Motorola Droid X :: E:Can't Open /cache/recovery/command - 2.2
Aug 21, 2010
So, has anyone with this error been able to push the update through? i read (cant find it now) that this has something to do with OTA updates. the way i understood it was, this is a folder Verizon looks for during an update. so if thats true would it cause me to get stuck in on the MOTO LOGO screen?
I took unrooted my phone today because I was going to excange it for a new one because of a loose headphone jack but it turns out it was my headphones. I used SMupdater and it went fine. now when I try ot root again I get a "can't open cache/recovery/command" error in recovery and it wont let me select any of the options by hitting the camera button. idk what to do
So I am trying to root my phone I am at the point where I am rooted and I have made a nandroid backup. I have moved those files to my computer and put the bugless beast nandroid files in their place. The problem is when I go to Droidroothelper and select reboot/recovery my phone reboots and the /! comes up on my screen and a line on the bottom says E: can't open /cache/recovery/command......
any tips I dont know what to do to load the nandroid backup of the bugless beast.
I was having black SLCD (RUU_Bravo_HTC_WWE_1.21.405.2_T2_Radio_32.41.00.32 U_4.08.00.09_release_137222_signed.exe) and have solved the problem right now and do OTA update to Froyo and there is System Info.:
Following the big guide and I am at the nanroid backup stage in the recovery utility. I've got Android system recovery utility Use trackball to highlight, click to select. Options: Reboot system now [home+back] Apply sdcard:update.zip [alt+s] Wipe data/factory reset [alt+w] Then at the bottom it says E: Cant open /cache/recovery/command Thats the full screen, nothing about backup/restore
I have just recently rooted my wife's phone because she saw a couple of themes she wanted and I informed her the only way to get themes like what she was looking at (J-Rummy's Pink Life) was to root and rom the device and then theme it. So what I did was just root the phone using RSD Lite by installing SPRecovery on her phone and then applying the root update.zip file to the device. No problems from that point on. I did that a few days ago. I just went ahead and purchased Rom Manager for easier application of Roms/Themes. I downloaded Lithium Mod/Pink-Life Rom and then selected clear data and cache and install. I have run into nothing but problems. I am getting constant force closes, system freezes, reboots, etc. So, first thing I think of is, different kernel. Same thing. I try three different kernels and get the same problems. I then decide to just revert back to her previous setup (clean 2.1 with Root access). Everything is back to normal with no issues at all except for the fact the wife wants a Pink Rom.
I then decide to try BB 0.4, thinking maybe it had something to do with the ROM. I installed it the same way as I did the last one. I did everything through ROM Manager. Got the same results. I just wanted to make sure I listed everything I did so maybe there could be some different insight on what is going wrong, but my question is...is it better to reboot into recovery and wipe data/cache and then install from recovery or just install through Rom Manager? I know that sounds dumb because Rom Manger boots into recovery anyway and does exactly what you would have done, but does it truly do it the same is my question? If the answer is yes, Rom Manager takes care of all that for you, then does anyone know of anything else I could try to maybe get a ROM running on this device without all of these problems? I am running out of ideas. I have even tried installing it through SPRecovery (changing the name to update.zip of course).
Recently I switched to SDK 1.1 and it worked for a short time without any problems. Now I'm getting "Can't open dex cache '/data/dalvik- cache/system ..." error and emulator doesn't start at all. Just shows Android screen of death with blinking cursor. When I repoint Eclipse back to 1.0 r2 it works fine. I did adb shell and /data folder is empty.
I'm brand new to this world of mobile Internet.I feel like a kid in a candy store with all the neat apps out there for my new 3G.I was wondering, among all the endless apps out there, is there an app which allows me to open other apps simply by saying their names? Ex. "open Settings", "open Google Maps", "open Pandora".I just know it's gotta' be out there.
When I am trying to build my application as a part of image I am getting the following error :
E/dalvikvm( 1334): Can't open dex cache '/data/dalvik-cache/ system@a...@email@example.com': No such file or directory I/dalvikvm( 1334): Unable to open or create cache for /system/app/ test.apk (/data/dalvik-cache/system@a...@firstname.lastname@example.org) E/Util( 1334): Class Not Found : java.lang.ClassNotFoundException:
But when I push the apk manually to the device (into system/app), it works fine.
I am wondering why is it so as both ways the apk is present at system/ app only.
Am I wrong in thinking that a dd based tool would be better than having to rely on a 3rd party recovery? If you used to dd, you wouldn't have to deal with any of that stuff right? Could you not just make images of all the partitions of your device and store them on your computer as backup? Then if you get bricked, could you not use those images again and just re-image the drive?
That's the problem I'm having with my device. My buttons will no longer function so I can't flash anything in the recovery and using Odin (Samsung) to flash works but no existing roms or kernels that I can find will fix the touchscreen.
However, I can access the device through ADB and I'm assuming I could get the device to show its partitions on Linux right? So then could I use someone else's existing partitions and re-image those on my device?
Is this possible? I'm trying to make an automated script without any user interaction. I can select sideload mode manually using the volume and power buttons when in ClockworkMod Recovery, however I want to enter sideload mode using the command prompt from my computer.
I hit the top button. Flash Clockworkmod recovery or what ever it said. I then backed up my Current ROM. I then downloaded Cyanogen v6.0.0 cr2. It downloaded and rebooted my phone. But It went to a screen with a Triangle w/ exclamation and a phone under it. I then hit the up vol button and camera, and now I'm at the Android system recovery page and I don't know what to do next. These are my options reboot system now apply sdcard:update.zip wipe data/factory rest wipe cache partition wipe base band data. I did click to backup current ROM and wipe data and cache.
First off let me say that I was wrong about this issue. Its not an issue with Easy root it is just something built into android. So I apologize to anyone I argued this subject with but specifically Patch. Its also not an issue with rom manager. This applys to users that after flashing a custom recovery they can boot into it once but the next time you try to boot into recovery it has reverted to stock.
This mostly happens to users of easy root or users that use my guide for rooting using Linux
So for the fix.
Download this file and place it in the root of your sd card. http://dl.dropbox.com/u/7223192/install-recovery.sh
Download Terminal Emulator from the market. The one by the dev Jack Palevich. Open it and type the following commands.
su mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system dd if=/sdcard/install-recovery.sh of=/system/etc/install-recovery.sh chmod 550 /system/etc/install-recovery.sh sync
after that just flash the custom recovery of your choice and you should be good to go.
I tested this on my phone and another user tested it for me and it worked for both of us. If anyone has an issue let me know. This issue is so sporadic that its hard to have people test the fix.
I was looking through the files via ASTRO and also Files last night. I noticed several cases where folders, which I removed the app, were still in the directory. Also, the Zedge folder was full of images from browsing I presume.
I've cleared the cache via the browser and a lot of stuff was not removed. I thought I deleted an app and traces still remain.
Wanted to wipe data/cache before i flashed a new rom..so i did it in recovery..but after i did it and rebooted, when i got to the "touch android to begin" the touch wouldnt register..what's the problem? tired it a few times and was the same.
I'm considering installing a rom and I've heard that doing a data and cache wipe is the proper thing to do to ensure success. What I'm concerned about is how easy it is to restore/re-do all of your settings like ringtones, notification settings, app settings etc. How long does it usually take you to set up your phone again after installing the new rom?
If you do not root, you could go from 2.0.1 to 2.1 with no wiping of data and cache, it just installs & away you go. Same with 2.1 to 2.2. No wiping of data and cache and all is still there as you left it: apps, settings, preferences, etc. SO, why is it important to do this if you root? What's the difference? And, who said it was important to do? Is there some exact proven logic on why if your rooted you must do this and if not, your somehow fine? That 1 step difference causes a lot of extra work, so I am wondering why this is said to be a must for rooters and non rooters need not do it when they get updates?
Using the widget to read stories is draining the memory down on me, has anyone found a way to clear the cache for it? clearing the browser cache doesn't do it, and I have 5mb that's gone from reading the stories.
Browser seems to chew up memory pretty well, which is usually okay, but it would be good to be able to clear it. Well if you long press on the back button you get an option to exit and clear cache. Neat. Any other apps do this?