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?

Unbrick tool for OnePlus 5

{
"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"
}
Some china OP5 user got it from OnePlus staff, and uploaded it to china cloud drive.
[Driver]
Mega:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=889764386195921378
[Oxygen Version Download]
After you use this tool, your OP5 will be restore into stock Oxygen OS.
Mega 1:
https://mega.nz/#!MPBXkJjK!O2uDD7Xx04KPT_cx9coMHnGtaeSK06t9gwNpUR4KDXE
Mega 2:
https://mega.nz/#!gjRFmB4C!-HN00YSS2tUy5ZQTbJbzwEmZ8VU_iv5lLaTlbXin7Ec
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?fid=745425885120760474
[Hydrogen Version Download]
After you use this tool, your OP5 will be restore into stock Hydrogen OS.
Source :
http://www.oneplusbbs.com/thread-3587805-1-1.html
Baidu pan:
http://pan.baidu.com/s/1qYz7hZu
pwd: 0fb4
Mega (corrupted):
https://mega.nz/#!kyJ1XJ7D!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Mega 2:
https://mega.nz/#!RmQnQKTB!ghgEuR2sb1XkyGM4n5KDjOiID4KS6cFL5cIQqjSRAkc
Google Drive:
https://drive.google.com/file/d/0B9vxnq7dlG4pYVJGaGZOYWNuZzA/view?usp=sharing
AFH mirror (Thanks to @Titokhan):
https://www.androidfilehost.com/?w=files&flid=204903
[Tutorial]
The steps is the same as 1+3T.
Ref:
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

Great ! I always prefer a fastboot / edl flash.
Sent from my ONEPLUS A5000 using Tapatalk

Isn't it Oxygen OS?

gonsa said:
Isn't it Oxygen OS?
Click to expand...
Click to collapse
Yes,it isn't.
However you can easily install Oxygen OS by yourself.:laugh:
Ref:
https://forum.xda-developers.com/oneplus-5/how-to/guide-installing-oxygenos-chinese-t3647409

Someone should be able to tweak this to fetch OOS files instead of H2OS. Both the firmwares are the same except userdata
Sent from my ONEPLUS A5000 using Tapatalk

Someone should upload this to androidfilehost so there are other places to download incase the original is taken down.

file in mega is corrupted.
please upload in any uploading site

@snowwolf725 ,since I already "came back" from fastboot-ed github/OOS/MSM8998 build, I like to clarify few tips:
-Unbrick via Qualcomm QFIL tools were well documented here and there (Oneplus 1/2/3/3T) ; but Qualcomm never granted free distribution of QualcommQDLoader9008 DRV or QFIL, AND your WindowsPC has to be disabled with integrity checks or antivirus. So it should be considered as the last extreme ultimate rescue.
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.

@oF2pks if I get your process correctly, for a clean flash, Flash all needs to be done 3 times with the stock recovery followed by OEM lock and post that the last step is to fastboot erase boot/system/user data/cache followed by adb sideload of the stock firmware?
Sent from my ONEPLUS A5000 using Tapatalk

On this subject, we need a return to stock guide for the OP5 :good: Fine writeup oF2pks! :highfive:

oF2pks said:
-For cleaned & original OOS4.5.x back, with certified Playstore (and Magisk SafetyNet), full official Oneplus tools work fine : you need fastboot + original op5recovery with adb_sideload ok ; the main process is to recovery wipe allx3 + fastboot toggle OEM Lock / Unlock + fastboot erase [boot / cache / system / userdata]. The concealed trick is to recovery wipe allx3 once more (official OP5 recovery is re-branded CM/Lineage "re-signed" recovery); these 3x wipes will re-initiate "correct" user partitions from 4x fastboot/erase, with "somewhere" a kind of signature or cert (?), before adb sideloading official OOSzip.
-Then, only use official twrp for limited Magisk SafetyNet.
-IMHO, crucial persist (img /dev/block/sda2) should also be backup(, like modemst1&2 ), for advanced testers only.
(I'm not here begging for thx), but if you succeed back to "pure certified" OOS, give your thx (for others user attention) here : https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 ; AND take time to check the attached Oneplus5 full "sparted" partitions txt: you "must" have identical partitioning.
Click to expand...
Click to collapse
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!

TwinAdk said:
Okay - my writeup of the above quick instructions:
The end goal of this process
To return your One Plus 5 (codename Cheeseburger) back to 100% STOCK condition - both recovery and ROM. OEM status will be unlocked, but this is not an issue for OTA etc. This status will be suitable to you if you wish to "start over" with the phone, sell it, or similair.
Steps
Preparation:
1. Make sure you have a WORKING ADB and Fastboot setup on your computer. I recommend the ADB tool found here:
https://forums.oneplus.net/threads/cannot-read-ota-zip.457965/#post-15957941
I had the problem "* cannot read 'D:\OP5.zip' *", but the ADB tools from the above link solved this :good:
Notice the revision difference here: https://i.imgur.com/JurOcUf.png (green = Good, working version, red = the version that failed)
2. Download the ORIGINAL OnePlus5 recovery image, AND the FULL ZIP for the stock OOS ROM - NOT an OTA image ([OFFICIAL] OxygenOS 4.5.6 (7.1.1) OTA for OnePlus 5, posted by @Funk Wizard in the 2nd post - thanks dude :highfive: )
The process:
3. Flash the stock recovery -- Command: fastboot flash recovery recovery.img
4. Boot stock recovery by rebooting the phone and press VOL+UP within 5 seconds to interrupt the process.
4a. Select Recovery with VOL buttons. Confirm with power button
4b. Choose your language in the recovery and select wipe data and cache and then Erase everything
4c. Select DONE, not reboot. Select erase everything 2 times more (so you have erased it all three times in total).
5. Reboot the phone into fastboot again, and type fastboot oem lock - confirm and let it reboot.
6. Reboot the phone into fastboot again, and type fastboot oem unlock - confirm and let it reboot.
(if you wish to have a unlocked bootloader, this allows you to flash a custom recovery and thus install custom roms).
7. Boot into fastboot mode. Now we will manually wipe and format cache, system and userdata. paste this command into the commandprompt:
fastboot erase cache & fastboot erase system & fastboot erase userdata
- This will run the 3 commands after each other.
8. Repeat step 4, 4a, 4b and 4c again. In 4c only a single "erase everything" is needed.
9. Reboot into recovery again, select Install from ADB - this will enter the sideload mode, allowing you to install ZIP (flash it) from the PC.
10. Yay. 10 step Anniversary - dont we love it?!:good::highfive:
11. Enter adb sideload C:\path\to\full\OOS\stock\rom.zip
12. The CMD window will say "serving (1%)", etc... After a good while, the phone will say Install success - reboot the phone.
Thats it! :good: 100% STOCK!
Click to expand...
Click to collapse
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.

File in mega is corrupt please re upload

hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu

Sir link is not visible

Link is not visible

hsareminia said:
file in mega is corrupted.
please upload in any uploading site
Click to expand...
Click to collapse
sanjeevattre said:
File in mega is corrupt please re upload
Click to expand...
Click to collapse
hsareminia said:
hi guy's. dont download from mega. this file is corrupted.
only download from baidu link.
http://pan.baidu.com/s/1qYz7hZu
Click to expand...
Click to collapse
I add new mirror links and dirver download link.
Driver:
https://mega.nz/#!l2oXjD6Q!pT6OQjtmikWX7Q_OjTJndo3Hy1miJ3KvdE7ghe3QfPQ

jasonwsc said:
I don't know, this seems way too complicated to do.
If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.
Assuming that your phone is functioning properly, why would you need to use ADB sideload commands for any of these? And why on earth are you unlocking the bootloader? You do know that "fastboot oem unlock" unlocks the bootloader right?
Also check out my guide for a more in-depth but easier way of doing things.
If your phone cannot boot up, use the unbrick tool posted by OP. You will end up with a working phone but with HydrogenOS. Then flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
I am aware that the process above is HIGHLY complicated - and is often not necessary.
At the time of my post, my phone was in a state where I had been doing crazy things with it (decrypted data, multiple custom ROMs and TWRP versions, including multiboot variants and the chinese one. On top of that I had flashed the am-verity and force decryption patch zip). This is as such not unusual, but my attempts to return to stock had failed (stock ROM zip failed to flash, stock recovery were wierd as well).
Therefore, when the quick layout for COMPLETE STOCK were outlined above, I grabbed them and did the process, while documenting it for future reference for others. Also, I choose to include the oem unlock and lock part - though I am fully and completely aware that it's unnecessary to 99% of the readers, after all this is One Plus phones
I had not been able to find any other sources of the steps outlined, though they may be simple, so I took all the steps how ever overkill they might be, because then there would be a documented process
The steps above would recover a One Plus 5 from a state where only adb works, pretty serious condition indeed....
I'm staying on OOS based custom ROMs as long as the blobs for the camera is undisclosed by One Plus. I haven't had time to reply to this sooner, have a great weekend, and @asonwsc, I agree with you :highfive:
Kind Regards
TwinAdk

jasonwsc said:
...If you are on official OnePlus firmware, just place the full zip or OxygenOS and flash using local update in settings. It's as simple as that. If you are on TWRP or custom recovery, also flash the stock recovery image.
If you are custom firmware, use TWRP to flash OxygenOS zip and then flash stock recovery. Then wipe data and cache.... flash OxygenOS on top of HydrogenOS. Wipe data and cache if needed.
Click to expand...
Click to collapse
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )

oF2pks said:
Even with a locked bootloader and a certified Playstore on unrooted device , you can miss security checks : try MagiskApp for SafetyNet test + https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground WITHOUT active su (root).
The only way to recover "factory"-like OP5 device is to follow fastboot/erase4 by recovery/wipes3, and thus you need to unlock. Then sideload original OOS/H2O
You can relock before entering Oneplus' Wizard settings (reboot physical power button long press) and sale OP5 like effective brand NEW.
( @TwinAdk don't get why you "missed" [fastboot erase boot.img] ; still prefer my R&B "style": https://forum.xda-developers.com/oneplus-5/help/oos-darkware-fullvendor-building-t3637344 )
Click to expand...
Click to collapse
But if the device is considered certified on the play store, then it passed SafetyNet without an issue.
Correct me if I'm wrong, but shouldn't SafetyNet pass under the following conditions?
1. Locked bootloader with no root (stock)
2. Unlocked bootloader with Magisk root.
Is it actually possible for a locked bootloader and unrooted phone to fail SafetyNet? You can't root without the unlocking the bootloader, so how would that trigger SafetyNet?

[Deprecated] [GUIDE] [NOOB-FRIENDLY] Custom ROM Flashing Guide

Custom ROM Flashing Guide​So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
{
"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"
}
2. Download vbmeta from View attachment q_vbmeta.img and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by @ThE_MarD from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Check ROM notes and see if it comes with inbuilt vendor or not. If it does, you can skip this step. If it doesn't, ask for the required vendor from the maintainer.
Note: All A12 ROMs so far have come with inbuilt vendor.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
11. Flash TWRP permanently using this: Permanent TWRP.
12. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again) (skip flashing vendor if you skipped step 8).
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT).
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. Marc Bourgoin -- TWRP and Device Developer
5. All the testers.
Thank you and I hope this guide benefits the community.

OSS Vendor Flashing Guide​Note: This guide is deprecated now, kindly refer to the guide above for latest ROM builds.
So after tons and tons of test builds, the good ol' devs managed to get everything working and gave us a super stable ROMs (many more to follow soon ). However, since our device supports A/B scheme, a newbie can find it rather difficult to get used to flashing ROMs, kernels and even GApps! So I decided to prepare a simple guide which should help you get used to flashing ROMs and lots of other stuff.
Disclaimer: If you don't know what bootloader is and/or don't know anything about Custom ROMs, I strongly recommend you to not try this on your own and rather watch some videos about them and the advantages/disadvantages associated with them.
Notes:
1. Prerequisites:
Unlocked Bootloader
ADB, Fastboot and Device Drivers (Google them)
Use Command Prompt instead of PowerShell for ease of use.
STEPS:
1. Boot into Fastboot mode (power+vol up) and run:
Code:
fastboot -w
Note your active slot from here. Mine is 'b' as can be seen from the pic attached. Yours can be 'a' or 'b'.
View attachment 4785824
2. Download vbmeta from View attachment 4961371 and then do this:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. Now run the following command in your fastboot using pc(obviously):
If your active slot was 'a':
Code:
fastboot set_active b
If your active slot was 'b':
Code:
fastboot set_active a
4. Either restart bootloader directly from your phone (using volume and power keys) or do this:
Code:
fastboot reboot bootloader
Your fastboot screen should now look like the following. Notice the change in the active slot (if yours was 'a' in the previous step, it should be 'b' now).
View attachment 4785825
5. It's TWRP time!!
Download TWRP (both boot.img and permanent zip) by Jackeagle from here.
Flash TWRP using:
Code:
fastboot flash boot boot.img
Make sure the name of your downloaded twrp image file is boot.img! If not, either rename the file or change the fastboot code to that filename.img
6. Now reboot to recovery using power and vol keys on your phone. You should see TWRP booting up now. If not, you've messed up somewhere, do the entire process again (correctly ).
7. Click on WIPE > ADVANCED WIPE, and choose System, Dalvik (Cache) and Data.
8. Flash OSS Vendor. You can flash via fastboot by downloading and extracting OSS_Fastboot.7z. Navigate cmd to OSS folder and run:
Code:
fastboot flash vendor vendor.img
Alternatively, you can simply flash OSS_Recovery.zip in TWRP/SHRP.
9. Now, if you unlocked your bootloader via official apk (provided by Asus), then flash ABL.zip in TWRP/SHRP. However, if you unlocked unofficially, you can skip this step.
10. Now, flash permanent twrp from here, change to the inactive slot and reboot to recovery again. Flash the same vendor you flashed on the other slot. In other words, repeat Step 8 (no need to flash abl again).
11. Time to flash the ROM of your choice. ! Click on INSTALL and then choose the ROM you want to flash. SWIPE>>>>>>>>>
12. Flash TWRP permanently using this: Permanent TWRP. Flash this simply in twrp.
Note (optional): Mount vendor before performing this step just to be safe.
13. Reboot to Recovery (IMPORTANT)
14. After rebooting, twrp would have automatically switched to your active slot (the one you had in Step 1)(check this in reboot section of twrp).
15. Now you can flash GApps, Magisk from the active slot anytime. This step varies from ROM to ROM as some ROMs have GApps pre-installed.
Note: Access TWRP by pressing power+vol down button simultaneously.
16. REBOOT>SYSTEM and you're done! Enjoy the ROM.
Credit Section:
1. Jackeagle -- TWRP and ROM Developer
2. Rohan Purohit -- ROM Developer
3. Sandeep.Sethi -- Kernel Developer
4. All the testers.
Thank you and I hope this guide benefits the community.

What is vbmeta zip doing?

If I'm on .58 flashing just vendor.img of .72 before all the steps helps?

bordi21 said:
What is vbmeta zip doing?
Click to expand...
Click to collapse
It disables the verified boot, so that you can flash gsi and custom roms. Without it, nothing other than zenui will boot.
jayd4321 said:
If I'm on .58 flashing just vendor.img of .72 before all the steps helps?
Click to expand...
Click to collapse
Yep flash vendor image and stock boot image of 72, and you'll be good to go!

I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.

Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.

viveknaudiyal said:
I have performed step 8 and now I am in twrp. How to perform Step 9. Please suggest
Edit- Thanks did it by copying the files to my otg and flashing through twrp.
Click to expand...
Click to collapse
Glad you were able to succeed
Xadus said:
Thanks a lot for your comprehensive guide, got to unlock the bootloader and flash twrp as per the guide.
However, I have a problem booting the ROM; the ROM installs perfectly well and I can reboot into recovery but can't get past the "ASUS" screen upon actually trying to boot the ROM.
Am I missing something? I followed everything down precisely and I honestly don't know what am I messing up.
A little help would be appreciated.
Click to expand...
Click to collapse
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?

AryanAA said:
Glad you were able to succeed
Okay! Can you provide your bootloader version and slots on which you have stock rom and twrp?
Click to expand...
Click to collapse
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.

Xadus said:
my bootloader version was the latest one .72 and my stock ROM was on slot b, which I switched to a for flashing twrp and then booted into twrp and switched back to b to clear data, system and cache; flashed the ROM in the same slot and then flashed the permanent twrp as well.
Following all this i could reeboot back into twrp but couldn't get the ROM to boot.
Click to expand...
Click to collapse
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).

@AryanAA can you please extend this guide on how to install magisk

AryanAA said:
After wiping system,data,cache, you had to go back to slot A and then reboot to recovery and after that flash the rom (read point 10 of post).
Click to expand...
Click to collapse
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.

HELP
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.

I was able to flash elementalX using this guide. Thanks for detailed info,i found this guide more understandable than the 1 we have in how to flash gsi thread.

milindmavadia said:
Encryption Unsuccessful!
Tried everything multiple times like mentioned in OP.
Click to expand...
Click to collapse
1. Flash DFE on both slots.
2. Go to fastboot and do fastboot -w on your rom slot

Xadus said:
I tried that as well.
I must have repeated the process numerous times, i tired flashing it on the slot where my twrp is and i tired flashing it on the slot where was stock was as well in the next try; both incidences gave bootloop.
Click to expand...
Click to collapse
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!

viveknaudiyal said:
@AryanAA can you please extend this guide on how to install magisk
Click to expand...
Click to collapse
Process of flashing magisk is exactly same as gapps. Infact you can install gapps and magisk in one go.

AryanAA said:
Interesting. I think you should restart the whole process and flash rom only on inactive slot rather than both the slots!
Click to expand...
Click to collapse
Maybe i will give try in the future, for now i flashed the stock as i was frustrated by the whole thing.
Thanks a lot for your help though.

Fastboot -w ..it's says "waiting for device" can any one help?

Aruss5 said:
Fastboot -w ..it's says "waiting for device" can any one help?
Click to expand...
Click to collapse
You have to first install adb and fastboot drivers to your computer.

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

[RECOVERY][UNOFFICIAL][3.5.2] TWRP for Galaxy M21 [CWB1 and Above]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
I am not the developer.
Developer: @naz664
Changelog:
Spoiler: View
Changelog :-
- Souls recovery with latest A12 support (Jan 2023)
- Updated kernel
- This recovery won't work on older stock version
So don't flash this unless you are running latest jan 2023 stock rom
How to install?
Spoiler: ODIN (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Press the volume down + volume up button whilst the phone is connected to a pc to boot in download mode;;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol down + Bixby key + USB cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, factory reset data and redo from step 5!
Download TWRP.tar from download link below;
Open odin and place the TWRP.tar file in AP slot and press start. Once you press start, keep holding power and volume up button and the device will reboot to recovery mode.
* If you're coming from stock, go to "Wipe" > ""Format Data" > type "yes" to format data. If you skip this, Internal storage won't work in TWRP
Flash the encryption_disabler.zip from the link below to disable internal storage encryption and patch stock recovery restoration.
Additionally, flash TWRP_Bootlogo_patcher to patch warning screens when booting the device.
If you want to root, flash Magisk.
Spoiler: TWRP
If you're coming from other TWRP versions, download TWRP.img, reboot to recovery, tap Install > Install Image > Navigate to downloads folder > select TWRP.img > Select Recovery and swipe to confirm flash. Go to reboot and reboot to recovery and the changes will have taken place.
TWRP Source: GitHub
Credits:
Soul reaper
Nazim
Lmao
Max B
Darshana & Encrypted for testing
Important:
This version only works on the latest update of stock rom (M215FXXU3CWB1) and above. If you are running an older version, use the previous build of TWRP.
Download: Link

И что делать ?

w1nk1 said:
И что делать ?
Click to expand...
Click to collapse
Different device?

Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.

OldNoobOne said:
Hi Fredin friend,
I Recently upgraded SM-M215G device to OneUi5.1 (M215GDDS3CWD1-20230522142126) Binary 3 and TWRP (twrp-3-5-2-m21-v3-1-a12-tar)but anything I am flashing is either bootlooping or stuck on Rom Logo, I flashed (Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip) still only Rom Logo showing, how to boot the GSIs? Any help appreciated.
Click to expand...
Click to collapse
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.

Fredin_ said:
Hi
If you had unencrypted data (if you could see files in internal storage) and flashed the latest stock rom, but you didn't flash encryption/multi disabler before the first boot into OneUI, it will probably cause problems.
So try formatting data and flash encryption/multi disabler (although I believe dm verity disabler also disables encryption by default, but it won't hurt flashing them). Or you can format data and not flash anything to let data stay encrypted, but then you won't be able to use the internal storage in TWRP.
Click to expand...
Click to collapse
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery

OldNoobOne said:
Hi friend Fredin,
Thanks for the reply.
I used (twrp-3-5-2-m21-v3-1-a12-tar) and it is smooth (just like previous Soulr-A11 twrp) but sideload did not work while the other recovery (TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) by Dev Ravindu Deshan works great too but Reboot to Recovery does not work properly all the time, so sometimes instead of Reboot to Recovery the changes happen when manually reboot to recovery using usb cable also sometimes it does not recognise pen drive. Till now I only managed to boot Tuki1.2 and the other Lineage 20 zip had Oplist error 1 issue. Hoping for GSI boot too later. Thanks for recovery
Click to expand...
Click to collapse
I'm not the dev btw, @naz664 is

Fredin_ said:
I'm not the dev btw, @naz664 is
Click to expand...
Click to collapse
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.

OldNoobOne said:
Hi Friend,
Naz Roms great also
sidetalk: Do you know how to unlock CWD1 Stock Rom bootloader? my bootloader isnt unlocked fully? And in Shaomi phones which model would you recommend, it has fastboot so.
Click to expand...
Click to collapse
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.

Fredin_ said:
What do you mean by it's not fully unlocked? iirc the toggle stays like that once the bootloader is unlocked.
Click to expand...
Click to collapse
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.

OldNoobOne said:
Hi Friend,
When I had unlocked the bootloader of the same device while it had A11 loaded in it, the oem unlock button was TOTALLY GREYED OUT (I swear I'm not lying), I mean even the toggle button was greyed out but in above picture you can see toggle buttons are Blue color and oem-unlock toggle button is light-blue but not fully greyed out, I didnt relock my bootloader before flashing A13 Stock CWD1 update
Now I cant flash GSI they refuse to boot always stuck on bootlogo.
Click to expand...
Click to collapse
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net

Fredin_ said:
Don't think there is any in between state. If you can flash stuff, your bootloader is unlocked. If the GSI is not booting, that's some other issue. Try the new AOSP ROMs instead.
A51 Builds by Royna - Browse Files at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Thanks Friend,
It looks like Royna's ROM zips (Lineage 20 & evolution_m21-ota-tq2b.230505.005.a1-06050648-community-unsigned.zip & crDroidAndroid-13.0-20230427-m21-v9.4.zip) not flashing, reason - TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list") and repartition issue even while sideloading. The only one that boots is TukiRom1.2, I havent tried Tuki1.3 yet. I tried Roynas' TWRP files too but after boot to recovery they get stuck, the other TWRP files (TWRP-3.5.2-m21-v3.1-A12.tar & TWRP.3.7.0_11.-.M215FXXU3CWB1.tar) boot and work with some issues though.