So, I inherited this seemingly bricked HTC One M7. I wanted to fix the phone and possibly flip it for a profit (since it was free and all), but I haven't been able to find a proper solution to the problem of this phone. Here's the skinny:
I'm using Windows 8.1 and think that most of my problem is stemming from the recognition of the device. I can see the device listed as "One" under other in Device Mgr, but when I downloaded the Win 7 drivers (per a guide I can't seem to find right now), Windows did not recognize what I was pointing it to when attempting to update the drivers, so the device remains unrecognized by Windows.
Fastboot commands work, but ADB commands will not work as the device is unrecognized?
The phone has no ROM. Factory reset from bootloader simply returns the bootloader screen and accomplishes nothing.
The phone currently has CWM recovery, but both CWM and TWRP are unable to mount /system /cache or USB. I was also unable to find any install .zips or backups in the recovery module.
The phone has the *TAMPERED* and *UNLOCKED* flags above the versioning in the bootloader and lists S-ON.
I've tried several approaches to fixing this phone, but each method seems to rely on some other step I can't complete. I've reached a stalemate (checkmate?). I'm not sure whether to be hopeful with this phone or not, but I'm going to be anyway. If anyone can offer me some help with fixing this thing, I'd greatly appreciate your time. Thanks!
Related
I ended up going from having a ROM that was missing features and I ended up having nothing but, recovery (ClockWorkMod) and the bootloader.
I would also like to include that my computer doesn't show HTC One or Mass Storage anymore though it shows up under the Device Manager settings when on Fastboot. De-bug is disabled, I don't have a rom to enable it so there goes that.
I do have a TWRP backup but I have no idea how to push it to the phone since debugging isn't enabled, adb cannot find device and fastboot knows that the phone is connected but fails when transfering, mostly when I try to flash a ROM into it.
In summary, HTC One only has access to bootloader, ClockWorkMod, no debug, no rom, clean storage.
I don't care what rom I have to install, if anyone can help as fast as possible I need it for work.
Also when I try adb sideload rom*.zip (error: device not found) shows up.
Thanks in advance.
I'm desperate to the point where all I want is to access whatever ROM is compatible with my HTC One, I'm glad to post any other info.
Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.
Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer
If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)
err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.
Okay, so this is the status quo of my friends phone: HTC One M7 UL, S-On, HBOOT-1.55, TAMPERED, UNLOCKED
There is no OS instelled, I can only boot into recovery (while booting from the bootloader it starts Team Win Recovery Project v2.6.0.1, when I boot from the phone being off it opens ClockworkMod Recovery v6.0.4.6) or bootloader. The internal storage is wiped. My PC is not able to install the device driver software, so I cannot put any files on the phone via USB cable. Also it appears to not be rooted, as the recoveries ask me if I want to install SuperSU. But if I accept this, nothing changes and the next time I get the same question.
All in all almost erverything on this phone is deleted and I have no idea how to put a ROM back on it to flash. Can anyone help me fix this?
Update: Trying out the USB-OTG-cable I get the error "E: Can't mount /storage/usbdisk"
krausebrause said:
Okay, so this is the status quo of my friends phone: HTC One M7 UL, S-On, HBOOT-1.55, TAMPERED, UNLOCKED
There is no OS instelled, I can only boot into recovery (while booting from the bootloader it starts Team Win Recovery Project v2.6.0.1, when I boot from the phone being off it opens ClockworkMod Recovery v6.0.4.6) or bootloader. The internal storage is wiped. My PC is not able to install the device driver software, so I cannot put any files on the phone via USB cable. Also it appears to not be rooted, as the recoveries ask me if I want to install SuperSU. But if I accept this, nothing changes and the next time I get the same question.
All in all almost erverything on this phone is deleted and I have no idea how to put a ROM back on it to flash. Can anyone help me fix this?
Click to expand...
Click to collapse
What errors do you have when installing drivers (adb) on your PC?
mb_guy said:
What errors do you have when installing drivers (adb) on your PC? Without a PC the only option would be a usb OTG cable, you could hopefully install a 4.3 OS as the recovery isn't new enough for KitKat
Click to expand...
Click to collapse
oh i ment just the ordinary windows "error"
trying adb out right now, never heard of it before
Update: I don't get how to use adb. Could you maybe tell me what to do? I get the respose "List of attached devices" and thats it, doesn't find any.
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
bboybtek said:
Hey all! I'm having some big problems getting my phone working. I was running Venom One rom for a while but then decided to try out something else and installed the CM 11S. Again phone worked perfectly but I got used to using Venom so I wanted to go back to it. And that's where I fu**ed it I think... I've installed the rom (I'm using T.W.R.P 2.7.1.1, standard cache and data format) like previously and again everything went smoothly with no errors. However, when I restarted the phone it got stuck on HTC logo. But it wasn't stuck like you couldn't do anything, I could lock the screen and when I unlocked it it would present me with the usual lock screen, time, taskbar etc. but when you unlocked it it went back to the HTC logo after a while an error popped up saying that the htc dialler was not responding. I haven't came across something like that ever before... So I went back to recovery and flashed the system again and again I had the exact same issue. So then I went and formatted everything including my internal storage, and that's where I made the biggest mistake. I forgot that I had the rom zip on internal storage and I'd lose it if I format the partition. No problem you'd say BUT I can't copy anything onto the phone.
When I connect the phone to my PC in recovery mode it just refuses to mount!! No matter which partition I want to mount, nothing comes up in my computer. I went on to the device manager and surely enough the HTC One is an unknown device... I tried side-loading the rom but the adb can't connect to the phone. I tried re-installing the HTC sync just to make sure I definitely have the usb drivers but still no luck. ADB devices command shows no devices connected. I've run out of ideas and I'm regretting my decision to try different roms...
I really don't want to buy a new phone so if anyone has ANY ideas please right it down. Thanks in advance!
Click to expand...
Click to collapse
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
alray said:
don't worry, you'll not have to buy another phone. Your issue is one of the most common issue we see here. First I will recommend you to use twrp 2.7.1.1 only to flash CM11 based roms and use twrp 2.6.3.3 or 2.6.3.4 for any Sense based roms.
You will first need to fix your drivers issue so you can adb push or adb sideload the rom to your phone again. there is a guide linked in my signature (nkk71's guide). In this thread, there is instruction (in the FAQ #2) about how to solve drivers issues.
When your drivers issue are solved, flash twrp 2.6.3.3:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in twrp 2.6.3.3 and adb push or sideload venom and hopefully it will be able to boot and it will be stable.
Click to expand...
Click to collapse
The only weird thing is, I used the 2.7.1.1 to flash the sense rom in first place and everything worked fine :/ . Anyway, thanks for the shout! :good: I'll give it a try right now and see how it goes.
Right, I'm having problems installing the drivers for some reason. The ones downloaded from this thread don't seem to be doing anything at all. When click on them they show up for a split second in task manager and then they disappear. No install wizard no nothing. So i downloaded the ones for Windows 7 from here but this just gives me a message that "Windows could not find driver software for your device." . I mean, what the hell?
Edit: Right, after a lot of struggle I've managed to successfully bring my phone back to life! I have no idea what caused the issues with installing the drivers. I've spent ages deleting every trace of HTC drivers, then installed Windows 7 ones and somehow it worked. Then flashed t.w.r.p 2.6.3.3 and venom and it seems to be working smoothly! Hopefully no more problems . Thanks a lot for helping out man!
I've got someone's old M7 after mine broke (suddenly died, no light whatsoever, but that's for another thread)
This M7 (completely stock) looked fine and I wiped it through fastboot. But It rebooted and greeted me with the former owner's settings. Going into recovery shows errors that it can't mount /sdcard. I suspect broken partitions/filesystems.
To remedy the broken partitions I tried to install a newer RUU, but as soon as I do the `rebootRUU` command it reboots, without going to the dedicated HTC RUU environment.
Then I tried to go into recovery and repair the filesystems through `adb shell`, but the shell is not available in a stock recovery.
To flash another recovery I tried to do the HTCDEV stuff first. Almost works as I come up until the screen with the disclaimer (on the phone!), saying yes/agree here, reboots (which should happen), but still, no unlocked bootloader
Does someone have any options left for me to pursue?
hansbogert said:
I've got someone's old M7 after mine broke (suddenly died, no light whatsoever, but that's for another thread)
This M7 (completely stock) looked fine and I wiped it through fastboot. But It rebooted and greeted me with the former owner's settings. Going into recovery shows errors that it can't mount /sdcard. I suspect broken partitions/filesystems.
To remedy the broken partitions I tried to install a newer RUU, but as soon as I do the `rebootRUU` command it reboots, without going to the dedicated HTC RUU environment.
Then I tried to go into recovery and repair the filesystems through `adb shell`, but the shell is not available in a stock recovery.
To flash another recovery I tried to do the HTCDEV stuff first. Almost works as I come up until the screen with the disclaimer (on the phone!), saying yes/agree here, reboots (which should happen), but still, no unlocked bootloader
Does someone have any options left for me to pursue?
Click to expand...
Click to collapse
The issue with the unlockable bootloader is normally relates to broken firmware. The solution is to flash an ruu or firmware package before unlocking the bootloader. But since rebootRUU mode is unstable that's not going to be possible.
Are you able to issue fastboot commands to the bootloader in fastboot usb mode? Can you post the output of
Code:
fastboot getvar all
?
Sent from my HTC One M9 using Tapatalk