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
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.:
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?
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.
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.
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 recently got a new droid incredible (my first phone besides the crapy razer) and my friends told me to root it. I used the guides on these fourms, rooted it, and apparently it worked (I have superuser and can download root only apps). The only problem is that everywere, it says recover once you root. Every time I've tried this, it just leads to a black screen with two white lights on each side. I've tried everything to fix it; I've looked at multiple threads and youtube vids, I even found an app that should sent it into Clockwork recovery mod, but even then it still had the problem. Does anyone know how to fix this, or should I just try un-rooting it (maby I did something wrong and it dosent say) and re-rooting it again?
When installing certain custom ROMs on rooted Android smartphones or tablets, you will encounter Status 7″ error issues once in awhile with ClockworkMod (CWM) Recovery.Status 7 error is caused while the ROM's updater script file checks to see if the phone model of your phone is compatible with the ROM you are installing, called asserts.
Asserts is a safety mechanism so you don't accidentally install another phone model ROM on your phone. E.g. You tried to install Galaxy S2 ROM on a Galaxy S3 and ending up hard-bricking your phone but you got Status 7 error which saved you.this safety mechanism is great but there are times where even if you have the correct ROM for your phone, you will get Status 7 error.
This is due to an error by the developer of the ROM in the updater script, causing havoc, making people install another custom recovery like TWRP recovery for no reason. You can fix the issue by installing TWRP recovery but if you need to restore your CWM backups later down the line, you will have to re-install CWM recovery, causing a big hassle.
Also, if you update to the latest CWM Recovery using ROM Manager, usually this problem is fixed.But what if you did update to the latest CWM Recovery and still happens? And yes, it does happen even when you update your CWM recovery.
If you simply don't want to change your recovery (because if it ain't broke, don't fix it) or you still get Status 7 error after changing recovery, you can simply edit the updater script yourself to get rid of the asserts.All you need is a computer and a zipping program! (You might be able to even do it on your Android device with AndroZip and text editor but I haven't tried yet.) MAKE SURE THE ROM YOU ARE INSTALLING IS COMPATIBLE WITH YOUR ANDROID DEVICE AS INSTALLING WRONG ROM CAN BRICK YOUR DEVICE!
Make sure if you are installing a ROM on AT&T Galaxy S3, the ROM zip file you downloaded is for AT&T Galaxy S3 not for Verizon Galaxy S3.
Step 1. Copy the ROM zip file to your computer and extract it using your favorite unzipping software.
Step 2. Once unzipped, browse to the META-INF/com/Google/android directory. You will find two files called update-binary and updater-script.
Step 3. Rename updater-script to updater-script.txt and open with your favorite text file editor.
Step 4. Get rid of the line starting with assert to next semi-colon. Usually this is the first line or one of the first lines at the top of the text file. Just delete them.
Step 5. Save file.
Step 6. Rename updater-script.txt back to updater-script.
Step 7. Rezip all the files yo've unzipped.
Step 8. Copy the new, edited zip file to your phone.
Step 9. Try re-installing ROM, now it should install fine without Status 7 error.
I have a rooted samsung captivate with sideloading enabled. After experimenting with different wifi tethering apps from the unofficial market, I began experiencing difficulties with my wifi connection. Even after uninstalling every app that I thought was changing the wifi state, the problem still persists. I can turn on the wifi and it will act normally for about 30 seconds before turning off without user intervention. In dmesg, the error is as follows: 'mmc1: Got command interrupt 0x00060001 even though no command operation was in progress.' Is this caused by an app or is this a more complicated problem?
can you flash this before you actually root your phone so you dont get bricked?and what are the ways to get a REAL brick? because i've tried looking and everyone has gotten either a usb brick or something else where they can just reflash or something.
I rooted it last week with the unrevoked 3 method which seemed to go ok then i tried some different roms and some worked some didnt. I tried to install the r8-bravo-desire-modacocustomrom-withadditions-a2sd+-signed...! This rom got stuck on the white start up screen. I thought that if i cleared the sd card it would install but still the same thing then i just got the white htc screen which i cant get off and i cant load the recovery to change anything...! The sd card is working and i can get into the hboot and when it reads the sd card says wrong img! Is there something missing on the sd card? Have i bricked my phone? Any ideas on a fix?
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...@firstname.lastname@example.org': No such file or directory I/dalvikvm( 1334): Unable to open or create cache for /system/app/ test.apk (/data/dalvik-cache/system@a...@email@example.com) 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.
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).
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 recently bought a cheap irulu tablet off ebay. it's running 4.2.2, and i'm not quite sure if it's rooted or not. i've read that most of their tablets are rooted right out of the box, so i downloaded 4 or 5 root checkers from the marketplace and some said it was rooted and some said it was not. i know that it does have su and busybox installed, but i don't have one of those superuser apps that request permission or anything. i can browse my full phone with any file explorer. i installed titanium backup, and it says on the main screen that root access is ok, but then it will pop up an error message that says:
BusyBox works but the "su" command does not elevate to root. There's something wrong with your "su" binary and/or "Superuser" app.
UPDATE Using the manual method I got to step 18 of copy and paste of the commands. But now I got the "read error (out of memory)" message while pusing the "flash_image recovery recovery-RA-heroc-v1.5.2.img" file.
When I type ADB devices, it comes up with this error: 'adb' is not recognized as an internal or external command, operable program, or batch file. I already installed the adb drivers, and Windows told me the drivers updated successfully. Any idea why I am getting this error? I hope to be rooted by the end of the night!