best way in my opinion is the following:
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 1After 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
- Open the Settings app on your Nothing Phone 1.
- Tap on About phone.
- Locate the section named Software info and tap on it.
- On the next screen, tap on the Build number 7 times until it says you’re now a developer.
- 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.
- 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.
- Scroll down a bit until you see USB debugging. Enable it as well.
- 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.
- Now open up a terminal window/Command Prompt instance and enter the following command: adb devices
- 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.
- 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
- 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
- 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.
- 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.
- Now, reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
- Congratulations, your Nothing Phone 1 now has an unlocked bootloader!
- 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 MagiskWith 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.
- 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.
- 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.
- 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.
- 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
- Download and install the Magisk app on the Nothing Phone 1.
- Open the Magisk app and tap on the Install button.
- Choose Select and Patch a File. A file manager will pop up.
- Select the boot image that you pushed earlier and let Magisk patch it.
- Pull it off your phone with this command: adb pull /sdcard/Download/magisk_patched_[random_strings].img
- Reboot the Phone 1 into the bootloader: adb reboot bootloader
- Flash the patched boot image: fastboot flash boot /path/to/magisk_patched_boot.img
- Reboot the phone: fastboot reboot
- 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.
WARNING: I wrote this step to allow you to re-lock your bootloader, but it seems that for this step, there are some problems. So after this warning, if you continue on this path, I could not be held responsible for what you will have as a result: soft-bricked, bootloop, etc.menu. You can either do this by holding the power and volume down buttons while booting up, or by entering the following ADB command: adb reboot bootloader
[*]Once you’re on the bootloader menu, you’ll now have to switch to using fastboot command to communicate with your device. To unlock the Nothing Phone 1’s bootloader, enter the following command: fastboot flashing lock
[*]Reboot your phone back to the Android OS. You can do this by sending the following fastboot command: fastboot reboot
Many thanks to Skanda Hazarika for his tutorial which you can read on the xda news page.
And thanks to Qiyue_ for the 1st Boot Magisk Patched for the Phone1
"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.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
I mean, I already unlock critical when got the phone 2 months ago, now can lock that or keep it unlock?
.\fastboot boot Magisk_Boot_Patched_1.5_XXX.img
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.
what do you think about this?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.
fastboot flash abl abl.img fastboot flash aop aop.img fastboot flash bluetooth bluetooth.img fastboot flash boot boot.img fastboot flash cpucp cpucp.img fastboot flash devcfg devcfg.img flash fastboot dsp dsp.img flash fastboot dtbo dtbo.img fastboot flash featenabler featenabler.img fastboot flash hyp hyp.img fastboot flash imagefv imagefv.img fastboot flash keymaster keymaster.img fastboot flash modem modem.img fastboot flash multiimgoem multiimgoem.img fastboot flash odm odm.img fastboot fastboot flash product product.img fastboot flash qupfw qupfw.img flash fastboot shrm shrm.img flash fastboot system system.img flash fastboot system_ext system_ext.img flash fastboot tz tz.img flash fastboot uefisecapp uefisecapp.img flash fastboot vbmeta vbmeta.img flash fastboot vbmeta_system vbmeta_system.img fastboot flash vendor vendor.img fastboot flash vendor_boot vendor_boot.img flash fastboot xbl xbl.img fastboot flash xbl_config xbl_config.img
Hey Sib64, could you please rephrase the guide correctly. This is because the way it is currently written, users will end up carrying out the third step of re-locking the bootloader right after performing the second step of rooting their device, which in turn will result in a soft-brick or bootloop. So it is advised that rather than having the relocking process as STEP 3, make it an altogether different section.