To cut to the chase…
My G5 (XT1671 32GB) has no IMEI. The one smart(?) thing I did before starting to screw around was make a backup with TWRP - 2 backups actually, one stock, the other AtomicOS. When I try to restore the backup I get an "unable to locate partition by backup name" message for these partitions: efs1, efs2, logo, oem. I gather the efs partitons are the ones that correspond to IMEI and other modem related things.
Is there any way to bring these partitions back? I've reinstalled the stock ROM (a few times now) and that doesn't seem to restore them (however when I try restoring I always get an error message on this line "fastboot flash partition gpt.bin"
Is restoring even going to fix the IMEI? From what I've read those backups are supposed to be an exact clone of the device - sort of like using Macrium to make an image of your PC (btw the backups include everything, whether it was needed or not ~6-7GB in size)
Cheers
Once you've flashed an oreo rom, imei will always be 0 when reverting to stock.
You could try this though: https://www.youtube.com/watch?v=XmKg84IXEbo
Going back to stock isn't the issue with the IMEI, it's whether you can turn off auto-update fast enough no to let an OTA update through (at least that's what screwed me)
I did run through the video you linked before hand. Kinda worked. Got 3G back, but when I tried the steps to restore 4G I just lost my IMEI again.
Still doesn't answer why I kept getting the missing partition message in TWRP. I do have full backups so you'd think restoring my efs would be the answer.
Turns out that was the answer… I have no idea what exactly happened but after trying the steps in that video again I decided to restore my AtomicOS backup (prefer it to Pixel Experience) for WIFI usage if nothing else. I got the same missing partitions message and this time somewhere during the restore process TWRP crashed/rebooted (could only boot as far as the bootloader menu). When I booted back into recovery to try and restore again I finally had all the options to restore my efs/logo/etc.. So I restored everything available (minus "system image") and am back to a fully functional AtomicOS.
I'm thinking I could also restore my stock backup now without problem now since I made it way before I ever tried any 64bit/Oreo roms. But ATM I don't want to tempt fate. Besides probably better to wait until Moto/Lenovo officially launches their Oreo update before considering stock again
Related
I have used Clockworkmod to backup and restore my Samsung GS4 Many, Many times. I have never had any problems restoring any previous backup before. Today after my phone updated an app from the play store, it started acting funny, so I made a backup, (like I have many times before) and after it was completed (no error messages) I proceeded to recover a previous backup that I restored a few times before, and it ended in a "Error while restoring /system!
I tried rebooting the phone and it just hung in the boot animation so I booted back into the recovery mode and again tried the same restore image, but same error. I then tried one that was done before the one I was having problems with, and got the same error. I have a hard time believing that all these backups have suddenly become bad! They ALL PASS THE MD5 CHECKSUM so they must be good!
UPDATE:
I failed to mention, that the phone was UNLOCKED when I made the backup and tried to restore it...
Not sure if that has any bearing on the result. I can restore an older version that was not unlocked when I made the backup, but it's waaaaay back and I lose so much of my data if I have to use that.
I'm not so sure what to do now. My phone is not too useful if it cannot be restored.....
Any help on what I can do to recover would be much appreciated.
Mahalo! (Thanks!)
Running stock 4.2.2 - Rooted Running another restore again. I wiped all the stuff I dare do and re-running the recovery (it takes a while to do)
Will post results after this one succeeds or bombs. :<(
I had this problem once with my s3.. I couldn't figure out now to fix it but what I ended up doing was reflashing my ROM from a clean state and then just restored the data from the backups in recovery.. All your apps and data will be restored except your system apps or mods
Sent from my SGH-M919 using Tapatalk
I am using a T800 (galaxy tab s 10.5 wifi) where TWRP is installed.
Prior to flashing an android 6.0 rom, I made a backup of the (stock) 5.0.2 rom. When trying to restore this, it fails on writing the data partition. Next installed the rom, ran it for a day or two, and created a backup from this as well. With two backups now available, none of them can be restored on my device. Every time it fails on the data partition.
Is there a way to get around it?
Twrp version?
Actual error?
Yeah, I know, the info is somewhat blurry.
I have done it one more time, with TWRP 2.8.6.2. The restore gets stuck at about 60%, busy with the data section. It is saying "E:extractTarFork() process ended with ERROR=255.
It did succeed in restoring the system partition.
musicmannetje said:
Yeah, I know, the info is somewhat blurry.
I have done it one more time, with TWRP 2.8.6.2. The restore gets stuck at about 60%, busy with the data section. It is saying "E:extractTarFork() process ended with ERROR=255.
It did succeed in restoring the system partition.
Click to expand...
Click to collapse
Update to my latest version and try that.
That error is erroneous and can mean any one one of different things. Usually a corrupt backup. Some sd cards can be incompatible and can cause this.
Try v2.8.7.2 first, then a different sd card or internal storage.
I am trying to create a master backup of my phone with all of my apps installed and set up the way I want them as a kind of master reference point that I can always go back to in case of problems. I had thought that the way to do this was to set everything up and then do a Nandroid backup from TWRP. However, when I restore it completely resets my system.
I have:
Oneplus 3
TWRP 3.1-0-0
lineage-14.1-20170413-nightly-oneplus3
I am also getting the annoying Dm-Verity message at boot. I have tried to kill it but for now, as it is only cosmetic, I will leave it.
I would appreciate any help.
I continue to research this and I have found this from the twrp.me web page.
"On most devices shipping with Android 6.0 or higher, the device maker has enabled dm-verity as a security measure. The device will signature check blocks of data on the system partition during boot at the block level. The usage of dm-verity prevents TWRP from being able to successfully restore a normal system backup. On most of these devices, you will see an option on the backup page for System Image. A system image backup takes up more space than a regular system backup, but the system image backup is a bit-perfect backup that, when restored, will not break dm-verity (assuming that you don't break dm-verity before making the backup). On a handful of devices, you may also find a Vendor and Vendor Image backup option. The same rules apply with regards to dm-verity. If you need a perfect "go back to completely stock" backup then you should be using System Image (and Vendor Image, when available) instead of just system."
So it sounds like if I make a more complete backup I should not have any issues. But my backups included everything possible to backup.
Still searching for answers.
OK. I just created a backup of a very basic (no apps installed) lineage install. Just creating (not restoring) the backup without flashing anything factory reset the phone.
Flash latest twrp (3.0.4-1). it'll solve your problem..
Thanks vinothkumarv for the reply. I will go get it off twrp.me now. But while I do that, wouldn't TWRP 3.1-0-0 (the one that I am using) be newer than 3.0.4-1?
twrp.me doesn't have 3.0.4-1 listed. A web search brings me to this page that indicates that it is a bug in recent versions of twrp. Another page has a couple of users saying that a modified "blue spark" twrp does not have this issue. I will do some experimenting and get back tomorrow.
Thank you vinothkumarv for the suggestion. I was barking up the wrong tree (thinking dm-verity was responsible) until your suggestion.
hi boxylisher, even i faced the same issue. if I enter twrp, it'll do reset my phone. after flashing this twrp, it resolved that issue.. you can also try this..
Boxylisher said:
twrp.me doesn't have 3.0.4-1 listed. A web search brings me to this page that indicates that it is a bug in recent versions of twrp. Another page has a couple of users saying that a modified "blue spark" twrp does not have this issue. I will do some experimenting and get back tomorrow.
Thank you vinothkumarv for the suggestion. I was barking up the wrong tree (thinking dm-verity was responsible) until your suggestion.
Click to expand...
Click to collapse
TWRP 3.1.0-0 is compatible with OOS but not with other ROMs. So you will have to use either jcadduono's or eng.stk's versions of TWRP which are compatible with both OOS and other ROMs.
dammit....I just flashed the right twrp rebooted recovery. did another backup deleted my old one then rebooted and phone is wiped factory reset. Its because I forgot to turn of screen security?!! dam...oh man...im bummed....... EDIT. It wiped my existing ROM. Im trying to restore the backup that I made with the correct TWRP fingers crossed. I never had any of these problems on my OP2 this phones kicking my ass!! it didnt work its wiped again fdam
Hello Dollar, Yes I feel your pain. It's clearly a bug in TWRP. I am now using bluespark TWRP and everything is running the way it is supposed to.. I have Backed up and restored without this bug wiping my system. I have not set a password yet (and I won't until after I make another "master backup").
Hello,
sorry if this has been mentioned anywhere before, but I wasn't able to find something similar.
So I know why way around with my old Nexus 5 in things backing up the phone with Titanium or TWRP, but since it's wifi module died on me I switchted to the HTC 10, which is kinda intimidating to me when it comes to updating to new OS or backing up. With the NExus 5 it was a walk in the park for me.
First, I don't really understand the concept of S-On and S-Off. Don't know if this is related to my problem, just wanted to mention it.
My HTC 10 is rooted, bootloader unlocked, S-On and runs on 7.0 2.41.401.41.
TWRP is the latest available version.
Before I rooted the phone I made a backup of the stock system image etc like explained in one of those "how to root the htc 10" tutorials (no writing allowed).
To root I had to allow writing onto the system partition of course.
Now, I made an TWRP backup. I backed up everything that was available in TWRP. Userdata, cache, system etc.
Few weeks ago I ran into some problems (I though I did, turned out Google App is just weird) and wanted to restore my TWRP backup.
So I did. Went to TWRP and restored the backup from my SD card.
Got no error messages during the process, but when I wanted to boot up the phone the green HTC boot animation did its thing and then froze at the HTC logo, which would result in a bootloop after ~10 minutes of waiting.
Could force the phone to go into bootloader and from there into TWRP, but that's the best I could do.
Also removed SD and SIM card trays, but that didnt do anything.
Had to factory reset and then do a backup via Titanium backup, which is better than nothing but still a pain in the a** because some things just have to be set up manually, which took me quite a while. I honestly don't want do that again anytime soon
Does anyone have an idea what could went wrong or what I did wrong during the backing up and restoring process?
Except for that, I tried to understand how to update to an upcoming version of the OS when the phone is rooted with S-On and how I could keep my userdata? On the Nexus 5 I just manually installed everything via adb except userdata.img and only had to re-root the phone afterwards. I am afraid this isn't possible with the HTC 10, am I right?
The HTC 10 forces encryption and that has broken TWRP restore for me if I try to switch between ROMs. If I switch ROMs then I have to do a full wipe / format. The one time I tried to go back to my original OS I had a similar issue and I ended up flashing the full RUU to get back to stock.
The only time I am able to restore in TWRP is if I'm returning to the same ROM that I am currently running. Even then I usually just restore the data.
I've been trying to install one of the android 10 lineages on my wife's phone.
It keeps on bootlooping and by now I have tried so many combinations of twrp and restores, wipes, different roms and restoring the backup of an android 9 lineage.
The phone keeps bootlooping, sometimes in the "your bootloader is unlocked" message and sometimes in the lineage startup movie.
It even seems to bootloop in the twrp startup screen, but maybe it is just slow and my impatience is getting too high.
I've tried two different twrp versions as one gave an error in restoring a backup (I think the newest one gave the error).
Could it be that a backup made in the older twrp cannot be restored with the newer twrp?
I'm running out of options and may need to go back to stock, which is not the easiest path to take.
Oh, the phone was rooted when I made the backup, if that makes a difference...
Any thoughts?
If you backed up all partitions, then restore all of them and follow the steps to install...
Note: Before you restore the partition, make sure to wipe it, it ensures that nothing goes wrong...