@EarlyMon I'm talking about novices because I am one. You said, "I once performance-tuned an HTC kernel and rom just to prove a point." I don't even know how to build a kernel yet. I still have a lot to learn. My first phone was a Samsung Galaxy Prevail and I learned a lot from the devs on this site but HTCs are so different I have a lot more to learn, even though some things are very easy for me.
"
@scotty85 explained the real reason elsewhere, naturally, I don't remember the details, but fastboot booting a recovery from your pc is a no go on the latest HTCs. Including mine.""
I don't know where a thread is that says this but I think the kernel with write protect removed will work because I tried to install su through TWRP and it rebooted and did not install. I used a write protect removed kernel and it went off without a hitch. I used the tutorial located here:
http://forum.xda-developers.com/desire-510/general/guide-how-to-unlock-install-recovery-t2988292. I have done this a least a couple of times and it works perfect every time. I have never had a problem with fastboot. One thing I would add is to always wipe Dalvik-cache and cache before rebooting. I have had some bootloops and this has always solved the problem. It loops at the HTC logo screen, I either hold Down + Power button or take out the battery. I'm sorry I don't have links explaining why any of this works. I tried it myself though and this is the solution. We can probably just keep communicating and eventually find out the reason why.
"Anyway, that's the last that I intend to argue about the land of milk and honey. "
"XDA mods wouldn't stand for driving traffic away from their site."
I am not trying to argue with you or be disrespectful to the site. I'm sorry if I came off like that. I am simply trying to learn. I appreciate this site and others because it gives me a place to learn about things that I thoroughly enjoy. I am an extreme introvert and coming to sites like these allows me to socialize with others that share my interests. I will stop trying to drive traffic away and I will simply give an answer to a user's question in the future.
@knoober as you said there are no hard bricks. That is a good thing. I'm sure a person would have to mess up very bad to hard brick these phones.
"I figured on trying the TWRP method (which has never worked for me on any other device) but I havent flashed the recovery yet, only booted to it using <fastboot boot recovery.img> because I wanted backups before messing with stuff.... and when I tried to take backups I ran into the internal storage/sd problem... which I needed root to fix, and then the SU binary needed an update, and I couldnt install busybox.... and the vicous circle continues. "
The internal storage is not enough for the backup, because it is 1GB+ and on the stock ROM you have less than 1GB to use unless you delete things, which you can't do without a write protect removed kernel.
" Now Just waiting for S-off I guess."
We have S-off. You have to relock your bootloader and you can use Sunshine. I haven't done it and don't really plan to, but others have.
"busybox is being an ass as well"
Exactly how is it being an ass? I can probably help you with that. I have had one recurring problem with busybox. I will install it and it will say it cannot gain root privileges then it exits. I simply go back in the app and it works perfect.
@EarlyMon @knoober I was lost at first when you two were talking about bloat. It is the bloat, but something else on these devices still take up a ton of space. Even after removing all bloat you only have ~1GB internal memory to use. Link2SD will be your friend. I currently use a 32GB ext4 partition to link internal apps. You can try out Cyanogenmod 11 and a ported GPE ROM. Devs are currently working on Cyanogenmod 11 and 12 and the GPE ROM, because they all have problems.
