First of all, the Rezound is ONLY unlocked, NOT S-off. I know a lot of people that came to this device, came from another HTC that was more than likely S-off with an engineering hboot. This is like a free pass to do whatever you want with little fear of your device exploding. Basically, as long as you didn't overwrite your Hboot, you couldn't screw it up.
Unfortunately, unlocked does not include this free pass. However, devs and users alike seem to be forgetting this and flashing everything anybody with a pulse posts up with little regard to the consequences. To this, I say Devs: Shame on you for posting it, and Users: Shame on you for following blindly. So, here's my .02 on the situation.
Developers: You have a responsibility to the users. They rely on you to deliver a product that isn't going to mess up their phone in some way shape or form. A disclaimer stating that you aren't responsible for damage isn't a catch-all "Sorry you aren't as smart as me, go post in the general forum". Be mindful of what you're doing and take your time. I know that we all want to be the first to the public with the latest and greatest, but if it ruins the experience for the userbase, did you really accomplish anything? Anyway, here a couple of guidelines I think everyone should follow:
- First and foremost, I think everyone needs to come to a consensus on the Mainver that will be used. Personally, I say use whatever the latest OFFICIAL release is. If Verizon is on 2.01.605.11, then EVERY PH98IMG should be using an android-info.txt that reflects that. Someone should maintain a thread with an attached file that EVERY dev can use in their work.
- And while we're talking about PH98IMG files, I see absolutely no reason that ANYONE should be posting ANY of these that contain anything other than a Kernel or recovery image. If a user wants to update their hboot/radio/whatever they should be relocking their device and taking it OTA, then unlocking and reflashing their desired ROM. There is just too much margin for error when packing/repacking stock images and not worth the risk in my opinion.
- Quit packing kernels in ROMs using fancy scripts and what not. Release a ROM zip, and include a kernel as a seperate download if it contains something that is necessary for the functionality of the ROM. The extra 14 seconds it takes to flash in bootloader isn't the end of the world and it removes an extra chance of "oops, I forgot to update the mainver".
- If you are privy to a leak, please take the time to make it safe. Extract it and release it as a flashable zip with a seperate kernel flash with the correct mainver based on the current baseline. It only takes an hour at most to properly prepare it this way and ensures that there aren't 37 threads about not being able to downgrade a week later.
- Hboot is not clockwork recovery. You shouldn't be flashing anything there that isn't a kernel or recovery image. Period. If you download a PH98IMG.zip and it contains anything besides boot.img or recovery.img, you better be asking why BEFORE you flash it. Also, it's a good idea to make sure android-info.txt contains the correct mainver.
- Know what you are flashing. If someone has a developer tag, there's a good chance they have at least a decent grasp on what they are doing. If someone with 9 posts says he created the greatest ROM of all time, you better be skeptical. Maybe he did, but just be aware of what you are getting into and double and triple check.
- If you do manage to screw it up somewhere, keep your cool. Search the threads first, as you probably aren't the first, nor will you be the last. If it was a ROM/kernel/whatever, post your issue/concern in that thread first and wait patiently for a response. If you don't get one, PM the developer and again, wait patiently. We have lives, and being without your phone isn't the end of the world. If it is, you should look at your priorities.