How To Guide [GUIDE][HowTo] Unlock and root Nothing Phone (1)

[medok92]

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?

 

[Pho3nX]

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

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

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK. THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!) GOOD CONTINUATION TO ALL...

forum.xda-developers.com

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

ANNOUNCEMENT: I'M STOPPING THE FOLLOW UP AND UPDATE OF THIS TOPIC TODAY, IF SOMEONE WANTS TO TAKE OVER, CONTACT THE MODERATOR IN THIS LINK. THE TOPIC REMAINS AS IT IS AND WILL NOT BE UPDATED ANYMORE (BY ME ANYWAY!) GOOD CONTINUATION TO ALL...

forum.xda-developers.com

Links for tutorial and also the original 1.1.6 EEA if you want
Just patch it

 

[xtcislove]

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?

best way in my opinion is the following:

1. extract payload from 1.1.6 firmware using payload dumber
2. copy boot.img to phone
3. install latest magisk apk and patch the boot.img you copied with it
4. copy patched_boot.img to pc
5. reboot to bootloader and type fastboot BOOT patched_boot.img
6. if everything is fine your phone will boot and you can open magisk, deny reboot and select direct install.
7. enjoy root.

you can skip part 6 if you type fastboot FLASH patched_boot.img but first method is failsafe.

 

[ot_inc]

If you want to revert to NothingOS or want a boot.img, here you go.
patched boot.img is also available.(Global v1.1.0~v1.1.6)

reindex-ot.github.io

Re*Index. GitHub Pages

reindex-ot.github.io

 

[Oswald Boelcke]

Moderator Announcement

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

 

[phaleg]

Hey everyone,

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

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

How to bootloader unlock and root the Nothing Phone 1​

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

Step 1: Unlock the Nothing Phone 1’s bootloader​

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

Step 2 - Rooting your Nothing Phone 1 with Magisk​

With an unlocked bootloader, you can now boot modified boot images. For Magisk to work, you’ll need to patch the Nothing Phone 1’s stock boot image.

1. Since your device has been wiped earlier, you’ll need to go back and re-enable Developer Options and then re-enable USB Debugging. Make sure your Nothing Phone 1 is still recognized by your PC.
2. Download the full OTA package corresponding to the installed software version on the Nothing Phone 1.
   • 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.​

Spoiler: Relock the bootloader of your Phone(1)

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

Hello!
After point 4, I pushed to my mobile the boot image, I imagine that I do it with normal USB cable and phone on, because you mention to use the app magisk from phone to patch it, correct?

But the next steps, you say to pull the file off from phone with a command, that makes me think that this is in bootloader / fastboot mode? Points 9 to end basically, thanks

 

[MrUrgit]

Hello!
After point 4, I pushed to my mobile the boot image, I imagine that I do it with normal USB cable and phone on, because you mention to use the app magisk from phone to patch it, correct?

But the next steps, you say to pull the file off from phone with a command, that makes me think that this is in bootloader / fastboot mode? Points 9 to end basically, thanks

"adb" commands are done with the phone in normal operating mode i.e. switched on. You will need to enable the USB debugging option in Developer Settings first, and may also have to enable the USB file transfer mode.

"fastboot" commands are done in bootloader/fastboot mode

 

[Pho3nX]

Updated thread :
- Links (adb & Magisk)
- Advise (for Unlock Critical)

 

[gamal001]

Updated thread :
- Links (adb & Magisk)
- Advise (for Unlock Critical)

and who unlock critical, need to lock it or keep it ?

 

[Pho3nX]

and who unlock critical, need to lock it or keep it ?

Never unlock it, and i have tried all custom roms existing and back NOS multiple times and even downgrade without problems. So don't unlock critical is more safe.

 

[gamal001]

Never unlock it, and i have tried all custom roms existing and back NOS multiple times and even downgrade without problems. So don't unlock critical is more safe.

I mean, I already unlock critical when got the phone 2 months ago, now can lock that or keep it unlock?

 

[Pho3nX]

I mean, I already unlock critical when got the phone 2 months ago, now can lock that or keep it unlock?

No, if you have never encounter problem, still unlock.

 

[ilPLAymo]

hello, i could not go from 1.1.6 to 1.1.7 so i also tried to remove the root, now i have reached 1.5.0 Global but i can no longer reactivate the root
i see errors in the log but i can't interpret them
can anyone help me?
thanks in advance

 

[Pho3nX]

hello, i could not go from 1.1.6 to 1.1.7 so i also tried to remove the root, now i have reached 1.5.0 Global but i can no longer reactivate the root
i see errors in the log but i can't interpret them
can anyone help me?
thanks in advance

Best way is for you to :
1/ Uninstall Magisk Manager, if you have also Uninstall boot/Uninstall full options, apply them before
2/ Restart
3/ On Bootloader/Fastboot mode, take your Magisk Patched file here (be carefull to take the good version, Global or EEA) :

.\fastboot boot Magisk_Boot_Patched_1.5_XXX.img

4/ Your system boot only with Magisk privilege injected once, wait a little, Magisk Manager will appair again:
- In Magisk > Install > Install Directly (Recommanded > Reboot

Normally it should be good

 

[ilPLAymo]

thanks for your help, it doesn't work :-(
attached you can see MM before i uninstall it and the commands i've passed to the phone, i think there's no errors but when i've rebooted no MM app installed
the only thing changed is in file explorer, as you can see i have to phone's partitions (i guess a and b)
and look at the termux image: "qssi" what's this? it was Spacewar last time i check it
very strange situation, is like i could flash or boot any boot images and it make no difference, i could try to boot or flash an image from another phone, just to understand something more :-?

 

[Pho3nX]

thanks for your help, it doesn't work :-(
attached you can see MM before i uninstall it and the commands i've passed to the phone, i think there's no errors but when i've rebooted no MM app installed
the only thing changed is in file explorer, as you can see i have to phone's partitions (i guess a and b)
and look at the termux image: "qssi" what's this? it was Spacewar last time i check it
very strange situation, is like i could flash or boot any boot images and it make no difference, i could try to boot or flash an image from another phone, just to understand something more :-?

Boot again with the Magisk Boot Patched, if Magisk manager don't appair, install again the Magisk APK for refresh the Manager. After Magisk Manager installed > Install > Install Directly > Reboot

You can have this problem when you have used "Hide Magisk App" before upgrade ROM.

 

[ilPLAymo]

Boot again with the Magisk Boot Patched, if Magisk manager don't appair, install again the Magisk APK for refresh the Manager. After Magisk Manager installed > Install > Install Directly > Reboot

You can have this problem when you have used "Hide Magisk App" before upgrade ROM.

yes i was using option to hide magisk app before update to 1.5 but nothing mate, ive already tried this way many times but no results
another info, i was not able to update to beta so ive flashed the fastboot rom file from Lahaina in fact if you look deep at the pictures youll see his name in the bootloader version and i can flash everything but it doesnt change
i guess problem is there cause i can flash everything and my phone still boot, for my experience if i flash the wrong file phone does not boot so is like im not flashing or booting really even if i dont face any error with terminal commands

 

[ilPLAymo]

Boot again with the Magisk Boot Patched, if Magisk manager don't appair, install again the Magisk APK for refresh the Manager. After Magisk Manager installed > Install > Install Directly > Reboot

You can have this problem when you have used "Hide Magisk App" before upgrade ROM.

what do you think about this?
https://www.reddit.com/r/Magisk/comments/sez0uy

 

[ilPLAymo]

sadly but im backing up everything in order to move to Xtended ROM

 

[ilPLAymo]

ahahahah exactly when i was backing up i did it, magisk installed
don't know what exactly was the fix, the sure i can tell is that reboot to fastboot is wrong, reboot to bootloader works, only flash boot boot.img is wrong, flash boot_a works