[ROM/GUIDE] Full Updates / Back to Stock Files via TWRP (A2017U, A2017G, A2017) - ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve

READ, READ BEFORE PROCEEDING
YOU'VE BEEN WARNED​
Ok, I wasn't going to create a new Thread for this but is really needed to keep this a little separate but in the same thread, so here i'll be updating base on current updates for each variant this Thread will contain Current Updates and as for now current updates are :
REQUIREMENTS :
- Plain and simple, you just need TWRP. Either via @tenfar or @tennear Tools or happens that you already have TWRP install.
ROOT:
If you are UNLOCK BOOTLOADER proceed with STEP 7, if not you'll need to use @tenfar Modded boot image base on your system update to get root access.
Each steps will contain 2 files which are:
1- BootStack
2- System+Boot
Q: Why 2 Flashable Zip Files?
A: Well cuz a lot of us know you CAN use / try other variant system image , i have separate what is just needed to for that purpose, meaning if A2017U want to give a shot to A2017G or A2017 software you will just need to Wipe Cache -Dalvik - Data and Flash the A2017G or A2017 Flashable system file or vice-versa.
The Bootstack just need to be flash ONCE per variant, the A2017G CAN'T use A2017U Bootstack (well you probably can but IS NOT RECOMMENDED) .
- A2017UV1.1.B35 (Nougat) (Post # 2 or Click Here)
- A2017.B10 (Post # 4 or Click Here)
- A2017G.B08 (Post # 3 or Click Here)
- A2017G Flashable Stock Recoveries (Post # 5 or Click Here)
-------------------------------------------------------------------------------------------------------------------------------
I'll be Updating this thread base on current Updates and please let's keep this thread clean and on-topic
-------------------------------------------------------------------------------------------------------------------------------

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017UV1.1.0B35 NOUGAT Update
-----------------------​
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N) / B19(N) / B25(N) / B32(N)
-----------------------------------------------------
Once you booted to TWRP , Tap Mount and Check "Mount, System as Read-only", this is very important
1- Download the following zip files
- A2017UV1.1.0B35_bootstack_by_DrakenFX.zip
- A2017UV1.1.0B35_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (Wipe Data if you aren't updating from B29-MM or B15-N)
5- Flash A2017UV1.1.0B35_bootstack_by_DrakenFX.zip( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- FlashA2017UV1.1.0B35_systemstock_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT AND KEEP TWRP after flashing Stock System, download SuperSU v2.79 (Or your preferable Root method)
WARNING - WARNING​NOTE : YOU MUST FLASH SUPERSU OR VM-VERITY ZIP, IF YOU WANT TO KEEP TWRP, THE B32 UPDATE HAVE STRIP BOOLODER
8- REBOOT and Enjoy Nougat B35 Rooted or Just Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
.
.​

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017G.B09 Update ( Files Provided by @tron1 )
-----------------------​
-----------------------------------------------------
UPDATING FROM B01, B02, B03, B05 , B06 or B08 Rooted or Stock
-----------------------------------------------------
1- Download the following zip files ( Thanks @tron1 for making the files )
- ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip
- ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017GV1.0.0B09_BootStack_by_tron1.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017GV1.0.0B09_StockSystem_by_tron1.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B09 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
. Here's the B08 Files in case are needed
. TWRP_A2017G.B08.BootStack_By_DrakenFX.zip
.
. TWRP_A2017G.B08.FStockSystem_By_DrakenFX.zip
.
..................................................................................................................................................................................................
.
. Here's the B06 Files in case are needed
. ZTE_A2017GV1.0.0B06_BootStack_by_DrakenFX.zip
. md5 : fa64983faaf4d37a26772dab53a61ff2
.
. ZTE_A2017GV1.0.0B06_StockSystem_by_DrakenFX.zip
. md5 : 3b34ac0d1c81248454666b9ae644da16
.
.................................................................................................................................................................................................
.
. Here's the B03 FIles in case are needed
. ZTE_A2017G.B03_BootStack_by_DrakenFX.zip
. md5 : ae0f260a9bd7ee486704842bc9efa202
.
. ZTE_A2017G.B03_StockSystem_by_DrakenFX.zip
. md5 : 5086d5a0d73e07a257b9f4cb4b7c7631
.
..................................................................................................................................................................................................
.
.
. Here's the TWRP B06 Flashable Stock Recovery
. TWRP_B06_StockRecovery.zip
.
. Here's the TWRP B08 Flashable Stock Recovery
. TWRP_B08_StockRecovery.zip
.
..................................................................................................................................................................................................

YOU MUST HAVE ACCESS TO TWRP TO PROCEED
THIS WILL NOT WORK IF YOU DON'T HAVE TWRP
I'M NOT RESPONSABLE IF THIS PROCESS CREATED A THERMAL NUCLEAR DEVICE
AND / OR TURN YOU INTO FIRESTORM.
NOT RESPONSABLE IF SOMETHING HAPPEN DURING THIS INSTALLATION OR IF
YOU DO A MISTAKE DURING THIS PROCESS
READ, READ , READ , READ AND PROCEED AFTER READING ALL THE STEPS ​
A2017.B10 Update
-----------------------​
-----------------------------------------------------
UPDATING FROM B09 or Below Rooted B20
-----------------------------------------------------
1- Download the following zip files
- ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip
- ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
2- Move both files to your device ( Internal or SDCard )
3- Boot to TWRP.
4- WIPE Cache - Dalvik - DATA (I will say system as well but is up to you, i normally do wipe system if i'm flashing a system image).
5- Flash ZTE_A2017V1.0.0B10_BootStack_by_DrakenFX.zip ( THIS FILE IS JUST TO FLASH ONCE, THERE IS NO NEED TO FLASH THIS MORE THAN JUST 1 TIME )
6- Flash ZTE_A2017V1.0.0B10_StockSystem_by_DrakenFX.zip
IF YOU ARE UNLOCK BOOTLOADER PROCEED WITH NEXT STEP FOR ROOT - CLICK SHOW CONTENT-
7- IF YOU WANT ROOT after flashing Stock System, download SuperSU v2.65 which i have been mention before since day 1 and just flash the file.
8- REBOOT and Enjoy B10 Rooted or Stock.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​NOTE : If you don't flash SuperSU / Root when you boot to system for the first time, there is a script (i can't disable) in system that WILL REPLACE your TWRP Recovery back to Stock Recovery, so keep in mind that you may end up with stock recovery after this.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------​.
.
.B10 & B11 Flashable TWRP Files can be found here also :
https://www.androidfilehost.com/?w=files&flid=118419
.
.

----------------------------------------------
A2017G
Flashable Stock Recoveries
----------------------------------------------
Folder with A2017G Stock Recoveries B06 , B08 and B09
TWRP Stock Recoveries Flashable Zips
----------------------------------------------​

Last Reserve for something else thread related

:good:

@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.

TheRoyalSeeker said:
@DrakenFX could you please provide system dump or atleast tell me a way to extract everything of stock rom on my pc.
Click to expand...
Click to collapse
System Dump for which variant? i know A2017G and A2017 are .dat but that can be converted to .img very easily, if you have windows you can use this Android DAT/IMG File Unpack and Repack V 2.0 , that's what i use to convert .dat to .img.
If you need more info just PM.

Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.

AllAboutAndroids said:
Can't seem to get Root access. Wipe Cache, Dalvik, Data and System. Flash the files in order: Bootstack > StockSystem > SuperSU 2.65 but it doesn't work. If I don't flash Root, it boots up accordingly.
Click to expand...
Click to collapse
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Let me try that now and will let you know asap!

AllAboutAndroids said:
Let me try that now and will let you know asap!
Click to expand...
Click to collapse
Let's us know I'm mins away from doing this but NEED root!!

S8ntsHaz3 said:
Let's us know I'm mins away from doing this but NEED root!!
Click to expand...
Click to collapse
Noooooope. I went back to Stock Recovery somehow...even though I had TWRP all along.

Sad days

xtermmin said:
Something to try: after wiping cache/dalvik/data/system, go to Mount, make sure System is not checked, and make sure "Mount system partition read-only" is checked. Then flash bootstack > StockSystem > SuperSU 2.65.
Click to expand...
Click to collapse
Trying this again!
S8ntsHaz3 said:
Sad days
Click to expand...
Click to collapse
Got TWRP back. I'm going to attempt the method above and let you know!

AllAboutAndroids said:
Trying this again!
Got TWRP back. I'm going to attempt the method above and let you know!
Click to expand...
Click to collapse
Awesome thanks !!!!

S8ntsHaz3 said:
Awesome thanks !!!!
Click to expand...
Click to collapse
Hmmm stuck at "Please Wait..."

Which method did you use to obtain root/TWRP?

S8ntsHaz3 said:
Which method did you use to obtain root/TWRP?
Click to expand...
Click to collapse
Using:
D:\Downloads\axon7root-us-b27>axon7root.exe -p 3 -r
That only gave me TWRP. I still can't get Root to work on the B27 Update.

Related

Install OOS Open Beta 8 (N) / 7 (MM) without Breaking official TWRP

This guide allows you to install OOS Open Beta 8 (N) / 7 (MM) without having to switch to modified TWRP
All credits to the respective developers
Downloads : G-Drive | MEGA
Unified Links above contains the following.
[Added] OOS Leaked Open Beta 9 (Mirror only) will modify Once it is released
1- Modded OOS Open Beta 8 (No F2FS , Downgradable to any OOS version)
2- Modded OOS Open Beta 7
3 - Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Unified Flashable Zip)
4- Super SU 2.78-SR5
5- Official TWRP
6 - Modified TWRP Recovery 3.0.2-1.28 Credits @eng.stk
7- Latest Xposed Installer (Beta 7 Only) (It will give you the option to download / install the latest version of framework automatically)
8- Open Beta 8 Full flash able (F2FS support with Modified Recovery @Funk Wizard)
Instructions for Clean / Dirty Flash (Over any Open Beta after 3.5.1) :
1. Boot into TWRP (modified or official which ever you are on)
2. Wipe Dalvik / ART cache & cache OR Factory Reset ( If you are coming from another ROM)
3. Flash Modded OOS Open Beta 8 (Dont Switch /system and /data to F2FS if you want to root) or Beta 7
4. Wipe Dalvik and Cache
5 . Flash official twrp as image (even if you are already on it)
6. Reboot to into recovery directly (this will prevent recovery from being overwrite by the stock)
7. Flash SuperSu (Optional)
8. Flash Debloater / Pixel Laucher (Black) and H2OS Icon Packs , Google Assistant (Clear Google App Data after Booting) (Unified Flashable Zip) (Optional)
9. Reboot to System (It will reboot twice if you flashed SuperSU) - That is normal
You are good to go :good:
Regards ,
Muhammad A. Iftikhar
Is there any kernel for this build ???
Normas Interruptor said:
Is there any kernel for this build ???
Click to expand...
Click to collapse
Eng.stk yesterday teased us with an upcoming kernel for 3.5.4 Community Beta.
Whatch this thread: http://forum.xda-developers.com/oneplus-3/development/kernel-t3404970 .
Can I dirty flash it from FreedomOS based on 3.2.7?
xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Nope, they are two different ROMs on different channels: for instance you could have dirty flashed if you were on 3.5.2 or 3.5.3.
I need to wipe system too? Or only cache/dalvik + data?
xGOGI said:
Can I dirty flash it from FreedomOS based on 3.2.7?
Click to expand...
Click to collapse
Yes you can as you have firmware of 3.2.7
xGOGI said:
I need to wipe system too? Or only cache/dalvik + data?
Click to expand...
Click to collapse
System Wipe only if you are coming from another ROM , I.E CM or AOSP based / Nougut
How do i flash official twrp in modified twrp, do i have to extract the downloaded file?
puschkin said:
How do i flash official twrp in modified twrp, do i have to extract the downloaded file?
Click to expand...
Click to collapse
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.
ahmediftikhar said:
Click Install > "Install Image" it will showup in the location you download the file should have ".img" extention .
simply download it in the phone from the link in OP.
Click to expand...
Click to collapse
Thanks for the quick reply!!
puschkin said:
Thanks for the quick reply!!
Click to expand...
Click to collapse
This will further help you out
Thanks for this great tutorial, worked like a charm
I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki
ralph78 said:
I want to try new CB but more likely I will be going back to official 3.2.7 I have nandroid backup ready. My question is, if I follow your guide and then I want to restore my backup, will I be able to do it without the hassle?
Wysłane ze zmywarki
Click to expand...
Click to collapse
You can even dirty flash this over 3.2.7 (will take some time after 1st boot to optimize apps depending on the number of apps installed) , Nandroid can be restored with out hassle if you choose to clean flash 3.2.7 after testing CB
I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?
XS_31 said:
I'm on TWRP 3.0.2-1, and I can't install Rom zip, it always tells me that zip file is corrupted. I've downloaded it twice however, once from Google drive, once from AFH.
Any idea of what's wrong?
Click to expand...
Click to collapse
Try re-flashing Twrp by downloading a fresh copy , and manually mount system before flashing the ROM ,
You can also try downloading it directly to your gdrive and let it sync in your PC / phone by "make available offline" feature in drive app
how to back from 3.5.4 to stock again?
File corrupt from both links, also.
ritchiedrama said:
File corrupt from both links, also.
Click to expand...
Click to collapse
Yes... File is corrupted... So much of mobile data wasted..

no_verity_op5(t) _v3.zip for OOS OB13 with Project Treble

I made small changes based v2
Suitable with OOS OB13 with Project Treble.
No need to mount any specific partitions (in recovery) manuly such as /vendor
Click to expand...
Click to collapse
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Download Link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
daxiaamu said:
How to use
If you see this thread, you should know how to use this file.
Just all the same as v2. More info here https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-decrypt-data-partition-t3642144
Can be used for HOS/OOS 7.1 8.0 8.1 and 8.1 with Project Treble and mokee rom
Click to expand...
Click to collapse
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Awesome. Thank you very much @daxiaamu!
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
Same thing here. Thanks for the heads up.
fjsferreira said:
File is damanged. also, has a zip.zip extension, but still, after renaming it, doesn't open (at least on the PC)
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
a63548 said:
Awesome. Thank you very much @daxiaamu!
Same thing here. Thanks for the heads up.
Click to expand...
Click to collapse
link https://drive.google.com/open?id=1dMeYaIC4eFNBc3sfNQpGUqFzcqttlMZ0
Need new link please
Aballamis said:
Need new link please
Click to expand...
Click to collapse
You can also use the one from xXx https://forum.xda-developers.com/on...1-1-speed-ram-optimized-t3627121/post72802213
Aballamis said:
Need new link please
Click to expand...
Click to collapse
Here's a mirror: http://www.mediafire.com/file/1psz6...ForceEncrypt_2.0_%28OP5-5T-Treble%29.zip/file
Recommendation
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Mohitash said:
I recommend this-
Its unversaly. I use this on every rom.
Regularly updated.
http://zackptg5.com/android.php#disverfe
XDA Thread for this-
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
P.S. I never format data while updating before flashing this (never needed, it works fine without that). I onlyformat data whenever i want pure clean install of any rom.
Just make sure to flash this after rom and after custom kernel or anything that edits boot. But flash this before Magisk. So. In short-
1. Flash- rom
2. Flash custom kernel or any thing that edits boot
3. Flash this to decrypt and to boot ur device successfully
4. Then flash Magisk
Note1: When you need clean install then follow these steps-
1. Factory reset (as normal when u do but if u r flash pure stock than wipe everything- i recommend this everytime for every stock(based) rom)
2. Reboot to recovery again
3. Click on Format data, type yes and format it.
4. Reboot to recovery again
5. And now go on flashing as mentioned above before these steps.
Note2: When u just need to update and not clean install. Then follow these steps-
1. First make sure to remove all magisk modules (when enabled it makes issues - after Magisk 18 and Pie update - before these updates i never got issues)
2. Now in twrp flash update zip
3. Flash anything that edits boot (ex. - custom kernel) if you want.
4. Now flash Magisk
5. Don'y flash any tweaks etc yet. (xXx NoLimits also)
6. Reboot.
7. Now if you want flash tweaks, modules etc.
8. And now only you are ready to flash xXx NoLimits again if you want.
**
*I guess this may help many of you in many cases.*
**
Click to expand...
Click to collapse
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
amitporedi007 said:
Can the DM Verity n force encrypt disbler installed after magisk and without formatting data
And which one is best for Android pie
Click to expand...
Click to collapse
Magisk must be flashed after dm...zip. But if you have already installed magisk then no worries. Flash DM Verity n force encrypr disabler and then again flash magisk. No need to format data in this case. Format data only needed when you are doing pure clean install of stock (based) rom. Check my signature, i am on OOS 9.0.2 that is android pie 9.0 and magisk v18. Decrypted (using that dm verity and force encrypr disabler).

[TWRP] 3.3.1 Aroma/Busybox compatible (ultra-low brightness)

Aroma compatible twrp (recovery.img) : https://androidfilehost.com/?fid=6006931924117889478
(tested on latest April Xperia Pie : 47.2.A.10.45)
BASIC guidance :
Be sure to read NewFlasher thread carefully first (Widevine L3 instead of L1 for locked bootloader).
0) recovery download
1) fastboot mode blueLight :$ fastboot flash recovery 270recovery9omni8-1FBEkeymaster3-twrp3_3_1.img
2) reboot STRAIGHT to twrp and always backup /boot only before Magisk-ified (needed with /system only in case of complete re-initialization or format, and for Treble roms)
3) flash magisk (min 17.3)
4) boot Pie (SafetyNet and Playstore certified should be ok with latest Magisk app after few mn)
Note: don't force remove bloatware: just disable them, so they won't reappear after future ota.
Once done, with your original /boot backup ( plus complete/full Magiskified backup), you can switch, without format /data, to my (xz1 enhanced) aosp Treble /system image: https://forum.xda-developers.com/pr...arm64aosp-9-0-0r21-microg-ufofficial-t3878115 , and restore back SonyXperia later with your full backup.
Future upgrade(ota):
-XperiFirm new firmware download + move away fotaKernel..sin & userdata..sin & simlock.ta + newflasher(with greenLight!)
-reboot STRAIGHT to recovery (and backup /boot only, before Magisk-ified)
-flash latest Magisk (min 17.3)
-boot Pie (SafetyNet and Playstore certified should be ok with latest Magisk app after few mn)
Optionally:
(-install Magisk Screen recorder or Snapdragon gallery, or aospEmail-SnapExchange free of analytics... )
-For better battery use KernelAdiutor with [conservative]highCpu & [ondemand]lowCpu (Adaway...)
Note: with or without su/hack, NightLight dim brightness is actually broken (wip)
Supplement:
This edition includes latest Aroma File Manager and TA partition backup: saves copies in sdcard/TWRP/ of TA, modemst1&2, boot.img plus some /vendor files like the identification build.prop ( default.prop fstab.qcom gps.conf uevent.rc). Every backup proceeds a copy of previous sdcard/TWRP/ TA.bin modemst1&2.bin and Id. build.prop in sdcard/TWRP/BACKUPS/.
Recovery simplified source : https://gitlab.com/oF2pks/twrppoplardevice/tree/aromaBusybox_Omni-8_1 (47.1.A.12.270)
with : TW_TARGET_USES_QCOM_BSP := false & Busybox v1.22.1
kernel : https://github.com/cryptomilk/android_kernel_sony_msm8998
prim-origin : https://github.com/cryptomilk/android_device_sony_yoshino/blob/lineage-15.1/twrp.mk
Thank you, working fine. How i change ui color? Flash the attached zips?
snake218 said:
Thank you, working fine. How i change ui color? Flash the attached zips?
Click to expand...
Click to collapse
No, just re-create (sdcard)/TWRP/theme/ui.zip exactly, and then launch Advanced§ReloadTheme from twrp recovery . Since I didn't include languages/*xml in them, you can only select Settings§Language without my uploaded themes (ui.zip) first. (Advanced§AromaFM & backupTA lines are also missing in regular uiBlueClassic.zip xml).
They are many twrp themes on xda, just be sure to use 3.3.0 ui.zip compatible edition.
Thanks for the new TWRP with Encryption. Device SOV36
Thank you for this fine version of twrp.
I am getting this error when making a full backup (ticked all partitions)
"error backing up system image, cleaning up folder"
I am running stock 47.2.A. 10.45 and j4nn kernel. Ric is off (i can write in system) and twrp are flashed.
i press "cancel" when asking for a password.
Normally the twrp just backup everything without any issues, so i must do something wrong??
Kind regards torben5247
Some themes for this ?
kojak1989 said:
Some themes for this ?
Click to expand...
Click to collapse
You can also use these themes for the 3.3.xx twrp
https://forums.oneplus.com/threads/custom-themes-for-twrp.849931/
Or if you search with Google, you can use all the 3.2.3 theme
theflanker said:
You can also use these themes for the 3.3.xx twrp
https://forums.oneplus.com/threads/custom-themes-for-twrp.849931/
Or if you search with Google, you can use all the 3.2.3 theme
Click to expand...
Click to collapse
but I do not know who will be good so that's why I'm asking
kojak1989 said:
but I do not know who will be good so that's why I'm asking
Click to expand...
Click to collapse
Why do you think it's a risk? If it doesn't work, it doesn't fit the theme and I use it!
@oF2pks
Hi, your newest version have original theme from TWRP or that from your previous version ?
Why can't I install any other ROM with this recovery?
Getting some invalid zip error.

/system corrupted

Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
MertFatih said:
Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
Click to expand...
Click to collapse
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
g_seva said:
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
Click to expand...
Click to collapse
Update: after format, it stucks on twrp(directories are not encrypted), and rom is not flashing at all I mean it is not writing to /sdcard (loading screen says it successfully flashed but not in the reality )and there are only 'obb' and 'TWRP' directories in the /sdcard also the twrp version is not even change by fastboot or flashing img after a reboot it recovers itself to build -0
I will try it with the Chinese teams's twrp build for this time
Solved with another twrp version

Installing, Updating, Backup and Restore Guide for OP6/6T

This is a bit late but why not. THIS IS A COMPILATION OF ALL THE OS METHODS YOU NEED FOR THE OP6/6T.
ENJOY my guide
DISCLAIMER:
*I am not responsible for bricked devices, damage to your device*
Sorry for a long list of methods, some work for others and some don't. But I recommend to pick a method and stick to it. Maybe read the part at the top as some have notes about mine or someone else's experience/recommendation. Don't skip steps and follow each step.
If stuck, just ask and I or anyone else will try and help
I am here to post methods for anyone who is interested/need help. I have tested these myself and helped others who may be struggling
Download
The guide has loads of files/ zips/ tools to use/flash/install. But no worries as everything can be downloaded and there are links AT THE BOTTOM OF THIS THREAD (NOT COMMENTS) to where to download:
SDK Platform Tools (Fastboot tools) from Developer Android
TWRP from mauronofrio
Magisk from topjohnwu
Gapps (Google Apps) from NikGapps. I recommend omni for ROMs that don't include Gapps.
Fastboot ROM for OP6 + OP6T from mauronofrio
MSMDownload tools for OP6 + OP6T from Some_Random_Username
IMPORTANT NOTES!
YOU REQUIRE Platform Tools (Fastboot Tools) IN ORDER TO USE THE METHODS IN THIS GUIDE AS TWRP NEEDS TO BE INSTALLED!
YOU NEED TO HAVE A UNLOCKED BOOTLOADER AS WELL!
For GAPPS, u can use the same or a updated version of the package. But has to be the same type u used to install it like (stock, full, Omni, basic, etc). ONLY FLASH/INSTALL IF the RESTORE SCRIPT DIDN'T SHOW UP during a DIRTY FLASH/UPDATE AND ONLY FLASH AFTER REBOOTING TO RECOVERY AFTER FLASHING/INSTALLING A OS/BUILD ZIP FILE!
How to get Platform Tools
These tools are used to install TWRP, to unlock the bootloader of your device and is needed to use the METHODS in this guide.
Download the platform tools.zip of your software platform (Mac, Windows, Linux)
Extract the platform-tools.zip
To use it go into your platform-tools folder
Press shift + right-click and choose command prompt or PowerShell
Connect your device when it's in fastboot mode and done
How to install TWRP
Sadly this Guide is for Windows, but other platforms like Mac or Linux can be found online.
YOU CAN USE THIS METHOD TO INSTALL A NEWER VERSION OF TWRP TOO
You need to have downloaded Platform Tools which the link is attached below.
Transfer the TWRP.img file into the platform-tools folder
Now transfer TWRP.zip into your device's internal storage. (connect -> allow file transfer -> drag and drop files)
If you want root download and transfer magisk.apk and the link is supplied below. Also, RENAME from .apk to .zip
Now we must boot into fastboot mode. (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Now connect your device to a Windows device
Press shift + right-click. Choose command prompt or PowerShell
Enter "fastboot devices" and your device should be displayed if it's connected
Type "fastboot boot twrp" file name (do twrp + press tab) and press enter
Then you should be booted into TWRP
Enter the password and swipe to allow modifications
Press install and find your TWRP.zip file
Swipe to confirm Flash
If you want root do this
Press the back arrow and find your magisk.zip
Swipe to confirm Flash
Reboot to the system and done
Otherwise, just reboot to system. Up to u
Installing a Custom ROM
Install Custom ROM on OP6T from OOS
Make sure u have BACKED UP your device and have the latest OOS installed in both slots. If u do, go to Method 3.
If u have finalize.zip, go to Method 2.
Method 1
If u don't have OOS installed in both slots or finalize.zip, use this method.
Transfer OOS.zip file, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot TWRP
Flash OOS + TWRP
reboot recovery
Flash OOS + TWRP
Reboot recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
If u have finalize.zip, do this method. Using finalize is way quicker as there's less flashing and rebooting.
Transfer OOS.zip file, finalize.zip, TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash OOS + finalize
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 3
Once you have installed OOS in both slots do this part.
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to Bootloader
Boot to TWRP
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Reboot to system
Otherwise, just Format data -> reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Installing Custom Rom not from OOS
You can use finalize method or just flash OOS + TWRP way. The finalize way is there for some who like less flashing and rebooting.
Using the methods in Install Custom ROM on OP6T from OOS
Using the old way, use Method 1
Using finalize.zip, use Method 2
Remember to factory reset (wipe, but no need to wipe internal storage)
Backing Up OOS and Custom ROM
Make sure u have installed the latest TWRP version from mauronofrio
You should use TitaniumBackup or Migrate to back up your apps and contacts.
Also, have a copy of your Internal Storage folders if u have important files.
TWRP Backup backs up your OS like Apps, settings and set up, but not internal storage.
NEVER BACKUP SYSTEM AND VENDOR! ONLY SYSTEM.IMG or VENDOR.IMG IF YOU HAVE TO!
Restoring it makes going back way easier like you have never left
Or you can go manually and try and restore everything, but why do that when you got TWRP?
I do both ways of backing up
Backing up OOS
Boot TWRP recovery
Choose Backup
Choose boot, data. YOU DO NOT NEED TO BACKUP System.img and Vendor.img!
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Backing up a Custom ROM
Boot TWRP recovery
Choose Backup
Choose boot, data, system.img, vendor.img
Swipe to backup
Once done, either boot to system or mount
Transfer the whole TWRP folder onto a storage device
Done
Restoring OOS and Custom ROM
Restoring OOS TWRP Backup
To restore OOS use either fastboot ROM or MSM. Fastboot is the fastest and easiest way if u have a TWRP backup which there's a method to how to make one in this guide. BUT if you are restoring to go back to stock OOS then use MSM
I use Fastboot ROM restore for that too as we are restoring our data anyways and also for switching/installing a custom ROM. Much easier in my experience.
DOWNLOAD FULL ZIP OF OOS version of your TWRP backup otherwise you could risk doing the whole restore method again OR setup from SCRATCH! IF you aren't restoring a TWRP backup, I recommend either TRANSFER or DOWNLOAD via WiFi or oxygen updater, a UPDATED version of OOS AFTER doing either fastboot ROM or MSM restore methods. As they restore a old version of OOS!
Restoring using Fastboot ROM
Download fastboot ROM of your choice using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Restoring using MSM Download Tool
Download latest MSM version of your choice using the link in the Download Link section.
Extract/ un-zip
Click on MSM tool .exe file
Turn off device
HOLD BOTH volume buttons
Connect your phone
Wait for your device to be connected and it should show as green
Click verify to check and press start
Wait till phone reboots
The setup device and u can carrying on restoring your device if u don't want a unlock bootloader or return to what your device was like before.
Go into developer options
Allow OEM unlocking
Reboot to bootloader
Enter "fastboot devices" to check your device is connected
Enter "fastboot oem unlock"
Swipe for yes
Then it will reboot again
continue to the next method
For both fastboot and MSM
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore only boot and data
Swipe to restore
If you have backed up your internal storage folders do this
Reboot to recovery
Transfer all your internal storage folders
Reboot to system and done
Otherwise, just reboot to system. U can update OOS as well if it's outdated. The method is below to update OOS with ROOT. Up to u
RESTORING TWRP BACKUP HAS ISSUES ON THESE ROMs
CrDroid (Method 1 + 2 don't work). Method 3 works (install Gapps if the ROM doesn't have it!)
Restoring a Custom ROM TWRP backup 1
I tried using this method, but it didn't work for me.
You can use this method to switch ROMs too
Boot TWRP Recovery
Flash OOS + Finalize
Boot to bootloader, boot TWRP
Flash TWRP
Reboot Recovery
Transfer twrp backup
Restore System.img, Vendor.img and boot
Boot to system and setup system
Reboot to recovery
Restore data
Reboot system. Done
I had an issue with this method where rebooting system it was from fresh and my data didn't restore. If this happened to you, then do method 2 (Restoring a Custom ROM TWRP Backup 2)
Restoring a Custom ROM TWRP Backup 2
The first method didn't work for me. But this method did
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up briefly and DO NOT RESTORE ANYTHING.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot recovery
Transfer whole TWRP Folder into internal storage
Restore everything (System.img, vendor.img, boot.img and data)
Swipe to restore. If data couldn't restore then boot system, setup system, boot TWRP and restore data.
Reboot system. The first reboot might go dodgy and it did for me.
Reboot system and transfer all your internal storage stuff
done
If this did not work still. Then do the 3rd method...
Restoring a Custom ROM TWRP backup 3
If the previous 2 methods has failed for you. Then try this.
Restore fresh like you're going back to OOS.
Choose one method. Fastboot or MSM method.
I prefer the fastboot method.
Download fastboot ROM using the link in the Download Link section.
Extract/ un-zip
Boot your device into fastboot mode (Either do it with the advanced reboot in developer options or power off device -> boot recovery Vol - + power -> boot to bootloader or power off device -> press Vol Up + Vol down + power)
Click flash-all.bat
Once booted into system, set it up and update to OOS version of your TWRP backup.
Download the full zip using the link in the Download Link section.
Transfer the OOS .zip to internal storage.
Go into settings -> system update -> Update via local upgrade -> find zip file and press install
Do this twice to make sure you have installed that version of OOS in both slots
Transfer TWRP.zip, Build.zip (Custom ROM zip file) into internal storage.
Boot to bootloader
Boot TWRP
Install TWRP
Reboot to Recovery
Flash Build.zip (Custom ROM zip file)
Flash TWRP
If the ROM doesn't have GApps included do this
Reboot to recovery
Flash Gapps if not included
Format data
Otherwise, just Format data -> reboot to recovery. Up to u
Reboot Recovery
Transfer twrp backup
Restore data
Reboot system. Done
If it still fails, repeat steps 1 to 15. But restore everything and you should be back on your custom ROM like you never left.
Updating OOS and Custom ROM
Update OOS with Root (Magisk)
Always do a TWRP backup before updating your OS in case
Download the full zip file of the latest OOS, transfer the zip file to internal storage NOT IN ANY FOLDER
Download and transfer twrp.zip file to internal storage
Go into settings, system update, update via local upgrade and choose the file
Wait till the installation has finished. If failed TRY AGAIN!
DO NOT REBOOT!
Go into Magisk Manager, modules
Find the twrp zip file and install TWRP
DO NOT REBOOT!
Go into Magisk Home
Press install
Press install via inactive slot
Reboot system and done
You will reboot into the next slot
You don’t have to repeat the installation to install the latest OOS in the other slot. But you should and I use this method many times and has never let me down.
Updating OOS without root
Go to System Update -> find the update install and reboot.
Or download the zip -> transfer to internal storage -> update via local upgrade -> reboot and done
Update a Custom ROM
Method 1
Always do a TWRP backup before updating your OS in case
Use this method just to update the ROM.
Boot recovery
Flash new version + twrp
Reboot recovery
Flash new version + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Method 2
This method uses finalize.zip
Boot recovery
Flash new version + finalize + twrp
If the ROM doesn't have GApps included,
The restore script should show up during the installation of the new ROM.zip
BUT if the restore script DIDN'T pop up do this
Reboot to recovery
Flash Gapps if not included
Reboot to system
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system. Up to u
Updating vendor
Use Method 1 and 2 for ROMs with Gapps. Use Method 3 for ROMs with no Gapps included.
Method 1
If u haven’t updated your Custom ROM and your Vendor… You can use this method to update both or just the vendor.
Boot recovery
Flash OOS + twrp
Reboot recovery
Flash OOS + twrp
Reboot recovery
Flash Custom ROM + twrp
Reboot recovery
Flash Custom ROM + twrp
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 2
This method uses finalize.zip
Boot recovery
Flash OOS + finalize + twrp
Reboot recovery
Flash Custom ROM + finalize + twrp
Otherwise, reboot to system. Up to u
If you want root do this
Reboot to recovery
Flash Magisk
Reboot to system and done
Otherwise, just reboot to system
Method 3
This method is for ROMs with no Gapps included
You can use this method as well for updating to a vendor that has a NEWER ANDROID version like from OOS 10 to OOS 11 vendor.
Boot recovery
Flash OOS + Custom ROM + twrp
Reboot recovery
Flash OOS + Custom ROM + twrp
If u flashed GApps, the restore script should show up during the installation of the ROM.zip
If the GApps script didn't show up do this
Otherwise, skip step 3
Flash Magisk if u want root, otherwise skip step 2
Reboot to recovery
Flash Magisk
Flash Gapps
Reboot to system and done
Download Links:
SDK Platform Tools (Fastboot Tools) Here
OOS versions for OP6 (under Signed Flashable zips) Here
OOS versions for OP6T (under Signed Flashable zips) Here
TWRP for OP6 Here
TWRP for OP6T Here
Magisk Here
NikGapps Here
Stock Fastboot ROM for OP6 Here
Stock Fastboot ROM for OP6T Here
MSMDownloadTool for OP6 Here
MSMDownloadTool for OP6T Here
TitanumBackup App Here
Migrate App Here
Credits:
@mauronofrio For his amazing work on the TWRP recovery and Stock Fastboot ROMs for OP6/6T
@topjohnwu For his work on Magisk
@Nikgapps For their work on creating Gapps
@Some_Random_Username For his Collection of MSMDownloadTool for OP6/6T
@OPTeam For the collection of OOS zips for OP6/6T
@dreamwhite For the method (Method 3) of updating the vendor which works wonders for ROMs with no GApps included
First
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
plepew said:
Hey Guys,
Need a some expert advice please.
Long story short. I need to replace my OP 6T McLaren's battery as I have serious degradation in battery capacity (73% Serious Loss), meaning the battery is no longer charging to 3700mAh, max charging atm is around 2600mAh, which it drains very quickly. FYI Anything above 80% is the limit for average performance, >90% is best. You can use the OP Diagnostic App 1.0.0.9 to determine your own status. Does not work on all OP devices above 6 btw. Maybe other versions work. Anyway, will be getting OP to change the battery (no real local guys I can trust tbh, all Sammy & Apple guys...) and they want me to Factory Reset the device (complete wipe including internal storage (backed up already to PC)) before sending the device to the OP Repair Center for the obvious reasons of Privacy & Security.
On my device, I have a suite of apps that are no longer available to install with APK specially Signed, but won't be able to re-install (long story & can discuss in a PM more if there is an interest to help on this). These APK will not work any other way, I've tried! This being said, I know that TWRP Nandroids work well & have been doing these backups for yrs and have restored backups with these apps installed and it works! But I have not had to restore any as of late and TWRP Backup has somewhat changed in regards to the partition selections available. See TWRP Options pic below.
When OP returns the device to me, it will mostly likely be on the latest release of 10.3.11 (Hopefully).
Here is the current setup and runs perfectly!
OOS 10.3.11
TWRP: twrp-3.5.2_9-0-fajita
Magisk 23
The last Nandroid done today (No PW for good measure, but secured locally offline), I selected all partitions. Is this the best way to insure I get my full device backup restored?
View attachment 5319753
I'm guessing that I will have to, Unlock the Bootloader, reinstall TWRP same version the Nandroid was created with in order to restore that backup.
Looking forward to hearing from you guys to make the best decision before proceed with the factory reset.
Thanking you all in advance for your time & assistance!
Cheers!
Click to expand...
Click to collapse
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Extreme_Ninja2099 said:
Idk if u have read Mauronofrio's XDA thread on TWRP backups. BUT NEVER BACKUP OR RESTORE SYSTEM OR VENDOR! From my guide, you don't need to backup vendor.img or system.img or anything else that's not Boot or Data FOR OOS. Make sure you have everything like a copy of everything folder/file in your internal storage before u wipe it.
BUT because you're going to wipe your device. U should have a copy of everything in case but don't backup system or vendor as they're useless and will crash your system if u restore those!
After you've got your device from repair, follow my method to restore OOS TWRP backup on your device and YOU'LL only NEED TO RESTORE BOOT + DATA. Once you have booted back to your system, everything should be there like you never left, but transfer your internal storage stuff as some apps store files in your internal storage. Once that is done, that should be it and it would be like you've never left
If the TWRP backup restore doesn't work let me know, but from my experience with going back to OOS via my TWRP backup I only backed up and restored boot + data for OOS. Custom ROMs are different but isn't the case for you
Click to expand...
Click to collapse
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
plepew said:
Wow, thanks for the quick reply!
I have not read Mauronofrio thread and will do!
I completely missed the system & vendor piece in your instructions....my bad!
So just to confirm, my backup that I have done with all checked off is good, but only restore Boot & Data with an exact duplicate of the current Internal Storage...right?
Going forward, when creating the Backup, just select Boot & Data and I'm good to go? Or select all Except: System Image(only) & Vendor options (both)?
Also, just so I can understand a bit better, "System" is the actual OOS? Meaning, if I restore Boot & Data on any OOS, all my apps and data will be as I never left, or we should always restore on the OOS that was current at the moment of the Backup (which I have always done in the past).
PS. I may just do the backup again, just to make sure SYSTEM & VENDOR are not there for good measure!
Click to expand...
Click to collapse
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Extreme_Ninja2099 said:
First off, I already posted everything you need in my last comment and that's what I usually do. Everything should be there and not like you need to pay or reply to get the extra stuff that you may need. No point in replying asking for more as I'll just be repeating myself over and over.
Just choose boot & data for TWRP backups for OOS specifically going forward and after you got your device from repair. System, vendor doesn't work in my experience and will crash your system. Only backup the .img variant which was stated by the dev (Mauronofrio) for TWRP for OP6/6T devices. Only backup system.img and vendor.img if u need to backup system+vendor, but YOU don't have to for OOS and I said this previously.
JUST DO A BACKUP OF EVERYTHING OTHER THAN SYSTEM AND VENDOR. YOU SHOULD ONLY BACKUP SYSTEM.IMG AND VENDOR.IMG NEVER SYSTEM OR VENDOR.
They never work and will increase the size of your backup and will take even longer to transfer to your storage device from your phone.
YES, to your new question. You should update/ be on the same OOS version as your TWRP backup before u restore data + boot. Restore OOS via fastboot or msm and update to get to the same version of OOS as your TWRP backup. YOU should only do this if your phone is in the wrong version of OOS as your backup after you've got it back from REPAIR.
ALWAYS BE ON THE SAME VERSION OF OOS AS YOUR TWRP BACKUP BEFORE YOU RESTORE YOUR TWRP BACKUP OF OOS!
Maybe take a copy of your wifi passwords, take a google backup in settings, take a copy of sms/call logs and contacts. Other stuff that you may not have stored just in case the TWRP backup fails, but it shouldn't. Good luck
This should be it and there isn't anything else that you'll need
Click to expand...
Click to collapse
Thank you!!
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
thanking you guys in advance for you help & guidance!
plepew said:
Hey guys, for some reason I ended up on "Unmodified System Partitions", must have tapped the screen a few times in error while handling the phone I guess.
What should I do?
Unable to go back to TWRP main menu without selecting an option.
I am rooted, on stock OOS and not doing customs ROM at this time...
What should I do?
Select "Keep Read Only"? or Swipe to "Allow Modifications"?
View attachment 5320971
thanking you guys in advance for you help & guidance!
Click to expand...
Click to collapse
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Extreme_Ninja2099 said:
Swipe to allow modifications. But it seems that your internal storage corrupted. Not sure what you did and how you got into this situation.
After you swiped to allow modifications... If the internal storage files are a messed up, try to switch slots and reboot recovery
Click to expand...
Click to collapse
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
plepew said:
I swiped and yeah, the IS was messed up in File Managfer(TWRP).
Selected Reboot then Selected the Slot I remembered I was on : "A"
Rebooted & Boom all good!
Thank you for the help once again! You rock!!
Click to expand...
Click to collapse
Cool and at least that was a easy fix
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
jas84701 said:
Sorry, I'm a total noob, hopefully this is an easy question to answer. Is there any way that I can tell what version of OOS my TWRP Backup contains? I can't remember what version my phone was running when I did the TWRP backup and don't want to mess it up after I restore the phone from MSM. Thanks in advance for your help!
Click to expand...
Click to collapse
Well u posted this twice which isn't necessary and people will try and reply. But I'm not sure if there is a way to know and as long as u copied the whole TWRP folder for that backup, u should be fine restoring it with a newer version of TWRP. If it really matters to you, then maybe try and find the latest TWRP on the date you did the backup? I think just using a newer TWRP version should be fine
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Waynenolan92 said:
Should I use the same Gapps package I flashed during clean installing when updating custom rom?
Click to expand...
Click to collapse
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this helps
Extreme_Ninja2099 said:
U don't have to use the same gapps package. Using a updated one would be better. But, u only have to for ROMs that don't include gapps (vanilla builds) AND the Restore script doesn't show up during installation. Opengapps doesn't have that script but nikgapps does. Using dirty flash/updating a ROM should show the restore script and if it doesn't then just reboot to recovery and flash the updated or same gapps package. This can also be the same for updating the base/vendor (use method 3 in that section of the guide). I hope this help
Click to expand...
Click to collapse
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Waynenolan92 said:
Thanks for your replay)))it's my first using vanilla rom(without Gapps), so I flashed nikigapps Omni package, and my question is: should I always use the same package, or I can go with core package for example?
Click to expand...
Click to collapse
U can... But it doesn't really matter as a updated package works fine and u only need to use it if the nikgapps restore script doesn't show up when updating the ROM or vendor/base (OOS underneath)
I want to CHANGE custom ROMs (havoc to Lineage OS a11 to a12) I have taken TWRP back up of boot+data+system.img+ vendor.img. once I flash the new a12 Lineage plus Nikapps core plus magisk. What steps to restore data? any response is appreciated in advance. Thank you.

Categories

Resources