How To Guide (Guide) Unlock Bootloader, Root with Magisk, Stock and Patched boot images: Model A065 EEA

Search This thread

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
Has anybody had issues updating to 2.0.3?

Restored stock image
installed 2.0.3
re-rooted and now the device says i'm at 2.0.2a and can't run the update any more "installation failed"

I can boot both rooted and stock boot images 2.0.2a and 2.0.3 on slot b
Cannot boot at all with any boot image on slot a

I get an error 20 when using the nothingofflineotaupdate
when trying to sideload i get an error with expecting pongEEU but trying to flash pong
Yea this is what happened to me, I flashed a payload using fastboot enhance and it crash dumped my phone...

Unfixable at present so sent it RMA..be careful what steps you take next and do not do what I did.

A factory wipe didn't fix it for me so don't bother with that..

It's possible it's the cow files which can be deleted using fastboot enhance, but I'd be hesitant to do anything at this point.

You're EEA based so there is no remote help.. ideally you need a service center...is there anything like that where you are?

I'll share this post with some of the lads/ Devs on TG and see if they can weigh in.

Someone suggested flashing a firmware using twrp, but I'd like to confirm first.

Don't do anything drastic for now
 

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
@1slotrk

One of the Devs came back and suggested not doing anything for now, it's been escalated with nothing, it's affecting a lot of people.. so you're not alone..

Not much you can do for now and honestly there isn't much between 2.0.2a and 2.0.3

It's your call but I'd trust what he's saying.
 
  • Like
Reactions: 1slotrk

Globus.gd

Senior Member
Mar 30, 2007
111
19
Gdynia
Nothing Phone 2
I am reading what You wrote about bricking..
Maybe there is an option to clone working phone (I mean to make a complete image of memory of working phone and flash it directly to bricked phone)
Cloning SD cards is quite easy, making image od card memory block by block.
Maybe this could be a solution.. Then we won't have differences in slot A or B.
But I have no idea how to get directly to flash memory.
I hope You understand my thinking :)
 

1slotrk

Member
Mar 13, 2016
35
10
Google Pixel C
OnePlus 7 Pro
Yea this is what happened to me, I flashed a payload using fastboot enhance and it crash dumped my phone...

Unfixable at present so sent it RMA..be careful what steps you take next and do not do what I did.

A factory wipe didn't fix it for me so don't bother with that..

It's possible it's the cow files which can be deleted using fastboot enhance, but I'd be hesitant to do anything at this point.

You're EEA based so there is no remote help.. ideally you need a service center...is there anything like that where you are?

I'll share this post with some of the lads/ Devs on TG and see if they can weigh in.

Someone suggested flashing a firmware using twrp, but I'd like to confirm first.

Don't do anything drastic for now
I am in the US and don't know why my phone says EEA (Europe????). I am not going anything for the time being. I am happy to wait and see what options I have. BTW thanks for the reply and advice.
 

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
I am reading what You wrote about bricking..
Maybe there is an option to clone working phone (I mean to make a complete image of memory of working phone and flash it directly to bricked phone)
Cloning SD cards is quite easy, making image od card memory block by block.
Maybe this could be a solution.. Then we won't have differences in slot A or B.
But I have no idea how to get directly to flash memory.
I hope You understand my thinking :)
That would be the MSM tool or nothing flash tool

It's currently being tweaked, as it's not working perfectly, in fact it can cause more problems than it fixes right now..

Only certain region devices work with it and only some of the time, you need to enter EDL mode in order to use it and not all devices want to go into EDL mode, I managed to get mine into it once.. then it wouldn't go again, I bought an EDL cable (hydra) but couldn't be bothered waiting for it so sent my device off for RMA..

In time these things are going to become fixed and working as they should, until then we're on thin ice...

Unlocking the bootloader and rooting is perfectly fine, some mods etc but any kind of flashing could get risky, like fastboot enhance or flash tool.
 

Ky0sHiR0

Senior Member
Aug 30, 2013
268
43
Yea the issue was unique to myself.

The guides still good, it was just my phone mate..

Uninstall magisk.

Update.

Grab magisk patched image 2.0.3

Or you could try to update with temp unroot, personally haven't been able to do it that way..
I did following instruction from first post:

  1. Uninstall Magisk
  2. Update
  3. Install to Inactive Slot (After OTA)
Really fast process.

Thanks
 
  • Like
Reactions: dladz

1slotrk

Member
Mar 13, 2016
35
10
Google Pixel C
OnePlus 7 Pro
Figured a way around my issue!

1. Restored stock boot images with Magisk
2. Reboot
3. Clear data from google play store and play store services
4. Reboot
5. OTA started working through the system updater in settings
6. Reboot using the reboot button in the OTA
7. Temp booted the 2.0.3 rooted boot img
8. Rooted using direct installation
 
  • Like
Reactions: kouzelnik3

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
Still waiting for my device to come back from RMA.

Sent a week ago yesterday..

Times its taken other devices to come back, including transit.

Sony z1 - 3 days
OnePlus 5 - 5 days
OnePlus 10 pro - 6 days
Nothing 2 - 8 days and counting.

All you'll see when you check the status is
"in progress"

If they miss the post today then it'll be Wednesday next week, which is approaching 2 weeks, that is blackberry time scales..

Appalling.

Screenshot_2023-09-21-10-07-38-86_40deb401b9ffe8e1df2f1cc5ba480b12.jpg
 

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
So far, when waiting for your Nothing 2, you're getting "nothing, too". :) :)
I'm experiencing the nothing experience, I've never felt like I've had so much of nothing before.. 😂

You RMA your device, anticipate over a week being without your phone in the UK, they are shocking, so little tech knowledge in their dept, they don't listen and work from a script, I clearly said that I have a device stuck in crash dump mode, they went ahead and asked me to jump into settings and factory reset..

Ahhhh,

I can't do it again so just going to leave them to it... Complaining clearly doesn't help..
 
Last edited:
  • Like
Reactions: Unn113 and HippoMan

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
Is that *their* drawing?

If so, it's "we empathize with your frustration about having to wait so long ... but we still are not moving very quickly with this."

:)
If it was I'd give them some respect, but nah it's mine 😂

Honestly at this point, I've lost all hope for a Monday delivery... It's looking Wednesday at the earliest... Trying so much to like their company but they're not helping their cause...

First red flag was the free gift for pre ordering.

A tote bag!

OnePlus gave me £150 headphones..

HTC have me beats headphones and two cases, I'd have been happy with a cap, but a tote bag... Cmon Mr Pei.

Now EDL mode is like a myth, you need a cable to get into it and not the one I bought but the V2 version.. now RMA being a shambles... It's a pretty broken system if I'm being honest.. they're definitely not reinventing the wheel here.
 

HippoMan

Senior Member
May 5, 2009
2,375
1,109
Hippoland
Just out of curiosity ...

I'm not familiar with the use of EDL. If I get my device into crash dump mode and have such an EDL v2 cable, how would I use that cable to get my device out of crash dump mode?

In other words, once I get the device to boot into EDL mode, then what's next? Is there a way to flash a ROM when in EDL? Or are there one or more other things I would need to do?

Thank you!
 
  • Like
Reactions: dladz and ysco

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
Just out of curiosity ...

I'm not familiar with the use of EDL. If I get my device into crash dump mode and have such an EDL v2 cable, how would I use that cable to get my device out of crash dump mode?

In other words, once I get the device to boot into EDL mode, then what's next? Is there a way to flash a ROM when in EDL? Or are there one or more other things I would need to do?

Thank you!
Generally speaking if you have been flashing things and having a tinker you'll usually be ok if you can get to recovery or fastboot, you have an avenue out...

But on the occasion that you can't and you're in what's known as crashdump mode, then you'd usually try one of a few things.

1. Force a power down by holding all buttons then hold vol up and down whilst connected to a laptop/pc, the screen won't come on but you'll hear a ding and your device manager ( if you've installed the 9008 driver) will show a device in 9008 under ports I believe, from there you can use the nothing flash tool which is basically a modded version of Qualcomms flashtool (QFIL)

From there you just click flash and you're back at 100% stock, your bootloader will be relocked and it'll be like a new phone, nothing like a factory reset, this is total.

2. If the button combination doesn't work, then you can use a cable with a button on it to invoke EDL mode, v1 I have (untested) but others have said that V2 works and will get you into EDL mode.

From there you just just click flash etc etc.

3. Open your phone and use the test points, afaik no one knows where they are just yet so that's not an option.

4. RMA like me, because nothing worked.

I chose the RMA method because I stupidly thought that it wasn't going to work and nothing being a new company would be fast in returning my device..

The nothing flash tool itself has an NTFI file (I think it's NTFI) which houses the phones software, however the ones we've tested don't actually work yet (v 715 iirc).

A newer version of the flash tool firmware is out there but we don't have it yet, eventually someone will "acquire it" and we'll be ok, but until then if you find yourself in CD mode then I would say with some certainty that you'll need to RMA your device.

Edit: whilst your phone is operational you could actually put it in to EDL mode by running through option 1... It'll 100% work, however I think if you're stuck in CD mode then the bootloader is having problems bringing you out so it doesn't work..

I managed to get into EDL once by luck when I was in CD mode then I just gave up when I couldn't again.
 
  • Like
Reactions: HippoMan

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
I think the v2.0 hydra cable is this one.

Could be wrong though, I got the v1 version off Amazon... £4


This one from TG.

Screenshot_2023-09-22-17-39-55-93_948cd9899890cbd5c2798760b2b95377.jpg
 
Last edited:
  • Like
Reactions: HippoMan

HippoMan

Senior Member
May 5, 2009
2,375
1,109
Hippoland
Generally speaking if you have been flashing things and having a tinker you'll usually be ok if you can get to recovery or fastboot, you have an avenue out...

But on the occasion that you can't and you're in what's known as crashdump mode, then you'd usually try one of a few things.

1. Force a power down by holding all buttons then hold vol up and down whilst connected to a laptop/pc, the screen won't come on but you'll hear a ding and your device manager ( if you've installed the 9008 driver) will show a device in 9008 under ports I believe, from there you can use the nothing flash tool which is basically a modded version of Qualcomms flashtool (QFIL)

From there you just click flash and you're back at 100% stock, your bootloader will be relocked and it'll be like a new phone, nothing like a factory reset, this is total.

2. If the button combination doesn't work, then you can use a cable with a button on it to invoke EDL mode, v1 I have (untested) but others have said that V2 works and will get you into EDL mode.

From there you just just click flash etc etc.

3. Open your phone and use the test points, afaik no one knows where they are just yet so that's not an option.

4. RMA like me, because nothing worked.

I chose the RMA method because I stupidly thought that it wasn't going to work and nothing being a new company would be fast in returning my device..

The nothing flash tool itself has an NTFI file (I think it's NTFI) which houses the phones software, however the ones we've tested don't actually work yet (v 715 iirc).

A newer version of the flash tool firmware is out there but we don't have it yet, eventually someone will "acquire it" and we'll be ok, but until then if you find yourself in CD mode then I would say with some certainty that you'll need to RMA your device.

Edit: whilst your phone is operational you could actually put it in to EDL mode by running through option 1... It'll 100% work, however I think if you're stuck in CD mode then the bootloader is having problems bringing you out so it doesn't work..

I managed to get into EDL once by luck when I was in CD mode then I just gave up when I couldn't again.
Thank you for this detailed and very helpful explanation!

I never knowingly installed the "9008 driver", and I don't even know what that is.

I've ordered a v2 EDL cable now, just in case I might need it in the future.

I hope that "nothing" turns into "something" for you and that you get your phone back soon!
 
Last edited:
  • Like
Reactions: dladz

dladz

Senior Member
Aug 24, 2010
16,027
5,977
Liverpool
Nothing Phone 2
Thank you for this detailed and very helpful explanation!

I never knowingly installed the "9008 driver", and I don't even know what that is.

I've ordered a v2 EDL cable now, just in case I might need it in the future.

I hope that "nothing" turns into "something" for you and that you get your phone back soon!
Here's the driver.

Really hope they fix their bootloader issues and release full kernel sources.

Time will tell I guess.
 

Attachments

  • Qualcomm-NT_PONG.zip
    429.8 KB · Views: 10
  • Like
Reactions: HippoMan

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Finally got my phone back after 2 weeks.

    England to England.

    Nothing takes that long to run the qualcomm flash tool and ship back.

    Crazy bad.... but it's back and i'm never doing that again.
    2
    Still waiting for my device to come back from RMA.

    Sent a week ago yesterday..

    Times its taken other devices to come back, including transit.

    Sony z1 - 3 days
    OnePlus 5 - 5 days
    OnePlus 10 pro - 6 days
    Nothing 2 - 8 days and counting.

    All you'll see when you check the status is
    "in progress"

    If they miss the post today then it'll be Wednesday next week, which is approaching 2 weeks, that is blackberry time scales..

    Appalling.

    Screenshot_2023-09-21-10-07-38-86_40deb401b9ffe8e1df2f1cc5ba480b12.jpg
    2
    no ^^nothing^^ lost in this proces
    So when you need to update you won't be able to If you're rooted as the update looks for the boot image, the very image you patched to root, as it won't be there you need to unroot to allow the update to go through, so no nothing is deleted.

    Tbh you do not need to uninstall the magisk app.

    To update you do this.

    Open magisk and click uninstall.
    Click full uninstall.
    Open settings and click system.
    Click system update.
    Take the update.
    Your device will reboot.
    Allow it to boot then boot to fastboot
    Download the patched boot image from the OP
    fastboot boot the patched boot image.
    Allow your phone to boot
    Open magisk and click install
    Direct install
    Reboot
    Done.
    2
    So when you need to update you won't be able to If you're rooted as the update looks for the boot image, the very image you patched to root, as it won't be there you need to unroot to allow the update to go through, so no nothing is deleted.

    Tbh you do not need to uninstall the magisk app.

    To update you do this.

    Open magisk and click uninstall.
    Click full uninstall.
    Open settings and click system.
    Click system update.
    Take the update.
    Your device will reboot.
    Allow it to boot then boot to fastboot
    Download the patched boot image from the OP
    fastboot boot the patched boot image.
    Allow your phone to boot
    Open magisk and click install
    Direct install
    Reboot
    Done.
    i know now but i think you quoted the wrong gy ;) but hey no problemo

    it was Mozie who asked
    2
    i know now but i think you quoted the wrong gy ;) but hey no problemo

    it was Mozie who asked
    Tbh i was addressing both of you as you do not need to uninstall the magisk app, but yea I clicked the last comment and you'd commented just before I did, didn't see your response... 👍🏼
  • 16
    Hi all,

    Always nice to have a guide to get you started with unlocking the bootloader & rooting your device (y)

    I'll always post boot images as and when firmwares become avaialable ;)



    IMAGES

    Nothing 2 V2.0.1 (Magisk 26.1)

    Nothing 2 V2.0.1a (Magisk 26.1)

    Nothing 2 V2.0.2 (Magisk 26.1)

    Nothing 2 V2.0.2a (Magisk 26.1)

    Nothing 2 V2.0.3 (Magisk 26.3)


    Pre-requisites

    1. ADB/Fastboot files so you can communicate with your device, you can download my copy here I put mine in c:\adb which is also where i'll be referring to for this guide
    2. A Windows 10 - 11 PC / Laptop and your USB cable, one that allows ADB / Fastboot commands (some do not)
    3. Capability to communicate via Fastboot, if you do not have the correct driver you can download my one from here
    4. Magisk manager installed on your phone
    You can grab it from here https://github.com/topjohnwu/Magisk




    Obtaining ADB access to your device using your computer and checking fastboot commands are working


    1. Connect your phone to your computer using your USB-C cable.

    2. Allow it to see the device, if it automatically installs the driver (which it should) then you're good to go, if not then use the driver i posted above in pre-requisites, this one

    3. On your phone Open settings and navigate to "About phone" and expand the Nothing OS tab

    4. Click "Build number" several times (5) then enter your PIN, this will enable "Developer Options"

    5. Back out, then click "System"

    6. Scroll down to "Developer Options" and open it.

    7. Scroll down to "USB Debugging" and turn it on (if at this point you are prompted with a dialogue box asking for authorization then please check the box and allow it) also turn on "OEM Unlocking" in the same section and agree to any prompts, back out to your home screen.

    8. On your computer Download this folder.

    This is adb and fastboot so you can talk to your phone via your PC.

    9. Move it to the root of the C: drive, so it looks like this in the filepath

    C:\adb

    10. Navigate to the folder and perform the following:

    i) Hold shift and right click an empty space within the folder
    ii) Click "Open Powershell Window here" or "Open a Command prompt Window here"
    iii) A black or blue window will appear with some text


    11. In the window type the following command

    adb devices
    press enter

    If you are now prompted with an authorization dialogue on your phone, please check the box and allow it.

    On your computer you should see a readout of a device followed by a code, this is a good sign, you now have ADB access and can continue, if it says unauthorised then you didn't allow the prompt on your phone, repeat the above and accept the prompt on your phone remembering to check the box.

    12. On your computer In the window type the following command:

    adb reboot bootloader
    press enter

    Your device will reboot to the bootloader, then type in the following command:

    fastboot reboot

    If your device rebooted then you're all set for the next part, if not and it says waiting for device then it'll be because your driver isn't working, grab the USB driver in pre-requisites then repeat until it works.



    Unlocking the bootloader


    NOTE* THIS WILL WIPE YOUR ENTIRE DEVICE, IT'S UP TO YOU IF YOU WANT TO BACK UP OR NOT. I WOULD RECOMMEND DOING SO


    1. Connect your phone to your computer

    2. On your computer Navigate to C:\adb

    i) Hold shift and right click an empty space within the folder
    ii) Click "Open Powershell Window here" or "Open a Command prompt Window here"
    iii) A black or blue window will appear with some text


    3. Type the following command into the window

    adb reboot bootloader
    press enter

    4. Type the following command into the window

    fastboot flashing unlock
    press enter

    NOTE* THIS IS THE PART THAT WIPES YOUR PHONE IF YOU WANT TO BACK OUT, NOW IS THE TIME TO DO SO, ONCE STARTED DO NOT DISCONNECT THE CABLE OR FORCE A SHUTDOWN FOR ANY REASON THIS COULD RESULT IN A BRICKED DEVICE

    5. Your phone will warn you and go through a set of screens, please agree and move forward until the device reboots

    You have just unlocked the bootloader to your phone, it will now show an orange state flag when you boot your phone, theres no way round this atm unfortunately, it's the small price we pay for freedom on android :(

    Once the device has booted, set it up again and then follow the steps to unlock "developer options" and enable "USB Debugging" once more, this is the last time you'll have to wipe (y)



    Using Fastboot Enhance & Magisk to obtain stock and patched boot images

    1. Download and copy the fastboot enhance folder to your desktop or a location of your choosing.

    Download from here: https://github.com/libxzr/FastbootEnhance/releases

    2. Download the firmware of your choice (if you can find one!! Always use full zips, not incremental) and open it using Winrar or a similar zip program, extract the file called payload.bin to a folder of your choosing.

    3. Run the program FastbootEnhance.exe, a window will appear, click Payload Dumper, then click browse and point to the payload.bin file, the contents of that payload.bin will now be shown, bare in mind you'll need to check the box "Allow incremental" even if it's a full zip

    4. Look through the images listed, one of them will be called boot.img, this is the file we'll be patching, highlight it then click extract, this will copy the image out to where you put your payload.bin file, copy this to your phone, root of storage; called /sdcard.

    On your phone

    5. Open up Magisk and click Install / Update, if you don't see update then change channel, do this by changing the channel in magisk settings, it'll then show the install/ update buttons.

    6. Select "Select and Patch a file" it'll open up a file browser, navigate to the boot.img you copied earlier and select it, allow it to complete (this will output a file called "magisk_patched" which will be output into the Downloads folder)

    You now have a patched boot.img ready to boot or flash to either slot with fastboot or boot via fastboot.

    I would recommend booting as this is risk free, if it's a bad image for whatever reason and you choose to flash it! Then your phone will bootloop.


    Rooting by booting

    1. Obtain a patched boot image for your device variant preferably using payload dumper or download one of mine from the foot of this guide or if you've just performed the above guide you should already have a functional one, copy this file to your fastboot folder on your computer

    2. Reboot your phone to fastboot
    and connect to your computer

    ADB/reboot/bootloader
    Press enter.

    3. Boot the magisk patched img

    fastboot boot magisk_patched (or name of your patched boot img)
    Press enter.

    Your phone should now boot automatically, you should now be rooted 👍🏼 But we need to make this permanent, if you were to reboot you would lose root.

    4. Open magisk manager and click install/update, if you are missing the install/ update buttons, change magisk version to beta in magisk settings and install the update, the buttons should then show.

    5. Select "Direct install (recommended)" then click ok.

    6. Allow magisk to permanently root your device then click reboot.

    You should now boot and remain rooted.





    Being rooted & Updating with an incremental update whilst retaining root
    ***NOTE: risky, doesn't always work, disable all modules before proceeding and reboot.

    1. Open Magisk and select "Uninstall Magisk" then select "Restore Images"

    2. Open settings / system / Software update and download the incremental update (will be substantially smaller than a full zip)

    3. Once completed you'll see "Restart Now" do not click this, back out and then re-open Magisk.

    4. Within Magisk, click "Install" then click "Install to Inactive Slot (After OTA)" Then click "Lets Go" your device will now reboot

    NOTE* I've noticed that my device didn't boot after doing this and or the update didn't install, if this happens your device will more than likely eventually swap slots and then boot, i also noticed an issue with the update not actually installing after performing the above steps, so do so at your own risk.



    STOCK BOOT IMAGES

    A065 Nothing 2.0.1

    A065 Nothing 2.0.1a

    A065 Nothing 2.0.2

    A065 Nothing 2.0.2a

    A065 Nothing 2.0.3


    PATCHED BOOT IMAGES

    A065 Nothing 2.0.1

    A065 Nothing 2.0.1a

    A065 Nothing 2.0.2

    A065 Nothing 2.0.2a

    A065 Nothing 2.0.3

    TROUBLESHOOTING

    Safety net fix (fixes wallet and hides root)



    Removal of Magisk Modules using ADB

    If flashing succeeds but you don't have root and you've followed all the instructions, you may have some magisk modules still active, try performing the following.

    1. Connect your phone to your computer.

    2. Reboot the phone, then during the boot animation enter this command via ADB.

    adb wait-for-device shell magisk --remove-modules

    3. Allow to boot, modules will be removed and root should then be active.


    Magisk not showing root, install updates buttons not visible

    1. Make sure you have granted permission to magisk in settings / apps / magisk / permissions

    2. Make sure that the update channel is on canary, then force close magisk and then re-open

    3. If it still doesn't work then update magisk using canary

    4. Last method to check would be to change to the beta channel in magisk settings, then install it.

    Or change the update channel, install the version on offer, then change back to canary, install and you should be good to go.


    Pulling a boot image from your live device

    1. Connect your phone to your computer and open up an adb command prompt with the capability to communicate with your phone (see above for set up)

    2. Connect using ADB SHELL

    adb shell
    Press enter

    3. Gain SuperUser access

    su
    Press enter

    4. For boot_a or boot_b type:

    dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a.img

    Press enter

    This will output a boot image to the root of your phone storage /sdcard/ called boot_a.img

    For boot_b type

    dd if=/dev/block/bootdevice/by-name/boot_b of=/sdcard/boot_b.img

    Press enter

    This will output a boot image to the root of your phone storage /sdcard/ called boot_b.img



    Window's version

    Windows 7 will not work with fastboot, please use Windows 10 or Windows 11


    FILES & DOWNLOADS


    ADB and Fastboot files: https://mega.nz/folder/HF1CwKQZ#NxsaViNm6Py0JzRipvrRqQ

    Fastboot Driver: https://mega.nz/folder/jEtBASIK#fiBe-cT40fHgP3rNWyFQEA

    Safety net fix mod: https://mega.nz/folder/KA8HQRoT#wk6S51NrM51DZuARhyiC5Q

    Stock boot image for 2.0.2 (if your phone won't update) thanks.
    @Unn113 and @ysco
    5
    OP UPDATED: Stock and Patched images available in OP (y)

    A065 V2.0.2a

    Stock: https://mega.nz/folder/uQcDhJqI#KG4gkCA50SbscQLkprgm1A
    Patched: https://mega.nz/folder/6YVSibKI#1YUt-56asVizUahL_DfrUw
    4
    Finally got my phone back after 2 weeks.

    England to England.

    Nothing takes that long to run the qualcomm flash tool and ship back.

    Crazy bad.... but it's back and i'm never doing that again.
    3
    Thanks for the guide.

    Any possibility of creating a magisk module for the same?
    Nah I doubt it, although we're all on the same one so I could do this, then upload the lk image..

    There has been things like this in the past, I used it on the many HTC devices although it was a little more involved back then.


    I'll have a look for the lk image today, as we don't have the full zip I'll try extract the lk image from my live device, edit it then reflash it, hopefully it accepts it...

    Would be nice if someone would have tried it before me but hey ho...

    Will do it when I get back from gym later on this afternoon most likely.
    3
    OP UPDATED: New 2.0.1 uploaded, both stock and patched images at the foot of the OP

    ;)