General Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS

Search This thread
By:
Advanced…
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
Ostry10 said:
EEA and still seen as EEA.

When im trying to update Via adb sideload im getting error:
E: Failed to unmount /mnt/product/nt_log

Maybe because of that i can update?
Click to expand...
Click to collapse
That error is also something that i always had trying to update with sideload.

If you can boot a patched boot img maybe we can find the reason for error 20, but it can be complex, are you in?

It can help a lot of people, using a terminal is required, but it shouldn't be too hard.

Termux or bash from adb debugging will be used.
 
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
Ostry10 said:
Yeas, I can patch boot.img.
Click to expand...
Click to collapse
Ok firstly boot the patched boot img

open a terminal emulator, and send the "su" command to gain root priviledges.

now
Code: 
cd /mnt/product/nt_log/ota_log/

You are now in the log folder for ota updates.
Do
Code: 
ls

To have a list of files in the folder.
The files are multiple tar.gz files for older ota attempt but there should be one folder (one value not ending with tar.gz) with a modern date

Do
Code: 
cd *name of the folder*
to open the folder, ls command should show you the structure of the folder and that there should be an ota.txt file

Now to copy that txt file to the root of the sdcard
Code: 
cp ota.txt /sdcard/

Now on the root of the sdcard of the phone you should have the ota.txt log, send it to me privately through xda messages.
 
  • Like
Reactions: Ostry10
RZ(One)

RZ(One)

Member
Apr 14, 2022
25
22
Could you share how you get to dump boot.img of any update? I'm seriously interested by this
 
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
RZ(One) said:
Could you share how you get to dump boot.img of any update? I'm seriously interested by this
Click to expand...
Click to collapse
I open a terminal emulator, send "su" command to gain root priviledges, then
Code: 
cp /dev/block/by-name/boot(_a OR _b depending on the active slot) /sdcard/boot.img

For the stock boot img i go to /data with cd command then use stat to get the latest created magisk_backup_hash, open the folder and search it there.
 
RZ(One)

RZ(One)

Member
Apr 14, 2022
25
22
AnotherM1m said:
I open a terminal emulator, send "su" command to gain root priviledges, then
Code: 
cp /dev/block/by-name/boot(_a OR _b depending on the active slot) /sdcard/boot.img

For the stock boot img i go to /data with cd command then use stat to get the latest created magisk_backup_hash, open the folder and search it there.
Click to expand...
Click to collapse
How are you supposed to get su privilege before dumping the boot?
 
O

Ostry10

Member
Nov 17, 2012
24
6
AnotherM1m said:
Ok firstly boot the patched boot img

open a terminal emulator, and send the "su" command to gain root priviledges.

now
Code: 
cd /mnt/product/nt_log/ota_log/

You are now in the log folder for ota updates.
Do
Code: 
ls

To have a list of files in the folder.
The files are multiple tar.gz files for older ota attempt but there should be one folder (one value not ending with tar.gz) with a modern date

Do
Code: 
cd *name of the folder*
to open the folder, ls command should show you the structure of the folder and that there should be an ota.txt file

Now to copy that txt file to the root of the sdcard
Code: 
cp ota.txt /sdcard/

Now on the root of the sdcard of the phone you should have the ota.txt log, send it to me privately through xda messages.
Click to expand...
Click to collapse

I wrote to you privately.
 
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
Still searching for a solution with @Ostry10
The error is caused by uefisecapp sha256 hash not corresponding to the expected one.

Also thanks to the user we have the ota zip to 154 from 152! I've updated the main page

UPDATED THE REASON
 
Last edited:
  • Like
Reactions: iamthechickengod
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
Hello!

For everyone having problems updating with offline ota updater because of error 20, I've made a script that easily copies logs from the phone into the sdcard.

github.com

GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1

Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1 - GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only test...
github.com github.com

You need root to run this script.

The logs can be then copied here to find out why things are not working.

@Ostry10
 
  • Like
Reactions: TheHappyBuddhist and Ostry10
caffeine01

caffeine01

Member
Dec 23, 2022
23
1
Who killing 'em in the UK?
AnotherM1m said:
Hello!

For everyone having problems updating with offline ota updater because of error 20, I've made a script that easily copies logs from the phone into the sdcard.

github.com

GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1

Bash script that searches for ota.txt and copies it to /sdcard, only tested on NP1 - GitHub - LukeSkyD/NP1-OtaTxtExtractor: Bash script that searches for ota.txt and copies it to /sdcard, only test...
github.com github.com

You need root to run this script.

The logs can be then copied here to find out why things are not working.

@Ostry10
Click to expand...
Click to collapse
i ran this and it seems like my bluetooth parition image is ****ed, and i think it is due to the fastboot rom.

heres the log output:

Code: 
05-20 22:54:57.560  1754  1754 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
05-20 22:54:57.565  1754  1754 I update_engine: [INFO:dynamic_partition_control_android.cc(340)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
05-20 22:54:57.568  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `abl`
05-20 22:54:57.570  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/abl_b partition without O_DSYNC
05-20 22:54:57.579  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.582  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 5 operations to partition "abl"
05-20 22:54:57.585  1754  1754 I update_engine: [INFO:delta_performer.cc(487)] Starting to apply update payload operations
05-20 22:54:57.646  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `aop`
05-20 22:54:57.648  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/aop_b partition without O_DSYNC
05-20 22:54:57.655  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.658  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 6 operations to partition "aop"
05-20 22:54:57.709  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `bluetooth`
05-20 22:54:57.711  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/bluetooth_b partition without O_DSYNC
05-20 22:54:57.716  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.718  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 20 operations to partition "bluetooth"
05-20 22:54:57.729  1754  1754 E update_engine: [ERROR:fec_file_descriptor.cc(32)] No ECC data in the passed file
05-20 22:54:57.731  1754  1754 E update_engine: [ERROR:verified_source_fd.cc(50)] Unable to open ECC source partition /dev/block/bootdevice/by-name/bluetooth_a: Invalid argument (22)
05-20 22:54:57.732  1754  1754 E update_engine: [ERROR:partition_writer.cc(317)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
05-20 22:54:57.734  1754  1754 E update_engine: [ERROR:partition_writer.cc(322)] Expected:   sha256|hex = D0877F02B283D60224B0A6815FE0F20980918DE5E1440B7792F440DA73B6A7F0
05-20 22:54:57.735  1754  1754 E update_engine: [ERROR:partition_writer.cc(325)] Calculated: sha256|hex = 8310E97ACC2B6C031095D1E0DDB62C4E64F1790223E3B31697415A292A2B4893
05-20 22:54:57.736  1754  1754 E update_engine: [ERROR:partition_writer.cc(336)] Operation source (offset:size) in blocks: 0:2
05-20 22:54:57.738  1754  1754 E update_engine: [ERROR:partition_writer.cc(245)] Unrecoverable source hash mismatch found on partition bluetooth extents: [0, 2]
05-20 22:54:57.740  1754  1754 E update_engine: [ERROR:delta_performer.cc(199)] Failed to perform SOURCE_COPY operation 11, which is the operation 0 in partition "bluetooth"
05-20 22:54:57.741  1754  1754 E update_engine: [ERROR:download_action.cc(227)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
05-20 22:54:57.777  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
05-20 22:54:57.781  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
05-20 22:54:57.782  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
05-20 22:54:57.783  1754  1754 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
05-20 22:54:57.784  1754  1754 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
05-20 22:54:57.786  1754  1754 I update_engine: [INFO:update_attempter_android.cc(591)] Processing Done.
05-20 22:54:57.788  1754  1754 I update_engine: [INFO:delta_performer.cc(1268)] Resetting recorded hash for prepared partitions.
05-20 22:54:57.790  1754  1754 I update_engine: [INFO:update_attempter_android.cc(625)] Resetting update progress.
05-20 22:54:57.858  1754  1754 I update_engine: Successfully unmapped snapshot vendor_b
 
A

AnotherM1m

Senior Member
Nov 20, 2016
303
157
caffeine01 said:
i ran this and it seems like my bluetooth parition image is ****ed, and i think it is due to the fastboot rom.

heres the log output:

Code: 
05-20 22:54:57.560  1754  1754 I update_engine: [libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
05-20 22:54:57.565  1754  1754 I update_engine: [INFO:dynamic_partition_control_android.cc(340)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/super
05-20 22:54:57.568  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `abl`
05-20 22:54:57.570  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/abl_b partition without O_DSYNC
05-20 22:54:57.579  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.582  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 5 operations to partition "abl"
05-20 22:54:57.585  1754  1754 I update_engine: [INFO:delta_performer.cc(487)] Starting to apply update payload operations
05-20 22:54:57.646  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `aop`
05-20 22:54:57.648  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/aop_b partition without O_DSYNC
05-20 22:54:57.655  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.658  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 6 operations to partition "aop"
05-20 22:54:57.709  1754  1754 I update_engine: [INFO:partition_writer_factory_android.cc(41)] Virtual AB Compression disabled, using Partition Writer for `bluetooth`
05-20 22:54:57.711  1754  1754 I update_engine: [INFO:partition_writer.cc(169)] Opening /dev/block/bootdevice/by-name/bluetooth_b partition without O_DSYNC
05-20 22:54:57.716  1754  1754 I update_engine: [INFO:partition_writer.cc(103)] Caching writes.
05-20 22:54:57.718  1754  1754 I update_engine: [INFO:partition_writer.cc(181)] Applying 20 operations to partition "bluetooth"
05-20 22:54:57.729  1754  1754 E update_engine: [ERROR:fec_file_descriptor.cc(32)] No ECC data in the passed file
05-20 22:54:57.731  1754  1754 E update_engine: [ERROR:verified_source_fd.cc(50)] Unable to open ECC source partition /dev/block/bootdevice/by-name/bluetooth_a: Invalid argument (22)
05-20 22:54:57.732  1754  1754 E update_engine: [ERROR:partition_writer.cc(317)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
05-20 22:54:57.734  1754  1754 E update_engine: [ERROR:partition_writer.cc(322)] Expected:   sha256|hex = D0877F02B283D60224B0A6815FE0F20980918DE5E1440B7792F440DA73B6A7F0
05-20 22:54:57.735  1754  1754 E update_engine: [ERROR:partition_writer.cc(325)] Calculated: sha256|hex = 8310E97ACC2B6C031095D1E0DDB62C4E64F1790223E3B31697415A292A2B4893
05-20 22:54:57.736  1754  1754 E update_engine: [ERROR:partition_writer.cc(336)] Operation source (offset:size) in blocks: 0:2
05-20 22:54:57.738  1754  1754 E update_engine: [ERROR:partition_writer.cc(245)] Unrecoverable source hash mismatch found on partition bluetooth extents: [0, 2]
05-20 22:54:57.740  1754  1754 E update_engine: [ERROR:delta_performer.cc(199)] Failed to perform SOURCE_COPY operation 11, which is the operation 0 in partition "bluetooth"
05-20 22:54:57.741  1754  1754 E update_engine: [ERROR:download_action.cc(227)] Error ErrorCode::kDownloadStateInitializationError (20) in DeltaPerformer's Write method when processing the received payload -- Terminating processing
05-20 22:54:57.777  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(177)] Received transfer terminated.
05-20 22:54:57.781  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(129)] TransferEnded w/ code 200
05-20 22:54:57.782  1754  1754 I update_engine: [INFO:multi_range_http_fetcher.cc(131)] Terminating.
05-20 22:54:57.783  1754  1754 I update_engine: [INFO:action_processor.cc(116)] ActionProcessor: finished DownloadAction with code ErrorCode::kDownloadStateInitializationError
05-20 22:54:57.784  1754  1754 I update_engine: [INFO:action_processor.cc(121)] ActionProcessor: Aborting processing due to failure.
05-20 22:54:57.786  1754  1754 I update_engine: [INFO:update_attempter_android.cc(591)] Processing Done.
05-20 22:54:57.788  1754  1754 I update_engine: [INFO:delta_performer.cc(1268)] Resetting recorded hash for prepared partitions.
05-20 22:54:57.790  1754  1754 I update_engine: [INFO:update_attempter_android.cc(625)] Resetting update progress.
05-20 22:54:57.858  1754  1754 I update_engine: Successfully unmapped snapshot vendor_b
Click to expand...
Click to collapse
Which sw version are you on?
 
You must log in or register to reply here.

Similar threads

herna
Development Paranoid Android Topaz 6 - Nothing phone (1)
Replies
392
Views
68K
S
Shuyin10
A
Question Gcam for Nothing phone 1
Replies
48
Views
40K
M
meuhmeuh51
Pho3nX
How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)
Replies
248
Views
38K
E
EzerchE
Sib64
  • Sticky
Question [HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly
Replies
423
Views
35K
I
iamthechickengod
aswin_a_s
Development PixysOS v6.3.1OFFICIAL for Nothing Phone 1 [android 13 QPR3] [STABLE]
Replies
131
Views
33K
aswin_a_s
aswin_a_s

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 4
    A
    AnotherM1m
    shailantani said:
    Thank you so much for explaining this!
    I just realised I had rooted it the wrong way, could you perhaps explain just a teeny bit more on that?
    So I have to flash the stock boot.img now? And then do I proceed with the update via dialer?
    And after that I have to proceed with booting magisk img to get root access again right
    Click to expand...
    Click to collapse
    HEADS UP EVERYONE

    I wrote a guide about updating NP1, also while rooted

    Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS

    Note: This is not a support thread for issues...
    forum.xda-developers.com forum.xda-developers.com

    It's in the third message

    Remember to never reboot with magisk, it does not work.


    Let us know how it goes and if you encounter any difficulty
    View
    3
    Pepousek67
    Pepousek67
    AnotherM1m said:
    Updates:
    Added 2.0.2.hotfix to incremental ota list, added stock and magisk patched boot, updated error 20 guide, added two guides to follow for updating the phone with steps to keep root

    Fixed some formatting issues.
    Click to expand...
    Click to collapse
    Screenshot_20230904-190402.png

    Small hotfix update for 2.0.2. came today via OTA. PS: this confirms that even after a manual update to 2.0.2, the update will come via OTA.
    View
    3
    A
    AnotherM1m
    pyry666 said:
    I can confirm that there is something wrong with non patched hotfix boot.img, tried previous one and it bootesd just fine. I also use magisk 26.3. Didnt try patched one though cause i like to patch myself. Maybe non patched hotfix boot.img is corrupted or somethin? Well everything works now anyway as it should..
    Click to expand...
    Click to collapse
    Yes you are right, stock 2.0.2.hotfix boot img was corrupted

    The new link is: https://mega.nz/file/j5Rl0bqC#UbfHZDLcJ-jf44jbHD7hH_qysWSz0TETptih9evgsO8
    View
    2
    A
    AnotherM1m
    Updates:
    Added 2.0.2.hotfix to incremental ota list, added stock and magisk patched boot, updated error 20 guide, added two guides to follow for updating the phone with steps to keep root

    Fixed some formatting issues.
    View
    2
    A
    AnotherM1m
    jmissao said:
    So, in case I'm in another custom ROM, in order to go to 2.0.2, I have to:
    1. first flash 1.1.8 full
    2. then incremental 1.1.8 -> 1.5.4
    3. then incremental 1.5.4 -> 1.5.5
    4. then 1.5.5 -> 1.5.6
    5. then finally 1.5.6 -> 2.0.2
    is that it?
    Click to expand...
    Click to collapse
    You should

    - Download full 1.1.7 EEA or GLOBAL
    - Extract boot and vendor_boot from the fw with payload dumper (do not delete the zip file yet)
    - Boot the phone into fastboot
    - Flash those two .img files
    - Boot into recovery and select adb sideload
    - adb sideload the full zip previously downloaded
    - wipe/format data

    You can now boot your phone, if you want to root it remember to BOOT the magisk patched boot, not flash it and then do a direct installation of magisk through the app.

    For the other fw versions there could be some otas that jumps through a lot of them that we don't know about.

    I would suggest to not root the phone but perform updates through the settings app.
    View
  • 31
    A
    AnotherM1m

    Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread.

    Regarding problems with the Phone(1), you can post in     this open topic​

    The Nothing Phone(1) was officially unveiled on July 12th and we know a good part of the specifications of the smartphone.

    • Phone(1) - Model : A063
    • Initial Code Name : Abra / Global Name : Lahaina / EEA Name = Spacewar
    • Android 12

    Platform =>OS - Android 12 - Nothing OS
    Chipset => Qualcomm SM7325-AE Snapdragon 778G+ 5G (6 nm)
    1. CPU => Octa-core (1x2.5 GHz Cortex-A78 & 3x2.4 GHz Cortex-A78 & 4x1.8 GHz Cortex-A55)
    2. GPU => Adreno 642L
    Memory => 8Go & 12Go
    Storage => 128Go & 256Go - UFS 3.1 - no card slot
    Sim => Dual SIM (Nano-SIM, dual stand-by)

    Network Technology => GSM / HSPA / LTE / 5G
    1. 2G Bands => GSM 850 / 900 / 1800 / 1900 - SIM 1 & SIM 2
    2. 3G Bands => HSDPA 800 / 850 / 900 / 1700(AWS) / 1900 / 2100
    3. 4G Bands => 1, 2, 3, 4, 5, 7, 8, 12, 17, 18, 19, 20, 26, 28, 32, 34, 38, 39, 40, 41, 66
    4. 5G Bands => 1, 3, 5, 7, 8, 20, 28, 38, 40, 41, 77, 78 SA/NSA
    5. Speed => HSPA 42.2/5.76 Mbps, LTE-A, 5G

    Comms => WLAN => Wi-Fi 802.11 a/b/g/n/ac/6, dual-band, hotspot
    1. Bluetooth => 5.2, A2DP, LE
    2. GPS => Yes, with A-GPS. Up to dual-band: GLONASS (1), BDS (2), GALILEO (1), QZSS (1)
    3. NFC => Yes
    4. Radio => Unspecified
    5. USB => USB Type-C 2.0, USB On-The-Go
    Dimensions => 159.2 x 75.8 x 8.3 mm - 6.27 x 2.98 x 0.33 in
    Weight => 193.5 g - 6.84 oz
    Build => Glass front (Gorilla Glass 5), glass back (Gorilla Glass 5), aluminum frame

    Dispaly => OLED, 1B colors, 120Hz, HDR10+, 500 nits (typ), 1200 nits (peak)
    Size => 6.55 inches = 103.6 cm2 (~85.8% screen-to-body ratio)
    Resolution => 1080 x 2400 pixels, 20:9 ratio (~402 ppi density)

    Battery => Li-Po 4500 mAh, non-removable
    => CHARGING => Fast charging 33W, 50% in 30 min, 100% in 70 min (advertised)
    => Wireless charging 15W
    => Reverse wireless charging 5W
    => Power Delivery 3.0
    => Quick Charge 4.0

    Protection => Corning Gorilla Glass 5

    Camera => 50 MP Main Camera, Dual
    => 50 MP, f/1.9, 24mm (wide-angle), 1/1.56", 1.0µm, PDAF, OIS
    => 50 MP, f/2.2, 114˚ (ultra wide angle), 1/2.76", 0.64µm
    => LED flash, panorama, HDR features
    => Video recording 4K@30fps, 1080p@30/60fps, gyro-EIS, live HDR
    => Front Camera, Selfie 16 MP, Single
    => Features -16 MP, f/2.5, (wide-angle), 1/3.1", 1.0µm
    => Video recording 1080p@30fps

    Others =>
    1. Multiple LED lights on the back (notifications, charging progress, camera fill light)
    2. Blinking red light on the back (video recording indicator)
    3. IP53 - splash, water and dust resistant
    4. 3.5mm jack => No
    5. Loudspeaker => Yes, with stereo speakers
    6. Sensors => Fingerprint (under display, optical), accelerometer, proximity, gyro, compass

    Android_14_1200x675_a45ea069-8c30-4396-bd9c-050ae4443dfb.jpg


    LATEST NEWS (dd/mm notation is used)



    ​
    NOTHING OS ZIP - DOWNLOAD OTA/FULL ZIP UPDATE FILES

    Special thanks to HofaTheRipper, AVB Delenda Est, neilphetamine, Cathair2906 & 1ststep for sharing their firmwares & boot files links !!
    ​
    ​
    ​
    ​
    ​








    ​
    ​







    (DO NOT PERFORM THE 1.1.7.HOTFIX UPDATE IF YOU WANT TO UPDATE TO 1.1.8)

    ​
    ​

    From BETA.2 onwards the update zips are unified meaning that the same zip can be used for both Global and EEA versions!

    ​
    ​
    From 1.5.2 onwards the update zips are unified meaning that the same zip can be used for both Global and EEA versions!






    ​

    NOTHING OS IMG - DOWNLOAD BOOT IMAGES

    /!\ IT'S HIGHLY RECOMMANDED /!\
    to always using fastboot "boot" command installation
    instead directly "flash" a patched boot.img file to avoid any risk of brick

    Code: 
    .\fastboot boot Magisk_Patched_XXX.img
    ​

    By the way if Magisk patched boot file is good, device will boot temporary with root and install Magisk, you must simply install/apply root on the boot definitively :
    - Open Magisk > Install > Install Directly (Recommanded) > Reboot... Voila !

    If the Magisk patched boot file don't boot, just do a hard reboot/shutdown by pressing ON/OFF button +5 seconds, device reboot directly with your stock boot without problems.

    ​














    • Stock 1.1.8
    • Magisk Patched 1.1.8

    From BETA.2 onwards Boot Images are unified meaning that the same img can be used for both Global and EEA versions!

    From 1.5.2 onwards Boot Images are unified meaning that the same img can be used for both Global and EEA versions!










    What are the regional variants of Nothing OS ?

    Nothing offers two distinct regional variants of Nothing OS.
    • Intended for European countries is the "EEA" version, as it meets the requirements of the European Privacy Directive and the General Data Protection Regulation (GDPR).
    • The other version, the so-called "Global Version" is intended for Asian and Australian devices.
    You can easily control the regional setting of your Phone(1) by going to your Shell terminal or Android emulator (e.g. Fuss, Termux) and executing the following command if on Nothing OS >= 1.5:
    Code: 
    getprop ro.product.name

    If Nothing OS <1.5
    Code: 
    getprop ro.product.system.name
    • These commands will return "SpacewarEEA" if the device is delivered with the European firmware.
    • For International models, the result should be "Spacewar" only.

    Don't forget to read this post which tries to gather your problems, but especially solutions brought by members

    [HELP THREADING] Nothing Phone 1 Common Issues and Problems​

    View
    22
    A
    AnotherM1m
    NOTHING OS - Older News
    Nothing just published this blog post:

    nothing.tech/blogs/news/android-14-beta

    It's really early in development, read carefully the post if you want to try Android 14 on Nothing Phone (1)
    Code: 
    error code -2: pre-build-incremental is different from ro.build.date.utc
    This is what many people are reporting while trying to update to 1.5.3.HOTFIX or 1.5.4

    Go to Settings, System, Date and Time, remove automatic time zone and set it manually to China, Shangai was the only option working for me.
    Now reopen the offline updater and try starting the update once again

    Don't forget to set automatic time zone again after you are done!
    The cause of the instability of rooted system with 1.5.3(/hotfix) is the implementation of MGLRU, a new way to handle processes and memory while the phone is under pressure.
    This module should fix the issue:

    GitHub - LukeSkyD/NP1-MGLRU-FIX: Magisk module to fix freezes and crashes on NP1 phone

    Magisk module to fix freezes and crashes on...
    github.com github.com

    If you encounter freezes or crashes user @gwolfu made this module which script runs every 30s to force MGLRU to stay disabled:

    GitHub - gwolf2u/MGLRU-Disabler

    Contribute to gwolf2u/MGLRU-Disabler...
    github.com github.com
    Both 1.5.3 and 1.5.3.hotfix versions of NOTHING OS are currently unstable if the device is rooted and booting a magisk patched boot img.
    An issue has been opened on magisk github.
    For now if you want root and a stable device stick to 1.5.2, do not update until the cause of freezes is found.

    NOTHING OS - Changelog

    Nothing OS 1.1.0 Changelog:
    Here’s the complete changelog for the Nothing OS 1.1.0 update for the Phone 1
    • New features
      • Introduced experimental Tesla control feature.
      • Introduced experimental NFT Gallery widget.
      • We heard your feedback on the Beta Launcher – the Search Bar on the home screen is now optional.
    • Camera improvements
      • Glyph fill light is now available in Portrait Mode.
      • Improved clarity and reduced noise when taking photos in low light environments.
      • Improved dynamic range when taking photos in low light environments.
      • Improved photo clarity when using the ultra-wide camera.
      • Improved colour consistency across the main and ultra-wide sensors.
    • Bug fixes & Performance optimisations
      • Updated Android security patch to July 2022.
      • Fixed a lock screen bug that would sometimes hide the fingerprint icon.
      • Improved the reliability of the Glyph Interface.
      • Battery life optimisations when device is on standby.
      • Improved Face Unlock performance.
      • General bug fixes.
    Nothing OS 1.1.2 Changelog:
    The complete changelog for the European Nothing OS 1.1.2 update​
    • New features
      • Added a toggle for showing the fingerprint icon when screen is off.
      • Always on display will now be turned off during the night by default.
    • Bug fixes & Performance optimizations
      • Improved charging performance and compatibility with 3rd party chargers.
      • Resolved Bluetooth codec issue.
      • Optimized minor UI details.
      • General bug fixes and stability improvement.
    Nothing OS 1.1.3 Changelog:
    The complete changelog for the European & Global Full Nothing OS 1.1.3 update​
    • New features
      • Added option to turn on Google’s Adaptive Battery to intelligently optimise battery life.
      • Redesigned fingerprint verification UI for 3rd party apps.
    • Camera improvements
      • When using Glyph lighting, images are automatically adjusted to optimal colour and brightness.
      • Impoved photo clarity when using the front camera.
      • Faster Night Mode and HDR photo processing time.
      • Richer colour saturation when using the ultra-wide camera.
      • Reduced noise and increased sharpness when using zoom.
      • Added reminder to clean the camera lenses.
    • Bug fixes and performance optimisations
      • Resolved an issue that caused stuttering in some apps like Twitter, Play Store etc.
      • Resolved an issue that prevented mobile hotspot from working properly.
      • Fixed ussye that caused the lock screen to crash after tapping on a notification and then trying to use finger unlock.
      • Polished minor UI details.
      • General bug fixes.
    Nothing OS 1.1.4 features the following changes:
    • New features
      • New option to flip the 3-button navigation bar.
      • All Ear (1) app features are now integrated into Nothing OS. Customize gesture controls and switch Noise Cancellation modes and more in Quick Settings and Settings.
      • Now supports LHDC high-def audio.
    • Camera improvements
      • New option to add a Nothing themed watermark to the camera app.
      • Improved ultra-wide camera colour calibration and increased colour consistency between main and ultra-wide sensors.
      • New motion detection algorithm added for improved stability when shooting moving objects.
      • Increased shooting speed when using HDR in ultra-wide mode.
    • System improvements
      • September Security Patch.
      • Reduced battery consumption for Always On Display and other use cases.
      • Improved thermal performance.
      • New UI for system updates.
    • Bug fixes & Performance optimizations
      • Fixed network issues for certain carriers.
      • Fixed an issue causing incoming calls to show up as Unknown Contact.
      • Fixed HDFC Bank app fingerprint issue.
      • General bug fixes.
    Nothing OS 1.1.6 features the following changes:
    • New features
      • Now supports Google AR Core.
      • Indian users covered by Reliance Jio can now access 5G.
    • Camera
      • Sharper videos with improved stability.
      • Recording light indicator is now always-on by default.
    • Improvements
      • Optimised, more fluid Launcher experience.
      • More accurate battery status.
      • Increased maximum brightness when displaying HDR content.
      • Updated, more reactive Flip to Glyph animation.
      • Glyph charging light now synced to sound effect.
      • Updated NFC sound effect.
      • General bug fixes.
    Nothing OS 1.1.7 features the following changes:
    • New features
      • Now supports battery percentage display for AirPods. You can enable it in Settings - Experimental features.
    • Improvements
      • Updated to October/November Security Patch.
      • Improved OS fluidity and reduced stutters.
      • Adjusted the thermal threshold to better balance performance and temperature.
      • Improved audio quality when recording videos.
      • More accurate battery status.
    • Bug fixes
      • Resolved an issue causing Whatsapp notifications to be unresponsive in lockscreen.
      • General bug fixes.
    Nothing OS 1.1.8 features the following changes:

    • The full Nothing X app will now be available in Nothing OS.
    • Fixed an issue causing the system to shutter in some scenarios.
    • General bug fixes.
    Nothing OS 1.5 Open Beta features the following changes:

    This is the first version of many to come and the priority is to ensure the stability of migrating to Android 13.
    • Android 13 Highlights:
      • More colour schemes are availables from the wallpaper selector
      • All apps must now have your permission before sending notifications
      • Added a QR code scanner shortcut in Quick Settings
      • Added support for setting per-app language preference
      • Added the Live Caption feature which detects speech from audio output to automatically generate captions.
      • Added a clipboard preview after copying text allowing the content to be edited directly from the clipboard
      • Better privacy protection such as Photo picker, Nearby WiFi devices Permission, Types of media permission, etc.
    • Nothing OS Improvements:
      • Improved the user interaction of Network and Connectivity tiles in Quick Settings
      • Reduced the wait time when loading apps
      • Implemented a new self-repair feature to periodically delete unused system dumps and cache
      • Optimised the smoothness of many animations throughout the whole system
      • Improved the volume setting panel, allowing granular volume controls without unlocking the device
      • Improved the game mode light notification and added the Google game dashboard
    • Weather app beta release!
      • Take an initial look at Nothing's in-house Weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
      • Air Quality Index and more animations will be added in later stages
    • This is the first version of the Nothing OS
      1.5 Open Beta, so there are still many more features in development and you should also expect to run into some bugs and with the following      :

      - Google Pay and Netflix cannot be used normally.
      - Pop-up view feature will not be available.
    Nothing OS 1.5.1 Beta features the following changes:

    A warm welcome back to the second round of the Nothing OS 1.5 beta programme! Below are some additional features that we will bring to the NothingOS 1.5 update. Additionally, congratulations to those of you have been newly selected to participate!
    • Weather app beta release!
      • New Nothing weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
    • Weather app beta release!
      • Take an initial look at Nothing's in-house Weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
      • Air Quality Index and more animations will be added in later stages

        Thanks for your ongoing support and contributions to our efforts in improving the Nothing OS Experience. Let's continue building Nothing together.
    Nothing OS 1.5.2 Stable features the following changes:

    It's finally here. Our Nothing OS 1.5 official release. As a thank you for taking part in our Open Beta, we want you to experience it first.

    Experience Nothing OS 1.5, powered by Android 13. Our most significant update yet. With all new features and improvements.
    • Weather app
      • New Nothing weather app
      • Tapping a weather widget on the homescreen now directly opens the corresponding city in Weather instead of opening a link
    • Customisation
      • All new Glyth soundpack for more ringtone and notification sounds.
      • More colour schemes available from the walpaper selector.
      • New collection of minimalist wallpapers.
      • Icons can match your background colour to make your home screen look more consistent.
      • Lockscreen shortcut customisations. Create shortcuts for camera, torch, device controls, and wallet.
    • Improved experience
      • Easily switch data usage when using dual SIM with the improved network Quick Settings panel.
      • Automaticallyshow the current network and display how much mobile data you have used in Quick Settings.
      • Directly scan a QR code in the Camera app. Scanner also appears as a shortcut in Quick Settings.
      • Select language preferences for different apps.
    • Visual improvement
      • A New look for Media Control. Puts album artwork on full display with a wider set of music controls.
      • Improved volume settings panel. Allows granular volume control without unlocking the device.
      • Improved Game mode light notifications. So there is less distraction when you are playing.
      • Smoother animations when transitioning the display between on and off.
      • More refined Camera app interface.
    • Privacy and safety
      • Get an alert when an app accesses your clipboard. Cleared history after a period of time to prevent unwanted access.
      • Added Personal Safety app.
      • Better privacy protection including Photo Picker, nearby Wi-Fi devices permission, and select media permission.
    • System performance
      • Fingerprint unlock accuracy has improved by up to 12%.
      • App startup speed has increased by up to 71%.
      • Standby power consumption has improved by up to 50%.
      • Implemented a new self-repair feature to periodically delete unused system dumps and cache.
      • Increased system stability.
      • General bug fixes.
    Nothing OS 1.5.3 features the following changes:
    • What’s New
      • New support for manually adding games to Game Mode (games not installed from Play Store will not be able to be used with the Game Dashboard).
      • Smoother animations for pop-up view.
      • Improved fingerprint transition between the lock screen and AOD.
      • New wallpapers.
      • Added support for Ear (2).
      • New memory management algorithm that reduces app restart times by over 35% and lowers CPU consumption to improve overall battery life. Improved system stability.
    • Bug fixes:
      • Fixed abnormal appearance of Night Light mode in certain scenarios.
      • Fixed the flashing charging prompt on the AOD interface.
      • Fixed issue where Glyph lights did not show for incoming WhatsApp calls.
      • Fixed freeze issues during YouTube video playback.
      • Fixed issue where weather data did not show in the Quick Look widget.
      • Other general bug fixes.
      • Update size: 91.79 MB
    Nothing OS 1.5.3.hotfix features the following changes:
    • Fixed an issue causing notifications to not appear when Quick Settings is active.
    • Fixed an issue preventing the NFC toggle to function as intended
    1683219274383.png
    screenshot_20230627-171648-png.5941475
    uokrfnbomtkb1.png
    1693840151336.png
    View
    8
    A
    AnotherM1m
    HOW TO PERFORM OTA UPDATES
    In red there are instructions that root users must follow to correctly update their phones
    By my tests, rebooting with magisk after an ota always leads to a bootloop

    Dialer method (recommended for root users)
    Download the right incremental from HERE
    In your phone's memory outside any folder, create a new folder called
    Code: 
    ota
    and place the previously downloaded .zip file there

    Open magisk, select uninstall, restore stock images

    if the operation is successful proceed, otherwise you'll need to boot into fastboot and flash stock boot img for your fw version with the command
    Code: 
    fastboot flash boot *stock boot file.img*
    Boot then magisk patched boot with the command
    Code: 
    fastboot boot *magisk patched boot file.img*

    Open the dialer app and dial
    Code: 
    *#*#682#*#*
    start the update and wait for it to finish

    When the message asking you to reboot appears, go back to your phone's homescreen (by pressing the home button or by swiping if you have gestures enabled) without selecting anything
    Open Magisk, on Magisk's tab, select install
    Then select install on inactive slot (ota) and wait for it to finish

    Reopen the dialer updater app which we left open before and
    select reboot

    you will reboot with the newer fw while rooted

    Settings app
    Beware of being two magisk patched boot talked about in this procedure: the newer fw magisk patched boot img and the current fw magisk patched boot img

    Download the Magisk patched boot img for the newer sw version you are going to install on your phone from     HERE

    Open magisk, select uninstall, restore stock images

    if the operation is successful proceed, otherwise you'll need to boot into fastboot and flash stock boot img for your fw version with the command
    Code: 
    fastboot flash boot *stock boot file.img*
    Boot then magisk patched boot img of you "old" fw with the command
    Code: 
    fastboot boot *magisk patched boot file.img*

    Open Settings' app, go to System, System update and start the update
    Press the reboot button when it finishes.

    After the phone turns off, press and hold VOL DOWN to boot into fastboot
    Launch the command
    Code: 
    fastboot boot *new magisk patched boot file.img*
    To boot to the newer fw while semi-rooted
    To keep root once the phone boots up and the update notification finishes, open Magisk, select install and then direct installation

    Couldn't update - Installation problem / Error 20
    1693842774926.png

    This error will be displayed if you are trying to perform an OTA Update with non-stock/broken partitions.

    If you are rooted you probably didn't restore the stock boot image before updating, but there could also be other reasons.
    Other broken partitions.

    For now, only phones with an unlocked bootloader can fix this issue.

    GitHub - LukeSkyD/NP1-FLASH-ALL-SCRIPT: Script to flash full zip os to your NP1

    Script to flash full zip os to your NP1...
    github.com github.com

    Follow this guide in order to reinstall your fw to a working state or dirty update your phone (without wiping)

    HOW TO GET BACK TO NOS FROM CUSTOM ROM
    PREREQUISITES
    • Fastboot/Recovery knowledge
    • Fastboot and adb drivers installed and working
    • Download the latest full zip update file available, 1.1.7 EEA or 1.1.7 GLOBAL
    • Extract boot.img and vendor_boot.img partitions from payload.bin inside the zip or simply download and extract them:
    1.1.7 EEA or GLOBAL

    LET'S PROCEED
    1. Boot the phone into bootloader mode
    2. Open a terminal on your pc
    3. With your terminal, flash stock 1.1.7 boot with the command
      Code: 
      fastboot flash boot *DRAG boot.img HERE*
    4. Flash stock 1.1.7 vendor_boot with the command
      Code: 
      fastboot flash vendor_boot *DRAG vendor_boot.img HERE*
    5. Boot into recovery with the command
      Code: 
      fastboot boot recovery
      or through your phone, with VOL DOWN/UP to navigate the menu and POWER Button to confirm
    6. From the phone, select Wipe fata/factory reset with VOL DOWN/UP buttons + POWER to confirm (needed for custom roms, unknown for downgrades)
    7. Then select Apply update from ADB
    8. On your pc, send the previously downloaded zip file with the command
      Code: 
      adb sideload *DRAG THE .ZIP FILE HERE*
    9. Wait for the process to finish
    DONE!

    HEADS UP WHILE UPDATING TO A13
    [STABLE] UPDATING TO NOS 1.5.2
    Prerequisites:
    Global & EEA device with NOS 1.1.8
    The OTA Update file from 1.1.8 to 1.5.2. The link is down below: Global and EEA are not unified.

    Global users will have no problem performing the update with the necessary precautions.
    An EEA user on 1.1.7 no hotfix should update to 1.1.8.
    Updating to 1.1.7.hotfix will prevent you from updating to 1.1.8.
    They will need to perform beta updates.

    [BETA] UPDATING TO NOS 1.5.2
    Prerequisites:
    Global device with NOS 1.1.7
    OR
    EEA device with NOS 1.1.7.hotfix
    The OTA Update file from 1.1.7(/hotfix) to 1.5.0. The link is down below.

    Then from 1.5.0 to 1.5.2 perform all the needed beta updates
    View
    7
    A
    AnotherM1m
    UPDATE: set the time zone to China, Shangai to use the offline updater
    View
    7
    TheHappyBuddhist
    TheHappyBuddhist
    @Phon3nX
    Reading through this thread (and other threads in this forum), I see a lot of users facing issues updating their devices, especially with root. Even I have faced issues with updating and I try different methods to fix it, but there is still no single method that works 100% of the time. Sometimes local update method works, sometimes sideloading with ADB, etc.

    It would be great if you could create a guide for updating their devices with root, possibly with all the different methods and troubleshooting methods. I do not mean unlocking or rooting, but updating NP1 by keeping root access. Sure, there are a lot of individual posts on this topic spread across this forum, as threads and as comments in threads like these, but I think it would be better to have it in one of the reserved sections in the original guide thread.

    Thank you and kudos for the great job you do here. :)
    View

New posts