Related
Help!!!
I rooted my phone then installed clockworkmod recovery v3 (not sure if it is actually there)
I installed Radio S-off but upon getting to the bootloader I see ENG S-off
I used ROM Manager to flash the Android_Revolution_HD_2.0.13.
I ticked the wipe data and cache but didn't tick the backup existing rom (noo!)
Upon rebooting it is now stuck on the HTC logo screen =[
I got into the bootloader screen and tried the following:
*factory reset -> ended up going to the HTC logo again
*recovery -> goes to HTC logo again
pretty much choosing any option = HTC logo
I've tried formating my SD card but that didn't change anything
sniff sniff
Help please!!!!!!!
Are you running clockwork mod 3.0.0.6? if not, update to that and that should fix your flashing problems. Not more than 2 hours ago i was in your same situation
Are you using the dhd from telus or elsewhere?
Oh, I believe I installed 3.0.0.5
How do I update to 3.0.0.6, I cannot get into the recovery menu =[=[
I've been stuck with this problem for the last 4 hours XD, I'm reading all the forum threads to try and find a solution
Oh yes I'm on Vodafone
Are you able to start the process over again?
just search clockwork mod 3.0.0.6 and there is a thread here with a zip file you can download and upgrade to ver .6
mangolime said:
Help!!!
I rooted my phone then installed clockworkmod recovery v3 (not sure if it is actually there)
I installed Radio S-off but upon getting to the bootloader I see ENG S-off
I used ROM Manager to flash the Android_Revolution_HD_2.0.13.
I ticked the wipe data and cache but didn't tick the backup existing rom (noo!)
Upon rebooting it is now stuck on the HTC logo screen =[
I got into the bootloader screen and tried the following:
*factory reset -> ended up going to the HTC logo again
*recovery -> goes to HTC logo again
pretty much choosing any option = HTC logo
I've tried formating my SD card but that didn't change anything
sniff sniff
Help please!!!!!!!
Click to expand...
Click to collapse
Can you get into recovery? try flashing the ROM from recovery and see if that helps. I have seen many people who say that their DHD is stuck at boot screen. And almost all of them have used ROM manager to flash the ROM...so i do not know if there is something going on there with ROM manager (which it should not).
Before flashing you should have made sure that, you have Eng S-Off. Read this if necessary:
http://forum.xda-developers.com/showthread.php?t=857537
try pasting PD98IMG.zip on your SD card again, boot the phone into bootloader, and let it install that zip file again.
if that doesn't work, turn your phone off and take out the battery, then put it back again, and try again the above.
it worked for me in a similar situation, I hope it will help you also.
Thanks everyone for your help!
I was able to get past the problem by downgrading to cwm 2.5.1.3
After 5 hrs at it I was afraid that I would end up with a brick phone!!
xxo!!!
I had the same problem yesterday...moving down to a clockworkmod 2.5.x fixed the issue for me as well. Glad you got it sorted out.
First of all, hello to all forum members!
I had not been particularly active here in the forum,
but I read a lot here and build some knowledge.
so far I have solved all my problems due to browse and read.
But now I am facing a problem, where I need help.
I got a desire from a friend with wrong nexus one blackrose hboot.
I managed to install alpharev hboot on it, but its not booting the rom, neither the recovery.
I decided to get a ruu on it, to reflash boot, system, recovery, etc.
After i did:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <rom.zip>
the phone is stuck in fastboot RUU mode. No matter if I pull the battery and power on with vol-, vol+ or back, the fastboot RUU mode starts (Black screen with htc logo in the middle and 4 exclamation marks in the corners).
What Ive done so far:
Tried different RUUs(Europe, WWE) via fastboot. Most of them fail while writing radio image.
Tried to flash the radio image via fastboot. Most of them stuck while writing.
Asked a friend with exactly matching hardware to send me his working nand backup, his hboot is CM7 r2, so I flashed it
to match his nand backup.
I flashed his boot/recovery/system/cache and the latest radio, matching the nand backup.
The latest radio was flashed successfully.
The recovery in his nand backup was 4EXT Touch 1.0.0.3
So, after flashing boot, recovery, system, cache and even misc and userdata (AND erasing them prior on second try), the behaviour stays the same, the phone wont boot the rom or recovery and no matter what buttons I press on power on, it boots at fastboot RUU mode.
I tried
Code:
fastboot oem boot
, but that keeps stucking in the white htc splash1
If I plug in the usb cable and pull it out again, I see the hboot infos:
AlphaRev CM7 r2
BRAVO PVT1 SHIP S-OFF
HBOOT-6.92.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
<date>
RUU
After a lot of research, Ive found several opinions:
-its a brick (sure it is ;D)
-its a radio brick (ive sucessfully flashed the newest radio, so I doubt it)
Almost all users wo tried it hardly, and havent given up after the second try,
recovered their phone from this fastboot RUU mode.
I can run all fastboot extended commands, and flash RUUs over it.
So: what have I done wrong? Is there anything missing?
Can someone who knows what he says please take a look over it?
Thank you really much
criestr
After "a lot" of research you still haven't looked at my guide, well done.
Sure Ive looked at your guide,
I work with linux, and I hate flashing tools.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
Click to expand...
Click to collapse
Is it any difference to use
Code:
fastboot flash hboot bravo_alphaspl.img
instead of using Android Flasher?
I dont think so, and Ive already done the steps in your guide, except using Android Flasher to flash the AlphaRev stock version.
Or is there another point in your guide that Im missing?
If so, then I am sorry for wasting your time.
I know, I am "new" here, so thats the standard answer for all newbs from you.
Thats ok. But Ive fixed a lot of phones without open even one thread, just with hours of research. But after google search for about 8 hours, several tries and following several guides and tips I didnt find an answer yet.
New update: Ive managed to push and boot the 4EXT Recovery image.
Fair enough, but the guide was meant to be made as easy to use as possible.
All you had to do was flash the stock hboot, or the downgrader, and then try a RUU.
The reason for it being stuck, is because alpharev hboots have write protection (meaning they won't be overwritten until you use the downgrader), and since you had the cm7r2 partition flashed, there was not enough space in /system for the stock ROM.
Hi again,
thanks for your answer.
I had the right stock hboot whilst flashing the RUU, so that wasnt the problem.
The RUU always failed to write the radio. A few hours ago i figured out that
the problem was because of a faulty battery. I changed the battery, loaded it
half an hour, and voila! the RUU was running quite fine.
The stock rom wasnt booting yet, but from then it was possible to go into the HBOOT/Fastboot, so it was making progress ;D
After another research I found out that my misc partition was screwed, maybe because the blackrose hboot, maybe because of the pre-owner.
Fixed the misc partition with cid, kernel commandlines & rom version.
After that I wiped cache and data, and did fastboot oem boot.
The rom was booting, but did random reboots/crashes after about 3-5 mins.
After 3 or 4 reboots the phone is now stuck at htc splash1, and isnt booting anymore.
For now I will try to flash the nand backup again, see if that works out.
Anyone has an better idea?
Thanks alot
criestr
New update:
The phone switched randomly between bootable and non-bootable bootloop/stuck in splash1.
I tried different radios, different boot & system.img from RUUs.
I can flash a new recovery, tried 4 different ones, none of them is booting,
not over hboot->recovery and also not over
Code:
fastboot oem gencheckpt
.
The only thing that worked was to erase cache and immediatly do
Code:
fastboot boot recovery.img
,
so after the stock rom randomly reboots, I decided to install a custom rom for CM7 r2 hboot. So I flashed the CM7 r2 hboot again, erased cache, booted the recovery and flashed rom.
The rom was booting! But again, after fiddling with flashing a new recovery with 4EXT Updater, the rom rebooted into splash1 and stuck there.
After this first time, it has yet never rebooted again. So I twist my fingers that it was a custom rom bug on first boot.
Flashing the recovery via 4EXT Updater worked for me, despite of none of the recoverys flashed via fastboot had booted before.
Anyway, thanks for the help.
Hopefully it helps someone with the same problem,
but I doubt there are many people dumb enough to flash blackrose hboot on a desire
Cheers
criestr
I had a similar problem with my old Magic. I have Desire now but never had that problem. I hope not.
Anyways, the way I solved it was to flash the right radio.img. I supposed you can try to fastboot flash radio radio.img. Make sure you use the right radio.img. That is what I did if I recall correctly and it worked for me on Magic. I don't know if it is will work on Desire that way.
The other thing is when Ruu failed at radio, I think it is because the lower version of radio.
I hope this helps.
Try it and let me know.
bortak said:
After "a lot" of research you still haven't looked at my guide, well done.
Click to expand...
Click to collapse
link please
[Q] "succesfully" Flashed phone hangs up and gets stuck at HTC splash screen
Hi,
I've got an odd issue with my GF's phone.
Specs:
Revolutionary rooted
Buzz PVT Ship S-off
H-Boot 6.01.1002
microp-0622
touch panel - Atmelc03-16ac
Radio: 3.35.20.10
Rom: KWBR Rom android 2.2.1
Kernel: 2.6.32.21-g0f9e9b5 htc [email protected]#1
After I flashed the KWBR rom it ran fine for a week or so untill it hung up. Manually switching off wasn't possible so had to take out the batt.
After restarting it hangs at the white HTC screen (without quietly brilliant) and stays there like forever.
Also resettting it in recovery to factory settings doesn't work out.
Ultimately re-flashed KWBR again but y'day it hung up again and everything described above happened again.
However on a normal restart/reboot/power off-power on it does what it's supposed to do.
Has Anyone experienced this before? and moreover anyone a solution? (because GF's get cranky when phones are messed up)
Have you tried flashing another ROM?
(Don't forget to do a nandroid backup )
nejc121 said:
Have you tried flashing another ROM?
(Don't forget to do a nandroid backup )
Click to expand...
Click to collapse
Tried Cyanogen only for a couple of hours after s-off (but madam found it toooo far off from what she was used to) and haven't nandroid backupped. Titanium though
de vetnek said:
Tried Cyanogen only for a couple of hours after s-off (but madam found it toooo far off from what she was used to) and haven't nandroid backupped. Titanium though
Click to expand...
Click to collapse
What about other Sense ROMs, like RemPuzzle?
Will do when it hangs up again. however it looks that for Rempuzzle I have to partition my SD Card first before flashing.
if I understand correctly
Partition SD card, Swap 0
Then flash REMpuzzle and I'm good to go?
Can I instantly flash 2.43 or should I first flash 2.40 and then 2.43 ?
Back up your SD card first.
And yes, first flash 2.4.0 then 2.43.
Hi!
I've been using ViperDHD 1.2.3 on my HTC DESIRE HD but now it crashed and it's stuck on the HTC logo. I belive the problem isn't the rom because I've been using it for almost a year and it has worked perfectly.
I can get it to HBOOT screen, but I cant go to RECOVERY because it just show the HTC logo and nothing happens.
Some text found in HBOOT:
***** AAHK *****
ACE PVT ENG S-OFF RL
HBOOT-0.85.2425
MCROP-0438
RADIO- 26.10.04.03_M
eMMC-boot
Apr 12 2011, 00:55:45
I spend whole yesterday searching but I didn't found any solution. So please help me! :crying:
you can try flashing recovery from hboot and see if then you can at least boot into it. then make a backupz and reflash. dirty flash might help, if it doesnt, fullwipe then reflash. your data should still be in nand backup, and you should be able to extract it with titanium backup. if this dont work, you probably have a more serious problem...
it might be helpful if you could provide more details what exactly happened, because "crash" doesnt really tell a lot.
t0mas_ said:
you can try flashing recovery from hboot and see if then you can at least boot into it. then make a backupz and reflash. dirty flash might help, if it doesnt, fullwipe then reflash. your data should still be in nand backup, and you should be able to extract it with titanium backup. if this dont work, you probably have a more serious problem...
it might be helpful if you could provide more details what exactly happened, because "crash" doesnt really tell a lot.
Click to expand...
Click to collapse
I choose the RECOVERY option from HBOOT menu (is this what you mean?), then it vibrated and showed the HTC logo and after that nothing happened.
I was playing music when the phone vibrated few times and the screen went black, I could still hear noise from the speaker. Then I took out the battery and put it back and then I booted the phone but it was stuck in the HTC logo.
So is it dead now? :crying:
You can try what the previous member said. Flash a recovery either using pd98img.zip or fastboot.
Sent from a dream.
It says: "No image or wron image!"
MMCMVI said:
It says: "No image or wron image!"
Click to expand...
Click to collapse
or your sdcard is corrupted to work as a goldcard and there to flash PD98IMG files (try the same file with another sdcard) or perharps the file is misspelled. Check that you don't have .zip.zip or something similar.
glevitan said:
or your sdcard is corrupted to work as a goldcard and there to flash PD98IMG files (try the same file with another sdcard) or perharps the file is misspelled. Check that you don't have .zip.zip or something similar.
Click to expand...
Click to collapse
I've tried diffrend sdcards and diffrend files but it doesn't work. I found onde PD98IMG file that the phone regonized but when i pressed "yes" it did something and showed the HTC logo and after that nothing happened.
The file that my phone found (link) is only 220kt so I think it would not work anyway.
MMCMVI said:
I've tried diffrend sdcards and diffrend files but it doesn't work. I found onde PD98IMG file that the phone regonized but when i pressed "yes" it did something and showed the HTC logo and after that nothing happened.
The file that my phone found (link) is only 220kt so I think it would not work anyway.
Click to expand...
Click to collapse
Why are you trying to mess your device? You were running Gingerbread and you are trying to flash a Froyo RUU?? That is not good...you will probably mess the bootloader that way.
If you are s-off you can flash any ruu in fastboot...but if your device keeps vibrating for a while when you turn it on... and youwait for about 30 minutes and boots, then that means that your bootloader is corrupted and you need to fix it.
How long does it take to boot in hboot?
glevitan said:
Why are you trying to mess your device? You were running Gingerbread and you are trying to flash a Froyo RUU?? That is not good...you will probably mess the bootloader that way.
If you are s-off you can flash any ruu in fastboot...but if your device keeps vibrating for a while when you turn it on... and youwait for about 30 minutes and boots, then that means that your bootloader is corrupted and you need to fix it.
How long does it take to boot in hboot?
Click to expand...
Click to collapse
The phone starts like it should but it just get stuck on the HTC logo.
Booting in HBOOT goes also normaly, just few seconds from pressing the buttons.
mate, what are you trying to flash is bootloader not recovery. dont know why you want to do that? since your phone is behaving wierd, i dont think it is a good idea. you should find recovery image (.img) and flash with fastboot (your bootloader says you are eng s-off) or pdimg containing recovery, and then see if you can boot into it. if it does, you are on a good way to have your phone working again. if recovery flashes good and you still cant boot into it, i have no clue how to proceed...
I managed to install a PD98IMG file (with recovery image), but it's still stuck at HTC logo.
Hi all,
This is my M8 - Stock, Rooted & S-OFF. It's an unlocked O2 one which I use on EE in the UK
M8_UL PVT SHIP S-OFF
CID-02___001
HBOOT-3.19.0.0000
RADIO-1.25.21331147A1.06G
OpenSDP-v48.2.2-00564-M8974_FO.1211
OS-4.20.206.1 <--- after the OTA, this now reads OS-4.20.206.2
eMMC-boot 2048MB
The Stagefright OTA for my M8 just downloaded, so I re-flashed recovery with one that I extracted from the last 5.0.1 OTA (it usually has the latest TWRP) & let it install the OTA. Everything went fine, it rebooted afterwards to recovery, then automatically rebooted again... & then it sticks at the boot screen after showing the O2 logo & chiming.
From the stuck boot screen, I can reboot it into the boot loader or recovery fine, but now when I boot it into recovery I get this:
Android system recovery <3e>
LRX22C release-keys
Volume up/down to move highlight;
enter button to select.
reboot system now
apply from sd card
wipe data/factory reset
wipe cache partition
reboot into bootloader
power down
view recovery logs
apply from phone storage
_____________________
E:missing bitmap oem_unlock_bg
(Code -1)
E:missing bitmap oem_unlock_bg_yes
(Code -1)
E:missing bitmap oem_unlock_bg_no
(Code -1)
Write host_mode success
handle_cota_install: No CW files. Skip cw installation.
What do you advise?
I haven't tried to factor reset it yet, but there is nothing on the phone that isn't backed up, so I can reset, re-flash or do anything required to get it back. As it's S-OFF, at a pinch I could change the SID & flash an entirely different ROM, although I have tended to stay Stock up until now...
If everything else fails, is it worth downloading the 5.0.1 RUU from http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563 resetting my CID to HTC__001 & then letting it re-download & re-install the OTA before I re-root it & install TWRP again?
Nope... that didn't work! I just get
(bootloader) shift_signature size for header checking...
FAILED (remote: 32 header error)
regardless of whether I have a CID of HTC__001 or 11111111
& a factory reset doesn't seem to have made any difference either, as it is still stuck on the boot screen.
Any ideas of what to try next please?
Hey i Have the same Problem, but i doesnt have S-off (Still on S-ON) so i cant get RUU, or ?
Problemts solving hints ?!?!
I got the same problem, stuck on the boot screen.
S off, supercid, rooted, stock recovery and rom.
Hope we ll havé a solution quickly...
Hi,
maybe install TWRP recovery, restore everything to the state before applying the OTA and then trying once more?
But the newer TWRP versions might not even work any more, at least I have this problem, see http://forum.xda-developers.com/htc-one-m8/help/help-longer-enter-twrp-recovery-one-m8-t3186208.
HTC really seems to have done something nasty with this update. And it actually does not even fix all StageFright vulnerabilitis, the latest one stays open.
Cheers,
Tim
OK, I managed to get my phone back... I left the CID as HTC__001 but the trick was to rename the RUU to 0P6BIMG.zip & copy it to the root of the SD card using an adapter plugged into my PC. Then, I just rebooted it with Power & Vol Down, whereupon it automatically found it & started the update. I did note the prominent warning of "Do not power off your phone", so I left it to do its thing which took quite a while). Now, it's busy "optimizing apps", so I know that we are back up & running. OK, now, it's found the OTA & is busy downloading it again as well, so it appears that I now have a nice, stock, unrooted WWE install instead of my old O2 one. I must do a nandroid backup as soon as I replace the recovery with whatever version of TWRP works, but happy happy, I have my phone back again. I do hope the OTA doesn't kill it again when I run it, but as it is now 100% stock, I am full of hope.
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
JustinSB said:
OK, I managed to get my phone back...
Click to expand...
Click to collapse
Glad you got it running again. It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
tim_h said:
It would be very interesting for me to know whether you also have problems with twrp-2.8.7.0 not booting.
Click to expand...
Click to collapse
I live right out in the sticks here in England, so my Internet connection is filthy - I'll have to leave it overnight to download all the apps that it needs to reinstall before I'll even try the OTA again. Then I'll see if the latest TWRP works, or it we have to go way back to get a version that plays nice. I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
It looks like tomorrow will be just as much of a learning curve as today
JustinSB said:
I also wonder where we stand on rooting this version too, but I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
JustinSB said:
Peter13337 - I don't know how to fix yours, seeing as you aren't S-OFF & the trick that I just pulled needed it, but I think that you might be able to flash an RUU that matches your own installation exactly. I would double check that though. However, if you know your CID & your modelid is 0P6B10000, then maybe your CID is in the list here http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1 & if it is, then the RUU will work anyway & you'll be laughing.
Click to expand...
Click to collapse
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF
peter13337 said:
Hmm
Found out, that i doesnt have stock OS. I Have CID VODAP102.
And Now ? Nandroid Backups which i Found for that need again S-OFF
Click to expand...
Click to collapse
crap
I've got exactly the same problem after running OTA I'm on s-on
I would be greatful for the solution
Edit: TWRP restore saved my phone
BTW it would be good to know how to apply this bloody update. I've stock rom so no sure why it bricked my phone
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499
Peter13337 - There's a Stock Nandroid backup for your CID here, which would give you (hopefully) a way out: http://forum.xda-developers.com/showthread.php?t=2701376
It may also give you the chance to run the update, then factory reset it to Google will restore everything for you from its automatic backups. Good luck
ritdaw said:
I had the same issue on my O2 M8 and managed to resolve by using RUU_M8_UL_L50_SENSE60_MR_O2_UK_4.20.206.1_Radio_1.25.21331147A1.06G_20.69.4196.01_F_release_414450_signed.exe
I extracted rom.zip (by opening the exe to let it extract and then finding it within %temp%), renamed it to 0P6BIMG.zip and put it on my sdcard. I then booted up the phone with power and volume down and it applied the RUU. Once booted into Android I re-applied the stagefright update and all is working again.
Note: It will wipe the device.
o2 RUU can be found here:
https://www.androidfilehost.com/?fid=95916177934555499
Click to expand...
Click to collapse
:sly: You are a legend :thumbup:
Sent from my Nexus 6 using XDA Free mobile app
After restoring TWRP I tried running OTA again
it screwed the device up again
I've got a feeling there will be wave of similar posts soon
thanks HTC for faulty OTA
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk
tony_5309 said:
Are you all trying to install this update while having TWRP as your recovery? Cause that's where your problem is.
I've put 3 HTC M8's back to full stock and accepted the updates with no problems.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
tim_h said:
Yep, flashing super-su 2.46 worked just fine for me. No problem there ...
Click to expand...
Click to collapse
tim_h, I flashed TWRP 2.8.7.0 without any problems, rebooted it & used it to flash super-su 2.46 fine. It doesn't give me any problems at all & everything works & boots exactly as it should.
m112 said:
no, I flashed recovery from the OTA file, otherwise i would get only red triangle.
I restored the backup by booting to TWRP.
Click to expand...
Click to collapse
Oh ok. Good.
Sent from my HTC One_M8 using Tapatalk
JustinSB said:
I guess that I just need to flash a current supersu from TWRP, when I finally get it working...
Click to expand...
Click to collapse
OK, after flashing the RUU yesterday, as I mentioned above, I left it downloading all my apps overnight, along with the Stagefright OTA (on my reeeaaaly sloooooow Internet connection), rebooted it to load various HTC updates, then installed the OTA. WARNING! The OTA reboots it twice, & the second time it just sits there on the Boot Screen for well over a minute before it boots & goes into the whole "optimizing apps" routine. I was getting really worried that it had all gone wrong again, but thankfully I stepped away from the phone & let it be, & it came good just before I gave up hope. But compare this with what originally happened yesterday (on a rooted, slightly elderly stock ROM), when I also left it alone & it just sat there for an hour, doing nothing... I don't know the answer, but this OTA seems to be really very picky!
One it had installed & rebooted & I was 100% certain that I was in the clear on the OTA, I flashed in the latest TWRP, which worked fine & gave me no problems at all (Note, there have been reports of people having problems with recent versions of TWRP after this OTA, but I didn't replicate those problems). I used TWRP to install UPDATE-SuperSU-v2.46.zip so I am now back up & running rooted again. But because of this I now have a brand new, shiny WWE Stock ROM (as opposed to my elderly, & heavily patched O2 Stock) with the latest firmware, TWRP & SuperSU. I'm happy that it all works, but I have the greatest of sympathy for everyone out there who didn't have S-OFF, as without it I'd have had very serious problems.
Good luck everyone