[One (M8) Android Development] skulldreamz:
Hey first off the fixed twrp version works %100. I had just flashed the fixed recovery.img when my hboot was blank. What was the fixed version suppose to magically bring my OS version back, of course not. Lol You first need to reflash your firmware to make the version show again in hboot. Then you flash the fixed version of twrp. You are correct that I had made a premature statement along those lines before I had cleaned my op up some and I take full responsibility in letting the community know it was because of my user error upon flashing it. This is a perfect example of someone not reading the full directions and then making a comment about something not working when it does work flawless the whole time and that's not cool to the dev who has worked so hard to get that project out only to have a bunch of "false bugs" in their own thread and they don't deserve that. That's the whole reason I made my video to show that dd'n my .img is perfectly safe if done correctly. Even though I believe the person might have taken some error credit I still dont like the doubt of other members in the community thinking to themselves who's fault is this really. I've dd so many imgs its insane and never had a single problem, ever. Buts that's just my opinion on the safest way to flash something and other people like fastbooting stuff better. For me I trust myself doing the work a million times more than me doing the work and other factors that are out of my control become invovled too. Now if a problem were to happen it's gonna be my fault and that would be easier to swallow than saying to myself, damn the power cut out during a ruu flash and you have yourself a bricked device or a cable coming out and that's a brick or a USB port or harddrive or any part that connects 1 device to another device, you double the chances of hardware failure. Maybe its because where I live is very prone to our power cutting off is why I have grown more comfortable with a full battery in my handset and no strings attached and my own knowledge and not a current that runs that I have no control of. Even if you use a battery with your pc you could have a internet provider failure where on a phone you have wifi n data. And when dd you can recheck what you have typed to make sure its perfect before you hit enter for the 1/10 of a second flash. Lastly a ruu can take up to 20 minutes on a slower PC or on mine usually about 5 mins but that's a lot higher of a risk of time your phone is vulnerable than the 1/10th of a second that it takes to dd a .img Anyway I have felt bad for the guy even though he got a new device and part of me tries to blame myself because I only want to help people but I had many people read the directions and say the process has been instructed well so if people are going to make modifications on $600 phones without being totally prepared then that is where n why the disclaimer comes in on all of our threads. Well I'm glad you asked that question because it gave me the layout to explain how important reading all directions are and shows what can happen from embarrassing yourself like me from stating that someones awesome job of fixing something didnt work when it was my own fault not reading the full directions to something way more extensive by again not reading the directions and making a paperweight out of your cell phone. To conclude whether you choose to dd that day or ruu that day just know that there are risks but I would bet if someone bricks their phone its not the way they chose that caused it, it's the not knowing what your doing and doing it anyway that caused it. Google Google Google