Database Develop

[Q] Is my One toast?

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.

[Q] Semi-bricked HTC One

Hi guys sorry to be of trouble.
I rooted my HTC One today after being on Vodafone UK stock ROM. I think I flashed a bad kernel and now I can't seem to get anywhere. When I turn on the phone, I get the green HTC logo and then black screen. When I press the power button the Capacitive buttons light up. However I do have full access to the bootloader and TWRP recovery. When I try to sideload a ROM, I get a verification error. I know I'm doing something wrong, if someone could help me get past this I'd really appreciate it.
My phone's details are:
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.161.1
fastboot getvar all gives me
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4311mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks guys.

ten bucks goes to whoever can get me through this
Thank you!

Alright ! I got your PM and here I am :
Start your phone in bootloader (adb reboot bootloader)
Select "Fastboot" so that it appears in red instead of HBOOT
On your computer, make sure fastboot sees your device, then type "fastboot erase cache"
Type "fastboot reboot-bootloader"
Reflash your recovery (I recommend CWM). Might as well play it safe.
Wipe data/factory reset (you will loose everythng)
*** If there are files you need to keep, you can always use adb pull to get them out before hand (let's say a nandroid backup or other important thing)
Wipe Cache partition
Advanced -> Wipe Dalvik Cache
Since you didn't have any luck using sideload, we'll use push
Code:
adb push [path/nameoffileonyourcomputer.zip] /sdcard/rom.zip
Once that is done, simply take your cell phone
Select Install zip
Choose zip from sdcard
Voila ! You should be good to go !
ROM-wise, I really recommend you get Android Revolution HD. It stays true to HTC Sense while really improving it. The only issue is that your device is still S-ON, which is something that should be fixable pretty soon .
Hit me up if there's anything else !

Thanks a million for your detailed reply.
Before I tackle it, I have a small question. In step 5, you advise to reflash recovery. Would I transfer the CWM recovery file to the phone using the push method you also mentioned?
Thanks.

Gadge64 said:
Thanks a million for your detailed reply.
Before I tackle it, I have a small question. In step 5, you advise to reflash recovery. Would I transfer the CWM recovery file to the phone using the push method you also mentioned?
Thanks.
Click to expand...
Click to collapse
Nope
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]

Thanks again for the quick reply!
I've done everything up to Step 9. Unfortunately I get the error "error: device not found".
Do I have to mount a space on the memory or something first?
Regards,
G.

Gadge64 said:
Thanks again for the quick reply!
I've done everything up to Step 9. Unfortunately I get the error "error: device not found".
Do I have to mount a space on the memory or something first?
Regards,
G.
Click to expand...
Click to collapse
In recovery you should have access through ADB. Once plugged in and connected, on the CWM main page; try
Code:
adb devices
to see if you can connect.
Otherwise, you're going to have to try :
Select "Install zip"
Select "Install zip from sideload"
On your computer, try adb sideload [pathonyourcomputer/rom.zip]
Try it out

attanasi0 said:
In recovery you should have access through ADB. Once plugged in and connected, on the CWM main page; try
Code:
adb devices
to see if you can connect.
Otherwise, you're going to have to try :
Select "Install zip"
Select "Install zip from sideload"
On your computer, try adb sideload [pathonyourcomputer/rom.zip]
Try it out
Click to expand...
Click to collapse
I did that and it was still showing me nothing. Sideload failed also.
I went into device manager and noticed the yellow triangle where the HTC was listed. For some reason it failed to load the driver when I turned on my computer this evening, when it was working fine all day. I forced the driver in now, and currently the file is transferring. I'll let you know how it goes!
Btw thanks again for your reply.

I went for the ViperOne ROM, and that's currently installing. Looking good!

Just to update, everything's working fine now.
Thanks a million attanasi0 for your great help! I'll PM you in the morning

My HTC One is soft-bricked(?) and i have no idea what to do

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.

How do i run ADB from system32??? [solved]

I am trying to recover my HTCone m7 from this stuck logo screen upon lunch. At this point I want to get s-off in order to RUU my phone. The bagillion potential fixes online have lead me to believe that i need to push Android Rev HD in order to add firewater which will grant me s-OFF, allowing me to run the RUUexe. following>>>>>htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-firewater-any-computer-015123
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?

tacoDawg said:
NOW i need to use abd but it wont connect for s--t. I'm guessing its because my computer is referencing the drivers from system32 but when i move my platform-tools folder to systems32 i get "...adbwinapi.dll file missing" or somethiing like that.
My question. How do i get ADB working from system32?
Click to expand...
Click to collapse
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.

Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
well moving the abd folder to the C drive did get fastboot working without the "adbwinapi.dll file missing" error but adb just wont connect. Its showing up in device manager as "ACER composite ADB Interface" and in Driver File Details its pulling files from system32.

Jxt. said:
Hello there, you do not need to have your adb folder in your system 32 folder in order to work. Instead, try moving it to the root of your Hard drive, so that it looks like C:/adb then try it from there. Tell me if that works
Click to expand...
Click to collapse
alray said:
Don't know why you think you have to do this. Adb doesnt have to be executed from system32. You can execute it from anywhere as long that all files are in the same folder (adb.exe, fastboot.exe and their related dynamic link library like adbwinapi.dll and adbwinusbapi.dll)
You also need your HTC drivers correctly installed on your computer.
ADB commands will only work from a custom recovery or from a booted OS with usb debug enabled.
Fastboot commands are used from bootloader mode.
Click to expand...
Click to collapse
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.

tacoDawg said:
i thought the adb.exe and the driver needed to be in the same place for some reason... Ive switched out the htc drivers a gazillion times i dont think thats the issue..or maybe it is..... all i know is ADB refuses to cooperate.
Click to expand...
Click to collapse
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.

majmoz said:
You might try and start over.
** Uninstall the HTC driver from your computer and reboot.
** Download and install the latest HTC drivers. Do not install Sync or remove it after it installed.
** Download and install ADB & Fastboot in your root drive
** Assuming you can boot your phone normally, check Settings >> Developer options >> USB Debugging must have a check by it showing it is enabled.
** Now connect the phone to the computer and type the following in a cmd window:
Code:
adb devices
You should see your serial number in the cmd window.
Now type:
Code:
adb reboot bootloader
You should see the bootloader screen on your phone.
** Using the pwr and vol buttons select Recovery assuming a custom recovery is installed
** While at Recovery's main screen, type:
Code:
adb devices
You should see your serial number and next to it recovery Now you should be able to run the adb commands that you desire.
You mention that you want to run a RUU and that is why you want to s-off! If the RUU is the same version or higher you can run it as long as your bootloader is locked/relocked. If it is lower or a different version then you need s-off.
Click to expand...
Click to collapse
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.

tacoDawg said:
ive tried starting from scratch.. i have this RemoveOldHTCDriver3.exe that ive run but i dont know if that does the trick.. also what about the adb drivers? how would i remove those?
my phone is stuck at the launch screen, RUU seems like it would fix this.. so if i dont need s-off when i run the RUU why dose it stick at sending evvvvverrrrryyyyyyyyy eeeeffffiiiinnnnggggggg time?
Im going to try downloading another newer RUU maybe that will work..
thanks btw.
Click to expand...
Click to collapse
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.

majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
did everything you suggested.. got further than before kinda. I feel asleep at like 2am with the RUU app still sending.. I woke up around 5 something and it was still sending so i just shut down my computer and went back to sleep... when i wake up again the phone says RUU failed or something.
I re-run the app thinking maybe it was because i didnt 'run as administrator' two hours later its still sending...........................
this is the ruu im using: RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
maybe that bracketed 2 is throwing something off, i dont know.
is there an alternative to RUUexe.... maybe adb push a zip?

majmoz said:
To remove the HTC drivers go into Control Panel >> Programs and Features >> find HTC Drivers and highlight then select uninstall. To remove the adb and fastboot just delete the folder but save your files that are to be flashed or pushed to another folder first. When you download the newer RUU make sure it is for your variant and the version number is higher than what you presently have.
Click to expand...
Click to collapse
Jxt. said:
Hey taco, so all you are trying to do is flash an RUU?
if so you might want to check that you have the proper model id and matching RUU file, afterwards type "fastboot oem rebootRUU" capital sensitive.
Then start the RUU, If that's not what your trying to get done then tell me what you are trying to do.
Click to expand...
Click to collapse
Yes im trying to RUU, i ran it and after forever it still said sending. I shut the computer down and the phone booted to bootloader with no options to chose from, all it said was "RUU, RUU zip transfer failed" or something like that.. i rebooted and am trying the ruu ran as administrator.

Jxt. said:
Okay so you are getting a flashing error.
Are you in RUU mode when flashing this? (black screen, silver logo of HTC).
You have the correct RUU? (Can you give me a link of where you got it?)
Can you take a screenshot of your pc when you get the error?
That should let me know whats going wrong.
Click to expand...
Click to collapse
my computer just restarted out of nowhere so i lost the cmd prompts from the last attempt but after like 3 hours of sending (ruu app says sending........ and the phone has silver htc w/ blk bkg) i entered fastboot rebbotRUU and the phone reboots to the stuck launch green htc logo screen.. on my computer the ruu app says successful transfer or something... im guessing it didnt work.
ruu:
http://forum.xda-developers.com/showthread.php?t=2496074
phone says: relocked ***security warning***, hboot 1.56
htcONE m7 tmobile....

tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA425W909681
(bootloader) imei: ******1457712
(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: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s

tacoDawg said:
tried RUU for the 5th time... force rebooted the HTC after 2 hours, got 'ruu 155 unknown error'
results of fastboot getvar all:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(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: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.

Jxt. said:
You might want to edit your last post and delete your imei, you don't want to show that around !
---------- Post added at 10:53 PM ---------- Previous post was at 10:50 PM ----------
Another thing, you should be s-off or at least have a stock recovery. One of the two.
Click to expand...
Click to collapse
damn, how stupid of me...thanks. yea, i was trying to get s-off but they suggest ruu.

majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.

tacoDawg said:
MY GOD I COULD KISS YOU! I have been struggleing with this phone for liike 3 months now and you just broke the case like it was nothing. If you ever need to hide a body, consider me down, I owe you one.
Click to expand...
Click to collapse
You are welcome glad I could help. If you could put [Solved] on the title of your first post that would be great. Happy flashing!!!

majmoz said:
You are trying to run a RUU that is a lower version than your phone. Give this one a try is should be the same version or higher.
Click to expand...
Click to collapse
Jxt. said:
Yeah, tell me how that works
Click to expand...
Click to collapse
s***s working now, thanks for looking out.

[Q] Possible Hard Brick. How can I fix it?

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.