Captured this OTA returning to Android 12 after nearly bricking my T-MOBILE branded N200 and using MSMtool to get back to stock.
https://android.googleapis.com/packages/ota-api/package/f706ca0ab8556311d76c565135816d3873a4a15c.zip
This is a Full OTA for the N200 T-Mobile variant DE2118
This can be used to return to stock from a A11 or A12 fw based custom ROM.
YOU MUST BE ABLE TO ACCESS FASTBOOTD
if you can not access fastbootd, install LineageOS recovery and ensure it is functional before using this method.
First extract fastboot flashable images from the stock OTA.zip using a tool such as theses:
Linux - https://github.com/vm03/payload_dumper
MacOS/Linux/Windows (definitely faster than vm03) - https://forum.xda-developers.com/t/...d-ota-payload-dumper-written-in-rust.4573841/
ensure that the output .img files are in a directory that you can use fastboot commands in (ex. platform-tools)
fastboot reboot fastboot
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition vendor_dlkm_a
fastboot delete-logical-partition vendor_dlkm_b
fastboot delete-logical-partition my_carrier_a
fastboot delete-logical-partition my_carrier_b
fastboot delete-logical-partition my_engineering_a
fastboot delete-logical-partition my_engineering_b
fastboot delete-logical-partition my_heytap_a
fastboot delete-logical-partition my_heytap_b
fastboot delete-logical-partition my_manifest_a
fastboot delete-logical-partition my_manifest_b
fastboot delete-logical-partition my_product_a
fastboot delete-logical-partition my_product_b
fastboot delete-logical-partition my_region_a
fastboot delete-logical-partition my_region_b
fastboot delete-logical-partition my_stock_a
fastboot delete-logical-partition my_stock_b
fastboot delete-logical-partition odm_a-cow
fastboot delete-logical-partition odm_b-cow
fastboot delete-logical-partition system_a-cow
fastboot delete-logical-partition system_b-cow
fastboot delete-logical-partition system_ext_a-cow
fastboot delete-logical-partition system_ext_b-cow
fastboot delete-logical-partition product_a-cow
fastboot delete-logical-partition product_b-cow
fastboot delete-logical-partition vendor_a-cow
fastboot delete-logical-partition vendor_b-cow
fastboot delete-logical-partition my_carrier_a-cow
fastboot delete-logical-partition my_carrier_b-cow
fastboot delete-logical-partition my_engineering_a-cow
fastboot delete-logical-partition my_engineering_b-cow
fastboot delete-logical-partition my_heytap_a-cow
fastboot delete-logical-partition my_heytap_b-cow
fastboot delete-logical-partition my_manifest_a-cow
fastboot delete-logical-partition my_manifest_b-cow
fastboot delete-logical-partition my_product_a-cow
fastboot delete-logical-partition my_product_b-cow
fastboot delete-logical-partition my_region_a-cow
fastboot delete-logical-partition my_region_b-cow
fastboot delete-logical-partition my_stock_a-cow
fastboot delete-logical-partition my_stock_b-cow
fastboot create-logical-partition system_a 1
fastboot flash system_a system.img
fastboot create-logical-partition system_ext_a 1
fastboot flash system_ext_a system_ext.img
fastboot create-logical-partition product_a 1
fastboot flash product_a product.img
fastboot create-logical-partition vendor_a 1
fastboot flash vendor_a vendor.img
fastboot create-logical-partition odm_a 1
fastboot flash odm_a odm.img
fastboot create-logical-partition my_product_a 1
fastboot flash my_product_a my_product.img
fastboot create-logical-partition my_engineering_a 1
fastboot flash my_engineering_a my_engineering.img
fastboot create-logical-partition my_stock_a 1
fastboot flash my_stock_a my_stock.img
fastboot create-logical-partition my_company_a 1
fastboot flash my_company_a my_company.img
fastboot create-logical-partition my_carrier_a 1
fastboot flash my_carrier_a my_carrier.img
fastboot create-logical-partition my_region_a 1
fastboot flash my_region_a my_region.img
fastboot create-logical-partition my_heytap_a 1
fastboot flash my_heytap_a my_heytap.img
fastboot create-logical-partition my_preload_a 1
fastboot flash my_preload_a my_preload.img
fastboot create-logical-partition my_manifest_a 1
fastboot flash my_manifest_a my_manifest.img
fastboot create-logical-partition my_bigball_a 1
fastboot flash my_bigball_a my_bigball.img
fastboot flash abl_a abl.img
fastboot flash abl_b abl.img
fastboot flash bluetooth_a bluetooth.img
fastboot flash bluetooth_b bluetooth.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash core_nhlos_a core_nhlos.img
fastboot flash core_nhlos_b core_nhlos.img
fastboot flash devcfg_a devcfg.img
fastboot flash devcfg_b devcfg.img
fastboot flash dsp_a dsp.img
fastboot flash dsp_b dsp.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash featenabler_a featenabler.img
fastboot flash featenabler_b featenabler.img
fastboot flash hyp_a hyp.img
fastboot flash hyp_b hyp.img
fastboot flash imagefv_a imagefv.img
fastboot flash imagefv_b imagefv.img
fastboot flash keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash logo_a logo.img
fastboot flash logo_b logo.img
fastboot flash oplusstanvbk_a oplusstanvbk.img
fastboot flash oplusstanvbk_b oplusstanvbk.img
fastboot flash qupfw_a qupfw.img
fastboot flash qupfw_b qupfw.img
fastboot flash rpm_a rpm.img
fastboot flash rpm_b rpm.img
fastboot flash tz_a tz.img
fastboot flash tz_b tz.img
fastboot flash uefisecapp_a uefisecapp.img
fastboot flash uefisecapp_b uefisecapp.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_system_a vbmeta_system.img
fastboot flash vbmeta_system_b vbmeta_system.img
fastboot flash vendor_boot_a vendor_boot.img
fastboot flash vendor_boot_b vendor_boot.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash xbl_config_a xbl_config.img
fastboot flash xbl_config_b xbl_config.img
fastboot --set-active=a
fastboot reboot bootloader
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot -w
Hope this helps someone.
Travisholt92 said:
Captured this OTA returning to Android 12 after nearly bricking my N200and using MSMtool to get back to stock.
https://android.googleapis.com/packages/ota-api/package/f706ca0ab8556311d76c565135816d3873a4a15c.zip
This is a Full OTA
This can be used to return to stock from a A11 or A12 fw based custom ROM.
Recreate a A12 super partition for slot A:
In fastbootd delete all of these listed partitions (including vendor_dlkm if coming from custom ROM)
fastboot create-logical-partition system_a 1
fastboot flash system system.img
fastboot create-logical-partition system_ext_a 1
fastboot flash system_ext system_ext.img
fastboot create-logical-partition product_a 1
fastboot flash product product.img
fastboot create-logical-partition vendor_a 1
fastboot flash vendor vendor.img
fastboot create-logical-partition odm_a 1
fastboot flash odm odm.img
fastboot create-logical-partition my_product_a 1
fastboot flash my_product_a my_product.img
fastboot create-logical-partition my_engineering_a 1
fastboot flash my_engineering_a my_engineering.img
fastboot create-logical-partition my_stock_a 1
fastboot flash my_stock_a my_stock.img
fastboot create-logical-partition my_company_a 1
fastboot flash my_company_a my_company.img
fastboot create-logical-partition my_carrier_a 1
fastboot flash my_carrier_a my_carrier.img
fastboot create-logical-partition my_region_a 1
fastboot flash my_region_a my_region.img
fastboot create-logical-partition my_heytap_a 1
fastboot flash my_heytap_a my_heytap.img
fastboot create-logical-partition my_preload_a 1
fastboot flash my_preload_a my_preload.img
fastboot create-logical-partition my_manifest_a 1
fastboot flash my_manifest_a my_manifest.img
fastboot create-logical-partition my_bigball_a 1
fastboot flash my_bigball_a my_bigball.img
Then flash the zip in fastboot enhanced to flash the rest of the required partitions before rebooting (or use a payload dumper to extract all partitions to flash them manually on Linux)
Hope this helps someone.
Click to expand...
Click to collapse
Just have them flash the ota itself in fastbootd and then fastboot. Does the same thing. This is unnecessarily overly-complicated. To many areas for error.
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, use the fastboot enhanced method.
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
DisclaimerThe information on this site may contain errors or inaccuracies, and we do not make any warranty or guarantee as to the accuracy of the information. Your warranty will be void if you tamper with any part of your device / software. YOU are choosing to make these modifications. XDA is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
All the best,
xda-developers
Sprunglicious said:
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, Either use the fastboot method above.
Click to expand...
Click to collapse
WHAT?! they definitely didn't do it right then. Assuming the user didn't flash the full FW which is how they ended up bricked. I have found NO WAY of simply flashing the OTA (using any recovery or fastboot enhanced) to automatically regenerate the super partition. it doesn't work. This guide however DOES explain exactly how to properly regenerate the super partition and only that.
I will revise the OP when i get the time to include the full flashing instructions for Windows, Linux, Android, and MacOS. Thank you for bringing this to my attention.
Edit: OP instructions are now for Full OTA install with fw flashed to both slots. Hopefully this helps.
scanman0 said:
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
Click to expand...
Click to collapse
If the user can get to bootloader then custom recovery such as LineageOS recovery can be flashed to gain Fastbootd permissions to properly reflash the device firmware.
See next post
Sprunglicious said:
For those who read this.. do not use this guide. There has been a report of a user (who did it step by step exactly and verified) and ended up bricking their device, Either use the fastboot method above.
Click to expand...
Click to collapse
scanman0 said:
I too have also assisted someone who bricked phone with this guide as it deletes files from copy a & b at the same time and if anything goes wrong or reboot, they are soft bricked and cannot boot to recovery or fastboot!
Click to expand...
Click to collapse
These comments seem unnecessarily critical and assumptive rather than constructive. Have either of you actually followed the guide or just making assumptions based on what another user reports? I think we all know it's quite easy for folks that don't know what they're doing to mess things up quickly because they aren't paying attention. Let's encourage contributors to continue to post by being supportive. It's okay to question the validity of something but do so constructively please.
I'm happy to report that other than a couple minor issues where a few commands needed the _a/b specification (which OP has fixed already) this guide worked without issue. I just flashed an N200 running LineageOS to stock OOS using the supplied OTA and the linked OTA dumper for macOS (Yes, macOS! did the whole process on my MacBook which was awesome).
@Travisholt92 Thanks for an excellent guide!
CmdrCrichton said:
These comments seem unnecessarily critical and assumptive rather than constructive. Have either of you actually followed the guide or just making assumptions based on what another user reports? I think we all know it's quite easy for folks that don't know what they're doing to mess things up quickly because they aren't paying attention. Let's encourage contributors to continue to post by being supportive. It's okay to question the validity of something but do so constructively please.
I'm happy to report that other than a couple minor issues where a few commands needed the _a/b specification (which OP has fixed already) this guide worked without issue. I just flashed an N200 running LineageOS to stock OOS using the supplied OTA and the linked OTA dumper for macOS (Yes, macOS! did the whole process on my MacBook which was awesome).
@Travisholt92 Thanks for an excellent guide
Click to expand...
Click to collapse
You have failed to note that this guide has been updated since I had commented. As I have said elsewhere, there was no hostility meant by anything above. Simply a warning to those out there. Because having to modify _a or _b are not small acts when it comes to the world of Android Modification. My account may be semi-new, but I have been doing this since the android 4.0 days. as this was a new account created due to losing access to my old account. So let's not even bother trying to get into the credibility argument. It isn't something worth either of our's time.
By all means did I want this to be helpful, but the reality is that there were multiple devices to have been reported to have been ruined, being left with a CDE error. Which means they could not have been recovered with the MSMTools in the wild, as they could not pass the verification check to flash. And during this process there was zero ways to get to fastboot to fix the devices in that manner.
Frankly, due to what had occured, I have been having to pull my own time trying to help these individuals in a situation that I did not cause in the first place, when i could have either been working on my own project and spending time with my family. I have been working on trying to build an ops file to flash with the current MSMTools out currently to eventually get these devices fixed (as they are belonging to normal OEM configuration of the OnePlus Nord N200 (Dre). Not the AA variant. This process has been unsuccessful thus far, meaning we still have paperweights.
The only thing I ask is that some kind of assistance be given to those who followed the improper guide in its' original form. As they deserve that much at the very least.
I am more than happy to help and try and figure something out, as you both can contact me elsewhere as well. Let's talk this out like civilized people and come up with a solution.
Thanks again, and I wish you to continue to live happy lives,
Sprungles/Sprunglicious
Sprunglicious said:
You have failed to note that this guide has been updated since I had commented. As I have said elsewhere, there was no hostility meant by anything above. Simply a warning to those out there. Because having to modify _a or _b are not small acts when it comes to the world of Android Modification. My account may be semi-new, but I have been doing this since the android 4.0 days. as this was a new account created due to losing access to my old account. So let's not even bother trying to get into the credibility argument. It isn't something worth either of our's time.
By all means did I want this to be helpful, but the reality is that there were multiple devices to have been reported to have been ruined, being left with a CDE error. Which means they could not have been recovered with the MSMTools in the wild, as they could not pass the verification check to flash. And during this process there was zero ways to get to fastboot to fix the devices in that manner.
Frankly, due to what had occured, I have been having to pull my own time trying to help these individuals in a situation that I did not cause in the first place, when i could have either been working on my own project and spending time with my family. I have been working on trying to build an ops file to flash with the current MSMTools out currently to eventually get these devices fixed (as they are belonging to normal OEM configuration of the OnePlus Nord N200 (Dre). Not the AA variant. This process has been unsuccessful thus far, meaning we still have paperweights.
The only thing I ask is that some kind of assistance be given to those who followed the improper guide in its' original form. As they deserve that much at the very least.
I am more than happy to help and try and figure something out, as you both can contact me elsewhere as well. Let's talk this out like civilized people and come up with a solution.
Thanks again, and I wish you to continue to live happy lives,
Sprungles/Sprunglicious
Click to expand...
Click to collapse
Even before OP updated it, it worked. I used the original form myself. As far as I can tell the expanded form was an effort to ensure less issues for those who have no business attempting it in the first place. I wouldn’t call that improper.
No one is questioning your “credibility” and I’m not sure why you even feel the need to bring that up because it has no bearing to the conversation. This is about whether you know what you’re doing with Android, but rather whether you can be a decent contributor to the conversation for the benefit of all those involved, the community itself and OP.
As for your other point, you’ve taken it upon yourself to attempt to help people who clearly don’t know what they’re doing, fix their issue. Them screwing things up isn’t on OP and as is the case with anyone who provide guides/info/suggestion on XDA, it’s not their responsibility to fix an issue that happens as a result following them. If that was the case, I doubt we’d have any developers contributing on here.
You might want to rethink how you respond to someone if you’re wanting to be civilized as you indicate. And I know you know how.
Alright. As I have said before, there was no I'll intent behind any of what was said. It was all out there as a disclaimer as some newbies ended up misinterpreting information that had been put. At this point in time, things have been settled in this regard. I appreciate the feedback and am glad the original creator updated the post to have less of misunderstanding.
The message was put there as a "Lets not use this if we don't know what we are doing" kind of announcement if that wasnt already clear. As, at this point, each post would be best written as a step by step so the mass majority of people can understand and get use out of it.
Being understanding of the general public, and how they are going to read something and use it is a skill somebody must use when writing a guide online. As, if it is not a learning tool, then it needs be stated as such. As, the user has gone to the post for reference and instructions.
But again, at this point in time, everything has been updated and has calmed down. The writer and I are on good terms and an understanding on both of ours sides. We both have admitted the wrong and have accepted the good from this situation. So, if you have an issue with me, you have my contact information, let's take it there rather than on some public forum. It's quite inappropriate. Do also note, I did try fmto reach out to the creator before writing the warning in this post.
Sprunglicious said:
Alright. As I have said before, there was no I'll intent behind any of what was said. It was all out there as a disclaimer as some newbies ended up misinterpreting information that had been put. At this point in time, things have been settled in this regard. I appreciate the feedback and am glad the original creator updated the post to have less of misunderstanding.
The message was put there as a "Lets not use this if we don't know what we are doing" kind of announcement if that wasnt already clear. As, at this point, each post would be best written as a step by step so the mass majority of people can understand and get use out of it.
Being understanding of the general public, and how they are going to read something and use it is a skill somebody must use when writing a guide online. As, if it is not a learning tool, then it needs be stated as such. As, the user has gone to the post for reference and instructions.
But again, at this point in time, everything has been updated and has calmed down. The writer and I are on good terms and an understanding on both of ours sides. We both have admitted the wrong and have accepted the good from this situation. So, if you have an issue with me, you have my contact information, let's take it there rather than on some public forum. It's quite inappropriate. Do also note, I did try fmto reach out to the creator before writing the warning in this post.
Click to expand...
Click to collapse
Just stop. You’re replying to a post from over a week ago. I’m aware of what’s taken place since then. Good lord.
Related
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
pacomiguel said:
Hello, this is my first time in the xda forum, I hope you help me with my situation since I have been trying to solve my problem for several days without any success. Without more to say I tell you my situation:
1 week ago I decided to make a rom flash on my motorola G7 POWER (XT1955-2 RETAIL), so I proceeded to download a rom from youtube, perform the procedure without any problem and when I finish the cell phone restart, until here everything normal. Now I comment the problem arises after the restart of the cell phone, I realized that it did not start and stays in the logo of Motorola and restarted again.
I gave myself the task of checking that it could have failed and I found that when it was flashing they appreciated several errors 1 of them is the following:
C: \ Users \ maxic \ Desktop \ fflanfl \ Motorola_Moto_G7_Power_XT1955_2_ 9.0_CFC_US_181210 \ Firmware> fastboot erase customize
erasing 'customize' ...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.009s
Those are the mistakes I found. I've tried flashing 1 million times with different roms and nothing please I need your help to solve my problem.:crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
sd_shadow said:
There is a G7 Power section
https://forum.xda-developers.com/g7-power
See
https://forum.xda-developers.com/g7-power/how-to/complete-noob-guide-to-rooting-metropcs-t3954986
Download from
https://mirrors.lolinet.com/firmware/moto/ocean/official/
Try
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hello, thanks for the information but I had tried to do that before, the bootloader is locked on my device and there is no way to unlock it in the condition that my cell phone is.
Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmware/moto/deen/official/RETAIL
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
ALSO YOU CAN USE RSD Lite Tool
Please
I Don't know to Re-Lock Boot loader. It shows Need signed Bootloader
can be installed in phone version? is there any risk?
Enviado desde mi Pixel 2 XL mediante Tapatalk
I flashed it and it works pretty good.
I havent had any issues.
Unique code
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
cyyy said:
I followed the guide here:
https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
It's for a different Motorola phone, but the process is the same. After you enter the required data on the Motorola website, you will get the unlock key in a few minutes.
Click to expand...
Click to collapse
Ok! I'll try another time!
deveshbabu said:
Download Retail Version of Android 10 Version
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Commands To Flash
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_a system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Justphemy said:
i did all but still on android 9,btw i have two errors:
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.0
error: cannot load 'system_b.img_sparsechunk.0'
PS C:\adb> fastboot flash system_b system_b.img_sparsechunk.1
error: cannot load 'system_b.img_sparsechunk.1'
i didnt saw those files on the package.
can someone help how to install the package on my device plzzz?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
moisestrindade said:
Hey, guys! How did you get the Unique Key to unlock the bootloader? I asked it through Motorola Website but I didn't get an answer so far..
The solicitation hasn't reached even 24h period yet, but I remember doing that other times, and it was really fast.
Click to expand...
Click to collapse
I'm using the Lenovo Moto Smart Assistant PC application and I'm in the middle of the upgrade.
FaBMak said:
https://forum.xda-developers.com/showpost.php?p=82134389&postcount=36
Click to expand...
Click to collapse
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Justphemy said:
thanks man, i just updated my phone without those files and it's working normal now, anyway i flashed that file now, is it ok? have to do any format or reset?
Click to expand...
Click to collapse
I don't know, i just saw this on the other thread. I think that if it's working ok, keep it.
if my device is RETLA will RETAIL work fine on it?
EDIT: I can confirm, as of first boot, everything seems to be in order! functioning LTE, anyway!
EDIT2: Play store is broken, everything gets stuck at 99%. going to try to rollback to Android 9.
Also I need help locking the bootloader on Motorola one p30 play xt1941-3 please help anyone.
HI everyone...
During last Weeks I have been working on getting a recovery working for this device, I upload the first version of what I have done, I was not able to test it properly due there is an issue with touchscreen if someone has the possibilitie to test it with an mouse that would be great. It was made for the xt2016-2 version only regards
You will need fastboot on your PC:
https://forum.xda-developers.com/showthread.php?t=2317790
as well a bootloader unlocked
WARNING:Flashing this may get device encrypted data so it may delete your data
i am not responsable of any damaged device
first you have to know your active slot on the device for that you will do the following:
Make sure the smartphone is connected to the PC with a USB cable
Now boot the smartphone into Fastboot Mode
Open up a Command Prompt, Windows PowerShell, or a Terminal in the same folder as your ADB and Fastboot files
Type out the following command. . .
fastboot getvar all
. . .then press Enter on the keyboard
Wait for a lot of text to finish scrolling and look for the (bootloader) current-slot text
This should actually be toward the bottom without the need to scroll up.
The letter after this text will be the currently active partition slot for your device
Commands to flash it and things you will need:
Blank vbmeta (To remove AVB verfication): https://mega.nz/file/nDwjACqQ#YljxjKbR3QLwFyj4LuMpKE4NR8ZlPOgQ9t9PWXADBqk
command: fastboot --disable-verification flash vbmeta_(slot what you are using) vbmeta.img
then we are gonna flash the TWRP image
TWRP XT2016-2: https://mega.nz/file/nDwjACqQ#YljxjKbR3QLwFyj4LuMpKE4NR8ZlPOgQ9t9PWXADBqk
Command: fastboot flash boot_(slot what you are using) TWRP.img
NOTE: REMOVE THE () AND JUST PUT THE LETTER*
In case of brick: I leave stock images
command for vbmeta: fastboot flash vbmeta_a vbmetastock.img
command for vbmeta: fastboot flash vbmeta_b vbmetastock.img
Vbmeta:https://mega.nz/file/OP5jAISC#NFLCqerxXZC5aY9-WW5fq6cUlZ6WWwDQxIMvfN0nOxI
Boot:https://mega.nz/file/3fIQhQzA#GFeIbb1TYPg8x8Lq_fBiNu9UFenUgvFH1-eVjIm4uqE
You flash boot same way than previous one.
If someone wants to help with the developing just pm me and I'll answer as soon i can
Can't Download TWRP
Hey,
I want to try this but the TWRP link leads me to vbmeta link so I can't download it.
Test
I want to help you testing this but the link of TWRP is the same as the one for the vbmeta file
command: fastboot --disable-verification flash vbmeta_b vbmeta.img
returns
PS C:\adb> fastboot --disable-verification flash vbmeta_b vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verification
Dr0wn3d said:
command: fastboot --disable-verification flash vbmeta_b vbmeta.img
returns
PS C:\adb> fastboot --disable-verification flash vbmeta_b vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verification
Click to expand...
Click to collapse
Fastboot commands do not necessarily work on all Android devices. Their compatibility differs from OEM to OEM.
Dr0wn3d said:
command: fastboot --disable-verification flash vbmeta_b vbmeta.img
returns
PS C:\adb> fastboot --disable-verification flash vbmeta_b vbmeta.img
C:\adb\fastboot.exe: unknown option -- disable-verification
Click to expand...
Click to collapse
Use: fastboot --disable-verity flash vbmeta_b vbmeta.img (For Slot_B)
fastboot --disable-verity flash vbmeta_a vbmeta.img (For Slot_A)
i cant download twrp too... any way I can help?
thanks
Blank vbmeta (To remove AVB verfication): https://mega.nz/file/nDwjACqQ#YljxjKbR3QLwFyj4LuMpKE4NR8ZlPOgQ9t9PWXADBqk
command: fastboot --disable-verification flash vbmeta_(slot what you are using) vbmeta.img
then we are gonna flash the TWRP image
TWRP XT2016-2: https://mega.nz/file/nDwjACqQ#YljxjKbR3QLwFyj4LuMpKE4NR8ZlPOgQ9t9PWXADBqk
[/QUOTE]
This two link are the same, please upload the TWRP link again, thanks
no more updates or new link?
umago mais sobre o twrp/
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool)
I've noticed a reoccurring theme. i myself am guilty of doing it and not realizing what went wrong.
It's one of two things:
1. If the device fails to boot "7" times in a row or encounters a hard panic, it will wipe the metadata partition (the decryption key for data/user storage) and may also switch to the alternate slot automatically.
If your device switches slots on it's own, your userdata is gone.. without a decryption key, there is no getting it back (without a very powerful computer and probably years to brute force decrypt)
You will not be able to boot again until you are on the correct slot (dictated by your super partition and other A/B partitions needing to be up to date)
When back on the proper slot, while in fastboot run:
fastboot -w
This will wipe userdata and metadata partitions to allow metadata to be regenerated upon first boot.
Either "fastboot reboot recovery" or use the keys to select reboot recovery. And "wipe everything"
After this you should be bootable. If not...
2. When attempting to prepare the system for flashing GSI, we humans are messing up surprise surpise.
The issue most specifically stems from the dynamic partition located at /dev/block/by-name/super
this partition actually contains 5 resizable partitions : (i've seen up to 7 on this device including -cow (copy-on-write)
system // system_a/system_b //
system_ext // system_ext_a/system_ext_b //
product // product_a/product_b //
vendor // vendor_a/vendor_b //
odm // odm_a/odm_b //
if on you are running stock and your stock is running on slot b for example, your dynamic partition layout is as follows:
system_b
system_ext_b
product_b
vendor_b
odm_b
the issue lies when we go to flash a GSI and start using the commands:
fastboot delete-logical-parition
fastboot create-logical-parition
i myself have done:
fastboot create-logical-partition system 0
this is wrong. it needs a target slot specified, you will have no issues creating the partition or flashing, but it will most likely fail to boot.
correct usage would be:
fastboot create-logical-partition system_b 0 // or use the size values provided by fastboot getvar all as shown in my example of how to switch slots/unbrick below
Prerequisites:
1. stock firmware package or complete dump of all of these FROM THE SAME SOFTWARE VERSION
I have a T-Mobile variant, but for this proof of concept i used the unbranded NA Software provided here https://www.oneplus.com/support/softwareupgrade/details?code=PM1630638351161
Required Partition Images:
system.img
system_ext.img
product.img
vendor.img
odm.img
boot.img
vendor_boot.img
dtbo.img
uefisecapp.img
imagefv.img
abl.img
core_nhlos.img
qupfw.img
keymaster.img
hyp.img
dsp.img
devcfg.img
bluetooth.img
logo.img
tz.img
xbl.img
xbl_config.img
featenabler.img
modem.img
rpm.img
oplusstanvbk.img
vbmeta.img
vbmeta_system.img
If you're on T-Mobile just use the MSMTool unless you prefer the unbranded software.
2. Fastboot Enhanced from this thread https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/
( Or if on Linux, find yourself some knowledge on how to use a payload dumper to extract these images from the stock firmware package )
ALL of the partitions listed above that are NOT the 5 in the dynamic partition have BOTH slots A and B on your phone, you can flash all of these packages to both slots and pick either slot A or slot B when you repartition your super partition.
IT IS THE SUPER PARTITION THAT DECIDES WHICH SLOT GETS TO BOOT
(it is in bold because this is the cause of most "bricks" and vbmeta but more on that in a minute)
How to recreate a usable/bootable super partition:
1: identify which of your slots is capable of booting into stock recovery/fastbootd
If you can't boot stock recovery or fastbootd
flash these stock partitions:
dtbo
boot
vendor_boot
to both slots (_a and _b) on all 3
and these
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
Then try again to see which slot is bootable, if neither you lost too much in your super partition that is needed to run recovery, grab a backup of a super.img from someone on here and fastboot flash super super.img, depending on which slot that super.img is meant for, that will be the slot you will need to be on to proceed with the rest of the fixing
2. Boot into Fastbootd ( fastboot reboot fastboot )
Delete EVERYTHING from the super parition.
even if you don't remember making it, dont skip any of these lines just ignore the errors it spits out
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition system_ext
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition product
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition odm
Now let's recreated something useable. For Stock version 11.0.5.0 N/A my super image used these sizes (obtained by fastboot getvar all )
For my slot B to Slot A proof of concept i used this for slot A:
fastboot create-logical-partition system_a 0x5AFDC000
fastboot create-logical-partition system_ext_a 0x4B7B3000
fastboot create-logical-partition product_a 0x7338A000
fastboot create-logical-partition vendor_a 0x3EC8D000
fastboot create-logical-partition odm_a 0x37E9000
And for a "bricked" user wanting to stay with slot B they used:
fastboot create-logical-partition system_b 0x5AFDC000
fastboot create-logical-partition system_ext_b 0x4B7B3000
fastboot create-logical-partition product_b 0x7338A000
fastboot create-logical-partition vendor_b 0x3EC8D000
fastboot create-logical-partition odm_b 0x37E9000
Depending on which you choose to create, you can now set your desired slot with
fastboot set_active a
or
fastboot set_active b
then use Fastboot Enhanced to flash either the entire payload bin, or flash each to each _a or _b partition from the long list above one by one.
DO NOT LEAVE FASTBOOTD UNTIL YOU'VE FLASHED ALL OF THESE PARTITIONS (NOT JUST THE 5!) OR YOU MAY BE UNABLE TO GET BACK TO FASTBOOTD!!!
Flashing a payload.bin (.zip) in fastboot enhanced will flash to whatever slot is currently active and it monitors which slot is active.
Last is for vbmeta
If you flash any sort of modified boot image (magisk rooted), gsi, or any sort of image that is not stock, you need to flash the stock vbmeta and vbmeta_system with --disable-verity and --disable-verification or you won't be able to do much if anything at all.
in either fastboot or fastbootd:
fastboot —disable-verity —disable-verification flash vbmeta_a vbmeta.img
fastboot —disable-verity —disable-verification flash vbmeta_b vbmeta.img
fastboot —disable-verity —disable-verification flash vbmeta_system_a vbmeta_system.img
fastboot —disable-verity —disable-verification flash vbmeta_system_b vbmeta_system.img
these are very important if you flash files that are not originally from that specific build version/variant
Happy flashing to you all Hopefully this helps some people.
It surprises me there are no success stories commented.
There was a user in the telegram chat that was waiting (for a few days) to be able to send their device back to OnePlus. I let others try to come up with solution for a few days before i took the time to dive into the issue myself.
Immediately upon following this tutorial, they had restored functionality of slot B on their device and avoided sending the device to OnePlus to fix.
As a proof of concept I updated slot A and recreated the super.img for slot A and could easily go back to slot B by flashing my backup super.img(which was for slot B) and switching active slot back to slot B. So made this guide for them to restore proper setup of the super partition.
I hope this guide can help others as well.
This got me back up and running on slot A,thanks again for the guide!
transgirlphoebe said:
Says the guy that gave the advice of wiping the super partition which is guaranteed to make sure you cannot get into recovery or fastbootD. Why don't you go ahead and get on somewhere before a moderator comes along and just removes you from the site entirely
Click to expand...
Click to collapse
I'll be back either way
transgirlphoebe said:
Says the guy that gave the advice of wiping the super partition which is guaranteed to make sure you cannot get into recovery or fastbootD. Why don't you go ahead and get on somewhere before a moderator comes along and just removes you from the site entirely
Click to expand...
Click to collapse
Know your facts
n ask the guy I helped....
he is the one who corrupted his super partition with @Travisholt92 BS twrp. (As stated by the guy I help himself)
B4 I even touched his sh*t.
I Spent 8+hrs remote desktoping with him last night. He seemed happy when I left the chat
I need to remove the ability to wipe the super partition. Don't blame my software for a user error just because you can't use it while running Android 12 GSI. It doesn't work on any device. On Android 11, my twrp works as intended.
Moderator Information
Hello,
I have to remove some off topic posts from this thread. Please post your comment following XDA rules. No finger pointing without proofs, neither calling names. Just be civil in the discussion.
Thanks.
Jerry
Travisholt92 said:
I need to remove the ability to wipe the super partition. Don't blame my software for a user error just because you can't use it while running Android 12 GSI. It doesn't work on any device. On Android 11, my twrp works as intended.
Click to expand...
Click to collapse
Honestly I think it would be best to make it to where you can only wipe user data, since apparently we have to baby the end users
┤Thread Cleaned (again)├┤We really need to stop throwing moderators towards this place and we need your help to make that happen. Please be nice to one another. There's plenty of misery going on out there as it is. This forum is about our shared passion for tech dammit, let's show some love. Or at least get us involved so we can spread some love before things get heated. Thank you for listening, keep an open mind and have a great weekend.├┤Timmy├┤Forum Moderator├
Timmmmaaahh! said:
┤Thread Cleaned (again)├┤We really need to stop throwing moderators towards this place and we need your help to make that happen. Please be nice to one another. There's plenty of misery going on out there as it is. This forum is about our shared passion for tech dammit, let's show some love. Or at least get us involved so we can spread some love before things get heated. Thank you for listening, keep an open mind and have a great weekend.├┤Timmy├┤Forum Moderator├
Click to expand...
Click to collapse
We resolved this disagreement outside of XDA to avoid this from happening in the future and to prevent the other party from getting themselves banned as they are a productive member of the community. I personally didn't want to see that happen over me. Issue resolved sorry for wasting your time
So ... I followed the steps in the OP and now the phone won't boot. Here's what I did:
1. Unpacked T-Mobile OTA payload.bin
2. Rebooted into fastbootd
3. Executed the following commands:
fastboot=/usr/local/bin/fastboot
$fastboot -w
$fastboot flash boot_a boot.img
$fastboot flash boot_b boot.img
$fastboot flash dtbo_a dtbo.img
$fastboot flash dtbo_b dtbo.img
$fastboot flash modem_a modem.img
$fastboot flash modem_b modem.img
$fastboot flash oplusstanvbk_a oplusstanvbk.img
$fastboot flash oplusstanvbk_b oplusstanvbk.img
$fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
$fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
$fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
$fastboot --disable-verity --disable-verification flash vbmeta_system_b vbmeta_system.img
$fastboot flash abl_a abl.img
$fastboot flash abl_b abl.img
$fastboot flash bluetooth_a bluetooth.img
$fastboot flash bluetooth_b bluetooth.img
$fastboot flash devcfg_a devcfg.img
$fastboot flash devcfg_b devcfg.img
$fastboot flash dsp_a dsp.img
$fastboot flash dsp_b dsp.img
$fastboot flash featenabler_a featenabler.img
$fastboot flash featenabler_b featenabler.img
$fastboot flash hyp_a hyp.img
$fastboot flash hyp_b hyp.img
$fastboot flash imagefv_a imagefv.img
$fastboot flash imagefv_b imagefv.img
$fastboot flash keymaster_a keymaster.img
$fastboot flash keymaster_b keymaster.img
$fastboot flash logo_a logo.img
$fastboot flash logo_b logo.img
$fastboot flash odm odm.img
$fastboot flash qupfw_a qupfw.img
$fastboot flash qupfw_b qupfw.img
$fastboot flash tz_a tz.img
$fastboot flash tz_b tz.img
$fastboot flash uefisecapp_a uefisecapp.img
$fastboot flash uefisecapp_b uefisecapp.img
$fastboot flash xbl_a xbl.img
$fastboot flash xbl_b xbl.img
$fastboot flash xbl_config_a xbl_config.img
$fastboot flash xbl_config_b xbl_config.img
$fastboot flash system system.img
$fastboot flash vendor vendor.img
$fastboot flash product product.img
$fastboot flash core_nhlos_a core_nhlos.img
$fastboot flash core_nhlos_b core_nhlos.img
$fastboot flash rpm_a rpm.img
$fastboot flash rpm_b rpm.img
$fastboot flash system_ext system_ext.img
$fastboot flash vendor_boot_a vendor_boot.img
$fastboot flash vendor_boot_b vendor_boot.img
Then rebooted into recovery the phone stayed dead. Any idea what went wrong and what to do next?
88bbraj said:
So ... I followed the steps in the OP and now the phone won't boot. Here's what I did:
1. Unpacked T-Mobile OTA payload.bin
2. Rebooted into fastbootd
3. Executed the following commands:
Then rebooted into recovery the phone stayed dead. Any idea what went wrong and what to do next?
Click to expand...
Click to collapse
Unbricked it using the MSMDownloadTools. The phone rebooted into OxygenOS and installed the newest update automatically. I intend to unlock the bootloader again and root the device, so if you can spot where I made a mistake in that list of commands you'll save me some trouble the next time I need to update.
It's very clear that you skipped the step of identifying current dynamic partitions using fastboot enhanced/payload dumper (which would have told you which slot was bootable, which slot to recreate, and would have helped you in identifying partition layout mistakes). Next time I advise taking a screenshot on a computer of the partition layout. but the MSM tool is the easiest unbrick method for Metro/T-Mobile devices
Also sorry for the delayed response, the server went down for maintenance about 20 minutes after you posted
But I'm glad you got it sorted out
88bbraj said:
Unbricked it using the MSMDownloadTools. The phone rebooted into OxygenOS and installed the newest update automatically. I intend to unlock the bootloader again and root the device, so if you can spot where I made a mistake in that list of commands you'll save me some trouble the next time I need to update.
Click to expand...
Click to collapse
Travisholt92 said:
It's very clear that you skipped the step of identifying current dynamic partitions using fastboot enhanced/payload dumper (which would have told you which slot was bootable, which slot to recreate, and would have helped you in identifying partition layout mistakes).
Click to expand...
Click to collapse
Your OP reads like that's only necessary for people with soft-bricked phones. Mine wasn't. I was trying to flash the newest OTA update onto a working, rooted TMO-branded phone. I checked which slot was active fastboot getvar active-slot and did not flash both _a and _b slots for the dynamic partitions.
I now have a working, TMO-branded phone with the newest OTA update installed, but I've read that rooted and bootloader-unlocked phones do not get OTA updates automatically. Is a subset of your OP's steps not the proper way to flash the new OTA payload in the future?
Thanks for clarifying.
Im honestly not sure. My mind doesn't care about stock on the N200 until Android 12 to be honest lol. Awaiting to build a Ryzen based PC to start compiling custom ROMs again. I know the n200 trees are nearly stable enough for daily driver usage. But I don't have a system worthy of compiling in less than 12 hours at the moment.
Better software will come soon enough, you won't have to deal with stock for much longer.
88bbraj said:
Your OP reads like that's only necessary for people with soft-bricked phones. Mine wasn't. I was trying to flash the newest OTA update onto a working, rooted TMO-branded phone. I checked which slot was active fastboot getvar active-slot and did not flash both _a and _b slots for the dynamic partitions.
I now have a working, TMO-branded phone with the newest OTA update installed, but I've read that rooted and bootloader-unlocked phones do not get OTA updates automatically. Is a subset of your OP's steps not the proper way to flash the new OTA payload in the future?
Thanks for clarifying.
Click to expand...
Click to collapse
Travisholt92 said:
Im honestly not sure. My mind doesn't care about stock on the N200 until Android 12 to be honest lol. Awaiting to build a Ryzen based PC to start compiling custom ROMs again. I know the n200 trees are nearly stable enough for daily driver usage. But I don't have a system worthy of compiling in less than 12 hours at the moment.
Better software will come soon enough, you won't have to deal with stock for much longer.
Click to expand...
Click to collapse
I didn't like the stock global N200. TMO fixes a few niggling issues (global doesn't recognize the CPU version, as an example), but global certainly makes the updating process simpler.
Anyway, I gleaned a lot of information from various posts of yours on this website which were useful, so thanks.
This guide worked for me to get back to stock from a GSI, THANK YOU! Your work is appreciated.
@Travisholt92 I get an error from fastboot when I try to delete/create the partitions.
fastboot create-logical-partition system_a 0
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm using fastboot version 28.0.2-debian. Any ideas why I can't recreate some of these partitions?
no_el said:
@Travisholt92 I get an error from fastboot when I try to delete/create the partitions.
fastboot create-logical-partition system_a 0
Creating 'system_a' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm using fastboot version 28.0.2-debian. Any ideas why I can't recreate some of these partitions?
Click to expand...
Click to collapse
You're using an outdated version of fastboot that doesn't support the required commands. Update to the latest version of Fastboot from the Google sdk
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
This is when they added the command.
33.0.1 is the latest and the download link is at the top of the page linked in this comment.
Hey guys,
I am trying to update my N200 to the newest OxygenOS, because it keeps nagging me to if I don't.
The first thing I tried was to re-flash the stock boot.img from the extracted OTA (which replaced Magisk with the stock recovery, too) - but still kept getting an installation error.
So I followed the steps above, and flashed *that* payload.bin with the Fastboot Enhanced tool - but it keeps boot-looping me back to fastboot mode. I think the partitions have changed sizes or something, and there's a message saying there were unknown partitions in the payload.bin too.
So for now, I'm flashing back to "OnePlusN200Oxygen_10.O.11_OTA_011_all_2203021426_2dd4f42a2d0545a3" and restoring my TWRP backup (which includes a "super" partition, but of that build), but if anybody can advise how I can update it to the DE2117_11_C.15 build, that would be great.
Hopefully there is a way to do it without erasing data. Usually for other phones I just unroot, install OTA, then re-root. But it seems trickier with the partition size nonsense going on here.
Edit: OnePlus download site hasn't updated the links yet, but there was a full OTA posted on XDA a few days ago, link here.
download (US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip)
(US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip | by Scanman0 for OnePlus Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
download (FastbootEnhance v1.4.0)
Releases · libxzr/FastbootEnhance
A user-friendly Fastboot ToolBox & Payload Dumper for Windows - libxzr/FastbootEnhance
github.com
download (SDK Platform Tools)
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
1.extract SDK Platform Tools to a location you can acces
2.open cmd as admin
3.cd\location to SDK Platform Tools
4.adb reboot fastboot
5.run all these comands below
fastboot delete-logical-partition system_a
fastboot delete-logical-partition system_b
fastboot delete-logical-partition system
fastboot delete-logical-partition system_ext_a
fastboot delete-logical-partition system_ext_b
fastboot delete-logical-partition system_ext
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
fastboot delete-logical-partition product
fastboot delete-logical-partition vendor_a
fastboot delete-logical-partition vendor_b
fastboot delete-logical-partition vendor
fastboot delete-logical-partition odm_a
fastboot delete-logical-partition odm_b
fastboot delete-logical-partition odm
fastboot delete-logical-partition modem_a
fastboot delete-logical-partition modem_b
fastboot delete-logical-partition modem
fastboot delete-logical-partition imagefv_a
fastboot delete-logical-partition abl_a
fastboot delete-logical-partition core_nhlos_a
fastboot delete-logical-partition qupfw_a
fastboot delete-logical-partition keymaster_a
fastboot delete-logical-partition hyp_a
fastboot delete-logical-partition dsp_a
fastboot delete-logical-partition devcfg_a
fastboot delete-logical-partition bluetooth_a
fastboot delete-logical-partition logo_a
fastboot delete-logical-partition tz_a
fastboot delete-logical-partition xbl_a
fastboot delete-logical-partition xbl_config_a
fastboot delete-logical-partition featenabler_a
fastboot delete-logical-partition modem_a
fastboot delete-logical-partition rpm_a
fastboot delete-logical-partition oplusstanvbk_a
fastboot delete-logical-partition my_bigball_a
fastboot delete-logical-partition my_bigball_a
fastboot delete-logical-partition my_carrier_a
fastboot delete-logical-partition my_company_a
fastboot delete-logical-partition my_engineering_a
fastboot delete-logical-partition my_heytap_a
fastboot delete-logical-partition my_manifest_a
fastboot delete-logical-partition my_preload_a
fastboot delete-logical-partition my_product_a
fastboot delete-logical-partition my_region_a
fastboot delete-logical-partition my_stock_a
fastboot delete-logical-partition uefisecapp_a
fastboot delete-logical-partition imagefv_b
fastboot delete-logical-partition abl_b
fastboot delete-logical-partition core_nhlos_b
fastboot delete-logical-partition qupfw_b
fastboot delete-logical-partition keymaster_b
fastboot delete-logical-partition hyp_b
fastboot delete-logical-partition dsp_b
fastboot delete-logical-partition devcfg_b
fastboot delete-logical-partition bluetooth_b
fastboot delete-logical-partition logo_b
fastboot delete-logical-partition tz_b
fastboot delete-logical-partition xbl_b
fastboot delete-logical-partition xbl_config_b
fastboot delete-logical-partition featenabler_b
fastboot delete-logical-partition modem_b
fastboot delete-logical-partition rpm_b
fastboot delete-logical-partition oplusstanvbk_b
fastboot delete-logical-partition my_bigball_b
fastboot delete-logical-partition my_bigball_b
fastboot delete-logical-partition my_carrier_b
fastboot delete-logical-partition my_company_b
fastboot delete-logical-partition my_engineering_b
fastboot delete-logical-partition my_heytap_b
fastboot delete-logical-partition my_manifest_b
fastboot delete-logical-partition my_preload_b
fastboot delete-logical-partition my_product_b
fastboot delete-logical-partition my_region_b
fastboot delete-logical-partition my_stock_b
fastboot delete-logical-partition uefisecapp_b
fastboot create-logical-partition system_ext_a 0x39952000
fastboot create-logical-partition system_a 0x26459000
fastboot create-logical-partition product_a 0xB9F7000
fastboot create-logical-partition vendor_a 0x67000
fastboot create-logical-partition odm_a 0x2593E000
fastboot create-logical-partition modem_a 0xDC00000
fastboot create-logical-partition imagefv_a 0x200000
fastboot create-logical-partition abl_a 0x800000
fastboot create-logical-partition core_nhlos_a 0xAA00000
fastboot create-logical-partition qupfw_a 0x10000
fastboot create-logical-partition keymaster_a 0x80000
fastboot create-logical-partition hyp_a 0x80000
fastboot create-logical-partition dsp_a 0x2000000
fastboot create-logical-partition devcfg_a 0x20000
fastboot create-logical-partition bluetooth_a 0x100000
fastboot create-logical-partition logo_a 0x1000000
fastboot create-logical-partition tz_a 0x400000
fastboot create-logical-partition xbl_a 0x600000
fastboot create-logical-partition xbl_config_a 0x80000
fastboot create-logical-partition featenabler_a 0x20000
fastboot create-logical-partition modem_a 0xDC00000
fastboot create-logical-partition rpm_a 0x80000
fastboot create-logical-partition oplusstanvbk_a 0x1400000
fastboot create-logical-partition my_bigball_a 0x2B046000
fastboot create-logical-partition my_carrier_a 0x8D6000
fastboot create-logical-partition my_company_a 0x55000
fastboot create-logical-partition my_engineering_a 0x55000
fastboot create-logical-partition my_heytap_a 0x2A926000
fastboot create-logical-partition my_manifest_a 0x55000
fastboot create-logical-partition my_preload_a 0x55000
fastboot create-logical-partition my_product_a 0xB9F7000
fastboot create-logical-partition my_region_a 0xAC000
fastboot create-logical-partition my_stock_a 0x2B9A6000
fastboot create-logical-partition uefisecapp_a 0x200000
6.Then boot up enhanced fastboot and click your device and switch to slot a
7.Then run Flash Payload.bin and select the file US_RETAIL_A12_C_16_FULL_ROM)DE2117_11.C.15_0150_202205192325.zip
8.after that reboot to recovery and factory reset
9.then reboot to system then you will be back to stock with system on slot a
michaelwaycraig67 said:
i might be willing to help users via discord but i work 6 days a week i will try helping who i can i have seccesfully helped a few users repair a few devices hope this helps
Click to expand...
Click to collapse
Hello and good morning, @michaelwaycraig67
We'd highly appreciate if you provide your support and assistance here on XDA and not by any social media. XDA is not the platform to promote Discord, Telegram, Facebook etc. If you do then I'm sorry that we've to close your threads or to remove your posts. Further information is available in the XDA Forum Rules e.g. in the rule no. 5 or at
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
Thanks for your cooperation.
Regards
Oswald Boelcke said:
Hello and good morning, @michaelwaycraig67
We'd highly appreciate if you provide your support and assistance here on XDA and not by any social media. XDA is not the platform to promote Discord, Telegram, Facebook etc. If you do then I'm sorry that we've to close your threads or to remove your posts. Further information is available in the XDA Forum Rules e.g. in the rule no. 5 or at
Telegram Chat Channels - Way Forward
WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...
forum.xda-developers.com
Thanks for your cooperation.
Regards
Click to expand...
Click to collapse
okay removed said text sorry about that didnt know that was a rule