Database Users

Help, a/b parition screwing up my OS

Hey so I was previously on the oreo beta and reverted back to stock. I reflashed stock using a few tutorials around and it worked for a bit but magisk was screwing it up and the log file kept filling up all the storage (a known bug) and every time it rebooted it would factory reset the phone. For some reason I changed the active partition to b instead of a and magisk isnt installed but apps like snapchat don't work.
What's the best course of action to fix this? Twrp doesnt show up in recovery, its only the stock recovery. Do I need to reflash twrp on partition b and swap back to a?

Flash back to stock
Then do not lock bootloaders
Sent from my PH-1 using XDA Labs

I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?

zNiiC said:
I never locked bootloader, and do you have a good tutorial on going back to stock since the one I used didn't work that well?
Click to expand...
Click to collapse
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.

tech_head said:
This thread : https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Download one of the stock OTA firmwares and "flash_all.bat/sh"
This will flash both A/B partitions and take you back to stock.
Click to expand...
Click to collapse
Hmm thats the guide I used. I'll try it again.

zNiiC said:
Hmm thats the guide I used. I'll try it again.
Click to expand...
Click to collapse
He's what I see for a "flash_all.bat/sh" for Oreo Beta2:
fastboot flash abl_a abl
fastboot flash abl_b abl
fastboot flash bluetooth_a bluetooth
fastboot flash bluetooth_b bluetooth
fastboot flash boot_a boot
fastboot flash boot_b boot
fastboot flash cmnlib_a cmnlib
fastboot flash cmnlib_b cmnlib
fastboot flash cmnlib64_a cmnlib64
fastboot flash cmnlib64_b cmnlib64
fastboot flash devcfg_a devcfg
fastboot flash devcfg_b devcfg
fastboot flash dsp_a dsp
fastboot flash dsp_b dsp
fastboot flash hyp_a hyp
fastboot flash hyp_b hyp
fastboot flash keymaster_a keymaster
fastboot flash keymaster_b keymaster
fastboot flash mdtp_a mdtp
fastboot flash mdtp_b mdtp
fastboot flash mdtpsecapp_a mdtpsecapp
fastboot flash mdtpsecapp_b mdtpsecapp
fastboot flash modem_a modem
fastboot flash modem_b modem
fastboot flash nvdef_a nvdef
fastboot flash nvdef_b nvdef
fastboot flash pmic_a pmic
fastboot flash pmic_b pmic
fastboot flash rpm_a rpm
fastboot flash rpm_b rpm
fastboot flash system_a system
fastboot flash system_b system
fastboot flash tz_a tz
fastboot flash tz_b tz
fastboot flash vendor_a vendor
fastboot flash vendor_b vendor
fastboot flash xbl_a xbl
fastboot flash xbl_b xbl
Note that both partitions are flashed.
Look at the flash commands in the version you want to go to and make sure BOTH slots are being flashed.

I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.

zNiiC said:
I'll double check that too. Also, do I need the /sh at the end of the .bat file? I don't remember reading that I need to use that on windows.
Click to expand...
Click to collapse
I'm sure you have solved this, but for the record, it's either. .bat or .sh depending on whether you are using windows or Linux.

[easy guide] [android pie mia2] [cam2api+root]

Hello Guys
So I decided to make a more easy guide to install Android 9
Using a Fastboot Flash
-REQUIRES-
CMD (DONT WORK ON POWERSHELL)
FASTBOOT FLASH UNLOCKED
FASTBOOT FLASH_CRITICAL UNLOCKED
Download this File
https://drive.google.com/file/d/1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4/view
(This is all img of BUILD)
Download this file
https://drive.google.com/file/d/1gwmmcQ1YAqiHVqBWtgouJPOwSHpJTdOO/view?usp=drivesdk
(fastboot necessary files)
1 Extract zip of Build
2 Extract zip of fastboot files on Build folder
3 Connect MIA2 in fastboot mode
4 Start flash using the commands :
IMPORTANT NOTE
IN SYSTEM FLASH MAY YOU GIVE ERROR ON MAGIC SPARSE.
IGNORE IT AND LET FLASH FINISH
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 modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.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 hyp_a hyp.img
fastboot flash hyp_b hyp.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 abl_a abl.img
fastboot flash abl_b abl.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 mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
Your apps don't be wipped!
*If you got a Bootloop*
fastboot erase system_a
fastboot erase system_b
fastboot erase vendor_a
fastboot erase vendor_b
And flash all again
Enabled CAM2API + ROOT
Fist of all Install Magisk Manager
FIRST BOOT IN SYSTEM
Download this
https://drive.google.com/file/d/11bUI_vz4hYvxEgu5dNEkpHuNBatbAtEz/view?usp=drivesdk
Put into Build folder than
Connect in fastboot mode
And use followed command
fastboot boot patched_boot.img
Open Magisk and Directly install Magisk zip
Now go to Root Explorer
System/build.prop look for
persist.camera.hal3.enabled=0
Change to =1
Have to lines on build.prop change all.
Don't forget to hit Thanks.

riirezende said:
Hello Guys
So I decided to make a more easy guide to install Android 9
Using a Fastboot Flash
-REQUIRES-
FASTBOOT FLASH UNLOCKED
FASTBOOT FLASH_CRITICAL UNLOCKED
Download this File
https://drive.google.com/file/d/1GQc8oG90LjKneYy0vH4y9ZNb6rryELP4/view
(This is all img of BUILD)
Download this file
https://drive.google.com/file/d/1gwmmcQ1YAqiHVqBWtgouJPOwSHpJTdOO/view?usp=drivesdk
(fastboot necessary files)
1 Extract zip of Build
2 Extract zip of fastboot files on Build folder
3 Connect MIA2 in fastboot mode
4 Start flash using the commands :
IMPORTANT NOTE
IN SYSTEM FLASH MAY YOU GIVE ERROR ON MAGIC SPARSE.
IGNORE IT AND LET FLASH FINISH
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 modem_a modem.img
fastboot flash modem_b modem.img
fastboot flash xbl_a xbl.img
fastboot flash xbl_b xbl.img
fastboot flash pmic_a pmic.img
fastboot flash pmic_b pmic.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 hyp_a hyp.img
fastboot flash hyp_b hyp.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 abl_a abl.img
fastboot flash abl_b abl.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 mdtpsecapp_a mdtpsecapp.img
fastboot flash mdtpsecapp_b mdtpsecapp.img
fastboot erase ddr
fastboot reboot
Your apps don't be wipped!
Enabled CAM2API + ROOT
Fist of all Install Magisk Manager
Download this
https://drive.google.com/file/d/11bUI_vz4hYvxEgu5dNEkpHuNBatbAtEz/view?usp=drivesdk
Put into Build folder than
Connect in fastboot mode
And use followed command
fastboot boot patched_boot.img
Open Magisk and Directly install Magisk zip
Now go to Root Explorer
System/build.prop look for
persist.camera.hal3.enabled=0
Change to =1
Have to lines on build.prop change all.
Don't forget to hit Thanks.
Click to expand...
Click to collapse
If u already have magisk why u editing build.prop?
just flash camera2api enabler

Adinid said:
If u already have magisk why u editing build.prop?
just flash camera2api enabler
Click to expand...
Click to collapse
Because don't work ???
Need change stock values

riirezende said:
Because don't work ???
Need change stock values
Click to expand...
Click to collapse
u tried to install this in magisk manager?

Adinid said:
u tried to install this in magisk manager?
Click to expand...
Click to collapse
Yes Dude as I say need change values existing on build.prop

Hey.....camera2api enabler screwed my root with magisk...!!!

Can you share some AnTuTu Benchmarks scores please?

Im getting stuck on the Android One screen.

harrypakhale said:
Im getting stuck on the Android One screen.
Click to expand...
Click to collapse
same cases

Do you solve it?

harrypakhale said:
Im getting stuck on the Android One screen.
Click to expand...
Click to collapse
Same here, bootloop after flashing.

+1

EricTrasancos said:
Do you solve it?
Click to expand...
Click to collapse
No problem at the files. Must be followed correct.

JimYoung said:
Same here, bootloop after flashing.
Click to expand...
Click to collapse
hellonasty said:
+1
Click to expand...
Click to collapse
Followed correctly?
Some guys are related boot loop in all methods.
I suggest you try again slowly

I also ended up on bootloop first time. It seems that the problem was that I was using fastboot with powershell.

So if I get the error in system I should NOT try flashing system again, but just ignore it and continue with vendor?

Get bootloop. I flashed this twice and failed to boot

Worked perfectly. For those who have trouble: Make sure to wait (EVEN 10MIN IF IT'S NECESSARY) after flashing both system_a and system_b as vendor_a and vendor_b. DO NOT CLOSE CMD. Make sure to use CMD and not PowerShell. If after fastboot reboot the phone shows a flashing black screen after the Android One logo DO NOT PANIC! AFTER A WHILE IT BOOTS UP NORMALLY.

soygogeta4 said:
Worked perfectly. For those who have trouble: Make sure to wait (EVEN 10MIN IF IT'S NECESSARY) after flashing both system_a and system_b as vendor_a and vendor_b. DO NOT CLOSE CMD. Make sure to use CMD and not PowerShell. If after fastboot reboot the phone shows a flashing black screen after the Android One logo DO NOT PANIC! AFTER A WHILE IT BOOTS UP NORMALLY.
Click to expand...
Click to collapse
Mine just stuck at black screen and when I press the power button it vibrates

Worked but when i edited build.prop it messed up my root with magisk
---------- Post added at 10:39 AM ---------- Previous post was at 10:03 AM ----------
djavo22 said:
Hey.....camera2api enabler screwed my root with magisk...!!!
Click to expand...
Click to collapse
Me too, found a solution?

Bricked - Don't know what to do

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.

Can't get hard bricked OP8P to EDL mode

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

Question Unable to install any updates

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.