Cyanogenmod Installer failed!

[Akolyte]

Im a noob with Android but I want Cyanogenmod, so I used the Installer, everything went fine until it wanted me to unlock my bootloader.  I did what it said and then it seemed like my phone crashed.  After that the CM installer said they couldn't detect my device and I thought my device was in a bootloop.  Luckily one manual reboot got it back into the OS, I'm now afraid of trying again with the installer but I really really want Cyanogenmod.

 

What do you think of the issue? Do you think I should try again?  

 

My Phone is the HTC One GSM. 

 

 

[rustikles]

I had this problem when I used the CM installer on my One. It ended up successfully installing clockworkmod, which allowed me to then flash the rom. You may want to check if that's the same for you. Hold down the volume down button and power button until the screen turns off, and let go of the power button NOT the volume down, keep it pressed. It should take you to a screen where you can choose "recovery".

[Akolyte]

I had this problem when I used the CM installer on my One. It ended up successfully installing clockworkmod, which allowed me to then flash the rom. You may want to check if that's the same for you. Hold down the volume down button and power button until the screen turns off, and let go of the power button NOT the volume down, keep it pressed. It should take you to a screen where you can choose "recovery".

it just sends me to the bootloader, you can select recovery but its a white screen with androids skating

 

@rustikles edit:

 

btw, according to root checker, my phone is not rooted.  

[AMICLG]

it just sends me to the bootloader, you can select recovery but its a white screen with androids skating

 

@rustikles edit:

 

btw, according to root checker, my phone is not rooted.  

I'm pretty sure it needs to be rooted.

[rustikles]

it just sends me to the bootloader, you can select recovery but its a white screen with androids skating

 

@rustikles edit:

 

btw, according to root checker, my phone is not rooted.  

In that case, I would give it a go with the installer again, then go straight to the CM wiki for non-installer instructions to root. I think most of the issues with the installer come from USB driver compatibility maintaining a connection with the device through reboots and firmware changes (at least in my experience).

[Akolyte]

In that case, I would give it a go with the installer again, then go straight to the CM wiki for non-installer instructions to root. I think most of the issues with the installer come from USB driver compatibility maintaining a connection with the device through reboots and firmware changes (at least in my experience).

f***!

 

I hit recovery like you said and now theres just a black screen!  Oh f***ing s***! D':

 

Edit:

 

@rustikles I think its broken!  I cant do anything! >:'(

[rustikles]

f***!

 

I hit recovery like you said and now theres just a black screen!  Oh f***ing s***! D':

 

Edit:

 

@rustikles I think its broken!  I cant do anything! >:'(

Are you able to turn off the device and access the screen where you chose the recovery option in the first place? You might have to hold down the power button longer than you think necessary.

[Akolyte]

Are you able to turn off the device and access the screen where you chose the recovery option in the first place? You might have to hold down the power button longer than you think necessary.

I got to that screen, I already told you I hit recovery! 

[rustikles]

I got to that screen, I already told you I hit recovery! 

I know, but if you can still get to that screen, you can also use fastboot. From there the stock ROM can still be reloaded. I'm sorry you're having problems  . Trust me, I've been there and know the feeling. Do you have adb on the computer you're connecting the phone to?

[Akolyte]

I know, but if you can still get to that screen, you can also use fastboot. From there the stock ROM can still be reloaded. I'm sorry you're having problems  . Trust me, I've been there and know the feeling. Do you have adb on the computer you're connecting the phone to?

Nope I'm a complete noob, but my phone rebooted automatically, its a miracle!  

 

I dont have root I dont think and I dont have a custom recovery either.  Its just stock with an unlocked bootloader, Though I've heard TWRP is a better recovery than CWM, thats what I've heard according to some stuff I found on the internet, not sure though.  

And, I dont know what adb is.  

I'm gonna watch a movie and let the stress off, so ill brb. 

[rustikles]

Nope I'm a complete noob, but my phone rebooted automatically, its a miracle!  

 

I dont have root I dont think and I dont have a custom recovery either.  Its just stock with an unlocked bootloader, Though I've heard TWRP is a better recovery than CWM, thats what I've heard according to some stuff I found on the internet, not sure though.  

And, I dont know what adb is.  

I'm gonna watch a movie and let the stress off, so ill brb. 

I agree, take some time away from it. I took a full two days of messing with that crap before it finally worked the way I wanted it to. Also, FYI if you get CM loaded, don't even consider trying to do nightly updates. I did, and didn't fully understand in inconvenience of having a phone that needed to make it through the workday, but wouldn't boot or work properly (as some nightly builds do).

 

Some info for when you get back into this (I'm just summarizing from the CM wiki)

• ADB (Android Debug Bridge) is a command line program that allows you to interface a computer with the android device. Information about it and common commands can be found here. On Windows, it is most easily acquired through Google's android SDK and is in the "platform-tools" folder. If you aren't already aware, this means it can only be used from command prompt on windows with syntax like "adb _____" (e.g. "adb push filename")
• To unlock the device you'll use "fastboot" which is also a program found in the SDK. This is basically a pre-android boot utility for loading firmware. Essentially you'll plug in the phone to your computer via USB and follow the instructions on the CM wiki that I linked earlier. But you did say that it now has an unlocked bootloader, so you're past this step.
• Again using fastboot, you'll then load the recovery image of your choice (make sure it's the right version for your device) as described in the wiki.
• Once you're past that, take a breath because 95% of the work is done 
• Then, you just need to use to use the command "adb push CMImage.zip  /sdcard/" to actually put the ROM in you're device's storage. You'll also want to get standard google apps for the version of android you're running and load them in the same way with adb, otherwise you'll run into problems when you set up the device (like not having the play store or a working keyboard  )
• In CWM (it should be similar in TWRP) choose "wipe data/factory restore" then "install zip from sdcard" and find your CMImage.zip and let it install (If you want to back up an image of your previous rom, do that before loading the CMImage.zip using "backup/restore"). Then do the same for the .zip of gapps you loaded.

You're done! It seems overwhelming at first, but about half the trouble in the whole process is just understanding what to do with and when to use the different commands like fastboot and adb. If you follow the wiki, there shouldn't be any issues. 

 

Not knowing how familiar you are with text based commands, to use adb and fastboot on windows, open command prompt and "cd directory_location_of adb_and_fastboot" before you try and use the commands. Also, just put the .zip files you're going to move in the same folder with adb too, to make things easy.

 

Again, from someone who has been there and had trouble, I wish you the best with it. Having a rooted phone really is worth the trouble IMO.

[Akolyte]

I agree, take some time away from it. I took a full two days of messing with that crap before it finally worked the way I wanted it to. Also, FYI if you get CM loaded, don't even consider trying to do nightly updates. I did, and didn't fully understand in inconvenience of having a phone that needed to make it through the workday, but wouldn't boot or work properly (as some nightly builds do).

 

Some info for when you get back into this (I'm just summarizing from the CM wiki)

• ADB (Android Debug Bridge) is a command line program that allows you to interface a computer with the android device. Information about it and common commands can be found here. On Windows, it is most easily acquired through Google's android SDK and is in the "platform-tools" folder. If you aren't already aware, this means it can only be used from command prompt on windows with syntax like "adb _____" (e.g. "adb push filename")
• To unlock the device you'll use "fastboot" which is also a program found in the SDK. This is basically a pre-android boot utility for loading firmware. Essentially you'll plug in the phone to your computer via USB and follow the instructions on the CM wiki that I linked earlier. But you did say that it now has an unlocked bootloader, so you're past this step.
• Again using fastboot, you'll then load the recovery image of your choice (make sure it's the right version for your device) as described in the wiki.
• Once you're past that, take a breath because 95% of the work is done 
• Then, you just need to use to use the command "adb push CMImage.zip  /sdcard/" to actually put the ROM in you're device's storage. You'll also want to get standard google apps for the version of android you're running and load them in the same way with adb, otherwise you'll run into problems when you set up the device (like not having the play store or a working keyboard  )
• In CWM (it should be similar in TWRP) choose "wipe data/factory restore" then "install zip from sdcard" and find your CMImage.zip and let it install (If you want to back up an image of your previous rom, do that before loading the CMImage.zip using "backup/restore"). Then do the same for the .zip of gapps you loaded.

You're done! It seems overwhelming at first, but about half the trouble in the whole process is just understanding what to do with and when to use the different commands like fastboot and adb. If you follow the wiki, there shouldn't be any issues. 

 

Not knowing how familiar you are with text based commands, to use adb and fastboot on windows, open command prompt and "cd directory_location_of adb_and_fastboot" before you try and use the commands. Also, just put the .zip files you're going to move in the same folder with adb too, to make things easy.

 

Again, from someone who has been there and had trouble, I wish you the best with it. Having a rooted phone really is worth the trouble IMO.

Thanks, but I think ill just watch a youtube video...

[Akolyte]

I agree, take some time away from it. I took a full two days of messing with that crap before it finally worked the way I wanted it to. Also, FYI if you get CM loaded, don't even consider trying to do nightly updates. I did, and didn't fully understand in inconvenience of having a phone that needed to make it through the workday, but wouldn't boot or work properly (as some nightly builds do).

 

Some info for when you get back into this (I'm just summarizing from the CM wiki)

• ADB (Android Debug Bridge) is a command line program that allows you to interface a computer with the android device. Information about it and common commands can be found here. On Windows, it is most easily acquired through Google's android SDK and is in the "platform-tools" folder. If you aren't already aware, this means it can only be used from command prompt on windows with syntax like "adb _____" (e.g. "adb push filename")
• To unlock the device you'll use "fastboot" which is also a program found in the SDK. This is basically a pre-android boot utility for loading firmware. Essentially you'll plug in the phone to your computer via USB and follow the instructions on the CM wiki that I linked earlier. But you did say that it now has an unlocked bootloader, so you're past this step.
• Again using fastboot, you'll then load the recovery image of your choice (make sure it's the right version for your device) as described in the wiki.
• Once you're past that, take a breath because 95% of the work is done 
• Then, you just need to use to use the command "adb push CMImage.zip  /sdcard/" to actually put the ROM in you're device's storage. You'll also want to get standard google apps for the version of android you're running and load them in the same way with adb, otherwise you'll run into problems when you set up the device (like not having the play store or a working keyboard  )
• In CWM (it should be similar in TWRP) choose "wipe data/factory restore" then "install zip from sdcard" and find your CMImage.zip and let it install (If you want to back up an image of your previous rom, do that before loading the CMImage.zip using "backup/restore"). Then do the same for the .zip of gapps you loaded.

You're done! It seems overwhelming at first, but about half the trouble in the whole process is just understanding what to do with and when to use the different commands like fastboot and adb. If you follow the wiki, there shouldn't be any issues. 

 

Not knowing how familiar you are with text based commands, to use adb and fastboot on windows, open command prompt and "cd directory_location_of adb_and_fastboot" before you try and use the commands. Also, just put the .zip files you're going to move in the same folder with adb too, to make things easy.

 

Again, from someone who has been there and had trouble, I wish you the best with it. Having a rooted phone really is worth the trouble IMO.

Okay, I've downloaded TWRP recovery, you think I should just get the latest one?

 

Also, should I use SuperUser or SuperSU?  Another thing, is where do I download them

 

And just as a perfectionist thing, how do I get Gapps once I've installed CM? 

[rustikles]

Okay, I've downloaded TWRP recovery, you think I should just get the latest one?

 

Also, should I use SuperUser or SuperSU?  Another thing, is where do I download them

 

And just as a perfectionist thing, how do I get Gapps once I've installed CM? 

The latest is probably a good bet. I use SuperSU, but it doesn't matter all that much (found on the play store). Also, as I mentioned, gapps are installed in the same manner as pushing the CM .zip with adb. They're, again, on the CM wiki.