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.
note before attempting any of this that rooting does void your warranty. I also am not reponsible for any damage that is done to your phone but am more than willing to help you solve a problem in IRC. See my signature on how to get on #ally IRC channel. I do not actually use the Clockwork Recovery (i use drellisdees).
Guide to flashing roms on the LG Ally with screenshots. First off. Make sure your phone is rooted. If your phone is not rooted see the following options.
I'm feeling the itch to go beyond the standard settings in Android and get into rooting. I'm following along with a lot of the developments here, but I often feel like I'm missing a lot of the background knowledge and vocabulary (what is recovery, how does one access it, what are all these different programs - nandroid, adb, etc.) to have a really strong grasp of what's going on here.
Now, if this were my computer, I'd just hop right in and start following along as best I can and mess things up along the way, no biggie, I have multiple computers and I'm competent to fix them.
I don't have a landline though, so I want to be a little more prepared before I accidentally brick my link to the outside world. Is there a good "tinkering with Android primer" out there that any of you would recommend?
Also, how easy is it to get back from whence I came on the Ally? I read the thread on unrooting, and I honestly didn't understand a lot of it, so I'm just looking for a "not gonna happen" or "it'll be easy when you finally understand."
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.
Alright guys, latest OTA update just hit my phone. I'm curious if I'm in a safe position to update? I'm using drellisdee's recovery v1.2.3 and Velocity 0.2 From what I've read, Amon-ra and clockwork custom recoveries will block this update from installing. I just want to be sure before going ahead and telling it to install. I assume this will keep my recovery and rom intact, and stop the notifications? Are there any other ways to stop the notifications? Just want to get a definitive answer from someone that's already done this with a custom rom and recovery.
I did not brick a tablet without having a cwm installed first and a nandroid backup. The tablet is an allwinner a23 not in some peoples opinion worth a lot of effort to fix. We have an identical tablet with the same firmware. If I root and install a custom recovery on the unbricked tablet can that zip be flashed without a custom recovery? I have looked about a bit and there seems to be conflicting opinions on this. The only prob I can see is the stock recovery may not have the option to wipe the dalvik cache.
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?
Just rooted yesterday, and everything was running great... untill I installed Simply Stunning v4.3. I went to make a back up and found that I cannot access my recovery, it was stuck at the M. Now Rom Manager says that if this happens, flash a different recovery then flash clockwork back. Here is the catch- When I try to flash a different recovery I get this, "An error occurred while flashing your recovery."
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 rooted my phone using Universal Androot (worked perfectly) and then proceeded to install ROM Manager to flash a custom ROM to my Ally. I used the Flash ClockworkMod Recovery first (sucessfully) then used Backup Current ROM to backup the stock (V8) ROM (sucessfully). I then proceeded to install the Velocity 0.1.1 ROM (sucessfully).
I've searched here a bit, and am unclear as to the process to restore my stock ROM using ROM Manager. I believe it would work as follows?:
Use Manage and Restore Backups. Select backup I made, and then restore.
If I wanted to un-root, I could then just use Universal Androot to un-root the phone (although I havent tried that part yet).
Love the ROM, just curious how to go back if I need to.
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 v126.96.36.199
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.
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.
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?
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.
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).
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 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?