[Verizon Galaxy S 5 General] uberpippi:
So, I've been screwing around with ROMs and I might have gotten a little overzealous when I was really too tired to have been messing with it, and I need some help reversing it.

Once upon a time I was rooted on NCG, and I was bored, so I followed the instructions for upgrading to OK3 without losing root. From there, I flashed AllianceRom V10 port. I'm pretty sure I did it through Safestrap, but I can't even remember. Everything was going great, lots of reboots and no issues. I installed all my apps without any problems, and then at some point I got the bright idea to wipe dalvik. So there was an app already installed called Lollipop Safestrap, and I"m not 100% sure what that was, because it appears that Safestrap doesn't support Lollipop, but who knows? I installed it and rebooted into Safestrap, did a full backup and then wiped Dalvik. From there, it would only reboot into Safestrap or into the stock recovery. I still don't understand why. I read that Safestrap sometimes had issues rebooting from the stock rom and I tried every combination of battery pull and rebooting that I could.

This is where things went badly. It was late and I was tired and I just wanted my phone back. I thought that I read somewhere in one of the threads that if you're seeing Safestrap when you reboot, it's because you didn't flash the right kernel. I know that that wasn't the right answer, because up until then it had been rebooting fine, and I also am pretty sure that I should have just loaded the backup that I had just made onto the stock rom slot, although I had read that there's lots of issues with that. So.... I had "G900V_OK3_Stock_KERNEL_SafeStrap-Flashable.zip" on my SD card, and I thought, screw it, I'm in Safestrap, so it must be a good idea to flash that! I did, rebooted, and made it past the recovery screen, but then all that happened was the AllianceROM logo sat forever and ever. It was spinning, and I let it go for up to a half hour before I battery pulled. That's all it will do now, other than being able to boot into download mode or stock recovery.

THEN, I thought... well I'm not really sure what I thought, but what I did was ODIN G900V_OD5_Bootloader.tar.md5. I'm not really sure why I thought that would help. But no real changes, so I guess it didn't hurt.

The stock recover is OK3, and in the recovery.log that's in the backup folder, it says:

ro.boot.bootloader=G900VVRU1BOD5

ro.bootloader=G900VVRU1BOD5

ro.build.display.id=AllianceROM_VZW_V10_G900V_XXU1BOH4

ro.build.version.incremental=G900FXXU1BOH4

ro.build.description=kltexx-user 5.0 LRX21T G900FXXU1BOH4 release-keys

ro.build.fingerprint=samsung/kltexx/klte:5.0/LRX21T/G900FXXU1BOH4:user/release-keys

ro.build.PDA=G900FXXU1BOH4

ro.build.hidden_ver=G900FXXU1BOH4

I copied lastlog to the SD card that this is what it says now:

[ro.boot.bootloader]: [G900VVRU1BOD5]

[ro.bootloader]: [G900VVRU1BOD5]

[gsm.version.baseband]: [G900VVRU2BOK3]

[ril.official_cscver]: [G900VVZW2BOK3]

[ril.sw_ver]: [G900VVRU2BOK3]

[ro.build.PDA]: [G900VVRU2BOK3]

[ro.build.description]: [kltevzw-user 5.0 LRX21T G900VVRU2BOK3 release-keys]

[ro.build.display.id]: [LRX21T.G900VVRU2BOK3]

[ro.build.fingerprint]: [Verizon/kltevzw/kltevzw:5.0/LRX21T/G900VVRU2BOK3:user/release-keys]

[ro.build.hidden_ver]: [G900VVRU2BOK3]

[ro.build.version.incremental]: [G900VVRU2BOK3]

So I think that maybe I just need to somehow flash something to do with OH4 on there, since thats what was in the original recovery? But I decided that before I continue to just flash random things like it's spring break, I should stop for a second and consult with you folks and make sure that I'm on the right track. Help?