Related
Hey guys! So, as You know, OP6 has Treble, but when You flash GSI's on it, it will take You to EDL mode instead. Why? Well.. because of A/B and VBMETA partition. So... how do we fix it? It's actually pretty simple! Follow the guide and You will be able to boot GSI roms on Your OP6
Note: Before You can flash any GSI, You have to unlock Your bootloader. To do that, simply type: fastboot oem unlock . Just remember that it will wipe Your data!
Important: Flash 5.1.6 or above before flashing v20. It looks like 5.1.6 fixed Treble problems. Files have been updated to: 5.1.7
Step 1: Download any GSI rom You want, in this guide I'll be using Phh Treble latest build: Phh Treble A/B v20 with GApps and SU
(Make sure to extract it before flashing. You can do that with 7zip)
Step 2: Download this zip. It contains stock VBMETA as well as stock boot image, just in case if Your device is rooted. Link: Treble OP6 Files 5.1.7
Step 3: Extract those files on Your desktop for example and open terminal/cmd in the same folder as Your files. (Before You can do that, You should download latest minimal ADB and Fastboot available here: ADB & Fastboot XDA Thread Link ) Now. Copy and paste those commands:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
This command will let You boot non OOS roms, like Phh Treble or any other Treble GSI.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Those commands will flash stock non rooted boot image to both of Your boot partitions (Treble roms need slightly different root that's why we need to use stock boot image for now)
fastboot flash system_a system-arm64-ab-gapps-su.img
fastboot -w flash system_b system-arm64-ab-gapps-su.img
Okay, these commands will flash Phh GSI to both of Your partitions. The only difference is that second command will wipe Your data partition which is most likely required to have a bug free boot. So backup Your data before!
Aaand that's it! :victory: Enjoy Your new GSI rom.
Thanks to Dewang Rocker for making a tutorial video! Make sure to like and subscribe
And one more Thanks to @AxM2 for posting my guide on Github!
OnePlus 6 Treble Github Page
Q/A
Q: Does this method work for all GSI images?
Yes! It should work fine, as long as Your GSI supports A/B partitioning. Most Devs build A/B GSIs so no worries.
Q: Bugs?
Build v20:
Stock camera has problems with focus, but if You install OOS camera it works fine.
Notch is covering screen a little.
Q: I want to see some screenshots!
Credits:
Phhusson for Wonderful GSI!
FunkWizard for latest firmware!
@dylanneve1 for being an awesome friend and helping me with many of my projects.
OnePlus for OP6 and releasing updates that are actually useful!
James Muir for Pixel 2 Guide on Github.
Google for creating Treble for us.
Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).
any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?
Joyarup said:
Looks promising! Anyone tried and confirm that the roms boot?
And what does wiping of data partition means? Will that wipe the internal storage too? or just the "data" (The apps and stuff).
Click to expand...
Click to collapse
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .
ProtoDeVNan0 said:
It does boot, tried the guide 3 times already just to make sure that it works. And -w will wipe Your internal storage, not just apps. So make sure to backup everything. Or You can just wipe data in TWRP and then boot GSI. This way Your internal storage won't be deleted. But a full backup is always recommended! Even if You flash new fonts or something .
Click to expand...
Click to collapse
Alright thank you for clearing things, I will give it a try and will let you know!
Thank you for your work.
I get unknown option when running the fastboot --disable-verity command
eminem5055 said:
I get unknown option when running the fastboot --disable-verity command
Click to expand...
Click to collapse
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.
Joyarup said:
Make sure the drivers and adb and fastboot is installed and your command line is in the exact location as your fastboot.
Click to expand...
Click to collapse
That worked thanks!
Abaddon said:
any idea what treble rom/s that has the feature of stretching third party apps to use 18:9/19:9 aspect ratio or whatever instead of it being cropped?
Click to expand...
Click to collapse
No idea if any rom has settings for 18:9/19:9 displays. But there's also the notch that covers the screen. In OOS we can hide the notch, but in Treble roms the notch will cover some parts of the screen in all apps. YouTube should support 18:9/19:9 though. Maybe there is some app that can help with the notch? Or some Magisk module? I think that GravityBox should allow us to resize status bar so that apps won't be covered, but games hide the status bar so it will be useless in games. We might have to wait for Android P to take care of all the notch problems in GSIs.
Thank you for this!!
How is the camera on treble roms?
I think we need to wait P for notch support, or maybe some modders can do something
Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!
I don't think calling works yet, I am getting a soft reboot every time I try.
azsl1326 said:
Thanks for this guide. Looking forward to trying it out. With that said, just so I have my bases covered - What's the best way return to stock OOS if necessary?
Thanks!
Click to expand...
Click to collapse
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
sis3970 said:
I got mine back to stock by following this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
Thanks. Did you try this Treble version?
azsl1326 said:
Thanks. Did you try this Treble version?
Click to expand...
Click to collapse
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
sis3970 said:
No. Not yet. Planning to tonight.
Verstuurd vanaf mijn ONEPLUS A6003 met Tapatalk
Click to expand...
Click to collapse
Same for me. Also found this forum on XDA for Treble development - https://forum.xda-developers.com/project-treble/trebleenabled-device-development
No boot for me and phhusson, this guide does nothing different then what is mentioned already here as not working > https://forum.xda-developers.com/oneplus-6/help/dev-oneplus-6-luck-treble-seeking-help-t3795202
Tested on a total of 3 devices, no boot on neither, tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Until then I would put a big EXPERIMENTAL and DANGEROUS on this thread.
Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.
MishaalRahman said:
Can confirm this works, our display tester Dylan Raga got the LineageOS GSI booting.
Click to expand...
Click to collapse
Exelios said:
tho Mishaal just told me he got a boot, so it most be something else somewhere we have not yet identified.
Click to expand...
Click to collapse
If phh cannot get a boot on his own rom...
So after 2 weeks of debugging and trying to figure out why Treble GSI were not booting, then booting only for some users the final answer has been found.
This bootloader is way too stateful.
So if you try directly with proper vbmeta & system.img, you won't notice anything, it will just work, that's why some people say it works.
If you try system first without doing vbmeta, then it will mark the slot as not bootable. Flashing vbmeta afterwards will NOT mark it as bootable.
it also requires the latest fastboot with --disable-verity and --disable-verification, don't know why yet exactly.
Now if you bootloop to mark it as bootable again, you need to flash the boot partition of the slot.
Even worse than that "fastboot boot" works only if current slot is not marked as not bootable, so any try to launch TWRP fails once your in this mode.
This same issue also applies to users trying to restore to stock sometimes.
This means that the One Plus 6 will require proper documentation on how to do things, and people will have to stick to it, see official instructions in post 2.
Now that we know what the exact cause is, and how to deal with it, let the development begin.
PS
Doesn't seem to be OP fault, just stock Qualcomm bootloader.
Credits to Phhusson and me for making this possible, providing phh a device, documenting the findings and all.
WARNING This is still ALPHA
OFFICIAL INSTRUCTIONS
Correct installation procedure of a GSI on the One Plus 6, determined together with @phhusson
Make sure you unlocked the bootloader and that you have the absolute latest ADB and Fastboot from Google, none of the minimal packages we know of will work!
Then in fastboot flash the following, WITHOUT rebooting in between! this needs to be done all in one go!
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Use the STOCK boot image!
Then flash the GSI system image of your choice
Code:
fastboot flash system_a system.img
fastboot flash system_b system.img
Then flash STOCK vbmeta image with the specific commands!
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
then just fastboot reboot or select start on the phone.
---------------------------------------------------------------------------------------------------------------------------------------------------
If the above fails and you get a bootloop you will have to repeat all the steps above.
---------------------------------------------------------------------------------------------------------------------------------------------------
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
@Exelios
Thank you for sharing.
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Great work man,
I had held off trying as I didn't know if it would work for me or not. Looking forward to trying this out!!!
Sent from my OnePlus6 using XDA Labs
joemossjr said:
So if its marking it as unbootable can't you fastboot --set-active=other to get back to a bootable state?
Click to expand...
Click to collapse
Yeah you can do that once, but to get your first slot back you will need to re flash boot also at some point.
And remember once you flash boot you need to root and TWRP again.
Sent from my OnePlus 6 using XDA Labs
CertifiedBlyndGuy said:
Thread moved. Since this appears to be documentation rather than a physical product, this is the proper subforum.
Thank you!
-RJ
Click to expand...
Click to collapse
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
Give it a day, phh is trying to implement fixes to the findings in a more elegant and easier way for the end user, this thread was more intended to share our findings with other devs.
DocRambone said:
Any more details of what you found?, i tried numerous bootloader verity combos, only system.img that boots is aosp v18.
Click to expand...
Click to collapse
I've booted multiple roms comsic aosp aosip they boot just gotta get it right the first time
Exelios said:
An actual piece of software will be added by the end of the day.
Sent from my OnePlus 6 using XDA Labs
Click to expand...
Click to collapse
Ok. Just PM me and I'll move the thread when it happens
Still investigating, there is probably still something to this I'm missing
Exelios said:
Still investigating, there is probably still something to this I'm missing
Click to expand...
Click to collapse
What is the findings so far?
DocRambone said:
What is the findings so far?
Click to expand...
Click to collapse
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Exelios said:
Other then what's in the OP there seems to be also something else causing issues, not sure yet what exactly it is
Nope, phh just gave me the wrong vbmeta.img, one needs to use stock vbmeta not a modified one omg
I feel like an idiot now
But LOS still doesn't boot, something regarding sensors, stuck on boot logo.
Click to expand...
Click to collapse
I couldn't get v19 of phh's AOSP to boot for the longest time until I tried this! Thanks man!! :good:
I have cleaned up the OP and added clear instructions in post 2.
Tho LOS still doesn't boot for now, but that's because of a bug specific to the GSI, not a bootloader issue.
Delete
CertifiedBlyndGuy said:
Ok. Just PM me and I'll move the thread when it happens
Click to expand...
Click to collapse
Might I ask to make this a sticky?
Because every developer needs to be aware of it, this doesn't affect just GSI, one can run in the same issue even if flashing TWRP or restoring to stock or anything.
And every user should know about the official way to do things on the One Plus 6, which is slightly different then all other phones.
Thanks
The instructions in post 2 is the same as in the treble thread, still no boot other than aosp v18
lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!
it boots up with TWRP, but flashing Gapps was failure.
UPDATE: I used Open Gapps, better try Ground Zero GZR Gapps...
TASON42 said:
it boots up with TWRP, but flashing Gapps was failure.
Click to expand...
Click to collapse
GZR apps 180313 works good.
GZR-GaPPs-arm64REv4-Zero-8.1-20180628 worked. thx.
UPDATE: HuRUpdater_0.4, Magisk 16.7 worked.
Flashed a kernel, magisk and xposed with this. Seems to be working great.
olishadyx said:
Flashed a kernel, magisk and xposed with this. Seems to be working great.
Click to expand...
Click to collapse
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
ambitiousButRubbish said:
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
Click to expand...
Click to collapse
Proto8 is what I installed. Haven't made my mind up on it yet. Battery drain is definitely worse so far but apparently it takes a few cycles to adapt.
Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it
Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also
bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?
maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot
nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.
I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/
maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)
This version of twrp does not support backup and restore.
Install to both slots.
Fastboot flash --slot all boot twrp.img
Steps to install custom roms and root with Magisk.
Put magisk.zip, rom and twrp.img on your internal storage.
Reboot to twrp recovery.
Factory reset.
Install, select ROM zip and swipe to flash.
It will install to opposite slot, no need to reboot to install gapps if necessary. Install ROM and gapps if necessary. Then reinstall twrp image. Click install, install image. Select twrp image. Choose, boot and install to both slots and swipe to flash. The purpose of this last step is because after flashing ROM, twrp is overwritten by custom recovery. This will ensure twrp is kept.
Boot phone to system once then reboot to recovery and install magisk.zip file. Then reboot to system. Setup phone and click on magisk app. It will download full magisk app and you will be rooted. No more patching magisk file for root or adb side loading Roms. This is not my work. I'm just sharing.
Hi,
Just curious, what is the difference between your above version as opposed to this previous version (which does support backup/restore)?
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
JohnC said:
Hi,
Just curious, what is the difference between your above version as opposed to this previous version (which does support backup/restore)?
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
Click to expand...
Click to collapse
The difference is that you don't need a custom kernel with this version and this version is installed permanently as boot instead of ramdisk.
Even though you can install the other TWRP permanently, I do like the feature of yours of not having to use a custom kernel, but I need back/restore ability, so I guess I have to stick with what I have.
Hi,
Does this twrp allows the installation of other GSI images as well? Does the rom's build number have to do with anything if you want to root with this twrp? Can this twrp be overwritten/reverted or changed back to the stock recovery when flashed stock google images if anything goes wrong? Does installing a custom kernel after installing this twrp break anything?
Sorry for the sheer amount of questions as i'm still quite new to this kind of stuff for this phone specifically.
Yes
kiritoxd said:
Hi,
Does this twrp allows the installation of other GSI images as well? Does the rom's build number have to do with anything if you want to root with this twrp? Can this twrp be overwritten/reverted or changed back to the stock recovery when flashed stock google images if anything goes wrong? Does installing a custom kernel after installing this twrp break anything?
Sorry for the sheer amount of questions as i'm still quite new to this kind of stuff for this phone specifically.
Click to expand...
Click to collapse
Yes, you can install other images. You can root with this, build # doesn't matter. Twrp will be overwritten if you flash stock images or even other custom Roms. You would have to flash twrp to both slots again after flashing. I haven't tried custom kernel's so I couldn't help you with that.
TheSayaMan said:
Yes
Yes, you can install other images. You can root with this, build # doesn't matter. Twrp will be overwritten if you flash stock images or even other custom Roms. You would have to flash twrp to both slots again after flashing. I haven't tried custom kernel's so I couldn't help you with that.
Click to expand...
Click to collapse
Hi,
Thanks for replying to my previous questions. I have tried to flash a GSI but was unsuccessful. There was no errors in TWRP when flashing the GSI image but it just wont boot. It will be redirected back to the bootloader with the error "no valid slot to boot" after flashing.
I had this issue previously when installing GSI images even through the normal fastboot but it won't boot modded boot images, the stock ones work. Is there something that i'm doing wrong here?
kiritoxd said:
Hi,
Thanks for replying to my previous questions. I have tried to flash a GSI but was unsuccessful. There was no errors in TWRP when flashing the GSI image but it just wont boot. It will be redirected back to the bootloader with the error "no valid slot to boot" after flashing.
I had this issue previously when installing GSI images even through the normal fastboot but it won't boot modded boot images, the stock ones work. Is there something that i'm doing wrong here?
Click to expand...
Click to collapse
actually now that i think of it, I dont think its an issue with TWRP. I think is just that the Google Pixel 4A does not allow GSI installation. XD
TheSayaMan said:
This is not my work. I'm just sharing.
Click to expand...
Click to collapse
@TheSayaMan As you stated yourself that this is not your work, your thread has been moved out of the development section, for which it didn't qualify, but the thread has also been closed. Please thoroughly review the XDA Forum Rules and the following rules for posting in development:
**Rules for posting in development**
Only the following topics are allowed in DEVELOPMENT area: [DEV] - Development for any special projects or Apps [ROM] - Custom ROMs [KERNEL] - Custom Kernels [MOD] - Hack & Modifications for the phone with code only, zips go in...
forum.xda-developers.com
I've additionally removed your attachments. Recoveries like TWRP are released under GPLv3 i.e. if you publish a TWRP on XDA it has to be accompanied by a link to its source. Further information about XDA's policy regarding GPL and how we enforce it is available here:
[Mandatory] XDA-Developers and the GPL
XDA-DEVELOPERS AND THE GPL Hello Everyone, As many of you know, here at XDA we have a strict policy regarding GPL v2. What you may not understand is what that means and what effects it may have on you. Simply put "The GNU GPL is a software...
forum.xda-developers.com
When you review the XDA Forum Rules as seriously suggested by me above, please focus on rule no. 12 about sharing and giving credits when credits are due. This means you not only failed to provide a link to the source of this TWRP but also to give credits to its developer.
And if you choose to provide downloads for Magisk you MUST give credits to our Senior Recognised Developer @topjohnwu as the developer of Magisk and for the download to simply link to his Github account (https://github.com/topjohnwu/Magisk/releases/tag/v23.0) instead of attaching whatever...
Please do not hesitate to contact me in case of further questions. Thanks for your cooperation!
Respectfully
Oswald Boelcke
Senior Moderator