[RECOVERY][12L/11] Unofficial TWRP for the Microsoft Surface Duo
- Thread starter JengaMasterG
- Start date
-
- Tags
- microsoft surface duo twrp 11
Unfortunately, no. The Duo 2 uses a newer chipset and a different kernel. If there's development interest the guide to build TWRP should be mostly the same between the two devices. No guarentees though!
Oh I'm not that handy. I did unlock bl, patched magisk.img,and safety net good
Try rebooting back into bootloader, disconnect and connect the device, and make sure you have the latest platform tools from the android website.
If none of those steps work for you, I'll try to upload another image. Right now, the image should work fine for your device.
If none of those steps work for you, I'll try to upload another image. Right now, the image should work fine for your device.
As far as I'm aware:
After releasing android 12L for the duo, Microsoft stopped making different build versions. This recovery should work regardless of which duo 1 you have.
For the first version, now I was able to open the Bootloader, but the TWRP file causes the device and the Patched file to stop touching as well?
Found someone who may be able to assist us on this project. I sent you a message whenever you have time.
Supposedly he knows how to get touch, adb and decryption working
Supposedly he knows how to get touch, adb and decryption working
This is great! I just received my AT&T locked device, (which both Microsoft and AT&T refused to unlock because it was never activated on AT&T), but will be very keen to have TWRP once I manage to unlock the phone.
In case it was missed on the previous page, as I see its still marked as "not working"
Sideloading does work on android 11. Tested and confirmed with magisk.zip
Sideloading does work on android 11. Tested and confirmed with magisk.zip
After I learned how to do the root safely, and now there is a problem, the toch does not work in the device. I need a way to return its original version for the device to work. Where can I find it, knowing that the one on the Microsoft site did not work
Sorry, but not on this thread. It sounds like the boot image is the wrong one. Boot image version needs to match software version. There's a root guide here on xda for this topic.
Jenga is correct regarding Microsoft's differing Bootloader Build numbers, but from my experience it doesn't matter with Magisk & stock recovery. My current Bootloader has a different build than my system software build, however the boot image in the latest release is the same Boot.img as the previous releases. The Bootloader version installed is 2022.815.527, while the fresh system build is 2022.827.21. And I have no issues period when I patch my own Boot.img using the same fastboot steps in the rooting guide provided here on XDA somewhere. And afaik the Touch issues are from not using a stock device recovery but opting for alternative recoveries. HTH.
Top Liked Posts
-
There are no posts matching your filters.
-
8
TWRP Disclaimer
Code:* We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you.
After many months struggling with the source code, TWRP finally comes to the Surface Duo! Do not flash this boot image! TWRP will NOT boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
Special thanks to: @none24 Captain Throwback (TWRP team)
Requirements for Booting:
- Unlocked Bootloader
- Latest Platform Tools
- TWRP image
How to Boot:
With device connected to your PC and turned ON:
- adb devices
- adb reboot bootloader
- fastboot boot boot_TWRP.img
And with that, you're booted into TWRP!
What is working:
ADB Shell
ADB Push
MTP
Mouse Navigation
You tell me!
What is not working:
Touch Screen
ADB Sideload
You tell me!
Firmwares Tested:
- 2021.1019.24 GEN
- 2022.215.137 GEN
- 2022.418.56 GEN
- 2022.817.13 GEN (Android 12L)
Changelog:
Changelog 0.1.1
- Updated TWRP for Android 12L November Update (2022.817.13)
Changelog 0.1.0
- Data can now be Decrypted, but with no passcode set
- Updated Kernel and other binaries to the June update (2022.418.25)
Version 0.0.4
- Data can now be mounted, but only after a factory reset
- ADB push and Zip flashing is confirmed working (See Post #19)
Firmwares Tested:
- 2022.215.137
- System, Vendor, and Product directories can be mounted as read-only
- MTP enabled, but can't receive data
- TWRP Crypto Scripts added
Firmwares Tested:
- 2021.1019.24 GEN
- 2022.115.10 GEN
- Root directory found, but cannot find system_root, vendor, and product directories
- Internal Storage can now me mounted
- ADB push to sdcard tested and works
- Initial Release
Download via Google Drive
3TWRP UPDATE
-------------------------------------------------------
Version 0.0.4
Data can now be mounted, but only after a factory reset
ADB push and Zip flashing is confirmed working (See Magisk Attachment)
2
It sounds like Android 10 would need a different TWRP built for it if the system and vendor can't be mounted. Unfortunately, I can't build it for Android 10 since I am focused on to supporting 12L, enabling touch, and exploring other OS options.1TWRP Update
-------------------------------------
Version 0.0.2
- Root directory found, but cannot find system_root, vendor, and product directories
- Internal Storage can now me mounted
- ADB push to sdcard tested and works
