Unlocking Bootloader/ Magisk Attempt

[panzercool]

Did you try a factory reset on recovery or go throught the steps to adb sideload the factory image?

Well, it does not boot into the recovery mode when I select it (using the volume button). It just reboots and goes back to the start boot mode! Is there anything we can do from the start mode (fastboot start mode)

 

[bggold]

Well, it does not boot into the recovery mode when I select it (using the volume button). It just reboots and goes back to the start boot mode! Is there anything we can do from the start mode (fastboot start mode)

You might be able to fastboot boot the stock boot.img to get back in and copy the boot.ing to sd and use same steps as used to make root permanent and dd the stick boot image.

Or get into recovery a d do a factory reset.

Just a thought.

 

[panzercool]

You might be able to fastboot boot the stock boot.img to get back in and copy the boot.ing to sd and use same steps as used to make root permanent and dd the stick boot image.

Or get into recovery a d do a factory reset.

Just a thought.

Sure, thank you! Let me try that! I

 

[bggold]

Sure, thank you! Let me try that! I

Let us all know so others can use it if needed.

 

[josh_zombie]

Managed to brick mine as well. Sending to Microsoft in the morning. Hoping they don't charge the ~ $650 I saw for an out of warranty repair.

 

[panzercool]

Managed to brick mine as well. Sending to Microsoft in the morning. Hoping they don't charge the ~ $650 I saw for an out of warranty repair.

If you have the Microsoft Complete you pay nothing for a replacement!

 

[bggold]

Managed to brick mine as well. Sending to Microsoft in the morning. Hoping they don't charge the ~ $650 I saw for an out of warranty repair.

If you have the Microsoft Complete you pay nothing for a replacement!

I know all companies except google state that unlocking boot loader voids the warranty. Never had an issue before. But I spoke with microsoft before we got permanent root and l3 support said it will void the warranty.

Please try my steps to see before you get hit possibly with a charge.

Just looking out for you guys.

 

[josh_zombie]

I know all companies except google state that unlocking boot loader voids the warranty. Never had an issue before. But I spoke with microsoft before we got permanent root and l3 support said it will void the warranty.

Please try my steps to see before you get hit possibly with a charge.

Just looking out for you guys.

No-go for me. I stupidly relocked bootloader and can't unlock again (Allow OEM unlock not toggled in developer options). Can't flash boot image in fastboot/can't get to ADB to restore factory image/can't boot into recovery. Afraid I have no choice but to send in for replacement at this point. Lessons learned.

---------- Post added at 11:37 PM ---------- Previous post was at 11:29 PM ----------

No-go for me. I stupidly relocked bootloader and can't unlock again (Allow OEM unlock not toggled in developer options). Can't flash boot image in fastboot/can't get to ADB to restore factory image/can't boot into recovery. Afraid I have no choice but to send in for replacement at this point. Lessons learned.

I can, however, get to Qualcomm EDL mode and my PC recognizes the Duo over USB. But from what I understand (not much with Qualcomm EDL) these Qualcomm EDL tools don't seem to be optimized for a UFS file system. Let alone being able to find the correct files for a reflash... that's a whole different issue I'm not sure is worth pursuing given how new Duo is and my lack of understanding exactly how it works.

 

[panzercool]

No-go for me. I stupidly relocked bootloader and can't unlock again (Allow OEM unlock not toggled in developer options). Can't flash boot image in fastboot/can't get to ADB to restore factory image/can't boot into recovery. Afraid I have no choice but to send in for replacement at this point. Lessons learned.

---------- Post added at 11:37 PM ---------- Previous post was at 11:29 PM ----------



I can, however, get to Qualcomm EDL mode and my PC recognizes the Duo over USB. But from what I understand (not much with Qualcomm EDL) these Qualcomm EDL tools don't seem to be optimized for a UFS file system. Let alone being able to find the correct files for a reflash... that's a whole different issue I'm not sure is worth pursuing given how new Duo is and my lack of understanding exactly how it works.

Same boat as you! Nothing works at the moment! I hope Microsoft releases a flash tool! That would be really helpful!

---------- Post added at 02:55 AM ---------- Previous post was at 02:53 AM ----------

OP! Please update your original posts with a warning that this may brick your phone! We now have a few devices that are being bricked!!

 

[PROTOCOL]

when trying to fastboot boot magisk_patched.img after adb reboot bootloader im getting a failed (remote) command is not available in locked device.
edit *fixed above bootloader wasnt completely unlocked.

How do you place img file in root of sd? on device or through adb?

 

[bggold]

when trying to fastboot boot magisk_patched.img after adb reboot bootloader im getting a failed (remote) command is not available in locked device.
edit *fixed above bootloader wasnt completely unlocked.

How do you place img file in root of sd? on device or through adb?

You can copy it over when you are fully booted or adb push it.

 

[PROTOCOL]

You can copy it over when you are fully booted or adb push it.

Got the img file to stick. Now for some reason when the phone is booted my computer doesn't recognize device so can't push any commands.

I've compiled a new m launcher APK separately and need root to make changes to try and push the actual Microsoft launcher into device. I haven't done Android work for a while and may have forgotten a few things lol. Any help is appreciated. Thanks.

 

[bggold]

Got the img file to stick. Now for some reason when the phone is booted my computer doesn't recognize device so can't push any commands.

I've compiled a new m launcher APK separately and need root to make changes to try and push the actual Microsoft launcher into device. I haven't done Android work for a while and may have forgotten a few things lol. Any help is appreciated. Thanks.

Did you enable developer mode in settings?

 

[PROTOCOL]

Did you enable developer mode in settings?

Sure did. It might just be cause I'm so rusty but can't get su (showing permission denied) and losing comms between computer and device while it's booted.

 

[jgoorn]

Sure did. It might just be cause I'm so rusty but can't get su (showing permission denied) and losing comms between computer and device while it's booted.

Lack of su permissions when you are running adb shell is because root is not granted to adb shell via magisk superuser tab.

 

[arcanemagick]

Thanks for this, op! A couple observations from going through the process...

1. I made my own magisk_patched.img and its checksum didn't match the file you provided. I'm maybe using a different version of Magisk (v20.4), or MS updated the recovery image (2020.812.86)? Anyway, just pointing it out in case some version mismatch might cause trouble for others.

2. For PART 3, I was concerned about the possibility of leaving the boot partitions writable to all, so I tried it without the chmod (since the partitions are already writable by root which we get through su). This is all I did:

adb shell
su
dd of=/dev/block/by-name/boot_b if=/sdcard/magisk_patched.img
dd of=/dev/block/by-name/boot_a if=/sdcard/magisk_patched.img

No problems so far, so thanks again for putting this together.

 

[Perseu5]

Thanks for this, op! A couple observations from going through the process...

1. I made my own magisk_patched.img and its checksum didn't match the file you provided. I'm maybe using a different version of Magisk (v20.4), or MS updated the recovery image (2020.812.86)? Anyway, just pointing it out in case some version mismatch might cause trouble for others.

2. For PART 3, I was concerned about the possibility of leaving the boot partitions writable to all, so I tried it without the chmod (since the partitions are already writable by root which we get through su). This is all I did:


No problems so far, so thanks again for putting this together.

Happy to contribute! Things have been crazy lately, but I hope to have a completed app that will streamline everything within the next week or so. Additional optional modifications will be added as well.
Thank you for letting me know about this and helping the community!

 

[josh_zombie]

No-go for me. I stupidly relocked bootloader and can't unlock again (Allow OEM unlock not toggled in developer options). Can't flash boot image in fastboot/can't get to ADB to restore factory image/can't boot into recovery. Afraid I have no choice but to send in for replacement at this point. Lessons learned.

I can, however, get to Qualcomm EDL mode and my PC recognizes the Duo over USB. But from what I understand (not much with Qualcomm EDL) these Qualcomm EDL tools don't seem to be optimized for a UFS file system. Let alone being able to find the correct files for a reflash... that's a whole different issue I'm not sure is worth pursuing given how new Duo is and my lack of understanding exactly how it works.

In case anyone else lands themselves a hard brick, thought I'd share that Microsoft honored the standard warranty and replaced my Duo with a brand new (not refurb) device, no cost or questions asked. Never had to speak to anyone, only filled out the online service request. I even kept the charger & bumper (per their return instructions) and got new ones in the box. Whole process took about a week. Overall, very pleased with Microsoft Support for truly putting this customer first.

 

[daicaothu]

Anyone knows how to remove the warning screen each time the phone reboot?

Thanks

 

[panzercool]

In case anyone else lands themselves a hard brick, thought I'd share that Microsoft honored the standard warranty and replaced my Duo with a brand new (not refurb) device, no cost or questions asked. Never had to speak to anyone, only filled out the online service request. I even kept the charger & bumper (per their return instructions) and got new ones in the box. Whole process took about a week. Overall, very pleased with Microsoft Support for truly putting this customer first.

Good to know! Thank you!

My bricked device reached Microsoft today! No questions asked as well! Pleased with MSFT!!