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

Search This thread

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
normally thru the settings (just like a normal OTA, no adb or strange stuff). After that lock it
Ok for some reason during the setup rebooted and now its stuck again in the bootloader.
using your tool doesn't fix the problem.

Here is the log

nothing phone(1) fastboot flash by @sh4tteredd

DON'T flash a nothingOS version lower than that one that's currently installed on the phone!

In order to gather all the files that we need, consider to run my other script available on https://github.com/sh4tteredd/nothing-phone-1-tools

Instead, if you already have the .img files, put all your files in a subfolder called 'images' to continue

product: lahaina
product: lahaina
Erasing 'userdata' OKAY [ 0.027s]

F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 224472728 (109605 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
""
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 1cc00 0 200 at offset 0x00117760
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d201, 0001d202
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117761
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d203, 0001d204
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117762
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d205, 0001d206
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117763
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0001d200
Info: Overprovision ratio = 0.610%
Info: Overprovision segments = 665 (GC reserved = 335)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (97 KB) OKAY [ 0.004s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 4.162s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.004s]
Finished. Total time: 5.036s
Setting current slot to 'a' OKAY [ 0.030s]
Finished. Total time: 0.034s
Flashing A slot. Please wait...
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 18.346s
Sending 'abl_a' (148 KB) OKAY [ 0.004s]
Writing 'abl_a' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'aop_a' (204 KB) OKAY [ 0.005s]
Writing 'aop_a' OKAY [ 0.007s]
Finished. Total time: 0.023s
Sending 'bluetooth_a' (476 KB) OKAY [ 0.011s]
Writing 'bluetooth_a' OKAY [ 0.009s]
Finished. Total time: 0.030s
Sending 'boot_a' (98304 KB) OKAY [ 2.195s]
Writing 'boot_a' OKAY [ 1.367s]
Finished. Total time: 3.573s
Sending 'cpucp_a' (184 KB) OKAY [ 0.004s]
Writing 'cpucp_a' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'devcfg_a' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'dsp_a' (65536 KB) OKAY [ 1.462s]
Writing 'dsp_a' OKAY [ 0.301s]
Finished. Total time: 1.772s
Sending 'dtbo_a' (24576 KB) OKAY [ 0.557s]
Writing 'dtbo_a' OKAY [ 0.136s]
Finished. Total time: 0.703s
Sending 'featenabler_a' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'hyp_a' (3592 KB) OKAY [ 0.082s]
Writing 'hyp_a' OKAY [ 0.028s]
Finished. Total time: 0.120s
Sending 'imagefv_a' (524 KB) OKAY [ 0.015s]
Writing 'imagefv_a' OKAY [ 0.008s]
Finished. Total time: 0.034s
Sending 'keymaster_a' (264 KB) OKAY [ 0.007s]
Writing 'keymaster_a' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'modem_a' (173676 KB) OKAY [ 3.901s]
Writing 'modem_a' OKAY [ 0.405s]
Finished. Total time: 4.317s
Sending 'multiimgoem_a' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_a' OKAY [ 0.004s]
Finished. Total time: 0.017s
Sending 'odm_a' (1052 KB) OKAY [ 0.025s]
Writing 'odm_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product_a' 1/8 (262108 KB) OKAY [ 5.914s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_a' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_a' OKAY [ 0.033s]
Finished. Total time: 0.046s
Sending 'shrm_a' (48 KB) OKAY [ 0.002s]
Writing 'shrm_a' OKAY [ 0.006s]
Finished. Total time: 0.017s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/6 (262104 KB) OKAY [ 5.880s]
Writing 'system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system_ext_a' 1/2 (262116 KB) OKAY [ 5.931s]
Writing 'system_ext_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_a' (3636 KB) OKAY [ 0.081s]
Writing 'tz_a' OKAY [ 0.051s]
Finished. Total time: 0.142s
Sending 'uefisecapp_a' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_a' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.005s]
Finished. Total time: 0.013s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.014s
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/5 (262104 KB) OKAY [ 5.972s]
Writing 'vendor_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.182s]
Writing 'vendor_boot_a' OKAY [ 0.265s]
Finished. Total time: 2.458s
Sending 'xbl_a' (3600 KB) OKAY [ 0.082s]
Writing 'xbl_a' OKAY [ 0.030s]
Finished. Total time: 0.121s
Sending 'xbl_config_a' (224 KB) OKAY [ 0.006s]
Writing 'xbl_config_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
< waiting for any device >
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.043s
Flashing B slot. Please wait...
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 18.494s
Sending 'abl_b' (148 KB) OKAY [ 0.004s]
Writing 'abl_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
Sending 'aop_b' (204 KB) OKAY [ 0.005s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.023s
Sending 'bluetooth_b' (476 KB) OKAY [ 0.011s]
Writing 'bluetooth_b' OKAY [ 0.009s]
Finished. Total time: 0.030s
Sending 'boot_b' (98304 KB) OKAY [ 2.215s]
Writing 'boot_b' OKAY [ 1.264s]
Finished. Total time: 3.490s
Sending 'cpucp_b' (184 KB) OKAY [ 0.005s]
Writing 'cpucp_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'dsp_b' (65536 KB) OKAY [ 1.485s]
Writing 'dsp_b' OKAY [ 0.304s]
Finished. Total time: 1.799s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.559s]
Writing 'dtbo_b' OKAY [ 0.138s]
Finished. Total time: 0.707s
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending 'hyp_b' (3592 KB) OKAY [ 0.081s]
Writing 'hyp_b' OKAY [ 0.028s]
Finished. Total time: 0.118s
Sending 'imagefv_b' (524 KB) OKAY [ 0.015s]
Writing 'imagefv_b' OKAY [ 0.009s]
Finished. Total time: 0.034s
Sending 'keymaster_b' (264 KB) OKAY [ 0.007s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'modem_b' (173676 KB) OKAY [ 3.921s]
Writing 'modem_b' OKAY [ 0.410s]
Finished. Total time: 4.341s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Resizing 'odm_b' OKAY [ 0.012s]
Sending 'odm_b' (1052 KB) OKAY [ 0.025s]
Writing 'odm_b' OKAY [ 1.088s]
Finished. Total time: 1.137s
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.004s]
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 5.937s]
Writing 'product_b' OKAY [ 1.589s]
Sending sparse 'product_b' 2/8 (262124 KB) OKAY [ 5.924s]
Writing 'product_b' OKAY [ 0.579s]
Sending sparse 'product_b' 3/8 (262128 KB) OKAY [ 5.921s]
Writing 'product_b' OKAY [ 0.587s]
Sending sparse 'product_b' 4/8 (262120 KB) OKAY [ 5.917s]
Writing 'product_b' OKAY [ 0.527s]
Sending sparse 'product_b' 5/8 (262116 KB) OKAY [ 5.915s]
Writing 'product_b' OKAY [ 0.578s]
Sending sparse 'product_b' 6/8 (262128 KB) OKAY [ 5.922s]
Writing 'product_b' OKAY [ 0.567s]
Sending sparse 'product_b' 7/8 (262132 KB) OKAY [ 5.921s]
Writing 'product_b' OKAY [ 0.574s]
Sending sparse 'product_b' 8/8 (163680 KB) OKAY [ 3.710s]
Writing 'product_b' OKAY [ 0.391s]
Finished. Total time: 52.123s
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.003s]
Finished. Total time: 0.012s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Invalid sparse file format at header magic
Resizing 'system_b' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.005s]
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 5.945s]
Writing 'system_ext_b' OKAY [ 1.595s]
Sending sparse 'system_ext_b' 2/2 (221164 KB) OKAY [ 5.027s]
Writing 'system_ext_b' OKAY [ 0.480s]
Finished. Total time: 13.448s
Sending 'tz_b' (3636 KB) OKAY [ 0.082s]
Writing 'tz_b' OKAY [ 0.029s]
Finished. Total time: 0.121s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.004s]
Finished. Total time: 0.013s
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.005s]
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 5.961s]
Writing 'vendor_b' OKAY [ 1.635s]
Sending sparse 'vendor_b' 2/5 (262100 KB) OKAY [ 5.932s]
Writing 'vendor_b' OKAY [ 0.564s]
Sending sparse 'vendor_b' 3/5 (262120 KB) OKAY [ 5.936s]
Writing 'vendor_b' OKAY [ 0.555s]
Sending sparse 'vendor_b' 4/5 (262132 KB) OKAY [ 5.922s]
Writing 'vendor_b' OKAY [ 0.561s]
Sending sparse 'vendor_b' 5/5 (148864 KB) OKAY [ 3.365s]
Writing 'vendor_b' OKAY [ 0.431s]
Finished. Total time: 31.863s
Sending 'vendor_boot_b' (98304 KB) OKAY [ 2.212s]
Writing 'vendor_boot_b' OKAY [ 0.255s]
Finished. Total time: 2.477s
Sending 'xbl_b' (3600 KB) OKAY [ 0.084s]
Writing 'xbl_b' OKAY [ 0.034s]
Finished. Total time: 0.126s
Sending 'xbl_config_b' (224 KB) OKAY [ 0.006s]
Writing 'xbl_config_b' OKAY [ 0.009s]
Finished. Total time: 0.025s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
"Your phone(1) is rebooting"
Presione una tecla para continuar . . .
 

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy
Ok for some reason during the setup rebooted and now its stuck again in the bootloader.
using your tool doesn't fix the problem.

Here is the log

nothing phone(1) fastboot flash by @sh4tteredd

DON'T flash a nothingOS version lower than that one that's currently installed on the phone!

In order to gather all the files that we need, consider to run my other script available on https://github.com/sh4tteredd/nothing-phone-1-tools

Instead, if you already have the .img files, put all your files in a subfolder called 'images' to continue

product: lahaina
product: lahaina
Erasing 'userdata' OKAY [ 0.027s]

F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 224472728 (109605 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
Info: add quota type = 2 => 6
Info: format version with
""
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 1cc00 0 200 at offset 0x00117760
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d201, 0001d202
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117761
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d203, 0001d204
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117762
[f2fs_write_default_quota:1350] Writing quota data, at offset 0001d205, 0001d206
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 1cc00 0 200 at offset 0x00117763
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0001d200
Info: Overprovision ratio = 0.610%
Info: Overprovision segments = 665 (GC reserved = 335)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (97 KB) OKAY [ 0.004s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 4.162s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes

Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done

Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.004s]
Finished. Total time: 5.036s
Setting current slot to 'a' OKAY [ 0.030s]
Finished. Total time: 0.034s
Flashing A slot. Please wait...
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 18.346s
Sending 'abl_a' (148 KB) OKAY [ 0.004s]
Writing 'abl_a' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'aop_a' (204 KB) OKAY [ 0.005s]
Writing 'aop_a' OKAY [ 0.007s]
Finished. Total time: 0.023s
Sending 'bluetooth_a' (476 KB) OKAY [ 0.011s]
Writing 'bluetooth_a' OKAY [ 0.009s]
Finished. Total time: 0.030s
Sending 'boot_a' (98304 KB) OKAY [ 2.195s]
Writing 'boot_a' OKAY [ 1.367s]
Finished. Total time: 3.573s
Sending 'cpucp_a' (184 KB) OKAY [ 0.004s]
Writing 'cpucp_a' OKAY [ 0.006s]
Finished. Total time: 0.021s
Sending 'devcfg_a' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_a' OKAY [ 0.004s]
Finished. Total time: 0.014s
Sending 'dsp_a' (65536 KB) OKAY [ 1.462s]
Writing 'dsp_a' OKAY [ 0.301s]
Finished. Total time: 1.772s
Sending 'dtbo_a' (24576 KB) OKAY [ 0.557s]
Writing 'dtbo_a' OKAY [ 0.136s]
Finished. Total time: 0.703s
Sending 'featenabler_a' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_a' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'hyp_a' (3592 KB) OKAY [ 0.082s]
Writing 'hyp_a' OKAY [ 0.028s]
Finished. Total time: 0.120s
Sending 'imagefv_a' (524 KB) OKAY [ 0.015s]
Writing 'imagefv_a' OKAY [ 0.008s]
Finished. Total time: 0.034s
Sending 'keymaster_a' (264 KB) OKAY [ 0.007s]
Writing 'keymaster_a' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'modem_a' (173676 KB) OKAY [ 3.901s]
Writing 'modem_a' OKAY [ 0.405s]
Finished. Total time: 4.317s
Sending 'multiimgoem_a' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_a' OKAY [ 0.004s]
Finished. Total time: 0.017s
Sending 'odm_a' (1052 KB) OKAY [ 0.025s]
Writing 'odm_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'product_a' 1/8 (262108 KB) OKAY [ 5.914s]
Writing 'product_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_a' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_a' OKAY [ 0.033s]
Finished. Total time: 0.046s
Sending 'shrm_a' (48 KB) OKAY [ 0.002s]
Writing 'shrm_a' OKAY [ 0.006s]
Finished. Total time: 0.017s
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/6 (262104 KB) OKAY [ 5.880s]
Writing 'system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system_ext_a' 1/2 (262116 KB) OKAY [ 5.931s]
Writing 'system_ext_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_a' (3636 KB) OKAY [ 0.081s]
Writing 'tz_a' OKAY [ 0.051s]
Finished. Total time: 0.142s
Sending 'uefisecapp_a' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_a' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_a' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.005s]
Finished. Total time: 0.013s
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_a' OKAY [ 0.004s]
Finished. Total time: 0.014s
Invalid sparse file format at header magic
Sending sparse 'vendor_a' 1/5 (262104 KB) OKAY [ 5.972s]
Writing 'vendor_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.182s]
Writing 'vendor_boot_a' OKAY [ 0.265s]
Finished. Total time: 2.458s
Sending 'xbl_a' (3600 KB) OKAY [ 0.082s]
Writing 'xbl_a' OKAY [ 0.030s]
Finished. Total time: 0.121s
Sending 'xbl_config_a' (224 KB) OKAY [ 0.006s]
Writing 'xbl_config_a' OKAY [ 0.016s]
Finished. Total time: 0.031s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
< waiting for any device >
Setting current slot to 'b' OKAY [ 0.039s]
Finished. Total time: 0.043s
Flashing B slot. Please wait...
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 18.494s
Sending 'abl_b' (148 KB) OKAY [ 0.004s]
Writing 'abl_b' OKAY [ 0.006s]
Finished. Total time: 0.018s
Sending 'aop_b' (204 KB) OKAY [ 0.005s]
Writing 'aop_b' OKAY [ 0.007s]
Finished. Total time: 0.023s
Sending 'bluetooth_b' (476 KB) OKAY [ 0.011s]
Writing 'bluetooth_b' OKAY [ 0.009s]
Finished. Total time: 0.030s
Sending 'boot_b' (98304 KB) OKAY [ 2.215s]
Writing 'boot_b' OKAY [ 1.264s]
Finished. Total time: 3.490s
Sending 'cpucp_b' (184 KB) OKAY [ 0.005s]
Writing 'cpucp_b' OKAY [ 0.007s]
Finished. Total time: 0.020s
Sending 'devcfg_b' (52 KB) OKAY [ 0.002s]
Writing 'devcfg_b' OKAY [ 0.005s]
Finished. Total time: 0.018s
Sending 'dsp_b' (65536 KB) OKAY [ 1.485s]
Writing 'dsp_b' OKAY [ 0.304s]
Finished. Total time: 1.799s
Sending 'dtbo_b' (24576 KB) OKAY [ 0.559s]
Writing 'dtbo_b' OKAY [ 0.138s]
Finished. Total time: 0.707s
Sending 'featenabler_b' (88 KB) OKAY [ 0.003s]
Writing 'featenabler_b' OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending 'hyp_b' (3592 KB) OKAY [ 0.081s]
Writing 'hyp_b' OKAY [ 0.028s]
Finished. Total time: 0.118s
Sending 'imagefv_b' (524 KB) OKAY [ 0.015s]
Writing 'imagefv_b' OKAY [ 0.009s]
Finished. Total time: 0.034s
Sending 'keymaster_b' (264 KB) OKAY [ 0.007s]
Writing 'keymaster_b' OKAY [ 0.007s]
Finished. Total time: 0.024s
Sending 'modem_b' (173676 KB) OKAY [ 3.921s]
Writing 'modem_b' OKAY [ 0.410s]
Finished. Total time: 4.341s
Sending 'multiimgoem_b' (16 KB) OKAY [ 0.001s]
Writing 'multiimgoem_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Resizing 'odm_b' OKAY [ 0.012s]
Sending 'odm_b' (1052 KB) OKAY [ 0.025s]
Writing 'odm_b' OKAY [ 1.088s]
Finished. Total time: 1.137s
Invalid sparse file format at header magic
Resizing 'product_b' OKAY [ 0.004s]
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 5.937s]
Writing 'product_b' OKAY [ 1.589s]
Sending sparse 'product_b' 2/8 (262124 KB) OKAY [ 5.924s]
Writing 'product_b' OKAY [ 0.579s]
Sending sparse 'product_b' 3/8 (262128 KB) OKAY [ 5.921s]
Writing 'product_b' OKAY [ 0.587s]
Sending sparse 'product_b' 4/8 (262120 KB) OKAY [ 5.917s]
Writing 'product_b' OKAY [ 0.527s]
Sending sparse 'product_b' 5/8 (262116 KB) OKAY [ 5.915s]
Writing 'product_b' OKAY [ 0.578s]
Sending sparse 'product_b' 6/8 (262128 KB) OKAY [ 5.922s]
Writing 'product_b' OKAY [ 0.567s]
Sending sparse 'product_b' 7/8 (262132 KB) OKAY [ 5.921s]
Writing 'product_b' OKAY [ 0.574s]
Sending sparse 'product_b' 8/8 (163680 KB) OKAY [ 3.710s]
Writing 'product_b' OKAY [ 0.391s]
Finished. Total time: 52.123s
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.003s]
Finished. Total time: 0.012s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Invalid sparse file format at header magic
Resizing 'system_b' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Invalid sparse file format at header magic
Resizing 'system_ext_b' OKAY [ 0.005s]
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 5.945s]
Writing 'system_ext_b' OKAY [ 1.595s]
Sending sparse 'system_ext_b' 2/2 (221164 KB) OKAY [ 5.027s]
Writing 'system_ext_b' OKAY [ 0.480s]
Finished. Total time: 13.448s
Sending 'tz_b' (3636 KB) OKAY [ 0.082s]
Writing 'tz_b' OKAY [ 0.029s]
Finished. Total time: 0.121s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.020s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta_b' OKAY [ 0.005s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.004s]
Finished. Total time: 0.013s
Invalid sparse file format at header magic
Resizing 'vendor_b' OKAY [ 0.005s]
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 5.961s]
Writing 'vendor_b' OKAY [ 1.635s]
Sending sparse 'vendor_b' 2/5 (262100 KB) OKAY [ 5.932s]
Writing 'vendor_b' OKAY [ 0.564s]
Sending sparse 'vendor_b' 3/5 (262120 KB) OKAY [ 5.936s]
Writing 'vendor_b' OKAY [ 0.555s]
Sending sparse 'vendor_b' 4/5 (262132 KB) OKAY [ 5.922s]
Writing 'vendor_b' OKAY [ 0.561s]
Sending sparse 'vendor_b' 5/5 (148864 KB) OKAY [ 3.365s]
Writing 'vendor_b' OKAY [ 0.431s]
Finished. Total time: 31.863s
Sending 'vendor_boot_b' (98304 KB) OKAY [ 2.212s]
Writing 'vendor_boot_b' OKAY [ 0.255s]
Finished. Total time: 2.477s
Sending 'xbl_b' (3600 KB) OKAY [ 0.084s]
Writing 'xbl_b' OKAY [ 0.034s]
Finished. Total time: 0.126s
Sending 'xbl_config_b' (224 KB) OKAY [ 0.006s]
Writing 'xbl_config_b' OKAY [ 0.009s]
Finished. Total time: 0.025s
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
"Your phone(1) is rebooting"
Presione una tecla para continuar . . .
try to boot into recovery (after the "no command" screen you have to press power button + volume up) and then wipe from there. If it doesn't work re-flash with the script and repeat the wipe from recovery. Let me know
 

Gerard03

Senior Member
Jul 23, 2016
56
1
Nothing Phone 1
try to boot into recovery (after the "no command" screen you have to press power button + volume up) and then wipe from there. If it doesn't work re-flash with the script and repeat the wipe from recovery. Let me know
It didnt work when i wipe It says:
e:Open failed: /metadta/ota: No such file or directory
formatting /data
formating /metadata
wipe complete.
 

AntoXik72

Senior Member
Feb 27, 2013
100
50
It didnt work when i wipe It says:
e:Open failed: /metadta/ota: No such file or directory
formatting /data
formating /metadata
wipe complete.
Flash the super partition in Help to developers subforum before, look out for the slot you are, then use the script again, it should work again, then change to the slot where you flashed super partition and put it back as main for bootup, you should boot again
 
  • Like
Reactions: Sib64

yquitumadbro

Senior Member
Sep 17, 2020
50
10
So I am stuck on this prompt . Any ideas?
1661471071893.png
 
Last edited:

sh4tteredd

Senior Member
Aug 9, 2022
79
60
Italy

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.