[Verizon Droid Incredible 2] kerfex:
Maybe.....

Maybe your phone forgot it was S-off? Did you see this one post just a few back by RegnierD:

"

Also, for anyone that is interested, I pinpointed the root (haha) of my issues the past week-ish: My phone forgot it was S-Off somehow. Everythong was still rooted (because I was flashing rooted roms) and the bootloader functions still worked like S-Off (like fastboot recovery flashing), but roms couldn't actually make those same system level changes that were important. I figured this out when I went to update my SU binary through the SU app in this rom, and it said I wasn't S-Off. I tried several other roms and got the same error.

Now, this happens sometimes when you OC too high and your phone gets hot and locks up, which it did, once, about a week and a half ago (this happened to me multiple times on my OG DInc, which wouldn't OC past 1.08 mhz :P). Unfortunately, the only way to fix this for us (because of how Revolutionary unlocks and then overrides bootloader writing through fastboot/hboot) is to RUU back to Froyo (if anybody even knows what that is anymore, lol) via PG32IMG.zip, then run SuperOneClick to gain root, follow a string of ADB commands to flash the original 0.97.0000_336906 hboot, then RUU back to 2.3.3 via PG32IMG.zip, and then run Revolutionary again to get S-Off. The difficult thing about this, is that all the guides for this have links hosted by MultiUpload, and all the mirrors have gone dark. So, you have to extract that hboot .nb0 file from the Froyo RUU .zip. Sound confusing enough? Lol

The point being, this is why OC-ing is dangerous, and why we (I) need to be careful when doing so. I got lucky, and was able to fix the rather minimal corruption, but I (or some other unfortunate SuperUser carelessly playing with the processor) may not be so lucky next time if something goes wrong again because of playing too much with OC. I learned my lesson, that's for damn sure. XD LOL

Just a PSA, for other people that may run into issues like this down the road."

I had never heard of that one. So check to see if this happened to you.

---------- Post added at 04:45 AM ---------- Previous post was at 04:31 AM ----------

I do not know if Areoevans kernel or the stock kernel have the swap enabled. I do believe you have to enable this when compiling it. Now I used to use Swapper2 on the good ole ERIS and I had the first Partition on my sd card formatted FAT32 and the last 250 meg formatted as the linux swap space.

Now I am pretty sure if you format the card with the last partition being the swap partition (size of swap does not matter, so long as it is last partition on the card) the stock setting in swapper2 works. I think it was /dev/block/mmcblk0p3.

I also had 3 partitions thus the 0p3. p3 being the third partition. So if you just have 2 ( FAT32 and SWAP) then is the second block device and would be /dev/block/mmcblk0p2 . Agian size of swap does not matter so log as it is the last partition on your card.

EDIT: if you have several partitions on your sd card, then the format is the same, i.e say you have 4 partitions on your card, then you would add the SWAP as the the last partition and thus making it 5 physical partitions on the card, so 5 partitions on one block device and that would be: /dev/block/mmcblk0p5 .

EDIT2: the mmc designates what type of block device the kernel will be passing info/talking to and mmc is the sd card. The blk0 is the physical device as addressed to the kernel. i.e so where is it physically addressed in relation to all the block devices the kernel interacts with( memory, radios, ccd camera, etc.) and the p "whatever' designates the partition on the physical device.

I love linux/Unix