I damaged my dad's project one S, but it was saved after 5 hours.
I damaged my dad's project one S, but it was saved after 5 hours.
My dad is passing his HTC One S to my brother. I often install custom ROMs on Android devices because I dislike unnecessary bloatware, and we usually run apps that require root access. Let me begin by noting that the HTC One S is quite difficult to install custom ROMs on. I had to take my OLD DELL windows XP laptop, which takes a long time to operate since the phone’s driver doesn’t support Windows 8 or 10. So, I had to unlock the bootloader and install TWRP or CWR recovery files onto the device. Done. I selected CM 12 NIGHTLY because it seemed stable enough... sort of. You need ADB to transfer the ZIP file onto your phone’s internal SD card. Unfortunately, ADB wasn’t functioning properly. I decided to skip that step and made a huge error. I ended up wiping the internal storage. Now there’s no ROM left on the phone, and besides recovery and fastboot, nothing else boots. Suddenly the storage got corrupted. Everything is broken. TWRP can’t access any files. The phone is unusable. I reinstalled the stock recovery, cleared storage, and reset everything to factory settings. This restored my storage, though it only worked with the stock recovery. I re-flashed TWRP after a long search and troubleshooting. Four hours of work... I recalled that fastboot could flash boot.img files from the past with my S1. I flashed the CM10 boot.img, mounted the USB drive, and transferred the CM10 back onto the phone. Installed CM10 zip. It’s functioning now. It’s not much, but when you’re in a panic and everything seems lost... it helps. Jesus. And don’t forget, my Dell laptop is running so slow it feels like a dream. CM12 is now downloading... Thanks for reading. It’s 4:20am. I was hoping to sleep in at 11.
Fortunately, my OnePlus receives automatic CM updates automatically.
I encountered a loop while working with an XML file about video settings on my LG G3. I wasn't sure why this happened, but since I didn’t have a custom recovery, I updated the system using the stock ROM from the download option. LG provides a useful flash utility, and I installed TWRP afterward. I’m not using CloudyG3 at the moment.
Yeah see... HTC doesn't have that. Inorder to use a one-fix-all recovery to restore your shit back to stock you have to find the EXACT RUU file. This basically does that. You must match up your Carrier, baseband number and bootloader number. (Depends in you have N-ON or N-OFF) in my case I was ON so I couldn't have a different bootloader number... sadly I couldn't find this RUU file. It doesn't exist for this EXACT model/baseband/bootloader. Retarded as shit. Would have saved me hours.
My Xperia U is unfortunately my phone. I've successfully rooted it, which took a lot of time... I can't even get past the bootloader since it's an STa model.
Sounds like this device doesn't play well with CM12. The TWRP fix is broken now. I'm planning to use Clockwork recovery instead, or I'll go with CM10.
These experiences are exactly what help us develop our best problem-solving abilities. They showed me the importance of patience and thoroughness, especially when I faced a technical issue without any online support. I spent two hours traveling to my parents' house, fixing the software there, and then returning home. I wouldn’t have missed a crucial call or email from a job opportunity if I hadn’t taken the time to resolve it properly!
Balls are really impressive, honestly. I've handled something like this with my old Galaxy S before. That pressure often builds when dealing with these things. I'm lucky to have made it through. Keep pushing, just do whatever you can even if it doesn't seem right. You'll get it! (CM12 is now installed and functioning.)