• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM][WIP] BACKside ROM (CM7) + Green Machine Theme

Go to recovery and wipe cache partition,and Dalvik cache. Then install the BACKside ROM,then install the the gapps. No Green Machine Theme. Reboot

OOPS Let me rephrase that then.. xD How do remove the Green Machine theme WITHOUT having to go thru recovery again? :D
 
What have I done wrong??? Installed this ROM, liked quite a bit about it but continually got "ADW.Launcher is not responding" error message which caused the phone to reboot. So I went to my ClockworkMod Recovery v3.2.0.1 to restore my previous back-up but get a "MD5 mismatch!" message. I've never encountered this problem before now. I have restored backed up images before without this error message but now I get it regardless of which restore point I try. Are all restores corrupted? Can anyone help me to recover any or all of them? Is the ClockworkMod Recovery v3.2.0.1 of been using the culprit? I can easily flash a ROM again but I would hate to lose the 5 restores I have because I like each for different reasons. Please help and I thank all for any assistance.
 
Just flashed this lovely rom. Much better then aosp in my opinion. Was just wondering because I'm experiencing the slow sensor rotation like in aosp, if this was still an issue being worked on or if there is any fix for it.

Cheers!
 
Just flashed this lovely rom. Much better then aosp in my opinion. Was just wondering because I'm experiencing the slow sensor rotation like in aosp, if this was still an issue being worked on or if there is any fix for it.

Cheers!

I'm not 100%, so don't crucify me if I'm wrong, but I believe that the sensor rotation speed is a "problem" with the phone. My V has always been sluggish when rotating, even on stock...
 
Have you tried to format the SD card with the recovery menu before you put anything on it. If not, you might want to copy data to a folder on your PC. Then format the SD card in the recovery under mounts and format. This is just a shot in the dark in case you have run out of viable solutions,and might not be the most correct solution.

I formatted my sd card and think i figured it out. I dont think that my sd card was mounting properly so i mounted via the recovery menu and went to the USB MS under recovery and Viola it worked!

edit: Mass Storage doesnt work when its booted up normally but that doesnt bother me as long as it works somewhere

edit 2:downloaded clockworkmod recovery, formatted sd card and did format of phone and install of rom and it works perfectly. who knows what it was but I probably missed a step originally when I flashed and it just carried on until today.
 
Just flashed this lovely rom. Much better then aosp in my opinion. Was just wondering because I'm experiencing the slow sensor rotation like in aosp, if this was still an issue being worked on or if there is any fix for it.

Cheers!

Found on another forum discussing Bumblebee2.4 ROM: "Kernel updates: accelerometer improvements (makes games using it more responsive)", so possibly it can be improved through the kernel. From personal experience I've found clearing the cache then optimizimg the RAM via Memory Booster greatly increases the sensor's responsiveness.
 
Hey Jerry...really appreciate the work you and Blarfie are doing here. I still can't restore any previous back ups (and would still appreciate anyone's assistance regarding this) but I did reflash this ROM several times and now seems to be working better and I'm very pleased...even scored a 2073 on Antutu's benchmark test which is higher than any other CM7 I've tried (ath3no's was my second highest at 2027, excellent work).

I am experiencing one problem I have not not found with any other CM7 ROM thus far. The Android market has an app called "vmplayer", by ajeet vijayvergiya, that I use to watch .avi movies stored on my sd card. I like it because I can cue several movies at once then press play and they will play one after the other without issue. However, with BACKside vmplayer crashes immediately upon pressing play. Something in the script? aosp's and ath3no's played it fine so I imagine this one can, too. Can something like this be fixed? It is the only quirk I've found so far and probably of little importance to anyone else. Keep up the good work, you guys are making the Optimus V more enjoyable.
 
Regarding the bluetooth... last year I bought a cheapo $15 walmart special Emerson headset. I broke it out and started testing. It paired easily, made a few phone calls and Pizza Hut and Dominoes sounded great. I didn't receive any phone calls... I've got no friends. But everything else looks good on the cheapo end. Great job guys!!


I, too, have no friends but the real question is...Did you order a pizza and, if so, what kind. Mmmm....pizza....<drools>.
 
ECTOTHERM, Welcome. These new CM7-IHO ROM's require a very thorough and complete wipe. You must wipe,cache partition,Dalvik cache,data/factory reset. You must also format boot,system,data,cache. Do you see were your problems might be? Also I have found that it is best to install the theme after you have gotten a couple of reboots under the new ROM's belt to keep from getting forceclosures. EDIT: Once installed properly you should only have to wipe cache partition,and Dalvik cache when flashing an update with the gapps. Then wait for a couple of reboots before flashing the theme. I hope this has helped
 
I formatted my sd card and think i figured it out. I dont think that my sd card was mounting properly so i mounted via the recovery menu and went to the USB MS under recovery and Viola it worked!

edit: Mass Storage doesnt work when its booted up normally but that doesnt bother me as long as it works somewhere

edit 2:downloaded clockworkmod recovery, formatted sd card and did format of phone and install of rom and it works perfectly. who knows what it was but I probably missed a step originally when I flashed and it just carried on until today.
Glade you got it working. When you plug your phone in to a PC if you open the pulldown and select the box that says USB connected:select to copy files to/from your computer. A USB mass storage window will appear with the selection for said function. Hope this has ben helpful. EDIT: Xionia just isn't getting a complete and thorough wipe done before installing these new CM7-IHO ROM's,Installing the CWM 3.2.0.1 was the best thing to do and probably made the difference
 
What have I done wrong??? Installed this ROM, liked quite a bit about it but continually got "ADW.Launcher is not responding" error message which caused the phone to reboot. So I went to my ClockworkMod Recovery v3.2.0.1 to restore my previous back-up but get a "MD5 mismatch!" message. I've never encountered this problem before now. I have restored backed up images before without this error message but now I get it regardless of which restore point I try. Are all restores corrupted? Can anyone help me to recover any or all of them? Is the ClockworkMod Recovery v3.2.0.1 of been using the culprit? I can easily flash a ROM again but I would hate to lose the 5 restores I have because I like each for different reasons. Please help and I thank all for any assistance.

See here for MD5 error fix:

Clockwork-mod Recovery MD5 mismatch! error FIX - xda-developers

Did you by chance name the backup with special characters or spaces in the name? Maybe removing those should be the easy fix.

EDIT: Try the quick & easy fix first:

adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
 
Hey all. I am having the same problems as Dman861 with losing wifi every 5 minutes or so and then reconnecting. Dman861, did you happen to resolve the issue?
On my phone, I had originally rooted with Asadullah's instructions months ago using fastboot and bootloader. Then i flashed ASOP CMod7 2.3.4. Sometime after that my fastboot seems to have been corrupted, because when I select Reboot, and then on the submenu select Bootloader, I get the following error:
Fasboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()

I can pull my battery and get the phone to boot normally though after this.

I decided to try yogi-4's excellent instructions: http://androidforums.com/optimus-v-...-custom-kernel-rom-change-boot-animation.html, and that worked great getting Xionia CWMA v1.2518.4 recovery on there. Following his instructions, I got BACKside ROM (CM7) on there. After reading the potential solution, it looks like clockwork recovery is the way to go.
Given my issue with 2 recoveries on my phone, 1 working, 1 not, how would you recommend I proceed? Thanks!
 
Hey all. I am having the same problems as Dman861 with losing wifi every 5 minutes or so and then reconnecting. Dman861, did you happen to resolve the issue?
On my phone, I had originally rooted with Asadullah's instructions months ago using fastboot and bootloader. Then i flashed ASOP CMod7 2.3.4. Sometime after that my fastboot seems to have been corrupted, because when I select Reboot, and then on the submenu select Bootloader, I get the following error:
Fasboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()

I can pull my battery and get the phone to boot normally though after this.

I decided to try yogi-4's excellent instructions: http://androidforums.com/optimus-v-...-custom-kernel-rom-change-boot-animation.html, and that worked great getting Xionia CWMA v1.2518.4 recovery on there. Following his instructions, I got BACKside ROM (CM7) on there. After reading the potential solution, it looks like clockwork recovery is the way to go.
Given my issue with 2 recoveries on my phone, 1 working, 1 not, how would you recommend I proceed? Thanks!

Thanks. I'm glad it worked for you. As for your WiFi issue. I'm not sure. I'm not having having an issue with that, so I don't know how you should proceed. But I did want to say thanks for saying my 'How To' was excellent!! :D
 
I'm still having problems with my wifi, but then again I haven't had time to flash the Clockwork Recovery yet. Got to wait for a day off to do that. On my laptop, I did try logging into my router and modifying a few settings to no avail. I noticed that the last digit of my androids IP address was constantly changing as it tried reconnecting, even though I only have 3 other computers connected. Maybe that is just normal router operation though, I don't know a lot about it.
 
That sounds like a dchp issue, your phone is constantly being reassigned a new IP by the router. Try either setting your router's lease period to a very high amount, or changing to static IP addresses.
 
To clarify, for me it isn't a dchp issue, as my android mac address is assigned a permanent LAN IP. Also, didn't have this issue prior to the BACKside ROM (CM7). Guessing the xionia recovery doesn't wipe clearly. Curious if any thoughts as to the two recovery options i already have: Bootloader (fastboot) and Recovery (xionia) and adding clockwork recovery? How would I do that, and can I remove Bootloader?
Thanks!
 
You can try flashing the CWM recovery from here, it's an earlier version, but used by Blarf without problems. I have a later 3.2.0.1 CWM recovery flashed through ROM Manager and don't have any problems either.

[Tool] Flashable Zip Recoveries - xda-developers

This will replace your xionia recovery. Bootloader is something you want to keep.
 
Hey all. I am having the same problems as Dman861 with losing wifi every 5 minutes or so and then reconnecting. Dman861, did you happen to resolve the issue?
On my phone, I had originally rooted with Asadullah's instructions months ago using fastboot and bootloader. Then i flashed ASOP CMod7 2.3.4. Sometime after that my fastboot seems to have been corrupted, because when I select Reboot, and then on the submenu select Bootloader, I get the following error:
Fasboot mode started
gpio_i2c: invalid khz: 0
bl: i2c write error
udc_start()

I can pull my battery and get the phone to boot normally though after this.

I decided to try yogi-4's excellent instructions: http://androidforums.com/optimus-v-...-custom-kernel-rom-change-boot-animation.html, and that worked great getting Xionia CWMA v1.2518.4 recovery on there. Following his instructions, I got BACKside ROM (CM7) on there. After reading the potential solution, it looks like clockwork recovery is the way to go.
Given my issue with 2 recoveries on my phone, 1 working, 1 not, how would you recommend I proceed? Thanks!
As long as you have a recovery you should be able to get yourself out almost every problem. For the remaining you need to be ROOTed so you can give commands with a PC or emulator on phone. Download ROOT Checker from the market and see what it says, or if you have a terminal emulator all ready downloaded type in su. If you get a # your rooted. If you get anything else, including $ your not. If you have a file manager look in /system/bin and /system/xbin and make sure you have su installed. If you do look at the permission and see what it says. rwsr-sr-x is good. Anything less like r-sr-srx or r-xr-sr-x or r-xr-xr-x not good. Also make sure Busybox is installed properly(use root checker). Let me know what you come up with. Also you want to make sure you get ClockWorkMod v2.3.0.1 for a good wipe on any updates of the BACKside ROM(this way you don't have to wipe every thing 3 times); version 2.3.0 will not work. You can find it in ROM Manager in the market. WARRNING: Do not attempt to flash a ROM from ROM manager. Just flash the recovery. You can delete old backups that you have made and run the fix permissions options as well. EDIT: xionia recovery has a fix recovery loop option that might come in handy some day,so leave that on your SD card. Also if you ever go back to a Froyo ROM it seems to work better than CWM 3.2.0.1. Just remember Froyo=xionia ,Gingerbread=CWMod 3.2.0.1
 
Thanks Whyzor and AndyOpie150. AndyOpie150, downloaded ROOT Checker. Here are the advanced results for both root check and Busybox:
Congratulations! You have root access!
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
Standard su binary location: ls: /system/bin/su: No such file or directory
Standard su binary location: -rwsr-sr-x 1 root root 26332 Aug 1 2008 /system/xbin/su
Alternate su binary location: ls: /sbin/su: Permission denied
Root user id: Root not properly returning its user id
Root group id: Root not properly returning its group id

Installed Busybox Version:
v1.16.2androidfull
Busybox supports the following applets:
[, [[, arp, ash, awk, basename, bbconfig, brctl, bunzip2, bzcat, bzip2, cal, cat, catv, chgrp, chmod, chown, chroot, cksum, clear, cmp, cp, cpio, cut, date, dc, dd, depmod, devmem, df, diff, dirname, dmesg, dnsd, dos2unix, du, echo, ed, egrep, env, expr, false, fdisk, fgrep, find, fold, free, freeramdisk, fuser, getopt, grep, gunzip, gzip, head, hexdump, id, ifconfig, insmod, install, ip, kill, killall, killall5, length, less, ln, losetup, ls, lsmod, lspci, lsusb, lzop, lzopcat, md5sum, mkdir, mke2fs, mkfifo, mkfs.ext2, mknod, mkswap, mktemp, modprobe, more, mount, mountpoint, mv, nc, netstat, nice, nohup, nslookup, ntpd, od, patch, pgrep, pidof, ping, pkill, printenv, printf, ps, pwd, rdev, readlink, realpath, renice, reset, rm, rmdir, rmmod, route, run-parts, sed, seq, setsid, sh, sha1sum, sha256sum, sha512sum, sleep, sort, split, stat, strings, stty, swapoff, swapon, sync, sysctl, tac, tail, tar, tee, telnet, test, tftp, time, top, touch, tr, traceroute, true, tty, tune2fs, umount, uname, uniq, unix2dos, unlzop, unzip, uptime, usleep, uudecode, uuencode, vi, watch, wc, wget, which, whoami, xargs, yes, zcat

Gonna go look for CWM 3.2.0.1 and attempt to flash using xionia. If it works, will reflash the BACKside ROM again.

Again, appreciate everyone's help, will post results shortly. Andy, if you see something alarming on the results, let me know.
 
Thanks Whyzor and AndyOpie150. AndyOpie150, downloaded ROOT Checker. Here are the advanced results for both root check and Busybox:
Congratulations! You have root access!
Superuser.apk - com.noshufou.android.su - version 2.3.6.3 is installed!
Standard su binary location: ls: /system/bin/su: No such file or directory
Standard su binary location: -rwsr-sr-x 1 root root 26332 Aug 1 2008 /system/xbin/su
Alternate su binary location: ls: /sbin/su: Permission denied
Root user id: Root not properly returning its user id
Root group id: Root not properly returning its group id

Installed Busybox Version:
v1.16.2androidfull
Busybox supports the following applets:
[, [[, arp, ash, awk, basename, bbconfig, brctl, bunzip2, bzcat, bzip2, cal, cat, catv, chgrp, chmod, chown, chroot, cksum, clear, cmp, cp, cpio, cut, date, dc, dd, depmod, devmem, df, diff, dirname, dmesg, dnsd, dos2unix, du, echo, ed, egrep, env, expr, false, fdisk, fgrep, find, fold, free, freeramdisk, fuser, getopt, grep, gunzip, gzip, head, hexdump, id, ifconfig, insmod, install, ip, kill, killall, killall5, length, less, ln, losetup, ls, lsmod, lspci, lsusb, lzop, lzopcat, md5sum, mkdir, mke2fs, mkfifo, mkfs.ext2, mknod, mkswap, mktemp, modprobe, more, mount, mountpoint, mv, nc, netstat, nice, nohup, nslookup, ntpd, od, patch, pgrep, pidof, ping, pkill, printenv, printf, ps, pwd, rdev, readlink, realpath, renice, reset, rm, rmdir, rmmod, route, run-parts, sed, seq, setsid, sh, sha1sum, sha256sum, sha512sum, sleep, sort, split, stat, strings, stty, swapoff, swapon, sync, sysctl, tac, tail, tar, tee, telnet, test, tftp, time, top, touch, tr, traceroute, true, tty, tune2fs, umount, uname, uniq, unix2dos, unlzop, unzip, uptime, usleep, uudecode, uuencode, vi, watch, wc, wget, which, whoami, xargs, yes, zcat

Gonna go look for CWM 3.2.0.1 and attempt to flash using xionia. If it works, will reflash the BACKside ROM again.

Again, appreciate everyone's help, will post results shortly. Andy, if you see something alarming on the results, let me know.
I ran Root Checker on my phone because your root user and root group id's don't look right. On my phone this is what I got-The Root user id:uid=0(root), The Root group id: gid=0(root), I might not do anything until JerryScript or someone as knowledgeable can have a look at it(I'm not just a member,I'm a "Nuub"). I might be just doing the worry wart thing again,but I really don't know(I got alarms going off in my head for some reason-Figuratively speaking of course).I guess you should be all right to flash CWM 3.2.0.1 and a ROM. But you might have that Root thing looked into in case you ever get yourself into a jamb that would require root access and DOS commands.
 
Ok, fyi, I successfully got CWM 3.2.0.1 on my phone! I went back and followed yogi-4's instructions from step 17, wiping everything in the process and reflashed the BACKside ROM. Its running again, did not put the Green Machine Theme on this time.
But like earlier, as Dman861 experienced as well, I am still having the issue of my wifi dropping intermittently, just to reconnect moments later. Very disruptive. Definitely didn't have this problem with ASOP CMod7 2.3.4. I really like the BACKside build but am running out of options, particularly liking the bluetooth working and the speakerphone portion finally working, unlike the CMod7 one. Any additional thoughts? Not having any other issues with my wifi devices in my house (or my wife's phone which is also an Optimus V with ASOP CMod7). So I think I can safely rule out the router (which by the way I do use a static IP for my phone on my LAN). Appreciate everyone's help!
 
Back
Top Bottom