I rooted my phone using erisuser1's rooting for dummies method - this went off without a hitch, I followed the instructions to the T. I put several custom ROMs on my SD card (using the USB, and properly ejecting the phone as a drive) including KaosFroyo v37 and v38, CELBFroyo 3.6, PlainJaneT2_V2, and Vanilla_Tazz_19.I tried flashing each of them (following the wipe of the system info and the Dalvik cache) and all but the PlainJane got stuck in bootloops that lasted a long time. I waited anywhere from 15 minutes to a few hours, and none of the others ever loaded up. I'm fine using the PlainJane and happy to have the other features of root but am wondering if there's any advice or suggestions as to why none of the other ROMs worked for me?
I was attempting to flash a ROM for the first time. my droid is rooted, I thought I was doing everything right, obviously not. I was using clockwork to flash it. I have titanium backup, and I had it clockwork backed up. It said the flash worked, I tried booting, and got stuck on the "droid" animation, it loops over and over. I booted into recovery mode, cleared data and cache. Now I can occasionally get it through the normal boot animation, all the way past the droid eye, but then it goes back to the "droid animation", only its very glitch, and loops erratically. What should I attempt to do?
I have an eris flashed with PB00IMG and I believe I have root access. I am able to remove apps through terminal. I cannot get the google maps to update. I have removed maps.apk, htcnavi.apk and com.google.android.maps.jar. I have removed these separately and all together. I have been able to get it to update before, but I reflashed the PB00IMG because I could not get youtube videos to play without the stock browser. I got the youtube videos working again but cannot remember how to get the maps to update again. I wanted to try flashing different roms. I have downloaded a couple, placed them on the sdcard, and booted but I cannot get them to boot.
Every time I try I get a 'boot failed' then 'error at line 390' installation failed, aborted etc. If I try to reboot it just sticks on the HTC incredible screen. I've tried using Rom manager and directly from recovery. Re downloaded files. Maybe related but any kernels I tried stick on the same screen?
For the past 2 hours I have been searching this site and reading about Rooting and Flashing new ROM's etc. and I'm still having trouble. I downloaded Cyanogen 6.0.0 and when the phone re booted it got stuck at the Cyanogen boot animation screen, and when I pulled the Battery and rebooted in to recovery I was able to restore everything and now the phone works again.
So first off, how long should it take after downloading a new ROM to boot back up with the new ROM installed? And how can I save the ROM in to the SD card? And when I go to DL Cyanogen it asks which home application I should use and gives me ADWlauncher and Launcher 2 as options.
Imagine my surprise when I went to open a purchased book on my Kindle App, and was told that I had exceeded the max number of devices registered to my Kindle account. Upon further investigation, I found that each time I flashed a new rom, it registered as a new device on my Kindle / Amazon account! This was easily rectified by deregistering all but the "6th Eris Device" and I'm good to go. Just thought I'd share this with those readers here who use the Kindle App - no need to do a small flip-out, like I did.
So I rooted a few days ago using Universal 1 Click Method and flashed Xxtrasense ROM immediately (in step 4 of the instructions below).
Step 1) download and install this APK: http://dl.dropbox.com/u/8699733/erisone010.apk - VERSION 0.1.0 Step 2) Run, read disclaimer, press button Step 3) Reboot, once rebooted your phone should have Amon's recovery. Yay. Step 4) Use the recovery to flash rootme.zip that is now on your SDCard, or the custom rom of your choice. Step 5) Go into settings, and turn usb debugging on. After you have root, please uninstall this app.
I want to try new ROMs and have read through a number of threads but its only confused me more on the next steps. Questions are: 1. Do I need to do a NAND or NAND+ext backup (I've done a NAND back up shortly after flashing the Xtrasense ROM)? 2. Is Titanium Backup the only way to get my Apps and data transferred to any new ROMs I flash? 3. At what point is a dalvik wipe required?
If someone is able to provide a step-by-step outline (similar to jcase's 1-click eris root noted above).
I have a Droid Eris that I'm trying to flash from 1.5 to the latest rooted ROM 2.1. My first attempt, I copied PB00IMG.zip to the SD card, disconnected the phone, and flashed the firmware while disconnected from the PC. I think that prevented me from gaining root access, because I cannot remount the system directory using the adb commands (gives me access denied). I'm trying now to flash the ROM while still having the phone connected to the PC, but I'm not having much luck, as I am still being denied access.
I'm running CM7 on my droid and when i run the battery flat, plug it in to charge it. it then boot loops for like 5 mins and works just fine.. also any OC'd kernal suggestions, right now im using one of the chevyno1 kernels but the phone still seems a bit laggy at times what are some good tips to speed this thing up a bit. and how to fix the bootloop issue?
I have tried this on 4 Different Roms (Smoked Glass 4, 5, 6 and Nextheme 0.9) And no matter what I do, if I use a custom sound for notifications, the phone upon restart will boot loop indefinitely, and the only way I can make it stop is to VERY quickly slide the mute left so the phone is muted the next time it boots, then it stops, or if I cant get that to work, I have to restore from a nandroid backup. I have the files on my sd card in /media/audio/notifications All lower case (but have tried with a cap) The only things that hasnt changed, is that I have only tried mp3 files. But I also tried, by using the Zedge Ringtones App to the same effect. Whats the deal? Any Ideas?
Currently running Nextheme 0.9 ESE81 R3 BaseBand C_01.3E.01P
Edit: Also worth note as it may help, its only notifications that causes this issue, custom ringtones and alarms are fine. Even using the same short (8 second) Mp3 as a ringtone causes no issue. And the mp3 plays in the list of notifications when you select it, as it should. The only thing i can think of is possibly that the phones mp3 decoder loads after the boot up sound? Is that even logical?
I've got the rooted 2.1, easy. I've got all the java and adk and what not I got the flash_image and recovery.img. The command prompts all work fine till the last command, (I've tried 2 different chain of commands both work until a certain point).
adb shell mount -o rw,remount /dev/block/mtdblock3 /system adb push recovery.img /sdcard adb push flash_image /system/bin adb shell chmod 755 /system/bin/flash_image adb shell flash_image recovery /sdcard/recovery.img (After this one it says it cannot find flash recovery or image, cant exactly remember.)
- Open the Terminal and copy and paste the following commands with the phone connected to your computer. - adb shell [hit enter] - su [hit enter] - flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img (once again not found but I believe I followed correctly) this the end of commands the first half worked fine.
Both of the stickers - the one on my phone, and the one on the battery still have red X's. I have read that this is good. I dropped my phone in a toilet (recently flushed thank god) in the Staten Island Ferry Terminal (see, nothing good comes of traveling to SI!) and grabbed it out as soon as I saw it. I had a plastic case on the back of it. Took it apart as soon as I got my wits about me. And no, I wasn't using it - It flew out of my backpack when I turned around.
It will turn on but has this odd boot up screen. I don't believe rice will get the water out of the inside, and I don't have a screw driver tiny enough. If I bring it to the Verizon store will they know it had water damage from the screen alone? It looks normal almost like the DOS blue screen of death sort. Also, the little tiny green sticker in the lower right hand corner that says VOID - is that a water damage indicator too? I don't recall ever caring what it was.
I have a customer with a Droid Eris stuck at the boot screen (3 dancing green droid guys) and it wont go past that. I can boot it into Hboot, I've done a factory reset, didn't work. The customer said they deleted all their contacts from the phone, charged it then the next day it was stuck like this.
I have root access, have clockwork mod. i did a nandroid backup as well. now what is the next step? i downloaded rom manager and titanium backup(paid version) i thought i read somewhere about someone sayin that titanium has to be on the SD card or something for backing up the apps maybe same thing with rom manager? a little confused at this point im just a little bit lost here when it comes to flashing roms. i think i wanna flash capt jagers 1.6 rom but im not sure what else i have to do.
i have a ZTE (kis lite v790)..I've found ROMs for it but they are from other providers. the signed update.zip checks if your phone is from the right provider and exits if it doesn't match. All the rooting attempts on my phone have failed and if i edit the update.zipMETA-INFcomgoogleandroidupdater-script it fails the signature check.how on earth am i supposed to update my phone?
So I downloaded two different ROMs from incredible stuff. You know you want it. And I try to install them with Rom Manager by going to Install ROM form SD Card, selecting the zip. I downloaded, and then checking backup and wipe, but when my phone boots back up, nothing has changed. What is it that I'm doing wrong? I eventually rerooted and that solved my problems. I still have no idea what was wrong.
If you have a 3.29.651.5 build and you flash a custom ROM that says it has a base of 3.30.651.2, does that mean that it will update your phone to that particular base build? Or does it mean you need to have that particular build for it to work on your phone?
I want to flash a ROM for the first time but had a couple quick questions. After it is done will my contacts come back? What should I do before I flash a ROM? I already backed up my current rom (sense ui) with the ROM manager app. I have already backed up all my apps as well with titanium backup. I am good to go at this point? I want to try to MiUi rom that just came out.
Now that I'm fully rooted I'd like to experiment with a few different ROMs. My issue is: I'm a heavy user of Folder Organizer (great product). After I rooted initially, I flashed the Fresh 3.3 ROM after backing up using Titanium, Astro File Mgr, AND MyBackup Pro (I don't mess around). After I was done with the flash, I went to restore with Titanium. It didn't restore all of my apps, and actually not much of my data (for example, it didn't restore SMS for some reason). No worries: I went to my Astro backup, it got a few more of my apps, no data.
Finally, I turned to MyBackup Pro, fortunately it restored my SMS data. To wrap it up, I wound up having to restore a few apps from AppBrain, and I had to reset all the folders in Folder Organizer (a real pain). Is there a can't miss backup/restore process when flashing ROMs with Folder Organizer? I don't mind having to restore a few missed apps, but it takes hours to get the folders back. I'm also paranoid about the missind SMS data, but I think I have that covered.
I have been able to flash velocity 0.2 and then decided to upgrade to 0.3. When I did, I looked into flashing the turbo kernel for ally. Followed the instructions as said and now I have the choice to boot to recovery or if I let the boot go all the way through it gets stuck after the verizon logo. When I try to flash a different ROM, I hit install from SD card and everytime, no matter which ROM I pick, it starts updating but says opening file, then like 2 more lines saying opening, then it stops the install.
I have a problem in that every time I flash a ROM, it gets as far as flashing boot and I get the following error:
Writing BOOT:... E:Error finishing BOOT: E:Failure at line 401L write_raw_image PACKAGE:boot.img BOOT: installation aborted. /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue. ClockworkMod Recovery v22.214.171.124
I get this error every time. The weird thing is, despite getting the error, it still works with the defrost roms and has done with every release since 2.0a up until 2.0f. Any other ROM, MCRs, djdroid etc just result in a boot loop as far as the white HTC screen. I've wiped the dalvik cache and data but it makes no difference.
I have been trying different ROMs for months now via ROM manager. Anyway, I downloaded a ROM to my SD card (I always pick the "download folder") and then go into ROM manager and choose "install from sd card" but I can never see the ROM. For example, last night I DL the red theme for the redemptive ROM. I did not get any error messages. It look to transfer just fine. But I can find the blasted thing! I've tried looking via TB but still nothing. I've also tried via recovery but that did not work either. I have a feeling I am overlooking something stupid and as I said...will feel quite dumb but oh well.
I'm currently running Froyo after running the RUU: RUU_Bravo_Froyo_HTC_WWE_2.09.405.8_Radio_32.43.00. 32U_5.09.00.20_release_140022_signed.exe as per teppic74's thread over here: Froyo RUU update available
My desire has HBOOT 083 - which I know can be problematic when flashing. My question is: Is the unrEVOked v3.21 method of getting the new recovery menu the best/easiest/most reliable way to enable me to flash new roms on my phone? Are there any caveats? Anything I should be aware of beforehand? According to teppic74's thread, this version of Froyo cannot be rooted at the moment, which I'm not bothered about anyway. But, it would be nice to try some of those lovely new roms.
I have had no issues before, but now when I flashed the rubix focused 1.0 (from rubix 0.3) i have lost all but 20 camera pictures and all but 1 downloads. Even more odd is that when I restore to my backup the pictures show up but then they start to disappear. I connected my phone to my laptop and only the 20 pictures show up in the camera file, however, ALL of my pictures (camera, download, wallpapers, etc) show up in the thumbnail folder but the quality is not very good (obviously). does anyone have any idea how this happened and what I can do to get my pictures and videos back?
I just put Froyo 2.2 on my Moto Droid using this ROM: http://androidforums.com/roms-droid/127966-rom-stable-android-2-2-frg01-clean-untouched-virgin.html
And I used the 800mHz kernal found here:
How To: Get Android 2.2 (Froyo) On Your Motorola Droid Right Now! | TheUnlockr
I am experiancing a few freezing problems and bad start ups, but I am assuming these kind of surprises come with flashing different ROMs/kernals onto your phone. I noticed, however, that occasionally my screen will get really "twitchy" e.g. when I press a key on the android on screen keyboard it types the letter 4 times. or when i drag the notifications bar down half way and keep my finger still i can see the bar twitch up and down rapidly. I have heard from several review sites that twitchiness and stuttering usually have to do with the processing, which made me think of the kernal change. Does this mean i picked a bad kernal or a bad speed? If i get this twitching does it mean get a faster kernal or a slower kernal?