Develop Bugs

EVO 4G Unroot Help

I've looked into other threads on unrooting and it doesn't seem like anybody has the same issue as me.
The evo I'm trying to unroot is using HBoot 2.10.0001 if that makes any difference. I've already got the phone to S-ON, but whenever I try and flash over the PC36IMG.zip, it says abort. I've tried many different PC36IMG.zip files and they have all failed. What do I do here? I need help asap.
Please & thanks.

Seandeezy said:
I've looked into other threads on unrooting and it doesn't seem like anybody has the same issue as me.
The evo I'm trying to unroot is using HBoot 2.10.0001 if that makes any difference. I've already got the phone to S-ON, but whenever I try and flash over the PC36IMG.zip, it says abort. I've tried many different PC36IMG.zip files and they have all failed. What do I do here? I need help asap.
Please & thanks.
Click to expand...
Click to collapse
You're flashing it in the bootloader, not recovery, correct?

No I'm flashing it through the clockworkmod recovery like I would a ROM.
If I'm supposed to be flashing it over in bootloader, I'm not really quite sure how to do that. When I go into bootloader, it always does a check on PC36IMG.zip, so should I just put the new on there and let it do that check?
Also, where can I find the matching PC36IMG.zip for my HBoot version.

you do not flash a pc36img.zip through recovery..you let the phone do it through hboot. but one thing real quick b4 you try that. What baseband radio is currently on your phone???

{ParanoiA} said:
you do not flash a pc36img.zip through recovery..you let the phone do it through hboot. but one thing real quick b4 you try that. What baseband radio is currently on your phone???
Click to expand...
Click to collapse
The baseband radio is currently on 2.15.00.11.19

Seandeezy said:
The baseband radio is currently on 2.15.00.11.19
Click to expand...
Click to collapse
So turn the phone off, hold vol+power til you see a white screen; when prompted, apply the update and reboot; you'll be on stock. As paranoia said, you flash the PC36IMG in the bootloader, not recovery. Make sure you flash the s-on zip in recovery first.

teh roxxorz said:
So turn the phone off, hold vol+power til you see a white screen; when prompted, apply the update and reboot; you'll be on stock. As paranoia said, you flash the PC36IMG in the bootloader, not recovery. Make sure you flash the s-on zip in recovery first.
Click to expand...
Click to collapse
Where can I get the PC36IMG.zip that matches my baseband radio or whatever because I've read that you need to find the one that matches what's being ran.

RIGHT HERE
why are you unrooting just wondering

{ParanoiA} said:
RIGHT HERE
why are you unrooting just wondering
Click to expand...
Click to collapse
Beat me to it.

{ParanoiA} said:
RIGHT HERE
why are you unrooting just wondering
Click to expand...
Click to collapse
I'm unrooting because my mom needs to take it into the sprint store due to some hardware problems. She took it in there rooted and they told her they couldn't do anything about it because it was rooted. So here I am, trying to unroot so she can take it in and most likely get a new one.

I have another question. I'm noticing this file downloading is a .exe. I'm running a Mac, hoping that doesn't make any difference. Am I just transferring this file over to the SD card? and then on the bootloader screen press.....?

oh **** my bad. forget that one then. Dowload THIS ONE and just delete everything off the name except PC36IMG and put on sd card

{ParanoiA} said:
oh **** my bad. forget that one then. Dowload THIS ONE and just delete everything off the name except PC36IMG and put on sd card
Click to expand...
Click to collapse
Then when I go into bootloader, it should automatically check the PC36IMG.zip file and update itself then right?

When I get into the bootloader, it just loads the files really quick. Doesn't give me an option to update anything. Just options fastboot, recovery, clear storage, simlock, hboot usb. Not sure what to do. I have the new PC36IMG.zip on the SDcard right now. Just unsure on what I'm supposed to be doing with it in bootloader since I'm not flashing it in recovery.

Pick fastboot. It will scan and ask if u wanna update. Pick yes n let it go
Remember thanks button
Sent From My Pocket

{ParanoiA} said:
Pick fastboot. It will scan and ask if u wanna update. Pick yes n let it go
Remember thanks button
Sent From My Pocket
Click to expand...
Click to collapse
Whenever I clicked on Fastboot, all it did was do a little scan and then went back to same menu. Didn't ask me for an update or anything.
I'll post a picture in a second of what I'm seeing on the Fastboot screen.

This is what I'm seeing on the Fastboot screen.
{
"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"
}

Rite...pick bootloader n it will scan n ask u to say yes. If it isn't finding it then it isn't named exactly PC36IMG.zip (not. zip.zip) or it isn't on the root of SD card (not inside any folders)
Sent From My Pocket

I need to do this to multiple phones because we are having similar issues. On another phone I've tried flashing the s-on tool and I can't for the life of me get the phone back to s-on. I keep getting an error:
"verifying system type...
E: unsupported radio version
E: Update failed .Check /sdcard/soff.log.
E: Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted"
Why is this?
Edit: I've also looked into this and people always ask what HBoot version others are using, I'm using 2.10 so the tool can work for me. I just don't know why it's aborting. :/ Please help.

Seandeezy said:
I need to do this to multiple phones because we are having similar issues. On another phone I've tried flashing the s-on tool and I can't for the life of me get the phone back to s-on. I keep getting an error:
"verifying system type...
E: unsupported radio version
E: Update failed .Check /sdcard/soff.log.
E: Error in /sdcard/unrevoked-forever-son.zip
(Status 42)
Installation aborted"
Why is this?
Edit: I've also looked into this and people always ask what HBoot version others are using, I'm using 2.10 so the tool can work for me. I just don't know why it's aborting. :/ Please help.
Click to expand...
Click to collapse
We ask for the HBoot and radio, but for the unrevoked-son (or soff), you need the correct radio for it to work.
It will not work with these three (made for Gingerbread) radios,
EVO_Radio_2.15.00.08.08, EVO_Radio_2.15.00.05.02, EVO_Radio_2.15.00.04.08

Can't install ROM or update

I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.

kosraeboy said:
I hope that someone can help me with this problem. Sorry it is such a long post, but I thought it might help with diagnosis if I wrote it all down.
I have an HTC One X with Android 4.02. It was purchased from Optus. I followed the process on the HTC web site to root and unlock the phone. Since that time I have never been able to update automatically. I contacted both Optus and HTC and was told that this was because of the root and, more or less, “bad luck!” I’ve tried to manually update the zip file with CWM but just get an error message and abort update.
From time to time, the phone would lag badly and run slower and slower. The only way that I could fix it was to backup all the apps and data using Titanium backup; uninstall all the apps; and then re-install them. Afterwards, all would be fine again for several months. A couple of months ago, it began to happen again and I uninstalled/reinstalled, but this time it didn’t help. Finally, after trying to figure out what to do, I did a system reset and then reinstalled everything and everything worked fine except that one of my apps (one I use all the time!) now will not work at all.
I decided that this might be because I needed to update to a newer version of Android. Unfortunately, when I tried to install CM 10.2, the installation failed. I thought that this might be because the Bootloader was too old (v. 0.95) but I read that if it was an AOSP Rom that I wouldn’t need to update the bootloader. So, I tried to flash Xenon, but again no luck. I’ve scoured the forums, but can’t seem to find anything that matches this issue.
The phone is definitely rooted. I’ve previously installed new Roms on my old HTC Desire, so I’m pretty sure I’m doing it right. However, I’m by no means a particularly sophisticated user and quite often the discussion in the forums is a bit esoteric for me.
Do I need to update the bootloader? If I do, then do I need to unroot the phone first then update then re-root?
Any ideas would be appreciated.
Click to expand...
Click to collapse
Hi
Can you give some details of the phone? CID?, international version?, S-On or off?, etc?
In short i think it is a good idea to update to a more recent bootloader. Then get yourself on to a newer ROM.
You might also want to consider twrp (big) as a new recovery.
This forum has lots of info.
Also take a look at www.onexroot.com
Thanks

The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
What is your error in CWM?

kosraeboy said:
The CID is OPTUS001.
The phone was purchased in Australia from the Optus network - I'm guessing then, that is an international.
The phone is S-on. From what I was reading when I was figuring out how to find whether it was On or Off, it seems like it needs to be Off to install any new Rom. I'd that right?
THanks for your help.
Click to expand...
Click to collapse
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.

Noobdead said:
What is your error in CWM?
Click to expand...
Click to collapse
Hopefully this image works.
{
"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"
}

grwalker said:
You can flash ROMs with S-ON. I fact its good to leave it as S-ON in case you flash the wrong firmware. Saved my bacon a few times.
Even if you bought it through Optus doesn't necessarily mean an international. Ca you post a screen shot of the boot loader screen. That will tell us.
Also an you find the CID number? There's some apps that can give you the the number. It looks like HTC-xyz. This will help in finding the right firmware.
good luck.
Click to expand...
Click to collapse
The CID Number is: OPTUS0001
Here is bootloader screen.

kosraeboy said:
The CID Number is: OPTUS0001
Here is bootloader screen.
Click to expand...
Click to collapse
Can you post the boot loader screen shot again please. The link didn't work

Trying again
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.

kosraeboy said:
I made a mistake with the CID. It is: OPTUS001
Hopefully this will work this time.
Click to expand...
Click to collapse
Nope, link still doesn't work. Use the attachments button when replying to attached the screenshot.
If that still doesn't work then let me know what the first three lines are when you are in fastboot mode. (Hold Vol down and power until you enter fastboot). The reason i want this info is to confirm you have the international version of HOX. If the second line contains the words "Endeavoru" then you have the international version, and we can then find the right ROM and recovery for you to use.
Also this is the link to download Hboot 1.36 for OPTUS001. http://d-h.st/users/ClydeB1/?fld_id=8110. Download this and keep it handy.
I am assuming that your bootloader is unlocked. First line tells you this. Did you use the site http://www.htcdev.com/bootloader/? Do you still have the unlock token?

Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version

kosraeboy said:
Here are the first 9 lines. Don't know why it doesn't work.
*** UNLOCKED ***
ENDEAVORU PVT SsiteHIP S-ON RL
HBOOT-0.95.0000
CPLD-None
MICROP-None
RADIO-None
eMMC-bootmode : disabled
CPU-bootmode : disabled
HW Secure boot : enabled
Unlocked with htcdev.com. I no longer have the token, but can I get it by logging into htcdev site?
I'll download the firmware.zip file.
Thanks
Click to expand...
Click to collapse
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks

grwalker said:
The unlock token usually arrives by email. Do you still have the email? If not go thru the process again and get the token. Then keep the token. You need it after you flash the firmware.zip (new HBOOT)
The question you might want to think about is what ROM are you planning to install? That suggests the custom recovery you need to install. For instance HOX international works well on Lollipop but you have to reformat the memory using twrp-big. A simple task that you can find on www.onexroot.com.
Once you answer the ROM question, the steps would be as follows. Instructions can be provided if needs be.
1. Flash custom recovery of your choice
2 Flash the firmware.zip (HBOOT)
3. Flash the ROM of your choise.
Or you can go down the path that Thant is suggesting. I did the Lollipop upgrade using Resurrection Remix ROM after doing steps 1 and 2.
Thanks
Click to expand...
Click to collapse
Step 1 must to be after step 2, because if he flash firmware after recovery will be with stock recovery and not be possible to flash rom with stock recovery and must to flash again custom recovery. But how I think he is not a good with android devices don't have good skil to flash the firmware by him self. I suggest to answare my question and then to see if we can find RUU

Thank you both. Sorry for the delay in responding. Family emergency and I've not had time. I'll follow up in a day or so.

Sorry for the delay
Thant said:
Man give me the result from command fastboot getvar version-main then I will tell you from where to download the RUU and you will download it and relock your bootloader and run it you are with low hboot and have chance to have RUU for your main version
Click to expand...
Click to collapse
Hi Thant:
The result is: version-main: 1.29.980.11

kosraeboy said:
Hi Thant:
The result is: version-main: 1.29.980.11
Click to expand...
Click to collapse
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:

Thant said:
OK Reloack with command fastboot oem lock your bootloader and run this RUU if you get error try to find nandroid backup I will try to find you stock recovery but first try to run the RUU and report back after that:fingers-crossed:
Click to expand...
Click to collapse
Thanks. I'll try it and let you know.

I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?

kosraeboy said:
I've tried running the RUU. When it asks me to verify the ROM image version I want to update, the "To:"version is the same as the "From:"version. They are both 1.28.980.11 Before I go ahead, is that correct? Shouldn't it be a different version of the ROM image?
Click to expand...
Click to collapse
GO and see if the RUU will finish if yes this is good if give you error we will see what will do.
Yes they are the same but if RUU finish you will be complete stock and then will update wia Wi-Fi stock rom to latest hboot. Don't forget to relock your bootloader
replay if rUU finish and dont forget to make nandroid backup when you install new rom after update to latest hboot for your carrier

Flashed custom ROM but SIM stopped working

Ok so I posted in another thread where I was trying to flash a custom but a few things went wrong but help has been slow there so I thought it may be better to post here.
I got MM through OTA updates, this was when my M9 was bootloader LOCKED, not custom recovery, everything stock. After I was on MM for a few days I used htcdev.com to unlock the bootloader, then I got TWRP 3.0.0 and then I got SuperSU 2.65 and installed it through TWRP. Before installing SuperSU I made a backup through TWRP of Boot, System and Data. I copied this backup to my computer as well. At this point this is the current information on the M9 (Look at 3 attached screenshots as well):
kernel: lk
product: htc_himaulatt
version: 1.0
version-main: 3.38.1500.2
boot-mode: download
version-baseband: 01.01_U11440801_96.01.51207G_F
version-bootloader: 1.0.0.0000
mid: 0PJA11000
cid: GLOBA001
So after creating the backup, I installed SuperSU 2.65, then booted up the phone, everythings fine. So I went back to TWRP and installed Android Revolution HD 20.0 (had it on an sd card) and used the wipe data option it gives before installing. So after a long time of optimizing apps the phone boots up and starts the setup. I got to entering google account information and it asked for 2 step verification which sends a code to my phone number, but I then noticed I had no signal and it said No Service so I couldn't sign in to Google and had to skip that. After the rest of the setup I popped out the SIM and put it back, still nothing (keep in mind the SIM is locked with a pin if that affects anything, but it never even asked for the pin).
Now I go to Accounts and try adding my google account but the phone gets stuck at checking info... and while i can use the rest of the phone there is no way for me to sign into any google account now because every attempt results in checking info loop. I tried to reboot the phone multiple times but that did nothing. Last thing to note is that when i went to Settings -> About, there was no IMEI number as well as other information about the phone was missing so something went wrong for sure.
After that I restored from the TWRP backup and its back to normal, SIM working, Google acc working, all that is good like it was before. So any suggestions on how to get ARHD 20 now? I noticed that since I'm on 3.38.1500.2 which is higher than the firmware that ARHD uses, maybe that is the problem since I'm essentially downgrading the firmware right? I read that you can't downgrade firmware unless you are S-off but my M9 is S-on. All help is appreciated
{
"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"
}

Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk

shivadow said:
Instead of twrp 3, use 2.9.0.1 and then flash supersu 2.65.
The problem lies with twrp. Supersu has its own issues so only 2.65!
ONLY TWRP 2.9.0.1 AND SUPERSU 2.65 FOR MM HTC M9! YOU WILL ENCOUNTER ISSUES OTHERWISE!
S-off is worth paying for too.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yea SuperSU 2.65 I understand but I heard 2.9.1.2 is quite stable? You don't agree?

Not tried it. I just flashed 2.9.0.1 and stuck with it because it boots. Beggars can't be choosers and a working phone is better than a broken one.
Sent from my HTC One M9 using Tapatalk

Just wanna update my situation as it is resolved and the solution: S-OFF
I was on 3.38 with twrp 3.0 and SuperSU 2.65 and flashing ARHD 20.0 (which is on 3.35) was messed up as my SIM card wasn't working and signing into Google account was not working.
I restored my nandroid backup, installed SuperSU 2.65 again and then bought S-OFF, which allowed me to change my cid to HTC__001 and mid to 0PJA10000. Next i flashed a nandroid that someone uploaded of 3.35.401.12 and once that was done I flashed ARHD 20.0 and boom its done. Basically from what I understand you can't flash ARHD 20.0 if the firmware you are on is lower (i failed to go from 3.38 to 3.35). Also my SKU was 1500 but ARHD is 401 so that might be a factor as well. So yea S-OFF is great

Future Note.
Always try to stick with the general update the ROM is based off of. The System partition in STOCK/CUSTOM roms have a firmware folder that have drivers and config files that are meant to be used with the firmware.zip originally in that update.
For example (not real sw numbers)
HTC releases an official update 3.40.1540.1
3.40.XXXX.X is generally the base while X.XX.1540.1 is any software mods made by carriers or specific region teams. Firmware Updates (Radio Baseband, TouchScreen Driver, etc) are released along side the actual Android/HTC software. These official ROMS have config files that are design around this new firmware. When developers here on XDA make custom roms they are in a weird XDA way a carrier (3.40.ARHD.1 etc). They modify the HTC rom and make it their own, but their roms are still based off that firmware update.
So if you start using a custom rom based off 3.40, but the last firmware your phone installed is 3.10. You will run into issues and they might be small (less battery life or cell signal) or pretty big. Your sim not working, or wifi, or any number of issues. Stick to ROMS based off the firmware you have on your phone. Or if youre S-OFF and want to take that ever present risk. Update your firmware to that newer version.

Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?

ig88b1 said:
Can you go into a little more detail? I am S-off and unlocked. I upgraded to the latest Tmobile MM and then flashed ARHD and got the sim error/no signal. you changed your CID and MID? where did you get the MM nandroid from?
Click to expand...
Click to collapse
Yea if you go to settings -> about -> software information it should say your firmware version. If your version is NOT 3.35 you'll get this problem, here are the nandroid files, you only need the 3.35 one but if I understand correctly restoring from this nandroid might make you lose all data. https://www.androidfilehost.com/?w=files&flid=48820
ALSO that nandroid is for 401 SKU which is HTC WWE, so if you're locked to tmobile i dont know how that'll affect you so dont just restore to that nandroid.
And yea i changed my CID and MID : (idk if you know but you need extra files on your pc to run the following commands from pc)
fastboot oem writecid HTC__001
fastboot oem writemid 0PJA10000
fastboot reboot
I did this right before the nandroid restore and everything turned out fine.

Awesome man thanks so much! that nandroid took care of it, couldn't find one.

ig88b1 said:
Awesome man thanks so much! that nandroid took care of it, couldn't find one.
Click to expand...
Click to collapse
Glad I could help

M8 - No recovery, cant flash recovery or original ruu

My case in details:
I just bought htc m8 from another user and on its back the model ID was "0P6B100 "
I found that it has twrp recovery installed and super cid "11111111", i also notice in boot loader that its model "m8_wlv" which i think it is different from the model id written on the back that shows a Europe version while "wlv" referes to Verizon version.
**I don't know the phone original CID
The info found on boot loader:
----
locked
official software
m8_wlv pvt
s-off
cid-11111111
hboot 3.16.0.0000
radio 0.89.xx.xxxx
-----
I notice that there is no update tab available and noticed from many posts later that this occur because of the super cid
there is also conflict in battery charging percentage.. if my charge is 5% and I plug the charger it stuck on same percentage tell i restart to know the correct percent i charge to....
so i take a decision to download the official ruu, to receive updates or charge normally without conflicts in percentage numbers
i download ruu referes to Verizon because of the "wlv" found in boot loader...
I installed it from the pc via fasboot, and it installed safely without any problem...
After installation i found that this isn't my official rom , and my sim is not supported , also updates are only allowed in cdma mode
back to the boot loader to found that " official software version" is gone and also there is no twrp recovery or even stock recovery, when i hit recovery from boot loader it switch to the red triangle and every time i must press up bottom and power to restart
i failed to flash new recovery or twrp recovery from pc or sd card , i always get errors for that...
also the adb i am using in fastboot folder in not working, when writing any adb commands it always says
"error: device <null> not found
I download the ul RUU in order to flash it back but i always get an error in fastboot about header checking or model id failed
now what shall i can do in order to restore my phone original stock rom ? i don't want custom roms or anything from this staff.. all what i want is restoring my original stock rom and stock recovery.
is this because the conflict in the model id or the "m8_wlv" shown in bootloader ?

My comments below in red font:
kedaaho said:
i also notice in boot loader that its model "m8_wlv" which i think it is different from the model id written on the back that shows a Europe version while "wlv" referes to Verizon version.
You need to go by what it says in bootloader, the back cover info is not reliable. The back cover was probably replaced to remove the Verizon logo. We've seen this a lot on these forums (back cover replaced to remove carrier logos).
I notice that there is no update tab available and noticed from many posts later that this occur because of the super cid
SuperCID does not affect OTA updates. However, I believe the VZN version will only get OTA updates when connected to the VZN network. So that is your main issue with getting official updates.
i download ruu referes to Verizon because of the "wlv" found in boot loader...
I installed it from the pc via fasboot, and it installed safely without any problem...
After installation i found that this isn't my official rom , and my sim is not supported
back to the boot loader to found that " official software version" is gone and also there is no twrp recovery or even stock recovery, when i hit recovery from boot loader it switch to the red triangle and every time i must press up bottom and power to restart
Where did you get this RUU, and what is the exact file name? Its obviously not an official RUU; and I suspect its an RUU cobbled together by devs before the official ZVN RUU was available; such as this, or similar. It indicates its rooted, which would explain the modified software flag.
i failed to flash new recovery or twrp recovery from pc or sd card , i always get errors for that...
also the adb i am using in fastboot folder in not working, when writing any adb commands it always says
"error: device <null> not found
You can't flash recovery with a locked bootloader; and that is what LOCKED on the bootloader screen indicates.
I download the ul RUU in order to flash it back but i always get an error in fastboot about header checking or model id failed
Its fortunate for you that RUU failed. Do NOT attempt to flash this, or any other version RUU besides VZN They is not compatible, and may even cause a permanent radio brick due to partition differences with the VZN version.
Click to expand...
Click to collapse
Do a fastboot getvar all, and post the results (delete IMEI and serial numbers before posting). Mostly, I want to see the current MID.

redpoint73 said:
Do a fastboot getvar all, and post the results (delete IMEI and serial numbers before posting). Mostly, I want to see the current MID.
Click to expand...
Click to collapse
**Many thanks redpoint73 for replying, here is the results of getvar all
{
"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"
}
** the updates are disabled now but also before I flash VZN rom they are not avilable, i dont know exactly what rom i was on before the VZN but it was different cause it don't has any of the VZN logos or VZN applications like in the one I have.
** The Ruu downloaded and installed name is M8_VZW "0P6BIMG.zip" and i download it from here:
http://forum.xda-developers.com/showthread.php?t=2727831

Official VZN RUUs are posted here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845

redpoint73 said:
Official VZN RUUs are posted here: http://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Click to expand...
Click to collapse
I already downloaded the marshmallow version "VZWM8_S_ON_6_0" from this link this morning but it fails to flash using fastboot:
** shall I try flashing using another method ?
**shall I download the official Hboot too from same link ?
**what versions for hboot and ruu shall be downloaded ? current firmware "4.4.2 " or the marshmallow that i want to upgrade too ?

My answers below in red font:
kedaaho said:
I already downloaded VZWM8_S_ON_6_0 from this link this morning but it fails to flash using fastboot
Try using htc_fastboot instead of the "generic" Google fastboot (disregard step #1 and renaming of the RUU.zip - just use the same RUU as before and you don't need to rename as long as you use the proper file name in the command): http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
** shall I try flashing using another method ? You can certainly try the SD card method. Really, its probably the most straightforward method, as long as you have an SD card.
**shall I download the official Hboot too from same link ? No, hboot alone won't help your issue.
**what versions for hboot and ruu shall be downloaded ? same to android version i have "4.4.2 "]or the marshmallow that i want to upgrade too ?
Since you are s-off, technically any (VZN M8) RUU version should work (with s-on, you can only run RUU with same or greater versions - no downgrading). Although MM may cause a separate error running the RUU, so maybe try 5.0.1.
Click to expand...
Click to collapse

Many thanks dear,
The marshmallow version "VZWM8_S_ON_6_0" installed successfully via SD card
now the recovery is working , official status on boot loader
But it still A VZN software: The splash logo, the VZN applications, the notification of sim not supported, no stock browser(only chrome), no FM radio and updates are only available in CDMA mode
I believe the first rom came with my phone is not a VZN cause it don't contain any of this staff and also it showed on boot loader as an official rom !! for a reason i don't know it's only problem was no software updates ... and that's why i uninstalled it.
*is there any clean unlocked international official roms supported for m8_wlv "0P6B20000"?
Thanks again and again

Again, my responses in red font below:
kedaaho said:
But it still A VZN software, the splash logo, the VZN applications, the notification of sim not supported and updates are only in CDMA mode
I believe the first rom came with my phone is not a VZN cause it don't contain any of this staff and also it showed on boot loader as an official rom !!
*is there any clean unlocked international official roms supported for m8_wlv "0P6B20000"?
I don't know of any official software for the VZN version that doesn't have the VZN bloat and branding.
for a reason i don't know it's only problem was no software updates ... and that's why i uninstalled it.
This phone won't update OTA unless its connected to VZN, I already stated that. There's nothing you can do, that can change that AFAIK.
*shall I install a custom rom?, what is the best custom stable rom runing marshmallow advice?
If you want to get rid of carrier bloat and branding, than a custom ROM is probably your best bet. I don't personally own the VZN version. But I can tell you, that you can only use ROMs that specifically support the VZN M8 (otherwise you have to flash the proper kernel for it to work on the VZN M8).
Click to expand...
Click to collapse

redpoint73 said:
You can't flash recovery with a locked bootloader; and that is what LOCKED on the bootloader screen indicates
Click to expand...
Click to collapse
Now I want to root my device in order to use "Battery calibration" tool and thats because:
My battery percentage drain quickly and stuck on 2% for more than half an hour, also it stuck and dont update while charging and to know the real battery percentage everytime i must reboot to bootloader screen and reboot again..
I tried many thinks like :
*full drain
*full charge
*wipe cash from recovery screen
*restore to factory from recovery screen
*reseting the cash method "volume up +volume down+ power key for 2 min"
And all failed, my last chance is to use the battery calibration tool and it requires rooting.

Error when attempting to flash back to stock (failed: -2, 19)

Hi All,
Because my phone is only capable of booting into 'download mode', and unable to boot into any custom ROM I made the decision to try and set it back to stock.
Towards this end I have attempted to install the 0PJAIMG.ZIP file (from here) by booting my phone with the file correctly named and on the root of an SD card. Doing this presents the message 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"
}
I then press on the Volume up key and after a short time I am presented with the error message below -
I thought that the error above may have been related to the bootloader being unlocked. I therefore proceeded to relock the bootloader (fastboot oem lock) and attempted to flash the ZIP file again. However once more I was met with the error screen above.
I am quite stuck now! Not only will my phone not boot into any custom ROMs, but it cannot reflash to stock either. I am thinking that not S-OFFing the phone before unlocking the bootloader and installing TWRP may have been my downfall.
At any rate if anybody can shine a light from the other end of the tunnel it will be grealy appreciated.
Kind Regards,
Davo

And what firmware were you on, is it the matching firmware you tried to flash?
What recovery do you currently have?
A bit more info about your phone would help people to help you.
Sent from my HTC 10 using XDA Labs

More information - TWRP version...
Hi squ89r97,
Thanks for your interest in my post. I can state that I am using TWRP v2.8.7.0. However I am uncertain of how to determine the firmware version. Perhaps the screen capture below will shed some light.
I have been considering mounting then extracting a firmware file from one of the bin files inside the RUU file (any thoughts on this approach are welcome!).
On a related note when I unzip the RUU file which I downloaded I do not get correct file sizes for the bin files.
Here is a screen capture when looking at the file using WinRAR -
Then once I extract the files in the archive I see the following -
I am using Windows 10 to perform the unzipping. Should I be looking at any earlier version of Windows or perhaps Linux (Ubuntu)?
Any further help here would be fantastic. I have made about four other posts concerning my phone in various threads, and at the moment I am quite concerned that I am stuck with a 'very sexy paper weight'!
I have flashed ROMs onto many HTC devices before (HTC Sensation, HTC One X, HTC One XL, HTC Velocity) and not been confronted with this issue.
Kind Regards,
Davo

The custom roms don't boot because your firmware is too old. You need firmware 3.x for most of the current versions of the custom roms.
Your firmware is stated in the line with OS at the beginning (2.9.841.5). You can't use the RUU you linked in your first post since with S-ON you can only flash RUUs with the same or a higher firmware version than your phone. Besides winrar isn't able to handle RUUs correctly if they're encrypted (which are almost all of the M9 RUUs). You need 7-zip and the "right-click > open > #" method. Nevertheless it would be easier to use a tool like the one presented in this thread: http://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928
If you're not able to find a RUU you will need to either flash an older version of a custom rom (viperone m9 3.x for example) and then get S-OFF via sunshine to be able to downgrade your phone with the RUU from your first post or you search for a TWRP backup for your current firmware and follow the instructions in my signature (it's in the google sheet) or you use llabtoofer's RUU service to get back to stock (you can find it easily with google or if you read page one of my sheet). However after you installed the latest 3.x firmware on your phone you should follow the instructions "make your own backup" which can be found in my google sheet so that you're able to return to stock without much hassle the next time.
Sent from my HTC One S using XDA Labs

Hi Flippy498,
Thank you very much for your insightful response. I am going to start by installing an older version of ViperOne ROM. Will then (hopefully) S-OFF using the Sunshine apk.
I feel like there may be a 'light at the end of the tunnel'.
Cheers
Davo

I have successfully installed ViperOneM9 version 2.3.0. Will now wait until pay day before using the Sunshine S-OFF method. Then plan to return to stock, followed by an OTA to Marshmallow firmware, and finally installing the newest version of Viper!

Hi Flippy498,
I am now S-OFF (pay day was yesterday...yippy!). Last night I tried to use the RUU from my original post (by putting it [correctly named] on the root of my SD Card), onto the phone. I booted into 'Download mode' and followed the prompts...everything appeared to work fine. However when I booted the phone it went straight back into the Viper ROM that I had installed earlier. Furthermore I checked the firmware version through settings, and unfortunately nothing appeared to change.
Should I try the RUU using fastboot, or am I 'barking up a tree that isn't there' (as a Tibertan monk once said)?
Any further help would be greatly appreciated.
Kind Regards,
Davo

HOLD THE PRESS!
Just booted into 'Download mode' on my phone again (Vol Down + Power), and noticed that a couple of extra things were installing (had only hoped to enter Bootloader!). Once they finished I rebooted again...and...stock ROM (complete with Telstra icons) is installed again!!! Now for OTA updates to Marshmallow (preferably through Telstra!)...
Then...eventually onto the newest version of Viper ROM!

Sorry, I didn't have the time to answer. A RUU always only flashes some partitions and then reboots before it flashes the rest. On earlier firmware versions the M9 rebooted to download mode automatically. Don't ask me why HTC changed that behavior so that the phone now reboots to the (old) system instead.
Sent from my HTC One M9 using XDA Labs