[UNOFFICIAL BUILD] Nothing Phone 1 (Spacewar) for /e/OS-T and /e/OS-U

/e/OS Devices UnOfficial Builds
,
21

Hi ronnz98,
OK, I managed to unpack the boot.img and vendor_boot.img like it is described in

I enabled debugging mode and enabled there all the things that sounds useful :wink:
Now, going to bootloader with adb reboot bootloader there is shown in red letter: DEVICE STAT - locked.
When I now type

or even

fastboot flash boot boot.img && fastboot flash vendor_boot vendor_boot.img

like shown in
https://xdaforums.com/t/rom-official-spacewar-14-0-crdroidandroid-v10-x.4645778/
that was references here
nothing other than < waiting for any device > happens.
Continuing selecting “Recovery mode” even nothing changes. A few minutes later the nothing phone reboots to nothing OS.
What is my fault?

Edit: I found
https://www.xda-developers.com/how-to-bootloader-unlock-root-magisk-nothing-phone-1/
@ step 12 I struggle again: " Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device."
When I simply type “fastboot flashing unlock” nothing happens, when I select Start, the device restarts to Nothing OS. What is FFBM or the other Options Which one should I use? FFBM seems not to be the right one :frowning:

Sorry to be so silly :frowning:
Marte

22

Typically seen where you have a Windows drivers issue.

Check with Device manager if the phone is seen as a :warning: priblem device when in fastboot mode.

Windows update needs to find a “combination driver” or such.

23

No I’m in Linuxmint 20.3 here.
adb reboot bootloader works fine. But what do I have to do then to enable the fastboot commands? The pages I read suggests that I should select something with the volume keys.
Selecting Start then the device go to normal start. Selecting FFBM seems to have broken my device. 3 red dots are running from left to right … Puh, not really broken …
Back to bootloader I switched to recovery. I see an opened Android but fastboot even does only wait for any device.

Trying now fastboot devices instead of adb devices. adb tells me the phones that are connected to the PC, fastboot not.

Marte

I’m out of the house until 9o clock p.m. (berlin time). Then I’ll be back.

24

You should restart from the begining (unlock the bootloader).

1 Like
25

Did you try fastboot as root (??)

Very latest platform-tools.

BUT.

It is still locked. Did you think you unlocked it already?

26

No, as I wrote 2 hours ago. The command “fastboot flashing unlock” doesn’t work. On
https://www.xda-developers.com/how-to-bootloader-unlock-root-magisk-nothing-phone-1/
step 12 I don’t know how to do this. What to select to get fastboot work. Even “fastboot devices” doesn’t answer.
Marte

27

What is the response to

fastboot --version

I find: fastboot version 35.0.2-12147458 – that is July 2024, SDK Platform Tools

Have you tried a different cable? Are you using a USB port which is soldered to the motherboard of your PC? On the phone is OEM unlocking option Enabled?

Is platform-tools fully installed like Set up a device for development

Ubuntu Linux: Set up the following:

  • Each user that wants to use ADB needs to be in the plugdev group. If you see an error message that says you’re not in the plugdev group, add yourself to it using the following command:
sudo usermod -aG plugdev $LOGNAME

Groups only update on login, so you must log out for this change to take effect. When you log back in, you can use id to check that you’re in the plugdev group.

  • The system needs to have udev rules installed that cover the device. The android-sdk-platform-tools-common package contains a community-maintained default set of udev rules for Android devices. To install it, use the following command:
apt-get install android-sdk-platform-tools-common
28

the bootloader must be unlocked!!!

you have written it not so.

the unlocking is mandatory otherwise it will not work.

as @ronnz98 wrote at xda there are instructions on how to unlock it.

You can do this, and then everything else works. :slight_smile:

29

I both installed, and are able to define which version I use.

martin@Familienrechner:/mnt/NTFS-3.3T/eOS/test/platform-tools$ ./fastboot --version
fastboot version 35.0.2-12147458
Installed as /mnt/NTFS-3.3T/eOS/test/platform-tools/fastboot
martin@Familienrechner:/mnt/NTFS-3.3T/eOS/test/platform-tools$ fastboot --version
fastboot version 1:8.1.0+r23-5ubuntu2
Installed as /usr/lib/android-sdk/platform-tools/fastboot

I even tried it on my laptop using minuxmint 21.3 same issue. I’ll try it booting windows tomorrow.

I also are in plugdev group:

martin@Familienrechner:/mnt/NTFS-3.3T/eOS/test/platform-tools$ id
uid=1000(martin) gid=1000(martin) Gruppen=1000(martin),4(adm),5(tty),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),112(lpadmin),128(sambashare)

Even sdk is OK

martin@Familienrechner:/mnt/NTFS-3.3T/eOS/test/platform-tools$ sudo apt-get install android-sdk-platform-tools-common
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.       
Statusinformationen werden eingelesen.... Fertig
android-sdk-platform-tools-common ist schon die neueste Version (27.0.0+12).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
30

It would be very nice if I could do it :frowning:
I struggle on step 12.
“adb reboot bootloader” works fine. With red letters it starts with “FastBoot Mode” But as you registred it ends with red letters “DEVICE STATE - locked”
As far as I understood then I should

and give the command “fastboot flashing unlock”. But fastboot seems not work others than “fastboot --version” that you see in my message above :frowning:

I have no glue what to do. Tomorrow I’ll try with windows 10 may be windows 11, too.
Regards
Marte

31

Hey @Marte

because you don’t get the bootloader unlocked, I have a few questions.

  1. are developer settings on in original nothing os?

  2. if so, is OEM Unlock on?

  3. which nothing os version is used?

  4. usb debugging on?

you can try something else

Turn your phone off.

Then hold vol - pressed as well as the power button.

Then when you connect the phone to the PC and write fastboot devices,
something should be displayed.

it is not so you need to use another USB port or cable.

i think you can do that. :slight_smile:

1 Like
32

Marte, I didnt succeed using linux either. The locked moment in the process isnt fun, i know. Under windows it means you have to update the driver. Manually. Once you know how it is easy. Remember this is not build specific, so easier to find a solution online.

33

Hy there,
forget everything I wrote :frowning:
It was very simple, The third USB-C cable was good enough to do the job the others I labled now only to use as a charging cable. What I don’t understand: The other two cables where good enough to handle adb but not fastboot. Don’t mind, I see, there may be differences in quality. I recognise now also a big difference in speed for MTP transfers.
So silly. Sorry to bother you.
Thanks for your work on this phone to ronnz98 and all you other. Now I’ll turn 4 devices to /e/OS. the family is happy to upgrade our old J5 2016 :wink: to nothing phone 1
Marte

1 Like
34

It is not the first time we see that…

Congratulations for your success !

2 Likes
35

Hi admin here,
in my opinion you can remove my entries to keep the thread clear.
One simple question I do have again:
Should I lock the bootloader again? I tried it (with “fastboot flashing lock_critical” and “fastboot flashing lock”) and got a bootloop to recovery. I managed to reflash all, but with every reboot there is a nagscreen that tells me that the device is unlocked, unsave …
How to lock it correctly?
Next Question: How to root with Magisk? I really love Adaway on my systems, yes I know it works without, too, but I want to use VPN in other way.
Marte

36

You can’t relock the boot loader.

Install Magisk as usual… (device type dependent) Installation | Magisk

1 Like