Question [HELP THREAD][Nothing Phone (1)] Ask Any Question, Noob Friendly

Search This thread
hi, i have a rooted nothing phone (1) on 1.1.3 global version.
i was wondering if there's a way to remap the double click on side button action through a magisk module or termux? i'd like to use it to open gcam instead. long press instead works too.
i downloaded the gcam apk from here, it's the mgc_8.4.600_a10_v13 snap version.
i hope this question wasn't asked before, i looked around and didn't find any, i actually opened a user for this.
thank you in advance! :)
If I remember once you're rooted you cannot changed it.
Which is paradoxical, because you root your smartphone to personalise it and some things do the opposite.
I know that on my OP7T, I can't do it, even though I use the same GCAM version as yours. By default, it's not possible, because my OP7T is rooted.
 
  • Like
Reactions: justjest
If I remember once you're rooted you cannot changed it.
Which is paradoxical, because you root your smartphone to personalise it and some things do the opposite.
I know that on my OP7T, I can't do it, even though I use the same GCAM version as yours. By default, it's not possible, because my OP7T is rooted.
I actually went ahead and installed both Lsposed and Physical Button Master Control and tried to set it up to open gcam when the power button is pressed twice, after disabling the built in option. Key word: tried.

It disabled the multitask viewer(????) for some odd reason which essentially locked me out of gesture navigation, and I could not for the life of me get it to work again.

Eventually I accidentally wiped my super partition (whoops) trying to format the phone through fastboot (because regular formatting through the OS didn't work either), and had to use this flash tool to flash EU firmware, then flash the super image provided in this forum (can't find the post, but I highly appreciate the user for saving my ass), run fastboot -w, and viola! I have a working phone.

Obviously I unrooted and locked bootloader because holy heck what a ride! No more Xposed or any type of module for me. Not until they're 100% confirmed to work, and even then I'll have to heavily consider the cost. :D
 

TempestDK

Member
Feb 17, 2010
42
3
Probably stupid question, but is there a way to set different ringtones for each SIM? .. I know I could do that on my OnePlus9. But can't seem to find anything regarding that on this phone.
Might be hiding in plain sight, but darn it if I can find it.
 

Nyssa1104

Senior Member
Jul 9, 2010
955
208
Saint Denis
Probably stupid question, but is there a way to set different ringtones for each SIM? .. I know I could do that on my OnePlus9. But can't seem to find anything regarding that on this phone.
Might be hiding in plain sight, but darn it if I can find it.
Still waiting on Nothing to introduce this option which should be a standard thing.
 

SHAUN231

Senior Member
Apr 14, 2010
344
15
hey I have not been able to update my nothing phone. When i go to update i get in red letters updates are temporarily unavailable try later. I have done hard reset and still same error. also did a fastfoot install of stock os and same issue . any ideas ?
 

BigAndStrong

New member
Aug 30, 2022
3
0
Prague
Nothing Phone 1
Hi

I'm trying to get out of this error for a week and nothing helps so far.
Problem:
- only one partition bootable at a time (not enough space for creating enought partitions for _a and _b simultaneous in userspace)
- logcat spamming errors every second and sometime freezing whole device.
- because of this spamm in logs probably flashdrive will die soon.
- implementing updates/root/modules always a roulette with bad end possible.
Done:
- reflashing with flashing tools from sh4tteredd
- reflashing super partition
- reading bunch of xda/git threads with similar errors on different devices
- trying different tools and other fastbootenchanced apps.
- contacted Nothing customer service with the answer: " lmao get it to the service now and dont forget to take some dollaz xD"

Probably I have deleted (or created) some important partition/file which is linked with fstab and cause error of mounting from the start of booting process.
Can someone with better knowledge take a look on this log? thx!
 

Attachments

  • 2022-09-19_015823_logcat.zip
    245.4 KB · Views: 7
Last edited:

mustachedocto

Member
May 13, 2019
29
13
Hello nothing users. I have a problem display color. Although it works without a password, it gets corrupted as soon as the password is set. I still haven't been able to figure out why. I lock it after making it cold or hot in alive or standart mode. When I turn it on it is waiting in a reset state... I will be damned! How can i fix this? (V1.1.4)
 

lone1lyday

New member
Sep 20, 2022
3
0
我下载了qq但是每次用一两天它就开始闪退再也进不去了 重装还是这样 有什么解决办法吗

Edit moderation : Incorrect language - XDA Rule #4 - Sib64 - Moderator
 
Last edited by a moderator:
  • Angry
Reactions: mustachedocto

skaiii

New member
Sep 20, 2022
1
0
Hi, 2 days ago I got an option to update to nothing OS 1.1.4. I ignored It for a day and the next day the option to update was no longer present. I even checked in the system updates section and It shows " Your system is up to date". How do I get it back ? Please help.
 

dexlemaffo

Senior Member
Sep 3, 2014
89
22
Rabat
Samsung Galaxy A52s 5G
Hi, 2 days ago I got an option to update to nothing OS 1.1.4. I ignored It for a day and the next day the option to update was no longer present. I even checked in the system updates section and It shows " Your system is up to date". How do I get it back ? Please help.
 

icetea250

Member
Sep 19, 2022
14
1
I am trying to flash the firmware from fastbootd mode, but it fails with
Code:
FAILED (remote: 'No such file or directory')
Is there any solution or advice? Thank you and best regards,
Code:
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

Now connect your phone in fastboot mode to the PC via USB, then press enter to continue
product: lahaina
Erasing 'userdata'                                 OKAY [  0.013s]

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

Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
    Error: Sparse mode is only supported for android
/usr/local/bin/make_f2fs failed with status 255
fastboot: error: Cannot generate image for userdata
Setting current slot to 'a'                        OKAY [  0.006s]
Finished. Total time: 0.009s
Flashing A slot. Please wait...

Rebooting into fastboot                            OKAY [  0.002s]
< waiting for any device >
Finished. Total time: 10.509s
Sending 'abl_a' (148 KB)                           OKAY [  0.005s]
Writing 'abl_a'                                    OKAY [  0.010s]
Finished. Total time: 0.020s
Sending 'aop_a' (204 KB)                           OKAY [  0.008s]
Writing 'aop_a'                                    OKAY [  0.007s]
Finished. Total time: 0.019s
Sending 'bluetooth_a' (476 KB)                     OKAY [  0.017s]
Writing 'bluetooth_a'                              OKAY [  0.009s]
Finished. Total time: 0.031s
Sending 'boot_a' (98304 KB)                        OKAY [  3.085s]
Writing 'boot_a'                                   OKAY [  1.334s]
Finished. Total time: 4.426s
Sending 'cpucp_a' (184 KB)                         OKAY [  0.007s]
Writing 'cpucp_a'                                  OKAY [  0.006s]
Finished. Total time: 0.019s
Sending 'devcfg_a' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.004s]
Finished. Total time: 0.013s
Sending 'dsp_a' (65536 KB)                         OKAY [  2.049s]
Writing 'dsp_a'                                    OKAY [  0.293s]
Finished. Total time: 2.347s
Sending 'dtbo_a' (24576 KB)                        OKAY [  0.775s]
Writing 'dtbo_a'                                   OKAY [  0.138s]
Finished. Total time: 0.918s
Sending 'featenabler_a' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_a'                            OKAY [  0.005s]
Finished. Total time: 0.014s
Sending 'hyp_a' (3592 KB)                          OKAY [  0.116s]
Writing 'hyp_a'                                    OKAY [  0.027s]
Finished. Total time: 0.147s
Sending 'imagefv_a' (524 KB)                       OKAY [  0.018s]
Writing 'imagefv_a'                                OKAY [  0.010s]
Finished. Total time: 0.034s
Sending 'keymaster_a' (264 KB)                     OKAY [  0.009s]
Writing 'keymaster_a'                              OKAY [  0.007s]
Finished. Total time: 0.021s
Sending 'modem_a' (173676 KB)                      OKAY [  5.414s]
Writing 'modem_a'                                  OKAY [  0.393s]
Finished. Total time: 5.812s
Sending 'multiimgoem_a' (16 KB)                    OKAY [  0.001s]
Writing 'multiimgoem_a'                            OKAY [  0.004s]
Finished. Total time: 0.010s
Sending 'odm_a' (1052 KB)                          OKAY [  0.035s]
Writing 'odm_a'                                    FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_a' 1/8 (262108 KB)         OKAY [  8.244s]
Writing 'product_a'                                FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_a' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_a'                                  OKAY [  0.034s]
Finished. Total time: 0.041s
Sending 'shrm_a' (48 KB)                           OKAY [  0.002s]
Writing 'shrm_a'                                   OKAY [  0.005s]
Finished. Total time: 0.011s
Sending sparse 'system_a' 1/6 (262104 KB)          OKAY [  8.228s]
Writing 'system_a'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_a' 1/2 (262116 KB)      OKAY [  8.289s]
Writing 'system_ext_a'                             FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_a' (3636 KB)                           OKAY [  0.114s]
Writing 'tz_a'                                     OKAY [  0.042s]
Finished. Total time: 0.161s
Sending 'uefisecapp_a' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_a'                             OKAY [  0.006s]
Finished. Total time: 0.016s
Sending 'vbmeta_a' (8 KB)                          OKAY [  0.001s]
Writing 'vbmeta_a'                                 OKAY [  0.004s]
Finished. Total time: 0.010s
Sending 'vbmeta_system_a' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_a'                          OKAY [  0.004s]
Finished. Total time: 0.009s
Sending sparse 'vendor_a' 1/5 (262104 KB)          OKAY [  8.318s]
Writing 'vendor_a'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vendor_boot_a' (98304 KB)                 OKAY [  3.079s]
Writing 'vendor_boot_a'                            OKAY [  0.307s]
Finished. Total time: 3.391s
Sending 'xbl_a' (3600 KB)                          OKAY [  0.117s]
Writing 'xbl_a'                                    OKAY [  0.037s]
Finished. Total time: 0.160s
Sending 'xbl_config_a' (224 KB)                    OKAY [  0.008s]
Writing 'xbl_config_a'                             OKAY [  0.008s]
Finished. Total time: 0.021s
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
< waiting for any device >
Setting current slot to 'b'                        OKAY [  0.038s]
Finished. Total time: 0.041s
Flashing B slot. Please wait...
Rebooting into fastboot                            OKAY [  0.002s]
< waiting for any device >
Finished. Total time: 10.764s
Sending 'abl_b' (148 KB)                           OKAY [  0.006s]
Writing 'abl_b'                                    OKAY [  0.006s]
Finished. Total time: 0.015s
Sending 'aop_b' (204 KB)                           OKAY [  0.007s]
Writing 'aop_b'                                    OKAY [  0.006s]
Finished. Total time: 0.017s
Sending 'bluetooth_b' (476 KB)                     OKAY [  0.017s]
Writing 'bluetooth_b'                              OKAY [  0.009s]
Finished. Total time: 0.030s
Sending 'boot_b' (98304 KB)                        OKAY [  3.154s]
Writing 'boot_b'                                   OKAY [  1.304s]
Finished. Total time: 4.464s
Sending 'cpucp_b' (184 KB)                         OKAY [  0.007s]
Writing 'cpucp_b'                                  OKAY [  0.005s]
Finished. Total time: 0.017s
Sending 'devcfg_b' (52 KB)                         OKAY [  0.002s]
Writing 'devcfg_b'                                 OKAY [  0.004s]
Finished. Total time: 0.010s
Sending 'dsp_b' (65536 KB)                         OKAY [  2.106s]
Writing 'dsp_b'                                    OKAY [  0.272s]
Finished. Total time: 2.381s
Sending 'dtbo_b' (24576 KB)                        OKAY [  0.787s]
Writing 'dtbo_b'                                   OKAY [  0.134s]
Finished. Total time: 0.927s
Sending 'featenabler_b' (88 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.004s]
Finished. Total time: 0.012s
Sending 'hyp_b' (3592 KB)                          OKAY [  0.118s]
Writing 'hyp_b'                                    OKAY [  0.028s]
Finished. Total time: 0.150s
Sending 'imagefv_b' (524 KB)                       OKAY [  0.018s]
Writing 'imagefv_b'                                OKAY [  0.009s]
Finished. Total time: 0.031s
Sending 'keymaster_b' (264 KB)                     OKAY [  0.010s]
Writing 'keymaster_b'                              OKAY [  0.007s]
Finished. Total time: 0.021s
Sending 'modem_b' (173676 KB)                      OKAY [  5.571s]
Writing 'modem_b'                                  OKAY [  0.385s]
Finished. Total time: 5.960s
Sending 'multiimgoem_b' (16 KB)                    OKAY [  0.001s]
Writing 'multiimgoem_b'                            OKAY [  0.004s]
Finished. Total time: 0.009s
Resizing 'odm_b'                                   OKAY [  0.004s]
Sending 'odm_b' (1052 KB)                          OKAY [  0.037s]
Writing 'odm_b'                                    OKAY [  1.064s]
Finished. Total time: 1.109s
Sending sparse 'product_b' 1/8 (262108 KB)         OKAY [  8.436s]
Writing 'product_b'                                FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB)                          OKAY [  0.003s]
Writing 'qupfw_b'                                  OKAY [  0.035s]
Finished. Total time: 0.043s
Sending 'shrm_b' (48 KB)                           OKAY [  0.002s]
Writing 'shrm_b'                                   OKAY [  0.005s]
Finished. Total time: 0.011s
Sending sparse 'system_b' 1/6 (262104 KB)          OKAY [  8.373s]
Writing 'system_b'                                 FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Resizing 'system_ext_b'                            OKAY [  0.004s]
Sending sparse 'system_ext_b' 1/2 (262116 KB)      OKAY [  8.288s]
Writing 'system_ext_b'                             OKAY [  1.612s]
Sending sparse 'system_ext_b' 2/2 (221164 KB)      OKAY [  6.973s]
Writing 'system_ext_b'                             OKAY [  0.519s]
Finished. Total time: 17.564s
Sending 'tz_b' (3636 KB)                           OKAY [  0.119s]
Writing 'tz_b'                                     OKAY [  0.029s]
Finished. Total time: 0.151s
Sending 'uefisecapp_b' (124 KB)                    OKAY [  0.005s]
Writing 'uefisecapp_b'                             OKAY [  0.005s]
Finished. Total time: 0.015s
Sending 'vbmeta_b' (8 KB)                          OKAY [  0.001s]
Writing 'vbmeta_b'                                 OKAY [  0.004s]
Finished. Total time: 0.009s
Sending 'vbmeta_system_b' (4 KB)                   OKAY [  0.001s]
Writing 'vbmeta_system_b'                          OKAY [  0.005s]
Finished. Total time: 0.010s
Resizing 'vendor_b'                                OKAY [  0.005s]
Sending sparse 'vendor_b' 1/5 (262104 KB)          OKAY [  8.235s]
Writing 'vendor_b'                                 OKAY [  1.599s]
Sending sparse 'vendor_b' 2/5 (262100 KB)          OKAY [  8.254s]
Writing 'vendor_b'                                 OKAY [  0.543s]
Sending sparse 'vendor_b' 3/5 (262120 KB)          OKAY [  8.268s]
Writing 'vendor_b'                                 OKAY [  0.570s]
Sending sparse 'vendor_b' 4/5 (262132 KB)          OKAY [  8.397s]
Writing 'vendor_b'                                 OKAY [  0.550s]
Sending sparse 'vendor_b' 5/5 (148720 KB)          OKAY [  4.798s]
Writing 'vendor_b'                                 OKAY [  0.390s]
Finished. Total time: 41.975s
Sending 'vendor_boot_b' (98304 KB)                 OKAY [  3.116s]
Writing 'vendor_boot_b'                            OKAY [  0.274s]
Finished. Total time: 3.394s
Sending 'xbl_b' (3600 KB)                          OKAY [  0.115s]
Writing 'xbl_b'                                    OKAY [  0.036s]
Finished. Total time: 0.154s
Sending 'xbl_config_b' (224 KB)                    OKAY [  0.008s]
Writing 'xbl_config_b'                             OKAY [  0.007s]
Finished. Total time: 0.020s
Rebooting into bootloader                          OKAY [  0.000s]
Finished. Total time: 0.000s
< waiting for any device >
Setting current slot to 'a'                        OKAY [  0.038s]
Finished. Total time: 0.041s
Rebooting                                          OKAY [  0.001s]
Finished. Total time: 0.001s

Your phone(1) is rebooting
Press enter to continue
 

wozrast

New member
Sep 21, 2022
1
0
Hi family, I put the root on 1.1.3. I'm waiting for the OTA update to 1.1.4 to arrive. What actions will I need to take to save the root rights?
 

1stStep

Senior Member
Mar 27, 2012
59
2
Pau
Hi all
I figure buying the NP1 to replace my old Samsung Note3 lite. Please tell me the things I don't understand before I buy : I'm interested in having a phone without google's proprietary dependencies, so I guess I'll have to unlock the bootloader first then root the Nothing to install a ROM cooked by a dev.
First of all, I browsed the [ROM][OTA]... thread but I didn't find a link to a ROM with a description, maybe I missed it or we have to cook ourself ? Can we process all the steps and traps/errors from a Linux PC or do we need a Windows PC? If Windows is needed, anyone has experience of using a VM in that adventure?
Many thanks
 

Top Liked Posts

  • 1
    If the phone says fast charging is it always 33w? Or it can like fast charge at 15w?

    With ampere I'm seeing 3A but the voltage stays at around 4.4 which should mean 5V
    From my own experience, probably to prevent excess heat and battery wear, Nothing is throttling the wattage with screen on to max 15w, on my phone it's closer to 11w. According to AccuBattery's history, the average screen off charge speed when on a USB-PD 33w charger shows about 5800mA, so ~30w, whereas with screen on it's 1906mA, around 11w . So, if your charger is QC3, QC4 or USB-PD 3 compatible, it should charge the phone full speed when not touching the phone and with the screen off :)

    Edit: with lower wattage chargers, it is probably still halving the current just in case. Not sure.
  • 1
    I am considering to buy this phone and I'm wondering about few things.

    1. Does the phone screen use noticable PWM? Is it possible to use DC dimming? I am very sensitive to low frequencies used by many manufacturers like Samsung and had to switch to LCD screens in the past.

    2. What is "lost" after bootloader unlocking? Some manufacturers screw up camera, others remove DRM almost completely. Does Widevine stay at L1, or is it downgraded to L3?

    3. Does TWRP support data decryption?

    4. Does the phone support "hotbooting" by command "fastboot boot boot_image.img"? One of my previous phones didn't and rooting with Magisk/TWRP was PITA. :)

    Thanks!
    1. No dc dimming as far as i know.
    2. Im have root. DRM Info says: Security Level: L1
    3. No TWRP Recovery atm and i dont think anyone is working on this.
    4. Hotboot is possible.
    1
    You need to display white content for black bars to be easily visible, but it sounds like NP1 is using DC dimming afterall (I found a little conflicting reports on this). 🙂
    Tried again with white content. Flickering bars as you can see.

    The Nothing Phone is an awesome device. Hopefully it fits your needs.
    1
    NP1 bars seem better than mine on Mi A3 phone, so hopefully it'll be fine.

    Btw. is it possible to swap left and right buttons when using the standard navigation bar? I must have back button on the right side for one handed usage. 🙂
    I checked that for you and its possible(there is an option to switch it in normal settings). :)
    1
    I checked that for you and its possible(there is an option to switch it in normal settings). :)
    Cheers mate, I appreciate the effort! 🙂
    1
    Tried it again. Flashed super.img and used the sh4tteredd tool to flash the rest and it still only boots into fast boot
    You made sure that you chaged the boot slot as last step before booting?
  • 5
    Hi Everyone,
    I have created this thread which will allow to gather, but also to help by bringing answers to the various problems which can meet the owners of the Phone(1).
    Unfortunately some of these problems cannot be solved here, in which case you will have to contact Nothing Support and explain your problem clearly.
    Otherwise, if your problem can be solved here, feel free to post it here and xda members may be able to provide a solution for you and others.


    PLEASE SEARCH AND READ BEFORE TO POST EVERYWHERE, FOR A BETTER HELP. THANKS (y)
    3
    Hi, i noticed a weird bug with night shift mode on the nothing phone1, no matter how you'll set up your night shift mode it will always turn it on BUT it'll never turn it off again, at least for me now.

    Hopefully it'll get fixed within the next update
    3
    I was thinking of backing up my IMEI numbers when I get my device, to prevent this from happening. I'm hoping the Qualcomm Product Support Tool works with the phone. @Sib64 Do you suggest any other methods to back up the IMEI?
    Having no clear and definite visibility on this kind of problem and despite the various messages left on the Nothing Discord or the forum, there is no feedback yet.😠
    I wrote the tutorial that allows to use Qualcomm's tool (Qualcomm Product Support Tools) but I'm not sure if it works for the Phone(1), even if the processor is a Qualcomm Snapdragon.
    So when in doubt, I prefer not to post it.

    But this afternoon I will post a tutorial on how to use Sideload.;)
    2

    [IMEI CODEs switched to null]

    I have gone into engineerigmode and CIT app and i have seen all activity without apply any modified values.
    After i have applaied the new version of NothingOS 1.0.2 i have restarded phone and my imei code have switched to null.

    So i have unlocked oem feature in developer menu for performing fastboot flashing method of all partitions in the next future. I have perfomed a factory reset but my phone now is in bootloop bootloader mode. It's in softbrick.

    I have send some emails to nothing support.

    Anyone have the same/similar problem?​

    Thanks for the thread Sib.

    So about problem 1, heading over from the other thread, continuing it here,
    Issue is us getting some of our phone's partitions getting corrupted because we accessed engineering mode, cit (but no toggling on/off anything) Phone's on NothingOS1.0.2

    Eventually losing IMEI. It showing as "null" now.

    Tried contacting Nothing and Flipkart (India's logistics partner). And i'll update here as soon as something's up from either of them. Request other people in the same place to post here on the same
    I'll see if I can find anything on this subject elsewhere ;)
    2

    [IMEI CODEs switched to null]

    I have gone into engineerigmode and CIT app and i have seen all activity without apply any modified values.
    After i have applaied the new version of NothingOS 1.0.2 i have restarded phone and my imei code have switched to null.

    So i have unlocked oem feature in developer menu for performing fastboot flashing method of all partitions in the next future. I have perfomed a factory reset but my phone now is in bootloop bootloader mode. It's in softbrick.

    I have send some emails to nothing support.

    Anyone have the same/similar problem?​
    This Is my Twitter post about this issue. Share please for getting a technical answer.