Database Develop

[Guide]OnePlus 6T Rooted!

Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted earopean OP6T consumer ever.
If you need any help ask me on my telegram group: https://t.me/xOP6T
{
"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"
}

..

mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Can i ask you a little help to make a dedicated and better twrp?

mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.[/QUOTE
Is it possible..
After boot the twrp> flash twrp zip> boot on twrp> flash magisk> boot to OOS..?
Click to expand...
Click to collapse

you can also ROOT OP6T with the magiskmanager to patch the boot.img

Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now

Can confirm, this works on my 6T also.

Striatum_bdr said:
Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now
Click to expand...
Click to collapse
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced

What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?

Striatum_bdr said:
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced
Click to expand...
Click to collapse
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?

iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
You need to keep stock recovery to be able to use OTA, To use TWRP you'll have to download the whole oos ROM, flash it and then you need to reflash TWRP and magisk as there is no separate recovery partition on op6 /6t
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Because it's temporary you have to use sideload, as TWRP is present only in ram, and it seems that the op6 version have difficulties to decrypt op6t data partition if I understood correctly. And because I didn't want to flash for good TWRP on the phone to keep stock recovery.

cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Well when we boot the op6 twrp on our op6t's it doesnt ask to decrypt, so everything is in jibberish.

iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
When you get an OTA update it will download the full rom so it will be around 1,5gb. Just install it when you recieve it, and after that do the steps again to get root again.

mingo_mgx said:
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Doubt it.

feimummy said:
you can also ROOT OP6T with the magiskmanager to patch the boot.img
Click to expand...
Click to collapse
can u please elaborate sir ??

freakzapster said:
can u please elaborate sir ??
Click to expand...
Click to collapse
It's not very easy as you need to extract boot.img from the full oos zip(or extract it from your phone with fastboot), patch the boot img, then fastboot flash it back. Far more simple to to it as explained. And you need a computer anyway.
And with the new slot A/B architecture you need anyway a computer each time you flash a ROM, as you need to reinstall TWRP each time, due to the lack of recovery partition here (it's been 'replaced' by vendor partition necessary for Treble compatibility) .

@mingo_mgx: I have done a post here
Thanks for sharing the info :good:

ABotelho23 said:
Doubt it.
Click to expand...
Click to collapse
Yes he is, he was one of the few getting a Oneplus 6T on the 31st of October, and if there's no Guide to root yet, most of the users won't bother with unlocking BL

I had rooted my 6T and was installing midnight core magisk module. After flashing it in magisk i rebooted the phone and now im stuck in bootloop. I tried sideloading Magisk Uninstaller, But it gives me some error. Tried sideloading magisk, but still stuck in bootloop. Any suggestions?

TWRP[UNOFFICAL]-BETA-BUILD-[12-03-2019]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
Main Highlights
✪ MTP support
✪ Can flash stock os Images
✪ Backup/restore works with any os
✪ Restore your old twrp backup
✪ Optimized and faster
✪ Build On A29 Pre Built Kernel By Realme
✪ Full compatible with color os
ScreenShots
Download Link:
https://mega.nz/#!5gYnjQSB!YhC_ZTHuopwwP50LxTvJ1VOq4zYSfG0LAudWr6gatUA
Code:
Bugs
:GSI Flashing Has Some Issues
:If You Finds Any Other Bug Then Report Me
Credits;
AnuragRai(Developer)
Hamza(Tester)
RK(Tester)
Jatin(Tester)
MKS(RM2p Dev,Always Supported Me)
And Whole Realme Tester Team
XDA:DevDB Information
TWRP[UNOFFICAL]-BETA-BUILD-[12-03-2019], Tool/Utility for the Oppo Realme 1
Contributors
anurag rai, hamza
Version Information
Status: Beta
Current Beta Version: 01
Beta Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12

Flashing Guide
Code:
[CENTER]
:adb reboot bootloader
:fastboot flash recovery recoveryname.img
:reboot phone manually ,not from fastboot
:After phone boots up,power off it
:Press Power Button+Volume UP &Down For Approx 20 seconds
:After You Are Inside Of Twrp,do this
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot

Reserved

Thankyou bro..

Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate

anabhi said:
Finally we are getting working twrp recovery for rm 1:highfive: keep up the good work mate
Click to expand...
Click to collapse
Bro can you help me with fixing reboot to recovery issue

anurag rai said:
Flashing Guide
Code:
[CENTER]
:Wipe-Format Data-Yes And reboot manually by power off the device
:And Press Power Button+Volume UP & Down
:Flash Magisk And Reboot [/CENTER]
Caution
Code:
:Never Reboot directly to recovery by adb or fastboot commands as it will cause soft brick,
:always manually reboot
Click to expand...
Click to collapse
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.

It's Working ! Thanks Alot Mate.:victory:

awesome work bro.. thnks a lot u r too fast..

Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /

Awesome man!??

svsexodia said:
Why wiping data ? Also if we wipe data then won't it take time to setup the device after that only we could reboot. And I just need to put some some apps into system, I dont want to flash magisk. Can I just boot into recovery once using fastboot boot twrp.img command /
Click to expand...
Click to collapse
Yes you can

manavkush said:
Flashing Guide
Caution
After wiping data and turning off. My phone wont boot. I doesnt even show the logo. Please help.
Click to expand...
Click to collapse
Charge it bro

Realme 1 - Treble Rom
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'

johndoe5 said:
'TREBLE', let's talk about it.
Realme 1 supports treble, we have unlocked bootloader, a working TWRP, and several Treble Roms available, so why haven't anyone tried flashing a Treble Rom yet on Realme 1? Those are the only things we need to flash a Treble Rom on this device right? Am I missing something?
I don't have a backup phone nor do we have official firmware for Realme 1 to recover from soft brick, so I am not willing to risk my device yet. If someone else could do it instead I would appreciate it a lot.
P.S. Someone should start a pinned thread for 'Realme 1 - Treble Roms'
Click to expand...
Click to collapse
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:

It's_Shawn said:
I've Flashed Phh's GSI Treble Roms.All Of Em Seems To Work Fine But Volte Is Not Working On Any Of Em So I Had To Switch Back To Stock. I Tested AOSP 9.0,RR 9.0 And Lineage 8.1:silly:
Click to expand...
Click to collapse
Which TWRP did you use?
And where can I find the stock firmware?

johndoe5 said:
Which TWRP did you use?
And where can I find the stock firmware?
Click to expand...
Click to collapse
That Time I Didn't Use Any Recovery,I Used Fastboot Commands

Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.

5s4rnv33r said:
Hey I successfully installed TWRP recovery but I didn't flash magisk yet. But even now there is a message in status bar saying "Rooting of your phone has been detected. Tap to fix" and that screen is showing me to install 2.1GB OTA update. Idk what is happening I never faced such thing in any of my earlier phone while twrp flashing . What is this ? Can I install the update ? And why is it showing. Will there be possible bootloops if I install the update or willI I still be having TWRP or stock recovery get flashed. Please answer so i can proceed with my choice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.

vikas2316 said:
https://forum.xda-developers.com/re...l-method-root-realme-1-install-t3908030/page3
try the solution written in soham028 's post.
it worked for me and updating os will remove root.
Click to expand...
Click to collapse
Updating OS will remove root but will it also remove TWRP ???
One more question I followed all the steps correctly (including wiping data) but from TWRP I can't mount DATA.
---------- Post added at 10:01 PM ---------- Previous post was at 09:13 PM ----------
After wiping data if I just reboot to TWRP recovery then I can mount the DATA but once I have started the phone and set it up then again I boot into TWRP recovery and when I try to mount DATA I am not able to do so. Can't mount /data invalid argument. Please suggest something.

[Q][BONITO] Descendant X - android ver. 10r32

{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct ​
Android OS version: 10.0.0_r32
Security patch level: March​
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11

Cool cool some more love coming in

Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.

crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.

johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning

crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:

johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.

crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.

stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/

What version do I have to download for a 3a xl device ?

Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?

Hasn't been updated in like 2 months if I am reading it right

Question Recovery A/B

Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?

Devione said:
Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?
Click to expand...
Click to collapse
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.

HyperCriSiS said:
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.
Click to expand...
Click to collapse
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot

Devione said:
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot
Click to expand...
Click to collapse
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).

Freak07 said:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).
Click to expand...
Click to collapse
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?

Devione said:
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I don't know, but I guess if LOS supplied in form of payload.bin instead of many .img files then I think it's better to unpack all img's from there replace recovery and patched boot and "repack" it back if it's possible. At least that was the way I did that on Samsung phones. But there was only .tar archives, so that was much easier than .bin to repach which I think you will need some additional software.

Devione said:
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I'm not sure about the current situation on unofficial lineage. I'm also not using it on my zf8 but from others phones, which should apply to zf8 as well.
I'm pretty sure official lineage builds have an inbuilt OTA mechanism. Unsure about the unofficial one. Better ask in the lineage thread.
However, you can boot to lineage recovery and flash the lineage.zip from there without wiping the device if you were previously on lineage and are just updating.
If you want to be rooted you need to patch the boot.img from this update (extract from payload.bin if not already available) and flash it via fastboot after updating.
By telling you to extract payload.bin I just wanted to visualize what's being updated during flashing a firmware.zip so you have a better idea how it works.

Hi there, thanks for the replies.
Sorry I wasn't being clear. By firmware updates I meant the official Asus firmware updates which are zips containing payload.bin.
What I really meant to ask was the possibility of updating the Asus firmware when still running a non Asus ROM eg LineageOS.
Earlier on I've tried to reflash TWRP over the existing LineageOS recovery and it didn't seem to work so not sure what I did wrong there. Device still boots to LineageOS and running Lineage Recovery on "B".
Thanks guys for your time and replies.
Edit - the goal at the end of the day I guess is to
1. run a custom ROM (LineageOS, GSI, Omni etc.)
2. run TWRP
3. able to update Asus firmware when available

hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
{
"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"
}

[email protected] said:
hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
View attachment 5478501
Click to expand...
Click to collapse

[ROM][PixelExperience 12.1][A70][FN]

{
"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"
}
View info: https://www.xda-developers.com/pixel-experience-12-hands-on/
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Your warranty is now void!
>I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
>You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
What is working?
-Everything is working (also fingerprint; bluethooth; 1 sim/maybe 2)
-File's Download-
>Vendor: https://forum.xda-developers.com/attachments/vendor_a11-zip.5336611/
>Rom: https://github.com/zainullahk/universal-pixelexperience-samsung/releases
make sure to download the arm64-ab-12.0 and not the arm64-ab-vndklite.
!Optional!
>Kernel: https://opensource.samsung.com/uploadSearch?searchValue=A70.
>Magisk: https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip
-Installation guide-
>Enter recovery (TWPR).
>Press "Wipe"-->"Format Data" -type "yes".
>On PC Extract the rom.
>And copy "Vendor_A11.zip";"PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img";"app-debug.zip" to the external/internal sd storage.
>First install the vendor follow steps below:
>"Wipe"-->"Advanced Wipe"-->Select Dalvik; Cache; System and Vendor -->"Swipe to Wipe".
>Now click on "Install" then select "Vendor_A11.zip".
>Then go back and flash the rom as "System Image".
--------------------
>!Optional!
>Flash magisk (debug.zip) !DON'T DO OTA UPDATES FOR NOW IF YOU USE MAGISK!
--------------------
>Reboot System and it should work for samsung a70.
(I did't created the rom; vendor; magisk i just have found a way to install the rom onto a galaxy A70).
-Pixel Experience 12 v402-
>New update to pe!
>Check the Updater page on Treble App to OTA update.
>Sync with February sources of PE (give a warm welcome to Face Unlock).
>Sync with AOSP 12.0 v402 by @phhusson.
>Fix permissions on dynamic su binary.
-OFFICIAL SITE-
Home - Pixel Experience
Home - Pixel Experience
download.pixelexperience.org
-COMMENT BELOW FOR ANY ISSUE-

USE THE STOCK KERNEL TO BE SURE THAT THE ROM WORKS!

Is volte working with this rom?

MarvinMod said:
Is volte working with this rom?
Click to expand...
Click to collapse
Yes sure the LTE connection is working!

Topo's said:
Yes sure the LTE connection is working!
Click to expand...
Click to collapse
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
I had read "LTE" and not "VoLTE"

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
thanks! you are right

Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.

Dakshxda said:
Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.
Click to expand...
Click to collapse
@Dakshxda remember to have the stock vendor of your device!
Follow my updated guide:https://forum.xda-developers.com/t/rom-gsi-100-working-a70-no-bootloop.4470471/
this 100% work
​

"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+

Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop

removez said:
Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop
Click to expand...
Click to collapse
You dont need to change the build.prop..
Why would you need to?

Ive been very busy with work, building a house. I may jave time this evening to flash and confirm Volte working or not.

Can install on a70f?

I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?

MarvinMod said:
You dont need to change the build.prop..
Why would you need to?
Click to expand...
Click to collapse
The Samsung Wear program refuses to work with this firmware. I could change the name of the device and it would work

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
I installed it once crookedly and did not start up was a bootloop. Then I flashed the stock firmware and then this one and it started. But magisk worked crookedly, the /system_root partition was not mounted

So here's what I did:
1. Flash stock via Odin
2. Reboot and then power off, then go to download
3. Flash TWRP 3.6.2
4. Reboot to recovery
5. Follow instructions above
6. Got Vbmeta error so I flashed VBMeta.tar from here
7. Rebooted but now it bootloops
Topo's said:
"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+
Click to expand...
Click to collapse

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
1)I have wrote the post and i didn't copied.
2)I have tried this and worked whit my 2 devices (Galaxy a70FN;A70MN)
3)It is a generic system image

Moderator Info,
Thread has been closed at OP's request. @Topo's if you decide to progress further with the ROM, please report the first post and request to have it opened. We will be able to open it for you.
Thanks,
Stephen