I'm not sure how I did it but I now have an AOSP ROM installed and do not have the "custom" boot status screen anymore.
These are the steps that I took.
---------------------------------
Note that I have installed dozens of AOSP ROM's and my boot status always showed up as "Custom".
Now, it doesn't.
This is the ODIN tar I used to go back to stock originally:
I337UCUAMDB_I337ATTAMDB_ATT
Note however that this was not the first time I've gone back to stock using this file.
What was different this time though, was that ODIN was giving me errors about mismatching MD5 sum. So knowing that the file itself was good, I just removed the ".md5" from the filename and proceeded to Odin to stock.
These are the steps that I took.
---------------------------------
Note that I have installed dozens of AOSP ROM's and my boot status always showed up as "Custom".
Now, it doesn't.
- nuked AOSP rom (something went really wrong).
- wiped everything in TWRP 2.5.0.2.
- Odin stock.
- Rebooted several times.
- Rooted w/motochopper.
- Rebooted.
- deleted busy box.
- rebooted.
- installed GooManager and TWRP.
- Rebooted to recovery.
- rebooted normally (without installing root).
- rebooted to recovery.
- wiped everything including internal SD card.
- rebooted to recovery (without installing root)
- factory reset wipe again.
- installed PAC ROM (aosp).
- Rebooted a couple times and still don't have a "Custom" boot screen. I haven't had the custom boot status at all since my second reboot after ODIN to stock.
This is the ODIN tar I used to go back to stock originally:
I337UCUAMDB_I337ATTAMDB_ATT
Note however that this was not the first time I've gone back to stock using this file.
What was different this time though, was that ODIN was giving me errors about mismatching MD5 sum. So knowing that the file itself was good, I just removed the ".md5" from the filename and proceeded to Odin to stock.