Database Info

Coolpad Rogue (3320A) Stock Recovery, Kernel, Modem & Firmware Images

Coolpad Rogue 3320A - Stock 5.1.1 Build No. 5.1.157.00.T2.150810.LMY47V
Fastboot Flashable Recovery, Kernel, Modem & Misc. Firmware Images
Disclaimer You flash these images at your own risk. I am not responsible for bricked or otherwise inoperable devices as a result of flashing any of the files provided herein.
These partition images will help you recover a soft bricked device in the event you have missing or corrupt partitions. Additionally, in the event you are having signal or connectivity issues, flashing the modem/radio firmware could resolve those problems. I have provided all partition images for the 3320A with the exception of /system and /userdata. The stock /boot and /recovery images are always good to have in case you ever need them. At a minimum, save these images to external storage in case of future need. I will provide a full /system image in future at request.
WARNING Flashing bootloader or bootloader dependent partitions can result in a hard bricked device. Please do not flash bootloader type partitions unless you are well versed in this area. Tampering with these particular partitions is best left for developers and experts. I will clearly label any bootloader type partitions, in hopes that it will alleviate any confusion.
INSTRUCTIONS:
Install Minimal ADB and Fastboot on your PC or Laptop. The installation files can be found here on XDA Forums. Install the USB Drivers for your Coolpad Rogue 3320A. (The drivers are pre-installed on the device itself. If you are able to boot up, connect your 3320A to your PC and look in your PC's directory for an installation option.) Place the .img files you need on an external SD card or in internal storage. With your device powered off, boot into Recovery Mode by holding power and +volume simultaneously until the Coolpad logo appears -- then let off of power but continue to hold +volume until the stock recovery screen appears. Use your volume button to scroll down to Bootloader and press power to select. When the Fastboot screen appears, connect your device to your PC with a suitable micro USB syncing cable and press +Volume. In your Minimal ADB and Fastboot directory open a command window (Shift and Right Click).Type: fastboot devices If you are properly connected, your device serial number will be displayed in your command window under connected devices. If your serial number doesn't appear, repeat the above steps, ensure your USB drivers are installed correctly, and try changing USB ports on your PC or trying a different cable. Once you are connected properly, the rest is simple: I have named each partition image synonymous to its corresponding partition. In other words, the name of the file is also the name of your device's partition to be flashed.
EXAMPLE If you are flashing the "carrier" partition, you simply type fastboot flash carrier carrier.img Again, I will label each partition as to the type (e.g. recovery, bootloader, modem firmware, etc.)
DOWNLOAD LINK:
https://drive.google.com/folderview?id=0B7-zQU1VihD3eXE1SjBIby02Rmc
PARTITION NAME / TYPE
tz - "Trust Zone" Bootloader Dependent Partition
tzbak - Allotted Partition Backup of tz
ssd - Firmware Partition
sec - Firmware Partition
sbl1 - Secondary Bootloader
sbl1bak - Allotted Partition Backup of sbl1
rpm - Primary Bootloader
recovery - Stock Recovery Image
persist - Firmware Partition
params - Firmware Partition
panic - Firmware Partition
pad - Firmware Partition
oem - Manufacturer/Device ID Partition
modem - Radio Firmware
modemst1 - Radio Firmware
modemst2 - Radio Firmware
misc - Carrier/Region ID Partition
keystore - Firmware Partition
fsg - Radio Firmware
fsc - Firmware Partition
devinfo - Manufacturer/Device Info Partition
ddr - Radio Firmware
config - Carrier Specific Info Partition
boot - Stock Kernel/Ramdisk
aboot - Application Bootloader Partition
Hopefully this guide will help you restore your device from an inoperable state or restore connectivity from problems originating from damaged/corrupt partitions.

Relaying A Message from MotoJunkie01
Relaying A Message from MotoJunkie01
I apologize for not being in closer contact. I have some pressing issues going on and, coupled with work, man I've been tied up something awful. I'm going to need to drop off XDA for a month or better to get my personal issues attended to. I need a huge favor from you.
My little threads I have started, if you could go on and explain I'll be gone for a month or so. I'd appreciate it.
I've Not enough time to even do that.
So if anyone needs a reply I'd figure sometime in July, and I hope you all will understand and allow this time for MotoJunkie01 to attend to his personal matters. Signed: ResistanceIsFutile

Link not working
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files

Gamesmedic said:
Your above link does not work. Also I have no idea why you are trying to share images. Fast boot only pushes zip files
Click to expand...
Click to collapse
Sorry about the broken link. I just added a new working link with all listed firmware images.
You are obviously extremely confused about the purpose & function of fastboot commands. Allow me to educate you a bit. First, contrary to your statement, fastboot does not "push" files. And it most certainly does not push "zip files." In fact fastboot cannot be used to manipulate zip archives at all. . If you go back and read the thread, fastboot is used primarily, and as a preferred method by many, to flash firmware images to your device. (.img, .bin, mbn, etc) The firmware images in my link can be flashed to the Coolpad Rogue, via fastboot, to restore the partitions to pure stock/factory condition, in the event of a soft brick, bootloop, corrupt OS, etc.
I hope this clears your confusion some, before you hard brick a device trying to "push zip files" with fastboot.

Sim unlock
would this help to do a sim unlock

rachinda said:
would this help to do a sim unlock
Click to expand...
Click to collapse
No. SIM unlocking involves an entirely separate procedure. I am not even sure a SIM unlocking procedure is available apart from using a remote unlocking service or requesting an unlock code through the carrier directly. This thread is merely a source for stock firmware partitions for devices which are stuck in boot loop, soft bricked, poor or lost cellular service, connectivity issues, etc.

Here is the solution for BOOTLOOP after 9.0 beta

Hello everyone ,
so , I've been this and here is what i did to get back to normal :​
1- download MiFlash and the oreo 8.1 (V9.6.8.0.ODHMIFE) fastboot image from here
2- download *adb* file that i upload , and extract the files
3- download this file ,and extract the files , you will find *TWRP* folder
4- copy or move *adb* folder to the C:\
5- use Miflash to flash the fastboot image
6- when your phone start bootlooping go to the fastboot in the phone
7 - open the *adb* folder and run *Command Prompt* , write *fastboot boot recovery.img*
8- when the TWRP start go to pc and copy *TWRP* folder and place it in the main internal
9-go to restore in TWRP and chose the backup folder , restore *Boot* and *EFS* and swipe (if it doesn't show anything to restore go to TWRP>backup and copy *2018-12-06--15-41-27_PQ1A181205006* folder into *TWRP* folder "not to backup folder")
10- now in TWRP go to reboot and click bootloader
11- you will go to fastboot , flash oreo 8.1 (V9.6.8.0.ODHMIFE) by MIflash
12- everything will get back to normal !! :highfive:
update (3-10-2019) :
i recommend to flash latest official mi a1 rom maybe well fix it (using fastboot) ,
any way here is new link for TWRP file http://www.mediafire.com/file/j6682qbs7qa5sg5/TWRP.7z/file
thanks to :
@joeyhuab for the advice
@berlin51 for the link
@abhishek987 for the recovery image file​

So this will not mess up any IMEIs or anything? Is this a universal solution for everyone who messed up?\
EDIT: Nevermind, used the guide, works fine. Thanks for that!

It's working. Thank you!
Just need to copy "2018-12-06--15-41-27_PQ1A181205006" to TWRP folder.

following the tutorial, but my sim card didnt work, any solution?

adnbwta said:
following the tutorial, but my sim card didnt work, any solution?
Click to expand...
Click to collapse
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes

UCFour said:
IMEI must've got corrupted
Dail *#06# and check if it is showing phone's IMEI numbers n not zeroes
Click to expand...
Click to collapse
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?

adnbwta said:
imei still there, both sim, but in settings-imei SV both are 00, anyway to fix it?
Click to expand...
Click to collapse
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash

UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
Can you explain a bit
Sent from my OnePlus5T using XDA Labs

If anyone is planning to flash Pie stable/beta
1. First take a backup of EFS from TWRP and Low level backup of all partitions ( system n data not needed ) with low level backup tool via EDL
2. In order to get Pie booted, you just need "System.img" extracted from the OTA ( use payload dumper) or just take the system.img file floating around here
3. Transfer System.img to adb folder >> Boot to fastboot and flash the system.img only
fastboot flash system_a system.img
fastboot flash system_b system.img
Everything works except dual 4G/VoLTE
Downgrade will also won't have any issues
> For Dual 4G/VoLTE, you also need to flash modem and rpm
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash rpm rpm.img
fastboot flash rpmbak rpm.img [ Optional]
But now if you try to downgrade , you might end up with bootloop
>> To Fix bootloop, boot to EDL
Flash the fastboot rom you were running before when you took back of partitions
Then Use lowlevel backup tool to restore all the partitions and reboot
---------- Post added at 08:38 PM ---------- Previous post was at 08:35 PM ----------
Amanpreetsingh said:
Can you explain a bit
Sent from my OnePlus5T using XDA Labs
Click to expand...
Click to collapse
Procedure is same as flashing fastboot rom via EDL mode with MiFlash but instead of flashing it from fastboot try it from EDL mode
Use this command within fastboot mode to get to EDL
fastboot oem edl
Total process will take 10+ minutes, once the flashing status changes to "Success", hold the power button for around 10 seconds to reboot

UCFour said:
SV values are zeroes by default
Try to flash the same fastboot rom again but this time via EDL mode [ fastboot oem edl] using miflash
Click to expand...
Click to collapse
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now

adnbwta said:
done that, but the sim still not showing, tried to swipe sim to slot 2 but no change, really confused right now
Click to expand...
Click to collapse
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..

UCFour said:
Check if those IMEI numbers are your phone ones only? AFAIK EFS is device specific which contains information like IMEI, MAC Address..
Click to expand...
Click to collapse
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?

adnbwta said:
both IMEI in the settings and in the box are the same, but now after flash image from EDL both IMEI become 0 and unknown, any solution?
Click to expand...
Click to collapse
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom

UCFour said:
If anyone is planning to flash Pie stable/beta
Click to expand...
Click to collapse
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?

michkost858 said:
Is that for people who flash it through fastboot or is this required if we update to the stable through OTA as well?
Click to expand...
Click to collapse
There is no official fastboot rom yet, the one available has the contents of extracted payload.bin from the OTA
Even if you update your phone via official stable OTA, you will be facing same downgrade issues
Yeah i meant it for those who are planning to flash via fastboot as most OTA users with locked bootloader wouldn't bother to downgrade

Please help me I did the steps and manages to restore the stock rom, but I get a message saying "phone not allowed" And when I want to make a call tells me "mobile network not available "

UCFour said:
Use this guide
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190
1. Download 7.8.23 Nougat Fastboot rom, flash it via EDL
2. If the phone boots fine to OS, Great! [ IMEI fix only possible with Nougat ] else restore the EFS again via TWRP [ Don't restore anything else modem/boot] to get the rom booted
3. Download Qualcomm dailog driver, IMEI to Hex converter, HEX Editor and QPST tool [ Latest ]
4. Open IMEI to HEX Converter, inpur your IMEIs and save the hex numbers somewhere else
5. Now download the QCN file linked in this post, open the QCN with hex editor and navigate to the address locations 0x17C50 & 0x02530 and replace the hex values "08 8A 16 11 11 11 11 11 11" and "08 8A 26 22 22 22 22 22 22" with the ones you saved before and save the QCN file [ You can can .qcn extension if this file doesn't work in the final step ]
https://forum.xda-developers.com/showpost.php?p=76496159&postcount=23
5. Now type *#*#717717#*#* , you will see dialog port enable status
6. Connect phone to PC, enable Dev options and USB Debugging
7. Open QPST [ Software Download ], Restore Tab see if the port is showing. If it isn't update the driver within device manager
If the port isn't showing even after driver update, detach the phone USB and re-connect phone
8. with the Com port displayed, select browse under xQCN file tab and the select the QCN file u modified with your IMEI numbers
9. Select "Allow ESN Mismatch" and hit start >> wait until status changed to memory process done successfully (something similar)
10. Reboot phone and everything will be fine
After everything is done, first its better to update to Oreo via OTA first [ Two 1GB Updates ] and then flash oreo fastboot rom
Click to expand...
Click to collapse
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?

adnbwta said:
i follow the tutorial, but the imei in phone is different with the one in the box, maybe I did something wrong in step 5, can u tell me how to change or remove imei?
Click to expand...
Click to collapse
If the IMEI is different then u haven't edited the QCN correctly
Flash Nougat firmware again via EDL
and this time edit the IMEI hex values correctly in the qcn file via hex editor
Also make sure u have converted your IMEI to hex values

for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
---------- Post added at 06:24 AM ---------- Previous post was at 06:01 AM ----------
jai krishna said:
for me nothing is showing in twrp folder in restore
pls help
i folled the steps in op properly
Click to expand...
Click to collapse
I took my own backup of boot and efs.so one folder created in twrp folder.
i replaced my files with the downloaded files given in op
thanks a lot.love u all

I have a question, I am on Android P official BETA flashed with TWRP. I have backed up my previous P PE ROM with Boot, EFS, Persist, Modem full Nandroid Backup. Can I flash official P STABLE (Fastboot ROM) with MiFlash Tool when its available?? Without bricking my device??

[guide] Blu Vivo XL4 | | Vivo Xi || Vivo Xi+

The BLU VIVO XL4 has arived.
Sorry this guide is not for very new users, it relies on certain amount of prior knowledge.
**NOTE**
Unlocking Bootloader WILL set warranty flag to "NO"
Make the read-back backup, BEFORE unlocking, so there is a possibility to restore warranty to "yes"
Getting SPFlash Tool to work on BLU VIVO XL4
I used sp flash tool version 5.18.28
Needs custom DA file and Auth file. Both have been found from a near clone device.
Open flash tool select the DA file and Auth file from the link below.
add the scatter file from archive. There is a preloader file in the archive also. This is needed for spflash tool to open the Auth file.
Stock Rom and Auth file
Then follow the guide found on youtube.
Not planning to go into too much detail about the actual pulling of the firmware, as there is already
a fantastic guide with step-by-step photos and also a video.
Just the basics
Pull stock rom with spflash tool once just from the "boot region" to get the preloader file.
Process that file with the Wwr_MTK tool to get partition table information.
And one more time pull as one large binary file from the "user region" then split it into
individual images using the tool called "Wwr_MTK" it can be found on other site(Hovatek). I cannot put a
link as it is against forum rules (no advertising other forums)
But there is a youtube video that describes the process. And gives link for download of the tool.
**NOTE-1**
The Wwr_MTK tool did not have the correct chip (mt6762 In fact the "family class" for the chip is mt6765) as an option. Because of this you will need to add it to the tool before using it. Open the downloaded zip.( I used "WwR_MTK_2.40_Eng" ). Open "Template.ini" with text editing software, in the section labeled "CPU" add "MT6765 2" , keep same format as the rest of the file. Save the changes and close Template.ini.
Now when you run the tool, you will be able to create the scatter file as you split the rom into files.
**NOTE-2**
The tool connects to internet and downloads fresh the files and scripts when you start it. There is a 30 second ad screen displayed. If you block internet to the tool, then the add screen turns into 2 minute wait screen. I am not suggesting that you hack the tool to by-pass it, just letting you know what to expect.
IT IS HIGHLY RECOMMENDED TO MAKE YOUR OWN FULL BACKUP BEFORE PERFORMING THESE STEPS
AFTER YOU HAVE MADE FULL BACKUPS
Now to start modifying
DOWNLOAD
UNLOCK BOOTLOADER
unlocking bootloader is no more complicated then then enabling OEM unlock toggle in dev options menu.
Then performing Command in terminal. Just like so many android devices.
Unlock Bootloader
1. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select more "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
2. Open cmd or power shell terminal
3. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
4.Once the phone has finished loading into fastboot mode type this command
Code:
fastboot oem unlock
I also did --MIGHT be an optional step
Code:
fastboot flashing unlock
Do not think both were needed.
After each command when phone was rebooted,
it took extra time to open. But did not show the normal recovery screen while
it did the factory reset. But a reset did happen both times,
as I had the setup wizard each time.
Even after unlocking bootloader, doing a "fastboot boot *xyz.img" (boot or recovery test images)
Phone would only cycle to off then do a full reboot. Doing "fastboot flash boot boot.img" does flash the boot.
And "fastboot flash recovery recovery.img" does flash the recovery.
TWRP
1. Download TWRP From Link above
2. Enable Developer options on phone:
open settings--> "about device"--> click build number 5-7 times--> go back one screen in settings
-->select "more settings" --> scroll to bottom "Develpoer options" --> enable "usb debugging"
3. Open cmd or power shell terminal
4. reboot phone to bootloader with the following commands
Code:
adb reboot bootloader
5. Now give the command to flash twrp, assuming you downloaded the file to default download folder
Code:
fastboot flash recovery %userprofile%\downloads\TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img
5. Reboot to twrp. Needed to boot directly to twrp, or stock recovery will be re-flashed by phone.
Code:
fastboot oem reboot-recovery
Once inside twrp It is asking for password to unlock (decrypt)***automatic decrypt not work on this device as of YET***
this is supposed to be same password used to unlock phone.
Because this twrp does not work with encryption, every time you reboot you will have to select language, if changed from default.
To get recovery to be functional, you need to make phone patched for both "DM-Verity" and "Force-encryption"
I do this with
"Universal Disabler"
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
There is similar utiliy built into this Recovery image.
to use the built in option , Select ADVANCED, Then RM Forceencrypt
This will flash the lazypatcher with options set to remove encryption both in boot.img and /vender/*fstab : remove dm-verity.
--OR-- manually do the following steps
Steps
1. Download Zip from Link above.
2. Open TWRP
3. Open Wipe menu
4. Select format /data
5. Key in "YES" and swipe
6. Return to Home Page of TWRP
7. Choose reboot menu then recovery
8. Recovery should now have access to Internal memory (temp for now)
9. Use abd push to put the zip file downloaded above to internal memory
Code:
adb push %userprofile%\downloads\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /sdcard/
10. Select install menu , and install the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip
Do not rename the file. It installs and makes the patch base on the file name.
If you want to have root also, then flash Magisk at this point.
Now the dm-verity and force encryption are off. You can flash gsi custom rom, if you desire. At the moment, I have only been able to boot the phone with working cell data and calls on the PHH-Phusion --vanilla builds. Do not know why the gapps versions do not allow rill to function.
As of the writing of this I have put up V4 of the TWRP port. This version uses the correct mount points for this phone, not the ones from the source of the port. Also corrected the device name in default.prop, to match device name. Build fingerprint has been left as is. Fixed the micro sdcard name and OTG names. Added mipe to the "misc" /"para" partition to escape a factory reset recovery loop that [uu]could[/u] happen under certain situations.
And my prefered ported recovery from LRTeam TWRP-3_2_3-1020-OMFG-mod_b6-device-name-vivo-wipe-misc.img.
DOWNLOADS
Files
1. Sp Flash tool (v 5.18.28 or newer) https://androidmtk.com/smart-phone-flash-tool
2. stock XL4 ROM, DA file, TWRP all in shared folder https://androidfilehost.com/?w=files&flid=287088
3. stock Xi+ ROM, TWRP in shared folder https://androidfilehost.com/?w=files&flid=287703
4. Unviversal DM-Patch disable tool thread
5. Youtube Guide Video to use backup image splitter tool "WWR_MTK" https://www.youtube.com/watch?v=GMAytZ56hac
Kernel sources have been published 12-12-2018, by BLU
I have them synced to GitHub while I make test builds.
https://github.com/mrmazakblu/BLU-VIVO-XL4-kernel
Default defconfig should be arch/arm64/config/k62mv1_64_bsp_defconfig. Based off of build description in "getprop"
Built kernel has not been able to be booted yet.
TWRP is first ported and provided thanks to @Voinea12
.

placeholder not really welcomed here on XDA
just pm a moderator or report this thread when you`re ready to upload something, until then, thread closed

After seeing that the Blu vivo xl4 requires an "auth file" in order to flash with spflash tool, I asked BLU to supply the file.
They responded with a big fat NO.
.......
.......
THE NEXT DAY THE FILE WAS POSTED ON A DIFFERENT THREAD.
SO THERE HELP WAS NO LONGER NEEDED.

Just made successfull readback on preloader. and currently reading full rom.
will post link when done.
here is auth file and DA file I used.
pulled firmware is here.
there are more images in complete firmware, but the ones included should be enough , as long as you NEVER do format all from spflash tool.
STOCK ROM

So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Working version is available now

Thread was opened.

mrmazak said:
So far all attempts to load twrp have failed.
Also just tried to flash boot.img with the built kernel. When rebooted, phone just stayed on black screen. No back-light , nothing.
Just a repeating connect disconnect sound from pc. Long pressing power and trying to get into the bootloader menu failed.
Was able to Que up sp flash tool and keep holding the volume down button , on the next time it cycled on off preloader was caught and i was able to flash back the correct boot.img.
Click to expand...
Click to collapse
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?

psychofad said:
My streak with SP Flash is still a losing one, the auth file works for my phone as well (Blu Vivo XI+), I just used the preloader.img that was in the update.zip and ran it through the WwR MTK Tool and got the preloader.bin to go with the auth file as you indicated you had done, that was one hurdle that your post helped me solve, but for some reason when I start reading the full rom I get about 6-10 MB into it and then it disconnects from my phone and stops. Not sure if its driver related or what, which drivers did you use for the readback?
Click to expand...
Click to collapse
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?

mrmazak said:
To be honest I have not installed driver specific for this. I have vcomm drivers installed, same from couple years ago.
Is the readback stopping because you set wrong hex address length in the readback tab?
Click to expand...
Click to collapse
No, I got the readback of the EMMC_USER just fine and ran it through the WwR MTK tool and it gave me the hex address to use for the full rom readback, t then told me
Code:
The file size is smaller than the start position of the LK (uboot). To determine the type of processor and memory, it is necessary to read the full firmware in the SP Flash Tool, specify the parameters for reading: Start address: 0x0, Lenght: 0x1D1EC00000.
So I entered those two addresses as EMMC_USER readback. If my phone is off and I just connect it to the usb without holding any keys it gives me another error.....and I'm an idiot. just figured it out as I was looking at logs, apparently I must have changed the usb speed in sp flash which changes it's pid causing it to try and read from another port. It's downloading now

Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ

******EDIT*****
Most of the following problems did not repeat in same way when I tried to repeat the install process.
Main issue was with simcard. But exact process to get installed and working is still not known.
-- install after already having rooted, encryption removed stock, seems to work.
-- fresh full stock rom, full encryption, then gsi seems to not work sim card.
PHH-treble gsi images do boot this device. I do not have a bug list as yet.
working:WITH encryption removed:
1. wifi
2. camera
3. fingerprint- unlock
4. music
5. video
NOT working :WITH encyyption removed:
1. cell signal
2. cell data
3. phone
4. sms
---------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------
working:WITH encryption enabled
1. phone
2. sms
NOT working:WITH encryption enabled
1.. everything else
EDIT
Much of the force closing problems were from a corrupted external sdcard. When I removed the card , the force close messages did not come.
Getting 4G data connection was not stable. after a full reset and rom re-install I was not able to get data connection, and only able to have connection to make calls when set to 3G connection only.
some bugs in vendor I assume will need some help solving this.
EDIT 2
Finally got around to trying again. his time I started with vanilla version of phh-treble gsi.
4G data and sms, calls in out all work. Camera , video both work.
WiFi tethering did not work.
Setup that worked :
force encryption removed with universal dm-verity patcher, ( bothboot.img and vendor partitions both edited).
magisk patched boot

Would this work on Blu Vivo XI since same chipset?

sinkoo1979 said:
Would this work on Blu Vivo XI since same chipset?
Click to expand...
Click to collapse
It should. I have been working with few users with Xi+ it works for them. And another user of Xi provided a twrp port, but no details on if this read-back worked. It must have, I suppose it must have.
Please do try to do the readback for your self, and share the files. will help with twrp if I can

Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.

mrmazak said:
Guide has been revised.
The original guide suggests to format /data and patch device to remove force encryption. This works fine for stock rom, and modifying stock rom. But I have found that removing encryption will not allow the phone to work as a phone when flashed with GSI. The down side is, at the moment, there is no twrp that is working to read the encrypted /data.
Click to expand...
Click to collapse
Can any of this be done without a computer

Decaphyz said:
Can any of this be done without a computer
Click to expand...
Click to collapse
No, you need fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.

mrmazak said:
No, need you fastboot(PC preogram) to unlock bootloader and either sp flash tool or fastboot to flash recovery.
Click to expand...
Click to collapse
Oof

mrmazak said:
Thanks to @hanuma there is now a material themed twrp port.
The V2 version loads. But has no adb or mtp access
https://forum.xda-developers.com/showpost.php?p=78498431&postcount=95
https://mega.nz/#F!225EzQwT!t8hvGvmFoNYNvXev-Li1fQ
Click to expand...
Click to collapse
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site

IndifferentBear said:
I just did this, and it worked the first time. I got into the phone and set it up. But it was super laggy after a while. So I decided to reset the phone like how you would normally do to fix a problem, and now... it’s making me boot into the recovery each and every time I try and boot into the system... i installed the gsi rom "PixelExperience for AOnly" at max lees site
Click to expand...
Click to collapse
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition

mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
thanks dude! can you give me the command to run in terminal to do it? ill try that first, then ill try flashing stock recovery!
---------- Post added at 02:47 AM ---------- Previous post was at 02:44 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
but i was required to wipe the sys, data, cache, and dalvik/art to have a clean install.
---------- Post added at 03:33 AM ---------- Previous post was at 02:47 AM ----------
mrmazak said:
dont panic. this is minor bug. Easiest way to solve is to flash stock recovery. and do factory reset from there.
You can install image from twrp or fastboot, even spflashtool.
It is from the flag that is set into para(misc) partition.
You can clear it manually with terminal also, or even use one of the othe rtwrp images I shared. One with "misc" in the file name.
If you use one of those recoveries and do reset will also clear that reboot condition
Click to expand...
Click to collapse
YO! Oaky so basic laly when i flashed that misc recovery IT BOOTED!!!!! thank you soo much dude, your the best!

Root LG Velvet (LM-G900EM)

Finally got root on LG-Velvet LM-G900EM
Here is how i did.
I know...this is finally little bit complicated, but i dont want to copy something that possibly affects copyrights or other stuff.
Here is all that i've learned and done.
So you should be able to root also.
Prerequisites:
(allways have a valid backup)
- Unlocked LG-Velvet-Bootloader (on android device)
- Installed Python (on pc):
https://www.python.org/
- Unpacked Steadfast kdz-tools (on pc):
https://github.com/WildOne69/kdztools
(Modify the undz.py: Put a # in line 26. This should look like this:"#import zstandard as zstd"
Otherwhise you will get an error:"ModuleNotFoundError: No module named 'zstandard'"
- Downloaded Velvet Stock-Rom (kdz) (on pc)
http://lg-roms.com/lg-firmware/lmg900em/g900em10c/9081
1. Download the kdz-rom from lg-roms (on pc)
(this uses a special download-tool which may be spain)
Finally you should have something like:
G900EM10f_00_0716.kdz
2. Extract a dz-file from the kdz-file. (on pc)
Go to the directory where you've stored the kdz-tools.
example:
python unkdz.py -f G900EM10f_00_0716.kdz -x
(this gains something like G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz in a subdirectory)
3. Extract the boot.img from the extracted dz-file. (on pc)
example:
python undz.py -f c:G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz -s 40
..now you've got a boot_a.image hopefully in a subdirectory.
This is the original boot.img
4. Copy the boot.img to your mobile. (from pc to android device)
5. Run Magisk and patch the extracted boot.img (on android device)
6. Copy the magisk_patched.img to your computer again. (from android device to pc)
7. adb reboot bootloader (on pc)
Keep in mind that the Velvet is an A/B device, so we need to flash the boot.img twice.
8. fastboot flash boot_a magisk_patched.img
(on pc)
9. fastboot flash boot_b magisk_patched.img
(on pc)
10. fastboot reboot
(on pc)
11. Open Magisk and pray that you've root.
(on android device)
Have fun.
BR
Mike
PS:
Be careful locking your bootloader afterwards. As i've observed locking the bootloader again resets the mobile back to factory-defaults...so all your work has been gone.
I'm not responsible if you brick your device or it takes harm in any case.
Updates: As LG launched updates twice meanwhile i was forced to patch the boot-partitions again.
Simpliest way to do the updates with root:
- Start the update with LG-Bridge.
- After the download of the new KDZ is complete copy it out of the temp-directory (to extract the boot_a.img later)
- Do the phone-update with LG-Bridge. (Now your phone is in an unrooted state again)
- proceed with steps 2-11
- Jobs done (Actual android-version rooted)

Is there anyway to get this to work with lg-G900UM

Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.

MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
Guys, can you upload the stock ringtones ?
Thks

Nice work OP. Works like a charm. I remember the pre-Nougat days when rooting an Android device was, for the most part, a simple affair. Nowadays, with A/B partitions, Forward Error Correction (FEC), system-as-root, etc., rooting is tedious to say the least. Nice job figuring this one out. :good:

Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?

Bandetos said:
Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?
Click to expand...
Click to collapse
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.

MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
it doesn't working
maybe attach the boot.img file

if you check the version of python you got:
Python.3.8_3.8.1776.0
?
to be honest...dont want to take care on a file-store in the internet.

LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )

Either way, it's good to see that we at least have a few people trying to figure out things with this device. Honestly, I still carry my Redmi Note 7 Pro with me every day because of how much I miss being able to download a custom rom etc.
MikGx said:
LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )
Click to expand...
Click to collapse

Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.

JackTheMan18 said:
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.
Click to expand...
Click to collapse
I did that on an LM-G900EM. (No dual sim)
As i did it just usin the stock-rom, theoretically dual sim capability shoudnt get lost.
All this stands and falls with the possibility to unlock the bootloader.
If LG provides an unlock-code the rest should work.

Good
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G

BruceLee131 said:
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G
Click to expand...
Click to collapse
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.

MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
I'm also getting this error. I did try a second time following your steps to a tee and still getting the same error.

MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
Hi, I have bought LG Wing. I have entered into Developer Mode and I have activated OEM unlocked option. So do I need a bootloader unlock code? Can I root LG Wing with your instructions?

How did you get adb to recognize your device once you put it in download mode?

MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
I'm sorry if this is a dumb question, but if it isn't possible to get an unlock code for the G900UM (U.S. model), is there a way to gain SU status/root without unlocking the bootloader? I'm sure there's no exploit to unlock the bootloader without LG code, but I saw in some other threads (different makes/models) discussion of gaining SU via fastboot without unlocking the bootloader? So if my main concern is knowing everything that is on my phone and eliminating privacy/security vulnerabilties, can I gain SU status without unlocking the bootloader?

MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
I got the unlock.bin file from LG.
I'm not afraid to flash any partition...
it's simply impossible to flash twrp-3.4.0-g900em-dom133.imgù
writing 'recovery'...
FAILED (remote: Cannot flash this partition in unlocked state)
And even boot with that recovery
downloading 'boot.img'...
OKAY [ 0.718s]
booting...
FAILED (remote: BootImage is Incomplete)
Finally i'm not able to extract boot.img form LG kdz stock rom

How To Guide [FASTBOOT] [ROM] [PC REQUIRED] [OP9] Stock OOS 11.2.2.2AA

Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...​
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- Ensure you're using the LATEST version of SDK platform tools (from Android Studio) on your PC or you might be stuck at a later step (specifically, when rebooting to Fastbootd)
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Optional steps, at end:
Once you've successfully booted to 11.2.2.2, I would recommend that you download the latest full OTA from OnePlus' support page (11.2.9.9 is in the DOWNLOAD LINKS, below) and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this local upgrade ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash. So now, both slots A and B should have solid functioning ROMs.
Good luck!
DOWNLOAD LINKS:
Fastboot ROM 11222AA zip:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Stock Full OTA 11299AA zip
https://www.androidfilehost.com/?fid=7161016148664810093
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)

++This post is ONLY for those unfortunate souls who see <awaiting any device> in Fastboot mode for minutes while following the Instructions in Post #1++
- Once your OP9 screen shows Fastboot mode and you see <awaiting any device> for several minutes
- hit CTRL C to stop the flashing process
- go to Device Manager in Windows and look for the yellow-triangled ! device. LE2115 -- that's your unrecognized Fastboot device
- right click it and select update driver
- select "Browse my computer for drivers" and then "Let me pick from a list..."
- select ADB interface (and you might further need to pick the Universal or Samsung Android device) and install it
- once that driver window closes, go back to the PowerShell window
- type fastboot devices
=if you see a small string of characters, you're good. Go to the last step!
=if you only get another prompt, you need to unplug the OP9 and then reconnect it. Since you just updated the driver, Windows should now recognize and engage the driver for the Fastboot mode OP9. Confirm this by looking for a small string once you again type fastboot devices
=if you still don't get a small string confirming device recognition, try updating the driver again. And again. Because, you know, Windows. If you never succeed in getting Windows to recognize the OP9 in Fastboot mode, you might need to try downloading another ADB driver. But you really can't go further in this flashing process till the OP9 is recognized in Fastboot mode. Only then can you go on...
- the last step! Type rescuefastbootd.bat to complete the flashing process in Fastboot mode. With any luck, your OP9 will now flash the 2nd set of images and then reboot normally, on OOS 11.2.2 in slot B, and you will see the orbiting dots of a normal OOS boot. When you do, you can unplug your phone from the PC. Success!!

OPTIONAL: if you're reading this before catastrophe, I would suggest that you ensure you have working drivers for both Bootloader and Fastboot modes. (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) After driver installation on your PC, steps to do this look like:
- Settings>About Phone> tap Build number 7 times, then
- Settings>System>Developer Options>toggle Advanced Reboot.
- Hold the power button, select the 3-dot menu icon, tap Bootloader
- connect OP9 to your PC, and Windows 10 should install the right driver.
- On your PC, navigate to the Fastboot ROM downloaded unzipped folder.
- double-click cmd.bat and a PowerShell window opens.
- in the PowerShell window, type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager
- type: fastboot reboot fastboot
and your OP9 will reboot into Fastbootd mode; when you see a splash screen with a choice of languages...
- type: fastboot devices
=if you get a small string of identifying characters, you're good.
=if you get nothing but a command prompt, you need to install adb drivers in Windows' Device Manager (read over Post #2). Once that's done successfully (typing: fastboot devices and getting an identifying string), you want to reboot normally. Success!!

Yeah. Just in case.

Thank you

Nice write up, friend! Thank you for taking the time to do so.

reaper000 said:
Greetings,
I've appreciated @Slikkster2k's terrific thread that explains and walks you through fastboot recovery of a OnePlus 9. To make it more convenient, I've taken his process and adapted @mauronofrio's OnePlus 8 fastboot ROM to post a fastboot ROM zip for the OnePlus 9.
PLEAE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!!
AND BE WARNED THAT YOU WILL WIPE INTERNAL STORAGE COMPLETELY.
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
THIS IS THE LAST DITCH ATTEMPT BEFORE USING AN MSM TOOL TO GET YOU A BOOTING DEVICE...​
Instructions:
- On your PC, install bootloader drivers for OP9 (I used the Universal ADB driver found here: https://adb.clockworkmod.com/) and afterwards, you may need to use Device Manager in Windows' control panel to "update driver" for an unrecognized OP9 in Bootloader and Fastbootd modes.
- On your PC, download the Fastboot ROM zip from the download link below.
- On your PC, unzip downloaded file
- On your PC, navigate to its now-uncompressed folder
- Reboot your OnePlus 9 to bootloader mode. From a crashed state, you might need to hold down the power button for an ungodly amount of time (think 30 seconds) to fully shut down. Then hold down power and both volume buttons until you see the Bootloader screen
- Connect the OP9 to your PC
- On your PC in the uncompressed folder, double-click cmd.bat
- In the PowerShell window that opens, type fastboot devices
=if you see a small string of characters, you're good
=if you only get another prompt, you need to install adb drivers (see 1st step) before going any further
- type flash-all_slotb.bat
- type y
= because there's almost NO CIRCUMSTANCE that a fastboot ROM successfully flashes without wiping your data. As in deleting, formatting, absolutely annihilating everything on your device. Now if you have a perfectly functional device, then maybe you can avoid wiping. But that's not why you're here, are you? You've buggered your phone and are desperately looking for someway to get it to boot normally, before calling OnePlus and begging for an MSM tool. So if you're here, take a deep breath and kiss your data goodbye.
= flashing the ROM to slot B and then booting slot B gives you a better shot at one-step flashing success. It's been my experience that f you flash to slot A, some files simply don't flash and then you're left having to flash to slot B anyways.
= at some point, your OP9 will reboot to Fastboot mode for more flashing...but if you happen to see <awaiting any device> for several minutes, it means that the OP9 in Fastboot mode is not being recognized by Windows due to a driver issue, and for those unlucky folks, go to Post #2
= if your OP9 continues to blissfully flash in Fastboot mode, just let it go...
- Success is when you see a final reboot, and the twirling dots of a normal OOS boot, at which point you can finally unplug your OP9 from your PC.
Good luck!
DOWNLOAD LINK:
Fastboot OOS_11222AA_stock.zip | by reaper000 for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Credits:
- @Slikkster2k
- @mauronofrio (please un-retire!)
Click to expand...
Click to collapse
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).

Fireblast3 said:
Thank you very much, if not for this I would have to wait for my device to arrive from oneplus(cancel my request).
Click to expand...
Click to collapse
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!

reaper000 said:
Glad to help.
Here's your next steps:
I would recommend that you download the full OTA of 11.2.4.4 from OnePlus' support page and place it on your internal SD card's "root" directory (note that this is not the true root directory of internal storage accessible only if you are rooted with Magisk)
Then Settings>system>system updates and tap the gear icon (top right of screen) to do a local upgrade.
After Fastboot ROM flashing on slot B, this ensures that slot A will be overwritten by the full stock ROM, ending whatever badness was on slot A that led you to need a Fastboot ROM flash.
Good luck!
Click to expand...
Click to collapse
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"

Fireblast3 said:
Thanks for the tip but the dam oneplus page is giving me this error "Parameter error"
Click to expand...
Click to collapse
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip

reaper000 said:
Try the direct link...?
https://oxygenos.oneplus.net/OnePlus9Oxygen_22.O.07_OTA_0070_all_2104122241_e0f2a4d74c3844b4.zip
Click to expand...
Click to collapse
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.

Will this convert tmobile variant to global?

infamousvincci said:
Will this convert tmobile variant to global?
Click to expand...
Click to collapse
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.

reaper000 said:
Let me quote the OP:
THIS IS NOT MEANT FOR BRANDED DEVICES, OR TO SWITCH REGIONAL TYPES, OR AS AN UPGRADE PATH.
It wasn't intended to convert Tmo to Global.
If I recall correctly, there were reports of softbricks in previous OnePlus devices when Fastboot ROMs were tried as conversion tools, necessitating either MSM tool deployment or return to manufacturer.
Click to expand...
Click to collapse
ooofff. gotcha. Thank you so much!

Fireblast3 said:
Thanks, I contact oneplus support and it seem like they are updating their Software Upgrade section.
Click to expand...
Click to collapse
I've provided an AFH mirror for OOS' full OTA 11.2.4.4AA for convenient download.
Also, the recommendation I gave you is also now added to the OP.

I appreciate this. It would have definitely helped me back when I had these issues. Now it's here. I'm honestly scared to flash anything on this device.

I've redone the original post to reflect OnePlus' publication of 11.2.7.7AA as a downloadable full OTA and provided a mirror on AFH

My device bricked

I'm sorry to hear that. I'm not sure how much I can help, but perhaps you can please provide details? (device model, what circumstances led you here, what version of oos, what you've already tried, etc)

Please upload to MEGA or Google Drive or actually anywhere else as AFH is so slow it gives me 3 days for estimated download time. Thank you. Somebody sending a mirror would be much appreciated.