Question The current image (boot/recovery) have been destroyed

Search This thread
Sorry but I don't have a telegram. please write here
1. Download desired OOS firmware zip from OnePlus official website.


2. Use Payload-Dumper() to extract required img. And move the img mentioned below to some folder(let’s say xyz) inside platform tools folder(https://developer.android.com/studio/releases/platform-tools#downloads).


3. Boot to fastboot.
(Either press all 3 buttons OR adb reboot bootloader)


4. Open cmd in xyz folder and Execute these commands one by one to flash the necessary partitions:


fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


fastboot reboot bootloader


fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


5. Press the volume down button until you see “Recovery” and then press the power button.


6. Wipe system and data from stock recovery and reboot😏.


OPTIONAL:
7. To relock the bootloader-
fastboot oem lock


8. Done!
 
Last edited:
Sorry but I don't have a telegram. please write here
Do let me know if this worked, when you tried.

Also, I created this thread with required files/links, hope this help-
 

hamsteer

Member
Jun 4, 2014
12
1
1. Download desired OOS firmware zip from OnePlus official website.


2. Use Payload-Dumper() to extract required img. And move the img mentioned below to some folder(let’s say xyz) inside platform tools folder(https://developer.android.com/studio/releases/platform-tools#downloads).


3. Boot to fastboot.
(Either press all 3 buttons OR adb reboot bootloader)


4. Open cmd in xyz folder and Execute these commands one by one to flash the necessary partitions:


fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


fastboot reboot bootloader


fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


5. Press the volume down button until you see “Recovery” and then press the power button.


6. Wipe system and data from stock recovery and reboot😏.


OPTIONAL:
7. To relock the bootloader-
fastboot oem lock


8. Done!
 

hamsteer

Member
Jun 4, 2014
12
1
C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot devices
BA*************** fastboot

C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot -set-active=a
fastboot: usage: no command

I think it's because phone is in fastboot , not fastbootd

After flashing each partition with the corresponding img file in FastbootEnhance, the phone booted into recovery. After wiping the data and restarting the phone works
 
Last edited:
C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot devices
BA*************** fastboot

C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot -set-active=a
fastboot: usage: no command

I think it's because phone is in fastboot , not fastbootd

After flashing each partition with the corresponding img file in FastbootEnhance, the phone booted into recovery. After wiping the data and restarting the phone works
So your phone finally booted right. Great!
 
C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot devices
BA*************** fastboot

C:\oneplus\platform-tools_r33.0.2-windows\platform-tools\xyz>fastboot -set-active=a
fastboot: usage: no command

I think it's because phone is in fastboot , not fastbootd

After flashing each partition with the corresponding img file in FastbootEnhance, the phone booted into recovery. After wiping the data and restarting the phone works
Hey since your phone was not booting, how did you manage to boot into fastboot mode or how your device got detected on Fastboot Enhance?
 
Last edited:

wyman34

Member
May 27, 2006
7
0
1. Download desired OOS firmware zip from OnePlus official website.


2. Use Payload-Dumper() to extract required img. And move the img mentioned below to some folder(let’s say xyz) inside platform tools folder(https://developer.android.com/studio/releases/platform-tools#downloads).


3. Boot to fastboot.
(Either press all 3 buttons OR adb reboot bootloader)


4. Open cmd in xyz folder and Execute these commands one by one to flash the necessary partitions:


fastboot –set-active=a
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


fastboot reboot bootloader


fastboot –set-active=b
fastboot format:ext4 userdata
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash odm odm.img
fastboot flash system system.img
fastboot flash vbmeta vbmeta.img
fastboot flash vendor vendor.img


5. Press the volume down button until you see “Recovery” and then press the power button.


6. Wipe system and data from stock recovery and reboot😏.


OPTIONAL:
7. To relock the bootloader-
fastboot oem lock


8. Done!
I try to use this method, but when flash system.img it show "invalid sparse file format at header magic", then i used "fastboot getvar all" command it show many partition is raw, any ideas how to fix it? Thanks.
 

Attachments

  • PXL_20220813_161521420.MP.jpg
    PXL_20220813_161521420.MP.jpg
    6.7 MB · Views: 53
  • PXL_20220813_161449985.MP.jpg
    PXL_20220813_161449985.MP.jpg
    5.7 MB · Views: 53
I try to use this method, but when flash system.img it show "invalid sparse file format at header magic", then i used "fastboot getvar all" command it show many partition is raw, any ideas how to fix it? Thanks.
Try using the latest platform tools. Open cmd inside the latest platform tools folder, if still not working you can try the fastboot enhance method.

 

wyman34

Member
May 27, 2006
7
0
Try using the latest platform tools. Open cmd inside the latest platform tools folder, if still not working you can try the fastboot enhance method.

Try it but still got the same result, is it no hope to fix, thanks
 

hack-worker

Member
Oct 24, 2009
21
4
Добрый день всем. Друзья, кто-то знает способ оживить это.
 

Attachments

  • IMG_20220905_020129.jpg
    IMG_20220905_020129.jpg
    1.4 MB · Views: 28
Last edited:

hack-worker

Member
Oct 24, 2009
21
4
I came across instructions for reviving Nord 2 with the same screen here https://4pda.to/forum/index.php?showtopic=1043520&view=findpost&p=115266047, but this method did not work for me. When I try to turn on the phone in BROM mode, it starts a cyclic reboot. when the red alert screen turns on, the phone goes out of the device manager, turns off appears in the device manager. If disconnected from the computer restarts stop. Does anyone have any ideas? Or everything, you can not even seek salvation?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    There are two ways, the first is through contacting the Oneplus support service (but you need to have an account of the region to which the smartphone belongs, China or India), it's free. The service employee will connect remotely to your computer and do everything himself. The second way is paid, it is easy to find through Google. The result and actions are the same. I used the second method, since I have a Chinese phone, I myself am from Russia and I did not succeed in creating an account in the Chinese region of Oneplus. They have a mandatory condition, is to link a mobile phone number when creating an account, and numbers for (+7) Russia code are not active for them.
    1
    Made some progress!
    Got my hands on the Ace's firmware files, which included the scatter file. Redownloaded the newest 6.2 version of SP Flash Tool and loaded the scatter and auth files successfully. Clicked download, connected USB to phone while holding Vol + and Vol - and finally! Sp Flash Tool connected to the phone! However, now I've run into another problem: SP Flash Tool will show a red progress bar at the bottom saying 'Download DA', it will reach 100% quickly then throw me a very vague error simply saying 'error_msg'. And that's it. Tried unchecking different boxes, reinstalled drivers but it will always throw back this error.
    Any ideas to figure out what the error is and fix it would be amazing
    1
    hold the power button+vol up+vol down and then connect the usb cable to pc. The phone screen should remain black but it should be detected in mtk client. If Mtkclient freezes on "waiting for preloader VCOM", or the phone keeps rebooting itself out of BROM mode, keep rebooting the phone into BROM mode without letting go of the buttons, without disconnecting it from the pc, and without closing Mtkclient. And release all the buttons just when the phone has been detected. (It could need 2 to 3 reboots. If more, disconnect the cable and retry).
    Thank you, of course, but with this phone it does not work that way.