I wonder whether backing up Preload in TWRP is important or not? Is it different from system or what? Does backing up system suffices or we must back up preload too?
Related
Hi all,
I have a nexus 7 running Android 4.1.2 stock w/ root. Some months ago, I disabled the OTA update notification - but I can't seem to remember how!
I want to now re-enable OTA updates so that I can update to the latest android version, and not lose my installed apps.
I've searched the device for FOTAKill.apk inside /system/app, and its not found
I've also searched for frozen / hidden apps using Titanium Backup Pro... nothing
When I enter Settings -> About Tablet -> System Updates... it says I'm up to date... but I'm not, considering I'm running 4.1.2.
Any help or pointers in re-enabling OTA is appreciated!!
- make a full nandroid backup.
- using fastboot, flash the system.img file from the 4.2.2 factory image to the system partition.
- using your custom recovery, reflash a SuperSU root kit bundle.
- using the custom recovery, wipe cache and dalvik-cache.
If you don't like the result, restore the nandroid backup and proceed in a different fashion. It will probably break things like stickmount and any other changes that you caused in /system.
Note the above method is for use by lazy and sloppy users. A better approach is to make TiBu backups of only your market apps, bite the bullet, and start from scratch with a flash & (new) configuration of a pure stock ROM. In any case, every conceivable procedure should start with making a full nandroid backup and getting it copied to a safe place off the tablet.
I will also say that unless odd problems crop up, the portions of the factory install procedure (using fastboot) that deal with erasure or flashing of the userdata partition should be skipped, as these steps completely wipe your /data storage - including your /sdcard area in /data/media/0 and any CWM/TWRP nandroid backups!
It's not really clear why these steps would be needed unless the /data ext4 filesystem in the userdata partition got corrupted somehow. A more sly approach would be to use the custom recovery's "factory reset" procedure to clean up /data - either before or after flashing the factory ROM - and completely skip anything that touches the userdata partition in the factory install instructions.
good luck
I'll just put this out there for other noobs using twrp. I've never done a nandroid backup before, and I'm currently running twrp v2.6.3.2. When I select backup, it directs me to select which partitions, with boot, system & data already checked. Do I need to check any of the other options (Recovery, Cache, EFS)? TIA.
thestrangebrew said:
I'll just put this out there for other noobs using twrp. I've never done a nandroid backup before, and I'm currently running twrp v2.6.3.2. When I select backup, it directs me to select which partitions, with boot, system & data already checked. Do I need to check any of the other options (Recovery, Cache, EFS)? TIA.
Click to expand...
Click to collapse
most important is the EFS one, somewhere mentioned it contains your IMEI etc. Backup it, and copy it for safe keeping. Everything else you should be able to recover, but EFS if lost might lead you to a non-usable phone.
Cache not needed.
Recovery well depends, but its just 8-11MB more I would check it as well.
Actually you can back it up all.
The most space will take the SYSTEM and DATA anyways, the rest is few MB's. Let's say SYSTEM is your ROM (system apps etc), and DATA is your config and installed apps. (Not entirely true if you do some modifications but these 2 partitions you need to restore the backup as you had it)
Boot is the kernel. Which might be needed by the specific System if you go custom, again only some MB's.
Just remember that you can even choose what you will recover. So when you change your recovery, kernel etc and you go for restore of some older backup, careful of compatibility in between ROM and KERNEL for example
Awesome thanks for the quick informative info. I figured it wouldn't hurt to just backup everything, but I thought I'd ask just in case I missed something.
I had a full backup image in twrp.
Whenever i try to restore it auto reboot around 15% while restoring system partition ?
which partion to restore.
any issue if i chose to restore all partion
boot/system/system image/vendor/vendor image/data/cache/recovery/efs
any advice.
Thanks
kakabobo said:
I had a full backup image in twrp.
Whenever i try to restore it auto reboot around 15% while restoring system partition ?
which partion to restore.
any issue if i chose to restore all partion
boot/system/system image/vendor/vendor image/data/cache/recovery/efs
any advice.
Thanks
Click to expand...
Click to collapse
,,,You have to backup EFS once (via non-buggy twrp) and keep it stored on mobile and PC
... For ROMs..You just BACKUP system data boot
And restore them
... when shifting () different builds marshmallow to nougat... nougat 7.0 to 7.1 or whatever.. you need to INSTALL (not backup or restore) the CORRESPONDING vendor
That's it
Hi,
after few soft-bricks and hours, i was able to transform my stock A2017 B16 to stock A2017U B25 and everything is working.
now the device is B25, android 7.1.1 + TWRP 3.1.1-0 and i want to make full backup as i know the need it if something goes wrong (and it probably will )
in the back up options i see the following:
Boot (64MB)
Recovery (64MB)
System (4740MB)
System Image (6144MB)
Data (excl. storage) (4001MB)
Cach (27MB)
Modem (NON-HLOS) (95MB)
Bluetooth (BTFM) (1MB)
EFS (6MB)
for now, i did backup of all of them but didn't tried to restore because i saw somewhere that i can get you brick .
can you help me understand what to backup for *complete backup* which one i can use in emergency recovery cases?
Boot - This is your bootloader. I usually back this up.
Recovery - This is twrp, you could back it up by itself once, but it isn't necessary.
System - This is your rom and stuff. This is the main thing to backup/restore if you want to keep the current ROM you are on.
System Image - I'm not positive on this, but I think its a full image of the whole system with everything.
Data (excl. storage) (4001MB) - This is all of your personal data, apps settings, call logs, etc.
Cach - no point in backing this up
Modem (NON-HLOS) - I don't back this up either as you can always flash the newest modem files
Bluetooth (BTFM) - bluetooth settings/devices I think, probably don't need to back up.
EFS - Do one backup of this and keep it forever. If you ever wipe or mess the EFS up you are in trouble.
Don't count on all that 100% as I'm not a dev, but I've been doing this for years. Besides the one time backups I mentioned, I routinely just backup the boot, system and data and have never had any problems restoring.
If you are brave and installing a rom that runs on a similar base, sometimes you can backup only the data, and flash the new rom, then restore just the data and have all your settings and apps stuff back.
Hopefully that helps.
Boot, System, Data- just like the person above me.
That's all you really need to do. Sometimes I'll even do things like wipe system only if I'm having problems with the ROM, Gapps, or some random mod, and reinstall the ROM & Gapps to bring it back to a clean slate. Say, if I tried out A.R.I.S.E. sound mod but it was acting goofy and I wanted to make sure I removed all of its remnants.
Recovery is unnecessary I'd think.
EFS - I guess backup once.
Why not backup everything? It doesn't take up much space. System image seems to be the only one I'd leave out. I still back it up anyway.
ThePublisher said:
Boot - This is your bootloader. I usually back this up.
Recovery - This is twrp, you could back it up by itself once, but it isn't necessary.
System - This is your rom and stuff. This is the main thing to backup/restore if you want to keep the current ROM you are on.
System Image - I'm not positive on this, but I think its a full image of the whole system with everything.
Data (excl. storage) (4001MB) - This is all of your personal data, apps settings, call logs, etc.
Cach - no point in backing this up
Modem (NON-HLOS) - I don't back this up either as you can always flash the newest modem files
Bluetooth (BTFM) - bluetooth settings/devices I think, probably don't need to back up.
EFS - Do one backup of this and keep it forever. If you ever wipe or mess the EFS up you are in trouble.
Don't count on all that 100% as I'm not a dev, but I've been doing this for years. Besides the one time backups I mentioned, I routinely just backup the boot, system and data and have never had any problems restoring.
If you are brave and installing a rom that runs on a similar base, sometimes you can backup only the data, and flash the new rom, then restore just the data and have all your settings and apps stuff back.
Hopefully that helps.
Click to expand...
Click to collapse
You're mostly correct except boot, which is the kernel and not the bootloader, and system image is this as mention in an old TWRP changelog:
The Team Win Recovery Project has released version 2.8.7.0 of its custom recovery, known simply as TWRP. This update brings a system read-only option that's intended to help you make a pure backup of your system image that you can later flash to receive over-the-air updates after having rooted or ROMed your device.
Cheers.
@mb0 Basic backup is system data and boot to have a working device, but I'd backup everything at least once just to be on the safe side.
The "backup all" solution sound nice to me??
At least one full backup and i keep it in safe place(es).
Let's try the restore function and hope not to be surprised
Hehe, good luck mate!
I'm back to update...
Full backup (except 'cache') --> reboot to recovery --> normal 'wipe' --> reboot (to make sure that it wiped) --> reboot to recovery --> restore everything (except 'cache') -->reboot --> ITS ALL GOOD :good:
I am familiar with how by default in Stock Nougat for Moto G5 Plus, your data is encrypted and you must decrypt in TWRP by formatting data in order to view internal storage. I was just wondering if it is possible to restore an EFS backup through TWRP without having to decrypt your data (ie without formatting data)?
Any help is much appreciated!
Yes, decryption is only neccessary for the /data partition, you can modify and flash all other partitions without touching /data.