Develop Bugs

[Solved] Manual Flash Stock Firmware

How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.

Anutter226 said:
How would I flash the stock firmware Manually! I know I can use the unified toolkit but, I'm just trying to educate myself with the help of the XDA community.
ALSO! the main reason why is because I cannot get flash-all.bat to work.
I'm on Platform-Tools v. 25, but it still won't detect the boot slots like it should. So, if you guys can help me out on this problem, It would be awesome!
Lets say I'm on boot slot b.
I know the images should be flashed like this
Code:
fastboot flash aboot_b aboot.img
fastboot flash apdp_b apdp.img
fastboot flash boot_b boot.img
fastboot flash bootlocker_b bootlocker.img
fastboot flash cmnlib32_b cmnlib32.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash devcfg_b devcfg.img
fastboot flash hosd_b hosd.img
fastboot flash hyp_b hyp.img
fastboot flash keymaster_b keymaster.img
fastboot flash modem_b modem.img
fastboot flash pmic_b pmic.img
fastboot flash rpm_b rpm.img
fastboot flash tz_b tz.img
fastboot flash vendor_b vendor.img
But, I'm not sure about system.img and system_other.img.
Click to expand...
Click to collapse
What happens with the flash-all.bat file?

delete

airmaxx23 said:
What happens with the flash-all.bat file?
Click to expand...
Click to collapse
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.

Your fastboot is likely too old and can't read the pixel partitions. Make sure your Google drivers and fastboot files are up to date and try again.
Sent from my Pixel XL using Tapatalk

Anutter226 said:
As soon as it tries to flash one of the .imgs it says it isn't a partition. You can see it trying to flash boot partition not boot_b or boot_a.
Click to expand...
Click to collapse
I have used the flash all script several times and it works flawlessly.

Nevermind..

kiddiosky said:
Nevermind..
Click to expand...
Click to collapse
Mate somehow i too need the manuall commands Did you solved the problem/?

A2 lite stuck on bootload

Hi, i flashed a bad boot file and my phone is stuck on bootloader, i tried to get into edl but it's still stuck.
my bootloader is unlocked and i have access to download mode and i can run commands via fastboot. the problem is i can't remember what whas my android version (just got the phone yesterday, i think it's 8.1)
any idea how to get the phone working (any solution is good: back to stock or whatever)
oh, and i don't have root access if it's relevant.
thanks!

If you can access fastboot you can try
Code:
fastboot oem edl
And connect your phone to a PC and use MiFlash to flash the stock clean rom that you can download here
If it doesn't work, since you have access to fastboot you can extract images from here and flash them via fastboot by running the following commands from the same location of the images :
Code:
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 modem_a modem.img
fastboot flash modem_b modem.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 keymaster_a keymaster.img
fastboot flash keymaster_b keymaster.img
fastboot flash cmnlib64_a cmnlib64.img
fastboot flash cmnlib64_b cmnlib64.img
fastboot flash cmnlib_a cmnlib.img
fastboot flash cmnlib_b cmnlib.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash mdtp_a mdtp.img
fastboot flash mdtp_b mdtp.img
fastboot flash aboot_a aboot.img
fastboot flash aboot_b aboot.img
fastboot flash sbl1_a sbl1.img
fastboot flash sbl1_b sbl1.img

first of all - thank you!
i tried with miflash and it didn't work. when i flash an img file it's flashing it too fast, almost like it didn't do anything, and then it is stuck again.
about the second solution - how can i exctract img files from the file you gave me? there is a bin file in there and no img...
[edit]: it didn't flash because the folder name has spaces, now it's working. thanks!
b.t.w: do you know if there is another twrp for a2 lite then the one here ? because this is what started the problems..

I used to be like that when I was trying root by magisk
your device has update security september or aug ?! to see in setting - about
you can find original boot.img of update secrutiy your device (in topic:magisk update ota) to re-flash and reboot ... everything will be fine
Sent from my Mi A2 Lite using XDA Labs

I flashed stock rom and it's all good now. thanks!
if anyone has working twrp for a2 lite (not the one that published here unoffical)- it would help me.

As far as I know, the one you posted is the only version of TWRP for now. But the official TWRP for the Redmi 6 Pro (that is exactly the same device as ours but with dufferent partitions and MIUI ROM) has been released so fortunately the official build will be availbable for the A2 Lite soon
(btw, if ever needed again, the payload.bin file also needs to bé unpacked with a tool named "payload dumper" for example)

wrong. delete

Android 11 update.

Receiving Android 11 in Argentina. RETAR
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow , finally .....

Hey, vos sabes que actualice y me brickeo el telefono....
te salio bien?

I had problems after the update. The phone was always with Stock rom and it was never touched for anything root. It was updated by OTA and it became a brick after the reboot. I tried to recover by fastboot with the rom on android 9, 10 and 11 (11 rom downloaded from the lenovo app for pc) without any success.

hey, please someone dump stock firmware from that update, thanks in advance

stockrom.net_KANE_RSA31.Q1-48-36-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
drive.google.com

cdanieltoralesp said:
stockrom.net_KANE_RSA31.Q1-48-36-11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
drive.google.com
Click to expand...
Click to collapse
this rom works for AT&T Mexico ??? or for which country is it functional? how is it installed? What are the adb commands?

Poland•
Motoflash Pro

Does anyone flashed this particular Android 11 firmware ? How it works ? I'm a little bit confused because I didn't find anywhere on trustworthy sites , official firmware for Moto XT1970-3 . So , what's up guys ?

to update to android 11 ... why does the bootloader have to be locked again? You will not be able to create a .bat file like the one in this post = MOTO-VISION_ACTION_FASTBOOT-TOOL_9-10.zip - https://forum.xda-developers.com/t/...hare-thread-tool-fastboot-flash-info.3943516/ maybe you need different adb commands ???? Does anyone have knowledge and help us create a way to flash android 11 from adb? Thanks in advance.

I used this commands and extracted firmware files to folder with adb and fastboot tools and it booted but only with unlocked bootloader. I have tried flashing same region as mine with locked bootloader from A10 to A11 (reteu) and cannot boot. Security error.
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
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_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.11
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash system_b system_other.img_sparsechunk.3
fastboot flash vendor_a vendor.img
fastboot erase userdata
fastboot reboot bootloader
EDIT:
I added edited bat file but i dont know its works.
I copied lines and edited to comands i have write.
Please tell me if it works

Finally received Android 11 by OTA . Phone locked , unroot , in original state .
XT1970-3 , RETEU channel .
RSA31.Q1-48-36-11
Didn't observed major improvements , on the contrary old unoptimized apks are not fluent . Boot sequence is faster , face recognition is slower also fingerprint unlock . WiFi is better , Mobile Data apparently the same . Camera apk seems to be a little bit better . Internet browser seems a little bit faster . Banks apks , are working . Touch sensitivity the same .
Overall maybe is just an impression but I feel the phone kind of laggy .

MyBike4Life said:
I used this commands and extracted firmware files to folder with adb and fastboot tools and it booted but only with unlocked bootloader. I have tried flashing same region as mine with locked bootloader from A10 to A11 (reteu) and cannot boot. Security error.
fastboot flash pit diskmap.pit
fastboot flash fwbl1 fwbl1.img
fastboot flash ldfw_a ldfw.img
fastboot flash ldfw_b ldfw.img
fastboot flash keystorage_a keystorage.img
fastboot flash keystorage_b keystorage.img
fastboot flash bootloader_a bootloader.img
fastboot flash bootloader_b bootloader.img
fastboot flash modem_a modem.bin
fastboot flash vbmeta_a vbmeta.img
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash logo_a logo.bin
fastboot flash dtbo_a dtbo.img
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_a system.img_sparsechunk.10
fastboot flash system_a system.img_sparsechunk.11
fastboot flash system_b system_other.img_sparsechunk.0
fastboot flash system_b system_other.img_sparsechunk.1
fastboot flash system_b system_other.img_sparsechunk.2
fastboot flash system_b system_other.img_sparsechunk.3
fastboot flash vendor_a vendor.img
fastboot erase userdata
fastboot reboot bootloader
EDIT:
I added edited bat file but i dont know its works.
I copied lines and edited to comands i have write.
Please tell me if it works
Click to expand...
Click to collapse
I'm going to try, after a while I'll be back and I'll tell you how it went.

The .bat file worked very well, now I have Android 11, my channel is ATTXT, but I made flash of a ROM from another channel different from mine (TEFMX), now I have a question, you can have Root with magisk in Android 11???

Not received Android 11 on XT1970-1 Retla Brazil Costa rica version

Just received Android 11 , about 1 week ago , last few days I just got second Android 11 update with security patch till 01 August all these for XT1970-3 . It seems it has a better battery saver

Is there a way I can root Motorola One Vision Android 11 ?
Because I have tried a lot of times, but it all leads to infinite rebooting (I think it's called soft brick or something)
Maybe there is a way to root it correctly, but I think I have been doing it wrong
I would appreciate your help <3

DI_G7 said:
Is there a way I can root Motorola One Vision Android 11 ?
Because I have tried a lot of times, but it all leads to infinite rebooting (I think it's called soft brick or something)
Maybe there is a way to root it correctly, but I think I have been doing it wrong
I would appreciate your help <3
Click to expand...
Click to collapse
I managed to get root in android 11, I just followed the guide in the post where twrp-3.3.1-test4 comes out, and I also managed to install edExposed with the Gravitybox Module.

tin0o said:
I managed to get root in android 11, I just followed the guide in the post where twrp-3.3.1-test4 comes out, and I also managed to install edExposed with the Gravitybox Module.
Click to expand...
Click to collapse
I have tried to install TWRP too but it leads to an error after the command
Fastboot flash TWRP.img
Can you tell me how did you installed TWRP?
.
It would help me a lot <3

Finally Android 11 came into Retla Region XT1970-1 (Brasil or Spanish)

[GUIDE] How to Avoid Killing Your OnePlus 8 Pro / 8T / 9R with OxygenOS 12 / ColorOS 12

As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
Massive Update! Someone found a way to recover the phone using EDL Deep Flash Cable.
XDA Thread Link
(Even though I tried it when it happened to me all this time ago and it didn't work, but it does seem to work for few people who used a Black & White cable from AliExpress (maybe there's some hidden tech inside) so give it a try and report, there's also a chance that maybe some devices don't get burned out but simply refuse to boot because voltage is too high, and others might be fried forever, we will see with time I guess. Nonetheless, Good Luck!)
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
Update: Double check Your RAM just in case!
Post #3
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.

ProtoDeVNan0 said:
As You can see, recently we started seeing more and more threads complaining about OxygenOS 12 killing people's devices. I lost my 8 Pro the same way few months ago and we finally know what caused this!
ANSWER - THE BOOTLOADER!
While OxygenOS OTA is mostly safe, it can still accidentally flash the wrong bootloader on Your phone! Examples are having Magisk Props Module installed which will lead to OxygenOS flashing the wrong image or TWRP telling payload to flash DDR4 bootloader onto DDR5 device.
But wait.. how can an official bootloader kill the motherboard beyond MSM?! Well.. Here's the thing, OnePlus uses same signature to sign all four firmwares, OP8, OP8T, OP8Pro, 9R all use identical signature, which means that PBL (Primary Bootloader) will load XBL (Secondary Bootloader) no matter which one You flash.
But wait.. isn't there any protection to stop this from happening? Well.. there should be. In fact previously OnePlus 8 and 8 Pro firmwares both shipped with single bootloader that was either designed for DDR4 or DDR5. Now since OxygenOS 12 they started shipping DDR4 and DDR5 in the same package. And the reason why the phone dies is because LPDDR5 RAM uses lower voltage compared to LPDDR4X, and just because there's no code to prevent XBL from setting voltage too high on LPDDR5, it leads to RAM getting overvolted and dying.
How can we tell which one we should flash if we end up flashing OOS OTA manually through fastboot?
If You have OnePlus 8 (DDR4) You're supposed to flash xbl.img & xbl_config.img
If You have OnePlus 8 Pro / 8T / 9R (DDR5) You're supposed to flash xbl_lp5.img & xbl_config_lp5.img
I recommend everyone who makes fastboot flashers to include that change or make separate flashers for each codename!
Previously LP5 was only available in 9R firmware but it seems that OnePlus after joining OPPO has changed things a little and made things quite dangerous for many people.
View attachment 5578875
View attachment 5578877
Images above show that there are some checks but unfortunately they don't seem to work correctly and voltage is being set too high anyway.
So, Dear OnePlus, please stop adding non DDR5 bootloader to 8 Pro firmware builds! Or at least add protection to fail boot if DDR5 is detected.
Click to expand...
Click to collapse
This is so F'ing insane

Some extra warnings:
1. OnePlus 8T/9R also has LPDDR4x variant, make sure the variants before flashing.
2. The DDR detection process was artificially killed, stay away from the Magisk modules to keep safe.
3. TWRP is no longer recommended, use OxygenOS modified recovery or other ROM's recovery instead.
4. Flash/Root has huge risks, all operations need to be careful.
OnePlus 8 - LPDDR4x
OnePlus 8 Pro - LPDDR5
OnePlus 8T - LPDDR4x/LPDDR5
OnePlus 9R - LPDDR4x/LPDDR5

Thank you

Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.

Holy ****...
These are the images of IN2025_11_C_OTA_1100
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
my_bigball.img
my_carrier.img
my_company.img
my_engineering.img
my_heytap.img
my_manifest.img
my_preload.img
my_product.img
my_region.img
my_stock.img
odm.img
product.img
qupfw.img
recovery.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
xbl_config_lp5.img
xbl_lp5.img
And these are the images of 11.0.11.11
Code:
abl.img
aop.img
bluetooth.img
boot.img
cmnlib.img
cmnlib64.img
devcfg.img
dsp.img
dtbo.img
featenabler.img
hyp.img
imagefv.img
keymaster.img
logo.img
mdm_oem_stanvbk.img
modem.img
multiimgoem.img
odm.img
product.img
qupfw.img
recovery.img
reserve.img
spunvm.img
storsec.img
system.img
system_ext.img
tz.img
uefisecapp.img
vbmeta.img
vbmeta_system.img
vendor.img
xbl.img
xbl_config.img
Usually i use this script after changing a rom and after using MSM tool.
Code:
fastboot -w
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash recovery recovery.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot reboot fastboot
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
fastboot flash cmnlib cmnlib.img
fastboot flash cmnlib64 cmnlib64.img
fastboot flash devcfg devcfg.img
fastboot flash dsp dsp.img
fastboot flash featenabler featenabler.img
fastboot flash hyp hyp.img
fastboot flash imagefv imagefv.img
fastboot flash keymaster keymaster.img
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash opproduct opproduct.img
fastboot flash qupfw qupfw.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash product product.img
fastboot reboot fastboot
fastboot flash --slot=all abl abl.img
fastboot flash --slot=all aop aop.img
fastboot flash --slot=all bluetooth bluetooth.img
fastboot flash --slot=all cmnlib64 cmnlib64.img
fastboot flash --slot=all cmnlib cmnlib.img
fastboot flash --slot=all devcfg devcfg.img
fastboot flash --slot=all dsp dsp.img
fastboot flash --slot=all featenabler featenabler.img
fastboot flash --slot=all hyp hyp.img
fastboot flash --slot=all imagefv imagefv.img
fastboot flash --slot=all keymaster keymaster.img
fastboot flash --slot=all logo logo.img
fastboot flash --slot=all mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash --slot=all modem modem.img
fastboot flash --slot=all multiimgoem multiimgoem.img
fastboot flash --slot=all qupfw qupfw.img
fastboot flash --slot=all spunvm spunvm.img
fastboot flash --slot=all storsec storsec.img
fastboot flash --slot=all tz tz.img
fastboot flash --slot=all uefisecapp uefisecapp.img
fastboot flash --slot=all xbl_config xbl_config.img
fastboot flash --slot=all xbl xbl.img
fastboot reboot-bootloader
If i would have used this with OOS12 i would have bricked my phone on both slots instantly.....
Im so glad that i was sceptical because OOS12 had more .img files compared to OOS11 and i did not use the script.
People need to know this...
Am i right that as long as we stay on OOS11 and dont use anything from OOS12 we are good to go like before?

FYI. This is what I did to kill my phone, link below
"Warning" Total Brick After Flashing Android 12 Beta
My phone is totally bricked, and it will not respond to anything, a totally black screen, after flashing Android 12 Beta using Fastboot. I was on A12 Beta, I hated it, I wanted to flash AOSP, it did not work, so I decided to flash OOS 11 from...
forum.xda-developers.com

ProfEngr said:
Looks as if I need to just bite the bullet and roll back to 11 until 12 gets sorted. I won't hold my breath though with the rollout of the new "flagship" I doubt fixing 12 is a high priority.
Click to expand...
Click to collapse
Don't go to 12, it's LAME, Stay on 11, might even consider Samsung over OOS12

Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)

Niekdeg said:
Hi, i wanted twrp on my oneplus 8 pro IN2021 India and now i can't exit fastboot mode... when i press recovery mode then it boot into fastboot mode again.. and when i boot other rom's it stay the same (sorry bad english i am dutch lol)
Click to expand...
Click to collapse
Are you on Android 12 or 11?

nkhater said:
Are you on Android 12 or 11?
Click to expand...
Click to collapse
android 12

Niekdeg said:
android 12
Click to expand...
Click to collapse
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?

Niekdeg said:
android 12
Click to expand...
Click to collapse
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.

nkhater said:
Dude, be very careful, any wrong move you can lose your phone. I am not sure if MSMTool can help take you back to OOS 11.
download this https://androidfilehost.com/?fid=2188818919693750622
from here:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
have you ever used MSMTool?
Click to expand...
Click to collapse
i have that but my device isn't there... i have install the driver but noting..

FreshlyBaked 420 said:
Twrp is not ready for OOS 12. Next time you have a TWRP question, you should ask in the appropriate thread, and there's really no need to ask in multiple threads as you did. Keep threads on topic.
Click to expand...
Click to collapse
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same

Niekdeg said:
okay i do next time, i don't want this again.
but i flash roms all day but noting help and try other recovery image but still the same
Click to expand...
Click to collapse
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4

nkhater said:
yes it is
IN11DA tools (indian firmware):
ANDROID 11:
OOS 11.0
OOS 11.0.1.1
OOS 11.0.2.2
OOS 11.0.3.3
OOS 11.0.4.4
Click to expand...
Click to collapse
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so

Niekdeg said:
thank you, so i try them al, so just flash boot.img only or ? i don't want lose my phone so
Click to expand...
Click to collapse
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
here

nkhater said:
This is the MSMTool, there is no boot,img here, boot int EDL mode and restore your phone, watch couple of video on how to use MSMTool
Click to expand...
Click to collapse
i do but problem is my phone don't boot to edl mode

Question oneplus 11 stuck on bootloader

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help, this just happened to me, I was determined to try a covert from color os (phb110) to oxygen os, but what I experienced was difficulty so I was confused about returning the old stock rom? here I'm just stuck on the bootloader and can't access fastbootd, really just restarting the bootloader, is there a solution to fix it ??

Did you try researching this before doing this. https://forum.xda-developers.com/t/...fp-ota-bootloader-relock-pin-working.4546967/

M
MrSteelX said:
Did you try researching this before doing this. https://forum.xda-developers.com/t/...fp-ota-bootloader-relock-pin-working.4546967/
Click to expand...
Click to collapse
at first I followed the method above to convert color os to oxygen, only a few of my parts failed, and then I used another method but at that moment my fastbootd suddenly disappeared and couldn't be accessed, at this time my OnePlus just repeated to bootloader as in the photo

lhyyo06 said:
M
at first I followed the method above to convert color os to oxygen, only a few of my parts failed, and then I used another method but at that moment my fastbootd suddenly disappeared and couldn't be accessed, at this time my OnePlus just repeated to bootloader as in the photo
Click to expand...
Click to collapse
Start from step 3 again to restore fastbootd

MrSteelX said:
Start from step 3 again to restore fastbootd
Click to expand...
Click to collapse
I don't understand this step
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img comes out
Boot into fastbootd (Phone Screen: Which has language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
after I unzipped the file then what did I do with the file radio/oplusstanvbk.img ??

lhyyo06 said:
I don't understand this step
Download and unzip Abandon_PHB110_V13_202301030.zip
Unzip make sure radio/oplusstanvbk.img comes out
Boot into fastbootd (Phone Screen: Which has language selection)
Use Fastboot Enhance or command line
fastboot flash --slot=all oplusstanvbk radio/oplusstanvbk.img
after I unzipped the file then what did I do with the file radio/oplusstanvbk.img ??
Click to expand...
Click to collapse
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin

MrSteelX said:
Step 3:
Download and unzip eea73728a1b945ea8e3ff6b628495af5.zip
Goto Fastboot Enhance
Check "Ignore Unknown Partition"
Make sure fastbootd is NO (Phone Screen: The one with Menu and shows SECURE BOOT/DEVICE STATE)
Flash payload.bin
Click to expand...
Click to collapse
no no, I have succeeded with step 3, I asked again above for step 5 I don't understand. after unzipping the file, what should I do with this file radio/oplusstanvbk.img?

lhyyo06 said:
no no, I have succeeded with step 3, I asked again above for step 5 I don't understand. after unzipping the file, what should I do with this file radio/oplusstanvbk.img?
Click to expand...
Click to collapse
In fastbootd mode fastboot flash oplusstanvbk radio/oplusstanvbk.img

MrSteelX said:
In fastbootd mode fastboot flash oplusstanvbk radio/oplusstanvbk.img
Click to expand...
Click to collapse
and I always fail during this flash
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img

lhyyo06 said:
and I always fail during this flash
fastboot flash --slot=all system images/system.img
fastboot flash --slot=all system_ext images/system_ext.img
fastboot flash --slot=all vendor images/vendor.img
fastboot flash --slot=all product images/product.img
fastboot flash --slot=all my_product images/my_product.img
fastboot flash --slot=all odm images/odm.img
fastboot flash --slot=all my_engineering images/my_engineering.img
fastboot flash --slot=all vendor_dlkm images/vendor_dlkm.img
fastboot flash --slot=all system_dlkm images/system_dlkm.img
fastboot flash --slot=all my_stock images/my_stock.img
fastboot flash --slot=all my_preload images/my_preload.img
fastboot flash --slot=all my_heytap images/my_heytap.img
fastboot flash --slot=all my_carrier images/my_carrier.img
fastboot flash --slot=all my_region images/my_region.img
fastboot flash --slot=all my_bigball images/my_bigball.img
fastboot flash --slot=all my_manifest images/my_manifest.img
Click to expand...
Click to collapse
Remove --slot=all

MrSteelX said:
Remove --slot=all
Click to expand...
Click to collapse
all existing --slot=all deleted ?

lhyyo06 said:
all existing --slot=all deleted ?
Click to expand...
Click to collapse
fastboot flash system images/system.img