Develop Bugs

[Q] JB OTA update fails on rooted Vodafone One X

Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.

TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.

nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.

Just flash the RUU, update OTA and reroot.

Alright, will do and I'll let you know how it goes. Thanks

Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex

prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !

prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.

And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !

Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level

prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !

MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...

Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:

prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.

MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm

The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense

MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!

dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.

Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !

That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?

[Q] Stuck on Bootscreen, black boot loader, bricked?

Hey Guys,
my HTC One M8 ran on GPE 4.4.3, but today came an OTA update, which I wanted to install.
So I clicked install and my phone restarted to TWRP and the update wasn't installed.
Then I found this tutorial and tried it.
http: / / htc-one.wonderhowto.com/how-to/update-your-rooted-google-play-edition-htc-one-4-4-3-without-losing-any-data-0155404/
After flashing the OTA my boot loader menu turned black (image) and i wasn't able to install any Roms, also my phone sucks on boot screen.
Image: http: / / files.tobii5.de/assets/files/1/htc.png
Is it bricked?
I don't know what to do, please help me

Help
Please help me

It's certainly not bricked if you can access the boot loader.
Which recovery have you got installed now?

ashyx said:
It's certainly not bricked if you can access the boot loader.
Which recovery have you got installed now?
Click to expand...
Click to collapse
I use TWRP 2.7.1.0 and here is a screenshot of the error, showed while trying to flash a rom
http: / / files.tobii5.de/assets/files/1/twrp_error.JPG

It was a GPE OTA? Reflash a full GPE ROM

Sir-Fix-a-Lot said:
It was a GPE OTA? Reflash a full GPE ROM
Click to expand...
Click to collapse
The device is an regular "sense-device", but i flashed a GPE Rom, and after i wanted to flash the GPE 4.4.4 OTA update, it crashed.
And the screenshot of my last post was taken, when i tried to flash the GPE Rom again.

Tobii5 said:
The device is an regular "sense-device", but i flashed a GPE Rom, and after i wanted to flash the GPE 4.4.4 OTA update, it crashed.
And the screenshot of my last post was taken, when i tried to flash the GPE Rom again.
Click to expand...
Click to collapse
Could you try a different ROM please? I would recommend SlimKat, and going from there if you want to change.

Sir-Fix-a-Lot said:
Could you try a different ROM please? I would recommend SlimKat, and going from there if you want to change.
Click to expand...
Click to collapse
I think this wouldn't change anything, because i also can't restore a sense backup, i've made after rooting my phone.
But i wonder, why my boot loader menu changed its background to black. I guess, i have to refresh the stock boot loader, but i don't know how to do that.

Tobii5 said:
I think this wouldn't change anything, because i also can't restore a sense backup, i've made after rooting my phone.
But i wonder, why my boot loader menu changed its background to black. I guess, i have to refresh the stock boot loader, but i don't know how to do that.
Click to expand...
Click to collapse
At any point did you do the GPE conversion?

im having the same problem also. I have no OS. I have a rom on my mem but it wont flash and when i boot up my device it shows a unlocked lock that wasnt there before

I'm sorry i accidentally deleted your reply but everything seems to be working. I reflashed TWRP. Im going to flash a rom and see if it works. Thanks alot for your help.

xxnatanxx said:
I'm sorry i accidentally deleted your reply but everything seems to be working. I reflashed TWRP. Im going to flash a rom and see if it works. Thanks alot for your help.
Click to expand...
Click to collapse
This a different thread, my reply is in your thread

Sir-Fix-a-Lot said:
This a different thread, my reply is in your thread
Click to expand...
Click to collapse
i have so many tabs open but thanks tho.

My Phone showes a unlockt icon too.
I have tried to reflash my recovery, but nothing changed

Ok, my phone is working again, i just flashed an RUU of GPE

Stuck in boot screen

I unlocked my bootloader, installed custom recovery and rooted my phone so that I can install custom ROMS.
However, when I install a custom rom phone does not boot. It will get stuck on the HTC logo screen. I tried Android Revolution, InsertCoin and SkyDragon roms with same result.
I also tried to flash boot.img via fastboot with no joy.
I have S-ON (I tried to turn S-off but that attempt failed as well)
Can somebody please help me before I bust this phone up?

sti-06 said:
I unlocked my bootloader, installed custom recovery and rooted my phone so that I can install custom ROMS.
However, when I install a custom rom phone does not boot. It will get stuck on the HTC logo screen. I tried Android Revolution, InsertCoin and SkyDragon roms with same result.
I also tried to flash boot.img via fastboot with no joy.
I have S-ON (I tried to turn S-off but that attempt failed as well)
Can somebody please help me before I bust this phone up?
Click to expand...
Click to collapse
I know this definitely happens with Android Revolution, but if you leave it alone for long enough, it will boot. I am running SkyDragon now, and it seems to work just fine. Even though I am S-Off'd, it should still work for you since you have an unlocked bootloader. Can you post a screenshot of your phone in bootloader mode?

It might be because of your firmware. Do you happen to be on Verizon?

MrKhozam said:
I know this definitely happens with Android Revolution, but if you leave it alone for long enough, it will boot. I am running SkyDragon now, and it seems to work just fine. Even though I am S-Off'd, it should still work for you since you have an unlocked bootloader. Can you post a screenshot of your phone in bootloader mode?
Click to expand...
Click to collapse
You are right. I just found out that I was not waiting long enough for it to boot. However, everytime I restart the phone it takes almost 10 minutes for phone to boot but I shut it down and start, it would start.
Now, I dont cannot get root on SkyDragon. SuperSU says "The SU binary needs to be updated. Continue?" I would hit continue and hit "normal". I get "Installation Failed! Please reboot and try again" error message....Ugh this has been very frustrating...

sti-06 said:
You are right. I just found out that I was not waiting long enough for it to boot. However, everytime I restart the phone it takes almost 10 minutes for phone to boot but I shut it down and start, it would start.
Now, I dont cannot get root on SkyDragon. SuperSU says "The SU binary needs to be updated. Continue?" I would hit continue and hit "normal". I get "Installation Failed! Please reboot and try again" error message....Ugh this has been very frustrating...
Click to expand...
Click to collapse
I had the EXACT same thing happen. How I resolved the SuperSU problem: flash the SuperSU 1.94 zip in recovery. How I solved the slow as hell boot problem: go to Settings > Power and disable Fast Boot. Good luck!

babtron said:
It might be because of your firmware. Do you happen to be on Verizon?
Click to expand...
Click to collapse
I am on ATT

MrKhozam said:
I had the EXACT same thing happen. How I resolved the SuperSU problem: flash the SuperSU 1.94 zip in recovery. How I solved the slow as hell boot problem: go to Settings > Power and disable Fast Boot. Good luck!
Click to expand...
Click to collapse
Excellent! Flashing the SuperSU has resolved the root issue. Thank you!!
But the slow boot is still there even though I unchecked fast boot.

Check your firmware version.

babtron said:
Check your firmware version.
Click to expand...
Click to collapse
+1

babtron said:
Check your firmware version.
Click to expand...
Click to collapse
MrKhozam said:
+1
Click to expand...
Click to collapse
If the firmware version = build number then it is 2.22.1540.4

sti-06 said:
If the firmware version = build number then it is 2.22.1540.4
Click to expand...
Click to collapse
I had the same problem.. what fixed it for me was getting on my stock ROM and doing HTC's OTA update to 4.4.3. This updates your firmware and make it compatible with newer firmware ROMs (such as Android Revolution) To do the OTa if you don't know how I recommend restoring a stock nandroid , flash the stock recovery and you should be ggod to go.

ILIVE4HEAD said:
I had the same problem.. what fixed it for me was getting on my stock ROM and doing HTC's OTA update to 4.4.3. This updates your firmware and make it compatible with newer firmware ROMs (such as Android Revolution) To do the OTa if you don't know how I recommend restoring a stock nandroid , flash the stock recovery and you should be ggod to go.
Click to expand...
Click to collapse
I checked to see if there is an OTA update before I flashed a custom ROM and there was none. Can I just flash a stock rom with an updated firmware? If so where can I find the latest firmware?

How can I easily update the firmware on my T-Mobile HTC 10?

I have the T-Mobile HTC 10. I never converted it to US unlocked or anything. When I got it, I unlocked the bootloader, installed custom recovery (TWRP) rooted it, and slapped on a custom ROM (LeeDroid). I have a nandroid backup of my stock rom. I'm still S-ON.
Now I find out that T-Mobile has FINALLY pushed the firmware update. How I can easily upgrade the firmware on my phone?
What I tried was to backup my leedroid, restore my stock rom, and then take the update. But I got the corrupt file error.
No idea what to do now. I saw someone had a file of the OTA update (downloaded it), but I don't know what to do with that, or even if I can as I have S-ON.
How can I easily get to rocking the new firmware on my T-Mobile HTC 10?
Thanks!!

pappy97 said:
I have the T-Mobile HTC 10. I never converted it to US unlocked or anything. When I got it, I unlocked the bootloader, installed custom recovery (TWRP) rooted it, and slapped on a custom ROM (LeeDroid). I have a nandroid backup of my stock rom. I'm still S-ON.
Now I find out that T-Mobile has FINALLY pushed the firmware update. How I can easily upgrade the firmware on my phone?
What I tried was to backup my leedroid, restore my stock rom, and then take the update. But I got the corrupt file error.
No idea what to do now. I saw someone had a file of the OTA update (downloaded it), but I don't know what to do with that, or even if I can as I have S-ON.
How can I easily get to rocking the new firmware on my T-Mobile HTC 10?
Thanks!!
Click to expand...
Click to collapse
I flashed the untouched system image and boot img then I fastboot flash stock 1.21.206.4_rec.img I used this because I couldn't get a T-Mobile stock recovery
Then rebooted to recovery and adb sideloaded the ota zip
That's it job done

twinnfamous said:
I flashed the untouched system image and boot img then I fastboot flash stock 1.21.206.4_rec.img I used this because I couldn't get a T-Mobile stock recovery
Then rebooted to recovery and adb sideloaded the ota zip
That's it job done
Click to expand...
Click to collapse
Is that the command you actually ran?
"fastboot flash stock 1.21.206.4_rec.img" ?
Thanks

pappy97 said:
Is that the command you actually ran?
"fastboot flash stock 1.21.206.4_rec.img" ?
Thanks
Click to expand...
Click to collapse
Nope I changed the name to 1.21.img
So my command was.
fastboot flash recovery 1.21.img
I had downloaded a few I was gonna try them all.

twinnfamous said:
Nope I changed the name to 1.21.img
So my command was.
fastboot flash recovery 1.21.img
I had downloaded a few I was gonna try them all.
Click to expand...
Click to collapse
Thanks, very helpful!

Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).

pappy97 said:
Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).
Click to expand...
Click to collapse
I'm getting the same error unfortunately. I have USA T-mobile HTC 10. Does anyone have a solution for this or are we USA T-mobile folks doomed to wait for an RUU?

pappy97 said:
Everything worked great until actually applying the OTA update in recovery. It wouldn't do it, saying the update was for PMEWL devices, and mine is PMEUHL. I definitely tried to use your OTA update file that you posted in another thread. Any idea what this is all about? (Seems WL is a reference to another phone, maybe US unlocked. So perhaps this is the OTA for US unlocked, not T-Mobile US? Or it's really for TMO DE?).
Click to expand...
Click to collapse
So you don't have a T-Mobile is phone.?

twinnfamous said:
So you don't have a T-Mobile is phone.?
Click to expand...
Click to collapse
what's the exact stock image that you flashed?

twinnfamous said:
So you don't have a T-Mobile is phone.?
Click to expand...
Click to collapse
This is what my info reads.
I have 2 both from T-Mobile stores in US

max05xiii said:
what's the exact stock image that you flashed?
Click to expand...
Click to collapse
Recovery 1.21.206.4
System.img from 1.21.531.1

twinnfamous said:
Recovery 1.21.206.4
System.img from 1.21.531.1
Click to expand...
Click to collapse
Well, you're S-OFF and I'm S-ON. I don't know if that makes a difference or not. Thanks for your help by the way

max05xiii said:
I'm getting the same error unfortunately. I have USA T-mobile HTC 10. Does anyone have a solution for this or are we USA T-mobile folks doomed to wait for an RUU?
Click to expand...
Click to collapse
I have a untouched system.img and boot.img twrp backup from the new 1.81.531.1 update. I just need to upload it and share the link.
---------- Post added at 07:55 AM ---------- Previous post was at 07:50 AM ----------
max05xiii said:
Well, you're S-OFF and I'm S-ON. I don't know if that makes a difference or not. Thanks for your help by the way
Click to expand...
Click to collapse
Yea I was gonna ask.
It might make a difference being s-on but wondering if u tried to update firmware from the signed firmware?

I was running into issues flashing the Ota but eventually managed to to get it to work. Here's exactly what I did.
Place the Ota file on the root of an SD card.
On your PC, Pull the recovery image from the firmware zip within the t-mobile OTA file and place in the ADB folder.
In twrp, go to Mount, and mount system as read only.
Then, select Restore and go to your untouched system backup. The only two options that should be checked are System IMAGE and Boot.
Reboot to Download
Flash the stock recovery pulled from the OTA.
Reboot to Bootloader, then boot to Recovery
Select install from SD card and select the Ota file.
For me, it did seem to hang at "patching system" or something like that, but be patient. It did complete loading.
Hope this works for you
Sent from my HTC 10 using XDA-Developers mobile app

bsims85 said:
I was running into issues flashing the Ota but eventually managed to to get it to work. Here's exactly what I did.
Place the Ota file on the root of an SD card.
On your PC, Pull the recovery image from the firmware zip within the t-mobile OTA file and place in the ADB folder.
In twrp, go to Mount, and mount system as read only.
Then, select Restore and go to your untouched system backup. The only two options that should be checked are System IMAGE and Boot.
Reboot to Download
Flash the stock recovery pulled from the OTA.
Reboot to Bootloader, then boot to Recovery
Select install from SD card and select the Ota file.
For me, it did seem to hang at "patching system" or something like that, but be patient. It did complete loading.
Hope this works for you
Sent from my HTC 10 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wish I saw this post before I just flashed the zip and completely lost root.
Sent from my HTC 10 using XDA-Developers mobile app

Having trouble flashing ota after returning to stock.

Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks

You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).

redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img

rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297

redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.

rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?

redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...

rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.

rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2

ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...

rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?

rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.

ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?

Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !

Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help