Database Develop

Configuring Dual Boot [Flashable Configuration Zip v1.0 Released! 23 Jul 2012]

I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether by flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
Config-Dual-Boot-v1.0-signed.zip: http://www.mediafire.com/?edgat0koyp7d33l
Backs up /sdcard[-ext]/Boot (if it exists) to /sdcard[-ext]/Boot.bak
Creates Boot/ROM1 and Boot/ROM2 directory paths under /sdcard[-ext]
Installs Script Manager on ROM1 and ROM2
Contains shell script “copy-boot.sh” to copy ROM boot partition to boot image file
Contains shell script “boot-rom.sh” to switch to boot ROM2 from ROM1 and vice versa
The updated “boot-rom.sh” script now features generic boot image directory names: Boot/ROM1 and Boot/ROM2, and automatically captures the SD Boot directory path (/sdcard for CM ROMs and /sdcard-ext for Blur ROMs).
Instructions:
1. Boot to ROM1 (emmc)
2. Reboot to CWM and flash: http://www.mediafire.com/?edgat0koyp7d33l . Doing so will backup any existing Boot directory under /sdcard[-ext] and push a new Boot directory containing empty subdirectories ROM1 and ROM2 and two shell scripts: copy-boot.sh (copy boot partition to image file) and boot-rom.sh (boot switcher).
In the following steps, the shell (sh) commands can be run using ADB (Android SDK Platform Tools), Terminal Emulator, Script Manager or other suitable app.
3. Reboot to ROM1
4. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh”. This detects which ROM is running, ROM1 in this case, and copies its boot image to /sdcard[-ext]/Boot/ROM1
5. Configure Script Manager to execute “sh boot-rom.sh 2” which enables booting to ROM2. But do not run this command until ROM2 “boot.img” is in place. We'll do that now.
6. Reboot to fastboot and connect phone to computer.
7. Enter: “fastboot flash boot boot.img” where boot.img is a boot image file modified to host ROM2 on SD. Please see my Auto-Modify Boot Image thread.
8. Enter: “fastboot reboot"
9. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh” as in step 4.
10. Configure Script Manager to execute “sh boot-rom.sh 1” which enables booting to ROM1.
More on configuring Script Manager:
Go to Settings > More > Advanced Options > Config > Home Directory. Set home directory to /sdcard/Boot. Then while still in SManager, navigate to /sdcard/Boot and press boot-rom.sh to configure. Valid arguments are:
Code:
blank: Reboot to current ROM
1: Reboot to ROM1 (emmc)
2: Reboot to ROM2 (SD)
3: Reboot to recovery
Press the “Su” box to run as root (note green symbol) and press “Save” at top right. Then press “Run” at top left to launch boot-rom.sh and reboot to the other ROM.
Place shortcut to Script Manager on home screen.
If all goes well, you can now boot ROM2 from ROM1 and vice versa with just a few screen taps.
This procedure was tested working with Neutrino V2.8 EE (CM) on emmc and NottachTrix 1.3.1 ATT (Blur) on SD.
Legacy YouTube video (3:38) showing reboots from one ROM to the other: http://www.youtube.com/watch?v=31TPyAguQ60
Credits
Special thanks to jokersax11, Notorious544d, ATRIXXIRTA, ghost_og, hatefuel19, J-Roc and many others for their technical direction, useful suggestions and encouragement. And of course to the Photon/Atrix/Android dev teams, Koush and https://sites.google.com/site/devwom/

Thanks a lot dude! Im going to try this!

how do you install two roms at the same time? i thought this was showing how to do that but im confused. how do you change the cwm zip installers to .img?
edit:: sorry i thought this was the other thread showing how to install a dual boot system but in fact its how to configure it to boot into them easier. sorry for the mixup ill defiantly read over your 1st thread

Note: Joker recommended as a refinement to place all apps in sdcard to keep apps common to both builds. Good idea.
Click to expand...
Click to collapse
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!

Notorious544d said:
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Click to expand...
Click to collapse
Thanks for the good questions. I haven't yet considered Joker's tip in detail as I spent most of yesterday writing this thread, researching other related topics (and watching Downton Abbey with my beloved wife ). But off the top, I assume that if a given app works on both ROMs, theoretically there should not be a problem hosting it and its corresponding data on the kitchen table (sdcard).
I guess one of the challenging questions is: Are there certain apps for which data should be kept separate to enable ROM-specific customization?

I just updated my thread with this...
"Alternatively (and actually preferred), you can extract the contents of this zip: http://www.mediafire.com/?0kdp4qvy6fv71kp to /sdcard. It makes ROM selections generic, and also fixes a problem with boot-rom.sh (Android shell apparently does not like trailing spaces in script files.) Then drop your boot.img files into /sdcard/Boot/ROM1 and ROM2 and you're good to go."
Cheers.

I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...

[RECOVERY] TWRP v2.4.4.0 - GMod v0.1.1 for unlocked devices

Hey there!
Because there is still no TWRP released, I decided to build it.
I used to code in C++ since 2005. Made alot of stuff. Now I'm moving to android.
I used the official CM10.1 sources (+kholk's) and the official TWRP sources to compile it on OS X Mountain Lion 10.8.3 (initial release was compiled on Ubuntu 12.10. With GMod I'm using OS X)
It's using kernel 3.1.10 (extracted from boot.img) and some files from its ramdisk.
The output was a working TWRP recovery. Internal Storage (/data/media) works to use it as backup storage.
External SDCard should also be working, since you can change where to backup in TWRP settings (internal/external). I did not try that, cause I don't own an external sdcard
To boot recovery just hold down Power+Vol-Down.
To install zips navigate to /emmc (internal) or /sdcard (external)
Note: If you have a folder called 0 inside /sdcard, then move its content to the root of /sdcard and delete the folder 0 (/sdcard/0). Otherwise TWRP will act weird and the internal storage doesn't get properly mounted but would still be fully functional.
How to install (some methods, you can choose one of them):
1) Using fastboot:
Code:
adb reboot oem-unlock
fastboot flash recovery twrp2440-recovery.img
fastboot reboot
2) Using adb or Terminal Emulator (place on root internal storage[/sdcard])
When using adb
Code:
adb shell
then, same when using adb or Terminal Emulator
Code:
su
cat /sdcard/twrp2440-recovery.img > /dev/block/mmcblk0p1
sync
That's it. Hope it works well for you as it does for me.
Changelog:
Code:
v0.1.1
Added Aroma Filemanager
Added Clockworkmod Touch 6.0.3.0
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)
gordon0001

Re: [RECOVERY] TWRP v2.4.4.0 for unlocked devices
Thaaaaanks !!! TWRP is much better , easier , and faster than CWM .
It's always good to see new development threads :good:
Sent from my LG-P880 using xda app-developers app

Updated.
Decided to customize TWRP.
Aroma Filemanager, CWM, and more will come soon to be included in my custom TWRP.
Changelog:
Code:
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880 (Reboot recovery in recovery)
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)

gordon0001 said:
Updated.
Decided to customize TWRP.
Aroma Filemanager, CWM, and more will come soon to be included in my custom TWRP.
Changelog:
Code:
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880 (Reboot recovery in recovery)
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)
Click to expand...
Click to collapse
Great!

Updated.
Changelog:
Code:
v0.1.1
Added Aroma Filemanager
Added Clockworkmod Touch 6.0.3.0
To access them go to Advanced --> Extras

This looks very nice gordon0001! Thanks for posting. Can I use this as an alternative to CWM, since it doesn't work for me properly? Can it use zip packages with no incompatabilities?

Feregorn said:
This looks very nice gordon0001! Thanks for posting. Can I use this as an alternative to CWM, since it doesn't work for me properly? Can it use zip packages with no incompatabilities?
Click to expand...
Click to collapse
Most zip archives that works for clockworkmod works also for twrp. just flash my modded recovery and you have both.

Cant mount sd-card!
I cant mount sd-card in recovery, extsd is working tought...
Any ideas?
EDIT: I can see the log says "E: Unable to find partition size for ' /sdcard'"

eliel1301 said:
I cant mount sd-card in recovery, extsd is working tought...
Any ideas?
EDIT: I can see the log says "E: Unable to find partition size for ' /sdcard'"
Click to expand...
Click to collapse
As soon as I'm getting a microsd card I'll try to fix that.
BTW: Internal sdcard is mounted at /emmc (TWRP default)

Thanks!! Installed without problems (v.0.1.1) and menu is working fine so far.
Haven't used it to install zips/roms yet though.
Sent from my LG-P880 using xda premium

i wont update this thread anymore, since a made something new. that combines cwm&twrp.
http://forum.xda-developers.com/showthread.php?t=2220302
next update will have alot of improvements and twrp 2.5.0.0 included

is it possible to restore a cwm backup from TWRP rec?I get FAIL CHECKING MD5 SUMS

no

@gordon0001, any news with your recovery?
@GRG13, your signature is terrible big and ugly and the link to your "How to enable developer options [...]" is wrong. :laugh:

Thanks a lot for TWRP recovery .. Happy time to have it .. Thumbs up

[RECOVERY] [NEW: CWM Graphics] CTR Recovery for Galaxy A5

CTR Recovery for Galaxy A5​
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.

Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.

Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work

oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support

you welcome brother

DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse

DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro

Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.

@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...

corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now

DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..

corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port

DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?

corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think

I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery

Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz

What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far

akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal

DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.

akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands

[Resurrection Remix] [Unofficial] [2018-08-19] Treble [Discontinued moved to PIE]

LAST PERSONALLY Verified as working and "stable"*: GAPPS, 8/19 GAPPS
First and foremost, I'm simply compiling this for the OnePlus 6 and am making some small tweaks to include Opengapps and not only Go Apps in the builds.
The parent for this by phhusson can be found at [Resurrection Remix] [Unofficial] [2018-05-19] Phh-Treble
Next the most important information where to get the most current build of the ROM: Google Drive
For now I suggest the version ending in -go such as: 'rr_6_1_180616_system-arm64-ab-go.img.xz' as the '-gapp' is in development, I expect a number of builds over the next few days as I finally the build scripts and then the rate to tapper off to every two weeks or as there are changes that seem to warrant it, I'm not building nightly for no reason, as RR 6.1 is reasonable stable at this time.
Note: Attached (build.sh) is the build script currently being used, it is a work in progress. and will be updated in case you more regular builds. You will need 12GB of Ram Ubuntu 16.04+ (I'm using 18.04 now, but I started with 16.04) and at least 360GB (SSD recommended) to build, and upto 6 hours for the initial run and then 2 for ever additional run.
Many thanks to phhusson for allowing me to post this based off of his work.
Changes, when I have something to report. Not all build will:
The 7/7 build includes a number of patches recommended by DocRambone.
Overlay support to force Apps fullscreen, Under Display->Advanced
Some cleanups to the UI for the round corners
Better LED support
The 7/8 build is the same as 7/7, but includes July security patches, I built it in order to match the official release.
The 7/24 build is again to match the official release
The 8/19 build is again to match the official release, note regression in status bar height I'm looking into.
Second post: will have details on what is working and not
Third Post: will have full instructions on installation, backup restore based on my experiences
* Stable is relative, for me if I consider it usable from day to day it is stable.

As of 8/11/2018
In the GAPPS version
Working:
Fingerprint
Camera (Front and Back) + Flash (Also got the OnePlus Camera working*)
Speaker
Wifi (Some cut outs seen, this is not unique to this ROM and is dependent on the access port some are worse than others, no clue why)
Bluetooth
GPS
Brightness
Slider for Notifications as of 6/18 build
Mobile Data/Voice (tested dual SIMM is working)
Google Apps
Root (using magisk 16.3), told but have not personally tested that 16.4 without changes works as well
Ambient (works serious effect on battery see next post)
Full Screen Aspect Ratio Display->Advanced 7/07/2018 build+
More fully functional LED Improved for at least mounting USB sticks in 7/7 build
USB Host - Fixed for at least mounting USB sticks in 7/24 build
Bluetooth Phone audio is on the local headset. - Fixed in 7/24 build
Seems working NFC working 5.1.11 Vendor and Boot, not working with previous to 5.1.9 Vendor and Boot I have nothing to connect to to fully test
Not Working:
The Notch hides content (need to wait for P)
Unknown:
Camera Quality: I do little with the camera and am no photographer, so I can say nothing about quality, only it installed and took pictures
VaSU# said:
volte kinda works you can receive messages and calls and can send messages but cant call "out"
Click to expand...
Click to collapse
Please let me know if anything is missing, or needs to be added

Instructions to flash, backup ...
WARNING: With 5.1.8 I had no WIFI, so I suggest sticking to 5.1.6 to 5.1.7 FOR THE MOMENT
Instructions to flash, backup ...
Total time required about 90 minutes
Pre-Reqs:
First and foremost:
Start with at least 5.1.6 (or greater, as of writing 5.1.7 was the lastest), there are Treble fixes in 5.1.6 we need.
Second
verify you have a good USB cable (the Red one shipped with the phone is best)
Three
download the oneplus drivers and abd
- USB Drivers: OnePlus 6 USB Drivers for Windows
- ADB/Fastboot: ADB/Fastboot latest mini
Install both to your local system
Four
Download the latest TWRP (get both the img and zip files)
TWRP for OnePlus 6
Five
Download the files(Treble OP6 Files 5.1.6) from:
GUIDE] How to flash Treble roms on OnePlus 6
Extract and keep: vbmeta.img (if you are on 5.1.X where is the boot version you can keep the boot.img as well, if not discard).
Six
Download the lastest Oxygen OS ZIP and bootloader from:
[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates
As of writing this is:
5.1.6 full image: OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
5.1.6 boot: OnePlus6Oxygen_22_OTA_010_all_1806070151_boot.img
Seven
Download Device ID:
Device+ID APK
Eight
Download Magisk for Treble:
Magisk modified for treble
Since as of 6/2018 the default magisk does not support Treble we need a special version I suggest: Magisk-v16.3-factory-faizauthar12-20180406.zip as teh latest I could find with support.
Nine
Recommended download fastboot installable 5.1.6 (or latest build):
[ROM][STOCK][FASTBOOT][OP6] Stock Fastboot ROMs for OnePlus 6
Ten
Include Overlay/Ambient Display.
Download APK at: [Overlay] Enable Night Light, Auto-Brightness, Ambient Display & more on Treble ROM
Eleven
OnePlus Camera:
OnePlus Camera APK's
Finally
Download RR 6.0 for Treble compiled after 7/08/2018:
Either download the gapps or go version (gapps is still a work in progress when I wrote this)
ROMs Google Drive
Getting Ready:
WARNING: you will loss all data on your phone, backup anything you want or need, first.
Make sure you can get to fastboot (enable "Advanced Reboot" in developers options and make sure that you can enter on a reboot by pressing volume-down and power at the same time)
Make sure you are on 5.1.6+ (5.1.6 was the latest firmware upon writing this)
Remove Any security you have set (just to be safe)
Reboot to fastboot (bootloader)
run:
Code:
fastboot oem unlock
"You will be greeted with a Unlock Bootloader Warning page, Hit the Vol button to select Yes and turn it Blue and Hit the Power Button to Execute the selection, allow your device to reboot"
Backup EFS
If you have not already I'd recommend backing up EFS (to do so you need to be rooted, or else use TWRP):
Preferred, if rooted simply open a terminal and run:
Code:
su
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=2048
dd if=/dev/block/sdf3 of=/sdcard/modemst2.bin bs=2048
Copy these files someplace safe!
If not rooted reboot to fastboot (bootloader):
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
select only EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Backup the Phone
Recommended if you care: Backup your entire phone using TWRP as well:
Ensure that the latest twrp is in the same directory as fastboot (C:\Program Files (x86)\Minimal ADB and Fastboot) and run (3.2.1 was the lastest as of writing this):
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select backup
Select Everything except EFS and Modem
enter a meaningful name
swipe to backup
click "Reboot System" -> "Do not Install" for TWRP if asked.
You can now locate the backup under /storage/TWRP/BACKUPS and move it to a safe location off the phone.
Installing RR:
Finally we are ready to install RR (or any other Treble ROM), on the OnePlus 6. You will need a build from 6/7/2018 or later to have the required Vender-Hal to be present.
You will need to locate and install the AB version for the OnePlus 6.
Note: I'm using RR from 6/13 as the base for the guide: system-arm64-ab-gapps.img
SEE FIRST POST FOR CURRENT DOWNLOAD LOCATION I compiled this using phhusson's (Orginial Build Scripts)
instructions and a bit of setup on Linux. However most Treble base ROM's should work so long as they are from after 6/7/2018 in a similar manor.
* Remember this will wipe your device and you will loss all data *
First
boot in to fastboot (bootloader):
We need to go back to TRWRP and wipe internal storage and data to be safe, as the -w option to do so when flashing is not working for me.
- fastboot.exe boot twrp-3.2.1-0-enchilada.img
This will boot the phone into twrp
Allow modification
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Swipe to Wipe
Click back until you are at the main menu
Click on Reboot
Click on Bootloader -> "Do not Install" for TWRP if asked.
Second
Flash the new ROM:
Flash vbmeta.img to remove validation
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
To be safe flash a default boot image (5.1.6 in this case)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Next reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->Thiscan not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot to fastboot
Now flash a the new ROM:
- fastboot flash system_a system-arm64-ab-gapps.img
- fastboot flash system_b system-arm64-ab-gapps.img
Three
reboot:
Code:
fastboot reboot
You will see the "andorid" boot screen (this is different that the Oxygen one) and being the first boot it could take a while. If you see no boot screen or it does not boot (give 10 minutes), then you likely need to repeat these steps again. If you boot into RR then continue.
You may get a Vender image mistake error ignore it it only appewars on boot.
Skip the Setup by clicking all four corners top left->top right->bottom right->bottom left (it my take more than one try), at this point you have no networking, that is what we want.
Suggestion make backup here as you have a working OS! -- Instructions to follow
Four
Move over required files: You now have RR installed and working:
Enable developer mode and then enable Advanced Reboot
Then copy over gapps-nano, Device+ ID.apk, magisk-manager apk and magisk installer zip to the phone
To get the magisk manager you need to extract it from the zip as I cloud not get the normal one to install. Extract the zip: Magisk-v16.3-factory-faizauthar12-20180406.zip copy common\magisk.apk to the phone
Five
Deal with: "Play Services not Certified by Google":
Install Device+ID (APK downloaed above) and Open
Once done open the second line shows the GSF ID for this device
Android Register GSF
Login using a gmail account (I suggest the one you use for the playstore)
Enter the GSF in the field, now we wait about 5 to 10 minutes for it to propigate
Reboot the phone as we want paly services to start fresh
First add a wIFI network.
Critical do not let any apps update until you have registered playstore, so if you see a notification saying downloading, select and click pause. Doing so with the updated 6/17 paystore resulted in a black screen where you would enter your password, no know work around other than reset if this happens.
click on playstore it should now start
Now login to your account and you should be go (it may take more than one attempt no idea why).
Now enable the update if previously paused
Update all Apps from the playstore before continuing, this may take a while give it 10 minutes
Optional: If you want remove Device+ID now (but I leave it as it is an easy way to get information).
You now have a working Playstore, if you have hung downloads then you may need to clear the cache for play services and the playstore I assume the unregistered might be the cause of them getting messed up.
Five
Install magisk:
Ensure you copied magisk zip and also the magisk manager apk to your phone, do not open, but click Done
Install the magisk manager, by locating the file in filemanager and selecting it.Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Install
Select the magisk zip from the filesystem and flash
clear cache
Reboot->System (If asked about installing TWRP swipe to install)
Allow the phone to fully boot
Suggested: Reboot the phone
Suggested: disable checks for updates as 5.7 does not work with this build.
Root is now setup.
Six
Installer th onPlus camera:
Many people want the one plus camera, copy the apk downloaed above to the phone.
Open and install via a file manager
Seven
resize Data (as it will be only 11GB), the partitioon will be larger, depending on your devide se we will use TWRP and resize2fs to grow it.
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Advanced->Terminal
Code:
resize2fs /dev/block/sda17
Reboot System
Eight
Recommended, make a backup of your hard work:
Reboot into fastbboot (bootloader) mode
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select backup
Select Everything except EFS and Modem (as I'm unsure exactly which you need)
enter a meaningful name
swipe to backup
click "Reboot System" -> Swipe to reboot
Once back in RR copy the backup off the phone
Eight
Start using your OnePlus 6 with RR 6.0, rooted and with GAPPS
Nine
Upgrading:
Upgrading is simply replacing the system partitions and only these paritions (tested going from 6/13->6/16->6/17 builds)
Boot into fastboot (advanced reboot options)
Now flash the new system files:
- fastboot flash system_a new_system-arm64-ab-gapps.img
- fastboot flash system_b new_system-arm64-ab-gapps.img
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot System
Ten
Restoring a Backup from TWRP
*This is a work in progress I can not work out how to do so safely*
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Select Restore
Select the backup
Select Everything (other than EFS and Modem!)
Got to the main menu
Select Wipe
Advanced Wipe
Select Cache (and only Cache)
Swipe to Wipe
Reboot Fastboot
Eleven
Night Light, Ambient Display, requires Root:
My suggestion is not to do this if you care abut battery as I've seen major drain (even with Ambient display disabled, testing this).
Copy the apk downloaded framework-res__auto_generated_rro.apk to /vendor/overlays
Code:
mount -o rw,remount -t ext4 /vendor
cp <location of file> /vendor/overlay
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
Reboot
Comments:
TWRP does not boot if flashed onto RR (the TWRP logo appears but it will not boot), this is currently only go to protect you from using the OnePlus Recovery and messing up RR. Flashing TWRP does not affect booting into RR.
TWRP DOES handle encryption without an issue, even a wrong first pin is not an issue
TWRP making a backup of Treble ROM, backup everything for now: Data, Boot, System, System Image, Vendor, Vendor Image.
If you have problems with hung downloads from the Playstore: Pending hung PlayStore
Wifi can be flaky (appearently this is a more general issue as even stock had some issues, I fixed them by only using either 2.4 or 5Mhz wireless, if I had both active I had constant disconnects.
Worst case, to recovery, back to Oxygen 5.1.6 if you end up in a boot loop stuck booting to rtecovery, etc:
- flash-all.bat
Reboot into recovery (you need to do this with volume down +Power, or selecting from bootload):
In stock recovery select English
Select Wipe Data and Cache
Reset system settings->yes->done
Wipe Cache->Yes->done
Erase everything->This can not be undone, continue->done
back
Advanced
Reboot to fastboot->Reboot
Load TWRP:
Code:
fastboot.exe boot twrp-3.2.1-0-enchilada.img
Copy the Oxygen full ROM back to the phone
Code:
adb push OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip /sdcard
In TWRP
Install
Select OnePlus6Oxygen_22_OTA_010_all_1806070151_ad8b19ed516e78.zip
Go back to the root and select Advanced Wipe
Select Wipe
Advanced Wipe
Select Cache, Data and "Internal Storage"
Click on Reboot->Recovery (select Do not Install)
English
Wipe Cach and Data
Wipe Everything
Reboot
The phone will reboot same as the day it was made
If it does not then please refer to:
Mega Unbrick Guide for A Hard Bricked OnePlus 6
Note: Always boot fully at least once (I suggest twice and the first one is configuring android) before trying any steps above again.
Best of Luck, see a typo let me know
ERIC

thank you for this

[emoji102][emoji102][emoji102][emoji102][emoji102]
Sent from my ONEPLUS A6003 using Tapatalk

Thank you for putting so much hard work on this. Really much appreciated, will give it a try.

Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?

saintxseiya said:
Might be a noob question, but due to treble, is the camera quality the same with the OnePlus app?
Click to expand...
Click to collapse
No.

Great rom, I especially like the fact that I can choose to install without gapps (prefer fdroid). One thing that is missing is ambient display, hopefully it will be fixed sooner or later.

Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Abaddon said:
No.
Click to expand...
Click to collapse
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
same quality here

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
Never said anything about results, only that it could be installed and works, (takes pictures), personally I do little with the camera and am not photographer, but it can be installed (link above) and installed.
Updated the working to remove any confusion.

Maibol said:
same quality here
Click to expand...
Click to collapse
Could you post some comparison pics? Including portrait shots.
Would be awesome.

saintxseiya said:
Could you post some comparison pics? Including portrait shots.
Would be awesome.
Click to expand...
Click to collapse
sorry bro celebrating today with the family too much beer .....

So seeing this not even a month after the release of the op6 makes me happy and hopeful that we get a fully working RR-OS for the OP6 in the near future !

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
because Oneplus doesnt release blobs for camera

Pat123 said:
Stock OOS Cam on RR. Isn't that huge news? Wow! :good:
Have you tried this yourself? Ignore the treble part of his comment, but why would stock cam on OOS vs stock cam on custom ROM give different results in terms of picture quality?
Click to expand...
Click to collapse
It will never be the same as OOS stock. Because aside from there is no device tree provided by OnePlus, they will never release the camera blobs due to licensing issues. Once we get a stable and proper gcam port. It'll be better than the stock OOS cam or close

is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore

unix2208 said:
is a beautiful Rom, will there be an adaptation for twrp? I have to use the gapps, because at the go version Wear OS does not work. and in the gapp version would be nice if the smartbar was running. Unfortunately, the kill app does not work ( I can not use xposed, then my bank app will not work anymore
Click to expand...
Click to collapse
TWRP not for now as treble is build as an image, but you should be able to flash using twrp just switch to img (though I have not tested that).
The GApps version is posted the 6/18 is working great, see second post.
As for Banking I'm unsure if any Treble based ROM passed the checks, as with or without root, as they appear as unsigned.
As for smartbar, I'll give it a try when I get a chance, as I do not use it personally.
ERIC

So safetynet won't pass?

[Recovery][Stock OOS]Oxygen OS Stock recovery with ADB enabled

While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.
Prerequisites:
Oneplus 8 Pro
unlocked bootloader
access to fastboot on the phone
adb and fastboot
Installation:
Reboot the phone to fastboot, then flash the recovery from fastboot with the command
Code:
fastboot flash recovery <filename>
(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)
Uninstall:
Same as installation, but flash the original stock recovery instead.
Usage:
Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using
Code:
adb shell
to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.
Step-by-step this would be:
Code:
cd /data/adb/modules
to change to the Magisk modules directory
Code:
ls
to list the content of this directory, each module has its own directory, usually with a well-recognizable name
Code:
rm -r <directory>
to delete the directory in question. Tip: in console TAB-autocomplete works
Downloads:
10.5.4 BA Recovery
Modified 10.5.4 BA recovery from GDrive
Original 10.5.4 BA recovery from Gdrive
10.5.5 BA Recovery
Modified 10.5.5 BA recovery from GDrive
Original 10.5.5 BA recovery from Gdrive
10.5.6 BA Recovery
Modified 10.5.6 BA recovery from GDrive
Original 10.5.6 BA recovery from Gdrive
Notes of caution:
ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.
with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing
Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.

Description of method to modify recovery by yourself:
Prerequisites:
Android Image Kitchen (credit to osm0sis for providing this tool)
the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file
Now do the following:
unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within
navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"
look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)
look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb
look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour
save textfile
repack the image with Android Image Kitchen and voila:
you have a new modified recovery image you can flash

Thanks for this...
On fastboot we have to flash the modified recovery img?
EDIT : Nevermind haven't read the whole OP

I have a noob question: this won't affect data or magisk right?

To remove a module , command should not be :
( rm -rf < directory> ) ?...

cultofluna said:
To remove a module , command should not be :
( rm -rf < directory> ) ?...
Click to expand...
Click to collapse
Thanks for your comment, but technically no
The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does
I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...
But again thanks, I do appreciate your help!

HottieLinus said:
I have a noob question: this won't affect data or magisk right?
Click to expand...
Click to collapse
Correct, the recovery resides in a separate partition and flashing it doesn't do anything anywhere else.
In fact the recovery looks and behaves the same when booting into it, the change only becomes apparent by being able to use adb in recovery.

@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...

cultofluna said:
@s3axel can we use this recovery to escape bootloop due to install unsupported theme or any issue from substratum?
Or maybe just flashing stock boot IMG on fastboot is enough...
Click to expand...
Click to collapse
It should be possible as the recovery gives you full access to your file system and so, given you know what to remove/change, it should also be possible to recover from issues as you mentioned.
My problem: I have no idea where themes or substratum additions are installed directory-location wise, will need to research a bit. Or maybe someone else can chime in on this, then I could update OP with info on that as well...

Ok one more question..
Can we flash zips through the recovery?...
Via ADB sideload?.. maybe..

cultofluna said:
..Can we flash zips through the recovery?...Via ADB sideload?..
Click to expand...
Click to collapse
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:

s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Ok...
Because on pixel4 XL you can reboot to stock recovery and choose the the option ADB sideload...
And from there you can flash a custom ROM...etc..

Updated OP with 10.5.5 recovery..

s3axel said:
Updated OP with 10.5.5 recovery..
Click to expand...
Click to collapse
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
s3axel said:
I don't know but I doubt it as to my knowledge ADB sideload is a special mode that needs to be activated e.g. in TWRP. So far I didn't have the need to use such a functionality and thus haven't tried it :angel:
Click to expand...
Click to collapse
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.

Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
---------- Post added at 08:50 PM ---------- Previous post was at 08:48 PM ----------
Is the OnePlus 8 pro system partition dynamic? Meaning it'll be an absolute nightmare to ever get TWRP like the OP 7T series? I really hope not, flashing through ADB for everything sucks.
Click to expand...
Click to collapse
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...

cultofluna said:
Yep..
Definitely dynamic partitions...
Don't expecting a fully working twrp...
You can find a chinese twrp that boots and decrypt..
But sources are unknown...
Click to expand...
Click to collapse
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?

Burt Squirtz said:
do you have a link to that Chinese TWRP by chance? And how would I initially flash it, adb? Or Could I probably go through magisk manager?
Click to expand...
Click to collapse
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents

pyry666 said:
That Chinese TWRP violates glp so it cannot be shared here on xda..And if were you I woulnd be using that anyway..Just my two cents
Click to expand...
Click to collapse
What an incredibly helpful response. Sorry but if there's something that'll decrypt and allow me to backup and recover, of course I'm going to try and find it. And I suspect most other people here would too.

Burt Squirtz said:
That recovery looks like it's for BA. Does that recovery work on AA as well?
Click to expand...
Click to collapse
I don't know presently, usually I compare recoveries or I (or other users) add recoveries for other regions which they made by themselves. When recoveries are the same of course they can be used
RIght now I cannot download the 10.5.5 AA firmware (download aborts after some time), I'll add the recovery once this is working... EDIT: seems OP pulled the downloads, so no luck at the moment...

If there is a working twrp in China then perhaps it's worth making contact with them to see if either:
A) they can let you have it
B) they can help you fix this one?
It's presume the former would make the most sense, with permission I see no problem in obtaining it or linking it, certainly not taking about it. Makes no sense to just avoid an obvious assist whilst we all struggle without twrp.