Database Develop

[OFFICIAL] TeamWin Recovery Project 3.3.1 For Zuk Z2 Pro

{
"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"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for ZUK Z2 Pro (z2_row).
This is an official recovery support thread.
Known Issues
MTP broken in 3.3.0 and newer builds because of a TWRP issue with 4.4 kernel (you can still use adb push and adb sideload)
Requirements
Unlocked bootloader
Common sense and a Z2 Pro
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial z2_plus TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
cosmedd for his work on the TWRP tree for z2_row
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.

gg

*Insert some random thx sentence*

I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?

robert_b said:
I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?
Click to expand...
Click to collapse
As first because this has the factory mounted as vendor support instead of factory renamed as vendor. If you're already using a build with this support and you downloaded it recently it means that the build is the exact same as this one. I created a thread so that things can get out of Telegram only and also because soon it'll become official (the old one is deprecated pretty much)

Thread updated with the official tag and a new official build on the TWRP.me website. Enjoy

Encryption with latest AEX is not working.

rower19 said:
Encryption with latest AEX is not working.
Click to expand...
Click to collapse
What do you mean with "is not working"? What happens when you try to encrypt?

DD3Boh said:
What do you mean with "is not working"? What happens when you try to encrypt?
Click to expand...
Click to collapse
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Hi, sorry for the late answer. Can you pm me on telegram so that we can discuss the issue and I can eventually send you some builds to test? t.me/DD3boh
Thank you!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Checked with @DD3Boh and decryption for pie is working in a test build. He gonna push the new version after some more testing.
But be patient, we will be finally able to encrypt our device and decrypt it in twrp.
Thanks to him,
G0r3t3x

TWRP 3.3.0 just got released
Encryption was fixed, although mtp is broken because of 4.4 kernel (which is a must for encryption)
Instead of mtp you can just use adb push to push files to the internal memory, or either adb sideload <package path> to flash them directly without transferring to the internal storage (works only after having enabled adb sideload in the advanced TWRP tab)
Download link in the first post

Hi, thanks for your work.
I've tried to reinstall baseband but log says it's not installing nothing. Using twrp 3.3.0, i'm on ArrowOS.

A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery

DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Perfectooo :good:
..btw: what about MTP? ..it works now?

satmaster said:
Perfectooo :good:
..btw: what about MTP? ..it works now?
Click to expand...
Click to collapse
It doesn't work on official builds for some reasons, so I had to disable it
I could though make a build locally where for some reasons it should work fine

I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.

lunloon said:
I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.
Click to expand...
Click to collapse
I tried USB-OTG and it worked. Thankfully.
Can't make any sense out of the driver game.

Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.

Dolour said:
Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.
Click to expand...
Click to collapse
Probably you don't know why I even switched to 4.4 kernel, which is because 3.18 kernel in TWRP breaks decryption, which is quite an important thing.
Anyway I can build TWRP locally and send a build as that will somehow have mtp and USB in general working.

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.

[RECOVERY][lavender][UNOFFICIAL] TWRP touch recovery for Redmi Note 7

{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's 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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
All function in a normal TWRP
Multi-language support
Supports MTP
Support decrypt /data!
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot flash recovery recovery.img" in command line
5. Reboot and enjoy it
Download:
https://drive.google.com/uc?id=1rp_cgVuk6fsRybN0wDoOTbt_Pc-vOiHx&export=download
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/thelazyindian/android_device_xiaomi_lavender-twrp
Note:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
When you flash twrp for the first time in MIUI you need to goto Wipe > Format Data otherwise you won't be able to boot to system as it will ask for password.
GAPPS FIX: In TWRP, goto Mount > system_root and try reflashing.
FAQ:
How is it different from other TWRPs available for lavender ?
This build uses standalone decryption which is better than the recoveries using vold decrypt as vold decrypt will fail if system ROM is corrupt or wiped
Credits:
Huge thanks to @abhishek987 and @vasishath for helping
@tufadorin @faraz shafi (For testing)

Reserved

Work fine with encryption

This is working with Global Variant ? greatz ...

It works well. Just one detail. You can not see the clock, because it appears in the same place as the camera.
Thank you for everything.

Just 5 more days left to test this ?

Can you install official miui ota zip after installing twrp and magisk?
Would it brick the device?

Nice built.. I think official build arrives soon

strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.

vkmcondor said:
Can you install official miui ota zip after installing twrp and magisk?
Would it brick the device?
Click to expand...
Click to collapse
It won't brick the device, but no you can't install them.
The update will just fail and reboot you back into MIUI. Everything working as usual.
If you want TWRP/Magisk installed and get updates then you'll have to manually download the 'Recovery ROM' to the update you want to update to. Then flash it in TWRP like you would a custom ROM.
You'll want to reinstall Magisk after you flash the Recovery ROM to get root back.
TWRP remains intact

Enddo said:
It won't brick the device, but no you can't install them.
The update will just fail and reboot you back into MIUI. Everything working as usual.
If you want TWRP/Magisk installed and get updates then you'll have to manually download the 'Recovery ROM' to the update you want to update to. Then flash it in TWRP like you would a custom ROM.
You'll want to reinstall Magisk after you flash the Recovery ROM to get root back.
TWRP remains intact
Click to expand...
Click to collapse
Do I need to format or wipe data?

great work, just need a few days to unlock my bootloader and try this one

Diniodoc said:
strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.
Click to expand...
Click to collapse
same happend to me.can you explain how you fixed it via commandline ? i have to wipe phone and flashed successfully Xiaomi.eu rom . i have global device.
also i flashed now Magisk 19.0 .and it works.
much thx for your work admin ?

majo3000 said:
same happend to me.can you explain how you fixed it via commandline ? i have to wipe phone and flashed successfully Xiaomi.eu rom . i have global device.
also i flashed now Magisk 19.0 .and it works.
much thx for your work admin ?
Click to expand...
Click to collapse
I did not fix it, but you can decrypt your /data via terminal in TWRP : "twrp decrypt PIN"
But I didn't understand you, are you still facing that problem or did you solved it by reflashing MIUI?

Diniodoc said:
strange behaviour: TWRP is asking for pattern decryption when PIN is used and vice versa.
Decryption via command line works fine.
Click to expand...
Click to collapse
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
Updated in OP

vkmcondor said:
Do I need to format or wipe data?
Click to expand...
Click to collapse
Not if you're just manually updating by flashing the Recovery ROM. Think of it as a dirty flash a custom ROM. Just install it on top of your current build and then flash your Magisk ZIP and any other mods that may have been overwritten (due to needing to patch the boot.img

Diniodoc said:
I did not fix it, but you can decrypt your /data via terminal in TWRP : "twrp decrypt PIN"
But I didn't understand you, are you still facing that problem or did you solved it by reflashing MIUI?
Click to expand...
Click to collapse
i was first on original rom.then i flashed TWRP from here.after reboot i hang on screen were i have to enter password to access android.so i never have set a password and tryed mi Pin and miui Account password...but none pin was acceptet.
then i wiped data ...reboot ...but android doesnt load.
so i flashed xuaomi.eu Rom . after flashing it .the phone startet succesfully....
the thing is.... i never entered a pin or password to dercrypt my device....and what helped was wipe and flash rom .... greatz..

I am getting error 64 when flashing arm64 gapps.

ebautista said:
I am getting error 64 when flashing arm64 gapps.
Click to expand...
Click to collapse
Why did you even flash gapps?

thelazyindian said:
Due to a bug in android pie, the recovery may ask for pattern if you have set PIN/password for encryption (and vice-versa). Unfortunately, to fix this you need to format your data partition and ask the developer of ROM to include this commit.
Updated in OP
Click to expand...
Click to collapse
Good to know THX. I'm still using original MIUI so I think there is nothing to do than waiting or better use a custom ROM
One more question. Does anybody know if there is the possibility to use a separate password for encryption different from the lock screen? This was possible in earlier versions of Android.

[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

How To Guide [GUIDE] how to flash android 12-13 based gsi without bootloops

i have decided to post my personal procedure for flashing android 12 and android 13 gsi
all gsi that i will mention booted succesfull on my device (code M2103K19G)
i dont assume any responsability for possible bootloops. the procedure is 100%, if you follow will not have any problem
pre requisites:
bootloader unlocked
STOCK global miui13 installed. latest global is my favorite, but also other version works (no miui12, gsi could boot anyway, but maybe not)
magisk installed for testing the gsi before definitive flash (suggested but not necessary)
a pc with adb and fastboot installed + mtk driver
first step: choose your favorite gsi
my suggestions are: Spark a13.1 (my actual rom), crdroid 12.1 based, arrow 12.1 based, latest pphusson
download the gsi and test it via dsusideloader (you can try all gsi that you want). this is very important for verify have all what you need
in alternative read changelog of gsi or users feedback. the gsi that i have mentioned 100% boot guaranted
when you have chose the gsi wipe data and reboot phone to FASTBOOTD (i will not explain how to do, a modder must know this)
if you boot into fastboot cant flash system
download and extract fastboot stock rom
after this simply:
open image folder of your fastboot extracted rom
open a terminal (for linux user) or a cmd window (con win10 users)
flash vbmeta disabling dm-verity check typing: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
flash system.img (DONT ERASE SYSTEM PARTION!) typing: fastboot flash system system.img
flash stock kboot.img (or magisk patched for have root) typing; fastboot flash boot boot.img
reboot typing: fastboot reboot
no other commands needs, i'm 100% sure. tested directly by me
if you have made all steps correctly, and you have choosed and tested a good no wipe data is need and phone 100% boot
obviously, before flash gsi is important read the changelog of the rom for know bugs, function missing, fuction added, battery backup, performance, ecc ecc
for info about all gsi connect to official telegram channels
my favorites are pphusson channel and naz channel (the developer of my actual rom)
good look and dont ask me info about gsi. Ask directly to official telegran channel
READ WITH ATTENTION: this procedure is what i do every time i want to flash a gsi. i never encontered any bootloop, expect when a made wrong
thing like boot from slot b, flash a wrong boot.img image, flash a magisk module that is not compatible. so i dont will assume any responsability for damages to your device. it means that the problem isn't my procedure

PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help

this is the GSI img file that nned to flashed am i correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
fastboot flash system system.img
Click to expand...
Click to collapse

GrandEsquiRE said:
this is the GSI img file that nned to flashed am i correct?
Click to expand...
Click to collapse
No. Download suggestions unless you know how to solve bootloop.

up864 said:
No. Download suggestions unless you know how to solve bootloop.
Click to expand...
Click to collapse
Nvm, i'm already on corvus rn

viktak said:
I don't quite understand your screenshot , and I don't have your EvolutionX ROM at hand, but all the other GSI I have tried came as one compressed file, which when extracted, will give you a .img file. You are NOT supposed to extract the .img file.
That IS the system.img file that you need to flash at:
Click to expand...
Click to collapse
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file

GrandEsquiRE said:
yeah, i just testing the evoX rom on sideload, it boot but i dont really like it, then i change my mind to corvus, that img file on the screenshot is just img from the dsu sideloader that has been extracted from img.xz file
Click to expand...
Click to collapse
with dsu sideloader u can test gsi directly from xz file, no extraction is needed. is explained into the app

Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
Andyan will tell you
Andy Yan's personal builds // GSI - Browse Files at SourceForge.net
sourceforge.net

iijul said:
Hi Wetito, I've been waiting a lot for your thread like this.
Let me try it this weekend.
One question please, which one is with gapps?
Click to expand...
Click to collapse
search if its BvN then its vanilla(no gapps) if BgN it has gapps

downlod arm64 bgN g=with gapps v=vanilla (no gapps)
slim version is no suggested for the gsi i have mentioned and tested
arm64= a/b device (like our)
a64= device with no dunamic partitions
i hope my guide could be helpfull to prevent a lot of possible bootloops
(also if my english is not perct, I tried to make it as easy and understandable as I could)

wetito said:
PART 2: WHAT YOU HAVE TO DO FOR NO BOOTLOOP
- start from miu13
- have the bootloader unlocked
- test the gsi with dsu sideloader before permanent flash (if rom boot, flashing is safe) or ask to users a suggestion for a compatible gsi for our device
- make all fastboot commands in fastbootd mode
- active slot for flashing and reboot must be the primary (in most of cases is slot a)
- flash the stock boot.img before reboot
- flash stock vbmeta disabling dmverity check before reboot
-if u enter into recovery after reboot, wipe data
except first point (some gsi boot also starting from miui12.5 but is not recommended) all other must do correctly. some step cause low issue (wipe data from recovery is not a problem). but (example) flashing a bad boot image (like a not tested twrp) could cause high damages to bootloader= no fastboot, no recovery, bootloop to xiaomi logo
if u want to know more about i say, google sure may help
Click to expand...
Click to collapse
What rom is that? Can you give me the download link, and does fingerprint and 5g work?

This guide worked, thank you so much!

*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,

mg1122tt said:
*This is just the review*I've tried multiple gsi's but the best one that i found to be both stable and attractive is SparkOS, I'm into Pixel Experience but it just slows the phone down to an unusable state so i tried SparkOS and it's Pixel enough that i like it and I've been using it for quite some time now and it hasn't yet slowed the phone down, I'm really happy w this gsi and would 100% recommend it to those who're having a hard time deciding on which gsi to implement,
Click to expand...
Click to collapse
thats exactly what I did. but no matter the branch/distro these new androids are so damn ugly chasing after ios and they're gettting uglier and bigger every update. .
I was mainly interested in newest GSI because of mKVM but didjt realise at the time that only two phones in the world c8rrehtlly posses requirements for it. Windows FTW!

Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
At what stage of the process? After what step?
In general, there is no time when you have to force reboot it. You can do the whole process using adb/fastboot commands as described in the OP.

TedFin said:
Hey, I'm having an issue where if i turn my phones screen off i have to force reboot it for it to turn back on. can you help?
Click to expand...
Click to collapse
install magisk fix for this issue, sometimes appear. u can find the guide in this forum section. the thread is gsi brightness fix