How To Guide How to unbrick Nothing Phone 1 fastboot bootloop

Search This thread
By:
Advanced…
A

AntoXik72

Senior Member
Feb 27, 2013
109
53
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 you are on 1.1.4 but since your phone is already out of usage, you can try on your own.

In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.

You are missing some of the phone partitions? This might solve your issue.

Let's begin!

MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed


STEP 1 : Prepare everything

Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
fastboot devices
Click to expand...
Click to collapse

If a line appears, your phone is correctly connected.

Type the command :
fastboot flash super super.img
Click to expand...
Click to collapse

If it flashed correctly, you should see something like this :
C:\Users\Alex\Desktop\platform-tools>fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/9 (786428 KB) OKAY [ 19.574s]
Writing 'super' OKAY [ 0.013s]
Sending sparse 'super' 2/9 (786428 KB) OKAY [ 19.587s]
Writing 'super' OKAY [ 0.018s]
Sending sparse 'super' 3/9 (786428 KB) OKAY [ 19.609s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 4/9 (698716 KB) OKAY [ 17.393s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 5/9 (765968 KB) OKAY [ 19.103s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 6/9 (763420 KB) OKAY [ 19.074s]
Writing 'super' OKAY [ 0.017s]
Sending sparse 'super' 7/9 (786097 KB) OKAY [ 19.636s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 8/9 (786089 KB) OKAY [ 19.745s]
Writing 'super' OKAY [ 0.029s]
Sending sparse 'super' 9/9 (102406 KB) OKAY [ 2.853s]
Writing 'super' OKAY [ 6.798s]
Finished. Total time: 167.087s
Click to expand...
Click to collapse

Once that step is done, your phone has now working super partitions.


STEP 2 : Flash stock firmware

After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.

Download the correct region and version of the firmware.

Once the Firmware is downloaded, you should see a new fw.zip

Run the flash_all.bat script, it should flash all the partitions without issues.

If something went wrong, tell me in the comment section.

Then, your device should reboot.



STEP 3 : Check your slots

If your device is still not booting, simply change the slot you're on with the following commands :

fastboot reboot fastboot
Click to expand...
Click to collapse

You should reboot into fastbootd.

Then use :
fastboot getvar all
Click to expand...
Click to collapse

Look for the line where it says current-slot and it will tell you if it's A slot or B slot

Once you know on wich slot you are, try booting on the other one by running this last command :

fastboot set_active b
Click to expand...
Click to collapse
If you're on a slot, or :


fastboot set_active a
Click to expand...
Click to collapse
If you're on b slot.


Reboot your phone after that, and you should boot normally.



If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes

Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
 
Last edited:
  • Like
Reactions: 0jas, riccardorossi64, EnioSAF and 5 others
A

AntoXik72

Senior Member
Feb 27, 2013
109
53
Update :

Here are listed all the Super Partitions available for us to fix our Nothing :

1.1.3 EEA : Link

1.1.4 Global : Link

More to come...


Remember that you have to download the Sh4ttered tool version according to the version you are trying to restore.


Again, feel free to share a backup of yours that is not listed here to help other in need ;)
 
Last edited:
A

arinc9

Member
Sep 25, 2017
10
3
Nothing Phone 1
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.

There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.

Code: 
Erasing 'userdata'                                 OKAY [  0.027s]

    F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
        Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata

Wiping data on userspace fastboot works:

Code: 
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot                            OKAY [  0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata'                                 OKAY [  0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 OKAY [  0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s

There were also problems with flashing to B slot.

Code: 
Sending 'odm_b' (1052 KB)                          OKAY [  0.024s]
Writing 'odm_b'                                    FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB)         OKAY [  6.057s]
Writing 'product_b'                                FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB)                          OKAY [  0.002s]
Writing 'qupfw_b'                                  OKAY [  0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB)                           OKAY [  0.002s]
Writing 'shrm_b'                                   OKAY [  0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB)          OKAY [  6.077s]
Writing 'system_b'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB)      OKAY [  6.133s]
Writing 'system_ext_b'                             FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB)                           OKAY [  0.083s]
Writing 'tz_b'                                     OKAY [  0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.004s]
Writing 'uefisecapp_b'                             OKAY [  0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.000s]
Writing 'vbmeta_b'                                 OKAY [  0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_b'                          OKAY [  0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB)          OKAY [  6.079s]
Writing 'vendor_b'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
 
A

AntoXik72

Senior Member
Feb 27, 2013
109
53
arinc9 said:
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.

There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.

Code: 
Erasing 'userdata'                                 OKAY [  0.027s]

    F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
        Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata

Wiping data on userspace fastboot works:

Code: 
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot                            OKAY [  0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata'                                 OKAY [  0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata'                                 OKAY [  0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s

There were also problems with flashing to B slot.

Code: 
Sending 'odm_b' (1052 KB)                          OKAY [  0.024s]
Writing 'odm_b'                                    FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB)         OKAY [  6.057s]
Writing 'product_b'                                FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB)                          OKAY [  0.002s]
Writing 'qupfw_b'                                  OKAY [  0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB)                           OKAY [  0.002s]
Writing 'shrm_b'                                   OKAY [  0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB)          OKAY [  6.077s]
Writing 'system_b'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB)      OKAY [  6.133s]
Writing 'system_ext_b'                             FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB)                           OKAY [  0.083s]
Writing 'tz_b'                                     OKAY [  0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.004s]
Writing 'uefisecapp_b'                             OKAY [  0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.000s]
Writing 'vbmeta_b'                                 OKAY [  0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_b'                          OKAY [  0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB)          OKAY [  6.079s]
Writing 'vendor_b'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed

Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
Click to expand...
Click to collapse
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty for now.
On Xiaomi forum, they solved the issue by flashing the persist partition from a stock fastboot rom, can't tell if it'll work with yours but you Can Always give it a try if you can find a persist partition backup
 
Last edited:
sh4tteredd

sh4tteredd

Senior Member
Aug 9, 2022
79
61
Italy
AntoXik72 said:
That's perfect, thanks, i'll update the post tonight
Click to expand...
Click to collapse
AntoXik72 said:
Welcome to this unbrick tutorial​


This tutorial is EEA only at the moment

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 you are on 1.1.4 but since your phone is already out of usage, you can try on your own.

In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.

You are missing some of the phone partitions? This might solve your issue.

Let's begin!

MATERIAL REQUIRED :
Latest platform tools correctly installed Link
Unlocked bootloader both classic and critical unlock Link
Sh4ttered Tool (the 1.1.3 update!! for now as I don't have a super partition backup for both 1.1.4 or 1.1.3 Global) Link
1.1.3 super partition (EEA Only at the moment, feel free to share a Global one in the comments) Link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
Drivers of Nothing Phone installed


STEP 1 : Prepare everything

Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :


If a line appears, your phone is correctly connected.

Type the command :


If it flashed correctly, you should see something like this :


Once that step is done, your phone has now working super partitions.


STEP 2 : Flash stock firmware

After flashing super.img, you have to flash all the left partitions. For that, Run the Download.ps1 with powershell and download the 1.1.3 EEA made by Sh4ttered and downloaded earlier.

Once the Firmware is downloaded, you should see a new fw.zip

Run the flash_all.bat script, it should flash all the partitions without issues.

If something went wrong, tell me in the comment section.

Then, your device should reboot.



STEP 3 : Check your slots

If your device is still not booting, simply change the slot you're on with the following commands :



You should reboot into fastbootd.

Then use :


Look for the line where it says current-slot and it will tell you if it's A slot or B slot

Once you know on wich slot you are, try booting on the other one by running this last command :


If you're on a slot, or :



If you're on b slot.


Reboot your phone after that, and you should boot normally.



If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes

Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
very good man, I'm busy rn so it's sooo good that you wrote this for everyone, thanks!
 
  • Like
Reactions: Pho3nX, ashokram343 and AntoXik72
pankspoo

pankspoo

Senior Member
Jun 27, 2013
1,870
985
in front of ENCHILADA
AntoXik72 said:
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 you are on 1.1.4 but since your phone is already out of usage, you can try on your own.

In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.

You are missing some of the phone partitions? This might solve your issue.

Let's begin!

MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed


STEP 1 : Prepare everything

Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :


If a line appears, your phone is correctly connected.

Type the command :


If it flashed correctly, you should see something like this :


Once that step is done, your phone has now working super partitions.


STEP 2 : Flash stock firmware

After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.

Download the correct region and version of the firmware.

Once the Firmware is downloaded, you should see a new fw.zip

Run the flash_all.bat script, it should flash all the partitions without issues.

If something went wrong, tell me in the comment section.

Then, your device should reboot.



STEP 3 : Check your slots

If your device is still not booting, simply change the slot you're on with the following commands :



You should reboot into fastbootd.

Then use :


Look for the line where it says current-slot and it will tell you if it's A slot or B slot

Once you know on wich slot you are, try booting on the other one by running this last command :


If you're on a slot, or :



If you're on b slot.


Reboot your phone after that, and you should boot normally.



If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes

Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
 
A

AntoXik72

Senior Member
Feb 27, 2013
109
53
pankspoo said:
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
Click to expand...
Click to collapse
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.

For the downgrade, I can't tell, try it at your own risks.
 
pankspoo

pankspoo

Senior Member
Jun 27, 2013
1,870
985
in front of ENCHILADA
AntoXik72 said:
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.

For the downgrade, I can't tell, try it at your own risks.
Click to expand...
Click to collapse
Actullly the term you use must be revive phone from bootloop like that.
Any way thanks👍
 
Last edited:
  • Like
Reactions: AntoXik72
ayed78

ayed78

Senior Member
Sep 25, 2013
812
185
mine still stuck at fastboot...nothing tool not update....it detect lower version update on mine 1.1.4 global
 
Last edited:
You must log in or register to reply here.

Similar threads

Pho3nX
General Nothing Phone (1) [ROM][OTA][Nothing OS] Repo of Nothing OS - Update: 20-01-2023
Replies
503
Views
65K
Er. Aditya
Er. Aditya
herna
Development Paranoid Android Topaz Beta 1 - Nothing phone (1)
Replies
249
Views
28K
I
iesheiden
Pho3nX
How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1) - Update: 16/12/2022
Replies
231
Views
23K
G
Giunta._
A
Question Gcam for Nothing phone 1
Replies
43
Views
20K
L
luiwii
Sib64
  • Sticky
Question [HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly
Replies
266
Views
19K
G
gelu83

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 1
    A
    arinc9
    Decree said:
    If there's a way I can extract a working persist. Img from a ROM and restore it using that partition backup/restore tool, do you think that would work?

    It's just very odd to me that all my mother sensors work except fingerprint
    Click to expand...
    Click to collapse
    The only way I know is some apps that require root to backup partitions. If someone else knows a way to backup partitions without root, let me know.

    Stuff like fingerprint sensor includes information specific to the phone hardware, so installing someone else's persist backup breaks the fingerprint sensor. This is what I understand.
    View
  • 8
    A
    AntoXik72
    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 you are on 1.1.4 but since your phone is already out of usage, you can try on your own.

    In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.

    You are missing some of the phone partitions? This might solve your issue.

    Let's begin!

    MATERIAL REQUIRED :
    Latest platform tools correctly installed Link
    - Unlocked bootloader both classic and critical unlock Link
    - Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
    - Super partition listed in post #2 and corresponding to your device version and region
    - PC with Microsoft Windows 7-8-8.1-10-11
    - USB type C cable
    - Drivers of Nothing Phone installed


    STEP 1 : Prepare everything

    Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
    Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
    Then, connect your phone to the computer and type the command :
    fastboot devices
    Click to expand...
    Click to collapse

    If a line appears, your phone is correctly connected.

    Type the command :
    fastboot flash super super.img
    Click to expand...
    Click to collapse

    If it flashed correctly, you should see something like this :
    C:\Users\Alex\Desktop\platform-tools>fastboot flash super super.img
    Invalid sparse file format at header magic
    Sending sparse 'super' 1/9 (786428 KB) OKAY [ 19.574s]
    Writing 'super' OKAY [ 0.013s]
    Sending sparse 'super' 2/9 (786428 KB) OKAY [ 19.587s]
    Writing 'super' OKAY [ 0.018s]
    Sending sparse 'super' 3/9 (786428 KB) OKAY [ 19.609s]
    Writing 'super' OKAY [ 0.012s]
    Sending sparse 'super' 4/9 (698716 KB) OKAY [ 17.393s]
    Writing 'super' OKAY [ 0.012s]
    Sending sparse 'super' 5/9 (765968 KB) OKAY [ 19.103s]
    Writing 'super' OKAY [ 0.010s]
    Sending sparse 'super' 6/9 (763420 KB) OKAY [ 19.074s]
    Writing 'super' OKAY [ 0.017s]
    Sending sparse 'super' 7/9 (786097 KB) OKAY [ 19.636s]
    Writing 'super' OKAY [ 0.009s]
    Sending sparse 'super' 8/9 (786089 KB) OKAY [ 19.745s]
    Writing 'super' OKAY [ 0.029s]
    Sending sparse 'super' 9/9 (102406 KB) OKAY [ 2.853s]
    Writing 'super' OKAY [ 6.798s]
    Finished. Total time: 167.087s
    Click to expand...
    Click to collapse

    Once that step is done, your phone has now working super partitions.


    STEP 2 : Flash stock firmware

    After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.

    Download the correct region and version of the firmware.

    Once the Firmware is downloaded, you should see a new fw.zip

    Run the flash_all.bat script, it should flash all the partitions without issues.

    If something went wrong, tell me in the comment section.

    Then, your device should reboot.



    STEP 3 : Check your slots

    If your device is still not booting, simply change the slot you're on with the following commands :

    fastboot reboot fastboot
    Click to expand...
    Click to collapse

    You should reboot into fastbootd.

    Then use :
    fastboot getvar all
    Click to expand...
    Click to collapse

    Look for the line where it says current-slot and it will tell you if it's A slot or B slot

    Once you know on wich slot you are, try booting on the other one by running this last command :

    fastboot set_active b
    Click to expand...
    Click to collapse
    If you're on a slot, or :


    fastboot set_active a
    Click to expand...
    Click to collapse
    If you're on b slot.


    Reboot your phone after that, and you should boot normally.



    If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
    Sorry for my bad english sometimes

    Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
    View
    3
    sh4tteredd
    sh4tteredd
    AntoXik72 said:
    That's perfect, thanks, i'll update the post tonight
    Click to expand...
    Click to collapse
    AntoXik72 said:
    Welcome to this unbrick tutorial​


    This tutorial is EEA only at the moment

    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 you are on 1.1.4 but since your phone is already out of usage, you can try on your own.

    In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.

    You are missing some of the phone partitions? This might solve your issue.

    Let's begin!

    MATERIAL REQUIRED :
    Latest platform tools correctly installed Link
    Unlocked bootloader both classic and critical unlock Link
    Sh4ttered Tool (the 1.1.3 update!! for now as I don't have a super partition backup for both 1.1.4 or 1.1.3 Global) Link
    1.1.3 super partition (EEA Only at the moment, feel free to share a Global one in the comments) Link
    PC with Microsoft Windows 7-8-8.1-10-11
    USB type C cable
    Drivers of Nothing Phone installed


    STEP 1 : Prepare everything

    Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
    Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
    Then, connect your phone to the computer and type the command :


    If a line appears, your phone is correctly connected.

    Type the command :


    If it flashed correctly, you should see something like this :


    Once that step is done, your phone has now working super partitions.


    STEP 2 : Flash stock firmware

    After flashing super.img, you have to flash all the left partitions. For that, Run the Download.ps1 with powershell and download the 1.1.3 EEA made by Sh4ttered and downloaded earlier.

    Once the Firmware is downloaded, you should see a new fw.zip

    Run the flash_all.bat script, it should flash all the partitions without issues.

    If something went wrong, tell me in the comment section.

    Then, your device should reboot.



    STEP 3 : Check your slots

    If your device is still not booting, simply change the slot you're on with the following commands :



    You should reboot into fastbootd.

    Then use :


    Look for the line where it says current-slot and it will tell you if it's A slot or B slot

    Once you know on wich slot you are, try booting on the other one by running this last command :


    If you're on a slot, or :



    If you're on b slot.


    Reboot your phone after that, and you should boot normally.



    If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
    Sorry for my bad english sometimes

    Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
    Click to expand...
    Click to collapse
    very good man, I'm busy rn so it's sooo good that you wrote this for everyone, thanks!
    View
    2
    ot_inc
    ot_inc

    icetea250 said:
    I wanted to update from v1.1.4 (b slot) to v1.1.6 and was burning v1.1.6 image files to the a slot using fastboot, but maybe I inadvertently forgot to add "***_a" to the command and burned some v1.1.6 image files to the v1.1.4 b slot. When I reboot afterwards, I get a "Push any key to shutdown" message in the upper left corner with the Nothing logo, and I can't get into fastboot or recovery. Is there any way to fix it?(deepl)
    v1.1.4(bスロット)からv1.1.6にアップデートしようと思い、fastbootでaスロットにv1.1.6のイメージファイルを焼いていたのですが、多分私の不注意でコマンドに"○○_a"をつけ忘れて何個かのv1.1.6のイメージファイルをv1.1.4のbスロットに焼いてしまい、その後リブートするとNothingのロゴと共に左上端に「Push any key to shutdown」と出て、fastbootにもrecoveryにも入れず完全に詰んでいる状況です、ここまで来ると、サポートに送るしか直す手段は無いでしょうか？
    Click to expand...
    Click to collapse
    try it

    YouTube
    link(Japanese)

    【Xiaomi】Fastbootモードで「push any key to shutdown」と出て何もできない問題の修正方法【Redmi】 - ROM焼き試験場

    Rom焼きしようとFastbootモードでPCと接続した際、黒画面で左上に Push any...
    mitanyan98.hatenablog.com mitanyan98.hatenablog.com
    View
    2
    X
    xtcislove
    Awesome thank you. The super.img is the key to unbrick our NP1. This is the key to more modding.
    View
    2
    P6P
    P6P
    arinc9 said:
    What's the name of the app?
    Click to expand...
    Click to collapse

    Partitions Backup & Restore - Apps on Google Play

    Backup your important partitions to avoid any...
    play.google.com play.google.com

    This one for example.
    View

New posts