Database Info

[AOSP][9.0][GSI] AOSP Treble A750FN

This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix *click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon

compatibility
does it work for A750FNXXU1ARK2/ARK4?
Which file do I need to flash, vanilla, floss or gapps?

NickDeveloper said:
does it work for A750FNXXU1ARK2/ARK4?
Which file do I need to flash, vanilla, floss or gapps?
Click to expand...
Click to collapse
It should work with EVERY firmware on FN, but I simply was not able to try it out this way. Vanilla don't have gapps, use gapps imo.

This is awesome, thanks. Would there be a way to use stock camera app for wide lens support?

hhadi said:
This is awesome, thanks. Would there be a way to use stock camera app for wide lens support?
Click to expand...
Click to collapse
Only way to do it would be porting default camera app together with libs/drivers :c

Finger print option is not there in the settings for me. Is this a /vendor problem?

It sucks to be a a750gn user right now

Bootloop after flashing (help)
Erecik said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix *click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon
Click to expand...
Click to collapse
Am I the only one who is having a bootloop after flashing? (I did everything exactly like in the instructions.) Can anyone help me?

limeswift said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
Am I the only one who is having a bootloop after flashing? (I did everything exactly like in the instructions.) Can anyone help me?
Click to expand...
Click to collapse
Same here, I spent whole day on this thing and tried it 5+ times and lo luck. Maybe because I was trying it on A750F varient

I try to install 4 times. SM-A750FN
2 times got boot without network, ROM detects 2 SIM cards but unknown, cant search for networks, no phone numbers, only WiFi works.

Erecik said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix*click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon
Click to expand...
Click to collapse
A7 2018 is released with Oreo,So It's support A/B Partition

a750fn android pie
in my a750fn with this firmware A750FNPUU1BSC4, the aosp gsi rom not work. The only custom rom work for me is Android P (PR1) sGSI that is unofficial rom and it is google pixel rom but data not work! please can you help me?

I followed all the instructions.... Bootloop on SM-A750GN.

This Havoc OS version is working on my 750FN
https://forum.xda-developers.com/showthread.php?p=79267026
I've updated to newest Pie One UI Firmware first.
I had Havoc OS at my Xperia XZ and its a very light rom.
And I like the customization features.
With GApps aroma you can pixelfy it very well.
Camera is also working.
In my opinion the battery drain is more less than Stock Samsung ROM (and i installed a lot Google stuff with GApps aroma).
There are two annoying bugs;
-In windows no Drives appaer with usb connection (MTP device is present in device manager)
-No auto brightness.
Maybe someone could help with this two bugs.

It dose not work on my A750F Pie version. The build number is A750FNPUU1BSC4. I tried this rom to flash but I faced with bootloop every time, I tried other versions of GSI also but not worked yet!
Is there any solition? Plz help me!

As you can see in my post, it's for A750FN!

Erecik said:
As you can see in my post, it's for A750FN!
Click to expand...
Click to collapse
Can you tell me why it will work only for A750FN and not other firmware version like GN etc.

blazzer12 said:
Can you tell me why it will work only for A750FN and not other firmware version like GN etc.
Click to expand...
Click to collapse
It's not firmware difference. GN, FN, F, G, etc are different HARDWARE versions, so some minor changes are present in every version of phone. That makes it works only on FN

Erecik said:
It's not firmware difference. GN, FN, F, G, etc are different HARDWARE versions, so some minor changes are present in every version of phone. That makes it works only on FN
Click to expand...
Click to collapse
Thank you for clearing that up for me.

Hijacks said:
This Havoc OS version is working on my 750FN
https://forum.xda-developers.com/showthread.php?p=79267026
I've updated to newest Pie One UI Firmware first.
I had Havoc OS at my Xperia XZ and its a very light rom.
And I like the customization features.
With GApps aroma you can pixelfy it very well.
Camera is also working.
Click to expand...
Click to collapse
Sorry to ask that annoying question, but do you know if VoLTE and or WiFi Calling are working on any of the GSI ROMs?

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Introduction
This is an unofficial build of TWRP for Redmi Note 7 Pro (violet). Differences with the official one include:
- Supports CAF-based wrappedkey encryption (decryption) properly (tested with MIUI 10.3.5.0)
- Supports decrypting devices that have screen lock set up after Android 9 May update, which introduced a new key derivation function.
- Mounts the system partition at /system_root as per AOSP standards. This makes the auto-backup scripts (e.g. GApps / Magisk survival script) work properly during updates, and you no longer need any 'patch' to flash GApps / Magisk properly. However, this may break some existing ROMs. See below FAQ section for details.
- Appended DTBO to the recovery image so it doesn't depend on the dtbo partition. No standalone DTBO image required.
Flashing instructions
- Download and extract the img file
- Reboot to fastboot mode
- fastboot flash recovery whatever_img_file_you_extracted.img
- Reboot and press Volume + to enter recovery
- DO NOT try to run 'fastboot boot recovery.img', it won't work.
- DO NOT flash the fcrypt disabler if you use my recovery. There is no need to do so, and it is possible to mess stuff up if you don't know what you are doing.
- You have to format the data partition if and ONLY IF:
1) You were not encrypted, now going to an encrypted state, or vice-versa OR
2) You were on a ROM other than MIUI that does not support "wrappedkey" (ROMs would often state it supports wrappedkey if it does), now going to a ROM that supports it
Limitations
DO NOT boot this recovery with empty system and vendor partitions. It will fail to decrypt any data partition with empty /system and /vendor. DO NOT wipe system and vendor partitions without installing a new one before rebooting. I am working to remove this limitation.
Now works even with empty system and vendor partitions after 3.3.1-5. No need to worry about formatting system and vendor breaking TWRP any more.
The restore zip created by the Migrate app is NOT compatible with this recovery. It's a problem of the Migrate app, not this recovery. Please DO NOT try to flash the restore zip created by Migrate.
FAQ
- Q: Do I need any specific DTBO image to make this recovery working?
- A: Nope. It is appended to the recovery image so it will work with any DTBO.
- Q: What is wrappedkey?
- A: It's a different mode of FBE implemented in CAF, the Qualcomm branch of AOSP.
- Q: This cannot install ROM X, why?
- A: Because it mounts the system partition at /system_root, which is AOSP standard behavior for A-only system_as_root devices, but is broken in some custom ROMs currently (MIUI should work though). To make any ROM work again, they will need to include this commit from LineageOS Gerrit https://review.lineageos.org/c/LineageOS/android_build/+/247066
- Q: Decryption doesn't work with ROM X, why?
- A: Decryption should work for most ROMs based on the CAF branch (not AOSP). CAF ROMs (including official MIUI) use a different scheme for key storage, which is why TWRP hasn't supported it till now. I have ported the CAF encryption changes (wrappedkey) to TWRP, but unfortunately this will break ROMs that do not support the CAF wrappedkey mode of encryption. Here is a list of patches non-CAF ROMs need to support CAF-encrypted /data partitions https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged). If you confirm your ROM is CAF-based but the decryption still does not work, please open an issue on my GitHub repository which you could find below. (XDA threads are no good for issue tracking, sorry)
- Q: Why not contribute to the official TWRP?
- A: All the patches to the TWRP code base have been submitted to the official gerrit code review, though not merged yet, which you can see below.
Downloads
3.3.1-6: https://mega.nz/#!3QIRQYhK!Jq5QrGfJw5VCYZ8sq_BO1qNZecrFqlM9IB1IdSwogvI
changes: updated kernel to support pstore instead of /proc/last_kmsg. If you don't know what this is, it's probably not relevant to you.
Here you can find an unofficial LOS build with wrappedkey encryption and also proper system_as_root support for those survival scripts https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-lineageos-16-caf-encryption-t3933532. In addition, all official MIUI builds should flash just fine.
History versions:
3.3.1-5: https://mega.nz/#!nMowHKiL!zRvoTM0iIZKArmUDnZzaEFtXQv0_q7hIHUCmTHTOmOM
changes: 1) Now works even with empty /system and /vendor partition 2) Fixed brightness problem; 3) Enabled EDL Reboot
3.3.1-3: https://mega.nz/#!yAYXxAzZ!FNMYLzLphnSmJ-DbBx-OZUgxxYiftgn8e4Jn3kxiQik
Patches and sources
Patches for TWRP are available here:
https://gerrit.omnirom.org/#/c/34091/
https://gerrit.omnirom.org/#/c/34093/
https://gerrit.omnirom.org/#/c/34092/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34096/
Patches for ROMs to support wrapped key have been given in the above sections.
Source of the current device tree for TWRP: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp
Kernel source: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150, note that the device tree uses a prebuilt kernel image.
Contributors
PeterCxy, Dyneteve, merothh
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp

Now fixed and tested with MIUI.

PeterCxy said:
Now fixed and tested with MIUI.
Click to expand...
Click to collapse
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.

I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?

Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?

Can confirm this successfully decrypts storage, running xiaomi.eu on my phone. Thanks for your work.

Dwughjsd said:
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.
Click to expand...
Click to collapse
It did not decrypt MIUI 10.3.5.0 successfully due to magic (I missed some commits from qcom). It was fixed by pulling more commits in.

Jpwner said:
I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?
Click to expand...
Click to collapse
You won't need to erase userdata or flash fcrypt disabler anymore, if all the ROMs will update to support the wrappedkey encryption

Naveenthemi said:
Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?
Click to expand...
Click to collapse
just fastboot flash recovery whatever_you_downloaded_and_extracted.img

PeterCxy said:
just fastboot flash recovery whatever_you_downloaded_and_extracted.img
Click to expand...
Click to collapse
So it's possible for me to flash OTA Updates without encountering a bootloop and such?

Can someone please provide an alternate download link? The Mega link doesn't seem to work for me.
EDIT: Worked on a different device. Thanks.

Naveenthemi said:
So it's possible for me to flash OTA Updates without encountering a bootloop and such?
Click to expand...
Click to collapse
+1
Please answer

Good job! ?
I want you to know that your patch has been merged with the official one. I was away for a while so I hope you understand the little unfortunate delay.

In latest update can we flash any custom roms without any issue?

Yogendra Kher said:
In latest update can we flash any custom roms without any issue?
Click to expand...
Click to collapse
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in

PeterCxy said:
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in
Click to expand...
Click to collapse
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)

Naveenthemi said:
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)
Click to expand...
Click to collapse
Should work fine with MIUI. At least from what I have tested.

kushal.purkar said:
+1
Please answer
Click to expand...
Click to collapse
PeterCxy said it would as far as his testing had been done.

Gapps aroma not installing in this one as well. error 255

Can I flash Magisk and root my phone with this build.?
Do you have any Magisk zip file that will work.?
Thank you for your work

[RECOVERY][grus] KudProject's Unofficial TWRP 3.5.2_9-1 [16-05-2021]

This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.​
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.
Disclaimer​
Code:
/*
* Your warranty might not be void (thanks Xiaomi). However...
*
* I am 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 RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Requirements​
Xiaomi Mi 9 SE (of course)
Unlocked bootloader
Some knowledge on how to deal with your device... and patience.
Flashing Instructions​I assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
Where x and y are version of TWRP you're going to flash.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues​
/dev/null
Special Thanks​
Dees_Troy and everyone behind TWRP
Everyone on Mi 9 SE community
Device Sources​
TWRP repository fork
Device tree
Kernel source

Changelogs​twrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
twrp-3.4.0-0-KudProject-grus
Merged TWRP source changes up to 22 June 2020 (UTC+8)
Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
Restored system and vendor (non-image) backup support
Added support for backing up persist (and the image)
Build some blobs from source
Updated remaining blobs from V11.0.2.0.QFBEUXM
Updated prebuilt kernel to latest Pie
twrp-3.3.1-3-grus-20190802
Switched to source-built kernel
Updated blobs from MIUI China developer 9.7.4
Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
Added persist into fstab
Added vendor-side touch firmware
Get CPU temperature from proper thermal zone
Disabled vbmeta checks
Only allow image backups for system and vendor
Symlinked /system to /system_root/system for backward compatibility
Misc stuffs
TWRP and f2fs-tools upstream changes
twrp-3.3.1-2-grus-20190609
Fixed wrong USB-OTG mount point
twrp-3.3.1-1-grus-20190603
Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
Corrected vendor image flashing
Support for wiping /vendor
Support for flashing and backup up (as part of boot) DTBO
Defined TW_SCREEN_BLANK_ON_BOOT
(Properly) excluded TWRP app
Included private recovery configuration
twrp-3.3.1-0-grus-20190531
Initial build.

Notes​
Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.

Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...

it is save changed from wzsx150 twrp ? or must on fastboot ?

bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.

ok, gonna test it out , many thanks great work ??

Thanks! working so far so good

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol

rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.

Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk

krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!

@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks

denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?

luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.

denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?

luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029

Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).

puppetminds said:
Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs

[TREBLE] Pie VENDOR-IMAGE to boot Pie-GSI on X01BD

Code:
/*
* Your warranty is now void.
*
* We're 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 TREBLE
* SUPPORT 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.
*
*/
Alright so this is only done on user demand since GSI's were not booting with stock and custom rom vendor images
Install Instruction:
* Flash OFFICIAL TWRP
* Format /system, /data and /cache
* Flash vendor zip:
https://sourceforge.net/projects/arrow-os/files/EXTRAS/X01BD/P-GSI-Vendor.zip/download
* Flash boot.img:
https://sourceforge.net/projects/arrow-os/files/EXTRAS/X01BD/boot_permissive.img/download
* Install any Pie GSI system image using TWRP (Install image -> choose your system.img -> select system partition)
* Reboot
Known issues:
You tell me
Bug report:
All bug reports without any logs will just be ignored.
Where can i find GSI?
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Working GSI's:
* PhhAOSP pie
* ArrowOS GSI 9.x
* AOSiP GSI pie
Lemme know and I'll update it here!
Contributors
@kubersharma, @bauuuuu
(GPL kernel source: https://github.com/ArrowOS-Devices/...tree/9e41580d6c9fb2d5d896fef5ac5403a12d882d00 for the bootimge (kernel inside) linked)
PS: Generic System Image are made to support all treble devices but do not expect it to work as perfectly as a device specific build nor expect to have everything working!
ENJOY

reserved

reserved

Is it for real?

Will sGsi roms boot.?

Anubhav_singh said:
Will sGsi roms boot.?
Click to expand...
Click to collapse
This is basically for properly made GSI (built from sources for example: the one from phhusson or based on his sources)
I am not sure if OEM ported (sGSI) will boot
But we will see what we can do. Thanks

Wow, thanks for this. You and Bauuuuu always surprise us.

Will android q gsi boot

reverseflash said:
Wow, thanks for this. You and Bauuuuu always surprise us.
Click to expand...
Click to collapse
+1

@kubersharma the vendor image does not seem to work with OEM ported GSIs. I've tested MIUI but that got stuck on Asus logo, didn't reach the bootanimation.
I've attached a zip (2 logs), one was tested with the vendor image on this thread and second with default Arrow vendor.

As the OP says it's for source built pie GSIs

There is a huge background story on how messed the treble is in our device right now thanks to Asus, for having too much blob dependency on system.

If someone wants to try Q GSI dp6 (Generic or Pixel) should give a try after flashing my latest (20190812) LineageOS 16.0 build
https://sourceforge.net/projects/ku...12-UNOFFICIAL-X01DB-user-release.zip/download

kubersharma said:
If someone wants to try Q GSI dp6 (Generic or Pixel) should give a try after flashing my latest (20190812) LineageOS 16.0 build
https://sourceforge.net/projects/ku...12-UNOFFICIAL-X01DB-user-release.zip/download
Click to expand...
Click to collapse
I tried pixel gsi but that didn't even reach bootanimation. Did you flash any additional patches?
Edit: I flashed permissiver and fix_zygote.

Thank you kuber and bauuua for your work for our device

Please make one too for X00RD. Plz ?

Need of Vendor For Android 10 OOS
Need vendor for android 10 Oxygen OS ...it's time you havent updated vendors Dev's...thanks in advance

Hi, @kubersharma. Sorry for the off-topic question but I have an Asus Zenfone 4 (ZE554KL) on which with the Oreo and Pie upgrade ASUS standardized BLOBs but does not created a dedicated vendor partition, so no official treble support. I wish I could flash the GSIs on it. The part of creating the vendor partition is no problem, but would you have any tips or tutorials on how to properly move the files from /system/vendor to /vendor in a functional way and the boot img hack needed to boot? Thank you very much!

does it work on android 10??

hi thank you for the rom. Can you make one for zs551kl(zenfone 4 pro) thank you very much

[TWRP][UNOFFICAL] OrangeFox Recovery Project [R10.0]

Code:
/*
* Your warranty is now void.
*
* We're 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 recovery
* 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.
*
*/
OrangeFox Recovery Project FOR PDX206 R10.0
About OrangeFox Recovery:
OrangeFox Recovery
wiki.orangefox.tech
What`s working:
Data Encryption (Need to format data for the first time)
Fastbootd
ADB Sideload
Flashing ROM
mount point at /system
mount point at /product
mount point at /vendor
mount point at /ODM
Bugs:
SD Card (Permanent)
[Some SD Card May can read/write]
Download:
AFH
How to flash:
Flash it at fastboot or fastbootd using this command
Code:
fastboot flash recovery X.img
Then Reboot
Code:
// For fastbootd
fastboot reboot fastboot
// For recovery
fastboot reboot recovery
About Encryption (Read First!):
Encryption
wiki.orangefox.tech
Source:
Recovery DT
Feel free to donate me:
Paypal

You are the best man!

Nice thank you so much for that! Finally a working custom recovery for us, and much better than TWRP lol
I spotted some bugs anyway
1. We can't modify the splashscreen
2. We can't select our sd card for backup or even mount it (i'm still in fat32 (from previous LOS installation and in stock rom)

Hey, thanks a lot for that ken442266 !
I have 2 questions:
* Does it work if I updated my Xperia 5 ii with Android 11 ?
* When you write SD card isn't recognized, is it whatever possible to backup a rom backup from internal memory?
* Is it possible, with OrangeFox recovery, to root your Xperia 5 ii with Magisk onto Android 11 stock rom?
Thanks a lot for your help,
Yoannjap

Yoannjap said:
Hey, thanks a lot for that ken442266 !
I have 2 questions:
* Does it work if I updated my Xperia 5 ii with Android 11 ?
* When you write SD card isn't recognized, is it whatever possible to backup a rom backup from internal memory?
* Is it possible, with OrangeFox recovery, to root your Xperia 5 ii with Magisk onto Android 11 stock rom?
Thanks a lot for your help,
Yoannjap
Click to expand...
Click to collapse
Hi Yoannjap,
I can answer all three of these from my personal experience.
1. This works for me on Ken's Pixel Experience 11 Rom, which is android 11 based. However, it is using an android 10 vendor as a basis. I have yet to test it over Android 11 from stock.
2. You can do backups to internal storage, my SD card doesn't work yet and I was able to do that just fine.
3. Magisk should be flashable, but Magisk currently doesn't work with Stock android 11. I have it working with Pixel Experience 11 however.
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Here is an issue a few other user's have commented on about Magisk on Stock A11

Jayram2000 said:
Hi Yoannjap,
I can answer all three of these from my personal experience.
1. This works for me on Ken's Pixel Experience 11 Rom, which is android 11 based. However, it is using an android 10 vendor as a basis. I have yet to test it over Android 11 from stock.
2. You can do backups to internal storage, my SD card doesn't work yet and I was able to do that just fine.
3. Magisk should be flashable, but Magisk currently doesn't work with Stock android 11. I have it working with Pixel Experience 11 however.
Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II (needed system_ext removed from fstab) · Issue #3752 · topjohnwu/Magisk
ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...
github.com
Here is an issue a few other user's have commented on about Magisk on Stock A11
Click to expand...
Click to collapse
Thanks a lot for your response
1. Ok, I am very looking forward an OrangeFox recovery fully based on an Android 11 stock ROM (included a A11 vendor partition.
2. I also hope someday a version of OrangeFox could arrive with microSD compatibility...
3. finally, thanks for the link of the bootloop of Android 11 when you try installing MagiSK.
Good luck,
Yoannjap

However, do you know if OrangeFox R11 version works with Android 11 ROM on Xperia 5 II?

And sorry I asked you the same on your Kernel patched with Magisk.
Could you help me and other users, giving the complete step by step process from unlocking phone to get Orangefox and this new Kernel with Magisk installed on it?

Yoannjap said:
However, do you know if OrangeFox R11 version works with Android 11 ROM on Xperia 5 II?
Click to expand...
Click to collapse
It works with Pixel Experience 11, although its uses a Q vendor as a basis.

Yoannjap said:
And sorry I asked you the same on your Kernel patched with Magisk.
Could you help me and other users, giving the complete step by step process from unlocking phone to get Orangefox and this new Kernel with Magisk installed on it?
Click to expand...
Click to collapse
There's already a guide by @Miustone for unlocking and flashing firmwares and images: https://forum.xda-developers.com/t/...g-with-magisk-and-flashing-firmwares.4177209/
Process is still the same.

any chance of getting the device trees for this build?

I tried to flash this rec on 58.1.A.5.159 /A11 /xperia 5 ii.
Fortunately, it can run normally and there is no boot loop.
this rec still can manage magisk modules on A11.
However i found two issues:
1. The background theme does not work properly on A11.
2. Like running on Android 10, this rec resolution seems a bit wrong.

Thanx for sharing,man! is there anything new updates for A11 stock rom 222? Tried Orange Fox 10R, not working on my AS52 . Issued as mount problem, cant find device and so on.Any suggestions? if i want to install Los u posted before how do i do? Get lower version stock rom first or wait for new recovery supported?Many thanx

Does anyone have a mirror? The GitHub repository is no longer available.

This custom recovery it's working on xperia 5 ??

This custom recovery it's work on xperia 5 ??