Unlocking Bootloader/ Magisk Attempt

[LocBox]

Here is the the link to the magisk patched latest 2021_314_91 boot image for the unlocked Duo: https://drive.google.com/file/d/1MPkiy__HvBhnOKAGqgq9yY-sHGKNYwFe/view?usp=sharing

when checking system updates, does yours read Feb. 5, 2020 too for Android sec. patch?

 

[loloudoudara]

when checking system updates, does yours read Feb. 5, 2020 too for Android sec. patch?:

It reads "android security update: April 5, 2021"

 

[LocBox]

It reads "android security update: April 5, 2021.

It only shows the correct build for me under About, but when I check system update it reads Feb 5, 2020. It's done this a few times now since I've been rooting this phone.

 

[loloudoudara]

It only shows the correct build for me under About, but when I check system update it reads Feb 5, 2020. It's done this a few times now since I've been rooting this phone.

Does the OS return the correct security update without root? Meaning with the original boot.img

 

[LocBox]

Does the OS return the correct security update without root? Meaning with the original boot.img

it's correct now, but when flashing the latest riru core and edxposed, quickstep launcher crashes consistently along with system settings. it forces me to factory reset.

 

[Rai3]

Did you get this figured out? If not send me a PM, I can help you, I ran into the same issue.

Hi renegadeone8
My problem has not been solved.
What is PM?
Thank you for your kindness.

 

[loloudoudara]

it's correct now, but when flashing the latest riru core and edxposed, quickstep launcher crashes consistently along with system settings. it forces me to factory reset.

I'm sorry, I haven't really played with Riru and EDXposed. It looks like it might be worth posting on the official EDXposed thread.

 

[LocBox]

I'm sorry, I haven't really played with Riru and EDXposed. It looks like it might be worth posting on the official EDXposed thread.

it was the anywebview tweak...avoid for now as it causes crashes with lsposed/edxposed.

 

[renegadeone8]

Hi renegadeone8
My problem has not been solved.
What is PM?
Thank you for your kindness.

Someone else posted a guide here just FYI on how to do the update with the original post. He described the process better than I could while I stumbled through.

 

[Rai3]

Someone else posted a guide here just FYI on how to do the update with the original post. He described the process better than I could while I stumbled through.

If you don't mind, could you tell me where the post is?

 

[LocBox]

If you don't mind, could you tell me where the post is?

https://xdaforums.com/t/root-guide-updated.4266095/

 

[Rai3]

Thanks for the link.
However, I can't use this technique because I have lost my original boot image.
I think I can disassemble the new recovery image with payload_dumper and write all the img with dd, but I haven't tried it because I'm afraid of breaking it.
I do not understand android very well.

 

[NTchrist]

Thanks for the link.
However, I can't use this technique because I have lost my original boot image.
I think I can disassemble the new recovery image with payload_dumper and write all the img with dd, but I haven't tried it because I'm afraid of breaking it.
I do not understand android very well.

which boot image do you need? I have the last few original images.

Also, booting from the original boot image via fastboot should be a safe process even if you use the wrong one. Worst case is the system bootloops or crashes and simply rebooting the phone from local storage (power off / power on using hardware button) will boot from whatever is presumably working now.

 

[Rai3]

which boot image do you need? I have the last few original images.

Also, booting from the original boot image via fastboot should be a safe process even if you use the wrong one. Worst case is the system bootloops or crashes and simply rebooting the phone from local storage (power off / power on using hardware button) will boot from whatever is presumably working now.

Requires bootimg for 2020.1211.86.
I understand booting with fastboot.
The problem is that it is impossible to recover
There is no OTA update method.

 

[NTchrist]

Requires bootimg for 2020.1211.86.
I understand booting with fastboot.
The problem is that it is impossible to recover
There is no OTA update method.

sorry I don't have one that old. your best bet would just be to back everything up with titanium or something and do a wipe/update/restore

 

[Rai3]

sorry I don't have one that old. your best bet would just be to back everything up with titanium or something and do a wipe/update/restore

Thank you for your kindness.
I made a mistake and overwrote the original img, leaving only the magisk img.
I didn't understand that AT & T img and MS img are different.
Restore will not start with the wrong img.
Even replace it with a new virsion bootimg, restore will not start.
Since it is rewritten with magisk img, it will not be restored even if wiped.
Is my mistake

 

[NTchrist]

Thank you for your kindness.
I made a mistake and overwrote the original img, leaving only the magisk img.
I didn't understand that AT & T img and MS img are different.
Restore will not start with the wrong img.
Even replace it with a new virsion bootimg, restore will not start.
Since it is rewritten with magisk img, it will not be restored even if wiped.
Is my mistake

you should be able to flash everything from the current image with fastboot no matter what the state of your device.

 

[Rai3]

you should be able to flash everything from the current image with fastboot no matter what the state of your device.

That's the point I don't understand.
There are 24 imgs,
$ fastboot flash <partition> <filename>
<partition> doesn't understand what to show.
Please let me know if possible.

 

[NTchrist]

That's the point I don't understand.
There are 24 imgs,
$ fastboot flash <partition> <filename>
<partition> doesn't understand what to show.
Please let me know if possible.

1. Unplug the USB cable from your Surface Duo
2. turn it off
3. press and hold the Volume down button, then press and release the Power button. Continue to hold down the Volume down button until a menu appears, then release the Volume down button.
4. select Recovery mode using the volume buttons
5. Press and release the power button to select Recovery mode
6. Select Apply update from ADB, using the volume buttons, then press and release the Power button
7. Plug the USB cable into your computer
8. .\adb sideload surface-recovery-image.zip

This will install a fresh factory image. I'm not 100% sure on whether or not it will wipe your data partition, I think it will so make sure you back up your data first.

 

[Rai3]

1. Unplug the USB cable from your Surface Duo
2. turn it off
3. press and hold the Volume down button, then press and release the Power button. Continue to hold down the Volume down button until a menu appears, then release the Volume down button.
4. select Recovery mode using the volume buttons
5. Press and release the power button to select Recovery mode
6. Select Apply update from ADB, using the volume buttons, then press and release the Power button
7. Plug the USB cable into your computer
8. .\adb sideload surface-recovery-image.zip

This will install a fresh factory image. I'm not 100% sure on whether or not it will wipe your data partition, I think it will so make sure you back up your data first.

I can't use recovery after applying the wrong boot.img.
When I select recovery from the boot loader, it boots to normal.
Using the latest correct boot.img does not change the situation. (In this case, "no command" screen).

My device is giving me a "Your device is corrupt. It can't be trusted and may not work properly." error on startup.
The data seems to be inconsistent.
For this reason I believe I need to do a fastboot restore.