Unlocking Bootloader/ Magisk Attempt

[loloudoudara]

Same here. Had perfectly fine working root access and I patched the boot img from the newest recovery from MS's website. Reverted back to stock boot and did OTA. Every time I attempt to boot the patched img it just hangs at the MS logo. Regular boot works just fine. I'm bummed that I lost root access now.

Same exact problem. I've also tried the latest beta Magisk from Git with the Canary channels to root but it didn't work.

 

[loloudoudara]

Finally got root working on the latest firmware 1211_85. The trick is to use MagiskManager 8.0.3 and Magisk 20.4. Easiest way I found to do so was using a custom channel that points to the correct Git commit from the developper of Magisk.

Custom Channel: https://raw.githubusercontent.com/L...5f596dc2a351270120b31b665fb561294/stable.json

In case you don't want to go through the hassle, attached is the patched boot image for my Unlocked Duo.

boot_custom_channel_1211_85_magisk_803_204.img

drive.google.com

 

[deletemyaccount]

Finally got root working on the latest firmware 1211_85. The trick is to use MagiskManager 8.0.3 and Magisk 20.4. Easiest way I found to do so was using a custom channel that points to the correct Git commit from the developper of Magisk.

Custom Channel: https://raw.githubusercontent.com/L...5f596dc2a351270120b31b665fb561294/stable.json

In case you don't want to go through the hassle, attached is the patched boot image for my Unlocked Duo.

boot_custom_channel_1211_85_magisk_803_204.img

drive.google.com

Thanks so much for this, was running into the issue and had no idea what was going on.

 

[kekoslice]

Finally got root working on the latest firmware 1211_85. The trick is to use MagiskManager 8.0.3 and Magisk 20.4. Easiest way I found to do so was using a custom channel that points to the correct Git commit from the developper of Magisk.

Custom Channel: https://raw.githubusercontent.com/L...5f596dc2a351270120b31b665fb561294/stable.json

In case you don't want to go through the hassle, attached is the patched boot image for my Unlocked Duo.

boot_custom_channel_1211_85_magisk_803_204.img

drive.google.com

Thanks for this! I usually don't login to comment on stuff like this but I wanted to let you know that you helped me out. Trying to keep the Duo root community alive!

How did you figure this out though? You might not always be around to help us out lol.

 

[loloudoudara]

Thanks for this! I usually don't login to comment on stuff like this but I wanted to let you know that you helped me out. Trying to keep the Duo root community alive!

How did you figure this out though? You might not always be around to help us out lol.

Honestly trial and error. And the fact that I'm desperate for ad blocking! I'm a software engineer and a linux kernel developer so I do have the basics for Android development.

 

[LocBox]

Honestly trial and error. And the fact that I'm desperate for ad blocking! I'm a software engineer and a linux kernel developer so I do have the basics for Android development.

In trying this method, I can't install any modules anymore. It only shows the ones already installed, then it's blank under the online section.

 

[loloudoudara]

In trying this method, I can't install any modules anymore. It only shows the ones already installed, then it's blank under the online section.

Bunch of questions coming your way

Did these modules that you're trying to instaIl work on the surface duo with the previous rooted firmware? What's an example? What error are you getting? Have you tried deleting and reinstalling all modules?

I can't speak for other modules working with Android 10 and the Surface Duo, but I have the Systemless Hosts and Boot Animation modules installed.

 

[loloudoudara]

I'm happy to report that the latest firmware 2021_115_52 is running rooted on the unlocked surface duo.

Here is the the link to the magisk patched boot image: https://drive.google.com/file/d/1JQOB94_ig7RYhUVhIAqKu9I5Xr95kcuN/view?usp=sharing

 

[NTchrist]

I'm happy to report that the latest firmware 2021_115_52 is running rooted on the unlocked surface duo.

Here is the the link to the magisk patched boot image: https://drive.google.com/file/d/1JQOB94_ig7RYhUVhIAqKu9I5Xr95kcuN/view?usp=sharing

custom (old 20.4) channel? stable channel? or beta channel?

 

[NTchrist]

judging by the name "boot_custom_channel_2021_115_52_magisk_803_204" I'm going to answer my own question and guess custom channel is still required lol.

what is your strategy for updates? are you wiping and reinstalling? booting from a pc, flashing the stock boot images back and then doing an OTA, then re-running the root process? something else?

 

[loloudoudara]

judging by the name "boot_custom_channel_2021_115_52_magisk_803_204" I'm going to answer my own question and guess custom channel is still required lol.

what is your strategy for updates? are you wiping and reinstalling? booting from a pc, flashing the stock boot images back and then doing an OTA, then re-running the root process? something else?

Strategy: not wiping and reinstalling, but "booting from a pc, flashing the stock boot images back and then doing an OTA, then re-running the root process"

Here are the steps I use:

PART I: Update OTA

1. Place ORIGINAL boot.img in the root of Internal SD:

adb push boot.img /sdcard/

2. Make it permanent (you will lose root after this step so backup patched boot.img):

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

3. Restart phone:

adb reboot

4. Run OTA update

5. Restart when prompted


PART II: Root

1. Download the latest image off of Microsoft's site: https://support.microsoft.com/en-us/surfacerecoveryimage

2. Extract the boot.img out of payload.bin.

3. Place boot.img in the root of Internal SD:

adb push boot.img /sdcard/

4. Download the latest Magisk Manager. Open and hit the top install button.

The trick is to use MagiskManager 8.0.3 and Magisk 20.4.

Custom Channel: https://raw.githubusercontent.com/L...5f596dc2a351270120b31b665fb561294/stable.json

Select patch a file, and select your boot.img. Patch it. It should show up in your Downloads folder renamed magisk_patched_*.img. Remember the name.

5. Move patched file to /sdcard/

adb shell
mv /sdcard/Download/magisk_patched_*.img /sdcard/magisk_patched.img

6. Copy magisk_patched.img to PC
adb pull /sdcard/magisk_patched.img .

7. Fast boot magisk_patched.img:

adb reboot bootloader
fastboot boot magisk_patched.img

8. Make magisk_patched.img permanent:

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

9. Restart/ Done

 

[NTchrist]

Strategy: not wiping and reinstalling, but "booting from a pc, flashing the stock boot images back and then doing an OTA, then re-running the root process"

Here are the steps I use:

PART I: Update OTA

1. Place ORIGINAL boot.img in the root of Internal SD:

adb push boot.img /sdcard/

2. Make it permanent (you will lose root after this step so backup patched boot.img):

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

3. Restart phone:

adb reboot

4. Run OTA update

5. Restart when prompted


PART II: Root

1. Download the latest image off of Microsoft's site: https://support.microsoft.com/en-us/surfacerecoveryimage

2. Extract the boot.img out of payload.bin.

3. Place boot.img in the root of Internal SD:

adb push boot.img /sdcard/

4. Download the latest Magisk Manager. Open and hit the top install button.

The trick is to use MagiskManager 8.0.3 and Magisk 20.4.

Custom Channel: https://raw.githubusercontent.com/L...5f596dc2a351270120b31b665fb561294/stable.json

Select patch a file, and select your boot.img. Patch it. It should show up in your Downloads folder renamed magisk_patched_*.img. Remember the name.

5. Move patched file to /sdcard/

adb shell
mv /sdcard/Download/magisk_patched_*.img /sdcard/magisk_patched.img

6. Copy magisk_patched.img to PC
adb pull /sdcard/magisk_patched.img .

7. Fast boot magisk_patched.img:

adb reboot bootloader
fastboot boot magisk_patched.img

8. Make magisk_patched.img permanent:

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

9. Restart/ Done

Yep that's exactly what I ended up doing, thanks for the sanity check! That said, I used the current version of MagiskManager, just the custom repo for the actual boot image patching. Not sure if that will matter down the line.

 

[dj.est86]

Do you mind sending the link for actual img file of the magisk_patched boot img?

thank you in advance

 

[LocBox]

Is there any chance we can get Canary builds to work again?

 

[kirschdog1]

Can anyone help me I am on March unlocked and cant root. Can someone provide March patched image and also help me root my device?I tried multiple times following the instructions to no avail. I'm desperate

 

[NTchrist]

Can anyone help me I am on March unlocked and cant root. Can someone provide March patched image and also help me root my device?I tried multiple times following the instructions to no avail. I'm desperate

ATT Unlocked or Factory Unlocked?

 

[kirschdog1]

ATT Unlocked or Factory Unlocked?

Factory Unlocked

 

[kirschdog1]

delete

 

[NTchrist]

Factory Unlocked

I'm running the process right now on march to update mine, I'll pass on the info once I have it working

 

[kirschdog1]

I always get stuck after patching and booting the patched boot image it always hangs on windows icon and then I have to press power and volume to get it to boot.