Hi,
I'm installed TWRP 2.7.0.0 via GooManager and that went smoothly. But when I went to do a nandroid backup, the modem partition isnt there. The other partitions (boot, system, cache, data, efs) are there. In "Mount" the modem partition wasn't mounted so I tried to mount it, but that didn't add it to the available partitions to backup either. Is it normal for the modem partition to be missing? How can I back it up?
The modem is never backed up. All you need to back up are system, data, and boot
Edit, it would be good to backup only the efs partition once and store a copy off your phone in case that ever gets messed up
Sent from my Nexus 5
jd1639 said:
The modem is never backed up. All you need to back up are system, data, and boot
Edit, it would be good to backup only the efs partition once and store a copy off your phone in case that ever gets messed up
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks. :good: It's a bit confusing as I see some posts talking about backing up modem with TWRP....and other posts talking about grabbing a modem file from a developers thread and using that. I guess I'll go with the latter based on your large number of posts and >2000 Thanks received. :fingers-crossed:
DoughMucker said:
Thanks. :good: It's a bit confusing as I see some posts talking about backing up modem with TWRP....and other posts talking about grabbing a modem file from a developers thread and using that. I guess I'll go with the latter based on your large number of posts and >2000 Thanks received. :fingers-crossed:
Click to expand...
Click to collapse
Trust him, a modem don't need backup because it never been touched, only Odin can touch and modify modem when you flash a stock ROM
Sent from my GT-I9505G using Tapatalk
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data
Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).
I have a pattern lock and fingerprints and restore my backup without any problems?
Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!
Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.
Hi guys
Does anyone have a TWRP A2017G backup their willing to share?
I've lost IMEI and MEID and am trying to recover
Seconded. I seem to be in the same situation. Don't know if a TWRP backup will help, but I've been unable to connect to the cellular network after restoring a full TWRP backup which I suppose I shouldnt've restored. Re-entering my IMEI via a TWRP module didn't help as well. Neither does the adb shell dd command that formats the EFS partition found in another thread... Restoring EFS I backed up a while ago didn't help me as well.
Thanks in advance.
I have tried going back to stock boot/recovery backups, flashing every single A2017G update and even tried Tenfar's tool to restore the removed backups in his thread. Cannot seem to fix
Only had this phone for 3 days and it's now useless.
Controllerboy said:
Restoring EFS I backed up a while ago didn't help me as well.
Click to expand...
Click to collapse
Do you have a backup you could share?
As far as I know, the EFS bit is unique to each device. It contains your IMEI code, for example, which is unique for each device.... I can give you mine, but I'm not sure if that will help you.
I'll probably make a new thread asking for some help because I've tried about everything and I can't fix this mess on my own... I hope I won't have to send it back, no way of knowing they'll believe me
I've been doing some googling and perhaps we need a modem.bin file from a A2017G?
this is really not looking good
Hello, for some reason my persist partition corrupted and I think it was my mistake. I flashed the stock rom, and the fingerprint is now working, however, automatic rotation doesn't. Can anybody give a link to persist.img because I haven't able to find it from none of the updates asus released? If not a backup of persist partition. TWRP can easily make a backup of it.
Also, just for you know, deleting persist partition on ZE552KL doesn't lead to broken wifi, bluetooth or imei. Learned it through the hard way. You may ask why I didn't make a backup. It is because I didn't know it previously.
I would appreciate it if anyone could provide persist partition img or backup.
BTW, I also tried a raw image with the full name of "WW_ZE552KL_15.0410.1803.55_M3.10.47.19_Phone-user.raw".
Been struggling with a TWRP restore gone wrong for over a week now.
TWRPs today have many options for backup, a lot of which I couldn't find info online.
Usually I backup only Boot, Data and System.
But tend to make a first backup after installing TWRP with all options included.
On the Galaxy S10+ there are:
Baseband
Boot
Cache
Data (excl. storage)
EFS
Product
Product Image
System
System Image
Vendor
Vendor Image
Recently I was restoring several backups and restored this first backup with all options included.
Since, the phone boots and is stuck on the boot screen.
I can still boot into TWRP.
Can someone please help me understand how to solve this? :fingers-crossed:
I run LineageOS 17.1 with ianmacd TWRP, rooted with Magisk.
Can I solve this through TWRP?
Will flashing stock firmware through Odin is the only option? Or an option that will solve this at all?
Also if someone can detail what the different option are, that would be amazing!
If you can't restore another backup, then yeah it looks like you will have to use Odin.
Managed to get back to the ROM eventually.
If anyone can share info about the different options and what they actually are/do - will be very appreciated!
Pogromonolith said:
Managed to get back to the ROM eventually.
If anyone can share info about the different options and what they actually are/do - will be very appreciated!
Click to expand...
Click to collapse
These do exactly what the name suggests. I don't think there is much to explain. Usually you would only backup /Data and /System partitions, eventually /Boot and /Vendor.