Develop Bugs

Problems updating to 2.29.405.2

Hello all,
I tried to update to 2.29.405.2.
My Desire is rooted with 2.10.405.2 ROM (the original one).
I downloaded the update by manually checking for an update(via Wifi), ran it, and when the mobile rebooted I got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I clicked the power button and got the recovery menu and beneath that it said:
Code:
ClockworkMod Recovery v.2.5.0.7
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify the whole-file signature
E:signature verification failed
Installation aborted.
What should I do?
PS: This is the first update I am installing..I 'm new to anroid systems.
Thank you for your time!

If you update a rooted ROM there is a good chance you will end up with problems such as boot loop.
Signature verification failed because you are trying to apply an update to a modified ROM. You can turn it off and apply it but it's not recommended as said already.

Then what should I do?

pspuser007 said:
Then what should I do?
Click to expand...
Click to collapse
Update using Gold Card, but first use search button

or...
just get the RUU from shipped roms and run that...

First you would not lose much from not updating to 2.29, the only thing that is worth it is for the new radio, but if you are okay now, I don't think there is any reason to update.
If you want to do it, nevertheless, you should first unroot.
If your original ROM was 2.10.405.2 ,in other words, if you are not branded then you would not need to use a goldcard.

I just read you reply, 3722.
Well, I am thinking about it because of these:
http://forum.xda-developers.com/showpost.php?p=9808553&postcount=15
What should I do?
*Thank you all for the replies!

First tell us whether you are branded.
If you are you couldn't flash 2.10.405.2 version without a goldcard, and you said that you are on that version with root.
So either you have already made a goldcard or you are not branded.

i think 2.10.405.2 is an unbranded WWE rom.
the link to download 2.29.405.2 is below:
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
all you need to do is download this and after you've put your phone into fastbootand connected it to your PC , run the .exe.
this will get you to 2.29.405.2 but your phone will be unrooted and wiped so your contacts / apps etc. should be backed up.
you can then root again if needed.
HTH

just confirmation - 2.10.405.2 is unbranded

I am unbranded because I haven't used a goldcard to root my desire.
I 've downloaded the RUU.
Ran it, and when I got the screen that informs me about the progress and at the phone I got a black screen with silver HTC letters.
The RUU progress bar windows closed and gave me a message about checking that the phone is connected to the USB.
I disconnected the USB and saw the fastboot screen with only option RUU.
Plugged the usb cord again, and got the black screen with silver HTC letters.
Nothing happened.
So I closed the RUU.
Now what should I do with the device?
Turn off by removing the battery?

ok, can you put your phone into fastboot while not connected to the PC (back & power). you should see fastboot in a red box.
then connect to the PC, this should now change to fastboot USB.
if this is the case, try running the RUU at this point.
oh, and try not to be too hasty unplugging or taking the battery out

I just ran the RUU again and it's upgrading now.
Will reply, If I get any problems!
Thanks a lot mikep and all the other members that replied!

no problem, it will probs take approx 10 mins.
i hope you've got your contacts/apps backed up?
if you've used titanium, you will have to root again to gain access to them (Unrevoked).
hope it goes well - let us know

It went smoothly
I 've backed up with Titanium.
I have to re-root.
Will do it after I return home (in 3 hours).
Will reply here if anything occurs!
Thanks a lot again!

Happy Days!!!

Everything OK! I rooted & restored the backup.

Good stuff! Make sure you make another nand backup now you're on the newer rom so you have one to fall back to
Sent from my HTC Desire using XDA App

When you say another nand backup?
What is this "nand backup"? :-S (sorry I don't know much)
You mean backing up my whole system+data so that I can restore them if I try a custom ROM that I don't like?

Yep, correct.
Make a backup thru the clockworkmod recovery or thru rom manager.
You will then always be able to get back to the position you're at now.
Hope this makes sense
Sent from my HTC Desire using XDA App

Superuser disabled by default???

So my old g2 broke and I just got a new one. I rooted with the non-adb method. Now I've flashed miui and I'm getting the following error. See photo. I'm unable to use root required stuff and can't get into recovery. I can get into hboot however. Please help!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC Desire Z using XDA App

Do you have the superuser app in your launcher? have you actually opened it and given rights to things?

Well, I've installed superuser, opened it. It has app list, log list, which are both empty and a settings page. I opened the settings page to see if there was something to enable permissions, there wasn't. I've decided to go into hboot, do a factory reset. It took me into recovery and I wiped data/cache/dalvik. I tried installing a new rom, got an error status 1. Did some research, they said to run a scandisk, I did, it didn't change anything. So now I'm trying to root again using the ADB method since I don't have a rom on my phone and it fails to install a new one. So I'm stuck in recovery. ffs. lol. Now I'm having trouble with CMD commands as the guide says to write specific commands, which I write and it says they don't exist. Anyone willing to add me via MSN or yahoo and help me through this? I would GREATLY appreciate it.

I'll elaborate to exactly what I did ---- (My phone came with 2.2 with the option to OTA 2.3.3, I did NOT upgrade to 2.3.3)
Received my phone today in the mail. Loaded it up. Went directly to the non-adb root page here on xda. Downloaded the files, followed the directions exactly. Downloaded clockworkmod, flashed 5.0.2.0 recovery. Downloaded MIUI via clockworkmod. Rebooted my phone into recovery. Wiped data/cache/dalvik. Installed MIUI. Booted into MIUI. Downloaded Titanium backup to recover some files from my old phone(sd card), got that error saying I wasn't rooted. Tried downloading superuser, that didn't fix it. Downloaded busybox, and busybox wouldn't install because it said I wasn't rooted.
Rebooted into recovery, got stuck at white HTC logo screen. Removed battery. Restarted phone into hboot. Clicked factory reset which restarted the phone into recovery. Inside recovery, I wiped data/cache/dalvik again. Tried installing a new rom, got error status 1.
From here, I attempted to root via ADB method. Followed all the steps but HTCsync couldn't connect to my phone. Although it "adb devices" command recognized my phone and most of the adb commands were working (it seemed). I rebooted my phone into recovery after playing on adb for about an hour. I tried reinstalling that new rom and it installed! Well...sort of. Instead of getting an error, it said installed, but it was almost instantaneous. I knew something had fudged up. So I rebooted my phone anyway just to see if it had taken the new rom. It didn't.
I rebooted back into recovery, cleared data/cache/dalvik and reinstalled MIUI successfully. Now I'm in MIUI and it says there's no root. I tried connecting HTCSync via MIUI, it failed. I'm unable to use HTCSync with MIUI? Anyway, now I'm stuck and I have NO idea what to try next. Been at this for a few hours now and can't seem to get anyone to nudge me in the right direction. Thanks for reading.

Does your bootloader screen actually indicate that the phone is S-OFF ? It seems like you didn't complete a full root process and you're stuck half way so to speak.

I thought that's what happened. So what I did was, went ahead and put the stock rom back on my phone. I downloaded the PC10IMG and updated via bootloader. Now I'm back on 2.2. I can't get HTCSync to connect so ADB method is out of the question. Some version information, not sure if it's useful to you, but I still want to root my phone, just don't think that method works for me, not sure why.
Android Version: 2.2
Baseband version: 12.22.60.09bU_26---blah blah
Kernel: 2.6.32.17
Build number 1.19.531.1 CL---blah blah
Is that sufficient info for a pro dev to assist me? I've disabled my firewall aswell as windows defender to see if that would allow me to connect through HTCSync, but that didn't help. So now I have to find a new method of rooting my phone..

Problem solved. Started back from stock and tried the same method again but with different recovery. Viola! Success. Thanks anyway.
Sent from my HTC Vision using Tapatalk

Need Help, No Service, after installing CyanogenMOD 10.1

No Service, after installing CyanogenMOD 10.1
Tried following the steps outlined in this post but do not feel totally comfortable in saying I did it correctly as that post is not specifically for Incredible 2's and the instructions are not very clear.
I can obviously follow instructions, as I have gotten this far issue free. But his foggy instructions and the lack of files specific to this issue for Dinc2's make fixing this a little tricky.
Has anyone else seen this issue on a dinc2?

No other users have had loss of Cell service (No reception, zero bars) from Cyanogenmod 10.1?
Or said differently, Borked Radio's...

Not that I know of
One ROM @ a time....VIA ELECTRICITY

Last night I did a Factory restore from within Clockwork, then downloaded an un-rooted stock rom from this site (very bottom rom) dropped it on the root of the sd card and renamed it to PG32IMG.zip and rebooted to install the stock rom. (This will NOT remove s-off, see results of the reinstall picture below)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After this the phone rebooted a few times and I figured it was just not working so I went to bed, then woke up did some stuff and then went to supper with the family. after we got home I picked up the phone and noticed that the phone had reception bars, so I did *228 and it started to initiate the activation and it actually started the process, but I hung up.
I then proceeded to re install clockwork recovery. after this was installed, the phone just boots over and over, did this for about 15 minutes before I pulled the battery and re initiated a Factory Reset from within clockwork. after rebooting from this factory reset, there was no reception again. so I then pulled, from the vzw stock zip, the file named recovery_signed.img and placed it into the same directory as my adb & fastboot files, pulled the battery from the phone, rebooted into hboot, chose fastboot and ran:
Code:
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
After boot loader rebooted, I selected bootloader to get back to Fastboot, chose recovery, rebooted into phone which was once again re-boot looping. Will try more after work tomorrow, too tired right now.

Last night, cleared the caches out several times each, then factory restored twice in a row, then installed clockworkmod, reinstalled the "andyBONESTOCK_5.10.605.9" image, then, re installed the radio image "6.01.605.05 OTA 1.09.01.0312" twice in a row. Still had no service.....
Went to work, got home and the friggin thing has service.... wtf
So I reboot the phone and now it has no service..... Anyone have any ideas?

Problems solved. Must have had a corrupted radio file. Found a different source, installed, all is good.

which radio, from where, link?
Akinraze said:
Problems solved. Must have had a corrupted radio file. Found a different source, installed, all is good.
Click to expand...
Click to collapse
I tried the .320 radio here: http://forum.xda-developers.com/showthread.php?t=1134451
and it bricked my phone, HBOOT (revolution), said invalid, then installed it and the phone was bricked. Took forever to recover even HBOOT and then revolution and that was reset plus Android SDK, adb.
Used ChillyBean's 10.1 , May 9 13 build date, plus Kernel from here:
http://forum.xda-developers.com/showthread.php?t=2315062
But the audio for phone calls can give no sound at all. Bugs seem to be in services, like one audio driver doesn't release the audio, or turn it off so it cannot be turned on when the phone call is made, or some audio routing problem from the call (radio) to the audio HW (any, speaker, mic, bluetooth, headset).
I can tell it is this because if I turn audio on/off before the phone call enough times I get back the actual call in progress audio.
I'm using 0.312 but the last thing to try is the radios but the ones at the first link are at minimum corrupted.
I also don't get the overall source tree for CM10.1, I thought you had to have a build for specific HW vs. taking just the nightly? Is there a build tree for DINC2 from the CM10.1 nightlies?
The current no sound during phone call is a real bug and not specific to my HW, something isn't releasing or turning on or routing the audio via the 3GGP/CDMA call path. Dunno the actual path in HW for the voice communications.
This should be in dev. thread but the system won't let me post due to newbie status.

Well, I eventually got only a few roms to work without issues to my liking.
The one I am using right now, is the one I first got my phone back up running issue free, that is Team Venom Presents ViperINC 1.3.1 Sense4.1...
The radio inside the ics firmware listed at the very top of the 1st post for Team Venom Presents ViperINC 1.3.1 Sense4.1 is where you get the ics firmware.
I am almost 100% sure the Android Harpoon Repository has the radio I am using now as well as several other roms and kernals, all of which have had NO ISSUES for all that I have tried.
Hope you get things working correctly. and make SURE, to correctly get the radio and or Kernal files installed correctly, you simply rename the firmware ZIP file, that has all the .IMG files inside, to be named PG32IMG.zip and place it in the ROOT of your sd card and reboot to it. do this AFTER you have installed the rom. And YES, it takes some time to get things working corectly immediately after installing the firmware PG32IMG.zip file, so BE PATIENT, go take a poop, eat a meal, get some poontang. when you come back, all should be good.
And though it may seem stupid... Put the back cover on your phone, so your antenna connections are complete.
The when your all done, things show promise, connect your phone to your PC and open windows explrer and delete that PG32IMG.zip so it doesnt repeatedly install over and over.

Thanks Akinraze
Akinraze said:
Well, I eventually got only a few roms to work without issues to my liking.
The one I am using right now, is the one I first got my phone back up running issue free, that is Team Venom Presents ViperINC 1.3.1 Sense4.1...
The radio inside the ics firmware listed at the very top of the 1st post for Team Venom Presents ViperINC 1.3.1 Sense4.1 is where you get the ics firmware.
I am almost 100% sure the Android Harpoon Repository has the radio I am using now as well as several other roms and kernals, all of which have had NO ISSUES for all that I have tried.
Hope you get things working correctly. and make SURE, to correctly get the radio and or Kernal files installed correctly, you simply rename the firmware ZIP file, that has all the .IMG files inside, to be named PG32IMG.zip and place it in the ROOT of your sd card and reboot to it. do this AFTER you have installed the rom. And YES, it takes some time to get things working corectly immediately after installing the firmware PG32IMG.zip file, so BE PATIENT, go take a poop, eat a meal, get some poontang. when you come back, all should be good.
And though it may seem stupid... Put the back cover on your phone, so your antenna connections are complete.
The when your all done, things show promise, connect your phone to your PC and open windows explrer and delete that PG32IMG.zip so it doesnt repeatedly install over and over.
Click to expand...
Click to collapse
Your post helped me so much. I've been working on the phone all day because it said there was no service. Turns out since I was working on it without the back, since I needed to go into fastboot so many times, the antenna wasn't completed. The signal in my house turns out to be just weak enough for it to barely show up with the back on. Thanks again.

Found my own fix
http://teamuscellular.com/Forum/topic/7584-cyanogen-no-service-fix/

Video and/or step by step firmware upgrade instructions available?

So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.

guyverzero said:
So let me explain the scenario; I have a T-Mobile M9 that's S-Off, running Venom, and wanted to update the firmware from 1.32 to 2.7. I had done this in late July and got the success, and the firmware was running fine, but eventually the phone decided to just shut off on me, and the only way to turn it back on was via forced reboot. For the two weeks after that I had tried just about every method I read on Sneakyghost's post on the subject (I did an RUU, changed to superCID and flashed 2.10, did the full wipe and no wipe firmware) and every single time if I updated to anything newer than what was on my M9 originally it would, inevitably, do that thing where it became unresponsive after a while.
Since this seems to be a problem that only I'm having, I assume it's something I have to be doing wrong. With that in mind, is there any sort of video that has been made or really, really simple and thorough step by step instructions that could guide me through the process in a detailed way? I hate that I have to ask this, but I feel like I've done my homework and tried several different methods, and all of them have failed. I have HTC sync installed, I've tried on two different computers, I've done everything. I even flashed back 1.32 in the exact same way that I flashed 2.7, and as soon as I put it back to the old one it immediately solves the problem. Without fail putting the new firmware on has made my phone do this at least once within two days of installing, and then multiple times after that (I must've tried this about four or five separate times over three weeks). The obvious problem here is that the phone is completely unresponsive, which means that if it does this overnight my alarm doesn't work. Not to mention the missed calls and annoyances that occur when it happens throughout the day.
I just want to be able to experience the new firmware. Because right now I still have to deal with a (relatively) crappy camera experience and a phone that overheats constantly. I'm also really worried that when the M update comes out it may force me to have a newer firmware, and if I can't do it correctly I'll be out of luck.
So if anyone could help it'd be so very appreciated, either by telling me something I could have done wrong (I flashed the firmware via fastboot method both over viper and later over a stock Sense build). I also have the newest radio, so I literally have no idea what I could be doing wrong at this point, but I hope someone does. Again, thanks in advance.
Click to expand...
Click to collapse
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine

clsA said:
instructions are here >> http://forum.xda-developers.com/att-one-m9/general/att-developer-edition-ruu-how-to-t3086948
use the sdcard method and the DE RUU or the T-mobile RUU and your phone should work fine
Click to expand...
Click to collapse
Would restoring my nandroid after flashing that RUU cause anything to go wrong?

guyverzero said:
Would restoring my nandroid after flashing that RUU cause anything to go wrong?
Click to expand...
Click to collapse
it's always better to start fresh after the RUU

Nope, it's doing the same thing again. This is my GSam from last night.
Now, let me stress that I did everything clean. RUU, did a clean setup, clean venom flash, etc. I didn't restore any settings. I don't know what to do, as the phone is completely normal under 1.32. Oh and I flash 1.32 in the same exact way I do 2.7 as well, there's no difference
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my HTC One M9 using Tapatalk

Potentially bricked? Sprint M9 unable to take OTA

Good evening folks. I am in desperate need of expert advice on this subject.
I imagine that other users have encountered this issue, and this thread may be useful in the future to the assistance of others.
I am rooted, and S-off (as of yesterday). Yesterday, I had TWRP 2.8.7 installed, with stock sense (and sprint bloatware), running android 5.0.1, on firmware 2.11.651.19
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***
*** UNLOCKED ***
htc_himawhl PVT-SOFF
CID-SPCS_001
LK-1.0.0.0000
[email protected]
OpenSDP-15.6.1.00522.8994_1026
OS-3.41.651.4
Feb 3 2013,13:49:48(695981)
Let me describe my problem before I get into detail.
It started when I got my M9, I got it from Sprint, and instantly wanted to root it and install Cyanogenmod 13 on it.
To my mistake, I rooted the phone BEFORE I did the OTA update to Android 6.0
As we know, this is a block based system, and this introduces many difficulties.
I had been running TWRP 2.8.7, and stock sense with all my pre-loaded Sprint crap. I was unable to install cyanogenmod 13 or anything.
This led to much frustration, research, and pain as I browsed countless threads on the XDA forums, downloading many items, hoping they would fix my issue.
Now, for my issues.
The HTC RUU for my phone has never worked, and I was constantly met with ERROR 155. I attempted to re-lock the bootloader, but this made no difference.
Often, when I type in adb devices into the command prompt, I am prompted with something like "you are using a different version than the server... Daemon started.. Then devices: and then nothing. This is what I usually get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It is obvious to me that if no device is detected, then no work may be done on the phone.
Other times, the phone will recognize, but it seems as if there is no effect on what I am trying to do.
Last night, I paid sunshine $25 to S-off my phone, hoping that it would help me. While the S-off process was extremely easy with this service, my problems are not remedied.
I saw that to restore my phone to 100% stock, that I must complete a RUU with my device, renamed to 0PJAIMG.img, and move it to the SD card.
When I did this, I was still running Stock sence, and was able to move files to my SD card/External SD card.
I went into the bootloader and the phone recognized that I had a "0PJAIMG.img" file on my phone, but I used the wrong file. I used a 75mb file with the firmware, but not all of the sprint things with sense installed. I assumed that since this was the latest firmware, it would allow me to keep Sense and my files, and allow me to take the OTA update to the latest android version
Here are images with information to the INCORRECT "0PJAIMG.img" (that I had renamed from this screenshot) I installed on my phone using the bootloader.
You can see the CORRECT file at about 2GB, and the incorrect file at 75mb.
For reference, Here is what is included in the 75mb file.
Now, I am unable to connect my phone to adb, as it shows up as in the pictures.
I have no recovery installed, so the Stock HTC (and very basic) recovery is there.
I am continuously prompted to install the INCORRECT 0PJAIMG.img that I placed on my phone, and I have no way to remove it as I know.
When I boot normally, I see the HTC One logo, and then a black screen. The screen is still on, but completely black. There is no way to exit this, other than pressing all buttons for 5+ seconds.
I do have the correct 0PJAIMG.img (2gb file), but I have no way of switching these two files, since I cannot connect.
I cannot install TWRP due to no devices showing up in the ADB interface.
When I plug my phone into my computer, I do get the "connected" noise from windows.
Please let me know if I can be more specific. I am going on a trip soon, and will take whatever lengths to get my phone working again.
I have read all relevant threads that I know of, so please avoid re-directing me to another page unless you think I have perhaps missed something.
My end-goal is to have a fully functional HTC M9 with Cyanogenmod 13 snapshot installed. I am on sprint, so I am unsure if I can even use Cyanogenmod. My alternative preference would be the D-Boyz mod to sense.

UPDATE:
I am able to install TWRP 2.8.7.1, and play with that. It seems that when restoring from my old backups, I have the same firmware and OS.
Only now, my radio is bricked.
I have attempted to re-create this, after many painstaking "optimizing apps" runs.
I am currently in a "android is starting"... process.
I will keep this thread updated with information as I progress. I hypothesize that my radio will still be broken.
I am absolutley at my wit's end with this device. I should have never upgraded from the HTC M8. I miss you baby.
I am tempted to take my phone back to sprint. I paid for the S-Off though, and would like to avoid this if possible.
All I want is android 6.0 and CG13.... I'm sick of being annoyed by the "system update is available" notification constantly.
*** STILL UNSOLVED*** At first, I was prompted to do a system update (1 of 2), in order to prepare my device for android 6.0. Upon download completion of the first update, and when attempting to install, I am brought back to HBOOT, and the update is nowhere in sight, even when rebooted.
This is a constant loop, and always brings me back to HBOOT.
This is what I have been trying to figure out, and it has got me in an enormous mess ***

Solved by flashing the ZIP of the RUU for the latest version, placing it on the base of the Phone storage, and naming it "0PJAIMG.zip"