excited that there will finally be one for fully paid version <3 with all the tmobile and metro unlockings
Metro variant images? I believe we already have those here:
ah my bootloader is still locked and its brickedMetro variant images? I believe we already have those here:
I could be wrong, but I believe if your bootloader is still locked, your only option is the MSMDownload Tools.
We don't have those for the Metro variant yet. You could try contacting OnePlus customer support and requesting a remote session to repair your phone, that will get you a copy of the MSMDownload tools (please share them) for your variant.
I believe that the Metro and T-Mobile variants are actually the exact same phone, since they both share the same codename. I would say that users with Metro devices should try flashing the T-Mobile MSM tools if they need to unbrick their phone. If it works, the phone should still be Metro branded anyway.
In addition, while looking around through the MSM files, I found a string of code that suggests that the T-Mobile, Metro, and Assurance (Sprint?) branded phones all use the same software:
XML:
<SupportMultiTarget>
<Target ID="108" Desc="ASSURANCE" />
<Target ID="106" Desc="METRO" />
<Target ID="101" Desc="TMO" />
</SupportMultiTarget>I think the tech support in India is more interested in collecting positive reviews than fixing issues..
I'm sitting with a phone that I only used one day .. hopping the tool will make its way on this forum .. if not might sound like I wasted $270... anyways this is the last oneplus I'm buying
My OnePlus Nord N200 unlocked variant self soft-bricked, but I fixed it, here's the story:
I updated the software using the system update OTA, allowed it to reboot, and it said the update was done.
(However, it was not, as the second slot merge update is done silently in the background, as part of the seamless A/B model.)
I then allowed oem unlocking, rebooted the phone, and used fastboot to unlock the bootloader.
The phone automatically wiped some partitions as part of the unlock, but was then stuck in fastboot or fastbootd mode upon reboot(s).
I contacted OnePlus, but they were not willing to remotely fix my device (release the MSM tool) and instead wanted me to ship the phone to them.
We have the full OTA download available from OnePlus:
www.oneplus.com
and we can use payload_dumper python scripts by Gregory Montoir to extract the individual .img files from the OTA.
www.droidwin.com
but the important ones (system, vendor, etc) are not flashable in fastboot (only) mode due to the use of dynamic partitions (super.img). (see my edit at the bottom)
Forcing the merge to complete did not work, switching slots did not work, nor did reflashing boot.img fix it.
It turns out bundling the seamless A/B partitions together into a single dynamic partition ruins the redundancy of the seamless A/B model!
Finally, I took the idea from PopCaps1996:
and used another Nord N200 phone which was working, to download and run Partitions backup & restore.
play.google.com
This app has the ability to extract the super.img in its entirety from a working phone, and fastboot is able to flash this image directly into the dynamic partitions. (make sure you update to the latest fastboot).
take the super.tar.gz from Partitions backup and untar/ungzip it to the .img.
Copy it to the computer and fastboot flash it.
fastboot flash super super.img.
That fixed it for me!
So for those who have working fastboot, an unlocked bootloader, and can get the super.img (3.2GB tar.gzip) you can recover your phone like I did!
Edit:
I completed my recovery in fastboot mode only, but there is the ability to reboot into fastbootd mode (recovery mode with fastbootd), which is able to handle the dynamic partitions, and may work from the OTA .img files directly, avoiding the need for an extracted super.img file.
I updated the software using the system update OTA, allowed it to reboot, and it said the update was done.
(However, it was not, as the second slot merge update is done silently in the background, as part of the seamless A/B model.)
I then allowed oem unlocking, rebooted the phone, and used fastboot to unlock the bootloader.
The phone automatically wiped some partitions as part of the unlock, but was then stuck in fastboot or fastbootd mode upon reboot(s).
I contacted OnePlus, but they were not willing to remotely fix my device (release the MSM tool) and instead wanted me to ship the phone to them.
We have the full OTA download available from OnePlus:
Software Upgrade - OnePlus.com
Get the latest OxygenOS updates for your device.OxygenOS is always evolving. Learn about the latest features and improvements, and get even more out of your device.
and we can use payload_dumper python scripts by Gregory Montoir to extract the individual .img files from the OTA.
How to Extract Stock Boot.img from OnePlus OxygenOS Stock ROM
In this tutorial, we will show you how to extract the stock boot.img from OnePlus OxygenOS stock ROM and use it for rooting via Magisk
www.droidwin.com
payload_dumper
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
but the important ones (system, vendor, etc) are not flashable in fastboot (only) mode due to the use of dynamic partitions (super.img). (see my edit at the bottom)
Forcing the merge to complete did not work, switching slots did not work, nor did reflashing boot.img fix it.
It turns out bundling the seamless A/B partitions together into a single dynamic partition ruins the redundancy of the seamless A/B model!
Finally, I took the idea from PopCaps1996:
and used another Nord N200 phone which was working, to download and run Partitions backup & restore.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
This app has the ability to extract the super.img in its entirety from a working phone, and fastboot is able to flash this image directly into the dynamic partitions. (make sure you update to the latest fastboot).
take the super.tar.gz from Partitions backup and untar/ungzip it to the .img.
Copy it to the computer and fastboot flash it.
fastboot flash super super.img.
That fixed it for me!
So for those who have working fastboot, an unlocked bootloader, and can get the super.img (3.2GB tar.gzip) you can recover your phone like I did!
Edit:
I completed my recovery in fastboot mode only, but there is the ability to reboot into fastbootd mode (recovery mode with fastbootd), which is able to handle the dynamic partitions, and may work from the OTA .img files directly, avoiding the need for an extracted super.img file.
Last edited:
Hi "oCAPTCHA" I also have The Global Unlocked N200 and I am experiencing the same exact issue. I been up for 3 Nights surfacing resolutions but I fastbootd doesn't allow flashing the system ( No Partition error ).... I tried Just about everything but it seems you solved the issue. The Problem is I don't have another N200 nor can I get one. Is there anyway you can help me out with that partition and out of generosity I will paypal you a Donation ?
Thanks Alot.
MichaelBurrola,
I am hestiant to upload my partitions for legal liability reasons.
However, I suspect I may be able to help you another way, by using fastbootd commands and the OTA.
Are you sure you are in fastbootd mode, and are using an up to date fastboot? (older versions do not support dynamic partition commands!)
Here is a good source for fastboot.
androidsdkoffline.blogspot.com
"Android SDK Platform Tools"
Fastboot tutorial
Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and rebooting into fastbootd using the poorly named command:
fastboot reboot fastboot.
Next run
fastboot getvar all
check which slot is active (you could attempt to switch slots, but that didn't fix it for me)
and check your partition list against mine, particularly looking for your slot's set of super's sub-partitions
(assuming slot b) system_b, system_ext_b, odm_b, product_b, vendor_b
Partition list from OnePlus Nord N200 unlocked version 11.0.2.0.DE17AA in fastbootd mode
-cow (Copy On Write) partitions are unneeded and usually need to be deleted for space.
fastboot delete-logical-partition system_b-cow
Create any missing sub-partitions manually
fastboot create-logical-partition system_b 0x10000
fastboot create-logical-partition system_ext_b 0x10000
fastboot create-logical-partition odm_b 0x10000
fastboot create-logical-partition product_b 0x10000
fastboot create-logical-partition vendor_b 0x10000
(I don't believe the size must be correct, as they will resize when you flash them)
And then flash the partitions using the extracted OTA files from OnePlus
(system_b, system_ext_b, odm_b, product_b, vendor_b)
fastboot flash system_b system.img
fastboot flash system_ext_b system_ext.img
fastboot flash odm_b odm.img
fastboot flash product_b product.img
fastboot flash vendor_b vendor.img
You probably don't need to worry about boot_b since you have fastbootd working.
Also vbmeta and vbmeta_system (verified boot metadata), since verified boot turned off when your bootloader unlocked.
I am hestiant to upload my partitions for legal liability reasons.
However, I suspect I may be able to help you another way, by using fastbootd commands and the OTA.
Are you sure you are in fastbootd mode, and are using an up to date fastboot? (older versions do not support dynamic partition commands!)
Here is a good source for fastboot.
All Android SDK Latest Stable Versions
Android SDK Packages Latest Versions This page provides you all latest versions of available Android SDK Packages from SDK Tools, Compilers,...
androidsdkoffline.blogspot.com
Fastboot tutorial
Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and rebooting into fastbootd using the poorly named command:
fastboot reboot fastboot.
Next run
fastboot getvar all
check which slot is active (you could attempt to switch slots, but that didn't fix it for me)
and check your partition list against mine, particularly looking for your slot's set of super's sub-partitions
(assuming slot b) system_b, system_ext_b, odm_b, product_b, vendor_b
Partition list from OnePlus Nord N200 unlocked version 11.0.2.0.DE17AA in fastbootd mode
-cow (Copy On Write) partitions are unneeded and usually need to be deleted for space.
fastboot delete-logical-partition system_b-cow
Create any missing sub-partitions manually
fastboot create-logical-partition system_b 0x10000
fastboot create-logical-partition system_ext_b 0x10000
fastboot create-logical-partition odm_b 0x10000
fastboot create-logical-partition product_b 0x10000
fastboot create-logical-partition vendor_b 0x10000
(I don't believe the size must be correct, as they will resize when you flash them)
And then flash the partitions using the extracted OTA files from OnePlus
(system_b, system_ext_b, odm_b, product_b, vendor_b)
fastboot flash system_b system.img
fastboot flash system_ext_b system_ext.img
fastboot flash odm_b odm.img
fastboot flash product_b product.img
fastboot flash vendor_b vendor.img
You probably don't need to worry about boot_b since you have fastbootd working.
Also vbmeta and vbmeta_system (verified boot metadata), since verified boot turned off when your bootloader unlocked.
Last edited:
Oppo A93 MSM
Isn't this a rebranded Oppo A93? Any chance this would work for the bootloader locked, unlocked version?
Isn't this a rebranded Oppo A93? Any chance this would work for the bootloader locked, unlocked version?
I have a soft bricked device from an update issue as well. After thoroughly reading your post I have discovered I have several missing partitions. Mainly every single one necessary for the successful flashing of system, product, vendor, odm, and system ext.MichaelBurrola,
I am hestiant to upload my partitions for legal liability reasons.
However, I suspect I may be able to help you another way, by using fastbootd commands and the OTA.
Are you sure you are in fastbootd mode, and are using an up to date fastboot? (older versions do not support dynamic partition commands!)
Here is a good source for fastboot.
"Android SDK Platform Tools"All Android SDK Latest Stable Versions
Android SDK Packages Latest Versions This page provides you all latest versions of available Android SDK Packages from SDK Tools, Compilers,...
Fastboot tutorial
Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and rebooting into fastbootd using the poorly named command:
fastboot reboot fastboot.
Next run
fastboot getvar all
check which slot is active (you could attempt to switch slots, but that didn't fix it for me)
and check your partition list against mine, particularly looking for your slot's set of super's sub-partitions
(assuming slot b) system_b, system_ext_b, odm_b, product_b, vendor_b
Partition list from OnePlus Nord N200 unlocked version 11.0.2.0.DE17AA in fastbootd mode
-cow (Copy On Write) partitions are unneeded and usually need to be deleted for space.
fastboot delete-logical-partition system_b-cow
Create any missing sub-partitions manually
fastboot create-logical-partition system_b 0x10000
fastboot create-logical-partition system_ext_b 0x10000
fastboot create-logical-partition odm_b 0x10000
fastboot create-logical-partition product_b 0x10000
fastboot create-logical-partition vendor_b 0x10000
(I don't believe the size must be correct, as they will resize when you flash them)
And then flash the partitions using the extracted OTA files from OnePlus
(system_b, system_ext_b, odm_b, product_b, vendor_b)
fastboot flash system_b system.img
fastboot flash system_ext_b system_ext.img
fastboot flash odm_b odm.img
fastboot flash product_b product.img
fastboot flash vendor_b vendor.img
You probably don't need to worry about boot_b since you have fastbootd working.
Also vbmeta and vbmeta_system (verified boot metadata), since verified boot turned off when your bootloader unlocked.
When attempting to create the partitions in fastbootd I get the return of "expected argument" without being able to create the partitions to flash the images to super rendering the device stuck in fastboot.
Jaybone073,
Are you sure that you are using a recent Fastbootd?
(if using linux, run your terminal in the downloaded folder, and run the local version of fastboot using ./fastboot instead of the older version installed system wide from a repo)
The older versions of Fastboot do not understand virtual / logical partitions, so would give this result of them missing.
You can't be missing every single virtual partition and still have a semi-working soft-bricked phone.
I accidentally flashed vendor with a nearly blank image while working on GSI's, (Why did google bundle a vendor.img with their AOSP GSI?) and it hard-bricked my device. Without the drivers in vendor, the phone would only go so far as the unlocked bootloader warning, despite the other partitions being correct (only EDL mode would boot).
Your phone must have a working boot.img and vendor.img for you to have working fastbootd recovery environment.
I sent that hard bricked phone into OnePlus a few days ago, after confirming again that they still will not release their MSM tools for the retail / unlocked variant.
Here is a good source for fastboot.
androidsdkoffline.blogspot.com
"Android SDK Platform Tools"
Once you get Fastbootd working, you can simply flash the partitions from the OTA. If you have a backed up super.img, you could flash that instead using regular Fastboot mode.
Are you sure that you are using a recent Fastbootd?
(if using linux, run your terminal in the downloaded folder, and run the local version of fastboot using ./fastboot instead of the older version installed system wide from a repo)
The older versions of Fastboot do not understand virtual / logical partitions, so would give this result of them missing.
You can't be missing every single virtual partition and still have a semi-working soft-bricked phone.
I accidentally flashed vendor with a nearly blank image while working on GSI's, (Why did google bundle a vendor.img with their AOSP GSI?) and it hard-bricked my device. Without the drivers in vendor, the phone would only go so far as the unlocked bootloader warning, despite the other partitions being correct (only EDL mode would boot).
Your phone must have a working boot.img and vendor.img for you to have working fastbootd recovery environment.
I sent that hard bricked phone into OnePlus a few days ago, after confirming again that they still will not release their MSM tools for the retail / unlocked variant.
Here is a good source for fastboot.
All Android SDK Latest Stable Versions
Android SDK Packages Latest Versions This page provides you all latest versions of available Android SDK Packages from SDK Tools, Compilers...
"Android SDK Platform Tools"
Once you get Fastbootd working, you can simply flash the partitions from the OTA. If you have a backed up super.img, you could flash that instead using regular Fastboot mode.
Last edited:
MichaelBurrola,
I am hestiant to upload my partitions for legal liability reasons.
However, I suspect I may be able to help you another way, by using fastbootd commands and the OTA.
Are you sure you are in fastbootd mode, and are using an up to date fastboot? (older versions do not support dynamic partition commands!)
Here is a good source for fastboot.
"Android SDK Platform Tools"All Android SDK Latest Stable Versions
Android SDK Packages Latest Versions This page provides you all latest versions of available Android SDK Packages from SDK Tools, Compilers,...
Fastboot tutorial
Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and rebooting into fastbootd using the poorly named command:
fastboot reboot fastboot.
Next run
fastboot getvar all
check which slot is active (you could attempt to switch slots, but that didn't fix it for me)
and check your partition list against mine, particularly looking for your slot's set of super's sub-partitions
(assuming slot b) system_b, system_ext_b, odm_b, product_b, vendor_b
Partition list from OnePlus Nord N200 unlocked version 11.0.2.0.DE17AA in fastbootd mode
-cow (Copy On Write) partitions are unneeded and usually need to be deleted for space.
fastboot delete-logical-partition system_b-cow
Create any missing sub-partitions manually
fastboot create-logical-partition system_b 0x10000
fastboot create-logical-partition system_ext_b 0x10000
fastboot create-logical-partition odm_b 0x10000
fastboot create-logical-partition product_b 0x10000
fastboot create-logical-partition vendor_b 0x10000
(I don't believe the size must be correct, as they will resize when you flash them)
And then flash the partitions using the extracted OTA files from OnePlus
(system_b, system_ext_b, odm_b, product_b, vendor_b)
fastboot flash system_b system.img
fastboot flash system_ext_b system_ext.img
fastboot flash odm_b odm.img
fastboot flash product_b product.img
fastboot flash vendor_b vendor.img
You probably don't need to worry about boot_b since you have fastbootd working.
Also vbmeta and vbmeta_system (verified boot metadata), since verified boot turned off when your bootloader unlocked.
I do not have a backed up super.img I am guessing that it is unique to each device and cannot be flashed via fastbootJaybone073,
Are you sure that you are using a recent Fastbootd?
(if using linux, run your terminal in the downloaded folder, and run the local version of fastboot using ./fastboot instead of the older version installed system wide from a repo)
The older versions of Fastboot do not understand virtual / logical partitions, so would give this result of them missing.
You can't be missing every single virtual partition and still have a semi-working soft-bricked phone.
I accidentally flashed vendor with a nearly blank image while working on GSI's, (Why did google bundle a vendor.img with their AOSP GSI?) and it hard-bricked my device. Without the drivers in vendor, the phone would only go so far as the unlocked bootloader warning, despite the other partitions being correct (only EDL mode would boot).
Your phone must have a working boot.img and vendor.img for you to have working fastbootd recovery environment.
I sent that hard bricked phone into OnePlus a few days ago, after confirming again that they still will not release their MSM tools for the retail / unlocked variant.
Here is a good source for fastboot.
All Android SDK Latest Stable Versions
Android SDK Packages Latest Versions This page provides you all latest versions of available Android SDK Packages from SDK Tools, Compilers...
androidsdkoffline.blogspot.com
"Android SDK Platform Tools"
Once you get Fastbootd working, you can simply flash the partitions from the OTA. If you have a backed up super.img, you could flash that instead using regular Fastboot mode.
Also my device info shows this:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
which means when trying to create a partition I get this error"
fastboot create-logical-partition system_b 0x10000
Creating 'system_b' FAILED (remote: 'Could not open super partition')
fastboot: error: Command failed
And I am running the latest version of adb and fastboot. I thought I was but apparently it was JUST updated.
Last edited:
I am in fastbootd but it keeps saying that "< waiting for any device >" although I have all the necessary drivers on the system. I can do adb reboot bootloader and it works fine. From there, I can do fastboot devices and so on... It works.
But, my device is not getting recognized in the fastbood (where you see Advanced and Exit buttons) mode.
When I run "fastboot reboot fastboot", it goes back to fastbootd screen, where I can go to Advanced and Reboot to fastboot options are there. But, the device is not getting recognized by the PC.
EDIT: I have the latest fastboot: fastboot version 31.0.3-7562133
EDIT 2: The build on my Nord N2005G is 11.0.1.9.DE18CB. Does this procedure on this build?
Errors with the device not being recognized or authorized are due to not having:
1. USB debugging enabled.
2. authorized the computer's certificate on the USB debugging popup when the phone is running in the OS and connected to the computer.
3. sufficient permissions on the computer.
under linux, the first time ADB is run, it starts a daemon to connect using the permissions of that command.
so the first time in a session you run ADB, you must use sudo to give the daemon root privileges.
"sudo ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached"
also, the instructions should work for any build.
1. USB debugging enabled.
2. authorized the computer's certificate on the USB debugging popup when the phone is running in the OS and connected to the computer.
3. sufficient permissions on the computer.
under linux, the first time ADB is run, it starts a daemon to connect using the permissions of that command.
so the first time in a session you run ADB, you must use sudo to give the daemon root privileges.
"sudo ./adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached"
also, the instructions should work for any build.
Too many failed boot attempts deleted your encryption and switched your active slots. From fastboot run "fastboot -w" (this will format /data and wipe metadata), after this you switch your active slot using adb commands and see if you can get fastbootd then.
Anyone able to provide a super.img file? Currently I have a bricked device after flashing a blank vendor.img while installing a GSI. I have extracted the firmware and am able to flash the majority of images except any related to the super.img.
Is the super partition the same for both slot A & B or is each slot individual? If it's individual to each slot then slot A should still be available since B was deleted during GSI install, correct!?
Any help flashing the main images would be appreciated.
Also, if I am unable to get a copy of the super partition, would flashing the images that are successful and using a GSI work?
Is the super partition the same for both slot A & B or is each slot individual? If it's individual to each slot then slot A should still be available since B was deleted during GSI install, correct!?
Any help flashing the main images would be appreciated.
Also, if I am unable to get a copy of the super partition, would flashing the images that are successful and using a GSI work?
Top Liked Posts
-
There are no posts matching your filters.
-
5
11.0.1.5
Oh yeah here's the link: https://drive.google.com/file/d/1MCQwFabFYXZqw1xGT0P8-PV6FV2Fnj-V/view?usp=sharing4T-Mobile Variant MSM Tools .7z archive:
I've included a .md5 and .sfv file in the folder to verify the archive after downloading (they just check the .7z, NOT the extracted files).
All basic "I'm not responsible if you brick your phone with this" warnings apply... Even if they're a bit 'closing the barn door after the horse got out' as far as the intended end-users are concerned, lol.
*edit- I created an account on androidfilehost, and requested dev status. Once that clears I'll upload a copy to there as well.4
We haven't even received MSM tools for the unlocked variant yet, let alone have some figure out how to cross-flash between both variants. Be patient
