Database Develop

Upgrade to 5.1.1, but keep root AND user data

Hey guys,
quick question. I have a 5.0.2 z3c rooted with dual recovery and would like to upgrade to 5.1.1.
However, I don't want to lose neither root access nor my personal data. How to correctly dirty-flash a prerooted flashable.zip from recovery?
Also when creating the prerooted flashable.zip with PFRCreator, do I need to use the same Recovery package as I have installed or can I upgrade the Recovery on the go?
Edit: Sorry, wrong Sub. Please delete

To keep root you have to create a prerooted flashable zip (which you did) or maybe you can reroot from the recovery not sure.
To keep your data: your phone has several partitions, most notable are SYSTEM, CACHE and DATA. You want to update system, wipe cache and keep data (which contains your apps and data).
Just flash your resulting zip file through the recovery (it will only operate on the system partition here), then when you do the Flashtool flashing just uncheck DATA in WIPE section and it will keep your data.

TWRP backup question: system vs system image

Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Edit (1/15/2016):
Thanks to RMarkwald and scryan for the quick responses and info. So it seems that the system image isn't going to be needed, and backing up System, Data, and Boot will be good enough for normal backup of the phone/rom before trying something that might break the current setup.

giantninja said:
Thanks to everyone here up front for all the awesome help available here.
I just got my Nexus 6, and no issues unlocking bootloader, installing custom recovery (TWRP), getting root and flashing ROMs/zips (currently loving Pure Nexus with xposed).
My question is regarding backups. When you backup your current setup, most of the information I've found don't show the "System Image" partition under the "System" partition when you go to make a new backup. It's quite large, and I was wondering exactly what that is, and if you need to include that in your backup. Anyone know of a helpful link that explains the partitions?
Also, if you make a bunch of backups, and move them to your computer, does that make things harder if you want to restore from a backup? Can you restore from a backup on your computer just as easily as a backup on the phone's internal storage?
Thanks again
Click to expand...
Click to collapse
According to TWRP in regards to System Image: 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.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.

I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.

rocco24 said:
I already rooted my phone. Where can I get the pure system image now that I can later flash to receive over-the-air updates.
Click to expand...
Click to collapse
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju

simms22 said:
why would you want to unroot your phone, loose all your info, to flash a factory image, just to get an ota? why waste your time??? you can remain rooted, grab the system.img from a factory image, flash it with fastboot, not loose any info, then just reflash SuperSU and a kernel, and be updated. factory images are here https://developers.google.com/android/nexus/images?csw=1#yakju
Click to expand...
Click to collapse
Thanks for the explanation. I meant the system.img not the full factory image my bad.

rocco24 said:
Thanks for the explanation. I meant the system.img not the full factory image my bad.
Click to expand...
Click to collapse
the system.img is in the factory.img, just like the boot.img, cache.img, etc..

Nailed it thanks

RMarkwald said:
According to TWRP in regards to System Image: 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.
If you move backups to your computer, you'll either need to move them back to the internal storage of your phone or USB stick to use USB OTG to restore backups.
Click to expand...
Click to collapse
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again

giantninja said:
Ok, cool... So, if I want to try another ROM out, when I backup my current setup (Pure Nexus with xposed and some themes etc...), should I just backup System, data and boot? or should I backup that System Image as well? or is that System Image the snapshot of the stock ROM that the phone came with?
Thanks again
Click to expand...
Click to collapse
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...

scryan said:
Don't need the system image.
IIRC the system image will give you and .img file of your backup, you could then fastboot that to restore system. (I think... never tested. I believe you can do install and switch from zip to img as well...)
But for just a standard backup with TWRP so you can restore later if you have any problems... Just do as you said with the normal System (os), data (apps & app data), boot (kernel)
Not really sure who is using the system image option, or why...
Click to expand...
Click to collapse
Awesome. That's what I was thinking, but I've been wrong before, so it never hurts to verify.
Thanks!

Opps wrong thread... Lol

Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.

cstokes86 said:
Do any of you know how to reduce the size of or remove the System Image partition on the phone? It's taking up over 4gb on my phone and preventing me from restoring my data partition since it's running out of space during the restore.
Click to expand...
Click to collapse
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.

JimSmith94 said:
I delete any foreign keyboards I don't need to reduce the system partition size. Delete /system/app/(GoogleHindiIME, GoogleJapaneseIME, GooglePinyinIME, KoreanIME). You can either mount system in TWRP and delete, or delete them with a root explorer if you're rooted.
Click to expand...
Click to collapse
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.

I'm in npd90g preview flashed via twrp.if I want official ota
Just flash system image of mm latest and this downgrade doesn't brick my phone ? Can I get ota? And what other should I flash with system image ? Boot ,data and recovery also ?

I dont no much english like othetr peopel
Promblem is i root my honor5x then device get so heat up . After that i deciede to reset it factory setting i have done it but now my device is stuk in twrp loop its not going back normal condition like factory setting plz help me ........ plz

@Shakil jamali: Wrong forum. Go to Honor 5X forum and ask again.

cstokes86 said:
Thanks, Jim. I can wipe my main system partition to free up some space and then restore it later so I don't need to worry about tediously going through and removing unnecessary files. My issue is the "System Image" partition which is actually just over 3GB on my phone. I cannot seem to locate this partition and clear it out so I'm kinda stuck until I can figure out how to reduce the size of this partition ie clear out files from the partition either manually or entirely.
Click to expand...
Click to collapse
Good question. Is this system image actually a partition? Or something TWRP does combining the system image part with a few others into one file? If it is a partition would it be possible to delete it and resize system partition to make use of the extra space? I'm on a nextbit robin stock 7.1.1. Sys image shows as 3,072mb.

For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA

soyti2x said:
For some reason, i cant backup my device through twrp because of error 255. I tried unticking system, then ticked system image and somehow the backup worked. My question is, is it ok to backup with the system image instead of system? What happens when i restore? TIA
Click to expand...
Click to collapse
First, for your 255 error, look at this post. Get rid of the corrupted file and a normal nandroid will work.
To answer your main question, you can use the system.img as a backup. It is intended for people who want an complete, untouched system backup to restore prior to attempting a OTA update.
An alternative approach to backup/restore that works very well in N6, is Chainfire's FlashFire.

Magisk Installing OTA on Pixel XL 1

Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?

niko26 said:
Hi,
I own a Pixel XL 128GB, running 8.0.0 October FW. I have installed Magisk 14.3 beta 1437. Almost everything works, except for:
1. When installing Magisk using Magisk's internal installer it always downloads MAgisk 14.0 and tries to install this old, outdated version. Is this a bug?
2. I can't install OTAs, tried following john's installing instructions...
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
My steps were:
* Install stock boot loader - Magisk almost immediately confirms that it has installed the stock boot image. That's a bit surprising, I don't see any flashing dialog like when installing Magisk. Bug?
* trying to update using the internal OTA fails. It takes very long and suddenly stops.
Any idea what went wrong?
Click to expand...
Click to collapse
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Restoring the stock boot image through the Manager is instantaneous...

Hi @Didgeridoohan,
thank you very much for the quick answers!
Didgeridoohan said:
1. If you wan't the current beta to install, you need to change to the beta update channel in the Manager settings.
Click to expand...
Click to collapse
Thanks - I didn't know that.
2. You've probably done something that messes with important partitions (/system, /vendor, etc). It's enough to just mount the partition rw to destroy the ability to update through OTA.
Click to expand...
Click to collapse
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?

niko26 said:
Hi @Didgeridoohan,
thank you very much for the quick answers!
Thanks - I didn't know that.
Hm, how do I find out what has been messed on /system, and/or /vendor?
Does installing and using AdAway tamper with /system or /vendor?
So reflashing the stock boot image is not sufficent, correct?
And most important.. how do I fix this?
Click to expand...
Click to collapse
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though. Do you have TWRP installed? That'd be an issue as well...
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.

* DELETED *

Didgeridoohan said:
If you let AdAway directly write to /system/etc/hosts, then yes, you have a compromised system partition. If you're using Magisk Systemless Hosts you should be fine though.
Click to expand...
Click to collapse
Yeah, I've been using Magisk's systemless hosts-file.
. Do you have TWRP installed? That'd be an issue as well...
Click to expand...
Click to collapse
TWRP has not been installed permanently.
If you want to make sure that you can update through OTA in the future, clean flash a factory image (you can leave data intact) and then make sure not to touch /system or /vendor at all.
Click to expand...
Click to collapse
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.

niko26 said:
Yeah, I've been using Magisk's systemless hosts-file.
TWRP has not been installed permanently.
There aren't a lot of apps I am granting root. One of them is Titanium Backup. It may have tampered the fs.
Is there any kind of diff against the original folders which I can run to find out what has been tampered to possibly identify which app is causing the issues?
One of the main reasons for installing Magisk was because I was tired of flashing the entire system when updates have been released.
I never couldn't get Flashfire working properly when it comes to install updates / OTAs.
Click to expand...
Click to collapse
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...

Didgeridoohan said:
Since the OTA can check for a tampered system, I'm sure there's a way to check. Question is if it's worth the effort.
Any app that has root access can be the culprit... Could also be that you let TWRP mount system rw or something similar. Really hard to say...
Click to expand...
Click to collapse
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.

niko26 said:
Does TWRP mount system as rw by default? Because all I really do is.. boot to TWRP, flash the Magisk's zip. That's it. Nothing else.
Is there any other way I can install OTAs without using a computer with USB (and keeping root of course )?
As said... I never could FlashFire to work correctly. The documentation leaves a lot of questions open - BTW.. props to the Magisk's docs - much better.
Click to expand...
Click to collapse
TWRP doesn't mount system as rw unless you let it.
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
For a while there I also flashed the system.img and boot.img files in TWRP. If that months security update only had anything to do with those files it was just a matter of downloading the factory image and unpack those two files and flash them directly in TWRP. No computer needed (unless there was an update to the bootloader and/or radio). No idea if this is viable on a Pixel...
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.

Didgeridoohan said:
I've never used Flashfire and haven't updated through OTA since, 2014-ish. :laugh: I'm mainly going on theoretical knowledge here... On my Nexus I used fastboot to flash the factory image (until I switched to ROM flashing in TWRP) and now I just flash the full update package that OnePlus provides in TWRP.
Click to expand...
Click to collapse
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
My main use for Magisk is that all my system modifications are still there after I update my phone. Drastically cuts down on the time it takes to set my phone up after an update.
Click to expand...
Click to collapse
What settings are you referring to?

niko26 said:
I've tried installing TWRP permanently, but the moment I have installed an official patch, it got wiped - and I haven't found any docs how to prevent that.
Click to expand...
Click to collapse
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
What settings are you referring to?
Click to expand...
Click to collapse
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.

Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
Click to expand...
Click to collapse
Well, TWRP is gone after an update - I can't boot into it.
[/quote]I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.[/QUOTE]
Hm, I am not sure if I get you right. If it is about apps, I use Titanium Backup to recover my old apps+settings.

system files
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Didgeridoohan said:
After updating, you probably need to boot straight to TWRP and reflash root. If you boot directly to the OS, it'll automatically replace TWRP with the stock recovery.
I like to change screen density, debloat system apps, install Viper4Android, install boot scripts (LiveBoot, etc) and a bunch of other things. With Magisk, as long as I don't wipe /data, all of that will still be intact after a system update. And even if I wipe data I can restore a backup of the Magisk image or just flash the module zips in TWRP. Takes seconds rather than half an hour like it could prior to Magisk.
Click to expand...
Click to collapse

automattic said:
Most of the setting you mentioned are messing with the system files. "debloating" or removing and system applications with titanium backup will fail a system check with OTA update. You can freeze the apps i believe.
I changing the screen density and boot scripts. These are all system files locations.
I have had an ota work be re-installing the system apps from titanium backup and reverting all the other changes when it was failing before. Think this was back on android 6.0 though.
Click to expand...
Click to collapse
Since all of the things I mentioned are done with Magisk, none of them will cause an OTA to fail...
Reinstalling system apps will not work, since nowadays an OTA will fail just by mounting /system as rw.

Hi guys, trying to install latest OTA patch for Pixel 2. I am assuming process would be the same. I tried to follow the guide but hit the bump immediately. I can't see "Restore Stock Boot" when pressing uninstall. But there is restore images option. Hitting it does nothing, I receive the message that there are no backups. Where does the backup go so I can put the original file for it to be reinstalled?

How to go from OOS 5.0 to Stock Nouga

How to go from OOS 5.0 to Stock Nouga

Since you've made the spelling error twice, its Nougat, not "Nouga.".
I think the best way you could do it is flash the special Open Beta build on the Open Beta thread and then flash the stable build zip.
Whichever way you do the reversion, you will lose partial data, as N and O do not support each others app installations.

Z.boy said:
How to go from OOS 5.0 to Stock Nougat
Click to expand...
Click to collapse
If you are unlocked bootloader, flash twrp 3.1.1-2 and clear dalvik data cache and system, and just flash them through twrp
dont use twrp 3.2.0-0 because you cant install magisk, it shows installed but magisk doesnt seem to be recognized in apps
I've just done that, and everything seems working flawlessly
Pls do hit thanks if i help you

izukamikain said:
If you are unlocked bootloader, flash twrp 3.1.1-2 and clear dalvik data cache and system, and just flash them through twrp
dont use twrp 3.2.0-0 because you cant install magisk, it shows installed but magisk doesnt seem to be recognized in apps
I've just done that, and everything seems working flawlessly
Pls do hit thanks if i help you
Click to expand...
Click to collapse
Does your solution avoid erasing internal storage? Because that's the part that's preventing me as it can take too long getting my backups into the phone again.

rebelpixel said:
Does your solution avoid erasing internal storage? Because that's the part that's preventing me as it can take too long getting my backups into the phone again.
Click to expand...
Click to collapse
i never format my internal sdcard partition
it's taking too long time to backup and restore it again
as i said, only format dalvik cache data and system thru twrp and you're good to go

download special edition nougat revert zip file and flash it via recovery
http://oneplusroms.s3.amazonaws.com...337224&Signature=BEA4IHd/rVFqoPd2gh7EvwaoSeg=
notes :
The build will wipe app and cache data, but Internal Storage will be saved (ie: pictures and files)
Users who revert their device back to the special build can still OTA update the device to Android O build at a later date.
Steps to revert:
Download special build
Copy to Internal storage
Reboot to recovery Mode to install
Choose “Install from Local”
Choose the downloaded build to install

Question How to properly format my OnePlus 10 Pro

Hey everyone,
my op10pro became extremely buggy, system settings aren't being saved after reboot, the ui is becoming jank af, i am getting no notifications from any apps, popups are getting blocked... very annoying ****.
how can i fully format my entire system and start from scratch ? i am rooted.
i don't mean a factory reset, i already tried that. something that cleans deeper.
thanks in advance

Install a rollback package, maybe it helps (will install Android 12) or install the latest full package and format data.

I don't necessarily want to go back to an old version of Android, and i fail to see how it would help.
How do you suggest i format data ?

You can format data in recovery mate.
Or if you want a whole new OS then fastboot enhance (FE) will do it.
You can format using fastboot too but FE takes care of that.
PS: if you're restoring your apps after a wipe then that could be why it's buggy, let the system install then see how it feels, then restore only what you absolutely need.