1. You want that $100.00 in your pocket or an Amazon Fire TV don't you? Well here's the deal. With our new updated look we are in desperate need of an updated logo. The 'old' one has certainly served us well, but it's time. Find all the details here: bit.ly/1q0k6Wa
  2. DroidForums.net is currently undergoing a major software upgrade. If you are experiencing any problems logging in please: Contact Us

major bug

Discussion in 'Apex' started by mouthrulez, Apr 22, 2011.

  1. mouthrulez
    Offline

    mouthrulez New Member

    Joined:
    Apr 22, 2011
    Messages:
    84
    Likes Received:
    0
    Trophy Points:
    0
    I have the newest Apex for the Droid 2 and i love it. but I have found a major bug which causes the system to fail. It does this once you turn you phone off. When you turn the phone on, it loads until you get past the APEX boot logo. Then an error message pops up and say "Sorry! Process system is not responding." In order to fix this you must turn your droid 2 off. after its off, hold the power button and "x". then a droid and a "!" will pop up. hit the magnifing glass on the key board. then scroll down to factory reset. when its done, reboot the phone. this first reboot wont work so take your battery out and restart it. the error message will pop up again, this time hit "wait." hold the power button and then hit reboot. When your phone turns back on, it will bring you to the setup screen, but you will still have APEX as your ROM. Everything on your phone will be wiped clean except for APEX, the programs that came with it, and superuser.
    I will not be changing my ROM back to the stock one however, because i still love this ROM. Just please fix this bug ASAP.
    -THANKS in advance!
  2. Fabolous
    Offline

    Fabolous Superuser Developer

    Joined:
    Dec 10, 2009
    Messages:
    598
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    Illinois
    Hey, if that ever happens again, next time, try holding down the power button, and just hitting restart.

    That's a pretty rare error that I had the solution to posted on the wiki (which, unfortunately, is still down).


    Hope that helps!