Dear XDA-Developers Forum,
I require your help fixing my HTC One M7.
When I tried to use an RUU to set it back to stock firmware the RUU.exe returned error 155. Maybe I did something wrong. I have some experience flashing different phones but I'm not a pro like most people here..
Anyway, the phone hung at the black screen with the HTC logo. At some point I managed to reconnect to the bootloader and Fastboot commands were still available. I tried using Fastboot to verify I had the correct RUU which to all appearance was the case. After trying to reboot to system the phone is stuck in a loop. It displays the CM logo from the ROM it had previously installed.
From here, I'm stuck. Power button does not work, combinations to go into bootloader don't work. The only thing that does work is holding power and vol+ and vol- at the same time. This makes the phone reboot (showing white HTC screen with green logo). After a few seconds I am however stuck with the CM logo.
Is there a way to fix this?
Some additional info on my device:
HBoot 1.55
Bootloader unlocked
S-ON (although that's strange cause I had it turned off before)
CM 10.2 installed
TWRP 2.8.5.0
I hope someone has a solution. Of course all drivers and software are up to date and I have backup of my relevent data. I fear that I will need to get a replacement since extensive Google-Search would not yield a solution so far. It could be I'm just not educated enough to understand.
Best regards
Nick
Little Update
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
DNK83 said:
Without any chance of turning the device off and re-entering bootloader or recovery I waited until the battery finally died.
I plugged it into the wall charger. I was then finally able to start to the bootloader. It looked very usual. The security alert had disappeared and it was in HBoot mode.
I went on and selected factory reset guessing this to be the easiest and quite likely solution to the bootloop. TWRP started but showed a number of mounting errors and did not finish the operation. After auto-restart I'm back at the bootloop from the start.
Waiting for the battery to die again...
Any suggestions what I should do next?
Click to expand...
Click to collapse
Error 155 means your using the wrong RUU
You don't need to keep waiting for the battery to die, hold down the volume down button and the power button together, keep them held down, the captive lights on the bottom will flash about 15 times, when the phone goes off, let go of the power button only, the phone should now boot to the bootloader.
post your fastboot getvar all without imei and serial number please, anyone here needs more info about your phone before we can help and this will tell us all everything we need to know.
Hello,
thanks for your reply.
I have tried holding the power button and vol- together. Even after more than 30 seconds the phone does not react and keeps on showing the CM logo.
Sorry, for not providing more information. I would've posted the getvar info before but was not able to connect through fastboot.
Will do once the battery is charged enough for the next try.
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
take the brackets off the all () the command is fastboot getvar all
DNK83 said:
After the battery dying and charging a little bit I was able to go into fastboot mode. The loader screen was showing "fastboot usb". Trying to obtain the variables yields:
C:\fastboot>fastboot getvar (all)
getvarall) FAILED (remote: unknown command)
finished. total time: 0.016s
Click to expand...
Click to collapse
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
alray said:
Why the brackets () in "fastboot getvar (all)" ? The command is "fastboot getvar all" without the quotes.
Click to expand...
Click to collapse
The brackets are added because I'm tired and kinda angry.
DNK83 said:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3684mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Click to expand...
Click to collapse
first of all I recommend you flash twrp 2.8.6.0 from here, it will make life easier for you: https://dl.twrp.me/m7/twrp-2.8.6.0-m7.img.html
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then enter twrp, and create a very simple backup, just something like boot or cache.
now plug your phone into the computer, it should open on your computer as this version of twrp supports MTP, navigate to the TWRP backup folder on your phone and delete the backup file from the folder (just the backup file itself, none of the folders) it will be in TWRP/BACKUP/PHONE SERIAL NUMBER/DATE AND OTHER DIGITS/ delete the file in here and replace with the files in this zip (make sure you extract the zip first): https://www.androidfilehost.com/?fid=95897840722646676
now unplug your phone and restore the backup.
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
DNK83 said:
The installation of TWRP worked fine. Trying to make the simple backup yields a bunch of failed attempts to mount.
Click to expand...
Click to collapse
in that case, select wipe, and then format data button, type yes to confirm, when done, select reboot to recovery for change to take effect, it will say no OS installed, just ignore it, it will also ask you if you would like to install super SU, select do not install, when the phone boots back to recovery, try backup again.
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
DNK83 said:
Okay.
I formatted the card and was able to do the backup. I was neither notified of a missing OS nor asked if I wanted to Install Super SU. Reboot to Recovery worked normal.
Plugging the phone into my computer does not yield a connection that I could use to copy files.
Click to expand...
Click to collapse
make sure you are on the recovery main screen when you plug the phone into your computer, no sub menu's.
If it still doesn't appear on your computer, double check your device manager to make sure its showing in there correctly.
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
DNK83 said:
A "Google Nexus ADB Interface" is listed. Is that what we're looking for?
Btw: many thanks for the help so far. It's becoming quite exciting right now.
Click to expand...
Click to collapse
Strange, it should look like this pict below, I'm using a HTC One M8, with the latest TWRP, but its the same thing as yours, as I previously had the M7.
try uninstall, that driver and then manually install the correct driver.
check Question 2 here on how to manually force the driver: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
DNK83 said:
I have tried re-installing the HTC driver. So far no results. Did you want me to remove this ADB thing from the device manager? I am rebooting quickly to see if Win7 is the problem.
Click to expand...
Click to collapse
yes, just right click that other driver and uninstall it, then reboot.
I just download HTC sync manager and install that for my drivers, then just uninstall HTC sync, you will see the driver package which comes with sync manager just above it, leave that one alone, never had a problem with it.
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
DNK83 said:
The hardware detection ran when I plugged the phone in. The device is again listed as "Google Nexus ADB Device"
I have a package installed named "Minimal ADB and Fastboot Version 1.2". This is probably the reason why my phone is listed this way right now...uninstall?
Click to expand...
Click to collapse
strange, ive never seen it appear like that.
ive attached my adb and fastboot files below if you want to use those, maybe yours came with the google nexus driver.
Related
Ok, so, yesterday my phone just randomly froze. I rebooted the phone and it randomly popped up with this "Decrypt Storage" message where I have to put in a password which I never set to unlock my phone. So, I rebooted into clockworkmod. Well, it shows the CWM logo for a second then reboots into the normal boot. I tried going into the bootloader to do a factory reset. The same thing happens. I don't know what to do! My One is a paperweight! Can anyone help me?
Thanks so much in advance.
HotFieryTech said:
Ok, so, yesterday my phone just randomly froze. I rebooted the phone and it randomly popped up with this "Decrypt Storage" message where I have to put in a password which I never set to unlock my phone. So, I rebooted into clockworkmod. Well, it shows the CWM logo for a second then reboots into the normal boot. I tried going into the bootloader to do a factory reset. The same thing happens. I don't know what to do! My One is a paperweight! Can anyone help me?
Thanks so much in advance.
Click to expand...
Click to collapse
Do you have S-Off and or SuperCID? Can you restore a stored CWM backup? Tried flashing a RUU?
i dont know how ppl expect someone to help them if they dont provide details about their devices..sigh
Ok. I have S-On and I don't have SuperCID. My One is an unlocked One, not Dev version. I cannot restore to a CWM backup because CWM doesn't load. I cannot flash an RUU because when I try to relock my bootloader with fastboot, I get an error saying "FAILED (status read failed (Too many links))." I've also tried deleting userdata through fastboot and I get the error "FAILED (remote: not allowed)." I hope that this I can fix this, cause right now my One is a $600 paperweight.
Thanks so much for your help.
I also just read that this may help you.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .........................
(bootloader) imei: ..........................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4027mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.066s
Thanks again for your help
"FAILED (status read failed (Too many links))." is normal I think, mine says that every time but the operation is actually successful.
RuleOfSines said:
"FAILED (status read failed (Too many links))." is normal I think, mine says that every time but the operation is actually successful.
Click to expand...
Click to collapse
That may be true, but my bootloader still says unlocked.
Anyone have any idea what I should do?
fastboot erase cache
skinsfanbdh said:
fastboot erase cache
Click to expand...
Click to collapse
Ok. I did that. No detectable changes. Every other command still fails.
Oh, also I forgot to say that one change I noticed when it first stopped working was that the boot animation changed from the Renovate Rom one to "ANDROID" with light sweeping from left to right.
phone needs to be connected to the computer and booted to bootloader for the command to work
skinsfanbdh said:
phone needs to be connected to the computer and booted to bootloader for the command to work
Click to expand...
Click to collapse
I wasn't born yesterday.
the command to lock bootloader you are using is fastboot oem lock right?
Have you tried installing a new recovery from fastboot? Maybe try TWRP, to install fastboot oem flash recovery yourrecovery.img
nugzo said:
the command to lock bootloader you are using is fastboot oem lock right?
Have you tried installing a new recovery from fastboot? Maybe try TWRP, to install fastboot oem flash recovery yourrecovery.img
Click to expand...
Click to collapse
I'm starting to think this is a hardware issue. I used the fastboot oem lock command and it gets an error. I tried flashing the stock recovery, CWM, and TWRP. For all three, it says it is successful, but when I boot into recovery, it's the same CWM version I've had that loads the hat logo for a second and then crashes and boots normally. Do you know what the errors I get on almost everything mean?
Anyone?
HotFieryTech said:
I wasn't born yesterday.
Click to expand...
Click to collapse
LMAO.. this was so funny.
Please, anyone know how to fix my broken phone? I can't go to HTC because my phone's bootloader says "TAMPERED" and "UNLOCKED." Someone please help me
Thanks
bump
Anyone? I have a dead device here.
I have no clue what happened but I installed the newest Revolution HD rom and then my phone went and died and got stuck in bootloop but then I managed to get it to bootloader somehow (dont know how, it was magic I'm guessing)
I have it plugged in and it's in fastboot but I have literally no skill or anything when it comes to this stuff. I've tried for weeks to figure out what to do and tried understanding what's up but I actually feel even more confused than before.
I need somebody who's patient enough to explain to me in dot points, yes like a toddler, what to do from here step by step and how to get my htc one working again.
zackalphabet said:
I have no clue what happened but I installed the newest Revolution HD rom and then my phone went and died and got stuck in bootloop but then I managed to get it to bootloader somehow (dont know how, it was magic I'm guessing)
I have it plugged in and it's in fastboot but I have literally no skill or anything when it comes to this stuff. I've tried for weeks to figure out what to do and tried understanding what's up but I actually feel even more confused than before.
I need somebody who's patient enough to explain to me in dot points, yes like a toddler, what to do from here step by step and how to get my htc one working again.
Click to expand...
Click to collapse
Hey, hi
i am here to help you
are you ready??
Just let me know,
1. Are you sOFF?
2. Is your bootlader unlocked?
prunzzz said:
Hey, hi
i am here to help you
are you ready??
Just let me know,
1. Are you sOFF?
2. Is your bootlader unlocked?
Click to expand...
Click to collapse
YAY! thanks so much!
It's S-On and it says UNLOCKED at the top of the screen highlighted in pink so I suspect yes.
zackalphabet said:
YAY! thanks so much!
It's S-On and it says UNLOCKED at the top of the screen highlighted in pink so I suspect yes.
Click to expand...
Click to collapse
Let's just try to get your phone up and running, okay.
in bootloader/FASTBOOT USB: open a command prompt on your pc, go to your adb folder and type:
fastboot getvar all and copy/paste the output here (remove IMEI and s/n)
then
fastboot erase cache
and try to enter recovery (which one are you using by the way? including version number pls)
nkk71 said:
Let's just try to get your phone up and running, okay.
in bootloader/FASTBOOT USB: open a command prompt on your pc, go to your adb folder and type:
fastboot getvar all and copy/paste the output here (remove IMEI and s/n)
then
fastboot erase cache
and try to enter recovery (which one are you using by the way? including version number pls)
Click to expand...
Click to collapse
dont know what version number it is, it's CWMR.
did all that and it's just stuck on "waiting for device"
zackalphabet said:
dont know what version number it is, it's CWMR.
did all that and it's just stuck on "waiting for device"
Click to expand...
Click to collapse
does the screen show FASTBOOT USB in red; see attached
nkk71 said:
does the screen show FASTBOOT USB in red; see attached
Click to expand...
Click to collapse
yes it does.
zackalphabet said:
yes it does.
Click to expand...
Click to collapse
reboot PC and phone, if it still doesn't work, you may need to update HTC drivers; was it working properly before?
latest drivers:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
uninstall everything in control panel/programs that starts with HTC, then install these while you phone is NOT connected
nkk71 said:
reboot PC and phone, if it still doesn't work, you may need to update HTC drivers; was it working properly before?
latest drivers:
HTCDriver_4.8.0.002.exe 15.1 MB
uninstall everything in control panel/programs that starts with HTC, then install these while you phone is NOT connected
Click to expand...
Click to collapse
done and done!
zackalphabet said:
done and done!
Click to expand...
Click to collapse
fastboot devices
it should show your phones serial number, if OK, go to previous post and do the two commands
nkk71 said:
fastboot devices
it should show your phones serial number, if OK, go to previous post and do the two commands
Click to expand...
Click to collapse
it shows nothing. I dont think it's reading my device at all
zackalphabet said:
it shows nothing. I dont think it's reading my device at all
Click to expand...
Click to collapse
open Device Manager on your PC and check what you have
nkk71 said:
open Device Manager on your PC and check what you have
Click to expand...
Click to collapse
It says Unknown USB Device (Device Failed Enumeration)
zackalphabet said:
It says Unknown USB Device (Device Failed Enumeration)
Click to expand...
Click to collapse
what version of Windows are you on? I hope Win 7; Windows 8 and 8.1 sometimes have "issues", there are solutions (I think) but you'll have to look for them.
Try manually selecting a driver, if it's Win 7 or anything like it select "Update Driver" -> "Browse..." -> "Let me choose " -> "Android USB Devices" and select the "My HTC Version: xxxxx" the latest one.
nkk71 said:
what version of Windows are you on? I hope Win 7; Windows 8 and 8.1 sometimes have "issues", there are solutions (I think) but you'll have to look for them.
Try manually selecting a driver, if it's Win 7 or anything like it select "Update Driver" -> "Browse..." -> "Let me choose " -> "Android USB Devices" and select the "My HTC Version: xxxxx" the latest one.
Click to expand...
Click to collapse
I did that and it comes up with this:
zackalphabet said:
I did that and it comes up with this:
Click to expand...
Click to collapse
try uninstalling the driver (in device manager), reboot, and plug in phone again, see if you get the driver working.
nkk71 said:
try uninstalling the driver (in device manager), reboot, and plug in phone again, see if you get the driver working.
Click to expand...
Click to collapse
so I switched to my desktop and tried all of that again and now it seems to be reading it just fine.
after doing getvar all this came up:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3712mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
zackalphabet said:
so I switched to my desktop and tried all of that again and now it seems to be reading it just fine.
after doing getvar all this came up:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3712mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.069s
Click to expand...
Click to collapse
So now your problem is solved, right?
Sent from my HTC One using xda premium
I just installed GPe 4.4 and I'm stuck in boot hell too. It gets to select language and then it restarts.
BobFaggot said:
I just installed GPe 4.4 and I'm stuck in boot hell too. It gets to select language and then it restarts.
Click to expand...
Click to collapse
Same things happening to me. It shows the lockscreen and keeps restarting, whenever I go into my custom recovery it says "entering recovery..." and it goes back into bootloop Did you by any chance get yours fixed?
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
George Kayogre said:
Hello,
My phone is not rooted. It was still on factory setting, with no custom roms. I've been keeping up w/ the updates and i don't recall anything "special" happening before it was bricked yesterday night.
I tried accessing the fastboot screen (vol down + power button), and tried recovering, rebooting, and factory resetting, and they all sent it back to a freezing boot screen.
Using Hasoon2000's HTC One All-In-One Toolkit, I tried to boot it into bootloader, after a couple of hours, I saw a black screen w/ a red triangle in the middle, and after that, it just went back to being frozen at the Htc boot screen.
I have no idea what to do, any suggestions would help.
Thank You
-George Kayogre
Edit: Some specs in HBOOT:
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
George Kayogre said:
Hello,
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
Click to expand...
Click to collapse
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
clsA said:
don't make duplicate posts
I answered you here >> http://forum.xda-developers.com/htc-one/help/htc-one-soft-bricked-idea-to-t2851592
Click to expand...
Click to collapse
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
George Kayogre said:
Sorry about the other thread, i was instructed to make another one in the correct section, but then a mod also moved my old post to this section...making it 2...
Anyway, I'm unable to get my device recognized, all it shows is "waiting for device" for ever.
I'm trying to get the fastboot getvar from Hasoon's program, but it's returning an "error: device not found".
Click to expand...
Click to collapse
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
alray said:
first of all, if you are not returning your device to your carrier or htc like majmoz suggested above and you want to troubleshoot it yourself, you will need to get rid of that toolkit and learn how to use ADB and FASTBOOT from a command window. Toolkits aren't the best thing when troubleshooting. They often comes with outdated stuff.
Install your HTC drivers correctly on your computer
download and install the Android SDK or Minimal ADB and FASTBOOT
do the commands cIsA told you on your other thread and post the results. The output of "fastboot getval all" could also be useful
Click to expand...
Click to collapse
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
George Kayogre said:
Tried that, but still can't get my pc to recognize the device in bootloader, althought HTC sync does pop up every time i connect it.
When i type "fastboot devices" in the command prompt, nothing happens, then "fastboot clear cache" just shows "waiting for device".
I have downloaded the latest drivers, currently updating HTC Sync, hoping it'd affect something
Click to expand...
Click to collapse
uninstall htc sync and try again
alray said:
uninstall htc sync and try again
Click to expand...
Click to collapse
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
George Kayogre said:
Tried w/ and w/o HTC sync, ensured drivers were installed...and "fastboot devices" still has no effect.
Click to expand...
Click to collapse
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
alray said:
try another usb cable, another usb port. If the drivers are correctly installed, and the usb port/cable are ok and you still can't use fastboot commands from bootloader, it might be an hardware issue.
Click to expand...
Click to collapse
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
majmoz said:
Since, it is completely stock and you didn't change anything, it might be a hardware issue. I would return it to HTC or your carrier for repair. The black screen with the red triangle is the stock recovery screen. The other thing you might try is run a RUU if available. Can you post a fastboot getvar all with the imei and serialno removed?
Click to expand...
Click to collapse
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
clsA said:
Unzip this to your desktop and open a command window from it's folder (right click - command prompt here)
plug in your phone to the pc boot to the bootloader with power + volume down
type fastboot devices
your phone serial number should be listed
now type fastboot erase cache
it should say something about formatting cache
now fastboot reboot
hopefully your phone will boot back up
Click to expand...
Click to collapse
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
George Kayogre said:
Finally got my device to be recognized, all I did was plug in my phone, boot in into bootloader...again and again...till it was recognized
This is what "fastboot getvar all" returned:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.110
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *erased*
(bootloader) imei: *erased*
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4078mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I did run these commands, they were performed successfully, but my phone is still getting frozen on the boot screen
Click to expand...
Click to collapse
have you tried to perform a factory reset from the bootloader?
alray said:
have you tried to perform a factory reset from the bootloader?
Click to expand...
Click to collapse
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
George Kayogre said:
Yep, that was the first thing i tried to do, but i was still stuck w/ the same problem.
Click to expand...
Click to collapse
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
alray said:
if your phone is still under warranty, send it for repair because the next actions will void the warranty:
You'll probably have to unlock the bootloader, flash a custom recovery and flash a rom.
Not sure why this happened on a 100% stock phone. Normally, users get in this situation when flashing custom roms
Click to expand...
Click to collapse
Here's something new: after unlocking my phone, and having confirmed that i wanted all my "personal data erased", it just booted up normally and it worked, but then, while using it, t=it simply crashed...and got stuck in the bootloop again, which kinda points in the arrow of hardware issue again. I'm gonna try installing a rom (after i figure out how) and see where that leads me.
Update: Flashed CM11, phone still on boot loop, sending to repair soon.
Everyone, thanks for the help anyway, I really appreciate it.
Hi there, I must have flashed the wrong sense ROM. I am extremely noobish, so bare with me.
I tried following this amazing guide: http://forum.xda-developers.com/showthread.php?t=2739126 but have had no luck when it comes to flashing the recovery indicated.
"C:\adb>fastboot flash recovery twrp-recovery-2.7-m7-nobcb.img
error: cannot load 'twrp-recovery-2.7-m7-nobcb.img'"
It looks like I entered it right...
My phone will power on and function OK with data and text, but cannot make calls. Sometimes it'll reboot into hboot when I plug it into USB/AC. I have access to fastboot, but not adb, nor recovery.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: `
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35...
(bootloader) imei: 3559...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4118mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-331585dd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you for your time, XDA!
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
cyrusct82 said:
Have you selected the Fastboot option in bootloader before you flash that?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yes and it shows under "fastboot devices"
It's now managed to have gotten worse and will only boot into the spash screen, then Fastboot (not Hboot).
If I remove the sim card, it will boot up normally (unless it's plugged into USB/AC). If I insert the sim, or plug in the microUSB, it will shortly thereafter crash into fastboot.
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
nkk71 said:
1- error: cannot load -> means the filename is wrong
2- Are you able to get to any kind of stable (or at least semi-stable) part; ROM or TWRP?
3- can you please provide the link (thread and file please) of what you flashed; so that we can look what was corrupted
Click to expand...
Click to collapse
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Enigmatic Fart said:
1) I tried simplifying the name to TWRPnbc.img and it's still says failed
2) I was able to boot into the ROM, make texts and use data reliably for a bit, once this issue started, but now it is so bad I can only access fastboot (including presence in "fastboot devices" of fastboot commands). Hboot does not acknowledge USB, adb devices shows nothing (device manager shows nothing in Hboot mode) and attempting to load the ROM kicks me back to Fastboot (not Hboot). Recovery kicks me back to Fastboot as well :crying:
3)It was a while ago that I flashed this ROM and it WAS stable for nearly 6 months, but I think it was just the first ROM of the list for the GURU resets, here:
http://www.htc1guru.com/downloads/stock-rom-downloads/
The version of TWRP I was trying to flash, if you are interested, is in the guide/link in the OP.
Thank you for your time and attention, nkk71!
Click to expand...
Click to collapse
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
nkk71 said:
1- renaming the file is no problem, but you probably ended up with <NAME>.img.img (double extension due to Windows hiding known extensions), hence the use for Windows Command Prompt - DIR command and TAB-completion
2- you being able to boot (to some extent is good-ish)
3- the htc1guru files are meant for the HTC One M7, so nothing wrong there
i'll need to catch up with you tomorrow, as i'm off for tonight, take it easy
Click to expand...
Click to collapse
Cool man, I'll run through and try to flash it again in the meantime and edit this post with results.
Thanks again for your help! Peace!
EDIT: OK, I see what the issue was, but a new one popped up. So I was attempting to flash the recovery I placed in my phone's storage. I now have "TWRP.img" (latest TWRP) and "TWRPnbcb.img" (the no bcb one from that guide) in my adb folder (where fastboot is) on my PC and have attempted to flash both recoveries for S&Gs.
Here are the results:
"C:\Windows\system32>cd C:\adb
C:\adb>fastboot devices
HT35xxxxxx... fastboot
C:\adb>fastboot flash recovery TWRPnbcb.img
sending 'recovery' (11278 KB)...
FAILED (command write failed (No such device or address))
finished. total time: -0.000s
C:\adb>fastboot flash recovery TWRP.img
sending 'recovery' (12534 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s"
Last ditch bump! I don't want my phone retire in a junk drawer!
Enigmatic Fart said:
Last ditch bump! I don't want my phone retire in a junk drawer!
Click to expand...
Click to collapse
please post a "fastboot oem last_dmesg", after trying to flash something
@alray, might be able to decipher that
(sorry for the ping)
Hello everyone who is going to read this. So I have this old HTC M7 (Att and unlocked) that I need to put a new ROM on. However it has been about 3 years since I have done this. I moved to Germany a couple years ago, got a phone here and decided against messing with anything at the time. Well bad things happened with water and now I need to use my old phone.
I am not sure what kind of info will be needed but I will give as much now as I can from the "About Phone"
CyanogenMod version 11.0 installerXNPQ32
Android Version 4.4.4
Build Number cm_m7-userdebug 4.4.4 KTU84Q InstallerXNPQ32P
The phone was recently wiped and had some random apps put on just to be used for games or whatever but now I need it as a phone.
What I basically want to do is flash a new ROM that is more stable. However I have no idea on how to do that and the way I did it before is not a good way to do it now? Honestly I wouldn't care but my plan isn't due for renew until March. Any help I can get would be greatly appreciated and if I have posted this in the wrong area I am terribly sorry.
Drakeor said:
Hello everyone who is going to read this. So I have this old HTC M7 (Att and unlocked) that I need to put a new ROM on. However it has been about 3 years since I have done this. I moved to Germany a couple years ago, got a phone here and decided against messing with anything at the time. Well bad things happened with water and now I need to use my old phone.
I am not sure what kind of info will be needed but I will give as much now as I can from the "About Phone"
CyanogenMod version 11.0 installerXNPQ32
Android Version 4.4.4
Build Number cm_m7-userdebug 4.4.4 KTU84Q InstallerXNPQ32P
The phone was recently wiped and had some random apps put on just to be used for games or whatever but now I need it as a phone.
What I basically want to do is flash a new ROM that is more stable. However I have no idea on how to do that and the way I did it before is not a good way to do it now? Honestly I wouldn't care but my plan isn't due for renew until March. Any help I can get would be greatly appreciated and if I have posted this in the wrong area I am terribly sorry.
Click to expand...
Click to collapse
Can you post the output of "fastboot getvar all" (Don't post your imei and serialno)?
what custom recovery is installed on your phone (Name + version)?
alray said:
Can you post the output of "fastboot getvar all" (Don't post your imei and serialno)?
what custom recovery is installed on your phone (Name + version)?
Click to expand...
Click to collapse
I am not sure on how to get the info for fastboot and I have no recovery on as of yet. I factory reset it. If I do have one I have no idea which it is.
Drakeor said:
I am not sure on how to get the info for fastboot
Click to expand...
Click to collapse
install this, connect your phone to your computer, reboot your phone in bootloader / fastboot usb mode ("fastboot usb" in red letters)
start an adb/fastboot window: start menu ---> programs ---> minimal adb and fastboot ---> minimal adb and fastboot.exe
type "fastboot getvar all" without the quotes and hit "Enter"
copy/paste the output here (without the imei and serialno)
I have no recovery on as of yet. I factory reset it.
Click to expand...
Click to collapse
There is always a recovery on your phone, a factory reset does not erase the recovery partition, only user data.
If I do have one I have no idea which it is.
Click to expand...
Click to collapse
What about booting in recovery mode to check what version is installed....?
Hold power + vol down then select "recovery" from the bootloader menu.
alray said:
install this, connect your phone to your computer, reboot your phone in bootloader / fastboot usb mode ("fastboot usb" in red letters)
start an adb/fastboot window: start menu ---> programs ---> minimal adb and fastboot ---> minimal adb and fastboot.exe
type "fastboot getvar all" without the quotes and hit "Enter"
copy/paste the output here (without the imei and serialno)
There is always a recovery on your phone, a factory reset does not erase the recovery partition, only user data.
What about booting in recovery mode to check what version is installed....?
Hold power + vol down then select "recovery" from the bootloader menu.
Click to expand...
Click to collapse
Ok, I have everything downloaded. I have tried to get the "fastboot getvar all" but it just hangs there. Currently my computer is not seeing my phone so I am installing Android Studio. I think that is what I have to install in order to get the drivers for my phone to be seen.
I did find out the recovery (thanks for the info on how to find it). I am currently running CWM V6.0.4.8
Once I have the info I will edit this or post it if you have replied.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s