I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Dapherino said:
I was able to successfully follow all the steps for a fastboot rom, but it still didn't work. This was through using fastboot boot on the lineageos recovery.
Click to expand...
Click to collapse
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
xtcislove said:
Use MSM Tool. Hold all buttons very until your device appears in msm tool. YOu can start before you connect it and it should work.
Click to expand...
Click to collapse
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Dapherino said:
Thanks. I've tried this already. It doesn't boot into EDL. It just displays the first error message or boots into fastboot. Even if I use 'fastboot boot twrp...' and click 'reboot to edl' it doesn't work.
Click to expand...
Click to collapse
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
jamescable said:
Turn phone completely off. On msm tool, hit start so its waiting for device. Hold down ONLY the volume up and volume down buttons, plug in USB cable and you're good to go
Click to expand...
Click to collapse
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
xtcislove said:
Try to press start while the device is connected and then restart it. MSM tools trys to hook in first.
Click to expand...
Click to collapse
Thanks, I've tried this as well. It didn't work, since I cannot enter EDL mode.
Dapherino said:
Thank you for the advice. I've tried this and it doesn't do anything, since I can't get to EDL mode.
Click to expand...
Click to collapse
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
jamescable said:
Your phone is in EDL mode when its powered off and holding ONLY both volume bottons
Click to expand...
Click to collapse
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Dapherino said:
I understand that. When I do so, it just boots into fastboot. And when I tried to enter EDL through using 'fastboot boot' with a custom recovery, it did the same thing. Now I can't even use 'fastboot boot' anymore for some reason though.
Click to expand...
Click to collapse
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
jamescable said:
So you tried fastboot boot recovery?
Fastboot boot will never work to boot edl
Click to expand...
Click to collapse
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Dapherino said:
Yes. Even from a temporary custom recovery, I cannot enter edl from there.
Click to expand...
Click to collapse
Do this. Install a custom ROM using fastboot
Download any ROM you want. Extract the payload and put it in the payload input folder.
jamescable said:
Download any ROM you want. Extract the payload and put it in the payload input folder.
Click to expand...
Click to collapse
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Dapherino said:
I've tried this with 4 different roms [stock oneplus one, lineageos, pixel experience, and evolutionx]. Even though they flash successfully, I still encounter the exact same error when trying to boot into it, and I still cannot enter recovery or EDL.
Click to expand...
Click to collapse
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
xtcislove said:
This wont work and idk why. If i try a custom rom i always have to use msm tool to go back to oos.
I flash every partition with fastboot but i end in a boot loop if i where on a custom rom before.
Click to expand...
Click to collapse
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Dapherino said:
I accidentally disconnected my OnePlus 8 Pro while running the MSM Tool to restore back to oxygenos from lineage. Now it is stuck in a loop where it says:
<Error!>
Upgrade download failed!
This is caused by download interruption. Recommend you use download tool try again.
You need to confirm if there is failure message on download tool or not when you see this error.
also please check if you disconnect usb or click stop button when the download is not finished yet.
You can press any key exit this message
I can boot into fastboot from this state, but I am unable to flash a recovery or use a fastboot rom.
The recovery just doesn't work when I try to boot into it, and the fastboot rom gets stuck at
"Flashing is not allowed for critical partitions"
and when I try running
fastboot flashing unlock_critical
it says something along the lines of 'device already unlocked'
I cannot boot into EDL mode either, and trying to do so doesn't work.
I feel as if I am out of options, and am very worried about my phone.
Please help!!!
Click to expand...
Click to collapse
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
jamescable said:
Yeah, you need to wipe internal storage. In fastboot you can type
fastboot format userdata
fastboot format cache
Also, you can type
Fastboot -w
Click to expand...
Click to collapse
thats part of my batch script anyway.
Code:
:choice
set /P c=Do you want to wipe all the data ( Reccomended )[Y/N]?
if /I "%c%" EQU "Y" goto :wipe
if /I "%c%" EQU "N" goto :continue
goto :choice
:wipe
fastboot -w
goto :continue
:continue
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
pause
wgs1028 said:
This happened to me. I tried downloading Qualcomm drivers and reinstalling them and moved my platform tools to root of C:\, among other things. I was using OEM red cable and had been having to flip it a certain way to get WARP charge, so in desperation, I switched to a non-OEM cable, C to C, and that got me back in EDL. Good luck.
Click to expand...
Click to collapse
THANK YOU SO MUCH!!!!! Using a different cable worked!!!!!!!!!!!!!!!!!!!!!!!!!!!! I'm so glad my phone is ok. Thank you again, I really appreciate it.
Related
Hello,
I was playing around with the Mi A1 magisk and i was flashing it. But then i by accident pressed lock bootloader (and confirming because i did not payed attention to what it was saying) and now the phone is BRICKED :crying: Only thing i get is the connect sound when connected to PC, but the phone shows NOTHING , just black and vibrates when i hold power and any other button. (no fastboot or recovery)
I think it is done for :crying: which hurts me to say cuz i got it as gift.
I think it will be expensive to fix in service center..
PLEASE HELP IF YOU CAN AS FAST AS POSSIBLE
Thanks in advance.
Same happened to me. Did you change anything with tools? did you erase partitions? what exactly thing were you doing to brick it? only press the lock cant brickt it. Normally you can just re-unlock it and flash with the stockrom. Just give us more information about the process you were doing
Actually i booted TWRP by mohacm flashed Magisk then i powered off the phone and than it happend. When it locked i turned it on and showed the colorfull bar and Mi logo for split second and turned off every single time. After re-unlocking it was in bootloop so i tried to restore with Mi Flash tool and it showed error at the end (something wrong with partition b flash) So i tried again and it froze so i turned the tool off and it put it the state it is now.
Also the response of the phone happens only when plugged to PC
You've bricked nothing at all, just chill. I suppose you've installed all the drivers for the A1 while installing the Mi Flash if yes then install minimal adb and fastboot tool, paste all the files from the images folder from the firmware file to the directory of the minimal adb and fastboot tool, open cmdhere.exe located in minimal adb and fastboot tool folder, boot you phone into fastboot mode(press and hold volume down and power buttons at the same time till fastboot bot appears), plug the phone to the pc, enter the following commands:
- fastboot devices (You should see your device's serial tex next to fastboot text if you see nothing, install fastboot drivers properly)
- fastboot flash modem_a modem.img
- fastboot flash modem_b modem.img
- fastboot flash sbl1 sbl1.img
- fastboot flash sbl1back sbl1.img
- fastboot flash rpm rpm.img
- fastboot flash rpmbak rpm.img
- fastboot flash tz tz.img
- fastboot flash tzback tz.img
- fastboot flash devcfg devcfg.img
- fastboot flash devcfgback devcfg.img
- fastboot flash dsp adspso.bin
- fastboot flash sec sec.dat
- fastboot flash splash splash.img
- fastboot flash misc misc.img
- fastboot flash aboot emmc_appsboot.mbn
- fastboot flash abootbak emmc_appsboot.mbn
- 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 lksecapp lksecapp.img
- fastboot flash lksecappbak lksecapp.img
- fastboot flash cmnlib cmnlib.img
- fastboot flash cmnlibbak cmnlib.img
- fastboot flash cmnlib64 cmnlib64.img
- fastboot flash cmnlib64bak cmnlib64.img
- fastboot flash keymaster keymaster.img
- fastboot flash keymasterbak keymaster.img
- fastboot flash userdata userdata.img
- fastboot reboot
Done!
But the problem is that i cannot boot into fastboot. The phone doesent respond to any actions. I was writing it on the top of the thread. If could boot into fastboot then i would use Mi tool again.
Also when the phone is connected to the PC and i hold the Power and volume buttons (up or down doesent matter) nothng happens just the PC does the dis and connect sounds
try hold volume and and down and then connect to pc after that hold power button volume +,- in the same time then wait 6sec . check if ur phone detect on devie manager port
The PC CAN detect the phone. The problem is not in PC but in the phone cuz it wont boot or show NOTHING on the screen whatsoever.
The PC recognizes it as Qualcomm HS-USB Diagnostics 900E (COM3)
AND you're dumb enough to not mention that. If so buy a cheap type-c cable that works on your phone, make it a deep flash cable(search on youtube how to make it) and flash the stock rom using it, that's my best bet.
dont get how someone can mess up the bootloader. i think in 10 years of my phonelife the bootloader menu never bugged.
Ok guys,
Thanks to everyone who helped my phone Is Back alive thx to Xiaomi Service center.
Hello Everyone
My Oneplus 8 Pro won't turn on at all , not to recovery mode , not to fastboot mode , not to EDL mode , not even to charge... nothing
And I'm pretty sure everything is set up correctly , the msm tool , the qualcomm drivers , the cable and the port because i have an old oneplus 3t which i'm using for now and it got recognized in the msm tool as soon as i connected it
Here is some context of what happened before my Oneplus 8 Pro died :
I never flashed any custom roms on it , i've been using the stock firmware with root the whole time
I had a custom kernel installed on Android 11 before updating to Android 12 , when i updated to Android 12 (OTA update) the kernel went back to the stock one
after updating to Android 12 there was another OTA update that always fails to install (I believe it was 11.c.16), i got tired of it so i decided to manually updating to the latest firmware including that 11.c.16 incremental update and be done with it
I couldn't sideload it using TWRP becuase i couldn't install TWRP , everytime i tried to flash it using fastboot it seems like it succeeded but when i boot to recovery it boots to fastboot mode
so i googled how to install a firmware using fastboot commands , i found a method to flash the files one by one after extracting them using payload dumper and i tried it , when i was done flashing the files , as soon as i hit enter on the last command to reboot the phone it went to a black screen and has been dead ever since
Here are the fastboot commands i used to flash the firmware :
Code:
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 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 -w
fastboot reboot
Sorry for taking so long , I'm desperate
Any kind of help , suggestions or ideas are much appreciated
I haven't been keeping up on that thread since since it doesn't affect me, but I think you fell into the known "OOS Deathtrap" that's been explained here.
Like I said - no idea if it has a solution, or even if there is one now, but it couldn't hurt to read it.
Well... at least now i know what caused the issue , unfortunately i don't think there is a solution other than replacing the motherboard (which was the the solution i wanted to avoid)
I think it's time to say goodbye to oneplus
I wish i had read that article before flashing , Oneplus should put a disclaimer or a warning or something
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Reserved.
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Nimiskiv said:
try a fastboot boot twrp ( https://github.com/ApexLegend007/twrp_device_oneplus_lemonades/releases ) and try factory resetting it then see if you can switch your partition from a to be or b to a then try msm flashing ( https://androidfilehost.com/?fid=17248734326145733797 )
Click to expand...
Click to collapse
I can't even boot TWRP, it just shows the Oneplus logo and the"fastboot mode" thing forever. It's been 10 minutes now.
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
BillGoss said:
If you've used MSM then you're on OOS 11.
I assume the phone boots properly after MSM.
On OOS 11 you can only use TWRP 11 from https://dl.twrp.me/kebab/
And you can only use TWRP 12 on OOS 12 from https://forum.xda-developers.com/t/...in-recovery-project-8t-9r-2022-07-27.4473983/
PS: and you should have posted this in the 8T Q&A forum.
Click to expand...
Click to collapse
nope, still cant boot into twrp
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
BillGoss said:
Version of OOS?
Version of TWRP?
Does OOS boot cleanly?
What's your phone?
Click to expand...
Click to collapse
OOS is 11.1.0.2.KB09CB
I've tried TWRP 3.6.1, 3.6.0, and 3.6.2
OOS does boot cleanly.
Phone is KB2007.
The bootloader is unlocked.
I've truly never had this problem before.
You'll probably have to upgrade to the latest version of OOS 11 (or 12) before TWRP will boot.
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version (kb2005) it can work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin unto payload dumper after extracting them all into a folder then use the commands to flash them all with adb. Then reboot to recovery, factory reset, and MSM tool back to TMO.
do these commands one by one replacing the .img with the location of the .img. actually, just drag and drop the file after. ( ex: fastboot flash logo C:\Users\???\Desktop\???.img )
Just an extra recommendation to wipe the device
( Fastboot -w )BEFORE THE OTHER COMMANDS but you don't need to if it works without wiping.
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
I'm way too inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
honest recommendation, just use TMO to International MSM tool after. unless you want to keep it TMO (kb2007)
Nimiskiv said:
I have an idea, if you are in fast boot mode then you can flash everything manually. ( https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/ ) there's only international version so we got to work with that. Just use payload dumper to extract all the .img by dragging and dropping the payload.bin then use the .bat to flash them all onto the phone. Then reboot to recovery, factory reset and MSM tool it back to tmo. do these commands one by one replacing the .img with the location of the .img. actually just drag and drop the file after. ex: fastboot flash app (file)
fastboot flash logo logo.img
fastboot flash mdm_oem_stanvbk mdm_oem_stanvbk.img
fastboot flash modem modem.img
fastboot flash multiimgoem multiimgoem.img
fastboot flash odm odm.img
fastboot flash qupfw qupfw.img
fastboot flash recovery recovery.img
fastboot flash spunvm spunvm.img
fastboot flash storsec storsec.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash tz tz.img
fastboot flash uefisecapp uefisecapp.img
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot --disable-verity flash vbmeta_system vbmeta_system.img
fastboot flash vendor vendor.img
fastboot flash xbl xbl.img
fastboot flash xbl_config xbl_config.img
Ex: fastboot flash app ( c:/????/desktop/payload_dumper/extracted/app.img ) idk
Just an extra recommended to wipe the device
Fastboot -w but you don't need to if it works without.
I'm way to inexperienced with this but if anything goes wrong you can MSM tool back to fastboot.
Click to expand...
Click to collapse
MirageSteezyBoi said:
I've MSM'ed about 8 times today. Every single time I attempt to flash recovery, no matter which recovery, it overwrites the system and upon rebooting to recovery through fastboot, it permanently stays in fastboot. I can MSM out of it. I've tried conversion MSM, temporarily booting recovery, flashing firmwares, resetting, wiping. I cannot fix this. I have spent over 11 hours trying to troubleshoot this. Google comes up with useless results. This is the first time I've not been able to recover from a situation with this phone. Please, if you have any ideas, shoot. The model is kb2007.
Click to expand...
Click to collapse
Sorry I'm very bad at this. I was thinking you didn't even boot properly.... just update to the latest using oxygen updater or the systems bultin update... Im a moron and ill be leaving that up there.
So I flashed my phone using the fastboot ROM from this page.
reindex-ot.github.io
Re*Index. GitHub Pages
reindex-ot.github.io
I downgraded, even upgraded using this method to get root and call recording. All went fine, downgrading, upgrading, root, etc. Except no matter what I do all I get is a brown background with no customization options in any of the ROMS. They all produce the same.
What am I missing here ?
Thanks !
That's it . That's all !
rogerrulez said:
So I flashed my phone using the fastboot ROM from this page.
reindex-ot.github.io
Re*Index. GitHub Pages
reindex-ot.github.io
I downgraded, even upgraded using this method to get root and call recording. All went fine, downgrading, upgrading, root, etc. Except no matter what I do all I get is a brown background with no customization options in any of the ROMS. They all produce the same.
What am I missing here ?
Thanks !
Click to expand...
Click to collapse
What more you think of that ROM has?
solomon.rajan said:
What more you think of that ROM has
Click to expand...
Click to collapse
solomon.rajan said:
What more you think of that ROM has?
Click to expand...
Click to collapse
Seriously ?
Can't help you unless you mention what you're looking for
What i do if i like to go "stock" to do clean updates or to simply set everything to default.
I restore/downgrade to 1.1.3 (all partitions + super partition) and update via ADB sideload or system update.
Never had "missing wallpapers" if i get your problem correctly.
xtcislove said:
What i do if i like to go "stock" to do clean updates or to simply set everything to default.
I restore/downgrade to 1.1.3 (all partitions + super partition) and update via ADB sideload or system update.
Never had "missing wallpapers" if i get your problem correctly.
Click to expand...
Click to collapse
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.
rogerrulez said:
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.
Click to expand...
Click to collapse
Tool found here:
unbrick tool- EDL Flash-Read-Repair Region Change tool
unbrick tool Now available for Nothing Phone1.. Features: Read Firmware (EDL) (locked bootloader) Flash Firmware (EDL) (locked bootloader) backup EFS (EDL) (locked bootloader) Wipe FRP & userdata (EDL) (locked bootloader) Size: 2.7GB Version...
forum.xda-developers.com
That hard part is getting your phone to boot to EDL (if you're bricked) otherwise that'll shoot you straight back to stock with bootloader still unlocked.
rogerrulez said:
Yeah that’s what I would like to do. There is an msmtool out there but there are no links to download the necessary files.
Click to expand...
Click to collapse
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
You need EEA fastboot rom of 1.1.3 and the super.img from post 2.
This tutorial works fine.
I simply have a batch script with this content:
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause
Okay so, I did root and downgraded to acquire call recording and root. Then I upgrading using the fastboot method. Locked up the critical partition but left the bootloader unlocked.
There is an update for the 2.5.3 I'm on but I cannot apply it through the official update method or the dialer method !
I've flashed both partitions with the same ROM. It is the global version I have.
What am I missing here ?
Thanks in advance.
Try adb sideload
Try to remove root before update
So like, no one knows ?
xtcislove said:
Try adb sideload
Try to remove root before update
Click to expand...
Click to collapse
I don't have root and all partitions are locked.
I can try adb sideload again but I have my doubts.
I need a way to completely flash and start over I think. This phone is weird.
"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.
Moderator Announcement
Thread sanitized of all "snarky" and disrespectful replies.
Greetings to all. Just a friendly reminder if I may regarding XDA Rule 2.3 regarding member conduct:
2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
Click to expand...
Click to collapse
Please be polite to each other, and instead of replying to member comments that you may find offensive, please report them instead rather than creating a "flame war" requiring
Moderator interventions such as this. Thank you.
Regards to all: Badger50
xtcislove said:
"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.
Click to expand...
Click to collapse
Thanks. I will try that.
Badger50 said:
Moderator Announcement
Thread sanitized of all "snarky" and disrespectful replies.
Greetings to all. Just a friendly reminder if I may regarding XDA Rule 2.3 regarding member conduct:
Please be polite to each other, and instead of replying to member comments that you may find offensive, please report them instead rather than creating a "flame war" requiring
Moderator interventions such as this. Thank you.
Regards to all: Badger50
Click to expand...
Click to collapse
Okay will do. Thanks.
xtcislove said:
"I need a way to completely flash and start over I think. This phone is weird."
How to unbrick Nothing Phone 1 fastboot bootloop
Welcome to this unbrick tutorial NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours. I do not suggest following this tutorial if...
forum.xda-developers.com
Follow this guide and in the end relock the bootloader if you like. I did this several times and i get normal otas after this.
Click to expand...
Click to collapse
But ... none of the files are downloadable.
rogerrulez said:
Okay will do. Thanks.
Click to expand...
Click to collapse
I was reacting to how I was talked to. Simple. And I will do it again to someone who tries to demean or belittle me.
rogerrulez said:
I was reacting to how I was talked to. Simple. And I will do it again to someone who tries to demean or belittle me.
Click to expand...
Click to collapse
Please read my PSA again about "reporting" these matters rather than replying to them.
Thank you.
rogerrulez said:
But ... none of the files are downloadable.
Click to expand...
Click to collapse
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Edit: All you need is the 1.1.4 Global super.img and and 1.1.4 fastboot global rom.
You need this code to flash the images, obviously you need to edit the lines to fit your file path. Since you are an experienced user this should not be a problem.
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
REM fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause
xtcislove said:
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Click to expand...
Click to collapse
Thanks. Yeah, I've looked a that. But I compared both files and don't see any differences in the batch files. SO I'm wondering ... how is this better ?
rogerrulez said:
Thanks. Yeah, I've looked a that. But I compared both files and don't see any differences in the batch files. SO I'm wondering ... how is this better ?
Click to expand...
Click to collapse
Which two batch files? They will flash the super.img and ALL other partitions. The code i posted will flash BOTH slots.
You need a way to completely flash and start over. This is the way.
xtcislove said:
Which two batch files? They will flash the super.img and ALL other partitions. The code i posted will flash BOTH slots.
You need a way to completely flash and start over. This is the way.
Click to expand...
Click to collapse
Correct. I need to start over.
rogerrulez said:
Correct. I need to start over.
Click to expand...
Click to collapse
So whats the problem now?
1. Unlock Bootloader
2. Flash super.img
3. Flash fastboot rom to both slots.
4. Relockk bootloader or boot to android.
xtcislove said:
So whats the problem now?
1. Unlock Bootloader
2. Flash super.img
3. Flash fastboot rom to both slots.
4. Relockk bootloader or boot to android.
Click to expand...
Click to collapse
Thanks. Done that. many times actually. lol
rogerrulez said:
Thanks. Done that. many times actually. lol
Click to expand...
Click to collapse
And you installed all updates normaly with system updates or did you install anything manually?
xtcislove said:
I checked every link and all are downloadable.
Super.img
Shattered tool (an alternative could be to download from the 1.1.4 fastboot rom from https://reindex-ot.github.io/ and use the cmd commands i posted you a few days ago)
every link is working and you should already setup platform tools.
What you are trying to download what is not working?
Edit: All you need is the 1.1.4 Global super.img and and 1.1.4 fastboot global rom.
You need this code to flash the images, obviously you need to edit the lines to fit your file path. Since you are an experienced user this should not be a problem.
Code:
cd /d F:\Android\NothingPhone1\Other\platform-tools_r33.0.2-windows
fastboot -w
fastboot --set-active=a
fastboot reboot fastboot
fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_a F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_a F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_a F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_a F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_a F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_a F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_a F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_a F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_a F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_a F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_a F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_a F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_a F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_a F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_a F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_a F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_a F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_a F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_a F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_a F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_a F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_a F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_a F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_a F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_a F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=b
fastboot reboot fastboot
REM fastboot flash super F:\Android\NothingPhone1\Firmware\1.1.3_EEA_super_backup\super.img
fastboot flash abl_b F:\Android\NothingPhone1\Firmware\1.1.3\abl.img
fastboot flash aop_b F:\Android\NothingPhone1\Firmware\1.1.3\aop.img
fastboot flash bluetooth_b F:\Android\NothingPhone1\Firmware\1.1.3\bluetooth.img
fastboot flash boot_b F:\Android\NothingPhone1\Firmware\1.1.3\boot.img
fastboot flash cpucp_b F:\Android\NothingPhone1\Firmware\1.1.3\cpucp.img
fastboot flash devcfg_b F:\Android\NothingPhone1\Firmware\1.1.3\devcfg.img
fastboot flash dsp_b F:\Android\NothingPhone1\Firmware\1.1.3\dsp.img
fastboot flash dtbo_b F:\Android\NothingPhone1\Firmware\1.1.3\dtbo.img
fastboot flash featenabler_b F:\Android\NothingPhone1\Firmware\1.1.3\featenabler.img
fastboot flash hyp_b F:\Android\NothingPhone1\Firmware\1.1.3\hyp.img
fastboot flash imagefv_b F:\Android\NothingPhone1\Firmware\1.1.3\imagefv.img
fastboot flash keymaster_b F:\Android\NothingPhone1\Firmware\1.1.3\keymaster.img
fastboot flash modem_b F:\Android\NothingPhone1\Firmware\1.1.3\modem.img
fastboot flash multiimgoem_b F:\Android\NothingPhone1\Firmware\1.1.3\multiimgoem.img
fastboot flash odm_b F:\Android\NothingPhone1\Firmware\1.1.3\odm.img
fastboot flash product_b F:\Android\NothingPhone1\Firmware\1.1.3\product.img
fastboot flash qupfw_b F:\Android\NothingPhone1\Firmware\1.1.3\qupfw.img
fastboot flash shrm_b F:\Android\NothingPhone1\Firmware\1.1.3\shrm.img
fastboot flash system_b F:\Android\NothingPhone1\Firmware\1.1.3\system.img
fastboot flash system_ext_b F:\Android\NothingPhone1\Firmware\1.1.3\system_ext.img
fastboot flash tz_b F:\Android\NothingPhone1\Firmware\1.1.3\tz.img
fastboot flash uefisecapp_b F:\Android\NothingPhone1\Firmware\1.1.3\uefisecapp.img
fastboot flash vbmeta_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta.img
fastboot flash vbmeta_system_b F:\Android\NothingPhone1\Firmware\1.1.3\vbmeta_system.img
fastboot flash vendor_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor.img
fastboot flash vendor_boot_b F:\Android\NothingPhone1\Firmware\1.1.3\vendor_boot.img
fastboot flash xbl_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl.img
fastboot flash xbl_config_b F:\Android\NothingPhone1\Firmware\1.1.3\xbl_config.img
fastboot reboot bootloader
fastboot --set-active=a
fastboot reboot
pause
Click to expand...
Click to collapse
Okay. Thanks man.
No ! My phone is turned off. I can't do any updates.