I'm pretty impressed with this build. I especially love the screen off animation and orange highlights at the end of the list. Flashed a P3 standard volt 250-1000 and it's running fine. A little hot, but so was the stock kernel. Here are my issues:
No orientation change (already knew this would happen)
No camera (I thought it was only camcorder that didn't work?)
Keep losing mobile data (have to switch to airplane and back)
Signal/Wifi bars are grey instead of green
Anybody know of any fixes for these? Or are they common?
I think you meant your last post for the CM7 thread:) But we get your meanin'. Thanks for the take on 7.
Looks like everyone got the Image flash sorted. Cool. Now the big question. As this recovery is not supposed to be able to restore backups (nandroids) made with earlier recoveries, nor is it supposed to be able to update.zip most update.zips made to date, has anyone tried either?
Now be honest with me.
If a recovery image can't install updates or load backups, what's the point? :)
I am not sure why anyone would want this just yet. I've been flashing cm7 with 188.8.131.52 perfectly fine.
Sent from my Droid using Tapatalk
I downloaded and flash it just fine. It does seem to have a problem with flashing some zip files but I noticed this too with v184.108.40.206. I tried to flash CM226 and it said it was bad yet i know it works, I flashed a the sapphirev2 zip and it worked fine. Nandroid backup and restore also work fine for me, I just tested them. The only problem is that the whole thing is kinda slow, which according to Jeffv2 it a kernel problem.
Ive been messing around with the CWM source for a few days since I want to make my own modded version. I couldnt find the source for 220.127.116.11 (the one we use), so I decided to work on CWM3 since its the future and is updated regularly (My mods are easy to do). I'm downloading the git tree for gingerbread now and once I compile the latest recovery image I'll upload it for everyone to test out.
As for the "out of memory" error we all seem to get at times when trying to flash the image, just keep trying it will work eventually. You can try flashing another recovery or another CWM and it may work, try a reboot and then do it, etc... I've found that the easiest way to automate the flashing process is to use ADB and these commands:
sudo adb start-server
adb push ~/path/to/image/[recovery name].img /sdcard/
adb shell flash_image recovery /sdcard/[recovery name].img
adb reboot recovery
this is for linux, but essentially what it does is pushes the recovery image to the phones sdcard, flashes it automatically and then reboots the phone. All is done in about 30 seconds, it saves you a few minutes of doing it manually. Make a shell script out of it and its even easier!
brando flashing this the same way as 18.104.22.168?
awesome thx ......
personally i like the new look.
lol rom manager kinda doenst work any more ah well
Not much different than the whole Microsoft thing. Build it and they will come. Or is that build it and they will have to buy a bunch of new software after they come:icon_evil: I foresee a lot of arm flailing and teeth gnashing in the near future, and those threads about sprecovery v. CW will probably get very lively........
Originally Posted by furbearingmammal
Still, I am for everyone moving forward, and will do so. But then I still run XP, and have plans for my D1 for a long time to come, so what do I know?
Got 22.214.171.124 to work. Not too worried about ROM Manager since I do my ROM installs manually with CWM. Hopefully ROM Manager will catch up and get 3.x working with the program.