[One (M8) Q&A, Help & Troubleshooting] dan5001:
Lost & Puzzled Newbie

Hi Guys,

I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!

So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.

I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:

http://xdaforums.com/showthread.php?t=2799796

http://xdaforums.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727

I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.

What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.

I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it :o I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!

Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop :eek:

However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?

EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!

EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier :)

ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted :) Now I could just do with some help deciding what ROM to install & help on how to go about it.....please :)

EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!! :o :eek: :p

I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!! ;)

If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! :( I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it :D

p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!! :eek::eek::eek: