Database Develop

[EDL][A2017/A2017U] Emergency DL Mode TWRP + Unlock + Upgrade

{
"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"
}
INTRODUCTION
I'm providing a set of files that allow you to unlock your bootloader or recover from the closest thing you can get to a hard brick.
MiFlash is capable of flashing anything to your phone while it is in Emergency Download mode.
Yes, this is voodoo magic and it works! Recover from any and all bricks! Some might call it necromancy.
However, it can be also be used even if the device is perfectly alright to simplify upgrading procedures and make ROM flashing fairly painless.
This is for A2017U (North America) and A2017 (China) models only! Do not attempt this on A2017G.
INSTRUCTIONS
If you are flashing TWRP on a locked bootloader, you must first enable OEM unlocking on your device.
You can do this by navigating to Settings -> About phone -> Tap "Build number" 7 times.
Now navigate to Settings -> Advanced settings -> Developer options -> Enable "OEM unlocking".
Follow the steps below with the FASTBOOT_UNLOCK package first, then go into fastboot mode and use the
"fastboot oem unlock" command to unlock (and wipe) your device. Download adb and fastboot below.
Install the Qualcomm QUSB_BULK drivers from below.
You should be able to simply extract them, then right click qcser.inf and press Install.
If you don't have this option, then use devmgmt.msc (Device Manager) to update the driver after entering EDL mode by
selecting manual install and browsing to the qcser.inf file there.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Now install MiFlash (download below).
Open MiFlash and use the [select] button to select the A2017U_*_EDL folder package that you wish to flash.
Boot into EDL mode. (hold Volume Up + Volume Down + Power until you're stuck on a black screen)
Now just hit [flash] - watch the progress bars move and wait for the device row to turn green with flash complete!
If you are flashing TWRP, use the [Power] + [Volume Up] key combo to exit EDL mode and enter recovery. Release the keys when you see the ZTE logo.
You must have an unlocked bootloader to enter TWRP!
If the flash fails or is unable to communicate with the device, use the [Power] + [Volume Up] + [Volume Down] key combo to restart EDL mode.
Release the keys after 5 seconds then wait another 5 seconds before using the [refresh] or [flash] buttons on MiFlash.
EDL PACKAGES
FASTBOOT_UNLOCK
This will unlock all fastboot operations, including OEM unlock and fastboot boot/flash.
WARNING: Unlocking your bootloader will erase all userdata on the device! Your device will be completely reset to factory defaults!
Click here to download! (ZIP, 195.8 KiB)
B29_TWRP (Marshmallow 6.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B29 boot stack.
Click here to download! (ZIP, 59.4 MiB)
B15-NEW_TWRP (Nougat 7.0)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B15-NEW boot stack.
Click here to download! (ZIP, 60.6 MiB)
B15-NEW_FULL (Nougat 7.0)
This will install the entirety of the B15-NEW firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
B19-NOUGAT_TWRP (Nougat 7.1.1)
This will install TWRP 3.0.4-1 and unlock fastboot operations while restoring B19-NOUGAT boot stack.
Click here to download! (ZIP, 61.0 MiB)
B19-NOUGAT_FULL (Nougat 7.1.1)
This will install the entirety of the B19-NOUGAT firmware and boot stack, including signed OEM system and boot. OTA capable and unlocks fastboot operations.
Click here to download! (ZIP, 2.4 GiB)
TOOLS
Xiaomi MiFlash Installer
Version: 2016.08.30.0
Click here to download! (MSI, 31.0 MiB)
Qualcomm QUSB_BULK Drivers
Version: 2.1.1.0 (2014-01-25)
WHQL signed.
Once the drivers are installed, your device should be recognized as a COM port called "Qualcomm HS-USB QDLoader 9008".
Click here to download! (ZIP, 2.7 MiB)
ADB & Fastboot
Visit the SDK Platform Tools download page
Using this, you should safely be able to recover from any brick!
Once in TWRP, you can flash a full OTA or restore your backups and be on your way.
It is tested and working on Windows 10 64-bit.
All zips are signed with Android SignApk and can be verified with TWRP. (they won't install, just say it's not a valid zip after verifying)
A2017 (China) can use this to convert their phone to A2017U if they want. DO NOT flash on A2017G.
POSSIBLE ISSUES & SOLUTIONS
OTA update zips may fail in stock recovery even after flashing FULL EDL packages. This is because MiFlash does not erase blocks before writing the system image. You can run this command from TWRP terminal or adb shell to erase system partition before flashing the EDL package:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/system bs=272144
Once this is done, OTA zips should succeed in stock recovery after flashing a FULL EDL package.
CREDITS
This was based on the A2017 B07 EDL zip provided by @tenfar at this XDA thread.
HISTORY
2017-04-10 - Added B19-NOUGAT FULL and TWRP package
2017-02-11 - Added B15-NEW FULL signed OTA capable package
2017-02-11 - Added fastboot operation unlock package
2017-02-11 - Separated MiFlash, Qualcomm QUSB_BULK Driver, and EDL packages, removed 7z archives
2017-02-09 - Added B15-NEW TWRP package
2017-02-09 - Added B29 TWRP package

Any idea if this will work with Nougat or not?

neo4uo said:
Any idea if this will work with Nougat or not?
Click to expand...
Click to collapse
It will work on Nougat, however, you will end up on B29 bootloader. You'll need to flash B29 full and upgrade again.
I am having some weird issues with Nougat boot stack flashing + TWRP so I'll hold off on posting a B15-NEW version of this for now.
Update: You can now flash the B15-NEW TWRP package instead.

@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.

Situation: A2017U full stock in Nougat no unlocked bootloader, no root
Want to: Install LOS because i HATE this bullsh... called MIFAidonotknowWTF
Can i use this procedure to do that?
Thanks a LOT

So basically, MiFlash just lets you firehose in any file to a QualComm device from EDL mode? That's pretty handy.

I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.

Snaptraks said:
I assume the TWRP image will only work on an unlocked bootloader device, right?
Then again, I don't see why a locked bootloader device would get in such a bricked state in the first place.
Click to expand...
Click to collapse
It is softbrickable by adb commands... I have one device in boot loop.

trying to wrap my head around this whole bootstack/fastboot issue we have with the a7.
So in theory one could use this tool and then unlock (or just have working fastboot) directly from b15?
Then download the bootstack from los thread and be good to go? Or would that bork fastboot again...
I think I am currently running b20 bootstack on b15 by flashing draken's unlock zip without issue (that I know of) but am considering flashing the N version from los thread.

This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.

KwesiJnr said:
This thing works, guys! OMGOMGOMG! :highfive::laugh:
My device was in a "heavily bricked" state. No LED light on connect and permanent EDL mode. I am now fully functional after trying EVERYTHING but this.
Click to expand...
Click to collapse
Have fun! Nougat images are now up!

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help

Altomugriento said:
Can you help me to do this from full stock nougat?
1) Enable "OEM UNLOCKING" under Developer Options
2) Flash with MIflash the "A2017U_B15-NEW_TWRP_EDL"
2) reboot to recovery (vol - and power)
3) fastboot oem unlock
4) reboot to TWRP
5) Flash LineajeOS and Gapps
thanks for your help
Click to expand...
Click to collapse
step 2.5) reboot to bootloader from recovery
step 4) wipe system in twrp
step 6) use the [Format Data] button on wipe page of twrp (lineageOS may not be compatible with your current encryption, this will wipe all your settings and internal storage)
and yes that's everything, I believe.

Sticky. Nuff said.
Dev is finally taking off on this phone, thanks to literally 4 or 5 key people. I was afraid I'd made a mistake purchasing instead of O+3, but has worked out well.
Thanks for all your help in your free time.

DrakenFX said:
@jcadduono
N BootStack from LineageOS thread can be use for this if you want to give a try, instead of B29.
The stack is from a zip N file (I can't disclose right now) and is full N stack, minus Boot and System of course.
P.S. be advice that " keymaster.mbn " file flashes to " xlbbak " partition. Or just check the updater_script for N changes.
Click to expand...
Click to collapse
Thanks buddy, that keymaster -> xblbak appears to have been my issue! So illogical.
I compiled applypatch and used that to apply the B29_TO_B15-NEW .p files to my B29 binaries so they should be nice and exact. (sha1 matches from updater-script)
I can provide a full B15-NEW verity/OTA update friendly package if somebody wants. Just let me know.

Flash Done.
But i can't join to TWRP, it just turn it self off.

Eroticus said:
Flash Done.
But i can't join to TWRP, it just turn it self off.
Click to expand...
Click to collapse
If you are not unlocked you now need to go to fastboot mode and unlock before you can enter TWRP.
If you just mean the screen is still black, you have to hold volume + power up after flashing until it starts up, then let go when you see the ZTE logo.

Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock, rooted and fastboot working N B15 build?
Thanks

khangozzy said:
Hi @jcadduono
I'm about to get my A7 (A2017U version) in few days. Would you please advise which method/process/steps is the best to upgrade to stock and rooted N B15 build?
Thanks
Click to expand...
Click to collapse
Look up a couple posts.

jcadduono said:
Have fun! Nougat images are now up!
Click to expand...
Click to collapse
Because it had been reported that this was impossible, or at least very difficult, I wanted to clarify whether this means people with locked bootloader running N can now unlock and install TWRP?

[GUIDE] [UNBRICK] [BACK_TO_STOCK] Flash Stock ROM - Relock Bootloader - Remove TWRP

Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1810.334[/U] on primary device. Also I will try to help out in case of issues.
This GUIDE is useful to achieve following,
Unbrick your device
Flash Stock Rom
Remove TWRP / flash stock recovery
Lock the bootloader
Enable OTA ( if you have unlocked using Asus official bootloader unlock tool then you will not get OTA )
Files Needed are,
Fastboot Firmware :
WW-15.2016.1810.334 AFH (md5 : fd39c734cbe2722c0cea02f09cba528e) OR
WW-15.2016.1810.337 AndroidHost (md5 : 84197c90f2c913f5cd18dd06b9d82c4b)
Updates : Latest Update (Optional for all, mandatory only if you have UNLOCKED officially)
Steps to be followed,
Charge your device to more than 50%.
Remove all password protections - select SWIPE to unlock.
Create a new folder which does not have any spaces in folder name as well as folder path.
Download Fastboot Firmware and Drivers to above folder & extract both zips which will give you 2 new folders .. one for each.
Connect device to Computer and Install drivers based on your system. [ General process, go to windows Device manager --> Select Android device --> right click and select update driver --> browse to base path where the drivers are extracted and select it .. wait for windows to finish and show success message. ]
Enable USB debugging. Connect device to PC and open shell in ADB. Type adb devices it should list your phone.
You should be able to see results just like below before you proceed,
{
"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"
}
Boot into fastboot mode & connect to PC. [ For fastboot mode, turn the device off then Press power+Volume Up until you see Asus logo OR use command adb reboot bootloader as shown in above screenshot. ]
Open firmware folder and click on flashall_AFT.cmd & wait for the device to restart on its own. Takes about 5 min so be patient.
Setup your device.
You will have System update notification after that. Install OTA and enjoy.
ALTERNATE
You can download the recovery firmware from above links and put it in Internal Storage (DO NOT keep it inside any folder.).
You will get system update file detected message. Click on it to update.
If you want to uninstall few of the stock apps without ROOT access then refer to my other post HERE.

.A.V.i.n.a.S.h. said:
This GUIDE is useful to achieve following,
Unbrick your device
Flash Stock Rom
Remove TWRP / flash stock recovery
Lock the bootloader
Enable OTA ( if you have unlocked using Asus official bootloader unlock tool then you will not get OTA )
Downgrade firmware
Applicable for,
Model : ZB601KL (try on ZB602KL on your own risk)
ROM : Does not matter - Stock or Custom (AEX,Lineage etc.)
Recovery: Stock / TWRP
Bootloader State : Locked / Unlocked
Root : Rooted / Non-rooted users
Files Needed are,
Firmware : Uploading on AFH. At 73% right now so be patient
Drivers : Windows Drivers AFH
Prerequisites,
Make backup of all your apps and data. Internal Storage will be formatted. External will be safe but better to back it up as well.
Make a mind to take full responsibility of your actions. I have tested the solution on my personal device which was UNOFFICIALLY unlocked. But the risk is entirely yours if you follow the guide.
Make sure you validate checksum of all downloaded files before proceeding.
Steps to be followed,
Charge your device to more than 50%.
Download Firmware and Drivers & extract both zips which will give you 2 folders .. one for each.
Boot into fastboot mode & connect to PC. [ For fastboot mode, turn the device off then Press power+Volume Up until you see Asus logo. ]
Install drivers based on your system. [ General process, go to windows Device manager --> Select device --> right click and select update driver --> browse to base path where the drivers are extracted and select it .. wait for windows to finish and show success message. ]
Open firmware folder and click on flashall_AFT.bat & wait for the device to restart on its own. Takes about 5 min so be patient.
Setup your device. You will have System update notification after that. Install OTA and enjoy.
If you want to uninstall few of the stock apps without ROOT access then refer to my other post here.
Follow the spirit of XDA and hit THANKS if this actually helps you, so that future users also know that the method works.
Click to expand...
Click to collapse
U mean after flashing, the device bootloader gets locked again assuming it was unlocked initially (unofficially) ??

jide1 said:
U mean after flashing, the device bootloader gets locked again assuming it was unlocked initially (unofficially) ??
Click to expand...
Click to collapse
Yes .. you will have stock ROM + stock Recovery + Locked device + OTA ( if unlocked unofficially)

Not working on new firmware kindly see my other post for relocking bootloader. I have also replied to you.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
i am going to create a detail process guide soon.

myapky said:
Not working on new firmware kindly see my other post for relocking bootloader. I have also replied to you.
---------- Post added at 11:59 AM ---------- Previous post was at 11:58 AM ----------
i am going to create a detail process guide soon.
Click to expand...
Click to collapse
I was on OPM1.WW_Phone-14.2016.1804.305-20180521 then unlocked bootloader unofficially. Installed AEX rom. Tested it for 4 days.
Reverted with this method to 247 and updated again to 305. So it works on latest formware.
And if you do a compare of flashall_AFT.bat and unlock.bat (or relock.bat) the commands are one and the same. Partial code of flashall_AFT.bat is used for lock/unlock process. flashall_AFT.bat just have additional commnds to reflash recovery, system and other partitions.
Please create the guide .. at last we want a working process to revert back.
User will have success with at least one of the process

MY PROCESS WORK 100% FOR RELOCK BOOTLOADER TESTED !!
CURRENT FIRMWARE : OPM1.WW_Phone-14.2016.1804.305-20180521
AFTER UNLOCK BOOTLOADER DO THE FOLLOWING :
ASUS DRIVERS : FROM HERE https://androidfilehost.com/?fid=818222786056030820
FIRMWARE : DOWNLOAD CSC FACTORY IMAGE FROM HERE https://androidfilehost.com/?fid=962339331458995708. ZB610KL INDIAN VERSION.
EXTRACT THE ZIP FILE
AND EXTRACT RECOVERY.IMG FILE -(52MB) APPROX. ( FOR RECEIVING OTA)
FLASH IT WITH COMMAND : fastboot flash recovery recovery.img
1) Download Zenfone_Max_M1_Pro_Relock.zip and extract it to a folder on your desktop.
2) Power off your phone. Then press Power and Volume + key together, to boot into fastboot mode.
3) Connect your Asus Zenfone Max Pro M1 to the PC using a USB cable.
4) Windows will now automatically detect the device and start installing the fastboot drivers for it. If not, download and install these ASUS drivers.
5) Open the directory where you extracted the file from #1.
6) In that directory, open a file named relock_bl.cmd
7) A Command (CMD) prompt will do the rest of the work for you.
Let the phone restart.
8) It will then erase all the data on your phone (excluding Micro SD card).
9) Now the phone won’t show the “bootloader unlocked” warning that was displayed before you relocked the bootloader.
You have successfully relocked the bootloader.
REMEMBER : LOCKED BOOTLOADER SHOWS = CSC FASTBOOT MODE ( TO VERIFY IF LOCKED OR NOT)
UNLOCKED BOOTLOADER SHOWS = FASTBOOT MODE AND WARNING WHILE BOOTING THE PHONE
---------- Post added at 12:42 PM ---------- Previous post was at 12:41 PM ----------
.A.V.i.n.a.S.h. said:
I was on OPM1.WW_Phone-14.2016.1804.305-20180521 then unlocked bootloader unofficially. Installed AEX rom. Tested it for 4 days.
Reverted with this method to 247 and updated again to 305. So it works on latest formware.
And if you do a compare of flashall_AFT.bat and unlock.bat (or relock.bat) the commands are one and the same. Partial code of flashall_AFT.bat is used for lock/unlock process. flashall_AFT.bat just have additional commnds to reflash recovery, system and other partitions.
Please create the guide .. at last we want a working process to revert back.
User will have success with at least one of the process
Click to expand...
Click to collapse
I get your process, first downgrade then upgrade to latest firmware, by this stock recovery is installed with bootloader locked. then update to latest firmware, but this process doesnt work on some phone as mine another guide i have posted it works and easy method if anyone knows about adb and fastboot.

How to know our device is ZB601/ZB602 ?
Greetings

gusbalaa said:
How to know our device is ZB601/ZB602 ?
Greetings
Click to expand...
Click to collapse
ASUS ZENFONE MAX PRO M1 - INDIAN VERSION IS ZB601KL ( PURCHASED FROM FLIPKART ) -ALL PURCHASED IN INDIA WITH VALID INDIAN BILL FOR WARRANTY.
ASUS ZENFONE MAX PRO M1 - INDONESIAN VERSION / GLOBAL VERSION IS ZB602KL (INTERNATIONAL WARRANTY)
REFER BELOW LINKS :
INDIAN SUPPORT SITE ASUS :https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
INDONESIAN / GLOBAL SUPPORT SITE ASUS : https://www.asus.com/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
---------- Post added at 06:03 PM ---------- Previous post was at 05:46 PM ----------
CHECK BOOTLOADER LOCKED OR NOT VIA ADB FASTBOOT METHOD (CMD) AND ALSO CHECK DEVICE & BOOTLOADER VERSION
IN FASTBOOT TYPE :
fastboot devices
fastboot oem device-info
RESULTS : AFTER LOCKED BOOTLOADER
#SN NUMBER fastboot
VERIFY MODE - TRUE
DEVICE UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
DEVICE CRITICAL UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
CHARGER SCREEN ENABLED - TRUE
BOOTLOADER VERSION - ZB601KL (INDIAN VERSION) -0x01
OKAY
FINISHED

myapky said:
ASUS ZENFONE MAX PRO M1 - INDIAN VERSION IS ZB601KL ( PURCHASED FROM FLIPKART ) -ALL PURCHASED IN INDIA WITH VALID INDIAN BILL FOR WARRANTY.
ASUS ZENFONE MAX PRO M1 - INDONESIAN VERSION / GLOBAL VERSION IS ZB602KL (INTERNATIONAL WARRANTY)
REFER BELOW LINKS :
INDIAN SUPPORT SITE ASUS :https://www.asus.com/in/Phone/ZenFone-Max-Pro-ZB601KL/HelpDesk_Download/
INDONESIAN / GLOBAL SUPPORT SITE ASUS : https://www.asus.com/Phone/ZenFone-Max-Pro-ZB602KL/HelpDesk_BIOS/
---------- Post added at 06:03 PM ---------- Previous post was at 05:46 PM ----------
CHECK BOOTLOADER LOCKED OR NOT VIA ADB FASTBOOT METHOD (CMD) AND ALSO CHECK DEVICE & BOOTLOADER VERSION
IN FASTBOOT TYPE :
fastboot devices
fastboot oem device-info
RESULTS : AFTER LOCKED BOOTLOADER
#SN NUMBER fastboot
VERIFY MODE - TRUE
DEVICE UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
DEVICE CRITICAL UNLOCKED - FALSE (BL LOCKED), TRUE (BL UNLOCKED)
CHARGER SCREEN ENABLED - TRUE
BOOTLOADER VERSION - ZB601KL (INDIAN VERSION) -0x01
OKAY
FINISHED
Click to expand...
Click to collapse
Thanks. I have Indonesian version.
Got it

Will these methods work with official Unlocking also?
Thank you

atf2m4 said:
will these methods work with official unlocking also?
Thank you
Click to expand...
Click to collapse
not tested,
but better to use unofficial method to unlock as : If u unlock through official method service support team, they have a count of imei & serial number (record) of ur phone which is unlocked , so u might lose warranty by using official method so better to try unofficial method.

Check your version via ADB
gusbalaa said:
How to know our device is ZB601/ZB602 ?
Greetings
Click to expand...
Click to collapse
Enable USB debugging
connect to PC and type "adb devices" -- you will get ID from here
Type adb -s <id from last step> shell getprop | grep ro.product.device

.A.V.i.n.a.S.h. said:
Enable USB debugging
connect to PC and type "adb devices" -- you will get ID from here
Type adb -s <id from last step> shell getprop | grep ro.product.device
Click to expand...
Click to collapse
Thanks, i will try and report later.

I have a few questions
1.Will it remove the bootloader unlocked warning during boot
2.Can we do this step over a newer version of stock rom
3.do we have to unroot before flashing
4.ZB601KL is indian version or Indonesian

pranavsree00 said:
I have a few questions
1.Will it remove the bootloader unlocked warning during boot
2.Can we do this step over a newer version of stock rom
3.do we have to unroot before flashing
4.ZB601KL is indian version or Indonesian
Click to expand...
Click to collapse
Yes
I did it today on v305 so yes .. it works .. just remember to enable usb debugging & check device is detected in ADB & fastboot as well.
Commands to check device -
adb devices
fastboot devices
Not needed but you can if you feel like it.
601 is INDIAN.

Flashed and flashed successfully great guide ?

not working. getting this messege
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\platform.txt
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\current-slot.txt

himanshu_atrix2 said:
not working. getting this messege
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\platform.txt
FINDSTR: Cannot open max
FINDSTR: Cannot open pro
FINDSTR: Cannot open m1\WW_ZB601KL_14.2016.1802.247_20180419_AFT\\current-slot.txt
Click to expand...
Click to collapse
Please keep the files in the path which does not have spaces.
If you have a folder named max pro m1 then rename it to MaxProM1.
Also before clicking on flashall_AFT.bat check that device is detected in fastboot mode by fastboot devices command.
I think the command line arguments are not working due to whitespaces in directory/folder name.

latest indian ota WW-14.2016.1804.305 showing error
rs
sir
i unlocked bootloader official and after two day get back to stock rom because i unlocked it official i got not ota updates but i flash update manually one ota is (WW-14.2016.1804.252)sucessfully update, one which is latest(WW-14.2016.1804.305) is showing error on the time while phone reboot to flast update Also The latest update file is not extract on pc
??
???

.A.V.i.n.a.S.h. said:
Please keep the files in the path which does not have spaces.
If you have a folder named max pro m1 then rename it to MaxProM1.
Also before clicking on flashall_AFT.bat check that device is detected in fastboot mode by fastboot devices command.
I think the command line arguments are not working due to whitespaces in directory/folder name.
Click to expand...
Click to collapse
thanks. did what you said. it started but stuck here
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is build-type
--------------------------------
begin to flash partition xbl
target didn't report max-download-size
sending 'xbl' (2802 KB)...
FAILED (remote: unknown command)
finished. total time: 0.002s
done
--------------------------------
--------------------------------
begin to flash partition xblbak
target didn't report max-download-size
sending 'xblbak' (2802 KB)...

REALME C11 stuck in bootloop after flashing magisk.zip through TWRP recovery

I wanted to root my realme c11 rmx2185 so I unlocked the bootloader, flashed twrp recovery and then after flashing magisk.zip and selecting the reboot option it got stuck in boot loop. Now all I can do is to open the bootloader mode and nothing else otherwise it will keep rebooting again and again. If anyone can help me out I will be very grateful. Thank you.

Please answer the following questions
• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
• Did you flash a magisk patched boot.img or a magisk installer?
• Did you do anything else before flashing Magisk and before the incident happened?
Please answer these so I can be able to help you.

• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
RMX2185_11_A.93
• Did you flash a magisk patched boot.img or a magisk installer?
I downloaded magisk.zip and flashed it through TWRP custom recovery
• Did you do anything else before flashing Magisk and before the incident happened?
I unlocked the bootloader which cleared all the data on my phone ---> flashed TWRP.img
Before this incident my phone was absolutely in default condition.
When I asked this question my bootloader was unlocked but now I have locked it and all i can do is to press the power button to see the bootlooping. Can you help me out from here?
I locked the bootloader as my phone was in warranty so I thought it would be better to get it fixed by the company itself , but since my city has been locked down due to the covid situation, my phone is still with me unrepaired .
Now I can't even get to the bootloader mode by pressing buttons .
I wanted to root my device and I followed exactly what was given on this website > https://safeboxguide.com/how-to-root-realme-c11/

Sorry, wrong quote!

skund singh said:
I wanted to root my realme c11 rmx2185 so I unlocked the bootloader, flashed twrp recovery and then after flashing magisk.zip and selecting the reboot option it got stuck in boot loop. Now all I can do is to open the bootloader mode and nothing else otherwise it will keep rebooting again and again. If anyone can help me out I will be very grateful. Thank you.
Click to expand...
Click to collapse
1st, what do you mean by "open the bootloader mode" ? If what you mean is you can boot the device into fastboot mode ( using hard keys or else ) then the solution is quite easy. Just take the stock boot image of A93 ( if you don't have it then u can pm me, I'll send ) then flash into the device using follow commands :
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash boot boota93.img
- fastboot reboot
( remember to use patched vbmeta.img )
Your device will boot normal again.
2nd, from A87, the devs of Realmeme did something with the code so that if directly flashing magisk from custom recovery may random cause bootloop. So, my suggestion is to use fastboot command and flash the patched boot images like old times.

skund singh said:
• What software version (e.g. RMX2185_11_A.87 etc.) were you using?
RMX2185_11_A.93
• Did you flash a magisk patched boot.img or a magisk installer?
I downloaded magisk.zip and flashed it through TWRP custom recovery
• Did you do anything else before flashing Magisk and before the incident happened?
I unlocked the bootloader which cleared all the data on my phone ---> flashed TWRP.img
Before this incident my phone was absolutely in default condition.
When I asked this question my bootloader was unlocked but now I have locked it and all i can do is to press the power button to see the bootlooping. Can you help me out from here?
I locked the bootloader as my phone was in warranty so I thought it would be better to get it fixed by the company itself , but since my city has been locked down due to the covid situation, my phone is still with me unrepaired .
Now I can't even get to the bootloader mode by pressing buttons .
I wanted to root my device and I followed exactly what was given on this website > https://safeboxguide.com/how-to-root-realme-c11/
Click to expand...
Click to collapse
Now the situation is more complicated if your device's bootloader is locked. But why is that u r in boot looping and u choose to lock your bootloader????

LinhBT said:
1st, what do you mean by "open the bootloader mode" ? If what you mean is you can boot the device into fastboot mode ( using hard keys or else ) then the solution is quite easy. Just take the stock boot image of A93 ( if you don't have it then u can pm me, I'll send ) then flash into the device using follow commands :
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
- fastboot flash boot boota93.img
- fastboot reboot
( remember to use patched vbmeta.img )
Your device will boot normal again.
2nd, from A87, the devs of Realmeme did something with the code so that if directly flashing magisk from custom recovery may random cause bootloop. So, my suggestion is to use fastboot command and flash the patched boot images like old times.
Click to expand...
Click to collapse
yes sir, by "open bootloader mode" I meant booting into fastboot mode.
Now I have realised the mistakes which I did previously--
1. I was not having the latest A93 stock boot image
2. I didn't disable the verification(- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
I locked the bootloader again so that I can get it repaired for free as you know the warranty won't be valid if they found the bootloader unlocked.
Is there any other way this problem could be resolved???

skund singh said:
yes sir, by "open bootloader mode" I meant booting into fastboot mode.
Now I have realised the mistakes which I did previously--
1. I was not having the latest A93 stock boot image
2. I didn't disable the verification(- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
I locked the bootloader again so that I can get it repaired for free as you know the warranty won't be valid if they found the bootloader unlocked.
Is there any other way this problem could be resolved???
Click to expand...
Click to collapse
Replied with file sent at your inbox.

Sorry for the late response.
Getting your phone back to life without the help of a Service Center will be tough.
Since you locked your bootloader, it’s gonna be quite hard to get you back. But when there’s a will there’s always a way.
If you have a laptop or a PC, you can use Platform Tools to reboot your phone to TWRP (since you mentioned that you already flashed TWRP). After booting to TWRP Recovery, you can simply flash a copy of a boot image. Since @LinhBT already sent you the file, you can use that one.
To install the boot image, go to Install, click Install Image, look for the boot image file, click on it, then choose Boot partition. Then flash.
After doing that, your phone should be back to normal. Tell me if it works for you.

I'm having almost the same problem, I want to root my phone to install TWRP and Install Lineage OS. I have also the update package RMX2185 A.95 in case I needed it. I patched the boot.img with magisk manager and locked the bootloader (fastboot flashing lock and fastboot flashing lock_critical).
Now my phone stuck in a Bootloop with a Red State Warning and I can't go to recovery mode.
Details:
Model: RMX2185
Firmware version: RMX2185 A.101
Rooted: No
{
"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"
}

Marielorteza said:
I'm having almost the same problem, I want to root my phone to install TWRP and Install Lineage OS. I have also the update package RMX2185 A.95 in case I needed it. I patched the boot.img with magisk manager and locked the bootloader (fastboot flashing lock and fastboot flashing lock_critical).
Now my phone stuck in a Bootloop with a Red State Warning and I can't go to recovery mode.
Details:
Model: RMX2185
Firmware version: RMX2185 A.101
Rooted: No
View attachment 5527747
Click to expand...
Click to collapse
I got my phone fixed at the service center . They replaced the motherboard as those people are not professionals they don't have enough knowledge about the softwares and stuff. I got it replaced as it was absolutely free for me( I locked the bootloader so that my warranty doesn't get void as i had mentioned earlier)
Getting the motherboard replaced was much easier for me than finding a pro on the internet who might have a solution for this.
I believe that there must be some solution to this problem other than getting the motherboard replaced.
If you find any solution please share.

My problem is I don't know where is my warranty card.

TWRP & MAGISK - Can not install twrp custom recovery or magisk ;-;

I have a Redmi 9 Lancelot with A partition only , bootloader unlocked and i installed twrp 3.4.1 unofficial image in platform-tools folder in my PC.
I connected the device to laptop and write:
adb reboot bootloader
fastboot flash recovery twrp.img
And
fastboot reboot
And went in soft brick (bootloop), i unbricked it with fastboot commands. But is it possible to install twrp recovery to install magisk on my phone?
*Sorry for grammar that is my first post and i am a beginer ((
*Also I had a backup soo didn't lose data
after that i tried to install magisk with no custom recovery:
1. Installed magisk version 22
2. get the boot.img (a time I soft bricked my phone Redmi 9 Lancelot bootloader unlocked) the boot.img its for the same MIUI version of my phone
3. copied the boot.img to downloads folder, installed magisc V 22, generated the patched magisk file (magisk_patched_JsCNt.img)
4. enabled USB debuging, USB instalation and USB security debug
5. opened the CMD as administrator in platform tools folder with magisk_patched_JsCNt.img in it
6. My device its only A partition i checked with an app from an another tutorial (yours)
and
wrote
adb devices
adb reboot bootloader
fastboot flash boot magisk_patched_JsCNt.img
fastboot reboot
7. device entered SOFT BRICK (bootloop) and i unbricked it with fastboot comands
8. PLS tell me what did I do wrong PLEASE.

I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you should have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done

hokkus_nhw said:
I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you shoul have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done
Click to expand...
Click to collapse
dude entered soft brick again

hokkus_nhw said:
I had the same problem and found that this is the only solution.
The twrp im using is from this website: https://unofficialtwrp.com/xiaomi-redmi-9-root-twrp-3-4-1/
1. Download latest miui rom https://xiaomifirmwareupdater.com/miui/lancelot/ (make sure its "fastboot", you will need the boot.img later).
2. Flash it with "mi flash tool". Then download the magisk apk from here: https://github.com/topjohnwu/Magisk/releases
3. In the .tgz miui rom file find boot.img and copy it to your phone (you will need to extract it).
4. Patch the boot.img with the magisk app and copy it to your pc (the patched boot.img should be in your downloads folder)
5. Put your phone into fastboot mode (adb reboot bootloader), and flash the patched boot.img and vbmeta.img (you can find vbmeta on the site with custom twrp) - fastboot flash boot magisk_patched-[...].img, fastboot flash vbmeta vbmeta.img
6. After this reboot your phone and you should have magisk with root access.
* 7. Now you can flash twrp recovery with app from play store "flashify", you`ll just need to give it root access.
Last step is just if you want the twrp for flashing anything else.
Done
Click to expand...
Click to collapse
and now i am unbricking my phone bro

Got the same issue, as op, but my Phone simply ignores my try to enter bootloader, both from adb and from physical buttons. Got bootloop yesterday with hardbrick, but managed to reflash it with Official miui 12.0.4 Lancelot software FROM 31st of March 2021 version. Still not being able to put twrp, pbrp to it, no matter if i do it with vbmeta, or without. Few different versions had need tried already (to twrp), but no success. Once or twice, at the very beginning (before reflashing Whole rom) i got into twrp, but after restart Phone opened Stock recovery instead of twrp and my next try of putting it back in Phone resulted in bootloop, ay lmao xD
I'm Not sure now, what to do? I remembered having the same issue back in my first tulip days, but I cannot resemble a solution to it anymore.
There are no Official twrp or pbrp for this model, could it be the issue?

buczek0711 said:
Got the same issue, as op, but my Phone simply ignores my try to enter bootloader, both from adb and from physical buttons. Got bootloop yesterday with hardbrick, but managed to reflash it with Official miui 12.0.4 Lancelot software FROM 31st of March 2021 version. Still not being able to put twrp, pbrp to it, no matter if i do it with vbmeta, or without. Few different versions had need tried already (to twrp), but no success. Once or twice, at the very beginning (before reflashing Whole rom) i got into twrp, but after restart Phone opened Stock recovery instead of twrp and my next try of putting it back in Phone resulted in bootloop, ay lmao xD
I'm Not sure now, what to do? I remembered having the same issue back in my first tulip days, but I cannot resemble a solution to it anymore.
There are no Official twrp or pbrp for this model, could it be the issue?
Click to expand...
Click to collapse
the dude from the service told me: "I tried with all methods, with Xiaomi flash tool too, just the manufacturers can repair it"
i got it hard bricked ;-;

Officer X said:
the dude from the service told me: "I tried with all methods, with Xiaomi flash tool too, just the manufacturers can repair it"
i got it hard bricked ;-;
Click to expand...
Click to collapse
if your phone is still bricked you can try what i did... https://forum.xda-developers.com/t/hardbricked-redmi-9-mt6769.4302829/ try this
NOTE : When you got this error from the photo, dw bcs yes you still cant boot but the fastboot is back like after that just boot into fastboot and reinstall the official miui rom using mi flash tool
If mi flash tool says Error or smth that means your bootloader locked, simply just unlock it again with miui unlock tool
{
"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"
}

Stefy1337 said:
if your phone is still bricked you can try what i did... https://forum.xda-developers.com/t/hardbricked-redmi-9-mt6769.4302829/ try this
NOTE : When you got this error from the photo, dw bcs yes you still cant boot but the fastboot is back like after that just boot into fastboot and reinstall the official miui rom using mi flash tool
If mi flash tool says Error or smth that means your bootloader locked, simply just unlock it again with miui unlock tool
View attachment 5411139
Click to expand...
Click to collapse
Its ok now i have magisk, the ideea was that my PC (with redmi 9 drivers, mediatek drivers and adb and fastboot drivers), didnt see that the phone its connected in device manager (i found someone who fixed it)

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