Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
New version 2012-02-01: data wipe and then restore, backup to external and to internal (internal is now the default).
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Ok - first identified issue: If we are backing up to the external sdcard. This is fat32. So we have a file size limitation.
Also there may be a tool set size limitation in the binaries (as ported). This mainly affects "data", as this seems to include
pictures, video etc from the /data/media directories. So looks like to me data > 2G wont restore. Although it does create
(in my example 3.5G file and checksum is ok). I found that the 3.5G would not load. I retarred with all stuff in /data/media
deleted, (and fixed the nandroid checksum) then the data file loads (about 900M) and my device is recovered. I'm expecting if you try to back up more than 4G, the file will not be usable due to FAT32. I Hope this is clear.
So please check your file sizes (and nandroid sums) before attempting a restore.
So with this in mind,
Update: 2012-02-01: now backing up in the CWM tradition by default to the internal sd (which is ext4), and there are extra options enabled in the backup/restore menu. Please remember we are still in test mode. I think It is now working as intended and not backing up /data/media its easy to tell from the size of the data nandroid file.
So please backup your precious videos, pics etc from the /data/media directory independently.
Odin tar file (in the pda):
davp said:
Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Odin tar file (in the pda):
Click to expand...
Click to collapse
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
padebije said:
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
Click to expand...
Click to collapse
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
davp said:
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
Click to expand...
Click to collapse
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Ok guys, looks like there are file size issues due to fat32 external sdcard etc.
I believe the tool can still be useful, but be aware its limitations.
Have documented this in the first post as an issue.
The download is the same (I cant fix the fat32 limits).
padebije said:
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Click to expand...
Click to collapse
I use the one I had installed months ago (for phone). It the same version (downloaded mine from Intratech's gs2 official rom thread).
Sent from my GT-I9100 using XDA App
BRAVOOOOO!!!!!
I deleted all movie files > 2GB, and tried backup, wipe data, and restore again.
This time, I could make it thanks to your advice!
davp & ezy now, looks like you're famous.
http://www.theandroidsoul.com/new-g...or-both-3gwifi-edition-and-wifi-only-edition/
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Hi davp,
You should push source to git hub, perhaps we could enlist Koush or Codeworkx to assist us. of all the options i have tried with recovery.fstab i was never happy.
i could never get both internal and external sd cards to mount. when i had them both setup the menu options for flashing and restore / backup will show option for internal sd cards.
IMHO, recovery should back up to external, as if you really bung up your device you will not have access to internal memory. The fact most of us only have 16gb internal memory its makes more sense to back up to external sd card.
i remember the nook colour, had a simalar debacle when they 1st released CWM mod for it. you could look there. i really havn't had a chance to dig into this. perhaps over the weekend i get more time
davp said:
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Click to expand...
Click to collapse
Any chance somebody could please extract stock recovery and send me a target version?
Sent from my GT-P6810 using XDA Premium App
Tar not target...
Sent from my GT-P6810 using XDA Premium App
Help
Hi Guys,
EDIT: - I flashed an incomplete tar file as the download had not finished when I copied to sd card.
Got a small issues,
I have a Tab 7.7 running HC 3.2.
I gained root access and then install mobile odin pro.
I then proceeded to install this CWM and its not stuck at the galaxy tab 7.7 black and white screen at boot.
I selected the file i downloaded here using the recovery option to flash in mobile odin.
any ideas what i can do to get this working again?
Many Thanks
Syl
F2FS improves the benchmark score in most (if not all) devices by around 20%..
For testing:
I have modified an APK containing Aroma Installer to flash recoveries to fotakernel for our ZR's. This is an initial release..
It contains 2 recoveries.
PhilZ Touch and TWRP with f2fs (TWRP) support which has been tested and working in both Resurrection and Validus builds/ports and should work in all cm11 and CM12/CM12.1 with f2fs working in cm12 after march this year
Install the apk and flash either Philz or Twrp through the app in the drawer..
And no, this is not Xperia Recovery manager.
The recoveries are both contained in the app so making it 22MB to download.
The TWRP 2.8.7.0 has new graphics and f2fs support
PhilZ is stock 6.57.9 cwm v6.0.5.1 shared by @uncomment
Download APP here (contains the 2 recoveries mentioned above): Removed because of bugs.. will fix and upload to new link..
TWRP 2.8.7.0 f2fs with updated graphics flashable zip: https://drive.google.com/file/d/0B3slVcYWwXQ-RjNKUDhWWk5OemM/view?usp=sharing
(This is the latest recovery from TeamWin with their new blue theme.. I personally didn't like all that blue so I changed the images.. See screenshot below)
Philz Touch 6.57.9 flashable zip:https://drive.google.com/file/d/0B3slVcYWwXQ-MEd4TU1vb0NYcmc/view?usp=sharing
Flashable ZIP stock TWRP 2.8.7.0 with f2fs:
Put the zip in you sd card and flash through recovery.. This will push the twrp 2.8.7.0 f2fs to your fota kernel, reboot recovery after flash...
Download: https://drive.google.com/file/d/0B3slVcYWwXQ-YTB6V1N0eEx5SU0/view?usp=sharing
Please test (recovery.img)
UPDATED TO TWRP 2.8.7.0
Download here: https://drive.google.com/file/d/0B3slVcYWwXQ-SjJRRjdyZ2pzeXc/view?usp=sharing
Instructions are the same as below...
This is TWRP 2.8.6.0
Download here:
https://drive.google.com/file/d/0B3slVcYWwXQ-Q0pEYzlFSjhPNFk/view?usp=sharing
Place the recovery.img (it is named twrp.img when you download but rename to recovery.img) to you internal storage and use adb or emulator (download Android Terminal Emulator free from Store) commands to install to your Fota:
su (enter and grant root access if using Emulator)
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel (enter)
If you use Xperia Recovery Manager app by @championswimmer, rename the recovery.img to twrp.img and put in the TWRPXperia folder on your sd-card and flash to Fota through the app. Confirmed working.
If the image doesn't install correctly, please flash this hack:
http://forum.xda-developers.com/show...51&postcount=2
Only cache and data/ ext-sdcard is convertible for now, if you try to convert system, you will brick your phone..
Use the following method to convert:
Convert to f2fs by pressing Wipe > Advanced Wipe > select the desired partition > Repair or change filesystem > Change filesystem > f2fs
Some added info by @nostupidthing
with f2fs twrp installed, i've changed /cache and /data into f2fs without wiping. you just have to backup /data, then format it as f2fs, click "use rm-rf instead for format" in twrp settings, then restore /data.
If any one is looking for a theme for twrp recovery, i found an excellent theme here: http://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
(Download resolution 720x1280 for ZR)
As an added service I am willing to personalize the splash screen at recovery start-up should you have any request ie your name, flag etc but i will insist that "TeamWin" will be present somewhere on your personalized splash.. After all, we all benefit from their hard work.. Do not expect your request to be done within the hour but periodically check and i will upload and link as and when you request is done..
Massive thanks to @uncomment and @o-l-a-v and @Olivier and @blastagator and @qsnc including @nostupidthing for testing and for making this possible. @SdtBarbarossa for the app!!
the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.
nostupidthing said:
the "now changing the microsd to f2fs" is not necessary for /data & /cache. you may or may not like to do it, and i ended up not doing it because copying my several gbs of files out of the microsd takes so much time and i just gave up..
but if anyone wants to do it, basically you just copy the files to your PC, then format the microsd to f2fs, then copy the files back there.
Click to expand...
Click to collapse
I agree with you.. I have formatted my ext sd card but like you said, took ages to copy the content to pc and back again.. In my opinion not worth doing if anyone, like me, use the ext_sd card for storage of music and downloads etc.. Cache and data absolutely worth doing tho.. A great many thanks for your comments and help doing this..
sent from Paul's phone
one more thing. backing up /data via twrp will not back up your "internal sd" files, like camera photos if you store them internally instead of on the microsd, so you have to copy those yourself as well.
Added flashable zip to op... Should make things easier..
the 2.8.7 flashable zip works, bro. thx.
hey, any chance that you make an insaller version ?
Ilko said:
hey, any chance that you make an insaller version ?
Click to expand...
Click to collapse
I'll look in to it..
hagar006 said:
I'll look in to it..
Click to expand...
Click to collapse
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.
Ilko said:
Great
BTW, I would suggest you to set TWRP's file manager to open SDCARD1 by default instead of SDCARD0, if possible, or even both to let users choose. I'm not sure if this is ROM or Recovery dependent because it worked this way through the latest Validus ROM. I'd bet on the recovery side though.
Click to expand...
Click to collapse
It's party of the recovery but a few spaces down from the top in file manager is external_SD and a few spaces lower is SD_card so should be easy enough to find the way around..
BTW I've made new images and things for twrp which makes it a little easier to see but I'm waiting for permission from someone as I used their ui.xml to make that.. Will be added as soon as
Sent from my ZR
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.