Database Develop

[GUIDE] How To Backup Your OWN Firmware on any PRA

This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)

** Note **
just follow the steps and will have a fully backup, I tested 100 times while making roms for this device!
regards

One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..

Dr.TheMaster said:
One question, in step 3, when I flash stock_recovery.img.. Can I skip that and keep TWRP? For flashing Magisk or modified SuperSU.. Thanks a lot man.. You are the best..
Click to expand...
Click to collapse
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.

haky 86 said:
TWRP it's a mandatory to have root permissions, but you can revert to stock recovery once install Magisk or SuperSu.
Click to expand...
Click to collapse
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?

Dr.TheMaster said:
Yeah but I mean can I keep it as TWRP or is it necessary to flash the stock one after rooting?
Click to expand...
Click to collapse
if you want, you can keep twrp even after rooting.

Hi Haky 86, for my HUAWEI P8 lite 2017, the build number is PRA-LA1C185B167.
I found firmware PRA-LA1C185B176 at below links, do you think they are trustworthy - will they work on my phone ?
forums.easy-firmware.com/showthread.php?182653-PRA-LA1C185B176-zip
easy-firmware.com/home/browse/file-info/id/99327/

haky 86 said:
This is a simple allow you to learn how to backup and save a copy of your firmware on PC whatever it is like no brand, vodafone etc..
Requirements:
Unlocked bootloader.
Unlocked FRP.
TWRP Recovery, click here.
Steps 1: Disable Encryption
Download the following archive.
Reboot device into fastboot mode and run fastboot flash boot dec_boot.img && fastboot reboot.
Steps 2: Backup Your PRA Firmware
Reboot to fastboot mode.
Run the following command: fastboot flash recovery twrp-3.1.1-2-v2-prague.img && fastboot reboot
Reboot to TWRP -> tab on Backup -> select all partitions -> switch storage to external sd.
Steps 3: Re-enable Encryption
Once done, reboot to fastboot mode.
flash: fastboot flash recovery stock_recovery.img
flash: fastboot flash boot boot.img && fastboot reboot ( always from IMGS archive contents)
Click to expand...
Click to collapse
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?

Hinatasan said:
Hello, I followed all the steps, but this error appears and does not finish creating the backup, is there any solution,Thanks?
Click to expand...
Click to collapse
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.

haky 86 said:
this was possibile only on PRA-LX1C432B161 firmware, they update encryption on newer firmwares that make backup impossible to save.
Click to expand...
Click to collapse
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468

Hinatasan said:
You think it would be possible what they say in this post, but adapted to our PRA-LX1?
https://forum.xda-developers.com/oneplus-5/help/error-255-twrp-t3739468
Click to expand...
Click to collapse
Actually I won't fix nothing, I'm working on emui 8.x source to make newer roms (non treble one)

HELP ME
Good evening need some help to back up the firmware of a Huawei B310s Imei: 869242023527367
serial number: F5S8W17901002756
Thank you

Couldn't install Update fix

if you have any problems with updating just follow this instructions
First of all you need unlocked bootloader
1.Download and install adb and drivers (if you did it then skip this)
2. download stock rom there - https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
(i recommenting to download your current rom version)
3.download ota flasher from here - https://downloadmirror.co/2CVe/mi-a2-OTAFlasher.zip
4.extract ota flasher and .img files to the same folder
5.switch off your phone and go to Fatsboot mode (press power + volume down button for 8sec)
6.connect your phone to pc and double click to 'OTAflasher.bat'
7.wait for finish
8. restart your phone and update it
this method worked for me and i wanted to share it with you guyz
if you need any help lemme know
have good day

You need to unlock critical partitions then only can flash stock rom
Use this command -
fastboot flashing unlock_critical

ckpv5 said:
You need to unlock critical partitions then only can flash stock rom
Use this command -
fastboot flashing unlock_critical
Click to expand...
Click to collapse
but this will earse all my data right?

Yes .. if I remember correctly this unlock_critical will erase data. That's why it is advised to do it right after unlocking bootloader.
BTW .. the OTA Flasher that is linked at item no. 3, also available at originally posted on XDA - https://forum.xda-developers.com/showpost.php?p=78123332&postcount=457
can download without waiting time.

General [X60 PRO+] Chinese variant - Official Stock ROM Collection

V2056A | PD2056 | 5G China variant
- PD2056B_A_1.11.13 HERE Android 11

thats good!
and how can i flash it?
My device is last week broken . is the rom flashable with fastboot? thx mike

How did you broken the device?

You can simply upload zip on device with adb command and flash by using stock recovery mode
adb push .....

I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?

88user88 said:
I tried to flash my patched boot.img (via_magisk) with the MTKROOT V2.5.5 tool. -https://www.ayudaroot.com/root/vivo/como-rotear-los-telefonos-vivo-x60-pro-plus . The first problem was unlocking the bootloader. That did not make the tool. The tool failed .. I unlocked that manually in fastboot mode. After the bootloader was open, I tried the tool for the second time.
That was probably the serious mistake! The tool has transferred the patched boot img. So far everything was o. K. Then I booted to the Recovery Menu to clean the data and cache partition. (Factory Reset). Then restart system. Since then I have a bootloop and it was not possible to boot into recovery mode.
Then I flashed from the Indian Rom the boot and the recovery image.
Now the device booted again in Indian Recovery Mode (English). Then I tried to execute the recovery WLAN update. Unfortunately, the system has found no access points when searched.
!! F *** K !!
The next day I tried to flash the original CN-ROM with the QPST flashtool from https://www.needrom.com/download/vivo-x60-pro-plus/ ..
Here I had problems installing the Qualcomm driver for the EDL download mode or to boot the device in the EDL mode.
Without success!
Finally, I tried to flash all the items of the CN-ROM from Needrom via Fastboot. The Flash order of the items I had from the partition.xml file on the CN-ROM.
But I still have a bootloop ..
No access to the recovery WLAN Update-No networks are displayed ..
Do you have an idea for the EDL download mode?
Click to expand...
Click to collapse
My PC is over adb unautorized, after the Factory reset...

I managed to get this full rom from Recovery, there is a option to download the full last rom and burn. I use another phone with photo google translator to navegate in the menu.

I know this option with the update from the WLAN - but this option is no longer available to me - after the search for a network is completed, no further networks are displayed. He doesn't find any networks.

And the second problem was - I cannot import this Update.zip into the main directory because the PC is unauthorized.

It wasn't just the MTK tool that was wrong.
I think our mistake was you mixed recovery and boot of another Rom. I did that many years ago with Huawei but for me it was a hard brick. Better not mix!

yes i think thatat too. first step now- i try to put the phone in EDL download mode. Then I could try the Qualcomm Flash Tool -. .. But thank you anyway.

with which command did you unlocked the bootloader? I can't find a way.

@88user88 : i wish you the best.
Do you see a way to flash the indian ROM?

Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.

DPMDP said:
with which command did you unlocked the bootloader? I can't find a way.
Click to expand...
Click to collapse
+1

wolfgart said:
V2056A | PĐ2056 | Biến thể 5G Trung Quốc
- PD2056B_A_1.11.13 TẠI ĐÂY Android 11
Click to expand...
Click to collapse
hello i am a new user in vietnam, can you guide me in detail how to install . Thank you very much

I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out.

DPMDP said:
Question was not for me but:
I think i have a way that works. But for that I need the command to unlock the bootloader. Because none of the normal ones works.
Click to expand...
Click to collapse
OK, if we manage to restore my device, I'll give you instructions on how you can unlock your bootloader. then at least I know that in an emergency you also have the option to restore your device.
otherwise it would be too unsafe for me ...
ok?-now you come!

astrofahim said:
I spent almost 5 hrs yesterday tried to flash from CN ROM, Origin OS to Global ROM, FunTouch OS. I used several methods including AFTool, QFIL, and QPST tool. None of them succeed.
AFTool - failed to flash because missing Fastboot batch file in the global firmware.
QFIL - failed to flash because, Qualcomm Driver 9808 not detected.
QPTS - failed to flash because, Qualcomm Driver 9808 not detected.
I like Origin OS but the reason I want to change to FunTouch OS is because Origin OS didn't come with Google Mobile Seevice package. In fact, 'Hey Google' also didn't worked out. YouTube Vanced also always failed to open.
Click to expand...
Click to collapse
same here, my device is iqoo 7 cn origin os i downloaded from android 12 website, failed to upgrade in recovery mode when in hardware check.
both on funtouch os and android 12

Hi, does anyone know where it is I can find this PD2056C_A_1.14.1 firmware
the command menu of the recovery mode of the Chinese version and in Chinese or English

[Recovery] TWRP (Unofficial/Experimental) for Samsung M40

We got our first recovery for Samsung M40 (SM-M405F). This one is ported using Samsung Auto TWRP recovery porter by Team Hovatek
Please try and let everyone know if it works for you or not.
(If you want to do it yourself for any other Android OS version, you can refer to the original Hovatek post.)
You must disable dm_verity before flashing TWRP.
TWRP based on version: 3.5.*
Details of base recovery used for porting:
Source: Extracted from downloaded firmware
Version: Android 11
Build Date: Mon, 12 Apr 2021 07:54:43 +0000
Security Patch Level: 2021-04-01
Product code: INS
PDA: M405FDDU2CUD2
CSC: M405FODM2CUD2
If this works for you, please post here so everyone will know.
If something goes wrong you need and any stock img/file let me know, I will share that too.
Update 1 =>
NOTE: Unfortunately, I can not test this recovery for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Update 2 =>
Instructions for NON-Rooted and Bootloader locked device-
Unlocking Bootloader:
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Disable DM_Verity (Android Verified Boot):
Copy the vbmeta.img (download from attachments) into your adb and fastboot folder
You can now flash the vbmeta.img using fastboot to remove dm_verity from your device
// Enable USB Debugging and enter following commands in CMD/Terminal after connecting device to computer.
adb devices
// You should see your device listed
adb reboot-bootloader
// Device should reboot to bootloader
fastboot devices
// You should see your device listed
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
// OR if the command above doesn't work, try below
fastboot flash vbmeta vbmeta.img
// DONE
////////////////////////////////++++++++++++++++++++++++++////////////////////////////////
Note: For Magisk Rooted devices above steps are not required, as Magisk already patches vbmeta.img and disabled dm_verity (Android Verified Boot)
Flash TWRP with/without Root using Odin
1. Download and install Odin on your PC
2. Download the attached recovery.img, convert it into .tar
3. Reboot to download mode: power off your device and press Volume Up + Volume Down and plug in your device to a PC to boot into download mode.
4. Select recovery.tar under AP_ and Uncheck “Auto Reboot” in Options!
5. Flash the device
6. Now do not power on to System, enter into Recovery/TWRP mode using key combination.
Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
*DONE*
Enjoy TWRP!

Can you tell step by step procedure for flashing twrp in m40.
How to disable dm-verity?

I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.

Shashvatsawar said:
I guess this didn't work in my device.
"reason recovery: error verifying vbmeta image: invalid vbmata header" error is coming.
Click to expand...
Click to collapse
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.

did you already tested it on your device??

rohitrss said:
You must disable dm_verity before flashing TWRP.
Is your device rooted?
How did you flash this TWRP?
Please share your device info.
Click to expand...
Click to collapse
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?

deadinside322 said:
did you already tested it on your device??
Click to expand...
Click to collapse
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.

Thread title and note updated.

Shashvatsawar said:
My Product code : SM-M405FZBDINS
My device is rooted using magisk patch.
I flashed twrp before root using odin.
I didn't disable dm_verity.
How can I disable dm_verity?
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.
Click to expand...
Click to collapse
I tried it But I am not able to boot into recovery then.
It just reboots.

Shashvatsawar said:
I tried it But I am not able to boot into recovery then.
It just reboots.
Click to expand...
Click to collapse
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?

I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know

Akhil137 said:
I unlocked the bootloader, then booted my device to download mode.. change .img file extension to .tar then tried to flashing it using oden and selected recovery.tar in AP slot.. but it's stuck on file analysis.
Any help? Any step I did wrong? Let me know
Click to expand...
Click to collapse
As you have flashed TWRP before root, it failed at verification stage. You need to disable dm_verity, please follow https://forum.hovatek.com/thread-32719.html based on your OS version.
Otherwise, you can flash TWRP after rooting as Magics already disables dm_verity.

rohitrss said:
Did you try key combination or adb command?
Also, could you please share what all have you tried/done so far so I will have better idea?
Click to expand...
Click to collapse
I followed this thread to root my device
https://forum.xda-developers.com/t/root-sm-m405f-galaxy-m40.3951491/
There was no option of dm verity while patching stock rom using magisk.
Though My phone was successfully rooted.
I can't use fastboot as it's not showing my device in devices list ( tried a lot).
Finally I flashed your recovery using odin but after going to recovery mode it rebooted only. For recovery mode I tried key combination first and then a root app after device booted.

Updated post with detailed flashing instructions.

rohitrss said:
Updated post with detailed flashing instructions.
Click to expand...
Click to collapse
did the recovery work for you?

Is there any update?

When i try to go to bootloader, my device always go to download mode. how can i fix this???

rohitrss said:
Unfortunately no, I can not do any testing for few more days as this M40 is the only device that I have and it is also source of internet access for me and my laptop. If this mobile is turned off for any reason I wont have internet access so looking for fixes would be difficult.
But I have rooted some devices before and know how things work so I will help in every possible way if someone stuck at any place while trying this recovery.
Also, if someone confirms this recovery does not work, I am planning to port TWRP from scratch.
Click to expand...
Click to collapse
Bro, I am going to use twrp in my main phone M40.
And I don't care if it gets bricked :>

How to install GSI ROM on OnePlus n100.

Good morning guys.

bentalebnordine said:
Recently I installed lineage os 11 gsi rom on my OnePlus n100 and I wanted to share this experience with you guys :
Click to expand...
Click to collapse
- First you need to download This mini sdk
one_plus_nord_sdk.zip
drive.google.com
It is necessary for the cmd commands to work
- you need also to install the drivers , just go to
Universal ADB Drivers
OnePlus-USB-Drivers.zip
drive.google.com
You need to install both drivers clockworkmod and one plus drivers.
- To unlock the bootloader of your oneplus device just connect it to a Windows computer with USB debugging on and run the following commands from the mini sdk folder that just downloaded
adb devices
Then check your device for confirmation. Then
adb reboot bootloader
Then run the command
fastboot oem unlock
A factory screen will pop-up asking for confirmation, you need to confirm using the volume buttons and the power button.
The phone will reboot into recovery and wipe the data. Please do not interrupt this process or the device will not boot anymore.
So just be patient until the phone finishes booting and set it up and turn the USB debugging on.
bentalebnordine said:
2: after that you need to boot your device on fastboot mode, simply by running the code
adb reboot bootloader
And run the command
fastboot --disable-verity flash vbmeta vbmeta.img
Then this command
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
Note that you need to flash both files only once, unless you returned to stock rom.
bentalebnordine said:
Then run the command
fastboot reboot fastboot
Then flash the system of your choice by visiting
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
Note that the file downloaded would be in Xz format, so you need to extract it with 7zip or beanzip and put it on sdk folder.
The file downloaded must end with arm64_bvS.img. Xz and not with arm64_avS.img.xz (bvS not avS) or the phone will stuck on bootloop.
And the file extracted must not exceed 2.6 gB or you will get an error of resizing the system partition.
After flashing the system with the command
fastboot flash system <your system >.img
Run the command
fastboot -w
And finely the command
fastboot reboot
And good luck.
Click to expand...
Click to collapse
If you updated to Android 11 Oxygen OS 11 you need to switch slots by running the command
fastboot --set-active=a
Because android 11 were installed in the b slot.
If you have a problem booting into fastboot mode try extracting the mini sdk provided in the tmp folder on your desktop computer.
The working Android versions are 10,11,12. Now I am running Resurrection Remix ROM android 10 just amazing
NAMING
Some information you should know about knowing what type of gsi it is
<ARCH>_xyZ
<ARCH> can either be arm, a64 (arm32_binder64) or arm64
x can either be a or b
y can either be v, o, g or f
Z can be N or S
b = a/b
a = a-only
g = gapps
o = gapps-go
v = vanilla (no gapps included)
f = floss (free & open source apps instead gapps)
N = no superuser
S = superuser included
Z = dynamic superuser included
-lite = for VNDK Lite vendors (also can help with broken camera even on normal VNDK vendors)
so in most common example "arm64_avZ" is ARM64 A-only vanilla with dynamic superuser
you can simply look to the attached text file.

I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.

joegib said:
I am unable to flash any of the .bvs.img gsi files on a Metropcs (11) phone -- BE2015 following the guide. Bootloader is unlocked.
Any help is appreciated.
Click to expand...
Click to collapse
Me I have a BE2013 variant and I was able to flash it with gsi roms using just this guide. I should mention that I am not an expert on rom development.

If I am not mistaken, the BE2013 variant is the global factory unlocked. If so, then maybe these carrier devices will not work with your excellent guide. That being said, I was able to get the DSU to work fine -- AOSP 12.

If you're on the Metro firmware it's a bit tricky. You'll most likely have to still be running Android 10 but you can decrypt the data partition and mount system r/w. After you've accomplished that then it's a piece of cake. Follow this thread, I've been able to remount the system partition read/write on both my Google Pixel running Android 11 and Metro Firmware of OnePlus Nord n100. https://forum.xda-developers.com/t/...-superrw-featuring-makerw-read-write.4247311/

Is GSI for nord n100 updated?

VPH20 said:
Is GSI for nord n100 updated?
Click to expand...
Click to collapse
I'm running Project Arcana Android 12 GSI on my n100 without any issues. I've flashed serval different GSI ROMS but it's by far the best. There's a few things you need to know to successfully flash it but if the steps are followed exactly it's not a problem at all. Here are a few screenshots. It passes safety net basically out the gate with Magisk installed. You'll definitely have to flash the Global firmware to the Metro variant If you happen to be on that version. Luckily, if that's the case someone has already created a modified MSM flash tool that works without any other modifications.
{
"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"
}

Thanks, the link please.

bentalebnordine said:
Thanks, the link please.
Click to expand...
Click to collapse
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz

sdflowers32 said:
There's no verified instructions on this but I took the liberty to upload the necessary files to my Google drive that I used to successfully flash this GSI. First and foremost you'll need to revert back to the global stock firmware 10.5.5 using the msm tool. If you're on the the European firmware then I'm not sure if this will work for you or not and it definitely won't work on the Metropcs version but if you happen to be on the Metro version then you can flash the Global firmware to that device which is what I did. Once you're on stock 10.5.5 enable debugging and oem unlock in developer options and reboot to bootloader. If your bootloader isn't already unlocked enter the command fastboot flashing unlock_critical and use the volume keys to select unlock the bootloader. Your device will be wiped. Wait for the system to reboot then go back into developer options and enable debugging again. Once again reboot to the bootloader. Once there enter the command fastboot -w and wait for it to finish. Once it's complete enter fastboot reboot fastboot and wait to enter fastbootd mode. Use the vendor.img that's included in the zip file I have linked and enter fastboot flash vendor_a (name of vendor).img. Once it's complete enter fastboot reboot bootloader. Once you're back into the bootloader interface enter fastboot -w and wait for it to complete. Then with the twrp file I've supplied enter fastboot boot twrp10.img to boot to recovery (Don't flash only boot!!) When you enter recovery choose wipe, then format data and type yes. Reboot to the bootloader once again. Enter fastboot reboot fastboot and wait to enter fastbootd mode. Once there enter fastboot flash product_a product_gsi.img. Then enter fastboot erase system_a. Next enter fastboot resize-logical-partition system_a 4210000000. Once that's complete enter fastboot reboot bootloader. Once you're in the bootloader enter fastboot -w once again. Once complete boot back to twrp with fastboot boot twrp10.img. This is when you'll flash the GSI and it has to be loaded on your sdcard. Flash it to the system partition and reboot to the bootloader once it's complete. Your next move is important if you want it to boot. Again with the images I've supplied enter fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img then fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img. Now you can reboot to the system. For some reason twrp won't boot anymore once this GSI is flashed so I've also included the stock boot.img you can patch with Magisk and flash via fastboot to root and pass safety net.
Oneplus_files.zip
drive.google.com
https://xiaomemeindex.com/treble/Arcana/20220226/ProjectArcana_v402-arm64-bgS_20220226.img.xz
Click to expand...
Click to collapse
Thank you very much my friend for the help, I have the E2013 and it worked.

Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
Click to expand...
Click to collapse
Exactly.

bentalebnordine said:
Exactly.
Click to expand...
Click to collapse
I sent you a PM if that's okay please and thank you.

sdflowers32 said:
Awesome, I'm glad to hear it boots on the E2013. If you're on the the Metro version as I was it's difficult but not impossible. Unfortunately for myself I had no guide, just a few pieces of information I picked up here and there that I was able to bundle together into one long process. The great thing about OnePlus is the MSM flash tool. I've flashed firmware from just about every Android manufacturer but it's by far the easiest if you happen to brick your device. So easy even someone with no prior experience wouldn't have an issue using it.
I'd also like to mention that if you're into theming your device, the infamous dev kdragOn has developed an app called repainter that's quite amazing and works really well on this device and ROM. I'm in no way affiliated with him or the advertisement of his app but just making an honest recommendation
Click to expand...
Click to collapse
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
Go to this page you will find extra details about how to resize system partition and install larger system files.
https://forum.xda-developers.com/conversations/gsi-roms.14701453/#convMessage-15038845

Okay I just want to say thank you first and foremost to @bentalebnordine and @sdflowers32 because without your both helpful and informative guides I would have taken much longer lol! I can get a guide going completely. With the above guide that sdflowers posted make sure you follow this to a T or you won't boot trust me. Also the GSI images that work best for our device must be the following
system-arm64-ab-img.xz and they will work with no issues I'll put up a cleaned up guide as well to hopefully help others but again this is all only possible with the help of you two first and foremost so thank you!

Markus214 said:
Can I ask a stupid question most likely. I have the BE2015 variant and I followed your instructions to a T and they worked so thank you very much for that.
However if I wish to use another ROM as myself I personally like Android 10 which ROM would you recommend works with our devices? I tried using LineageOS but the Gapps file does not want to install each time I get error.
Edit: Might be time I update my signature lol
Click to expand...
Click to collapse
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.

sdflowers32 said:
DOT (Droid on Time) is another GSI that works beautifully on this device but it's Android 11. I personally haven't tried any 10 GSI'S. If you want to update to 11 through stock firmware I already have a DOT super.img I repacked that I'm pretty sure can be flashed without issues with the Android 11 twrp for this device and I'm certain can be flashed via fastbootd mode. Other than project arcana it's the only one I've been impressed with and I've flashed 7 or 8. At least 3 of them I could never get to completely boot after trying every trick of the trade. Arcana is by far the best but DOT runs a tight race. If interested let me know and I'll upload the super.img. I packed it myself so if I ever get bored and just want to go back it would be a much less painless process to flash and I've tested it and it works perfectly.
Click to expand...
Click to collapse
Thank you very much that would be great! I just downloaded DOT to try it out. I used it before on my 7T and it's great. I just am stubborn I'll say where I like Android 10 the most and 11 not bad but 12 I just don't like the interface and magisk 24 especially for what I do with the phones. I ideally would love to be able to use lineage but when it came time to flash Gapps I kept getting storage error even with resizing. I just want to again say seriously thank you so much without your guide I'd still be screwed

Instructions for flashing DOT GSI
(Start by flashing to stock 10.5.5 with the MSM tool for the device and follow the previous instructions to unlock the bootloader but only to this point)
I decided to edit this because it's been so long since I've removed encryption on this device I completely left out the steps to do so which are imperative. It's much easier to remove encryption on Android 10 than 11 with this device but as far as I know this is the sure fire way to flash an Android 11 GSI on this device. Maybe it can be flashed from 10 but I can't guarantee it as I can with this so here is the revised instructions.
1. Use the MSM tool to revert back to stock and unlock the bootloader
2. Upgrade OTA as far as you can up until version 11.0.4 (Most likely you'll have to use the file I've included in the attachment and perform a local upgrade by placing the zip file in your internal storage to get on this version) Remember this is only for the global firmware but it can be cross flashed with a modded MSM tool.
3. Once you're on 11.0.4 you'll need to format an SD card to exfat which can be done easily with windows because you're going to have to place the super.img on it to be flashed in TWRP. Android supports exfat but for reasons beyond my understanding when you purchase an SD card for Android it comes formatted as fat32 which has a 4 gig limitation.
4. Unzip the 11.0.4 super.img and load it on the SD card along with Magisk.apk. You can either rename the extension from Magisk.apk to Magisk.zip and keep just the one file on your card or copy it and place them both on but nevertheless you'll need the zip file to flash in TWRP after flashing the super partition. Use the TWRP11.img provided in this devices thread and have it placed in your platform-tools folder on PC. Reboot to the bootloader and enter fastboot boot twrp11.img (Or whatever the name of the image happens to be). Once you're in recovery choose wipe, format data and enter yes. Go back and choose install image then select the super11.0.4.img and flash to the super partition. Go back and flash Magisk.zip.
5. Now boot to the bootloader and with the volume keys enter stock recovery.
6. Wipe Data, Cache and System and reboot. I usually reboot back to the bootloader then boot TWRP again just to make sure I can mount all partitions assuring that the device is decrypted.
7. Now all you have to do is place the DOT_SUPER.img on your SD just as you previously did, wipe and format data, then flash it to the super partition just as you did with the stock 11.0.4 super. The boot image is provided as well but I wouldn't advise uninstalling Magisk. Upgrade if you like but it may not boot if you flash the stock boot.img
DOT Files