I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.
There may be a different way but i fixed that problem by using TWRP which i got in a thread from in the development section. It flashed with no problems. Im not sure what the issue but try a different custom recovery.
Sent from my GT-N8013 using Tapatalk 2
Had this issue also. Flashing from twrp did the trick. So once rooted, twrp installs through goo manager, which is here:
https://play.google.com/store/apps/details?id=com.s0up.goomanager
Read up on the twrp thread in android original development. The touch pad is a little dodgy, but it's workable.
Sent from my GT-N8013 using XDA Premium HD app
suspect_device said:
I rooted my GNote 10.1 with zedomax's method, including flashing CWM recovery and had no issues with it. I wanted to upgrade to JB, and was going to try CM10, but when I tried to flash the .zip file through CWM, it gives me an error message. I have included a screenshot of the error message if it will help.
I know it's not an official CWM, but I'm reading how others have done this and wondered if I somehow made a mistake. I've never had a problem flashing any other phone, and I don't know where to go from here.
Click to expand...
Click to collapse
Here's a flashable CWM from source:
http://db.tt/huUWk7Ty
This may help a bit. I found this somewhere on the web but I can't seem to find it again.
Related
I am having trouble, and since I cant post on the page where this should be asked. (this is my first post) I am asking here hoping that somebody will look...
I have rooted my verizon S3 and it works great... I am however trying to install a CM10 Rom on my device. I have followed the instructions and get all the way to selecting the zip on the sdcard. it finds it, it opens it and after about 20 seconds it gives me a status 7 error and says error in XXXXXX\XXXXX .zip
I have done all the steps perfectly and have formatted and wiped it twice trying this... I even have my backup in place...
I have tried 3 or 4 different cm10 roms and they all give me the same error... What am i over looking?
Thanks
I think you need to flash a CWM/kexec hybrid recovery.
Download the app EZ Recovery and flash the hybrid CWM 6.0.1.0
Sent from my SCH-I535 using Tapatalk 2
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
DROID3R said:
Well if he made the nooby mistake to flash cm10 with a non kexec recovery ..i think he should abandon his hopes of installing cm10 considerong the lost IMEI issue
VERIZON GALAXY S 3
Click to expand...
Click to collapse
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
kwiksilvr said:
That us not the issue... I can get into the CWM recovery just fine.. when I choose the install zip from sdcad and choose the rom it will go through finding the package, then opening the update package and then installing update... 20 seconds later i get some symlinks failed, then I get a status 7 error in the file itself..
Click to expand...
Click to collapse
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Marcismo55 said:
I guess what I recommended did not work?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
You could always Odin back to stock then re-root and install cwm again and restore your backup. May be an easier way not sure. But back up your files on a PC if you do that.
Sent from my SCH-I535 using xda app-developers app
kwiksilvr said:
nope and now im stuck boot looping TWRP after trying what you suggested unsuccessfully.
I appreciate the help... any ideas how I can get out of TWRP back to CWM so I can restore a backup?
Thanks..
Click to expand...
Click to collapse
I don't know how you are blaming me when I specifically told you to flash a ClockworkMod/Kexec recovery... not TWRP.
Seems your issue is lack of following directions. Good luck on solving your issue.
Sent from my SCH-I535 using Tapatalk 2
I have a quick question. If I want to go from TWRP 2.2.0 to CWM Touch is it as simple as flashing the CWM Touch zip in TWRP? I'm a little worried about flashing it within TWRP and bricking my phone. Coming from CWM touch to TWRP I simply downloaded GooManager and installed it within the app but going back to Touch seems trickier.
Why leave twrp what's the problem
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
Why leave twrp what's the problem
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Exactly what i was about to ask
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
hudson2508 said:
I have a quick question. If I want to go from TWRP 2.2.0 to CWM Touch is it as simple as flashing the CWM Touch zip in TWRP? I'm a little worried about flashing it within TWRP and bricking my phone. Coming from CWM touch to TWRP I simply downloaded GooManager and installed it within the app but going back to Touch seems trickier.
Click to expand...
Click to collapse
Yup, its as simple as flashing the zip. Make a fresh backup with cwm after you do it:thumbup:
Sent from my SGH-I727 using Tapatalk 2
I tried to flash Liquid Pre RC1 and got an error. I think you have to use CWM Touch to get it to flash and figured I'd go back to CWM. TWRP has been great but I feel like most all Roms work in CWM Touch but not all work in TWRP.
I've been trying to find a more stable JB rom from CM10 Alpha 3 and heard Liquid was pretty strong. Just tired of all the lockups and not ready to go back down to CM9 yet.
I flash everything in twrp your doing something wrong
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
hudson2508 said:
I tried to flash Liquid Pre RC1 and got an error. I think you have to use CWM Touch to get it to flash and figured I'd go back to CWM. TWRP has been great but I feel like most all Roms work in CWM Touch but not all work in TWRP.
Click to expand...
Click to collapse
I've found it's the exact opposite. TWRP and CWM Touch are slightly different in how they work; you sure you're not hitting the wrong button by mistake?
Not sure what happened but I tried flashing it once and it failed. Re downloaded the zip and tried a second time with the same error. The MD5 checked out and everything. I've flashed many times with TWRP with no issue so I'm not sure what's going on. Can anyone confirm that Liquid flashes successfully in TWRP? Not counting out user error but I've never had an issue flashing anything.
hudson2508 said:
Not sure what happened but I tried flashing it once and it failed. Re downloaded the zip and tried a second time with the same error. The MD5 checked out and everything. I've flashed many times with TWRP with no issue so I'm not sure what's going on. Can anyone confirm that Liquid flashes successfully in TWRP? Not counting out user error but I've never had an issue flashing anything.
Click to expand...
Click to collapse
What error is it returning
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
What error is it returning
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Finished running boot script
E: Unable to open zip file.
Error flashing zip '/sdcard/goomanager/>_Liquid....
I had issues with that use twrps built in file manager and change the permissions Chmod 777 it was once but it may help
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Probably a stupid question, but have you tried re-downloading Liquid? MD5 checks don't always reveal all flaws.
T.J. Bender said:
Probably a stupid question, but have you tried re-downloading Liquid? MD5 checks don't always reveal all flaws.
Click to expand...
Click to collapse
I did, tried downloading on the phone once and on my pc. Both failed.
First off, I apologize if I missed a thread that already talked about this. I tried to search for one, but I couldn't find one that actually helped me.
Ok, so I rooted my phone and unlocked the bootloader with Causal. Then I used GooManager to install TWRP and it is the latest version.
From there, I booted into recovery and did the following:
1) Did a backup to my external SD card
2) Factory Reset/wipe cache and Dalvik cache
3) Install ROM
I have tried both Carbon ROM v1.8 and Cyanogenmod 10.1.2. I have downloaded them on my computer, made sure my connection was good, matched up my MD5 sums, and I know that they are for my Verizon Samsung Galaxy S3 (d2vzw).
Once I thought the ROM would almost be installed, it would tell me it failed and tell me that there was a failure with executing binary updater. So from there I tried to use my Nandroid backup to restore my phone back to it's previous state. But when that was almost done, It gave me a failure as well. Unfortunately, I'm not even sure what the error actually was. So I used Odin to flash it back and blah blah blah.
So does anyone has any idea what I could be doing wrong? Or does anyone have any tips?
This worked for me.
http://forum.xda-developers.com/showthread.php?p=30386309
http://forum.xda-developers.com/showthread.php?p=33701313
Sent from my SCH-I535 using Tapatalk 2
eXPilce said:
This worked for me.
http://forum.xda-developers.com/showthread.php?p=30386309
http://forum.xda-developers.com/showthread.php?p=33701313
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thank you, but I already know how to flash it back to stock and everything. I just have an issue with getting my roms to actually flash and to have backups that will actually restore instead of handing out errors left and right.
I had the same type of issue. When the new ROM didn't work, trying to revert didn't flash. Read that this would reset back to STOCK and retried the new ROM flash.
1st link specified to follow EXACTLY. I messed-up one step. But once I got it right. All became great to go.
I thought as you have, just go with it for the fix.
Sent from my SCH-I535 using Tapatalk 2
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Ok, Ive unlocked my bootloader, installed CWM, rooted my device and checked that it worked, and when I go to the boot loader and select recovery it takes me to CWM. Ive made backups from it and and they restore fine. I even installed a custom kernel and it worked because noFrills let me OC/choose a different governor. Yet from the three ROMs Ive tried so far, they install fine, no errors from CWM, but when I boot up it just gets stuck booting forever. Ive tried wiping everything, Ive tried wiping some things, heck I even tried wiping nothing but I still get the same issue. Id really like to try a new ROM now that I went through the trouble of voiding my warranty, so please try to help me. Thanks in advance, alexbenh
Same here
Gonna try out this guy's method real quick except with CWM
http://forum.xda-developers.com/showpost.php?p=49668571&postcount=5
I know this seems obvious, but are the ROMs you are flashing specific for your device?
Sent from my ST18i using xda app-developers app
yes, I have the Moto G XT1034 and have flashed ROMs before on my old galaxy exhibit and never had any trouble with that
Join the club, same here, done everything right but no custom rom joy for me
Sent from my XT1032 using XDA Premium 4 mobile app
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
WOOOHOOO, I reinstalled the stock 4.4 firmware and everything, I couldnt root it with superboot so I just skipped the rooting step. Then I flashed CWM through the bootloader although I decided to take a risk and instead of "fastboot flash recovery recovery.img", I did "mfastboot flash recovery recovery.img" just to see if it would change anything. Not sure if thats why it works for me now, but its worth a try. Good luck to the rest of you who have this problem.
lowrider262 said:
If you're flashing a kitkat ROM, make sure you're already running KitKat. If you're still on 4.3, then fastboot flash the stock 4.4.2 image first, then try custom roms
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Yes, I was already running the stock 4.4 ROM the only differences was that I had a custom kernel which could possibly be an issue, but I wouldnt think so
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
BBOXPT said:
http://forum.xda-developers.com/showthread.php?t=2620060&page=2
Click to expand...
Click to collapse
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
alexbenh said:
huh, I had not tried using TWRP, but I thought CWM had a fix permissions command as well.
Click to expand...
Click to collapse
My experience. I tried CWM then loaded a Rom, the first one I tried being CM11 = Bootloop, Then I tried several other Rom's and always the same result, spinning on Bootloop
I then put the phone back to stock firmware 4.4.2 and tried TWRP version TWRP2630, no joy even the bootloader wouldn't work right.
Finally put the phone back to stock AGAIN (now getting frustrated!) and tried installing TWRP2631 using fastboot. That did the trick, now all ROM's load and run fine. This version of TWRP appears to be working well. Backup/restore works, and no problems at all.
Other's report CWM works well, but not for me unfortunately.