I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Gotta re lock your bootloader
fastboot oem lock
I got relock it even though it came unlocked? How would I unlock it again since I don't have the tokens from HTC development, or is the ruu gonna do that by itself.
Sent from my HTC One using Tapatalk 2
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA Z(1.29.1540.16) to the latest which I cant get an RUU for. The RUU available is 1.29.1540.3 no other available. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
All I can see now is a scren that says:
***TAMPERED***
***RELOCKED***
bunch of numbers and letters in green and
RUU in orange
schn1tt3r said:
I was having same issues as OP. After using the lock command, the update got longer. The black HTC screen even got as far as a progress bar. Well I now got ERROR 152 saying I should get the correct RUU. I am sure I have the right one, because there is only ONE developer edition RUU file from htcdev.com
Problem now is, I have the black HTC screen with warning signs on each corner.
One thing I saw on a video is you are supposed to restore to the same version? I had updated OTA to the latest which I cant get an RUU for. What do I do now? HTC One Dev Edition stuck on black screen with warning signs on all corners.
Click to expand...
Click to collapse
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Bosnazmaj said:
When I was doing it, the first time I got the 152 error. I simply just redid it and it accepted it on the second try. Trying relaunching RUU that you have and try the install again. That's at least how it worked with me.
Click to expand...
Click to collapse
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
schn1tt3r said:
Did you get that black HTC screen with warning signs on each corner? I am re-running the RUU, hope it works or I just lost $650.
EDIT: You used RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe right? Were you already OTA updated? I wonder why htcdev web says BrightstarUS for the dev edition instead of something else...
EDIT2: Its on that black screen with loading thing again... still exclamation marks on every corner... hope this works or else it won't be a nice first experience with Android coming from iOS lol and I've jailbroken and tinkered on those devices for so long.
---------- Post added at 08:31 PM ---------- Previous post was at 08:21 PM ----------
Yeah 2nd attempt the same error 152. I just lost $650 right?
The green bar goes all the way to the end, it sends it all, but it doesnt reboot. It just gets error. What else can I try? Device isnt even 3 days old.
Did it a third time, after Updating Radio, thats where the error appears.
Click to expand...
Click to collapse
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Bosnazmaj said:
What was the software version that it came with. Was it with the most recent one? I think 1.29.401.16 one?
Click to expand...
Click to collapse
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
I also have same phone de it shouldnt be tamperd relocked it should be only relocked
Sent from my HTC One using xda app-developers app
I find it funny now far Computer OS's have come and yet we always have to go back to good old DOS Command Prompt to fix things.
BTW, my phone now has bootloader RELOCKED due to the fastboot oem lock command, should I send the phone back just like that or unlock bootloader before sending it back?
I guess to Unlock bootloader again, I have to follow same instructions as if it were an AT&T version right? Did you UNLOCK yours again OP?
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
U sending it back to HTC?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yes, that is the reason I was doing all this restoring. I had ROOTed it to install AdAway. Ads is the only major drawback when compared to iOS (this is my first Android). When you see a gray image on my phone, there are 3 sort of water drops. Like between the touch screen and LCD.
Well, I am exchanging it actually. I like the HTC One a lot. It has a tiny gap, but I dont care about that much, the weird discoloration on the sceen, though, I do mind.
That makes sense.
Sent from my HTC One using Tapatalk 2
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
UPDATE
Ok, I figured out how to avoid the RUU 155 error. It seems that HTC for some dumb reason, although for a unlocked developer edition, we still have to lock the bootloader to utilize the RUU. Here are the steps I have done.
Although it is straight forward and easy to do, issues could always arise. I do not take any responsibility if things go wrong. Educate yourself first before attempting anything. If you do not know what you are doing, then don't do it.
Before Starting.
Make sure you have the latest HTC Drivers. You can use hasoon2000 HTC All-In-One Toolkit to complete that. That can be found at HTC One All-In-One Toolkit
Get the appropriate RUU from HTC Dev
1. Lock your bootloader through by booting into hoot and then going into fastboot and issuing the command fasboot oem lock.
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Notice, this will delete all of the files on the system so do this on your own cognition
4. Let the RUU do its thing. If you get an error during the process, such as 152, simply try again. I had it happen once. The phone was stuck on the black HTC screen with four triangles with exclamation points in each corner. If this happens you will not be able to reboot your phone. Simply relaunch RUU and it should reinstall it. If you get error 155 again, then you have not re-locked your bootloader.
3.Once you have successfully reinstalled the rom, you have to register with the HTC Dev to re-unlock your bootloader if that is what you want. The easiest to do this I found was by using the HTC One All-In-One Toolkit. It is a great tool and will help you with majority of things that I have mentioned above, including locking your bootloader. Follow the steps on the toolkit and you'll be all set. The Toolkit can be found here HTC One All-In-One Toolkit
If you found this helpful, click thanks. Also hit thanks to hasoon2000 for creating the toolkit.
Click to expand...
Click to collapse
Thank you. This was very helpful.
Glad I could help
Sent from my HTC One using Tapatalk 2
schn1tt3r said:
It came with the .3 and I did OTA to .16
The RUU you can get online from their web is only .3
===============================
Ok so... that black HTC screen accepts "fastboot" commands.
I downloaded the .ZIP version of the Developer Edition OS.
I went in command prompt, I typed
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
****GOT AN ERROR*****
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
.... so again:
fastboot flash zip PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.zip
10 minutes later
fastboot reboot
Oh my was I happy to see the white HTC Startup.
Click to expand...
Click to collapse
THANK YOU MAN!!!!!!!! You just saved me. I had the same problem except I had OTA .17 and trying to flash .16. My device was all jacked up but it's back to original.
Bosnazmaj said:
I am having an issue that I have not seen before and could not find any resolve thru XDA or Google. I am attempting to restore the 64G Developer Edition with the RUU from HTC Dev and I keep getting the 155 error. I even have attempted to install thru CWM the .zip. Still no avail.
I am currently rooted, and have CWM installed. The device is obviously Bootloader unlock. What I was able to find is that it possibly could be a issue that it is bootloader unlocked as some posts suggest to have you bootloader locked to install RUU, but that is obviosely not a posibility with the dev ed.
So what am I doing wrong, or what is the issue. I have confirmed that I was using the correct RUU.
Help Appreciated
.........
Click to expand...
Click to collapse
Bosnazmaj - thank you for this wonderful write-up & knowledge. I have a Dev edition myself. Sometime ago, I got into charging issues. Initially, assuming it to be software issues, I thought I'd run the RUU. So, like you, I too figured out that I have to lock my bootloader. Ran the RUU....long story short, found out that I have to give my phone for repairs (turned out to be a hardware issue).
So, the point I am trying to make is that, if we unlock the bootloader, certain apps (like flashlight, sound recorder etc) seems to get deleted. While this, on it's own, might not sound too alarming....the problem is, if these apps are not present, then the OTA does not & will not get applied as the OTA says that these apps have to be present. I am not sure how to unlock the bootloader without losing any apps.
Any knowledge / information on this is MOST appreciated.
Actually I used titanium backup to back those apps that disappear during root before I unlocked anything. Then once I rooted and unlocked I just restored them back with titanium and all was fine. But in reality you don't want to so an ota when you are rooted as you might loose root.
Sent from my HTC One using Tapatalk 2
Can't you re-unlock the phone using following command without going through the HTCDev website mess?
Code:
fastboot oem unlock
Just a heads up. I was able to return to stock using the RUU without locking the bootloader. It took a while to figure it out.
I went from ARHD 31 to A stock rom (m7_stock_dev_1.29.1540.16_signed_052313.zip) found on an old thread, also had to find a stock recovery that would work (i think it was the one liked in the ARHD thread) and used the revone S-off method, then applied the latest RUU from the htc dev site .and it installed and the bootloader remained unlocked.
I had to get this thing ready for someone who bought it. They asked if i could return it to stock with S-off. It was a pain in the but, but got it working
so heres what happen
download Andriod revolution for the sprint htc one
it reloaded and went to the bootloader screen I didn't know what happened so I reboot the phone from the bootloader
it went back the bootloader and then without thinking I used the ruu and it relocked the bootloader and didn't even restore the phone so
now I'm stuck with a phone that's stuck on the bootloader screen with it locked and no usb debugging or recovery
is there a way to unlock the bootloader still or atleast enable usb debugging from cmd ? I still have the unlock.bin from the last time I unlocked the bootloader
any idea no phone for me until then
Da1stig said:
so heres what happen
download Andriod revolution for the sprint htc one
it reloaded and went to the bootloader screen I didn't know what happened so I reboot the phone from the bootloader
it went back the bootloader and then without thinking I used the ruu and it relocked the bootloader and didn't even restore the phone so
now I'm stuck with a phone that's stuck on the bootloader screen with it locked and no usb debugging or recovery
is there a way to unlock the bootloader still or atleast enable usb debugging from cmd ? I still have the unlock.bin from the last time I unlocked the bootloader
any idea no phone for me until then
Click to expand...
Click to collapse
The problem was that there is no android revolution for the HTC one. You flashed an international Rom on the sprint variant and so it messed the phone up. You can still unlock the bootloader through the HTC website as before. Check the General section for the guides and the Q&A section to post your problems.
Also, check which RUU you used. Was it from the Sprint HTC one board or the general HTC one board?
I forget that typing in HTC one on the search brings general htc one forum anyway ...
I know how to unlock the bootloader but usb debugging isnt enabled and I don't have an os to enable it
Even tried the all in one to push the bootloader unlock and it just stays saying waiting for device
Da1stig said:
I forget that typing in HTC one on the search brings general htc one forum anyway ...
I know how to unlock the bootloader but usb debugging isnt enabled and I don't have an os to enable it
Even tried the all in one to push the bootloader unlock and it just stays saying waiting for device
Click to expand...
Click to collapse
in the bootloader it uses fastboot actually so if you have those drivers from the unlock till you will be able to do the steps htc asks
I'm going to try in right now let me see what happens
Da1stig said:
so heres what happen
download Andriod revolution for the sprint htc one
it reloaded and went to the bootloader screen I didn't know what happened so I reboot the phone from the bootloader
it went back the bootloader and then without thinking I used the ruu and it relocked the bootloader and didn't even restore the phone so
now I'm stuck with a phone that's stuck on the bootloader screen with it locked and no usb debugging or recovery
is there a way to unlock the bootloader still or atleast enable usb debugging from cmd ? I still have the unlock.bin from the last time I unlocked the bootloader
any idea no phone for me until then
Click to expand...
Click to collapse
Yeah so like the others said use fastboot to re unlock the bootloader, and by the way if you dont have s-off it will be harder to restore it, but if its the case, I would recommend just flashing a recovery and then pushing a rom and flash that. Hope that helps
Oh and always remember as long as you can access fastboot from the bootloader there is always a way to fix a software issue (for the most part)
I still have S-OFF and just tried the command "fastboot flash unlocktoken unlock_code.bin"
Its been saying waiting for device for the last 10 mins .
Da1stig said:
I still have S-OFF and just tried the command "fastboot flash unlocktoken unlock_code.bin"
Its been saying waiting for device for the last 10 mins .
Click to expand...
Click to collapse
Did you install driver for htc one at your computer ?
Sent From The Great HTC
Da1stig said:
I still have S-OFF and just tried the command "fastboot flash unlocktoken unlock_code.bin"
Its been saying waiting for device for the last 10 mins .
Click to expand...
Click to collapse
have you tried plugging your cable into a different USB port on your computer?
If you scour the forums with enough determination, I'm confident that you can find a solution to moving yourself past your current dilemma.
Good luck!
Here's why its not connecting its not the usb because it works with my other phone (GS3)
beny ms said:
Did you install driver for htc one at your computer ?
Sent From The Great HTC
Click to expand...
Click to collapse
Yea I always search before I post I found only one good thread with a similar issue on a htc one s but that thread doesn't have a solution
Sent from my SPH-L710 using xda app-developers app
Heres the RUU you want....http://forum.xda-developers.com/showthread.php?t=2508907
benny3 said:
Heres the RUU you want....http://forum.xda-developers.com/showthread.php?t=2508907
Click to expand...
Click to collapse
I don't think that will work since windows isn't understanding its on the bootloader so doubt it will connect to the ruu but ill give it a shot
benny3 said:
Heres the RUU you want....http://forum.xda-developers.com/showthread.php?t=2508907
Click to expand...
Click to collapse
Da1stig said:
I don't think that will work since windows isn't understanding its on the bootloader so doubt it will connect to the ruu but ill give it a shot
Click to expand...
Click to collapse
UPDATE:Forgot i already tired this since i have the RUU on my desktop. Device Failed Enumeration is my biggest issue one post says he fixed the issue but doesn't state how. The Error shows up with any htc in fastboot i tried deleting htc sync and all its addons from Add/Remove and it didnt help.So currently only think standing in the way of restoring the unlocked bootloader is the fact windows 8.1 keeps blocking the connection and Ubuntu doesnt either work with rooting for me or just because i dont know how to use it :cyclops:
Hey guys. So now i've spent around 7 hours non-stop trying to root my HTC Salsa c510b but alas i am out of luck. At HTCdev it requires me to update my HBOOT and in turn update the ROM; in order to do this i must have a minimum 1.17.862.3 software number for my ROM however me being unable to update this rodent keeps my ROM's software number at 1.17.862.2 (so close ). If i was able to get my ROM to be 1.17.862.3 i would be able to use the RUU for Voda-Hutch AU (model # PH1112000) and successfully run the command fastboot oem get_identifier_token and obtain further information to root my device. But i am stuck. Does anyone know how i could possible fix this problem. Really frustrated.
Regards, Faizan
MasterSplint3r said:
Hey guys. So now i've spent around 7 hours non-stop trying to root my HTC Salsa c510b but alas i am out of luck. At HTCdev it requires me to update my HBOOT and in turn update the ROM; in order to do this i must have a minimum 1.17.862.3 software number for my ROM however me being unable to update this rodent keeps my ROM's software number at 1.17.862.2 (so close ). If i was able to get my ROM to be 1.17.862.3 i would be able to use the RUU for Voda-Hutch AU (model # PH1112000) and successfully run the command fastboot oem get_identifier_token and obtain further information to root my device. But i am stuck. Does anyone know how i could possible fix this problem. Really frustrated.
Regards, Faizan
Click to expand...
Click to collapse
Well I dont think there is any need to unlock bootloaderin HTC Salsa
*Take Device to Fastboot
*Connect To Pc
*Type The Following Command :
fastboot oem unlock
*Accept the warning message on Device.
*Ur Boot Loader Is Unlocked Now.
## Remember It Will Void Your Warranty.
Hit THANKS.
Thanks man...i'll try it.
Itx ok
somehow my HTC salsa (in bootloader mode) doesn't detect in windows 10. i tried all the options mentioned in this portal but i failed to connect. thus i could not able to update HBOOT version so that i can unlock bootloader. It is appreciated if someone can help me on this topic.
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
rabeeh80 said:
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
Click to expand...
Click to collapse
I though for the GPE you only needed to fastboot OEM unlock.
jawmail said:
I though for the GPE you only needed to fastboot OEM unlock.
Click to expand...
Click to collapse
It didn't work .. I guess it doesn't work for 4.2.2 .. Not sure ..
Thanks
rabeeh80 said:
It didn't work .. I guess it doesn't work for 4.2.2 .. Not sure ..
Thanks
Click to expand...
Click to collapse
Unlocking the bootloader on GPe 4.2.2 is not possible any more. Also if you have an unlocked bootloader from before 4.4.2 OTA, don't ever relock cause you will not be able to unlock again. Google removed the partition that had the unlock splash screen. I have tried. The only way to unlock it is to find a signed 4.3 GPe RRU and downgrade. So if you are not rooted and S-on a signed RRU is our only hope! There is way to unlock if you are rooted or S-off.
Sent from my HTC One using xda app-developers app
Unfortunately you can NOT run a signed RUU to downgrade. This is going to have to come as a patch/update from google now
rabeeh80 said:
Dear all,
I have an issue that has dazzled me for a few days ..
I have a 4.2.2 Kitkat HTC one google play edition and would like to install a custom rom.
The first step should be to unlock its bootloader
I've gone through the online tutorial and did exactly what is needed .
1) Loaded into fastboot mode
2) fastboot oem get_identifier_token
3) I received the token and pasted it in HTCdev and got back the unlock_code.bin file
4) entered fastboot flash unlock token Unlock_code.bin in the terminal ..
This is supposed to trigger my phone to display the "Unlock Bootloader?" screen, as attached ... and this is not happening
I have all drivers installed properly and my phone has responded to the fastboot oem get_identifier_token command
but there is no screen displayed .. only the fastboot mode .
What should I do?
Appreciate any help you can give
Click to expand...
Click to collapse
This is really pain in ass. I am contacting both HTC and Google support for this. You can read it here
http://forum.xda-developers.com/showthread.php?t=2547894
Sent from my HTC One using Tapatalk
Thanks for your replies ..
I have to say that I now hate my phone .. I moved from IOS because I wanted the freedom of customizing my phone and installing ROMs and now I'm stuck
I thought a pure Google edition phone will be the least restrictive version of Android. .
I should have chosen the Sense 5.5 one ..
Hello.. how are ya devs
I've asked this last night numerously and ended up with headaches.. yes.
I accidentally wiped EVERYTHING from my htc one and I have S-ON so I basically can't flash a firmware.. So I spent the last night looking at my beautiful blank white screen.. How do I fix it please? I'd appreciate a help..
Quick Help (might work 4 you)
Hey buddy,
I got myself a M7 working again by letting it get set back to stock from a RUU.exe which fit to my phone.
It was S-On and with an UNlocked bootloader.
At first is to say that I cant provide any guarantee for the workability of my solution, neither will I take any responsibiliry in case you mess your mess up even more
But here is how I went on the case:
I just got myself this quick installer here to set up my PC for adb and fastboot commands!
Second you will need the HTC Drivers ("Solo Driver Installer) and a working USB Cable of course
After connecting Phone I started my Phone into bootloader and swiched to the "fastboot" mode! I used the Windows "CMD" command tool to find out which Baseband version i need, by typing fastboot devices and fastboot getvar all. The second command gives you the needed infomation about your Baseband!
After finding out, find your fitting RUU.exe right here and load that 1,6 GB file
At last all you need is to make sure that your bootloader is (RE-)LOCKED, because else the RUU.exe wont work!
A simple fastboot lock oem will do the thing! Afterwards your Phone should be able to get reflashed with the Stock ROM and stuff that comes by the RUU! NOTE: Unlocking your Bootloader requires a working OS as far as i know, and cant be done by another "Fastboot oem UNlock" command
This link is describing the same procedure in case you're unsure..
Greetings, a happy owner of a working HTC M7