• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [AT&T] Phone Stuck in Cyanogenmod recovery.

iAndrewFV

Lurker
I been having a issue with my HTC One prior to my mishap(which is the real reason im posting this). My phone has been going into Car Mode when plugged into a regular USB, wall or computer source. In a effort to see a fix, i checked to see if there was a update for my phone, and there was. So i updated it, and the update failed to register. Damn; so i waited a week or so and checked again for a update, nothing. So i figured, "well, the phone still has the old upgrade files, let me go into Titanium backup and erase that(which was UPDATE #.#(idk the exact numbers)). I did so, then restarted the phone. Uh oh... It started going through the upgrade phases but never went all the way. Then it went into Cyanogenmod Recovery and i went blank faced. I have no idea what to do at this point. Connecting phone to the computer won't register it in the File Explorer, but makes the audible sound of it connecting, so i don't really know how to access it. It wants to update, but has no files, which is what i stupidly deleted. Everytime i restart the phone in anyway i know of, it goes back to Cyanogenmod Recovery.
 
ok first off i do not have your phone, but i do know a bit about rooting phones.

when you have a rooted phone, there is no need to update it. most likely updates will not work anyways since the phone is rooted and you have a custom recovery.

all you need to do update the phone is to flash custom roms that has the update cooked into the rom. updates are just software and that is what custom roms are. so flashing roms is the easiest ways to update the phone.

so it looks like your phone somehow has been wiped with no software to install. all you need to do is get a custom rom file onto your sd card and have your recovery flash the file.....again i'm being a little vague as i do not have your specific phone. just make sure that you wipe first (dalvik cache, cache, and system.....i believe) before you flash your rom.
 
so it looks like your phone somehow has been wiped with no software to install. all you need to do is get a custom rom file onto your sd card and have your recovery flash the file.....again i'm being a little vague as i do not have your specific phone. just make sure that you wipe first (dalvik cache, cache, and system.....i believe) before you flash your rom.

Well, the phone does not have a SC-Card slot, nor will it be picked up on my File Explorer on my laptop(though it does register as being plugged in, the phone shows FASTBOOT USB on the "boot/power menu" and on the computer it signals with the audio that something connected, but does not show up). I already downloaded the next stable release of Cyanogenmod on my laptop and ready to go through the steps, but can't, as just stated.
 
Well, the phone does not have a SC-Card slot, nor will it be picked up on my File Explorer on my laptop(though it does register as being plugged in, the phone shows FASTBOOT USB on the "boot/power menu" and on the computer it signals with the audio that something connected, but does not show up). I already downloaded the next stable release of Cyanogenmod on my laptop and ready to go through the steps, but can't, as just stated.

do you have the latest htc drivers?

i'll also send word to scotty who is an expert on all things htc.
 
do you have the latest htc drivers?

i'll also send word to scotty who is an expert on all things htc.

I thought I did. I will go through and see if so and fix if not. Thanks.
Also, would the "latest drivers" fix the Car Mode issue i stated in the beginning be fixed? It is not the REAL issue here, but it would be nice to know.
 
have you been running cyanogenmod on your phone? did you use their installer to install it? cyanogenmod is not a recovery we would typically see,so im a bit unfamiliar with that.

clockworkmod and twrp are the more common recoveries.

when your recovery comes up,is there a menu? what are the options?

is your phone s off,or s on?

last and not least,are you able to boot to bootloader(hold power to force a hard reset,then hold vol down)

very likely we just need to sideload a rom to get your phone working again. :)
 
have you been running cyanogenmod on your phone? did you use their installer to install it? cyanogenmod is not a recovery we would typically see,so im a bit unfamiliar with that.

clockworkmod and twrp are the more common recoveries.

when your recovery comes up,is there a menu? what are the options?

is your phone s off,or s on?

last and not least,are you able to boot to bootloader(hold power to force a hard reset,then hold vol down)

very likely we just need to sideload a rom to get your phone working again. :)

1. I used their installer, yes. It goes into what i assume is their recovery, which i did not know existed.
2. The options are pretty much the same as clockworkmod/twrp, just cyanogenmod-labeled.
3. I don't know what "s" on/off means, I am fairly new to this scene of droid and assume it means "root" along side super user, which i do have.
4.Yes i can get to that bootloader screen.
 
s on/off is htc's bootloader security status,basically security on(does all sorts of signiture/version checks) or off(does no checks whatsoever). youll need to check your bootloader screen to get this info,it will say "ship s on" or "ship s off" at the top.

sounds like you just need to wipe and manually install the newest nightly or "M" release. you can try doing a factory reset first,and see if that lets tht phone boot.

failing that,well have to get your phone recognized in recovery by adb so we can "sideload" a rom,or you can try installing the rom with a usb stick(or sd card in a usb adapter) and an OTG cable plugged into the phone. most recoveries have the option to install from external storage when you have something plugged in.

not sure why you had issue,i install the newest nightly on a weekly basis on my m7,and they always go without a hitch. i am using twrp recovery,not sure if thats an issue or not.

here are some basic troubleshooting tips for adb/fastboot:
troubleshooting connectivity issues:
*make sure you have changed to your adb/fastboot directory!
*make sure usb debugging is enabled(checkmarked) to use adb in the OS
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror for 3.0.0.007. here is a newer driver you can use with newer phones/newer windows versions: HTC 4.0.1.002)

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot(not hboot!),enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.
 
sounds like you just need to wipe and manually install the newest nightly or "M" release. you can try doing a factory reset first,and see if that lets tht phone boot.

failing that,well have to get your phone recognized in recovery by adb so we can "sideload" a rom,or you can try installing the rom with a usb stick(or sd card in a usb adapter) and an OTG cable plugged into the phone. most recoveries have the option to install from external storage when you have something plugged in.

not sure why you had issue,i install the newest nightly on a weekly basis on my m7,and they always go without a hitch. i am using twrp recovery,not sure if thats an issue or not.

1. I figured just as much. I was hoping I would not have to factory reset

2. Would I be able to this without the factory reset bit? I plan on doing this idea first, i just need to find a adapter for this.

3. Well, the first update i tried installing did not go through, it failed to install every time and just restarted the phone. No idea why. That's when i deleted the "UPDATE" file/program/thing in Titanium Backup thinking the phone would not remember the update file/attempt.

I'll start looking into finding a adapter.
 
well,the important thing currently is to get back to a working device. your data doesnt do you any good if your phone doesnt boot ;)

hopefully you backed up contacts,calander,etc with google,so re-setup wont be as big a deal.

just make a backup before trying the factory reset. once you have the safety net of a working phone,we can try to figure out a way to get your phone booting with your restored data.
 
I was reading that factory resetting in a certain way could make the phone go in a worse state. Where would the correct place to do that be then, figure I'd try that first.
 
I was reading that factory resetting in a certain way could make the phone go in a worse state. Where would the correct place to do that be then, figure I'd try that first.

there is no way that i can think of thAt could make the phone in a worse state. all you need to do is find the "wipe" menus of your custom recovery,and use the option to "wipe data/factory reset". all this is doing is wiping your user data and cache partitions,its not removing your boot,system,recovery,etc.
 
there is no way that i can think of thAt could make the phone in a worse state. all you need to do is find the "wipe" menus of your custom recovery,and use the option to "wipe data/factory reset". all this is doing is wiping your user data and cache partitions,its not removing your boot,system,recovery,etc.

Just attempted, still it will not boot all the way and goes into the cyangogenmod recovery. Guess it is time for the ADB sideload. Would it be smart to find a similar version fo the OS or just go straight to the newest nightly/stable?
 
Just attempted, still it will not boot all the way and goes into the cyangogenmod recovery. Guess it is time for the ADB sideload. Would it be smart to find a similar version fo the OS or just go straight to the newest nightly/stable?

sorry for the late reply,been out of town for the weekend. i would prolly flash the newest stable version for now,if you havent allready.

hAve you had any luck,or is your phone still not booting?
 
Sorry for the late reply, but yes I have tried the adb sideload with GREAT SUCCESS. The phone is back on its feet. Thank you so much for helping me with this. :D

Note, when it attempts to download the newest version of cyanogenmod( i used cm-10.2.1-m7att.zip for reference), it downloadsn the file but fails to install( which is cm-11-20140804-snapshot-m9-m7), which is the issue I had that started this mess.
 
Back
Top Bottom