[ROM] [ROM][DROID2] ApeX 2.0.0 Release Candidate (RC3) (8/27/2011)

[mtuchris]

I am a few weeks in on apex over the OTA still going strong. Did a data wipe first. You will have to install the dark market app in the second post(?) to fix the error when purchasing apps. I seem to have pretty good battery life with this.

 

[siriusgamer]

Not being able to boot into clockwork happened to me when I first flashed Apex 1.4. It seems like flashing the rom got rid of clockwork.
What black market fix? Does that only apply to BUYING apps (with money) or downloading them (free and bought) in general?
And if ROM manager works on 2nd-init roms, why doesn't it work on other roms, and why does it work on stock roms?

 

[JSM9872]

I am a few weeks in on apex over the OTA still going strong. Did a data wipe first. You will have to install the dark market app in the second post(?) to fix the error when purchasing apps. I seem to have pretty good battery life with this.

Thank you for verifying that it works on the OTA

Not being able to boot into clockwork happened to me when I first flashed Apex 1.4. It seems like flashing the rom got rid of clockwork.
What black market fix? Does that only apply to BUYING apps (with money) or downloading them (free and bought) in general?
And if ROM manager works on 2nd-init roms, why doesn't it work on other roms, and why does it work on stock roms?

Yes it only applies to purchasing apps, downloading should be fine still. ROM Manager and CWM are very different things. You can use ROM Manager with different ROMs but for full functionality it requires 2nd-init ROMs since they are AOSP and thats what ROM Manager is made to work with. The newest CWM is designed for 2nd-init ROMs as well but may work with others. The only thing is many older files may not be compatible due to needing to use a different type of scripting.

 

[siriusgamer]

Yes it only applies to purchasing apps, downloading should be fine still. ROM Manager and CWM are very different things. You can use ROM Manager with different ROMs but for full functionality it requires 2nd-init ROMs since they are AOSP and thats what ROM Manager is made to work with. The newest CWM is designed for 2nd-init ROMs as well but may work with others. The only thing is many older files may not be compatible due to needing to use a different type of scripting.

I see. But I still don't understand why ROM Manager works on regular blur, but not blur based roms.

Does the market fix, fix buying movies on a rooted devices?

 

[nailbomb3]

Nailbomb posted in this thread that it worked, read at the top of the page your post is on and one page back for more info. I can not confirm due to not being on a D2. And you should use 2.5.0.8, the newer versions of CWM are really for 2nd-init ROMs.

I believe I used koushs d2 bootstrap to flash it yes. I've flashed so much stguff this last three weeks its hard to keep it all straight.

No grandmas thou.... lol....

Sent from my DROID2 using Tapatalk

 

[JSM9872]

I see. But I still don't understand why ROM Manager works on regular blur, but not blur based roms.

Does the market fix, fix buying movies on a rooted devices?

It should work with anything that you need to purchase. But I never experienced the bug in the first place so I never needed the fix either way. What do you mean regular blur vs blur based? I am not sure what exactly the difference is you are referring to.

And what ROM Manager functionality are you concerned with? As I said it does work just the functions that require recovery (installs, backup, etc) you need bootstrap for just like you always have on the d2. Unless you are on CM or other 2nd-init ROMs which since they are AOSP it works with normally.

Sent From a Tear in the Space/Time Continuum...

 

[siriusgamer]

I mean I've had ROM manager work on the stock rom, but not on apex, which is based off the stock rom. And on apex, when I tried to use ROM manager, it said I didn't have clockwork, even though I did.

And I've read that google blocks rooted devices from renting movies, does the market fix circumvent that?

 

[mtuchris]

I've only been using d2 bootstrap and i had to reinstall and reboot once after flashing apex to get it to work. Since then I haven't had any problems. I don't know if movies work with the market fix?

 

[siriusgamer]

Last question, if I wanted to return back to the OTA GB, would I have to flash the OTA over apex, or would I have to SBF and update that way?
Alternatively, could I just restore from a nandroid?

 

[mtuchris]

I have flashed a nandroid backup back to the ota and it worked fine. I havent tried flashing just the ota over apex but i don't think it would be a problem. There shouldn't be a need to sbf unless something goes wrong. Just remember to wipe data/factory reset from bootstrap recovery before flashing. I have made that mistake twice and had to sbf both times to get out of my bootloop.

 

[siriusgamer]

Small question, does 2.0 RC3 have a toolbox, like 1.4?

 

[vtnerd]

Small question, does 2.0 RC3 have a toolbox, like 1.4?

Not yet, but I think the plan is to release one with the final version.

I copied the hosts file from 1.4 to at least block ads in the meantime and that worked fine.

 

[JSM9872]

I just used jrummy's ROM Toolbox, it worked very well for me.

 

[siriusgamer]

So I can change the bootloader logo and boot animation with the ROM toolbox? I know that I can just copy the current bootanimation.zip i have to the SD card and move it back when I flash to apex, but I'm not sure how to get the red motorola logo back.

EDIT: Since bootloader logos can be changed by flashing a logo.bin, could I just remove the logo.bin inside the apex zip?

 

[DroidBurgundy]

I just used jrummy's ROM Toolbox, it worked very well for me.

WTF.. I cant seem to disable adds @ all on this version of Apex, can someone toss me a bone?