Database Develop

[Q] CWM flashing without ODIN

Hi,
I'm researching flashing via CWR, ROM over ROM without flashing to Stock via ODIN. Specifically, I'm at Cog 3.02 with "base" Cognition Kernel/Modem thinking about going to Andromeda...both employ Voodoo/EXT4, so shouldn't need to disable lagfix (I think?)...
I read at this link (apologies for spaces, but I'm new so can't post actual links): h t t p : / / forum.xda-developers.com/showthread.php?t=900463
a spirited debate starting about page 4 that flashing to ODIN is effectively doubling your chances for a bad flash, and that recovering a bad flash via CWM is far easier (just try re-flash again...and again(?) until fail back to trying ODIN) than recovering a bad ODIN flash.
If that's true, what prep should I do first via CWR?
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Another question I had was regarding nandroid. I made a nandroid backup right after flashing to Cog. Do I really even need this? Since I haven't changed kernel/modem, wouldn't I be better off just flashing my initial Cog zip file?
Finally thanks to all who make this site kick_ss. Connexion2005's videos are indispensable for a newbie like me. People actually answer questions here, and the Devs suceed in delivering onto us a wolf in (out of the box) sheep's clothing...something AT&T and Samsung have failed to do.
Cognition 3.02 is my first and only custom ROM and DG, you have literally saved me from making my phone a brick the old fashioned way: throwing it against a wall. Running flawlessly since Jan 17th...at the same time, I am eager to see what else is out there, ***safely*** as possible.
Thanks in advance.

Since they are both ext 4 you should be ok.
The rom wipes, I clear davlik cache before flash and after, but there our no good reason as to why
Efs files, do you use kies? If so you may want to back them up, if not don't worry, I have never backed then up
Odin flash is not needed but my opinion is you should know how to use odin prior to flashing. Why panic to figure it out if something goes wrong,?
NANDROID only needed if youare going back to cog and after you have flushed the rom you want to restore settings
I think I got everything you asked

Thank you.
So really just the Dalvik cache wipe in CWR prior to.
Kies...soooo failed ever getting that working, and don't seem to need it.
Yeah I actually flashed ODIN1 unnecessarily prior to my flash to Cog. I was at stock and somehow thought ADW would mess it up...rook. I have build 1006 so good to know ODIN's there if I need it.
Re: Nandroid, but if I kept the initial zip for my flash to Cog wouldn't I just use that? Or does Nandroid do better job of ensuring good flash back to what I have right now?
Not familiar with flushing...Would I be able to restore Nandroid directly on top of ROM I'm switching off of?
Thanks again.

OP,
You'd double the chance of failure if all else were equal. I don't have statistics, but I have no doubt that failures happen far more often with odin flashes, though.
1. Andromeda says requires wipe, does ROM install do this or do I do it via CWR first (wipe data/factory reset in recovery)? How 'deep' is a wipe...what do I need to save prior to this?
2. Wipe Dalvik Cache and/or wipe cache partition?
3. Save /efs folder?
4. Aside from TiBu backup to PC, am I missing anything else to save? I forgot to save my Android ID on my first flash, so it's my understanding I can only get that back via flash to Stock...I'd prefer to only go to ODIN if I have to.
Click to expand...
Click to collapse
The ROM install script does the wipe. This simply means all your apps and data will be erased (your pictures and anything on the internal and any external sdcard will not be deleted).
I never wipe the dalvik cache or cache partition before flashing. I only do that if I'm having issues like FCs (sometimes happens after a bad theme install, for example).
You probably should have backed up /efs before flashing anything, but that's not to say a backup now isn't a good idea. You only need to do this once.
If I recall, you do need to flash 2.1 to get the ID back. I'm not 100% sure there isn't another way.
WRT the nadroid backup, you don't really need it. What I do is keep 2 or 3 good CWM flashable ROMs and the CWM update.zip on my sdcard in case of problems. I also keep TiBU backup of my stuff there (which I also occasionally backup to my PC just in case my sdcard gets wiped for some reason).
One thing I would suggest is to be sure you have working button combos in case you ever need download mode (hopefully you never will, but it's always possible). If you don't have that, there is a clockwork flashable fix or you could just flash cognition or perception once and then flash whatever you want over them (you can do both flashes all without ever leaving recovery). That should fix the button combos since DG's ROMs include a good sbl.bin (I'm not a fan of that inclusion, but it is useful in this case). Since you are running Cog, I assume your download mode is already working.

Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...

Madtowndave said:
Thanks opcow.
Yeah I made sure I could get into d/l and recovery mode with button combos before I even rooted.
So would you ever use a Nandroid backup if you added a different kernel/modem to a ROM? Or would you just go back to the initial zip and SGS Kernel to flash kernel/modem? I haven't done kernel flash...yet...
Click to expand...
Click to collapse
If the ROM you were running when you backed up is compatible with the new kernel then I don't see why there would be a problem. I don't do it, myself, but I'm not sure why. Maybe it's because I have the paid TiBU and I just use that.

Thanks again...
Yeah I bought full TiBu, so obviously that should work for the apps/data.
Did some more digging tonight and apparently Nandroid backup is ROM only, not Kernel...So seemingly would need to be on same Kernel at least to do proper Nandroid restore.
...that being the case, I guess I don't understand why people stress importance of running a Nandroid prior to and/or post ROM flash...am I missing something?

If you like a rom and set everything up but want to try another doing a nandroid allows you to restore once you flash the rom again.
Also good to run nandroid on new flash, so if you play with themes and something goes wrong you can restore

That makes sense.
Showing me newbie-ness since I haven't played around with themes yet...
...Figured I'd at least get 2nd ROM flash out the shoot before playing with kernels, modems or themes...
This thread is helpful for me. I appreciate your time.

This is along the lines of the question that I was going to post so figured would ask here. I too am considering trying out the new Andromeda. I am currently using Cog 3.04 and want to test out the new Andromeda. The TiBu I have right now is from when i was on stock as I just recently purchased this and Cog was my first flash.. Would i want to continue to use that backup when i flash to andromeda, or would it be better to run a full backup with tibu while cog is on there and then flash to andromeda and use the cog backup??
also,, from above, i could possibly just skip the step with odin and go straight to andromeda? or do I need to run odin and put it back to stock before going over to andromeda?
thanks
zug

Hey Zug,
Just flashed andromeda last night via method outlined above...did not revert to stock at all (no odin). Only issue thus far is market only showing very few installed apps under 'My Apps', but I think this is a common issue. Will research solution tonight (I did have some issues getting back all apps from TiBu, but after I restored missing apps twice and rebooted a few times they all appear to be back). Also my simi clock widget comes and goes, not sure why...might clear dalvik cache to see if that helps.
Regarding TiBu, it saves apps and data. It is not ROM specific...you just back it up, then after you flash new ROM you restore missing apps with data (do NOT restore system data).
EDIT: Resolved the My Apps Market issue (only a few were showing after flash) by going to Settings, Applications, Manage, go to Market, Clear Data, reboot. Search is my friend.
i897 running Andromeda 2.0

Thanks Madtowndave.. i might give that a try.. so, since my phone is rooted and what not, i can just go to the guide and start at the portion about puting the new rom on the sd card, rebooting it and what not in recovery and select that zip and flash it right ? (well condensed version of course) and it should all be good?? guessing if this fails can always use the odin and wipe it and go back?
since i added a few new apps, guessing then that i should use tibu and go ahead and reback up everything since this rom does the master clear and then reload them right?? and hate to ask.. but how do I do the nandroid? newbie still to android and i know that just backs up the rom, but is it a app to dl from market? was fishing around in phone and didnt quite see it yet. .but figured i would do a nandroid in case i want to go back to cog.. this smart?
thnx again
zug

I think most of your questions are answered by others in this thread...
One thing I noticed last night is that I only got red (voodoo) cwm recovery menu via 3 button or long press power and reboot to recovery...when I rebooted to recovery via ROM Manager, I got the green cwm recovery menu. Not sure if this matters, but in another forum (on Vibrant phone, our sgs cousin), they said to flash ROM via the red voodoo cwm menu (since cog and andromeda both employ voodoo you can leave it enabled).
Nandroid backup you can do either from ROM manager or in cwm recovery...
Also andromeda wipes the system data, not a master clear...your data on 16 gig internal memory should not be affected, but is very good idea to backup everything to pc per the flash custom ROM guide.
i897 running Andromeda 2.0

Thanks again madtown.. going to give it a try now.. as andromeda just finished DL'ing

Good luck, hope it goes smooth for you as it seemingly has for me...Feel like a bit of a heretic for not flashing to odin first...maybe I'm just lucky.
i897 running Andromeda 2.0

hmm. ok. .so did the reboot to recovery and installed andromeda.. did it take a tad bit for yours to boot into the phone portion after it got to the andromeda screen?? mine seemed like it was hanging and was about to worry.. but finally booted in.. so figured would see if yours did too? .. gonna test stuff out now and restore tibu

Yeah, did for me too...and yes I was worried. Pretty sure this is very normal on first boot into new ROM in general. Like I said, TiBu was a bit cranky for me and required 2 restores and reboots...
Really enjoying this ROM, btw.
i897 running Andromeda 2.0

yeh.. im still doing the install from tibu (getting paid version after tomorrow since payday since im hating have to select install for every app ) .. and then will reboot and test .. though one thing ive noticed that is diff from the video is the lock screen.. in his review it was the lock button and he swiped it up.. mine is set to a puzzle piece by default?? any idea??
edit.. k mine was a 1st time go for apps restored with tibu .this is pretty nice.. it does appear to be a lot faster/smoother than cog so far.. though the Keep the lights on app should keep my bottom buttons on all the time right? least thats what i thought i was from the video and mine seem to still fade out.. even though i hit the app and it said it was enabled..

changing unlock is in settings, display...
Dunno about lights, mine just worked. Make sure service started and reboot I guess.
i897 running Andromeda 2.0

ok.. that was what it was for the lock part.. thnx .. didnt know that was there for those 4 choices.. thought only could do the none, pattern, pw etc..
everything went fine until i decided to load my contacts/sms etc from tibu.. now when i rebooted to add them, i keep getting the message "Sorry, The application Swype (processcom.swype.android.inputmethod) has stopped unexpectedly.. please try again" constantly getting things like that about swype.. any idea what happened or what i need to do?
edit.. sucked it up and re-flashed ;( will just sync contacts and deal with the ones missing for now ;(

[Q] Rom Manager VS NvFlash

(beware, noob here )
So, I've decided to flash CM7 nightly #127 (which seems to be the latest build) to my O2X...
I am completely new to this, so I am going to follow this tutorial: http://wiki.cyanogenmod.com/wiki/LG_Optimus_2X:_Full_Update_Guide
As of now, I've successfully rooted my device using SuperOneClick (so much easier than the method described in CM tutorial), and I made some backups with Titanium Backup.
On the forums here I read you need to also use NVFlash... That it is better that Rom Manager.... But there is no mentions of it in the official CM tutorial... All I found was this http://forum.xda-developers.com/showthread.php?t=1054492 but I'm not sure of what it does, and if it is necessary to use it when flashing CM...
So, what should I do? I already installed ROM Manager and flashed the recovery thingy... All I need is a external sd card (which I going to get today) to make the Nandroid backup, copy the CM zip on it and Flash it...
Is this procedure risky? Do I absolutely need to do it with NVFlash? Is it ok to do this as I already set up Rom Manager?
Any help will be greatly appreciated!!!
Thanks!!

NVflash is not necessary, in fact not even needed. Just need the cm7 zip file which needs to be renamed to 'update.zip' and put it in the root of the sd card. I think it's possible to flash using the internal sd card but I'm not sure. Once you flash that, you should flash the gapps file using 'install zip from sd card' using clockworkmod. Both of these flashing methods using CWM. I didn't use ROM manager, I just booted into CWM recovery and then flashed it. ALWAYS make a full rom backup before flashing and you should be safe and yes it's very safe.

Nv-flash is only needed when you have to restore your phone from some thing close to a absolute brick (when you have flashed some thing wrong or done some thing really bad, and it don't start by any means). That's when nv-flash is used to restore it as an last option. When nothing else works then you use it.
The metod described in the update guide is more advanced and yea its a bit of pain. But at the same time you do gain some practice on things that might be needed to do later in case you have problem with your phones. Things that people here on this forum almost assume that you know how to do. Also it works on all current known firmware for LGO2X. At least follow the steps until you have the adb set up. It might save you the frustration when you sit there and have problem with the phone.
Flashing is easier and faster with the rom manager app. Just remember to move your backups from titanium to the external sd as well. You don't want to lose those backups, right?
Last but not least.
Welcome to the living hell of always flashing the latest firmwares =D
And constant hunt for the highest ver numbers!
PS: Its safe as long as you remember "BACKUP BACKUP BACKUP"

Thanks for the replies
I have now successfully flashed the latest CM nightly build !!! And it rocks !!! I can't believe how sluggish my phone was with the official firmware... It is just crazy...
I had a few issues though:
- When I flashed CM (after data/cache wipe / factory reset), I couldn't find anything on my external SD card... To access the CM zip, I had to navigate to the internal SD card, and there I had a "_ExternalSD" folder... a bit weird...
- I exported all my contacts' numbers on the SIM card before flashing, but CM did not find anything... Hopefully I had a backup on my desktop, and had to manually re create all contacts (good thing I don't have too many...)
- I flashed the latest google App from http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps but the Market is the old version (2.x)
Other than that, I am now a happy CM user... No way I go back to official LG bloatwares!!!

BEC0MM said:
Thanks for the replies
- I flashed the latest google App from http://wiki.cyanogenmod.com/wiki/Latest_Version#Google_Apps but the Market is the old version (2.x)
Click to expand...
Click to collapse
You can flash (with CWM recovery same procedure that you used to flash CM7) latest Market from here:http://www.mediafire.com/temasek (Go to Misc Folder)
Temasek is a very active guy and has many goodies to share !

Striatum_bdr said:
You can flash (with CWM recovery same procedure that you used to flash CM7) latest Market from here:http://www.mediafire.com/temasek (Go to Misc Folder)
Temasek is a very active guy and has many goodies to share !
Click to expand...
Click to collapse
Thanks a lot for the tip
Should I uninstall (somehow) my previous Google apps, or can I just flash the new version on top of the old?

I just saw that a new CyanogenMod nightly build has been released (#146) and I'm eager to update (from #127).
But I am wondering if I need to go through the whole process again (Nandroid backup, clear data/cache, wipe, flash CM, flash google apps)...
Or can I just go to recovery mode (from Rom manager) and flash the latest CM build??
Thanks in advance for your answer!!

NVFlash is used kinda like fastboot for our device (Cyanogen said so in the RC1 forum), a just in case scenario. As if in rom manager gives you an endless bootloop and you can't boot into recovery mode. You can use the NVFlash CWM or rom manager, I actually never use rom manager; I just uninstall it.
As far as the CM Wiki goes, I'm trying to change it to include NVFlash but the wiki people are a bit strict on what gets linked to what...

BEC0MM said:
Or can I just go to recovery mode (from Rom manager) and flash the latest CM build??
Click to expand...
Click to collapse
Yep, that's all you need to do.

[Q] Brick GT-i9000, Can't flash rom using CWM

Hi all,
I've searched most forums and google and nothing found that I can use to revive my GT-I9000.
For background, I just rooted my galaxy using
* SuperOneClick and install TB, etc
* Install CWM by using CF-Root (I prev. have Android System Recovery (3e) and so need to follow addictivetips how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000)
* Take Nandroid backup of original firmware
* Flashed CM7 and CM9 back and forth with no issue.
My problem started when I thought I could just use the nandroid backup of original firmware and remove the bloatware, because CM9 is not on stable version yet.
The nandroid backup can’t boot up, so I goto recovery mode and try to reflash CM7 and CM9. The CWM from CF-Root can’t mount the SD card anymore, thus can’t flash the ROM.
I flash the “hardcore-speedmod.tar” from Full_Update_Guide using ODIN and got to the CWM 2.5.1.0 and can see the SD card, but when I try to flash CM7 or CM9, it says “assert failed: getprop (“ro.product.device”) == “galaxys” and a whole bunch of getprop with Status 7 and installation aborted at the end.
This is the same CM7 and CM9 that I used many times before and still in my internal SD card.
I've tried wipe data and cache but doesn't work. Going to Download mode or Recovery mode is not and issue though
I could try restore all from the nandroid backup but it says be carefull, so i hesitate as not want to make it worse. This nandroid backup is also created from diffrerent recovery (created using 3e and now CWM 2.5.1.0 that's running) - Update: took my chance but didn't work as can't mount
I’m not sure how I can copy other files into the internal SD card as well (in Windows).
I’m at my wits end and have search a lot and tried many things.
Please help
Cheers.
John

Try flashing some older stock android version over ODIN first, than root etc all over again. I had a similar problem just weeks ago and it did work for me, after screwing with it for 3 hours... Will search for some links and post them here, if I find them..

Go look in ask me anything I have the answer, there's a basic guide to save your phone, I have used it a few times and I have saved my phone from the situation u are in.
If you like my posts hit thanks

Last post before I go to sleep with a smile on my face.
For those who might have the same problem, below is what I did.
Did the "[ROM][ODIN]noobfriendly stock jvt firmware (root included)" thread to the T and works the 2nd time. 1st try almost killed the phone with BSOD appearring though.
Thanks for the tip jerdms.
IT'S ALIVEEEE.

[Q] NANDROID restores: TWRP won't boot, CWM corrupts data

Sorry for this being lengthy, I wanted to make sure I gave enough info.
Neither of the two most popular recovery tools are working for me. They both state the backups are successful but the restores have flaws. Is anyone experiencing the problems I am? If so, does anyone know what to do about them?
CWM Recovery Touch (and non-touch): Data restores leave certain things not working. I'm not sure what processes are stopping because it flashes and disappears to fast. I know that it causes the ROM Manager for CWM, Titanium Backup Pro, Google Play, and likely more to crash (disappear) immediately upon opening. Chrome browser *might* bright up the keyboard on the first click but it won't work then it will disappear and not come back (but the keyboard does work in other areas, I use Swype Keyboard). I've tried clearing cache and/or data on all 3, uninstalling them then re-installing via APK and various other things. This occurs regardless of whether a factory reset (data/cache) wipe is performed before the restore. However, if I restore with CWM Recovery *then* do a factory reset, Google Play will work and nothing crashes, nor are their long delays.
TWRP does not boot after a restore. It will pass the initial screen showing the phone model, the phone carrier splash screen, then sit on Samsung with the LED solid bright blue and hang.
My goal is to simply trust my backups. The CWM Recovery problem is workable in a terrible situation since my Titanium backups will get my phone *almost* to where it was (barring widgets, which are pain to re-setup, and a few other things).
Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone? Since I use the Swype keyboard I removed the other once, did a restore with CWM, had the problem so I did a factory reset and my stock keyboard was missing still (I think it's a Samsung keyboard)
App Details:
CWM Recovery Touch 6.0.4.7 (for Samsung Galaxy S3 LTE (GT-I9305))
TWRP 2.6.3.0 (for Samsung Galaxy S3 LTE (International i9305))
Phone Details:
Carrier: T-Mobile (Germany)
Model number: GT-I9305
Android Version: 4.3 (stock from Kies, so I do have Knox and it's disabled via SuperSU 1.91 from chainfire)
Baseband version: I9305XXUEMK1
Kernel version: 3.0.31-2051278
Build number: JSS15J.I9305XXUEML5

Titanium Backup Pro question: Is it normal when you remove a system app with Titanium Backup Pro, then do a restore in CWM for that app to still be gone?
No a Nandroid backup wipes the phone .
make a Nandroid then in recovery format system sdcard data cache .
You now have an empty phone and restoring the Nandroid should return exact same state .
All this reads as you are doing something wrong .

JJEgan said:
All this reads as you are doing something wrong .
Click to expand...
Click to collapse
I hope it is as simple as that. I'm booting up in recovery mode (Volume Up + Home + Power) choosing the backup or restore option, then backing up to the External SD card. Then on the restore I'm doing the same except selecting restore from the SD card (I've re-created the CWM problem 5 times, once was with advanced restore of just data the rest were basic restores doing everything). I'm not really sure what I could be doing wrong.
I have the 4.3 stock ROM before I did any custom stuff to the phone (which installed KNOX). I used chainfire's tar.md5 auto root image with Odin 3.09 in download mode when I root the phone, and I've installed CWM Recovery with ROM Manager and with an Odin tar flash in download mode. The install of TWRP was from an Odin 3.09 tar flash in download mode too.
With regard to the TWRP and CWM Recovery, I'm not really sure how easy it is for me to have messed up that part. Do you have this same model phone? Is it possible KNOX is involved in my issues? Maybe I should downgrade one of the recovery tools?

Downgrade your recovery and try again.

jonesjw362 said:
Downgrade your recovery and try again.
Click to expand...
Click to collapse
That's what I was thinking might be the best solution. Since the flaw in the restores with CWM Recovery are workable for me, I figured I may just wait until I have a need to restore to do that though. Once I do, I'll probably do a bunch of tests until I find something that works solid.
I've already restored my backups and widgets etc. a couple of times and don't really want to do it over again only to test. If there's a way to restore all of that without my having to set it up myself then I'll do it. Right now my Titanium restores don't include wallpaper (except lock screen), most of my widgets (maybe all, can't remember), and I think there was one other thing.

Advanced restore in recovery restore data only .

JJEgan said:
Advanced restore in recovery restore data only .
Click to expand...
Click to collapse
I tried that once, that's why I believe the CWM Recovery issue to be specifically with data. I'm going to do it again right now though and if things are messed up again I'm going to try jonesjw362's suggestion.

Downgrading didn't help (6.0.3.6 had a constant barrage of 4-5 apps re-crashing over and over again during the process).
I tried the following with CWM Recovery Touch 6.0.3.6, 6.0.4.5 and 6.0.4.7:
Factory reset wipe, open and test Google Play (more things break but that's the one I chose to test). Reboot into recovery mode and backup to the SD Card (not the external). Immediately advance restored data only (no wipe). Booted up, Google Play crashed, rebooted back into recovery and factory reset (data/cache) and advance restored data again with the same result.
I didn't try a downgraded version of TWRP (probably won't for now). I'm back to 6.0.4.7 and restoring my backups to get my phone back fully. Hopefully CWM Recovery comes out with a new version sometime in the near future that works for me or someone has some insight into what I can do to fix it with the existing (I'm out of ideas).

Issue Samsung stock 4.3 ROM
I ended up switching to CM 10.1.3 (was going to hold off until 11 was stable) but the Samsung stock 4.3 ROM was destroying my battery. After switching, I tested a NANDROID backup and restore with CWM Recovery Touch 6.0.4.7 (same version I was having problems with). The restore worked as it should, no problems.
End Result: As far as I can tell, the cause of the CWM Recovery data partition problem is due to the Samsung 4.3 ROM.
Edit: I was going to mark the post Resolved but I can't seem to find the drop down to do so (at least not in the same place I thought it was).

[Q] Help Needed With Restore

I hope someone can help me.
I just got my GT-N7000 back from Samsung after a repair to the audio socket. The phone was rooted but Samsung returned the phone to the stock JB 4.1.2 ROM. All was working as it should when I got it back.
Now, I wish to re-root the phone and restore my choice of custom ROM - Ultimate _N7000_XXLT4_JB_4.1.2. v6.0 with all my apps and data. This is the ROM I've been using ever since it was published without issue.
I have managed to re-root the phone with the PhilZ Touch 5 recovery + safe kernel and CWM Base Version v6.0.3.7 which I think is the version I was using before. This part of the procedure appears to have worked correctly and I can now boot into the PhilZ Touch 5 recovery without any issue.
However, after restoring the backup I made prior to the audio jack problem and rebooting, he phone hangs after a few initial swipes through the screens ie I can no longer swipe screens or start apps and the phone is non-responsive. All I can do then is remove the battery. No errors are being reported during the Restore and I've taken care to Wipe data/Factory reset, Wipe Cache Partition and then Advanced >Wipe Dalvik Partion.
I tried the Restore several times but the result is the same. One thing that may be related is that my lockscreen image is not the one I was using when I did the backup. Nor is it the stock image of the book and quill pen that the stock ROM uses (it's a picture of a kid leaping into the air with a big bunch of balloons which I've never seen before). This could mean that something isn't being wiped properly.
Any advice from the experts would be most welcome as I'm out of my depth.
Trevor

Did you check in Philz recovery if the restore of Preload partition is enabled..?

nokiamodeln91 said:
Did you check in Philz recovery if the restore of Preload partition is enabled..?
Click to expand...
Click to collapse
Thanks for the reply. No, I didn't know to check that but will do so in future. I have never encountered that setting before. Is it usually enabled by default?
I think the trouble was that at least one of my backup files was corrupt. I tried an earlier one and this one seemed to have fewer problems so concluded that this was the source of trouble.
In the end, I downloaded a fresh copy of the Ultimate ROM I was using which got the phone fully working again and then let Google download all my apps automatically. So I'm out of trouble now.
Thanks again.
Trevor