Database Info

[RECOVERY][enchilada] Unofficial TWRP 3.2.1-3 for OnePlus 6 by wuxianlin

Entire credit goes to @wuxianlin; I've just mirrored and organised stuffs.
Downloads:
Baidu
AFH mirror
Fixed variant by @joemossjr & @charlieb620
Sources:
https://github.com/wuxianlin/android_device_oneplus_enchilada
http://wuxianlin.com/
Screenshots:
https://m.weibo.cn/status/4243215098108813
Instructions:
Download required files from Downloads section.
Unlock the bootloader.
Reboot to bootloader.
Boot into TWRP: fastboot boot recovery-xx.img
Change Partition slot using TWRP: [Reboot => Change_Slot]
(for example, if you're in slot A, change it to slot B and vice versa)
Flash twp-installer zip.
Flash Magisk (use latest) for root access (optional).
Success!

Reserved for future.

Sweet, will give it a shot! Thanks!
Sent from my [device_name] using XDA-Developers Legacy app

Nice

Can't you just do fasboot flash recovery nameofrecovery.img?

JazzieBoi said:
Can't you just do fasboot flash recovery nameofrecovery.img?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76626087&postcount=127

Nice
Sent from my ONEPLUS A6000 using Tapatalk

akaHardison said:
Finally,TWRP is ready.
Sent from my ONEPLUS A6000 using Tapatalk
Click to expand...
Click to collapse
Finally? Dude the phone has been out like 3 days in the US and less than 2 weeks I believe anywhere else.
Get some patience maybe.

Is this still a temporary recovery or does this method make TWRP your permanent recovery?

Eric214 said:
Is this still a temporary recovery or does this method make TWRP your permanent recovery?
Click to expand...
Click to collapse
You need to flash TWRP-installer in TWRP, if you want permanent recovery.

Thaaank you very much!

Titokhan said:
Download required files from Downloads section.
Boot into TWRP: fastboot boot recovery-xx.img
Click to expand...
Click to collapse
Which files are required? There are a bunch of different files on that Baidu page.
Which image file should be booted to?

Displax said:
You need to flash TWRP-installer in TWRP, if you want permanent recovery.
Click to expand...
Click to collapse
where can I get twrp-installer from?

Displax said:
You need to flash TWRP-installer in TWRP, if you want permanent recovery.
Click to expand...
Click to collapse
so will making twrp permanent remove the a/b partition? that means i can't flash a/b compatible roms?

@nathanchance... I miss you
Enviado desde mi ONEPLUS A6003 mediante Tapatalk

There is really a lot of files in there. Which img should I boot into for the twrp?

There is a textfile in chinese (i assume) which I let go through google translate:
textfile
Maybe this will give some new information:
Code:
One plus six use ab partition, bring a lot of inconvenience to the brush, temporarily suggest less toss
One, unlock BootLoader (pay attention to backup data)
1. Developer Options Open OEM Unlock
2. Enter the fastboot mode: adb reboot bootloader
3. Unlock: fastboot oem unlock
The mobile phone prompts whether to unlock, the volume key selects Yes, the power button confirms
4 wait to boot
Second, brush into the specific boot
1. The disk boot folder has many types of boot
Introduction:
Official boot: the official original boot, recovery mode for the official recovery
Twrp boot: After brushing into recovery mode becomes twrp
Boot-with-magisk: automatically install migisk after brushing, recovery mode is official recovery, need to install magisk apk
Twrp boot-with-magisk: automatically install migisk after brushing, recovery mode is twrp, need to install magisk apk
name:
For example, boot-180513-h2os.img is based on the hydrogen OS 180513 version, be sure to match the use
Other files are similarly named
2. Brushing method
Enter the fastboot mode: adb reboot bootloader
Brush into the boot partition (boot.img is the path to the file being flushed into)
Fastboot flash boot boot.img
or
Fastboot flash boot_a boot.img
Fastboot flash boot_b boot.img
3. Restart
Fastboot reboot
Third, fastboot brush
Network disk fastboot flashable folder stored fastboot mode can be brushed into the img file
For example, you want to brush the system.img to the system partition (system.img is the path to the file you are working on)
Fastboot flash system system.img
or
Fastboot flash system_a system.img
Fastboot flash system_b system.img
For example, you want to brush the vendor.img to the vendor partition (vendor.img is the path to the file to be scanned)
Fastboot flash vendor vendor.img
or
Fastboot flash vendor_a vendor.img
Fastboot flash vendor_b vendor.img
Fourth, twrp card brush official ROM reserved twrp method
Twrp card brush official ROM brush common patch /twrp folder under the patch package
Note, twrp card brush official ROM, in fact, brush into the current partition does not start, after brushing is complete, activate the partition, restart after running this partition, but at this time twrp run in the current boot partition, need to restart the system into twrp Or restart the recovery mode into twrp, restart the boot partition and the partition started at this time is consistent, brush into the patch for the current boot partition has a role, otherwise the patch package is likely to be brushed into the next boot does not start Partition
Fifth, install magisk
If it is fastboot brush boot, directly brush into the boot with magisk
If it is twrp card brush official ROM, card brush twrp patch, restart twrp or restart boot into twrp, and then brush the patch under the commonly used patch / magisk folder
Six, install the supersu
Twrp card brush official ROM, card brush twrp patch, restart twrp or restart boot into twrp, and then brush the patch / supersu folder patch, even the computer input adb disable-verify, prompt Successfully disabled verity, restart
Seven, install xposed
If you have installed magisk, install xposed directly in magisk
If you have already brushed supersu according to the above method, add the official xposed patch and restart it.
Eight, third-party ROM
Temporarily unknown
Nine, expand the extension
Interested friends are expected to notice that you can choose to brush img into the _a or _b partition in the tutorial of brushing the img into the corresponding partition.
So how do we know if our phone is currently using a partition or b partition?
1.twrp mode, restart, there will be shown below
2. System mode, adb shell getprop ro.boot.slot_suffix
If _a is a partition, _b is partition b
AB Division, except for Google’s mobile phone, it is rare to see other mobile phones use,,,
So there are few methods related to playing online games,,,
Author:
Wuxianlin
Weibo: wuxianlin000000

You can't flash the recovery image... It boots up slowly into the OS, and that's it. Guess we will have to wait a little longer

The TWRP of OP6 looks like Google Pixel this time

Thanks!!!
But which version (file) do I need for Oxygen OS 5.1.5?
In each filename is someting with h2o-rom?

[RECOVERY] LineageOS 17.1 Recovery [X3][2020/08/24]

Introduction
This is a LineageOS Recovery compiled from the source tree of LineageOS 17.1 for Realme X3/X3 Superzoom.
Instructions (Installing Recovery):
1. Download recovery.img & vbmeta.img
2. Reboot to bootloader
Code:
adb reboot bootloader
3. Flash vbmeta
Code:
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
4. Flash recovery
Code:
fastboot flash recovery recovery.img
5. Run
Code:
fastboot reboot recovery
to enter LineageOS Recovery
Instructions (Installing Magisk):
You have to use the official Magisk, version 20.4 or later. Installing an older Magisk may make the system unbootable.
1. Download Magisk >= 20.4, put onto computer
2. Reboot to LineageOS recovery, select `Mount /system` (you may see some errors, but they can be safely ignored)
3. Select `Apply update from ADB`
4. Run
Code:
adb sideload Magisk-xxx.zip
5. You will see a signature verification error, select `Yes` to bypass the check
6. Reboot to system to enjoy your Magisk installation.
Notes:
- Since it's not TWRP, you cannot decrypt your /data in recovery for now, which means no data backup or recovery, and you cannot install on-device flashable zips through this recovery.
- Since it's not TWRP, it cannot prevent your OS from overwriting recovery automatically. If you use official ROM, you may need to manually re-flash the recovery every time. I'm not sure whether this can be bypassed with some Magisk module.
- You need to always click "Mount /system" before flashing any mods into the system (i.e. Magisk, OpenGapps, etc., ROMs themselves are not affected), otherwise they will fail to install. (Clicking the option does not actually mount /system; it just sets up necessary mappings from the super partition to each of the dynamic partitions so that the installation scripts will work)
Download:
https://sourceforge.net/projects/siddharthbharadwaj-s-builds/files/Realme X3/LOS Recovery/
Source Code:
Kernel: Used stock prebuilt one.

Thank you! This is now my preferred method to root Lineage that I haven't seen anywhere else.

Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO

I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance

Anubis2002 said:
I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is on my old Samsung A50. I honestly don't know the first thing about the root program that android runs on so I am looking for someone that has patience that can help a noob.
I have watched many youtube videos on this topic but I have found nothing on my specific phone.
Thanks in advance
Click to expand...
Click to collapse
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.​So make up your mind!

lopestom said:
About ROOT: https://forum.xda-developers.com/t/...attery-charge-limit-root-application.4251443/
About GSI: You not need TWRP. But if you want backup your userdata so need install that.
All depend about your decision: I'm install GSI and test. I chose the perfect GSI for me; so I don't need the backup => you not need custom recovery so use stock recovery.
I want GSI and need backup => need TWRP.
In the true both recoveries [stock & TWRP] has the fastbootd implemented!
So you need:
1- unlock bootloader;
2- stock or specific vbmeta file;
3- know how use fastboot commands for flash GSI;
4- Every time is more security flashing Custom ROMs if you have stock ROM!
Are you ready for flash GSI??!
Even if something goes wrong and you can't "revive" the device again?
Do you have everything it takes to feel relaxed if something goes wrong or successful?!!
I can put the instructions myself. But I will never be responsible for your actions and choices.​So make up your mind!
Click to expand...
Click to collapse
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.img
{
"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"
}

EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
Click to expand...
Click to collapse
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
EdsterX71 said:
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks

EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
EdsterX71 said:
Flawless instructions , thank you so much! TRWP & Root!
i had to flash Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
then follow your instructions .
Because firmware BLU_G0370WW_V10.0.04.03_GENERIC the WIIFI and Bluetooth did not function when using older version boot.img .
Click to expand...
Click to collapse
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.

lopestom said:
Unfortunately in the compiling TWRP time I haven't MicroSD to testing.
But now I know about and need fix so easy. The fix is not easy because my time and the issues about different adress/partition of MicroSD in G90 Pro. So I needed more knowledge and informations to fix that and need only write correct adress/partition. That's is to mount/start MicroSD automatically in the TWRP. But....
I not remember now because I not using MicroSD or OTG in the TWRP or ROMs. But maybe worked with the option in the TWRP - Wipe - FORMAT DATA; Reboot - Recovery. Test!
I have PBRP (other awesome Custom Recovery) if you want test too.
It's a shame you didn't try to remove the boot.img file from version 10.0.04.03 because it would be interesting to know the kernel changes. But as far as I know it was a security update and the fix for call volume I think.
I not using Xposed a very time ago. Sorry. You need search/ask in the Xposed forun.
Click to expand...
Click to collapse
Yes I would like to try PBRP , Thanks, I really like the specs on the Blu G90 Pro... But to be honest the camera is crap.

EdsterX71 said:
EdsterX71 said:
In TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
n TRWP the option for select storage for exsdcard (0)mb will not mount micro sdcard?
And which partitons do you select for a full backup.
thanks
Click to expand...
Click to collapse
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.

EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
EdsterX71 said:
I also have the Blu G90 Pro and trying to get root , could you please give me detailed instructions on using magisk or how to flash with trwp, i have flashed trwp through fastboot but cant decrypt data and when you restart device it reverts back to stock recovery.
also cant find stock firmware for this version BLU_G0370WW_V10.0.04.03_GENERIC to use magisk to patch boot.imgView attachment 5337319
Click to expand...
Click to collapse
ANy error with 10.0.04.02?
As your message and picture had BLU_G0370WW_V10.0.04.03_GENERIC
Update: Yes the kernel was changed with more informations and need new Custom recovery with that to work with new stock ROM.

EdsterX71 said:
boot.img for 10.0.04.02
And yes i would like to try PBRP, thanks.
Click to expand...
Click to collapse
Sent in PM to you.

I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team

lopestom said:
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
Need gsi link
Click to expand...
Click to collapse

Lopestom im having lags, overheat issues and system slow downs , why??
with or without gsi
my guess is hardware issue (emmc chip)

DarkeEmpire said:
I want a gsi link
Click to expand...
Click to collapse
Any GSI-Treble A10 arm64 ab - https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/

Can I use pixel experience

lopestom said:
I decided to write the commands for those who have TWRP or stock recovery. Both will work as it has the fastbootD option.
First, select the GSI for your architecture. On BLU G90 Pro, it is arm64 ab. Usually we must unzip to have the img file.
Copy the GSI.img file and the modified vbmeta.img file in the ADB folder - tools platform with which you unlocked the bootloader. Remember the need for the most current version of ADB!
platform-tools#downloads
For some users it is necessary to write warnings:
Stop now if you do not know what you are doing or have no experience in reviving your device!!!
You must have backup of your NVDATA, NVRAM, NVCFG, PERSIST, files made from your device.
The device must have the bootloader unlocked!
You need know the difference about fastboot and FASTBOOTD in your device!!
Your device has bootloader mode: recovery - fastboot - reboot (system)
Stock recovery has very options:
reboot system - reboot to bootloader - wipe - Enter fastboot - ...
reboot to bootloader => normal fastboot
Enter fastboot => FASTBOOTD
FASTBOOTD => some options
TWRP:
Reboot - Reboot bootloader => normal fastboot
Reboot - Reboot fastboot => fastbootD
Spoiler: Install GSI - BLU G90 Pro - G0370WW
Device in fastboot => You see the Serial number by your device
Code:
fastboot devices
The file vbmeta can use stock vbmeta; BUT you should flash vbmeta mod [vbmetaAndroidSC_mod.zip] for have TWRP and GSI.
Code:
fastboot --disable-verification flash vbmeta vbmeta_mod.img
Wipe userdata
Code:
fastboot -w
Your device MUST be at the fastbootD menu now. If not, you will not be able to flash the GSI successfully. Again, you can using TWRP or stock recovery.
fastboot normal to fastbootD
Code:
fastboot reboot fastboot
Erase a flash partition
Code:
fastboot erase system
or
Code:
fastboot delete-logical-partition system
deletes the product partition, allowing a larger system partition
Code:
fastboot delete-logical-partition product
I not need resize-logical-partition product. But if you want:
You will need a larger system partition to flash a GSI. There are 2 ways to achieve this
A. fastboot resize-logical-partition product 509344768
B. fastboot resize-logical-partition system 3089272064 or 3889272064
resizes product and system partitions. This gives you about 3GB of system partitions. You can adjust or arrive at your own numbers if you want different sizes.
Flashing GSI files: Sets disable-verity when flashing & Sets disable-verification when flashing the file img in the system partition.
Code:
fastboot --disable-verity --disable-verification flash system GSI.img
GSI.img is the file of any zip file that have any name by developers/Custom ROM.
For confirm great & fast start GSI
Code:
fastboot -w
For confirm and boot clean go to normal fastboot
Code:
fastboot reboot bootloader
Code:
fastboot erase userdata
Reboot to system
Code:
fastboot reboot
Wait the time 5~15 minutes to start.
Enjoy
Note: Since the Team Win code maintainers; still haven't found a way for TWRP to modify (write/copy/delete) any file in the logical partitions (System - Vendor - Product - odm) as Super partition; TWRP cannot install the img file on the system partition.
If you want to make changes you can try this: [SCRIPT][Android 10+] Universal Mount System read write R/W
In the GSI files you can modify files in the Super partition.
About adb-fastboot: Android Debug Bridge (ADB) Commands Manual
Any other questions or more help for BLU users: BLU Development Team
Click to expand...
Click to collapse
Shorten Code for blu g90 pro GSI NOOBS edit
fastboot devices
fastboot --disable-verification flash vbmeta vbmeta_mod.img
fastboot -w
fastboot reboot fastboot
fastboot erase system
fastboot --disable-verity --disable-verification flash system GSI.img
fastboot reboot
GSI supports
Havocs, Corvus and others but not pixel experience image is too large with gapps

sometimes when transferring file from pc to the device it fails over 1mb files like what????

lopestom said:
Spoiler: Unlock & Install Custom recovery - BLU G90 Pro
- OEM Unlock - select
- USB Debugging - select
cmd command:
Code:
adb devices
Code:
adb reboot bootloader
(or use the menu option).
The screen should show "FASTBOOT mode" at the bottom of the screen in small font.
cmd command:
Code:
fastboot flashing unlock
or
Code:
fastboot flashing unlock_critical
Read phone screen for instructions.
You will have to press volume up key to continue to unlock.
- Reboot phone. Setting again without data info. Power off.
Power & VOL+ to show FASTBOOT mode - recovery
Go to stock recovery and make WIPE data/factory reset & WIPE cache partitions.
Spoiler: Install Custom recovery
stock recovery - bootloader => fastboot (not fastbootd)
cmd command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmetaAndroidSC_mod.img
cmd command:
Code:
fastboot flash recovery recoveryTWRP350_G0370WW.img
cmd command:
Code:
fastboot reboot-recovery
File download from my github: TWRP3.5.0_10 BLU G90 PRO
About updated ROM version: You can remove/copy all partitions from last version any time. So boot.img or recovery.img can have with SPFT Read Back process with scatter file from v10.0.03.03 stock ROM.
Stock ROM G90 Pro BLU_G0370WW_V10.0.03.03
ROOT: Simple. Use custom recovery and flashing magisk-zip
or if you have boot.img stock so use magisk manager to have boot_patched.img and flash via fastboot.
Click to expand...
Click to collapse
Whenever I go into fastboot mode (with the text on the bottom left) no fastboot commands will work on my G90 Pro. Therefore I can't follow the rest of the instructions. Any possible solutions? Thanks.

BV9900 TWRP and Root for EAA Firmware

Hello I Port TWRP 3.3.1. and Magisk Manager v23 for rooting BV9900 with Firmware BV9900_EEA_S900AA_V1.0_20200522V12_user_20200523-0035!
If you have Firmware BV9900_EEA_S900AA_V1.0_20191225V08_user_20200103 Update to BV9900_EEA_S900AA_V1.0_20200522V12_user_20200523-0035.
instructions:
You must follow a procedure!
Make Backup because your data will be wiped!
Unlock Botloader!
Flash Firmware BV9900_EEA_S900AA_V1.0_20191225V08_user_20200103 with SP Flash tool -Includet Scatter File
Offical Firmware:
MEGA
MEGA provides free cloud storage with convenient and powerful always-on privacy. Claim your free 20GB now
mega.nz
Boot system
Connect wifi internet
Make system update to version BV9900_EAA_S900AA_V1.0_20200522V12_20200523-0035 - Normal Update in the Phone
Run on PC adb Tool and flash Vbmeta.imf from TWRP Folder:
adb devices
adb reboot-bootloader
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Power on Mobile
Power off Mobile
Run Sp Flash tool and Flash:
(RECOVERY)TWRP-Recovery 3.3.1.img and
(BOOT)-Boot-Magisk23.img with SP Flash Tool
Disconect Phone from PC
HOLD KEY UP and POWER. Then click Recovery.In TWRP-Recovery Slide "Swipe to Allow Modifications"
Go "Mount" Vendor and nvada
////If you cant mount Data Partition in TWRP-Recovery:
Format Data Partition In TWRP Recovery - You must Formating data not Wipe
Wipe Dalvik/Cache
Reboot to Recovery (check now if you can mount data)
/////
Copy File from BV9900 TWRP&Magisk/fstab/Vendor/etc to vendor/etc
Copy File from BV9900 TWRP&Magisk/fstab/nvdata to nvada
Reboot to System
Instal magisk apk from your launcher....Click ok and restart phone.
Now you can login to google acount.
If you have problem with loading Widgets find build.prop file in mobile or download from Playstore BuildProp Editor
This problem is solved very easily with root access. You just need to fix one line in the build.prop file:
ro.freeme_freemanager=1
ro.hct_autostart_manager=1
In these lines you need to change 1 to 0
Magisk manager works without TWRP great
In TWRP recovery dos not work mtp
And big problem with TWRP is if you formating data then mobile can not recognize sim card (IMEI null,baseband unkown)
If anybody have solution thanks.

Android 10?

Android 9

How remove Chinese text? Thank You.

Question phone wont boot after installing twrp or gsi (a125w, originally an a125u)

i've unlocked the bootloader of my phone, and it boots fine with stock recovery & oneui core 3.1, but whenever i install twrp or a gsi, my phone ceases to boot. any ideas?

tekkitheidiot said:
i've unlocked the bootloader of my phone, and it boots fine with stock recovery & oneui core 3.1, but whenever i install twrp or a gsi, my phone ceases to boot. any ideas?
Click to expand...
Click to collapse
Do u install TWRP through Odin?

C-Andy said:
Do u install TWRP through Odin?
Click to expand...
Click to collapse
The twrp must be built for a125w.
If you want I can modify the one you're trying but you need to send me your a125w stock recovery.img.lz4

physwizz said:
The twrp must be built for a125w.
If you want I can modify the one you're trying but you need to send me your a125w stock recovery.img.lz4
Click to expand...
Click to collapse
hello, ive been looking for a twrp that is compatible with sm-a125w because that is my model. how would i send you the stock recovery for this?

imdrew1234 said:
hello, ive been looking for a twrp that is compatible with sm-a125w because that is my model. how would i send you the stock recovery for this?
Click to expand...
Click to collapse
Just post it.
Attach files

physwizz said:
Just post it.
Attach files
Click to expand...
Click to collapse
here is the file. i included boot and vbmeta as well.
the link: https://drive.google.com/drive/folders/1L5491qUjTXUHKxXdLLlSOLBmwFY1rou-?usp=sharing

imdrew1234 said:
here is the file. i included boot and vbmeta as well.
the link: https://drive.google.com/drive/folders/1L5491qUjTXUHKxXdLLlSOLBmwFY1rou-?usp=sharing
Click to expand...
Click to collapse
Unzip to find the tar file.
Installing instructions in next post

Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz

thank you so much ive been looking for this forever!

physwizz said:
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz
Click to expand...
Click to collapse
i was also wondering if you knew why i cant make modifications to /system partition. whenever i check it in mount on the main screen of twrp /system still doesn't show. I wanted to get the pixel experience rom but i cannot due to this issue im facing since the system partition does not show as a partition i can flash the custom rom to as a gsi.

imdrew1234 said:
i was also wondering if you knew why i cant make modifications to /system partition. whenever i check it in mount on the main screen of twrp /system still doesn't show. I wanted to get the pixel experience rom but i cannot due to this issue im facing since the system partition does not show as a partition i can flash the custom rom to as a gsi.
Click to expand...
Click to collapse
Do you see system.img as a partition?

physwizz said:
Do you see system.img as a partition?
Click to expand...
Click to collapse
i do. only data and system image. data doesn’t show as flashable and system image is already full plus not enough storage for the custom rom. i think that there is supposed to be a prompt from twrp when you load into it to allow modifications to the system partition but this prompt does not show on this twrp which is weird. i cannot find a solution to this issue.

i

imdrew1234 said:
i do. only data and system image. data doesn’t show as flashable and system image is already full plus not enough storage for the custom rom. i think that there is supposed to be a prompt from twrp when you load into it to allow modifications to the system partition but this prompt does not show on this twrp which is weird. i cannot find a solution to this issue.
Click to expand...
Click to collapse
If you want to install a gsi to system.img you can.
You may need to go to advanced terminal and type wipe system Or wipe SYSTEM_ROOT

physwizz said:
If you want to install a gsi to system.img you can.
You may need to go to advanced terminal and type wipe system Or wipe SYSTEM_ROOT
Click to expand...
Click to collapse
but what do i do if the system image is only 3.1gb and the rom is 3.48 gb? is there any way i can repartition it or something?

imdrew1234 said:
but what do i do if the system image is only 3.1gb and the rom is 3.48 gb? is there any way i can repartition it or something?
Click to expand...
Click to collapse
Choose a smaller gsi

physwizz said:
Choose a smaller gsi
Click to expand...
Click to collapse
i can’t seem to find any other custom roms for my model sm-a125w they are all for the sm-a125f model and i don’t want to brick my phone. do you think the f model roms would work on my model or have any rom suggestions?

physwizz said:
Choose a smaller gsi
Click to expand...
Click to collapse
whenever i try to wipe system_root it says inaccessible or not found in twrp terminal. i dont know whats going wrong here.

imdrew1234 said:
whenever i try to wipe system_root it says inaccessible or not found in twrp terminal. i dont know whats going wrong here.
Click to expand...
Click to collapse
Wipe system

tr
physwizz said:
Wipe system
Click to expand...
Click to collapse
tried that as well and same error occurs.