Develop Bugs

[Q] JB OTA fails with the red rectangular

I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya

mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'

Also, maybe try flashing the stock kernel as well?

Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)

ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.

BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.

mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.

mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.

BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.

Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.

You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003

sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.

mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above

exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.

mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me

exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours

You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.

i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?

plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one

plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.

please help cant come back to stock

my phone (htc one x) version is for hong kong cid:622
right now im in Android_Revolution_HD-One_X_18.0 rom and I want to come back to stock
I have RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Rad io_5.1204.162.29_release_299865_signed file and I relock my phone and start run this ruu file and everything alright but when program start to check my phone version give error for phone version but im 100% sure that version of software and phone is same.
when my phone in orginal rom, ota update exactly come with this version and that time also have same problem and have error in phone version
any one have an idea? I really need to come back in orginal software

fastboot getvar version-main
And the actual error message please.

BenPope said:
fastboot getvar version-main
And the actual error message please.
Click to expand...
Click to collapse
2.17.708.7

uturn2316 said:
my phone (htc one x) version is for hong kong cid:622
right now im in Android_Revolution_HD-One_X_18.0 rom and I want to come back to stock
I have RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_HK_3.14.708.28_Rad io_5.1204.162.29_release_299865_signed file and I relock my phone and start run this ruu file and everything alright but when program start to check my phone version give error for phone version but im 100% sure that version of software and phone is same.
when my phone in orginal rom, ota update exactly come with this version and that time also have same problem and have error in phone version
any one have an idea? I really need to come back in orginal software
Click to expand...
Click to collapse
Can you please upload it?
I cant find this ruu.
Would be regretful...

you must first install the original boot.img + original recovery.img and then relock your bootloader , And try ...

samooorje said:
you must first install the original boot.img + original recovery.img and then relock your bootloader , And try ...
Click to expand...
Click to collapse
This information is false. Youonly need to relock bootloader.

TToivanen said:
This information is false. Youonly need to relock bootloader.
Click to expand...
Click to collapse
I have the same problem in ICS , after installing the original recovery and lock the bootloader the problem gone.

Samooorje is right but TT actually also, in some cases the ruu fails and after flashing back the stock recoveryand/or the stock boot.img they had succes. But this is not applied to everybody, i for instance did not had to reflash anything before running the JB ruu. Still have no clue why this is. :thumbup:
Sent from my GT-P5110 using xda app-developers app

back to stock for OTA
HTC ONE X on Stock Jelly Bean after i flashed JB viper x 3.3.3, everything was working fine. I decided to try an OTA update, reflashing the stock ICS back using Custom Ruu, wich is an awsome project. i returned to stock ICS 4.0.3, reflashed stock recovery, i tryied an ota update, i was able to get it ( not JB, i think it was something else, maybe ICS 4.0.4), than stuck in bootloop....in fast boot it was an red warning message, about recovery i think...i repeat the whole procedure once more, i got ICS 4.0.3 functionally, then OTA , after again boot loop. what do you think is the cause? could be the recovery? i flashed the recovery extracted from original stock ICS 4.0.3 rom
( RUU_ENDEAVOR_U_ICS_40_TMO_DE_1.29.111.11_Radio_1.1204.105.14_release_260730_signed)...i didn t try the JB stock recovery
now i m on ViperX again
hboot 1.36, CID T-MOB101

mightymike2012 said:
HTC ONE X on Stock Jelly Bean after i flashed JB viper x 3.3.3, everything was working fine. I decided to try an OTA update, reflashing the stock ICS back using Custom Ruu, wich is an awsome project. i returned to stock ICS 4.0.3, reflashed stock recovery, i tryied an ota update, i was able to get it ( not JB, i think it was something else, maybe ICS 4.0.4), than stuck in bootloop....in fast boot it was an red warning message, about recovery i think...i repeat the whole procedure once more, i got ICS 4.0.3 functionally, then OTA , after again boot loop. what do you think is the cause? could be the recovery? i flashed the recovery extracted from original stock ICS 4.0.3 rom
( RUU_ENDEAVOR_U_ICS_40_TMO_DE_1.29.111.11_Radio_1.1204.105.14_release_260730_signed)...i didn t try the JB stock recovery
now i m on ViperX again
hboot 1.36, CID T-MOB101
Click to expand...
Click to collapse
Are you posting this everywhere now ??? Stay in one thread. I will not follow you around here you know :banghead:
If you answered my question in the other thread we would be a lot further by now .....

[Q] Looking for RUU for VODAP019 (Ireland)

Hi, where can I find an RUU for Vodafone Ireland. Help much appreciated.

Depends on your main version
Fastboot getvar version-main
Please post the outcome ! :thumbup:

Mr Hofs said:
Depends on your main version
Fastboot getvar version-main
Please post the outcome ! :thumbup:
Click to expand...
Click to collapse
3.14.161.27
Thanks

There is no ruu for that, but there is a nandroid backup of the stock rom you can use
http://bugsylawson.com/index.php/files/file/214-cwm-nandroid-backup-cid-vodap102-31416127/

Mr Hofs said:
There is no ruu for that, but there is a nandroid backup of the stock rom you can use
Thanks mate. the restore worked and I was able to get the phone back working. Now to do some backups
I had previously been trying to restore to stock in order to bring it back to the shop under warranty (yellow/brown patch on screen on top right).
Thanks
Mick
PHP:
Click to expand...
Click to collapse

Cool, did you flash back the stock recovery too ?

Mr Hofs said:
Cool, did you flash back the stock recovery too ?
Click to expand...
Click to collapse
Just trid that to version 1-28 I think and I'm getting the dreaded red triangle
I thought that was a clean versio so maybe something else is wrong. Any ideas?

Uhm wait .... You flashed back a 1.28 stock recovery on a 3.14 rom. That's not going to work.
And what is your goal now actually after the restore ?
And where do you get a red triangle ? When you boot up the phone or when you try to enter the stock recovery ?
When you enter a stock recovery there will always be a warning sign like you describe, we are not supposed to go in there
This is a stock 3.14 recovery
https://www.dropbox.com/s/ms7vd18vb9watr8/stock recovery 3.14.img

Mr Hofs said:
Uhm wait .... You flashed back a 1.28 stock recovery on a 3.14 rom. That's not going to work.
And what is your goal now actually after the restore ?
And where do you get a red triangle ? When you boot up the phone or when you try to enter the stock recovery ?
When you enter a stock recovery there will always be a warning sign like you describe, we are not supposed to go in there
Click to expand...
Click to collapse
OK, I have now flashed 3.14 and booted into it. first time around it showed the normal icon for a while and then restored my system. Second time around when I booted into recovery is shows the red triangle over the image of a screen. Flashing CWM seems to be ok.
bootloader version: 1.36.0000
version-main: 3.14.161.27
cid: has changed to VODAP001
Should I startt again from the nandroid?
My aim is to fully restore the phone to stock and then lock it before I bring it back to the shop for hardware repair on the yellow/brown patch.

Does the phone boot up properly ?
I don't know if there is a nandroid that also matches your cid ?
Fastboot oem readcid
Will tell the real cid.
Do that and we check if there is one actually available.

Mr Hofs said:
Does the phone boot up properly ?
Click to expand...
Click to collapse
yep, it boots ok into wwm (after reflash) and into the main system but not into recovery if I flash stock.
I can make calls etc and everything seems normal.
Only software issue now seems to be that I can't flash stock recovery successfully

So when you flash the stock recovery the phone does not boot ?
Oke give the cid with the command, lets check that out
Crap....you wrote it in the title....overread it all the way !!!
I have an idea that might work !
Get the nandroid 2.17.161 vodap 001 and restore that one completely !
Then flash back this recovery
https://www.dropbox.com/s/wbav46spkbznovp/stock recovery 2.17.img
Then boot up the phone and update with official ota.
It worked before with and O2 nandroid .... Its worth a shot mate

Mr Hofs said:
So when you flash the stock recovery the phone does not boot ?
Oke give the cid with the command, lets check that out
Click to expand...
Click to collapse
Phone itself works with stock recovery but it won't boot into stock recovery itself without red triangle.
I've just been trying to change the cid with "fastboot oem writecid VODAP019" but I keep gettin either "too many links" or "unknow error". Itried tried but with the phone locked and unlocked :crying:
I'll keep trying to see if that will let me flash the stock recovery successfully and boot into it.
Mick

Hahaha that's the trick, the stock recovery is supposed to give you that warning sign ! That is absolutely normal. When you see that triangle screen you press volume - and power and it should enter the stock recovery. (Could also be volume +, can't recall it in my mind atm)
And you can't write a cid, we need S-OFF to do that .....

Mr Hofs said:
Hahaha that's the trick, the stock recovery is supposed to give you that warning sign ! That is absolutely normal. When you see that triangle screen you press volume - and power and it should enter the stock recovery. (Could also be volume +, can't recall it in my mind atm)
And you can't write a cid, we need S-OFF to do that .....
Click to expand...
Click to collapse
Ok I,m into stock recovery with 2.17
the standard blue options are at the top but I also have failed to mount /sdcard in yellow below that 3 times !! (no such directory).
rebooted and now I am downloading software updates v4.0.475679

mccmick said:
Ok I,m into stock recovery with 2.17
the standard blue options are at the top but I also have failed to mount /sdcard in yellow below that 3 times !! (no such directory).
rebooted and now I am downloading software updates v4.0.475679
Click to expand...
Click to collapse
immediately follwed by the main system update as expected

Yeah that's because the stock recovery can't mount it, the error is also normal. There is not much to do with the stock recovery.....
If the updates go well you het back the original stock JB rom and cid back !
Is it working .... the updates ?

Mr Hofs said:
Yeah that's because the stock recovery can't mount it, the error is also normal. There is not much to do with the stock recovery.....
If the updates go well you het back the original stock JB rom and cid back !
Is it working .... the updates ?
Click to expand...
Click to collapse
Hi, the updates took a long time to download. Everything is now working and back to stock.
Thanks for all your help and patience.
Mick

Good ! Hope you get the fix sorted too :thumbup:
CASE CLOSED !

Sorry for reviving an old thread. But this one seems closest to what I'm stuck on, so hopefully someone can help.
I was running a viperX rom on my htc one X for quite sometime, after updating the rom it was working fine but all of a sudden it stopped picking up any mobile network. Stupidly I deleted everything from recovery (cache, data on the sd card, the android OS, everything!). - No backup unfortunately.
I read about going back to stock, re-locked the bootloader and attempted to install via an RUU. My HTC One X is exactly the same as the one by mccmick, running 3.14.161.27 of the HTC software. Can't find an RUU for it anywhere.
But what do I do now? It ran out of battery, so I used command prompt to get the phone to change a little bit, then re unlocked the bootloader using hasoon2000's tool kit and installed the lastest version of CWM recovery so the phone can charge via mains.
There is no root access on the phone at the moment, can't access the internal sd card to put any ROM or superSU files on there. Mounting the sdcard for usb use via recovery does not work.
How do I resolve? I can't put a nondroid backup to the phone. Ideally I would like to go back to stock, but even if I can just install a rom and get everything working again, I'd be very happy.
Is there any command prompts I can use to send files over to the phone? Send a kernel, rom and root files over?
Should mention my phones cid is VODAP001 and running 3.14.161.27.

HOX Will not OTA plus No Imei

Hi i have been given a HOX to look at and it's had me stumped for the last 24 hours so now i'm asking for help. Here we go.
The phone has no IMEI/Baseband. The fasboot getvar all command returns the correct IMEI to the box but it just doesn't show in android so no signal at all stuck on airplane mode etc. It's a TMOB005 cid.
Tried loads of custom roms and methods no signal.
Tried to return to stock to flash stock RUU. My main 3.16.110.4 so try RUU RUU_ENDEAVOR_U_ICS_40_S_TMO_UK_2.17.110.5_Radio_2.1204.137U.21_release_284360_signed.exe it fails with script error and all other RUU fail at bootloader version.
I downloaded recommended nandroid for my main. 2012-10-29.07.35.43 from thread on here. Flashed boot img in fastboot. Flashed stock 1.29 recovery. Got the small 1.25mb OTA but then nothing after that and still no signal.
Tearing my hair out now. HBOOT is 1.39. Let me know if i've missed any info please any ideas now will help.

Oke i will give it a go !
You restored a 2.17 nandroid backup ? And flashed back a 1.29 stock recovery ?
In this case your rom won't respond to touch on screen ! You say your main version is 3.16 then you need a nandroid backup with at least that number....and a stock 3.16 recovery and not a 1.29 one
So.....enlighten me ?

Now you have me all confused?! The touch screen works fine with the stock recovery i flashed. It's one you recommended to someone else in a TMOB005 thread i saw. I'm not sure recovery is the real issue here anyway. The issue is not being able to flash an RUU, stock not doing the OTA it only reports the small one 1.25MB. Never asked for Jellybean OTa it just doesn't want to work.
The nandroid should be correct too as it's a TMOB005 one too.
If you can help let's start from my main as we know that's 100% right.
So what nandroid stock rom do i need, what recovery and anything else required?
Thanks for reply so far.

Oke you need a stock nandroid backup 3.16 if you have it (or already restored it) that's good then. Now we need your stock 3.16 recovery and not the 1.29 one.....
Is your 3.16 number matching this command ?
Fastboot getvar version-main

Ok I'll check when I'm at home next, I'll still appreciate any help/ideas/input from anyone. I'm sure my version matches the one with the version main command.
Does the recovery version have to match too? Where would I find the relevant one?

Try this one
http://db.tt/mp3v3KrP

Mr Hofs said:
Try this one
http://db.tt/mp3v3KrP
Click to expand...
Click to collapse
Thanks and is the nan droid I mentioned the correct one at all? Like I say it offers the small OTA does that have any significance?
Is there no possible way to flash ANY RUU?!

If the nandroid matches the main version number 3.16.110 then you have indeed the correct one. And no a ruu is not available so that's not possible atm.

I saw something about an RUU hack where it makes it think you have an older version or is that not possible any more? The custom RUU file isn't available for download any more.

Well its probably possible for some, but if the phone has updated touch drivers then its of no use. Ics and lower roms don't work because touchscreen doesn't respond !
And the OP is on 3.16 so that's a no go.
From 3.14 and lower it could work.

"fastboot getvar version-main" returns that my main is definitely 3.16.110.4. So what nandroid for definite matches and what recovery? Can anyone provide links please? Is 3.16.110.4 supposed to be Jellybean?!

Yes 3.16 is Jellybean. And the recovery will be in the nandroid backup, as well as the boot.img.

Will the nandroid backup not have clockwork mod recovery in it as that is required to make the backup?!

Hold on....
you have the 3.16.110 nandroid backup ?

No i have a main of 3.16.110.4. I have the 2.17.110.5 nandroid as i understand this should work for OTA as i read in another thread. As long as the red part matches. I have installed a 3.16 stock recovery too yet STILL not being offered the proper OTA (still get the 1.25MB one) plus the phone is still stuck without IMEI or baseband.
EDIT:
This guy you helped here... http://forum.xda-developers.com/showthread.php?t=2204955 was offered the OTA after using the same nandroid as me so what's going on?!

Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5

Mr Hofs said:
Well give it a go then !!!
Here is the 2.17 stock recovery......trying to recall what i missed/forgot.
http://db.tt/OtcxVXh5
Click to expand...
Click to collapse
Still no offer of the OTA hmm. It's such a shame we can't change CID or flash any RUU as I'm sure that would help me. I'm just stuck and this phone is useless.

What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !

Mr Hofs said:
What ota are you talking about anyway ? Restore the 2.17 nandroid and the 2.17 stock recovery and then ota up to JB !
Click to expand...
Click to collapse
That's exactly my aim but it's not happening.i've restored the correct nandroid (100% certain) unless there is a 3.16 nandroid? Then i've tried with stock recovery 3.16 and 2.17 both times. The only OTA i get offered is the first 1.25MB one and that's it nothing after it. Tried with bootloader locked and unlocked although this shouldn't matter.
Do you need GSM signal to be offered the OTA? As if you do i'll never get offered it as i don't have an IMEI or baseband etc.
I appreciate all the help you are offering Mr Hofs i see you have helped a LOT of people on here.
Just tried the recovery 2.17 that you uploaded as it's a diferent size to the ones i've previously tried but still no luck. No OTA at all.
Is stock recovery supposed to just show a red triangle? It's shows green first then changes to a red triangle ni'm not sure this is right even with bootloader locked.
Does recovery have to match as in 2.17.110?

No this stock 2.17 recovery works on branded phones too, its weird but indeed it could be related to no baseband and imei !

[Q] Dev edition m8 doesn't get 4.4.3 OTA

Hi all,
I'm sending my phone back to HTC becuase since day one it's been presenting issues (loose screen, the volume button is saggy and ultimatly what made me send it back, the camera seems to be having issues, I get the "you are blocking the secondary camera" message, when I'm not, and the camera can't focus correctly making the pictures extreamly blurry.
anyways, I'm getting the phone ready to sent it back, I flashed 1.54.401.5 firmware and went back to my old nandroid backup which was in 4.4.2, I flashed the stock recovery 1.12.1540.17 and the CID to the original one BS_US002.
I did a factory reset in the stock recovery and set up the phone, however I'm not getting the OTA for 4.4.3 and I have no idea what I'm missing...
any help would be highly appreciated.
ps: I used this as reference.
http://forum.xda-developers.com/showthread.php?t=2710735

I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota

Mr Hofs said:
I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota
Click to expand...
Click to collapse
thank you so much for your reply, I flashed the matching recovery, but still the update is not showing up, do you have any suggestions?
I'm downloading the stock nandroid listed in your nandroid backup thread for BS_US002 just to double check...

I think you need a different firmware. If you have the dev edition model that is originally on .1540 you can't do it via a 401 firmware.

My dev edition doesn't get 4.4.3 update either. All stock except unlocked s-off

Here a workaround for the ones interested:
1- Make sure MID and CID match, for the developer edition you have it should be:
MID: 0P6B12000
CID: BS_US002
If they match then you can download a stock nandroid and the firmware here.
2- Wipe evertying using TWRP and then restore the nand you´ve downloaded from the link above
3- Reboot your phone into booloader and then flash the firmware
4- I would advise you to clean the cache once you install the firmware in bootloader
5- Do a full factory restore from the bootloader, your phone should reboot by itself afterwards
In case you need it:
In order to flash the firmware you have to type Fastboot oem rebootRUU in bootloader mode then you will see an HTC grey logo, there you will have to type: fastboot flash zip firmware.zip. Make sure firmware you've have downloaded is renamed as "firmware.zip" before you do all this. I would recomend to perform this last command twice. To reboot your phone into bootloader type: fastboot reboot-bootloader, once your phone reboots then type Fastboot erase cache, perform a full factory restore there and let your phone reboot. After your phone reboots, you should have the latest version installed.
As and advise: be carefull with all this!

Mr Hofs said:
I think it's kinda strange to flash the 1.12.1540 stock recovery on a 1.54.401 firmware ?! Weird huh....because they don't match.....but......that has nothing to do wether you get update notifications ! You should get them wether they can be installed or not. But the combo recovery + nand will not work to official install of the ota
Click to expand...
Click to collapse
I flash any recovery to get dev ota and they all work

Or even simpler, as I did, apply the OTA through stock recovery.