I have Verizon Note 3, with Jasmine Rom and TWRP recovery.
I have posted a question about my phone started showing some sh** dialog over and over about facebook app not responding.
Till now i havent found any solution to it. So, seems as last resort, i will flash again with jasmine rom (if there is anyother better do tell me). But before that, i want everything (EVERYTHING) to be backed up, text messages, my games data, my installed softwares, cracked versions, everything. Is this possible???
Anyone coming to save the day????????
First you need to state whether you have a safestrap ROM or a unlocked bootloader and real custom recovery. Huge difference.
You should also bear in mind that if you are suffering from a corruption issue somewhere, a "complete" backup and restore merely records the corrupted data and restores the same corrupted data. What exactly would you gain that way?
Your hypothesis suggests you think a fix could be acheived by "refreshing" just the ROM (i.e. the /system mount). If you have any customizations in there, they will be lost unless you can identify them and re-create them after you have "refreshed" the /system mount. If you are unable to do that, you will lose them.
If you thought that you were unable to identify those changes and were going to plunge ahead and try anyway, theoretically you would get the same result by just flashing /system only and wipe the /cache mount without doing any backups at all. EXTREMELY RISKY MOVE THOUGH IF SOMETHING GOES SIDEWAYS. (You should always assume that something will go wrong and make backups... and get those backups off the phone in case the entire device needs to be wiped in a "start from scratch scenario)
Note that your apps have been under constant update all this time since Jasmine's release while it (Jasmine) has been standing still. There's no guarantee that what you are observing are not merely bugs in Jasmine uncovered by new application code.
A Herculean, careful and diligent backup & restore operation might fix nothing.
Related
Hello,
I have a MB525 that I purchased retail in the United States so it was never locked to any carrier. Currently I'm a T-Mobile customer and have no interest in changing that. I have to say I love this phone, mainly because it seems indestructible. Even years later the battery life is still good, but the stock 2.2.2 Froyo has become something of a problem because many of the Apps I would like to use have started requiring newer versions of Android.
I can't stay in the past forever, but I'm not quite ready to give up on this device so I started looking around at my options, and would you believe I found lots of other people who have this device and have worked very hard to produce updated Android OSes for it, and who have reported reasonably good success updating the device. I figured, Its already out of warranty, so I can't void a warranty I don't have. I also figured I'm a reasonably intelligent individual and have enough experience with Unix like operating systems that even if I get in trouble, I'll be able to ask the right questions to get out of trouble. Guess what point I have gotten to?
I started following the guide wikiDOTcyanogenmodDOTorg/w/Install_CM_for_jordan The Framaroot Gimli exploit worked great. I installed bootmenu 6.1 and Clockwork Mod Recovery. Fantastic. At this point, I was able to enter CMR and backup my mostly still factory ROM. If I understand correctly this is a nandroid backup. I copied that backup off of my SD Card to my PC. From this point I felt reasonably confident I could try things and in a worst case scenario restore to this backup.
Now I happen to have a stock ROM that seems to be a bit rare online, Blur_Version.34.4.806.MB525.Latam.en.01, so I figured at this point I'd do a service and create a backup using CWM after having done a factory reset. So I booted into the stock recovery, did a factory reset, restarted, and the OS was in a like new state. Perfect. Rebooted into CWM, and made a second backup of the factory reset state. I copied this off the SD Card to the PC. Now I figured I was ready for real fun.
I figured, I might as well put the most recent Android version I could find that people were reporting success with. This appeared to be @quarkx Kitkat build. The thread is almost a year old and has 500+ replies and so I guessed that most of the major kinks would have been worked out by now. I followed the directions on quarx2kDOTru and installed cm-11-20141015-NIGHTLY-mb52x.zip from Quarx2k.ru, and low and behold it worked. CM11 booted and everything looked great. WiFi worked. Gapps worked. Play store started installing my apps.
There was one small problem. The phone refused to connect to T-Mobile at all. So I did the reasonable thing. I searched and learned about base band switching, and consulted T-Mobile on what would be the correct APN settings. Occasionally it would connect to AT&T for emergency calling, but it never connected to T-Mobile no matter what I did. From my home I was normally getting excellent signal on the stock ROM, so I am reasonably certain that the actual signal in the area was not the problem, and that this had to be some kind of configuration or software issue. A wiser person probably would have gotten on the forum and asked for help, but wisdom be damned, I wanted to do it for myself.
So more research and at some point I thought, Well, I'll go back to the Stock ROM so the phone will be usable again, and I'll take another crack at CM11 again later. It was at this point that I realized that CMR had been replaced with Team Win Recovery Project. This recovery looked to be more feature rich and easier to use, so I accepted that. I backed up my CM11 install. then went to restore my original backup. Well you might have guessed by now that TWRP and CMR don't use exactly the same backup formats. I saw no obvious way to get back to my backup and couldn't find information that would allow reinstalling CMR. This was the first warning signal I foolishly ignored.
At this point I started looking around for slightly earlier builds of CM11 that might not have had the the problem connecting to T-Mobile. Here is where things get fuzzy about how things got into this state, since the work was spread over two days at this point. Somehow between all the flashing backing up and restoring, the device got to a state where the OS never actually finished could do here is yank the battery and reboot into TFRP.
At this point, attempting to restore would just result in the messages 'E: Unable to mount '/cache' and 'E: Unable to mount '/data' in the terminal. So After searching around I learned that I probably needed to format /cache and /data because somehow they were broken. Terminal commands, I can handle this. I start reading up and find the correct command and parameters for the format, and I type into the terminal inside TWRP and low any behold format can't be found. I start looking around the directories in my file system from inside TWRP and I've got a complete directoty structure, but no files in any directories other than on /sdcard. Well fuuuu.
Not sure what made me even try, but copying any file from my sdcard into /data somehow put /data into a state where a TWRP restore would work. So at this point I was able to restore the CM11 backup, and my phone now boots into CM11, 11-20141007-NIGHTLY-mb526. But.... the cellular network still doesn't work.
But now I am wiser and I am back to the point where a wiser person would have asked for help. So... Help?
Is 11-20141007-Nightly-mb526 the best rom an appropriate rom for my device? I'm guessing I missed something because other discussions on this forum mention newer builds, and also, my device is definitely a 525 not a 526.
Is my baseband version EPU93_U_00.60.03 right? The baseband selector allows me to pick from three T-Mobile settings: 3.4.2.-107-4, 3.4.2.-107-9, and 6.xx.0, none of which seems to allow me to connect to the cell network.
Thanks in advance for any assistance offered.
Sorry for the long potato.
Here is what I did to fix my problem.
I started with the original backup of my stock rom, and I used the unyaffs.exe from this thread: http://forum.xda-developers.com/showthread.php?t=1199416 to convert my CMR backup into individual files. I then went into those files, and found \system\etc\motorola\bp_nvm_default\ and pulled out the original radio firmware from my device. From there I used advice from several pages to create my own update.zip, copied it to my SD card and I booted into TWRP and installed the zip there. Reboot and Voila, It connected right at startup to T-Mobile with the normal speeds I get from my home.
Bonus, I attached my zip in case anyone else comes across this and needs it.
My Device has an FCC ID of IHDP56LC1 if that helps anyone match their hardware.
Hi all,
Some time ago i asked, and received, some support on these forums on how to properly carry out a nandroid backup... following the sound advice i got, i carried out my backup (using TWRP for the record, with all the options checked), and stored it away for a rainy day... said day came yesterday, when i messed up my system and rendered it instable (i tried to manually delete the dalvik cache directory in order to free up the 2,5GB of space it was taking)... since i knew there was i high chance of this ending in disaster, the last thing i did before the delete was carry out another nandroid, so i could easily return to where i had left off... how wrong i turned out to be
as soon as i the system became instable following my experiment of deleting the d. cache directory, i recovered the latest nandroid (i.e. the one i had made just hours before) and everything seemd to go smoothely until the first reboot... when the following happened:
- first reboot after recovery took ages, much like the first reboot following the flashing of a new rom... not the end of the world, but that was the first sign that all was not well
- the status bar disappeared, and there was no way of making it come back (i.e. nothing to do with the launcher, i typically use apex but i i tried switching to both nova and touchwiz which i also kept up to date but the stats bar was nowhere to be seen)
- even if not having a status bar with all the info on it is acceptable (which of course it isn't, but lets just say), the sytem became completely instable after 5minutes of operation... with each app taking turns to shutting down until i kept getting the message "system UI has closed" over and over, to the point that doing a reboot was challenging since i barely had the time to press on the screen between instances of this bloody error message appearing...
...i did of course try and return to my older nandroid backup, but... lo and behold... exactly same behaviour...
so now i have resorted to formatting the internal memory card and flashing a new rom and basically starting over... just what i hope the nandroid would spare me basically :/
question is: does this sort of error sound familiar to anyone? can someone give me a tip maybe on what i may have done wrong?
any opinion, tips& advice much appreciated
I have the exact same problem. It happens on TW Lollipop ROMs. Haven't found a fix. I'm using Philz Touch Recovery and the old no knox bootloader.
Anyone? I have researched this but cannot find any similar problems reported... it can't just be me and pavelcheto...
Maybe it a recovery fault. Faulty backup or faulty restore.
No problems with my older backups. I restored my KitKat TW backup, working fine. Restoring CM12 backups also works fine. I've looked for a new recovery, Philz is discontinued, CWM hasn't been updated for a year and I really don't like TWRP.
I use TWRP 2.8.3.0 and never have (and hopefully never will) encountered any issues with restoring backups.
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
platypus78 said:
Considering i recovered 2 separate backups for a total of 3 times (i tried recovering the first backup twice) i doubt the issue was with the recovery itself... however since pavelcheto had no issues with the kk recovery maybe it could be lollipop related?
Anyone successfully recovered a lollipop nandroid backup?
Click to expand...
Click to collapse
I recovered my lollipop gpe backup a couple of times without a problem.
Data encryption may cause restoring problems.
I have restored CM12 backups (based on 5.0.2) serveral times, no problem there. I've had issues only with TouchWiz Lollipop ROMs, I have tried different custom roms, all get bugged at restore.
pavelcheto said:
I have tried different custom roms, all get bugged at restore.
Click to expand...
Click to collapse
Just to make sure I understand correctly : you mean all TW custom roms you've restored have had problems?
Wonder if anyone else has managed a bug-free restore of a 5.x TW?
Yes, but only on Lollipop. KitKat TW roms restore just fine. I am using Philz Touch Recovery. I have tried 3 different TW Lollipop roms and they all fail to restore properly. No wallpaper, black wallpaper and no status bar. And after a minute or two System UI starts crashing. If then I do factory reset from recovery and the rom starts normally (welcome guide and stuff) and works fine.
bumping this thread because i cant seem to find a solution for this anywhere.
TheAwesomeBit said:
bumping this thread because i cant seem to find a solution for this anywhere.
Click to expand...
Click to collapse
There's no solution for this as per comments above. TW LP is not restorable. You can flash a new lollipop ROM tho'
Sent from my GT-I9505
I need help getting a logcat while my phone is shutting down and also while it is booting up.
Here is some history of my problems which will explain why I need to do this.
Note 3 sm-n900v
Currently running OF1 firmware and Alliance t-mobile rom
Rooted and unlocked bootloader TWRP recovery
I got this phone used for cheap and thought it would be an easy fix. I started with a clean odin of the stock OF1 firmware to put it in factory condition. Everything went great and had good signal and 4G LTE ran smooth and set up with no problems.
After the first time I rebooted the phone I had no signal. Checked About phone and my IMEI, baseband and serial number were gone.
I reflashed the phone in odin and everything was back. Another reboot and all is gone again.
I have tried different roms after rooting including some AOSP roms and always the same result.
I have checked to make sure that the phone wasen't a victim of the "NVbackup/restore" bomb and my NV partitions do not seem to be corrupted.
When I power off the phone it seems to take a long time to shut down (1-2 min.) so I suspect that something is being rewritten on the phone during a reboot. This is why I need to get the logcats so I can have some wizard/guru/hero/Android God read them for me and hopefully tell me what is happening to the phone and how to fix it.
I can work in ADB if someone would be kind enough to give me the commands needed to get the logs and where to post them or who to send them to for help.
I'm old but not stupid. Just an old fart that needs some help getting across the Android freeway.
Thanks in advance to anyone that can help.
Loaderboy
"got the phone for cheap" - did you call Verizon and inquire if the ESN was blacklisted?
If not, I would inquire before trying anything else.
(for shutdown; assumes you are rooted.)
Code:
adb shell
su
cd /data/local/tmp
cat > watcher.sh
#!/system/bin/sh
cd /data/local/tmp
logcat -c
logcat -v threadtime > watch_shutdown_logcat.txt 2>&1
^D
chmod 755 watcher.sh
./watcher.sh 2>>/dev/null &
exit
then reboot.
I know it's a pain in the butt to re-Odin the phone & re-root in order to run a single experiment, but you might also try the reboot cycle with the phone in airplane mode (or better yet in a location where you know you do not have a cell signal) to see if that has an effect.
Does the rooting process require a reboot? If so that would seem to be a chicken-and-egg problem - if your IMEI gets wiped on the first shutdown, then it would be hard to install a new ROM to find out whether it is carrier ROM software that is performing the changes.
Other possibilities: an intermittent hardware problem that is being mis-diagnosed as software behavior. If this were the case, occasionally the problem would appear even after a fresh Odin flash.
Other ideas include performing checksum (md5) signature comparisons on the stuff in /firmware and /firmware-modem before and after reboot to see if anything is changing, e.g.
find /firmware /firmware-modem -type f -exec md5sum {} \;
PS This advice doesn't mean I'm planning on helping you examine your logcats, but you should feel free to put them in a pastebin and provide the link here. You might want to scrub the file of any personal or device identifier information before you do that.
No the phone is not blacklisted, first thing I thought of. The problem happens on Verizon and Tmo roms alike.
The last time it lost the IMEI and baseband I got it back when I flashed Alliance rom but I havent rebooted since. The phone didn't lose root so I think I can experiment without odining the stock firmware and rerooting.
I will get the shutdown logcat and see if I can find anything before posting it.
Thanks so much for your quick reply.
The observation that it is ROM-independant is significant.
That would suggest that it is less likely to be due to a piece of application software unless all the ROMs carried the same application/code, or the functionality was coming from the TrustZone, or perhaps code in a kernel shared in common between ROMs exhibiting the behavior.
You seem to be suggesting that it can be corrected by simply flashing a new ROM. Normally that only involves the /system, /cache, and /data (when you wipe) partitions not the /firmware or /firmware-modem partitions.
It's just one hypothesis, but my money is on flaky hardware that causes a failed initialization during boot up. Evidence for that might be:
(1) boot the phone several times after you lose IMEI, both warm reboots as well as shutdown/boot and shutdown/battery pull&reinsert/boot. If it comes back up during any cycle... flaky hardware. (Note also that if you put the phone on the charger when it is "off" it actually performs a "silent boot"... I think the bootloader does this by providing the kernel with an alternate (skinny) ramdisk. In any event, many pieces of hardware could be fully powered up & kernel initialized when doing this, so potentially this could affect flaky hardware. Just be aware of it so you are correctly appraised of "how many time did I boot this thing?")
(2) Alternatively, NOT recovering service in a reproducible manner (e.g. flash & boot a ROM 4 or 5 times using the exact same procedure and one of those times service is not restored) also would be indicative of intermittent hardware troubles.
(3) if you have TWRP installed and the problem was due to some stateful behavior (e.g. something recorded into a file on the previous boot), performing a full wipe of /data might alter the behavior as that is the most likely place for it (esp. since you say that ROM flashing cures the problem). Try wiping & booting several times - does the problem come & go?
well I rebooted and lost signal. I then booted to TWRP and wiped data and still no signal.
I did this 3 times and no signal. Then I wiped dalvik /art cache and cache without wiping data and signal is back.
Getting closer. I will reboot to lose signal and then reboot to TWRP and wipe each one seperatly to see if I can narrow it down.
Stay tuned.
Wiped dalvik/art cache and signal is back. Tomorrow I will restore my stock backup and see if it works on that as well.
Thanks for giving me the tips on where to look. If it works on the stock rom I will then have to try to find out what is causing this to happen.
... and the result is?
.
bftb0 said:
... and the result is?
.
Click to expand...
Click to collapse
Flashed stock backup and everything was there. reboot and it's all gone. Boot to recovery and wipe dalvik cache and baseband IMEI etc. all back.
Sorry for the long break but spent the weekend moving a friend.
Sent from my SM-N910P using Tapatalk
loaderboy said:
Flashed stock backup and everything was there. reboot and it's all gone. Boot to recovery and wipe dalvik cache and baseband IMEI etc. all back.
Sorry for the long break but spent the weekend moving a friend.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Looks like you have your work cut out for you. Somehow I doubt you are going to find something meaningful inside of /cache, but I'd look there first since that is likely to be the simplest in terms of effort.
I suppose you could try a binary division method of manually deleting half of the .dex files and the corresponding entries in places like
/data/system/packages.xml
/data/system/packages.list
/data/system/install
/data/system/users/0/package-restrictions.xml
/data/system/users/0/runtime-permissions.xml
and then iterating (the divide the right group by half) but thats gonna get tedious fast - and possibly just cause bootloops or hangs.
Frankly, I still think there is an underlying bit of flaky hardware - if the ESN was clean, what would be the point of software being intentionally coded to "turn off the phone" on an otherwise clean ESN device, and a completely vanilla ROM (i.e. no personalization by initialization of a Google account credential, no market apps, etc).
If you decide to use logcat and you discover that you need to launch on boot because the logs are rolling over before you can manually run a logcat (very likely because of the long Dalvik rebuild times), you will either have to choose a ROM which has a hook for auto-starting a script (e.g. CM13 userinit.sh files), or you have to re-pack the boot image to execute a one-shot service during late boot (customizing init.rc), making sure to put the logcat invocation into the background so the service doesn't block init. In both those cases, make sure you write the log to someplace like /data/local/tmp - you can't use /sdcard as the automounter tends to mount it quite late in the boot.
good luck
So this started on Saturday. Motorola has been nagging me all week to update to Nougat and I have declined due to lack of XPosed compatibility. On Saturday, I turned my phone on only to see the update in progress. Don't know how they did that unless I unconsciously touched confirm with my butt at some point.
I have a Nandroid backup so I thought the solution would be simple -- restore the backup and get on with my life. After restoring the backup, the WiFi no longer works. On the searching for networks screen it appears to be on. But on the "more setting" screen, it is off and will not turn on.
I had this problem once before and reflashing the modem fixed it. I've flashed it three times now and it is still not fixed. What else might be the problem? Thanks!
pjcamp said:
So this started on Saturday. Motorola has been nagging me all week to update to Nougat and I have declined due to lack of XPosed compatibility. On Saturday, I turned my phone on only to see the update in progress. Don't know how they did that unless I unconsciously touched confirm with my butt at some point.
I have a Nandroid backup so I thought the solution would be simple -- restore the backup and get on with my life. After restoring the backup, the WiFi no longer works. On the searching for networks screen it appears to be on. But on the "more setting" screen, it is off and will not turn on.
I had this problem once before and reflashing the modem fixed it. I've flashed it three times now and it is still not fixed. What else might be the problem? Thanks!
Click to expand...
Click to collapse
First off, unless you signed a non-disclosure as part of MFN, you didn't get Nougat update (probably), it was just a security update... odd that it would even take since you have root and Xposed (and maybe TWRP) it would be impossible to apply to the update. Aside from that, IF you did get an update applied, then restored a Nandroid that means your boot image (kernel) and radio versions are out of sync... You need to either flash the modem package that matches your kernel or restore the nandroid you did before the restore.
acejavelin said:
First off, unless you signed a non-disclosure as part of MFN, you didn't get Nougat update (probably), it was just a security update... odd that it would even take since you have root and Xposed (and maybe TWRP) it would be impossible to apply to the update. Aside from that, IF you did get an update applied, then restored a Nandroid that means your boot image (kernel) and radio versions are out of sync... You need to either flash the modem package that matches your kernel or restore the nandroid you did before the restore.
Click to expand...
Click to collapse
So you're right.
The immediate reason for doing the Nandroid restore is because the update got my phone stuck in a boot loop. After the restore, it started pestering me to update again so I took the opportunity to look into it a little more closely and it is a security update, not Android N.
But that then raises another question, or two actually. I was under the impression that the Nandroid backup stored the entire contents of memory. Are there some bits, like the wifi modem, that aren't included? Also, if I unroot long enough to take the update, will that restore the wifi modem? I assume an update would check the integrity of system files.
Thanks for the quick reply. I don't come to xda often but it is always informative.
pjcamp said:
So you're right.
The immediate reason for doing the Nandroid restore is because the update got my phone stuck in a boot loop. After the restore, it started pestering me to update again so I took the opportunity to look into it a little more closely and it is a security update, not Android N.
But that then raises another question, or two actually. I was under the impression that the Nandroid backup stored the entire contents of memory. Are there some bits, like the wifi modem, that aren't included? Also, if I unroot long enough to take the update, will that restore the wifi modem? I assume an update would check the integrity of system files.
Thanks for the quick reply. I don't come to xda often but it is always informative.
Click to expand...
Click to collapse
A Nandroid doesn't include lots of stuff... It is 5 or so of 25-30 partitions, typical system, boot, data, cache, and sometimes recovery and a couple others, it doesn't include radios, persistent data (like IMEI or serial numbers), internal storage, bootloader, and lots of other stuff.
You cannot just "unroot" and take an OTA, for modern Moto devices your boot image and system partitions must be pure and untouched (the script can even tell if system was ever mounted r/w even if nothing has been changed) and you must have stock recovery. You must return to stock to take an OTA, there are several threads discussing ways to do it here.
Have had my OnePlus 2 since 2015, and it's been a solid performer up to today.
I had the crDroid ROM (8.1) installed, along with Magisk, and it's been working fine for over a month with zero issues.
Today, I went to remove an app that was being troublesome, and then rebooted. And it just bootlooped. Animation is playing, but that's it. It sits there for 10-15 mins doing nothing. I hold the Power button to shut it down, and then try booting again. Same thing, just a straight bootloop for 15 mins. So I reboot to recovery (TWRP 3.2.1.0) and flash the Magisk uninstaller, to see if restoring the stock boot partition would help. It didn't, and just gave the same bootloop. So I go back into TWRP, wipe /system /cache and /dalvik and reinstall the ROM and gapps. Reboot. Same bootloop.
Now I'm starting to get a little concerned. Right now I'm restoring a backup from 10 days ago that I made before I last updated the ROM, but assuming this fails, does anyone have any good ideas? I'm not an expert, but I'm not a novice either, and this isn't making much sense. Unless my OnePlus 2 is getting ready to check out, which would suck...
idk if you had any mods like kernel or whatever or what app you removed (and if it had root acces) but first make sure you are on latest twrp, then try to clean flash a rom like normal. try to boot it it should work.
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Gaffadin said:
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Click to expand...
Click to collapse
This means that a date/time overflow occurred in your system
You restored a backup from 10 days ago, I'm assuming an older version of the ROM? So the newer version has an overflow bug
Even if nothing changes on the system your system time is always changing and if the ROM or kernel is somehow messed up then this value can cause an overflow and if a security module of some sort (like fortify_source or stack_buffer_protection) finds out about the overflow it can prevent boot from happening
Note: below example not completely valid in the real world, I've removed some stuff and is just for clear understanding.
Let's elaborate, "signed int" accepts values from -32768 to +32768 (0 inclusive)
What do you think happens when a value below -32768 is passed? That's an underflow and it's not defined what would happen below that limit (actually stuff does happen but see below notice)
If you pass a value over 32768 you cause an overflow
Note: I'm not going to go into details about what exactly happens. This would add too much information and cause more confusion than it would clear
What does this have to do with the date? Well every second your system date increases and if you got one of these limits you're going to run into problems
This is the only possible explanation for what could have happened
Thanks for the explanation. i think I understood most of it.
The backup from 10 days ago was from an older version of the ROM, though I have since installed the latest ROM version on top of the restored backup without issue, as I did when I first made the backup.