I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
braneed said:
I recently flashed the 4.4.3 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I apologize for not being able to help you with your issue, but where did you get a 4.4.3 file for the RAZR HD?
LifeAsADroid said:
I apologize for not being able to help you with your issue, but where did you get a 4.4.3 file for the RAZR HD?
Click to expand...
Click to collapse
I have the same issue after OTA to 4.4.2. Usually happens to me when in YouTube or MX Player.
I see others with the same issue over in the Motorola forums.
Looking forward to hearing from others who have had this issue and found a solution.
My apologies, I meant 4.4.2
braneed said:
I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I have the same issue after OTA to 4.4.2. Usually happens to me when in YouTube or MX Player.
I see others with the same issue over in the Motorola forums.
Looking forward to hearing from others who have had this issue and found a solution
braneed said:
I recently flashed the 4.4.2 OTA onto my phone, then downgraded to JB to flash Carbon but was not pleased so I reformatted the phone, put 4.4.3 back and then restored a nandroid from before I downgraded.
Now, when I unlock the phone, the screen flashes blue, not just parts of it, the whole thing, almost like the display is going bad. If i open a game, it stops and wont do it again until i relock the screen.
Just curious of anyone else has had this happen.
Click to expand...
Click to collapse
I also have had this problem with my droid razr maxx HD. I also have 4.4.2 and haven't flashed anything to it, but it is unlocked and rooted. It usually happens to me when im in portrait on the twitch.tv app. it stops after a bit, but I have no idea what is happening. it also stops if I go to landscape mode.
Balls Hurricane said:
I also have had this problem with my droid razr maxx HD. I also have 4.4.2 and haven't flashed anything to it, but it is unlocked and rooted. It usually happens to me when im in portrait on the twitch.tv app. it stops after a bit, but I have no idea what is happening. it also stops if I go to landscape mode.
Click to expand...
Click to collapse
ditto
Now that I see others affected I should probably expand on my original post above.
Initially I took the 4.2.2 OTA update with an unlocked bootloader. After the update, phone stuck in splash screen with the "Locked Bootloader" message.
I then rebooted into recovery and re-installed the 4.4.2 AOSP using RSD.
I too see the blue flash most frequently while watching video and occasionally while in Touchdown exchange.
dunroven said:
Now that I see others affected I should probably expand on my original post above.
Initially I took the 4.2.2 OTA update with an unlocked bootloader. After the update, phone stuck in splash screen with the "Locked Bootloader" message.
I then rebooted into recovery and re-installed the 4.4.2 AOSP using RSD.
I too see the blue flash most frequently while watching video and occasionally while in Touchdown exchange.
Click to expand...
Click to collapse
I was completely stock jellybean when I took the OTA, not rooted or unlocked or anything. I only recently unlocked and rooted mine. I'm pretty sure I had the problem before I did all that.
Related
Randomly today my brother's Moto G just turned off and refused to get past the bootscreen and upon turning it off it simply reboots to the bootscreen, at the time the firmware was 4.4.2 and i attempted to flash it back to stock 4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2542219 , I got all the OKAYs, followed instructions completely and it still reboots to the bootloader after the 4.3 Stock load.
My question is, is there anything else I can do or is this phone done with?
I am currently in the process of reflashing with a 4.4.2 firmware, all for the xt1034 which is the phone model. Any help would be appreciated as none of the modes in the boot console [recovery,factory] etc do nothing but get stuck on the bootscreen.
And one last question, how long does the phone last on the bootscreen after a reflash? I waited 10mins but nothing changed.
EDIT: can someone change this thread to question, it seems i didnt click it properly >.>
2Ponies1Apple said:
Randomly today my brother's Moto G just turned off and refused to get past the bootscreen and upon turning it off it simply reboots to the bootscreen, at the time the firmware was 4.4.2 and i attempted to flash it back to stock 4.3 using this guide http://forum.xda-developers.com/showthread.php?t=2542219 , I got all the OKAYs, followed instructions completely and it still reboots to the bootloader after the 4.3 Stock load.
My question is, is there anything else I can do or is this phone done with?
I am currently in the process of reflashing with a 4.4.2 firmware, all for the xt1034 which is the phone model. Any help would be appreciated as none of the modes in the boot console [recovery,factory] etc do nothing but get stuck on the bootscreen.
And one last question, how long does the phone last on the bootscreen after a reflash? I waited 10mins but nothing changed.
EDIT: can someone change this thread to question, it seems i didnt click it properly >.>
Click to expand...
Click to collapse
Type: Fastboot -w
It will Delete user data but it will work normally
xxeldaddyjrxx said:
Type: Fastboot -w
It will Delete user data but it will work normally
Click to expand...
Click to collapse
Thanks, this worked but everything is ridiculously unstable at the moment, google services stopping all the time did i use a bad fw?
2Ponies1Apple said:
Thanks, this worked but everything is ridiculously unstable at the moment, google services stopping all the time did i use a bad fw?
Click to expand...
Click to collapse
do the Fastboot -w then re flash the android 4.3 and update to 4.4.2 and it should go back to normal
sorry for a late reply, been busy lately , im only 14 years old cx and got alot of school work and help my dad at work too.
Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Thorfell said:
Hi, hope someone can help me.
I have a Samsung Galaxy S4 (GT-I9500), it was on Android 4.3 and I upgraded to Andorid 4.4.2 via Kies.
This was a legitimate provider update.
Immediately on the first boot the Samsung Logo was blocky and pixelated, so was the Samsung animation.
This blocky-ness persists on the desktop and any app I open.
UNTIL I lock the screen and unlock it. Then everything becomes clear again.
I since then I installed a new 4.4.2 ROM via Odin, but no luck.
I have ClockWorkMod installed too. The strange thing is that when I boot into recovery mode (into ClockMod) the resolution is fine.
Any ideas?
Help would be greatly appreciated.
Click to expand...
Click to collapse
can you give us a pic?
Trozzul said:
can you give us a pic?
Click to expand...
Click to collapse
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Thorfell said:
Here you go.
I find out something else.
If I enable the lock screen pattern the the display stays blocky.
Click to expand...
Click to collapse
I think it's got to be config or software related beacause if I turn the lock screen back to swipe, restart and then lock it's fine again.
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Thorfell said:
I just took a look at the screenshots I attached.
They look fine!
that's very odd. What would cause the screen to display the images badly but save the screenshots as normal?
Click to expand...
Click to collapse
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Trozzul said:
well if CWM looks fine, try flashing twrp and see if twrp is pixely, if not get back to stock 4.2.2 or 4.3 and see whats up. maybe you had a bad install on 4.4?
Click to expand...
Click to collapse
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Thorfell said:
I tried flashing back to 4.3, but Odin Failed.
I am trying to get a different 4.4.2 ROM now.
Once I download the new ROM (my bandwidth is terrible), do you think it's worthwhile to re-partition in Odin as well to fix the blocky issue?
Do you think it could be boot loader related?
Click to expand...
Click to collapse
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Trozzul said:
thats up to you for the re partitioning, you know what it does right? as for Odin, did you get your firmware from here Sammobile.com? is download mode the same way as well?
Click to expand...
Click to collapse
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Thorfell said:
I fugure if the pixelation is config related or a corruption then a repartition would fix it.
I will put a 4.3 XFA rom from sammobile and see if the problem goes away. It will have to be on after the easter weekend though
Click to expand...
Click to collapse
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Thorfell said:
No matter what I do, I can't get a 4.3 ROM on my galaxy.
I have flashed back to an official Samsung 4.4.2 for my region but the blocky-ness is still there.
I'm going to take the device to a Samsung store and see what they say.
Thanks for the advice.
Click to expand...
Click to collapse
Latest update: The Samsung Service centre is not particularly helpful.
I left my phone there yesterday and explained the problem.
Got the phone back and all they had done was wipe the data and reinstall Android. It has not fixed the pixelated problem.
I explained the problem again in excruciating detail and have left the phone with them once again.
let's see what happens.
Can anyone tell me what actually kicks off the graphics processing as soon as the phone boots?
As in when the very first image is displayed on boot (the Samsung logo with device model number).
Is it the bootloader? If so any ideas on what I can do to reinstall the standard samsung one?
Problem solved.
So after all of that Samsung replaced my screen and it sorted the problem out!
Still, it's very odd that it failed immediately after the 4.4.2 update.
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
chrismin13 said:
Hello XDA!
I have some questions about my n8010. It is a tablet that I bought in Greece, in case that is necessary to know, and has an interesting background. It started late May. The tablet was unrooted and without any mods whatsoever. I was running the latest Jelly Bean update and had A TON of lag. I had replaced TouchWiz Launcher with Nova and a different gallery and music app with still a lot of lag. So I decided to flash CM11 since it would be lighter for the tablet. After some research I followed the root guide from Zedomax and everything was fine. I had root and so I proceeded doing a backup. This where everything got weird. The backup started but was stuck for long periods of time. After some time being stuck in a screen I decided I should force restart. After the Galaxy Note 10.1 logo appeared it just hanged there without booting into Jelly Bean. I checked recovery and download mode and they where all working fine so I flashed TWRP. It worked and so I took a backup and proceeded installing CM11. I had it already in my SD. I had followed the instructions in the XDA thread that said about removing a line to make it work on the n8010. The flash went great and after factory resetting I rebooted the tablet and everything was OK. At the first boot WiFi wouldn't work but after a reboot it was. The only thing that wasn't working was the video recording. It is a deal-breaker as I use it a lot. I had to switch ROMs. I tried CM10.2 and it still wouldn't. Same goes for Revolt. At lat I switched to a TouchWiz based ROM. Specifically Hyperdrive RLS8. Video was working so I stayed there. I was noticing that since I flashed CM11 my tablet showed up as an n8013 which was very weird but since these ROMs where designed for the n8013 I thought it was normal.
One ROM also had the front facing camera able to record. Upon further inspection I found that Download Mode had my tablet as an n8010 but with the flash count 0 and the status official! Now, I'm either super lucky or the completely opposite! It also says official under About Device! Fast forward a few months and I am now in a situation where the tablet lags once again like crazy. I uninstalled a couple of apps and also installed lighter alternatives and it's somewhat bearable. I was reading the Official OmniROM thread and saw that others also had issues, most of which had the new KitKat bootloader that I don't have, with YouTube and the Video Recording. The latest nightlies are said to have a fix. So I am thinking of installing OmniROM since I am lagging a lot and I would like Screen Mirroring to the Chromecast. My only concern is that I will either brick the tablet or the camcorder won't work. Many people have bricked their Notes and can't go back without the Samsung Service. Most have the new KitKat bootloader which I don't and I'm happy about. My tablet is in a weird situation, what should I do? Anybody else experiencing these issues? Any advice is appreciated!
Thanks in advance,
Chris
Edit: Forgot to say that I flashed Carbon ROM in September and I got a status 7 while flashing with PhilzCWM that I had installed in order to flash Hyperdrive. I had to flash back to Hyperdrive as it wouldn't boot after the status 7. It probably happened because it didn't have SE Linux support. If I do anything I'll flash the latest TWRP.
Click to expand...
Click to collapse
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
shaun298 said:
I would have fixed the original lag issues first. I would get it back to factory stock 100 percent, once back to factory I would do A factory reset and start all over. Get the system running stock as it should then reinstall apps one at a time. if it can't run stock for whatever reason other roms not going to fix the problem.
at least with factory stock you know what should be working. Instead of guessing if the problem is part of the new ROM
Click to expand...
Click to collapse
Thanks for the response!
Good idea! I was thinking of going back to stock and repeating everything. It should fix all my issues. It's too bad that I don't have a working stock backup and I will have to flash through Odin. The reason that I am not doing this is because I am afraid of making it even worse from the official status state that I have in Download Mode and my device is an n8013 under About Device. A flash back to stock through Odin would probably flash most of the system parts which would be kinda dangerous. But on the other hand that would mean that I could give it a brand new try with better luck possibly! It's not that TouchWiz ROMs don't work, it's AOSP that doesn't. I played a lot with Hyperdrive and seems like it's doing better from the lag prospective. But that's only gonna last 15 days. I am sure! So, I'll have your response in mind! Might try it out when I have some free time. Unfortunately, that will probably be Christmas.
Thanks,
Chris
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Phil789 said:
Going back to stock is good advice.Should certainly fix the video problem which you said was important.
Click to expand...
Click to collapse
I don't have any video playback issues. It's just the camcorder that doesn't work in AOSP ROMs.
Yes.My use of the word "video" should have been "video recording".
The time has come!
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
chrismin13 said:
Hello everyone, happy holidays!
The time has come that I follow your instructions. I've done my research and here's how I'll do it. Do you agree? Do you have any other suggestions?
Take full backups with my current configuration (Hyperdrive RLS8, PhilzCWM)
Factory reset the device and clean it up so that there is a lot of space
Install Samsung Drivers
Flash Stock Greek 4.1.2 Frimware (N8010XXUCMK2_N8010OXXCMK2_HOME.tar.md5) through ODIN v3 1.85
Let it boot up and do a factory reset from stock recovery
Flash TWRP 2.8.1.0 for the GT-N8010 (openrecovery-twrp-2.8.1.0-gt-n8010) (I chose this version since it has the most downloads)
Make a full backup once again
Flash Omni ROM 4.4.4 (omni-4.4.4-20141222-n801x-NIGHTLY)
Flash SuperSU (UPDATE-SuperSU-v2.40)
Flash PA GApps (pa_gapps-modular-mini-4.4.4-20141214-signed.zip)
Factory reset
REBOOT!
Check everything (Video, model, download mode, bugs, etc.)
REPORT!
If everything goes correctly I believe I should be OK! Hope my issues will be over since the tablet is slow once again. Kinda scared, so that's why I'm asking you. Will I be (mostly) brick safe? Hope so!
Thank you very much for your support,
Chris
P.S.: Should I root before leaving stock? I mean through TWRP.
Click to expand...
Click to collapse
I did it! It worked. Everything went OK but:
- Flash count is 0 and status official
- Back camera records in slow-mo
- Chromecast mirroring does not work
However:
-My device is an N8010
-I use the front camera instead
-Mirroring was not really needed
-LAG IS HISTORY!!! [emoji50] [emoji2] [emoji2] [emoji2]
I am so impressed by the performance, still doesn't best my nexus 4 with KK 4.4.4 but it's a GIGANTIC IMPROVEMENT! Veeery happy! Thank you for your support, I wouldn't be here without you!
Merry Christmas and happy holidays!
Chris.[emoji2]
Has anyone attempted this? The latest 5.0.1 is no good for me. I wonder if i can just flash 5.0 on top of it with out losing data or experiencing other problems.
i dont know if you are going to experience issues but what you can do is to copy, the data and obb folders, and backup the apps with titanium backup in your sd card.
dowgrade on stock tablet
Since an asnwer still hasnt been posted, Id like to know if it is possible to downgrade from 5.0.1 to 5.0. My tablet has never been rooted and has a locked bootloader, and I would prefer of it were to stay like that. Im thinking something similar to Odin on a GS4
andreinept said:
Since an asnwer still hasnt been posted, Id like to know if it is possible to downgrade from 5.0.1 to 5.0. My tablet has never been rooted and has a locked bootloader, and I would prefer of it were to stay like that. Im thinking something similar to Odin on a GS4
Click to expand...
Click to collapse
U would have to unlock your boot loader. There are instructions on nvidia's site explaining the process. After looking into this, i think the only way to downgrade requires wiping all data. I think i may just hold out until they release a new update. Fortunately nvidia releases updates fairly quick.
Thanks for the help
Does anybody else have graphic glitches such as green colours appearing purple, and even when I panic and restart it remains even on the boot logo then goes away after a bit (no particular remedy, it just goes). There doesnt seem to be any particular action that makes it do that, it just spazzes out for a bit. Is this a driver glitch or just my particular device?
Im hoping its a driver glitch of sorts and not my device malfunctioning
It's been a long night and I'm at a complete loss as to what to look for next...
Around 9PM last night, my phone randomly rebooted... it's done this a few times before, and i thought nothing of it. When it finally booted back up, I was at the "choose your language" setup screen. WTF.
I lost literally EVERYTHING.
FYI, this was on stock rom, and I didn't even have the OTA(s) because I was rooted and was content with 4.4.2
Well, since all my data was gone, I figured it was about time to see what I could get with a custom ROM. The phone's been sluggish lately, so I figured a bloat-less upgrade would help.
Long story short, I loaded the 5.1 firmwares for VZW, and the HBOOT as well, and flashed GPE_5.1 on it. It took it like a champ, but refused to boot. I tried changing the kernels during the GPE install, but none of them worked. Some would loop, some would kick me into recovery, and one would just stall and the animation would run forever. No worries, I'm sure I can go to a stock 5.x rom! But that's a big NOPE. I just get "installation aborted" with no reasoning or errors in CWM (I had TWRP at one point as well, and it didn't get me anywhere either) Or I get "symlink: some symlinks failed" ... it depends what rom i'm flashing.
I've tried stock and custom, rooted and not... literally nothing will take.
ALSO, in my attempts to remedy the problem, I tried to reflash the firmware, but fastboot starts that there's not enough space. A quick google search pointed to "not enough ram in the PC" which is BS because it's done it on 2 different systems, both with 16GB ram, one running Win8.1 and the other Win7.
To top it all off, somehow I relocked the phone (but i still have S-OFF) and without being able to boot into the OS, I can't unlock it with SunShine/Firewater.
Hopefully, someone can point me in the right direction...
Welp... It's working now...
Not 100% sure what I ended up doing that worked, but I was able to run the unlocker via creating a new unlock_code.bin from htcdev and ran that with the all in one toolkit.
From there, I was able to use the toolkit to flash a stock ruu rom (I flashed the 5.0.1 RUU, but when it booted, I was still in 4.4.2)
It apparently didn't like somwething in the boot order other than the ROM itself.
I'm now running S-OFF, relocked but rooted 5.0.1 after it took several OTAs. Not sure how many more OTA's are pending, but it just keeps prompting me lol...
At this point, I'm just happy it's booting, stock or not. I don't even know what recovery I'm running at this point...
Did you update your recovery??? To the latest one
Sent from my HTC6525LVW using XDA Premium 4 mobile app