Hello,
I just got the HTC One today, and installed CyanogenMod. There were problems with some key-features, so I decided to just stick with the stock rom. Unfortunetely, when I tried to re-install the stock rom, everything ****ed up, to say at least. So with the help of TWRP I wiped the SD-card, but I think something went wrong in the process, because the phone kept restarting only making it to the logo of TWRP. (Then, I tried to do an adb sideload, but I was told that no devices was found. Fastboot sees my HTC One, but ADB doesn't. Also, I am not able to transfer anything to the SD-card, as it is not showing up when I connect my phone to the computer. Now I am just stuck at the bootloader, with access to TWRP. The bootloader says TAMPERED and UNLOCKED.
I have been using the AIO-kit so do most of the unlocking.
How do I get my phone back to stock rom?
Or, how do I make ADB reconize my device?
Related
Hi,
so I rooted my phone, unlocked the bootloader, installed TWRP, put in 3 different ROMs on my External SD card, went ahead, deleted EVERYTHING from the phone, tried flashing ROMs, not a single one worked.
I rebooted the phone because I saw no other option, TWRP said that there is no OS, I went ahead and did it.
Now the phone won't start, I tried returning it to stock firmware as per lg-phones website guide (worked before, though my phone was not this messed up, I could access download mode and now I can't), but I keep getting connection problems. I have tried doing this with the phone just "turned on", it hangs on LG logo for infinity.
When I try putting the phone in download mode, the only thing I get is fastboot. When I try to use adb devices and other similar commands, it says device not found or simply does not list it, regardless of the "mode" the phone is in. However if I try and use LAF RECOVERY MULTITOOL, it detects my phone and I can use fastboot commands. I have custom recovery, boot and laf imgs on my PC, I tried flashing them all, PC and phone tell me everything's ok, but when I restart the phone, I get nothing... what am I doing wrong, and can this be fixed? If you have any questions, I'll answer to the best of my ability.
Thanks in advance!
SOLVED!!!!
Just found a backup laf.img that enables download mode... PHEW!
I had rooted my HTC One M7-Sprint a few months ago and installed CyanogenMod 11. Worked great. Now I'm trying to get it back to stock to sell it back cause I have a new phone.
I ran HTC One Gurus Rom "Guru Reset M7 Sprint 1.31.651.2" to return to stock with stock recovery. It did appear to work.
I have bootloader unlocked, and am S-ON.
One of the issues is that the Rom won't match the Firmware since all i could flash was the Rom being S-Off. The idea is that once I do an OTA it will update the Rom and the Firmware and I'll match.
But right now that mismatch between ROM and Firmware has my phone working, boots up into stock Android, but with a non-working screen. I'm told when we OTA it will be working again. the rom was 1.31, and from what I see in running Fastboot Getvar All the Firmware (I think that's version-main?) is 5.05.651.2. So I guess it's Cyanogenmod Firmware? Anyway, no match to the ROM version.
How do I get to the OTA without a working screen? I really don't want to buy any sort of hardware and spend a lot of $$, since I'm only going to get about $35 for the phone when I trade it in! I do have USB Debugging on and ADB working. Is there a way to start an OTA from ADB?
Have you tried just flashing the latest RUU? You may have to flash the full firmware first. That would get the phone up and running with the latest release.
http://forum.xda-developers.com/showthread.php?t=2795856
Hung applying OTA HTC One M7 Sprint
What I read from HTCOne Guru said (which is where I got the file I flashed) said you can't flash RUU if you're S-ON.
I found a cheap on the go cable, connected my mouse, and got the OTA downloaded. Then I said yes, install it. It restarted twice, then....nothing. Frozen. White HTC screen, nothing.
So I powered off, powered on, it starts loading, I hear about 3 notes of the HTC music as it's restarting, and ....nothing. Still stuck.
I can boot into Fastboot, but not ADB it seems (I can't get ADB Devices to return the device ID but I can get Fastboot Devices to return the ID.)
I've powered down and restarted, and I've tried to get into recovery (shuts down the phone). I've rebooted from Fastboot screen. Nothing works.
Steve Thomas said:
What I read from HTCOne Guru said (which is where I got the file I flashed) said you can't flash RUU if you're S-ON.
I found a cheap on the go cable, connected my mouse, and got the OTA downloaded. Then I said yes, install it. It restarted twice, then....nothing. Frozen. White HTC screen, nothing.
So I powered off, powered on, it starts loading, I hear about 3 notes of the HTC music as it's restarting, and ....nothing. Still stuck.
I can boot into Fastboot, but not ADB it seems (I can't get ADB Devices to return the device ID but I can get Fastboot Devices to return the ID.)
I've powered down and restarted, and I've tried to get into recovery (shuts down the phone). I've rebooted from Fastboot screen. Nothing works.
Click to expand...
Click to collapse
All HTC phones come s-on...I don't know where people are getting the info saying you cannot RUU if you are s-on. **Sidenote** You cannot RUU backwards if you are s-on.
The RUU is your best bet to get your device working again.
Remember you need to re-lock your bootloader before running the RUU
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Stevo001457 said:
Hi guys. I've had my HTC one for a while now and it had TWRP flashed on it. About a week ago I flashed the android revolution rom, worked well but my camera went really weird if I looked back at some recordings. So I wanted to revert back to stock everything. I flashed a stock recovery for the M7, after that I had the problem of not being able to connect my device to the computer when I fastboot mode. Simply wouldn't pick it up when I typed ADB devices in cmd. My device wouldn't show up after installing stock recovery. And it doesn't want to restore any roms either in stock recovery mode. I can't even access my folders in that mode to flash any roms. I click either apply from sd card, apply from phone storage. Says for a split second check CID failed or something and reboots itself.
I cannot flash TWRP back cause my computer since it can't pick it up. I've tried everything. Changing USB ports, uninstalling my drives for htc. Changing computers, unlocking, relocking bootloader. No result. I'm screwed cause I'm stuck on this android revolution rom, rooted. Just wanna flash custom recovery. I can connect it to my computer, access folders and add things to it but soon as I turn it off and go into fastboot mode it says fastboot usb and can hear the noise when its connected but it doesn't show up in adb devices and when I flash the TWRP it starts send then comes up with FAILED. Help please, would be appreciated!
Click to expand...
Click to collapse
Adb only works if you'te booted to OS or custom recovery. Command you're looking for in bootloader menu is "fastboot devices"
Fala Puno. Ja sam raditi sada. I'm of Croatian decent in Australia. I'll try this later when I return home
Fixed it! I'm an idiot, I didn't realise I was flashing the m8 twrp instead of m7. That's why it failed. Lol. Anyway thanks
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Relock bootloader and run an RUU.
HTC One M9
Jtsessions said:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Click to expand...
Click to collapse
Go back to TWRP and flash the stable SuperSU 2.65. Beta bootlooped for me too and then I went back to TWRP and flashed 2.65 and it was fine.
When you're in TWRP you should be able to connect the device to your computer and copy the 2.65 to phone storage and then be able to flash it.
Basically I've been trying to root my 4 year old HTC one m7 and after finally discovering that the bootloader was locked I managed to unlock it with much hassel and managed to insert TWRP as a custom recovery screen (YAY)
Therefore thinking that I was being smart I tried to root the phone by Flashing SuperSU into it. However I flashed UPDATE-SuperSU-v2.76-20160630161323 which is the wrong version for my phone =((
Now my phone goes through the boot logo and into a lit black screen where it doesn't do anything. I assumed this was a soft brick but i am currently unable to get out of it. I can get into fastboot and access fastboot commands but am unable to use adb commands while the phone is in fastboot. Keep getting adb server version (31) does not match this client (36).
Stupidly i didn;t backup a Nandroid copy and am unable to restore it(yes yes its stupid of me, now I know)
Currently using a Windows 10 Computer.
Any Ideas on how to get my phone going again?