Unlocking Bootloader/ Magisk Attempt

loloudoudara

Member
Feb 29, 2012
36
12
28
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

Member
Feb 29, 2012
36
12
28
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.

 
Last edited:
  • Like
Reactions: Rai3 and DaemonDant
Nov 13, 2010
15
1
23
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.

Thanks so much for this, was running into the issue and had no idea what was going on.
 
  • Like
Reactions: loloudoudara

kekoslice

Member
Feb 7, 2016
12
4
23
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.

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.
 
  • Like
Reactions: loloudoudara

loloudoudara

Member
Feb 29, 2012
36
12
28
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

Senior Member
Aug 16, 2009
109
13
38
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

Member
Feb 29, 2012
36
12
28
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.
 
Last edited:

NTchrist

Member
May 10, 2011
25
16
23
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?
 
Last edited:

loloudoudara

Member
Feb 29, 2012
36
12
28
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

Member
May 10, 2011
25
16
23
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.