• 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

I got to say jerry, your auto install is fantastic!! Thank you so much for giving updates, and supporting our little phone. On stock it seems so slow and outdated compared to whats out there now. But thanks to your rom, it never feels that way! Thanks so much for your continued development. Whatever your phone is in the future that you develop for will defiantly be the one I get. Without question.

By the way, to anyone with link 2 sd:

I got link 2 sd to work again just fine. After first boot it gave me the mount script error again. I Just recreated mount scripts, restarted about 4 times, and then linked dvack cache, rebooted again. Cleared up 2nd partition and dvack cache as well as clear all app cache. Works like a charm. So easy.
REMEMBER TO RESTART LIKE CRAZY AFTER INSTALLING A NEW ROM UPDATE. AFTER A COUPLE OF RESTARTS THE ROM SHOULD BE ALL GOOD TO GO.

@ philetus

I believe the easiest way is to just open backside updater. It will tell you if it installed correctly by saying an update is not available. (meaning you have the latest version.)
 
G19 said:
Not sure if it's supposed to work correctly yet, but just thought I'd mention it.

Seems like my auto-install function doesn't work. The phone boots into recovery, wipes cache, doesn't wipe dalvik, then the phone reboots without installing anything. Using 5-2 CWM green recovery and updating from 4-17 to 5-2 ROM.
Click to expand...

nitestalkr said:
same thing happened with me, so i just did a manual install, vol+ is the up key, vol- is the down key, and Home is the 'ok' key, and back is, well.. the back key.
Click to expand...

Same for me, and also ended up doing a manual install. (Waited till I was awake for that one hehe.)
 
Worked fine for me. Only thing was that my sd card apps didn't load up over a long time on the first boot so I just rebooted and they came up eventually.
 
For those who had auto-install failures, I'm sorry I didn't post clearer update instructions. The issue is with using the newer CWM-Green before upgrading the ROM and therefor the BacksideUpdater.

The previous versions, BacksideUpdaterV3.2 and CWM-G-417 used multiple command lines, and executed each one after a recovery reboot. I found this to be very inefficient during testing the newer features. Imagine rebooting each time a step is performed, wipe cache, format boot, format system, format data, install package, finally reboot system, that's 6 reboots for a single install.

The newer versions, BacksideUpdaterV3.3 and CWM-G502 use a single command line, and subroutines in the recovery to carry out the selected options. This allows everything to be accomplished with one reboot to recovery, and when finished a reboot to system.

So if you upgraded to the new CWM-Green-recovery-05022012 before you upgraded to BACKside-IHO-VM670-05022012, the older BacksideUpdaterV3.2 wrote multiple command lines (wipe-cache, then update-package). But the new CWM-G-502 only reads a single command line, hence the failed auto-install with this upgrade path. ;)

I don't plan on releasing many updates to CWM-Green, so this shouldn't be an issue in the future, but I'll be sure to be more explicit about the upgrade process next time.
 
For those with MediaFire issues, I would imagine my account was hit pretty hard this morning. About 12 hours after releasing the new build, there were already over 700 downloads. At 67mb per, that's a lot of bandwidth for a single account, and I'm sure they have some sort of throttling software to prevent abuse of their service.

Patience grasshopper, the owners of shiny things end up with trash cans full of broken pieces. ;)
 
JerryScript said:
For those who had auto-install failures, I'm sorry I didn't post clearer update instructions. The issue is with using the newer CWM-Green before upgrading the ROM and therefor the BacksideUpdater.

The previous versions, BacksideUpdaterV3.2 and CWM-G-417 used multiple command lines, and executed each one after a recovery reboot. I found this to be very inefficient during testing the newer features. Imagine rebooting each time a step is performed, wipe cache, format boot, format system, format data, install package, finally reboot system, that's 6 reboots for a single install.

The newer versions, BacksideUpdaterV3.3 and CWM-G502 use a single command line, and subroutines in the recovery to carry out the selected options. This allows everything to be accomplished with one reboot to recovery, and when finished a reboot to system.

So if you upgraded to the new CWM-Green-recovery-05022012 before you upgraded to BACKside-IHO-VM670-05022012, the older BacksideUpdaterV3.2 wrote multiple command lines (wipe-cache, then update-package). But the new CWM-G-502 only reads a single command line, hence the failed auto-install with this upgrade path. ;)

I don't plan on releasing many updates to CWM-Green, so this shouldn't be an issue in the future, but I'll be sure to be more explicit about the upgrade process next time.
Click to expand...

guess I was one of the lucky ones my update went flawless :thumbup:

PS I've been sick with pneumonia and lol guess it is making me dream some weird stuff I dreamed you also released a flawless port of lcs also lol
 
AndyOpie150 said:
Hey brotherswing. Could you put the BobZohme kernel in the All Things Root Guide. I have been to busy in my personal life the last few days and need to catch up with all my Guide duties. Thanks my green brother.
Click to expand...

I'll get that fixed shortly!





philetus said:
First time I used the auto install. Seemed really fast.
How can I verify it installed the updated rom?
Click to expand...
I think auto-install isn't working right now, I flashed the update manually.
 
can someone please tell me how to disable boot animation? I found it last time but can't anymore..

also is anyone having weird issues with opera mini? text won't show up when I load a web page.
 
Hey Jerry, whenever I uncheck " Show 3G icon " the whole status bar force closes. I believe Systemui? I never could find a reason..... Any ideas?
 
When I reboot, I get " Force Close " I click it, then the status bar goes away.

After that, I have to go to settings, check 3g Signal Icon, then reboot, to get it back.
 
A curiosity: when I plug speakers into my phone, it almost invariably gives me a FC on DSPManager. Not a big problem, and my just be my phone. Anyone else run into this? It has happened on the last couple of versions of BACKside.
 
129260 said:
By the way, to anyone with link 2 sd:

I got link 2 sd to work again just fine. After first boot it gave me the mount script error again. I Just relinked, restarted about 4 times, and then linked dvack cache, rebooted again. Cleared up 2nd partition and dvack cache as well as clear all app cache. Works like a charm. So easy.
Click to expand...

What did you relink?
 
cdunkle584 said:
A curiosity: when I plug speakers into my phone, it almost invariably gives me a FC on DSPManager. Not a big problem, and my just be my phone. Anyone else run into this? It has happened on the last couple of versions of BACKside.
Click to expand...

I've never had that problem. It should be the same as a headset. I plug my phone into my car everyday to play music and it's rock solid.
 
You must log in or register to reply here.
Back
Top Bottom