[ROM] ApeX 1.3.1 for Droid X - Running, running, as fast as it can (12/16/10)

[demoninsidemeh]

hi guy. new to this so might sound dumb. after i flash to apex do i need to keep the zip on my card or can i delete it? and whats up with the clock? i like the one in the screen caps but when i flashed i didnt get that. much thanks :greendroid::greendroid:

 

[ScottyDsntKnow]

You know, I had a M5 sum error last time I tried to restore Apex from a Nandroid and I had to just wipe/re-install a fresh copy since I didn't have a recent copy of anything else saved...

Didn't think anything of it and it only took like 20 minutes to restore everything. I really don't care either way since I've resolved to stick with Apex from here on out and hopefully everything Fab comes out with can just be installed over the previous version without a wipe. Well, obviously when there is an OTA or leak we'll probably need to wipe but that is par the course.

 

[ScottyDsntKnow]

hi guy. new to this so might sound dumb. after i flash to apex do i need to keep the zip on my card or can i delete it? and whats up with the clock? i like the one in the screen caps but when i flashed i didnt get that. much thanks :greendroid::greendroid:

I keep the latest full zip of whatever I am running on the SD card just to be safe. That big clock in the screen caps is not part of the rom, that is beautiful widgets available in the market for about $4-5 USD IIRC.

 

[r3dlined]

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

 

[Fabolous]

First I'll apologize because I tried another rom :-(.

Second I'll say that I almost immediately switched back to apex.

Right before installing the new rom, I did a nandroid backup of my apex 1.3.1, then I wiped data and cache and installed the "other" rom.

Didn't like the rom "security lock is busted", so I returned to recovery, wiped data and cache, then restored my nandroid of apex.

When everything finished, I booted up and just after the android logo I got an error that system had stopped responding followed by just a black screen. When I held the power button, I could reboot which took me to recovery.

There I tried wiping data, cache, dalvik cache, and battery stats for good measure. Restart and had the same thing happen (system not responding). I then went as far as to format system then restore the nandroid. Same result.

Only way to get out of it was to run the install.zip of Apex. Everything's fine, just odd.

I actually had the same thing happen before somewhere while I was restoring 1.3.0 for some reason (can't remember why). I never had this problem before, and it's really just an inconvenience if I want to jump back and forth.

Does anyone know of a fix? Did Fab put this in on purpose to dissuade us from swapping roms?

I didn't do it on purpose, but this little issue does manifest itself when restoring nandroids, or even sometimes when installing themes.

It's caused by my startup script, which usually waits about 42s before it runs, but if there's something causing the boot up process to take longer than usual (i.e. being restored/installing a theme, etc.), the script may run too early and cause the system to become unresponsive.

The quick fix for now is to hit wait, hold down the power button until the menu comes up, and hit reboot.

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

Might want to SBF it, because even if you restore a "stock" nandroid, it'll still be rooted.

 

[r3dlined]

First I'll apologize because I tried another rom :-(.

Second I'll say that I almost immediately switched back to apex.

Right before installing the new rom, I did a nandroid backup of my apex 1.3.1, then I wiped data and cache and installed the "other" rom.

Didn't like the rom "security lock is busted", so I returned to recovery, wiped data and cache, then restored my nandroid of apex.

When everything finished, I booted up and just after the android logo I got an error that system had stopped responding followed by just a black screen. When I held the power button, I could reboot which took me to recovery.

There I tried wiping data, cache, dalvik cache, and battery stats for good measure. Restart and had the same thing happen (system not responding). I then went as far as to format system then restore the nandroid. Same result.

Only way to get out of it was to run the install.zip of Apex. Everything's fine, just odd.

I actually had the same thing happen before somewhere while I was restoring 1.3.0 for some reason (can't remember why). I never had this problem before, and it's really just an inconvenience if I want to jump back and forth.

Does anyone know of a fix? Did Fab put this in on purpose to dissuade us from swapping roms?

I didn't do it on purpose, but this little issue does manifest itself when restoring nandroids, or even sometimes when installing themes.

It's caused by my startup script, which usually waits about 42s before it runs, but if there's something causing the boot up process to take longer than usual (i.e. being restored/installing a theme, etc.), the script may run too early and cause the system to become unresponsive.

The quick fix for now is to hit wait, hold down the power button until the menu comes up, and hit reboot.

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

Might want to SBF it, because even if you restore a "stock" nandroid, it'll still be rooted.

Is there an SBF for the most current 2.2.1 OTA?

 

[r3dlined]

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

Might want to SBF it, because even if you restore a "stock" nandroid, it'll still be rooted.[/QUOTE]

Is there an SBF for the most current 2.2.1 OTA?[/QUOTE]

I guess I could just unroot with Z4 and then do a factory reset.

 

[peacemaker]

Fab, I do like your work very much. You make great looking ROMs. Unfortunately for me, it just hasn't worked out. When I ran RC1, it was great at first, but eventually lead to random reboots quite often--went back to stock. Was enjoying stock for quite some time, then after 1.3 came out, I was itching to get back to it. Upgraded to the new version, was great for the first week, and now I'm experience sluggish response times on wake, random hangs, the camera/camcorder doesnt work everytime (screen will go black--but is lit). It is no longer "fast." I have loaded some apps, yes, but nothing crazy--just a few games.

I know this is always a work in progress, just wanted to write my notes.

 

[brewcrewwheels]

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

Might want to SBF it, because even if you restore a "stock" nandroid, it'll still be rooted.[/quote]

Is there an SBF for the most current 2.2.1 OTA?[/quote]


not a full sbf, but there is a 2.3.340 system only sbf, which should work for you.

 

[r3dlined]

LOVING THIS ROM!!!!!! I have a replacement X coming today. On my current X that is running Apex, can I just restore the original system backup through bootstrapper to put it back to what Verizon is expecting it to be? I have never tried to do that before, I always SFBed before.

Might want to SBF it, because even if you restore a "stock" nandroid, it'll still be rooted.

Is there an SBF for the most current 2.2.1 OTA?[/quote]


not a full sbf, but there is a 2.3.340 system only sbf, which should work for you.[/QUOTE]

I'm pretty sure I got the X to where it needs to be. I restored backup from before Apex was loaded, removed root with Z4, and then did a factory reset. Seems like its back to stock.

Think I missed something?

 

[brewcrewwheels]

you should be ok. if it were me, once i got the replacement up and running, i would sbf the one going back just to be sure. but that's just me.

 

[cubsfan187]

ok got another total noob question for you all. I am running the stock rom on the .340 update. I really like all I am reading about this rom but kinda reluctant to do the data/cache wipe. I also read somewhere that you should do a factory reset before installing. That is out of the question for me. Too many apps to lose if that is the case. Can someone tell me if this is really needed to install this rom whether thru rom manager or dl it to the sd.

Thanks in advance!

 

[r3dlined]

ok got another total noob question for you all. I am running the stock rom on the .340 update. I really like all I am reading about this rom but kinda reluctant to do the data/cache wipe. I also read somewhere that you should do a factory reset before installing. That is out of the question for me. Too many apps to lose if that is the case. Can someone tell me if this is really needed to install this rom whether thru rom manager or dl it to the sd.

Thanks in advance!

I am also fairly new, but this ROM ran fantastically awesome without doing a factory reset, just format data/cache. No apps were lost for me just had to log back into them.

 

[brewcrewwheels]

ok got another total noob question for you all. I am running the stock rom on the .340 update. I really like all I am reading about this rom but kinda reluctant to do the data/cache wipe. I also read somewhere that you should do a factory reset before installing. That is out of the question for me. Too many apps to lose if that is the case. Can someone tell me if this is really needed to install this rom whether thru rom manager or dl it to the sd.

Thanks in advance!

another thing to consider if you want to start flashing roms is to invest in a backup utility. i personally use my backup pro. some people prefer titanium backup. it's invaluable, especially when you start switching as going from one developer's rom to another will sometimes require you to wipe all your info.

 

[r3dlined]

ok got another total noob question for you all. I am running the stock rom on the .340 update. I really like all I am reading about this rom but kinda reluctant to do the data/cache wipe. I also read somewhere that you should do a factory reset before installing. That is out of the question for me. Too many apps to lose if that is the case. Can someone tell me if this is really needed to install this rom whether thru rom manager or dl it to the sd.

Thanks in advance!

another thing to consider if you want to start flashing roms is to invest in a backup utility. i personally use my backup pro. some people prefer titanium backup. it's invaluable, especially when you start switching as going from one developer's rom to another will sometimes require you to wipe all your info.

Do most people here feel the bootstrapper backup isn't sufficient?