How To Guide [GUIDE][HowTo] Unlock and root Phone(1) - Update: 04/08/2022

Search This thread

EXCIDIVM

Member
Aug 18, 2022
14
3
ahhh didn't get it, I suggest you to wait the next official OTA, do it (normally, thru the settings) , and after the update try to lock it

You really know your stuff. That did the trick!
Your solution updated me to 1.12, so I OTA updated to 1.13 right away. Afterwards I was able to relock my bootloader.

Happy end.
 

aleqa

Member
Nov 15, 2014
21
6
OnePlus 6
Nothing Phone 1
Hello, i am on 1.1.2 rooted.
To install the new update, what i need to do?
Flash stock boot image from 1.1.2.
Do i need to uninstall magisk? (click the button that is present on the app?)
Update
Download and patch the boot image 1.1.3
Flash the patched 1.1.3 boot image
Done?
Thanks
 

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
Hey everyone,

It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
So don't deprive yourself and here is the process of the two operations.

You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.



How to bootloader unlock and root the Nothing Phone 1

After unlocking the bootloader, you can use Magisk to root the device.
You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:


Step 1: Unlock the Nothing Phone 1’s bootloader

  1. Open the Settings app on your Nothing Phone 1.
  2. Tap on About phone.
  3. Locate the section named Software info and tap on it.
  4. On the next screen, tap on the Build number 7 times until it says you’re now a developer.
  5. Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
  6. You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
  7. Scroll down a bit until you see USB debugging. Enable it as well.
  8. Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.02) binaries installed.
  9. Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
  10. If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
    • If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
  11. Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
  12. Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
    • In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
  13. You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
  14. The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
  15. Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
  16. Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
  17. You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.

Step 2 - Rooting your Nothing Phone 1 with Magisk

With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
  1. Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
  2. Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
    • At the time of writing this tutorial, the latest available software for the Nothing Phone 1 is Global Full Nothing OS 1.1.2 ZIP for this build can be downloaded from here.
  3. Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
    • In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
  4. Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
  5. Download and install the Magisk app on the Nothing Phone 1.
  6. Open the Magisk app and tap on the Install button.
  7. Choose Select and Patch a File. A file manager will pop up.
  8. Select the boot image that you pushed earlier and let Magisk patch it.
  9. Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
  10. Reboot the Phone 1 into the bootloader: adb reboot bootloader
  11. Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
  12. Reboot the phone: fastboot reboot
  13. Open the Magisk app and your Nothing Phone 1 should be rooted.

Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.


-=o#0#o=-​


WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.

menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot


Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1

#root #nothingphone
I unlocked the bootloader and now i dont want it anymore I locked it but now is stuck in fastboot mode so i unlocked again and used the guide that is posted about how to unbrick nothing phone but still going on fastboot mode
 

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
I unlocked the bootloader and now i dont want it anymore I locked it but now is stuck in fastboot mode so i unlocked again and used the guide that is posted about how to unbrick nothing phone but still going on fastboot mode
try to use my tool!

 
  • Like
Reactions: Gerard03

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
try to use my tool!

I seen it gives error when typing fastboot -w

Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.016s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 0.021s
 
Last edited:

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
I seen it gives error when typing fastboot flash -w

Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.016s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 0.021s
it should continue even if fastboot -w gives error, can you please paste the whole output?
 

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
it should continue even if fastboot -w gives error, can you please paste the whole output?
Here it is.


C:\Users\gerar\Downloads\payload-dumper-go_1.0.0_windows_amd64\extracted_20220824_220838>fastboot -w
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.016s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 0.021s

C:\Users\gerar\Downloads\payload-dumper-go_1.0.0_windows_amd64\extracted_20220824_220838>
 

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
ah sorry, I didn't explain correctly. I mean my script should gives out the whole output with some specific errors, can you please run it another time?
 

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
ah sorry, I didn't explain correctly. I mean my script should gives out the whole output with some specific errors, can you please run it another time?
oh yes sorry

product: lahaina
product: lahaina
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.013s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 0.019s
fastboot: unknown option -- set-active=a
Flashing A slot. Please wait...
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
target reported max download size of 805306368 bytes
sending 'abl_a' (148 KB)...
OKAY [ 0.006s]
writing 'abl_a'...
OKAY [ 0.004s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'aop_a' (204 KB)...
OKAY [ 0.006s]
writing 'aop_a'...
OKAY [ 0.004s]
finished. total time: 0.013s
target reported max download size of 805306368 bytes
sending 'bluetooth_a' (476 KB)...
OKAY [ 0.013s]
writing 'bluetooth_a'...
OKAY [ 0.006s]
finished. total time: 0.022s
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.088s]
writing 'boot_a'...
OKAY [ 0.260s]
finished. total time: 2.348s
target reported max download size of 805306368 bytes
sending 'cpucp_a' (184 KB)...
OKAY [ 0.007s]
writing 'cpucp_a'...
OKAY [ 0.004s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'devcfg_a' (52 KB)...
OKAY [ 0.004s]
writing 'devcfg_a'...
OKAY [ 0.004s]
finished. total time: 0.009s
target reported max download size of 805306368 bytes
sending 'dsp_a' (65536 KB)...
OKAY [ 1.402s]
writing 'dsp_a'...
OKAY [ 0.218s]
finished. total time: 1.622s
target reported max download size of 805306368 bytes
sending 'dtbo_a' (24576 KB)...
OKAY [ 0.531s]
writing 'dtbo_a'...
OKAY [ 0.051s]
finished. total time: 0.584s
target reported max download size of 805306368 bytes
sending 'featenabler_a' (88 KB)...
OKAY [ 0.005s]
writing 'featenabler_a'...
OKAY [ 0.004s]
finished. total time: 0.010s
target reported max download size of 805306368 bytes
sending 'hyp_a' (3592 KB)...
OKAY [ 0.080s]
writing 'hyp_a'...
OKAY [ 0.011s]
finished. total time: 0.094s
target reported max download size of 805306368 bytes
sending 'imagefv_a' (524 KB)...
OKAY [ 0.015s]
writing 'imagefv_a'...
OKAY [ 0.004s]
finished. total time: 0.023s
target reported max download size of 805306368 bytes
sending 'keymaster_a' (264 KB)...
OKAY [ 0.009s]
writing 'keymaster_a'...
OKAY [ 0.006s]
finished. total time: 0.017s
target reported max download size of 805306368 bytes
sending 'modem_a' (173676 KB)...
OKAY [ 3.757s]
writing 'modem_a'...
OKAY [ 0.581s]
finished. total time: 4.342s
target reported max download size of 805306368 bytes
sending 'multiimgoem_a' (16 KB)...
OKAY [ 0.003s]
writing 'multiimgoem_a'...
OKAY [ 0.003s]
finished. total time: 0.008s
target reported max download size of 805306368 bytes
sending 'odm_a' (1052 KB)...
OKAY [ 0.026s]
writing 'odm_a'...
FAILED (remote: (odm_a_b) No such partition)
finished. total time: 0.033s
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
target reported max download size of 805306368 bytes
sending 'qupfw_a' (56 KB)...
OKAY [ 0.004s]
writing 'qupfw_a'...
OKAY [ 0.012s]
finished. total time: 0.018s
target reported max download size of 805306368 bytes
sending 'shrm_a' (48 KB)...
OKAY [ 0.003s]
writing 'shrm_a'...
OKAY [ 0.009s]
finished. total time: 0.015s
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
target reported max download size of 805306368 bytes
sending 'system_ext_a' (484932 KB)...
OKAY [ 10.385s]
writing 'system_ext_a'...
FAILED (remote: (system_ext_a_b) No such partition)
finished. total time: 10.391s
target reported max download size of 805306368 bytes
sending 'tz_a' (3636 KB)...
OKAY [ 0.081s]
writing 'tz_a'...
OKAY [ 0.014s]
finished. total time: 0.096s
target reported max download size of 805306368 bytes
sending 'uefisecapp_a' (124 KB)...
OKAY [ 0.005s]
writing 'uefisecapp_a'...
OKAY [ 0.004s]
finished. total time: 0.012s
target reported max download size of 805306368 bytes
sending 'vbmeta_a' (8 KB)...
OKAY [ 0.003s]
writing 'vbmeta_a'...
OKAY [ 0.003s]
finished. total time: 0.008s
target reported max download size of 805306368 bytes
sending 'vbmeta_system_a' (4 KB)...
OKAY [ 0.003s]
writing 'vbmeta_system_a'...
OKAY [ 0.004s]
finished. total time: 0.007s
target reported max download size of 805306368 bytes
Invalid sparse file format at header magi
sending sparse 'vendor_a' (771966 KB)...
OKAY [ 17.273s]
writing 'vendor_a'...
FAILED (remote: Partition not found)
finished. total time: 17.282s
target reported max download size of 805306368 bytes
sending 'vendor_boot_a' (98304 KB)...
OKAY [ 2.113s]
writing 'vendor_boot_a'...
OKAY [ 0.337s]
finished. total time: 2.452s
target reported max download size of 805306368 bytes
sending 'xbl_a' (3600 KB)...
OKAY [ 0.081s]
writing 'xbl_a'...
OKAY [ 0.009s]
finished. total time: 0.092s
target reported max download size of 805306368 bytes
sending 'xbl_config_a' (224 KB)...
OKAY [ 0.008s]
writing 'xbl_config_a'...
OKAY [ 0.005s]
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
fastboot: unknown option -- set-active=b
Flashing B slot. Please wait...
< waiting for device >
usage: fastboot
 
Last edited:

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
you can actually recover your phone but you have to update your adb and fastboot of your PC. I suggest you to delete all the adb and fastboot binaries that you have installed and the download the latest platform tools from google and paste the whole content into C:\Windows\System32
 

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
you can actually recover your phone but you have to update your adb and fastboot of your PC. I suggest you to delete all the adb and fastboot binaries that you have installed and the download the latest platform tools from google and paste the whole content into C:\Windows\System32
Thanks, thanks, and more thanks. now it's working. Do you have Binance? I want to send you some USDT for your help. also now the bootloader is unlocked can I lock it just by typing fastboot flashing lock?
 

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
Thanks, thanks, and more thanks. now it's working. Do you have Binance? I want to send you some USDT for your help. also now the bootloader is unlocked can I lock it just by typing fastboot flashing lock?
to relock the bootloader I suggest you to wait until the next OTA come out, update normally and after that relock it because if you try to lock now you'll probably get errors.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Moderator Announcement

    Ownership of this thread has been transferred from @Sib64 to @Pho3nX
    Regards
    Oswald Boelcke
    Senior Moderator
    1
    thank you for this answer, the phone currently under 1.1.6 never had root access, I have to use the files for version 1.1.4 then?

    No you must extract boot.img from the Payload.bin file (included in the full firmware 1.1.6) with payload_dumper_go_1.0



    Links for tutorial and also the original 1.1.6 EEA if you want ;)
    Just patch it
  • 14
    Hey everyone,

    It's been a few days since the Phone(1) went on sale. And already, Nothing is doing things right by making the Phone(1) Kernel available. The next step was to unlock the bootloader and root it. Both are already available and ready to use.
    So don't deprive yourself and here is the process of the two operations.

    You've already unlocked the bootloader and rooted a carrierless variant of either a Google Pixel or OnePlus, you should have no problem unlocking your Nothing Phone (1) and installing Magisk. For those of you with a memory lapse, here is a tutorial to guide you through the process.

    - Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -

    How to bootloader unlock and root the Nothing Phone 1

    After unlocking the bootloader, you can use Magisk to root the device.
    You must first unlock the bootloader in order to be able to start third-party software. Here's how to do it:


    Step 1: Unlock the Nothing Phone 1’s bootloader

    1. Open the Settings app on your Nothing Phone 1.
    2. Tap on About phone.
    3. Locate the section named Software info and tap on it.
    4. On the next screen, tap on the Build number 7 times until it says you’re now a developer.
    5. Go back to the main Settings page, tap on System, and near the bottom of the list, you should see Developer options. Tap on it.
    6. You should see an OEM unlocking option. Enable it. For security purposes, it may ask you to input your lock screen PIN/password if you have one set.
    7. Scroll down a bit until you see USB debugging. Enable it as well.
    8. Plug in your Nothing Phone 1 into your PC/Mac/Chromebook. Make sure you have the Latest version of ADB and Fastboot (33.0.02) binaries installed.
    9. Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
    10. If you see your device’s serial number and it says “authorized,” then you’re good to go. If this is your first time setting up ADB for this device, then you may see a prompt on your phone to enable USB Debugging for your PC. Grant it permission.
      • If you’re having trouble getting your Windows PC to recognize your device, try installing the latest Android USB Drivers.
    11. Now, reboot to the bootloader menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
    12. Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing unlock
      • In case you need to flash low-level firmware partitions like the bootloader images, you will have to execute another command afterwards: fastboot flashing unlock_critical
    13. You should now see text on screen warning you about the potential risks of unlocking the bootloader. On the screen next to the power and volume buttons, you should see some text. Press the volume up key until it says “unlock the bootloader.” Once it says this, press the power button.
    14. The phone will unlock the bootloader and reboot back to the bootloader menu. This time, the bootloader will show a red warning icon and “unlocked” text.
    15. Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
    16. Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
    17. You’ll see a warning message that your phone’s bootloader is unlocked on every boot, but don’t worry about that as it doesn’t affect your day-to-day use.

    Step 2 - Rooting your Nothing Phone 1 with Magisk

    With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.
    1. Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
    2. Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
      • Depending of your model, you have Global or EEA (European) firmware availables.
        You can download the latest full OTA firmware package here.
    3. Extract the stock boot image from the OTA package. For more information, take a look the “You have access to the recovery-flashable ZIP file” section our “How to Install Magisk on your Android Phone” tutorial.
      • In case you don’t want to download the whole OTA file, you can separately download the boot image just to the post #2 or from this post. However, to avoid version mismatch and other unforeseen errors, it is always advised to extract the boot image yourself.
    4. Now that we have the stock boot image to patch, push it to your device with this command: adb push <path_to_file> /sdcard/Download
    5. Download and install the Magisk app on the Nothing Phone 1.
    6. Open the Magisk app and tap on the Install button.
    7. Choose Select and Patch a File. A file manager will pop up.
    8. Select the boot image that you pushed earlier and let Magisk patch it.
    9. Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
    10. Reboot the Phone 1 into the bootloader: adb reboot bootloader
    11. Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
    12. Reboot the phone: fastboot reboot
    13. Open the Magisk app and your Nothing Phone 1 should be rooted.

    Keep in mind that unlocking the bootloader and rooting your Nothing Phone 1 will impact how you take advantage of updates. You'll have to learn to manually load monthly security patch updates. But don't worry, it's easy enough to do.


    -=o#0#o=-​


    WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.

    menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
    [*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
    [*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot


    Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
    And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1

    #root #nothingphone
    4
    Unbricking Nothing phone 1: Flash Stock Firmware with Fastboot

    - Disclaimer: I don't take any responsibility for anything you do to your tablet, which is to transform it into brick, break, or transform it into coffee machine -


    Warning : The process below will erase all the data on your device. So, I invite you to make a full backup of the device beforehand.
    Unfortunately, as I don't own the Phone(1) yet, I am unable to take screenshots with the Phone(1) at the moment. As soon as I can, I will put them online to finalize the tutorial. Thank you for your understanding


    STEP 1: What you need and read before the process.
    It’s really important for a process without problems
    1. Install Android SDK and the Platform-tools folder
    2. Download the Nothing OS version you need (see this post)
    3. Extract the "payload bin" file from the rom
    4. Extract the Firmware Stock "boot.img" from the rom (see this tutorial)
    5. Unlock the bootloader of your Phone(1) (see this tutorial)

    STEP 2: Boot the bricked phone 1 into Fastboot mode
    Very often, a soft-bricked or boot-looped device may already be in Fastboot mode. However, if you are stuck in a boot-loop, long press the Power key to turn it off.

    Then press and hold the Power and Volume Down keys (or Power and Volume Up keys on some devices) simultaneously to boot your device into Fastboot mode.

    In case you are unable to turn off your device, let the battery discharge. Once it is drained, connect it to the charger. Then, as soon as it is about to start, use the Power and Volume Up/Down keys and it will start directly in Fastboot mode.


    STEP 3: Format the device via Fastboot
    1.Go to the platform-tools folder where the extracted ROM is located.
    2.Then go to its address bar, type CMD in its address, and press Enter. This will launch the CMD window.
    3.Now run the following command to perform a factory reset (optional but recommended) ;)
    Code:
    fastboot -w


    STEP 4: Flash the Nothing Phone 1 firmware via the Fastboot commands
    1. Run the commands below in the CMD window [which is open in the platform-tools folder] to flash the partition file.
    2. Very Important: Only run one command at a time. If you get an error, however, do not exit the process halfway, but go on to the next flashing command instead.
    3. Don't forget to check your command line 🧐 before validating it, because often a small error blocks you!
    Code:
    fastboot flash abl abl.img
    
    fastboot flash aop aop.img
    
    fastboot flash bluetooth bluetooth.img
    
    fastboot flash boot boot.img
    
    fastboot flash cpucp cpucp.img
    
    fastboot flash devcfg devcfg.img
    
    flash fastboot dsp dsp.img
    
    flash fastboot dtbo dtbo.img
    
    fastboot flash featenabler featenabler.img
    
    fastboot flash hyp hyp.img
    
    fastboot flash imagefv imagefv.img
    
    fastboot flash keymaster keymaster.img
    
    fastboot flash modem modem.img
    
    fastboot flash multiimgoem multiimgoem.img
    
    fastboot flash odm odm.img fastboot
    
    fastboot flash product product.img
    
    fastboot flash qupfw qupfw.img
    
    flash fastboot shrm shrm.img
    
    flash fastboot system system.img
    
    flash fastboot system_ext system_ext.img
    
    flash fastboot tz tz.img
    
    flash fastboot uefisecapp uefisecapp.img
    
    flash fastboot vbmeta vbmeta.img
    
    flash fastboot vbmeta_system vbmeta_system.img
    
    fastboot flash vendor vendor.img
    
    fastboot flash vendor_boot vendor_boot.img
    
    flash fastboot xbl xbl.img
    
    fastboot flash xbl_config xbl_config.img


    Step 5: If you have not had any errors, then you can run the command below to boot your device onto the operating system.
    Code:
    fastboot reboot


    Well done 👏, you have just debricked your Nothing Phone 1 by flashing the stock firmware via the fastboot commands. (y)
    I hope this tutorial has helped you find your Phone(1).
    Thanks
    4
    FILES FOR NOTHING OS - (stock-boot, etc. )
    UPDATE 23/08/2022
    In this post you will find the following files:

    Stock_Boot for Nothing OS

    Nothing OS 1.0.2 :
    Stock_boot.img

    Nothing OS 1.1.0

    Global-Stock-boot.img
    European_Stock-boot.img


    Nothing OS 1.1.2

    Global-Stock-boot.img
    European-Stock-boot.img



    Nothing OS 1.1.3
    Global-Stock-boot.img - MD5 = 90718697fce8b1f3fac2fe747366f2d9
    European-Stock-boot.img - MD5 = 6e2fa5661c20e101ce127060ec11d95b
    3
    Moderator Announcement

    Ownership of this thread has been transferred from @Sib64 to @Pho3nX
    Regards
    Oswald Boelcke
    Senior Moderator
    3

    How to bootloader unlock and root the Nothing Phone 1

    Step 1: Unlock the Nothing Phone 1’s bootloader

    Step 2 - Rooting the Nothing Phone 1 with Magisk

    Step 3: Relock the Nothing Phone 1’s bootloader

    Hey Sib64, could you please rephrase the guide correctly. This is because the way it is currently written, users will end up carrying out the third step of re-locking the bootloader right after performing the second step of rooting their device, which in turn will result in a soft-brick or bootloop. So it is advised that rather than having the relocking process as STEP 3, make it an altogether different section.