HTC One Soft Bricked- Stuck @ CM load screen- Can't get into recovery

[z1ggy]

When I am at the step of going into recovery mode and selecting the SuperUser.zip file, the phone just reboots itself out of recovery.

I have followed all the instructions properly so far, and just did the flashing the twrp.img file. Not sure why this is happening. I can't finish the process to put CM on this phone now..

Edit: See latest posts, but I have rooted the phone now. Problem is currently I am stuck at the cyanogenmod loading screen on my phone. Trying to get the phone into bootloader does not work. Instead phone just does a restart then goes right back to the CM loading screen.

 

[cronos]

Make sure you have the latest recovery version. Also try out CWM if TWRP doesn't work.

You can also try flashing supersu instead of superuser.

 

[z1ggy]

Make sure you have the latest recovery version. Also try out CWM if TWRP doesn't work.

You can also try flashing supersu instead of superuser.

Trying CWM right now..It looks like a DOS command set up though...? not sure how to use this. After I typed in the 'flash recovery CWM.img' command this comes up

usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:

 

[dougp]

I recommend you go with the toolkit.

http://forum.xda-developers.com/showthread.php?t=2364445&highlight=toolkit

 

[z1ggy]

Using the latest TWRP helped.

Now I am installing CM and I got an error 75% of the way through saying the connection between comp and phone is bad. Now my phone is stuck on the CM loading screen and no further progress will go. When I do a restart.. Nothing happens. Just brings me right back to the same screen. Frustrating...

 

[Joe1987]

second the toolkit, it's worked for everything I tried.

 

[z1ggy]

I think the phone is bricked. D:

Stuck on the CM bootload screen, I press power + vol down button to get to bootloader.. It goes to HTC restart screen with the whole "this is a dev model..yadda yadda" in red at the bottom.. then won't go to the bootloader and goes right back into the CM loop.

Trying to use the command prompt does nothing because it says "waiting for device". Basically phone is stuck. Not even power + BOTH vol buttons will do anything.

 

[cronos]

The red message is because you have a custom recovery. Don't worry about that.

Try again booting to bootloader while putting the phone under bright light (I'm serious). When you get there, type 'fastboot erase cache', and then boot to recovery.

If you are able to get to recovery, try again installing the ROM.

If this still doesn't work, go ask around at XDA, someone should be able to help you out.

 

[z1ggy]

The red message is because you have a custom recovery. Don't worry about that.

Try again booting to bootloader while putting the phone under bright light (I'm serious). When you get there, type 'fastboot erase cache', and then boot to recovery.

If you are able to get to recovery, try again installing the ROM.

If this still doesn't work, go ask around at XDA, someone should be able to help you out.

Haha bright light?? What would that do..? I'm sure if I can get to the bootloader, that I can fix it. If that doesn't work though I might try just putting on the latest 4.4 update.

And this is the first & last time I try the all in one install from CM. It's probably not meant for my phone specifically.. Sigh. I am really worried here..

 

[cronos]

Haha bright light?? What would that do..? I'm sure if I can get to the bootloader, that I can fix it. If that doesn't work though I might try just putting on the latest 4.4 update.

And this is the first & last time I try the all in one install from CM. It's probably not meant for my phone specifically.. Sigh. I am really worried here..

Yeah, the bright light is because the HTC One has some kind of light-sensor protection so it won't boot while in the pocket or in a bag. If you want to force boot the phone and it's rather dark, sometimes the sensor takes over and prevent the phone from booting.

I didn't realize that you were trying to use CM installer. I thought you had to have stock everything (rom/firmware/recovery but unlocked bootloader) to start the process?

 

[tiracuenta]

Haha bright light?? What would that do..? I'm sure if I can get to the bootloader, that I can fix it. If that doesn't work though I might try just putting on the latest 4.4 update.

And this is the first & last time I try the all in one install from CM. It's probably not meant for my phone specifically.. Sigh. I am really worried here..

The bright light ensures the reboot can happen (it's a safety to prevent the phone rebooting in your pocket).

Do what cronos said first. That completely powers down the phone, enabling you to get into the bootloader on start.

The phone isn't completely bricked. You can rescue the phone as long as there is a bootloader of some kind on there, and maybe even without one.

What I would do is use fastboot to ensure you have the latest TWRP on there (make sure you erase the cache before trying to reinstall it), then use the adb sideload command to get the ROM zip onto the phone, then flash the ROM. That should be virtually guaranteed to work.

 

[z1ggy]

Yeah, the bright light is because the HTC One has some kind of light-sensor protection so it won't boot while in the pocket or in a bag. If you want to force boot the phone and it's rather dark, sometimes the sensor takes over and prevent the phone from booting.

I didn't realize that you were trying to use CM installer. I thought you had to have stock everything (rom/firmware/recovery but unlocked bootloader) to start the process?

I unlocked phone, then rooted it. Had stock ROM on it and I had the latest TWRP recovery flashed on.

USed the CM installer... Which was probably my mistake. I am going to search for the most stable version of CM specific for the HTC One on the XDA forum once I fix this issue.

Also is the light sensor on the front or back of the phone?

The bright light ensures the reboot can happen (it's a safety to prevent the phone rebooting in your pocket).

Do what cronos said first. That completely powers down the phone, enabling you to get into the bootloader on start.

The phone isn't completely bricked. You can rescue the phone as long as there is a bootloader of some kind on there, and maybe even without one.

What I would do is use fastboot to ensure you have the latest TWRP on there (make sure you erase the cache before trying to reinstall it), then use the adb sideload command to get the ROM zip onto the phone, then flash the ROM. That should be virtually guaranteed to work.

Okay, I will try holding down power + volume down tonight infront of my bright bathroom lights.

I do have the latest version of TWRP on there, I got off the XDA forums last night (2.6.3.x I believe)...So I don't think I will need to reflash..? I'm not totally familiar with the adb commands.. just the fastboot ones. And by ROM zip.. do you mean the .zip for CM..? Only zip I have placed on my phone is the Superuser zip.

 

[cronos]

I unlocked phone, then rooted it. Had stock ROM on it and I had the latest TWRP recovery flashed on.

USed the CM installer... Which was probably my mistake. I am going to search for the most stable version of CM specific for the HTC One on the XDA forum once I fix this issue.

Also is the light sensor on the front or back of the phone?


Okay, I will try holding down power + volume down tonight infront of my bright bathroom lights.

Light sensor is at the front, at the top of the screen. Reading light works perfectly, or even a flashlight.

I do have the latest version of TWRP on there, I got off the XDA forums last night (2.6.3.x I believe)...So I don't think I will need to reflash..? I'm not totally familiar with the adb commands.. just the fastboot ones. And by ROM zip.. do you mean the .zip for CM..? Only zip I have placed on my phone is the Superuser zip.

I just looked it up quick and this article I found actually says that you don't even have to have an unlocked bootloader for the CM installer. Maybe because you unlocked the bootloader yourself, installed custom recovery and rooted it, the installer gets confused?

http://htc-one.wonderhowto.com/how-...-now-without-rooting-unlocking-first-0149449/

Anyway, I'm going to refrain to say anything else as I don't have any experience with installing CM, especially with the automated installer. I highly suggest you to go to XDA forum specifically for HTC One Q&A. I'm sure there's somebody out there who can help you out. Good luck!

 

[z1ggy]

Light sensor is at the front, at the top of the screen. Reading light works perfectly, or even a flashlight.



I just looked it up quick and this article I found actually says that you don't even have to have an unlocked bootloader for the CM installer. Maybe because you unlocked the bootloader yourself, installed custom recovery and rooted it, the installer gets confused?

http://htc-one.wonderhowto.com/how-...-now-without-rooting-unlocking-first-0149449/

Anyway, I'm going to refrain to say anything else as I don't have any experience with installing CM, especially with the automated installer. I highly suggest you to go to XDA forum specifically for HTC One Q&A. I'm sure there's somebody out there who can help you out. Good luck!

Weird. I had no idea you could put CM on with out the unlocked rooted version. Skeptical... Anyway, I probably won't even try CM again if I do get back to recovery. A friend suggested liquidsmooth ROM.

And thank you for the help. I did already post this question in the XDA forums this morning. No replies yet.

 

[cronos]

Weird. I had no idea you could put CM on with out the unlocked rooted version. Skeptical... Anyway, I probably won't even try CM again if I do get back to recovery. A friend suggested liquidsmooth ROM.

And thank you for the help. I did already post this question in the XDA forums this morning. No replies yet.

I see it now. The AT&T section doesn't get much traffic, so that's probably why. Go to the international HTC One Q&A forum (I provided the link above) and post your question there.

 

[z1ggy]

I see it now. The AT&T section doesn't get much traffic, so that's probably why. Go to the international HTC One Q&A forum (I provided the link above) and post your question there.

Thanks, I changed the title a tiny bit and reposted it in that section.

Based on a few other threads, I could also just be not holding down the vol down button long enough for it to go into bootloader, but I think I was.

This phone seems really finicky (android in general) as to the exact order and timing that you do things in order to get into bootloader, recovery or download.

Confusing for first timers like me

 

[sweenish]

This thread should serve as an example of what happens when you don't do enough research.

And the side lesson of the value of the toolkits.

 

[tiracuenta]

I unlocked phone, then rooted it. Had stock ROM on it and I had the latest TWRP recovery flashed on.

USed the CM installer... Which was probably my mistake. I am going to search for the most stable version of CM specific for the HTC One on the XDA forum once I fix this issue.

Also is the light sensor on the front or back of the phone?


Okay, I will try holding down power + volume down tonight infront of my bright bathroom lights.

I do have the latest version of TWRP on there, I got off the XDA forums last night (2.6.3.x I believe)...So I don't think I will need to reflash..? I'm not totally familiar with the adb commands.. just the fastboot ones. And by ROM zip.. do you mean the .zip for CM..? Only zip I have placed on my phone is the Superuser zip.

Phones have weird names for things, not entirely sure why.

AFAIK: The bootloader is equivalent to the BIOS. It is the first thing that loads, everything else flows from there. Many manufacturers lock it, so that it will not load an unsigned ROM (OS). Unlocking it is necessary to modify the OS, which you have done.

Next comes the recovery. Works similarly to recovery partitions on PCs. This is where you can directly modify the phone's storage without loading a full OS. This is where you can gain root access and flash a ROM (install a new OS)

Then comes the ROM (OS).

I've never used the CM installer, but from the sound of it you've been doing a weird hybrid of the normal method and the CM installer method. You've actually done most of what you need to, so it shouldn't be too hard to go on from here.

From where you are:

get the phone into the bootloader, and then into TWRP, and connect your phone to your PC.

In TWRP, go to advanced->ADB sideload, select wipe cache and wipe Dalvik, and start sideload.

On your computer, you should have a zip file of the ROM you want to load. Open a command window in the directory containing your adb.exe. Type

adb sideload <path to zip file of ROM>

This will put the ROM onto the phone storage, where it needs to be so that the recovery can install it. Once complete the recovery usually will automatically install it. If it doesn't, go back to the main menu in the recovery and select install, and select

sideload.zip

. It will then install. Then install

superuser.zip

(to gain root) and reboot your phone. That should work.

If the phone community just used words in the same way normal computer world did, things would be so much easier.

 

[tiracuenta]

Thanks, I changed the title a tiny bit and reposted it in that section.

Based on a few other threads, I could also just be not holding down the vol down button long enough for it to go into bootloader, but I think I was.

This phone seems really finicky (android in general) as to the exact order and timing that you do things in order to get into bootloader, recovery or download.

Confusing for first timers like me

For the power off when the phone is in a bootloop or frozen, you need to hold power + vol for 10-20 sec under a light source.

To boot into bootloader from power off hold vol down + power until the bootloader shows.

 

[z1ggy]

Phones have weird names for things, not entirely sure why.

AFAIK: The bootloader is equivalent to the BIOS. It is the first thing that loads, everything else flows from there. Many manufacturers lock it, so that it will not load an unsigned ROM (OS). Unlocking it is necessary to modify the OS, which you have done.

Next comes the recovery. Works similarly to recovery partitions on PCs. This is where you can directly modify the phone's storage without loading a full OS. This is where you can gain root access and flash a ROM (install a new OS)

Then comes the ROM (OS).

I've never used the CM installer, but from the sound of it you've been doing a weird hybrid of the normal method and the CM installer method. You've actually done most of what you need to, so it shouldn't be too hard to go on from here.

From where you are:

get the phone into the bootloader, and then into TWRP, and connect your phone to your PC.

In TWRP, go to advanced->ADB sideload, select wipe cache and wipe Dalvik, and start sideload.

On your computer, you should have a zip file of the ROM you want to load. Open a command window in the directory containing your adb.exe. Type This will put the ROM onto the phone storage, where it needs to be so that the recovery can install it. Once complete the recovery usually will automatically install it. If it doesn't, go back to the main menu in the recovery and select install, and select . It will then install. Then install (to gain root) and reboot your phone. That should work.

If the phone community just used words in the same way normal computer world did, things would be so much easier.

Thank you, this was very easy and concise.

Does the new ROM.zip need to be in the adb folder on my pc as well?

Also, does it matter Im running android 4.1.2? If I download the latest version of a ROM and it's meant for the most up to date firmware for my phone (which I dont think my version is) will it cause issues?

 

[tiracuenta]

Thank you, this was very easy and concise.

Does the new ROM.zip need to be in the adb folder on my pc as well?

Also, does it matter Im running android 4.1.2? If I download the latest version of a ROM and it's meant for the most up to date firmware for my phone (which I dont think my version is) will it cause issues?

No problem.

It doesn't need to be. However if it is, then you can type "adb sideload ROM.zip" rather than "adb sideload C:\bla\bla\ROM.zip"

It doesn't matter that you're running 4.1.2. It's like going from one version of Windows or Linux to another - the only thing that matters is that it is designed for your phone.

 

[z1ggy]

so.. adb sideload isn't working. In TWRP it says

updating partition details...
full selinux support is present..
starting adb sideload feature


So when I type in adb sideload <filename>.zip nothing happens. I just get the long DOS crap that tells you all the commands you can use with ADB.

 

[tiracuenta]

so.. adb sideload isn't working. In TWRP it says

updating partition details...
full selinux support is present..
starting adb sideload feature


So when I type in adb sideload <filename>.zip nothing happens. I just get the long DOS crap that tells you all the commands you can use with ADB.

Check if you have the latest adb.

Silly one, but check that you've correctly typed the command and the name of the file.

Try adb push <filename>.zip if that doesn't work, that's supposed to work but i have the converse problem to you with that rather than sideload.

If that doesn't work, you should be able to find an RUU here for your phone, depending on your phone version: http://www.htc1guru.com/downloads/ruu-file-downloads/

this will reset your phone to its original state, and then you can start again with everything happening in the right order, and that should work

EDIT: What happens if you type "adb sideload g" without the phone attached? It should say "cannot read 'sideload'". If it doesn't, the problem is with adb.

 

[lothar]

This thread should serve as an example of what happens when you don't do enough research.

And the side lesson of the value of the toolkits.

Toolkits...Yuck.

 

[z1ggy]

All,

Thank you for your time and replies. I have manually installed CM10.2, things seem to be working fine and are stable.

Learned my lesson on reading things thoroughly (use XDA) and that contrary to what one person said, toolkits with full installers etc aren't the best way (at least for me and what I found).