[RECOVERY][12L/11] Unofficial TWRP for the Microsoft Surface Duo - Microsoft Surface Duo ROMs, Kernels, Recoveries, &

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)
If you still are currently on android 11, please remain using version 0.1.0 of TWRP!
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)
Spoiler: Changelog History
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
Version 0.0.3
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
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
Version 0.0.1
Initial Release
Download via Google Drive​

*cracks knuckles* let's see..

JengaMasterG said:
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! It is not tested to boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
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
You tell me!
What is not working:​Touch Screen
ADB Sideload
You tell me!
Versions Tested:​
2022.115.10 GEN
Click to expand...
Click to collapse
Hey where's the actual file?

LocBox said:
Hey where's the actual file?
Click to expand...
Click to collapse
It would help if XDA told me it didn't upload it lol. I added a link to GDrive. It should be available now!

TWRP 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
JengaMasterG said:
Download via Google Drive
Click to expand...
Click to collapse

JengaMasterG said:
Thank You!!!
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! It is not tested to boot directly into the system! Again: this is a tethered boot and should not be flashed/replacing the boot image installed on your device.
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
USB OTG
You tell me!
What is not working:​Touch Screen
ADB Sideload
MTP Storage Mode
You tell me!
Firmwares Tested:​
2021.1019.24 GEN
2022.115.10 GEN
Changelog:​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
Spoiler: Changelog History
Version 0.0.1
Initial Release
Download via Google Drive​
Click to expand...
Click to collapse

how can i get past the System read only screen?

Also, now with this being achieved the likely ROMs to use would be the Treble A/Bs over in the Treble ROM section on XDA. CHAOS should run for example

LocBox said:
how can i get past the System read only screen?
Click to expand...
Click to collapse
You will need to plug a mouse into the USB C port for now. The touch isn’t working and I’m researching how to get that fixed.

LocBox said:
Also, now with this being achieved the likely ROMs to use would be the Treble A/Bs over in the Treble ROM section on XDA. CHAOS should run for example
Click to expand...
Click to collapse
Probably! The prebuilt kernel is available and we can create custom ROMs already. We just need a fully working twrp. If you know anyone who has experience in this let me know!

well ill be damned somebody did it. now if we could only get some custom roms
I appreciate you!

Has there been anymore progress ? and if not how can we help?

none24 said:
Has there been anymore progress ? and if not how can we help?
Click to expand...
Click to collapse
I'm still trying to get touch working and resolve the issue with decrypting the data partition. If you know someone with TWRP experience or have made TWRP before you are welcome to help compile it!

JengaMasterG said:
I'm still trying to get touch working and resolve the issue with decrypting the data partition. If you know someone with TWRP experience or have made TWRP before you are welcome to help compile it!
Click to expand...
Click to collapse
i've had experience decrypting it using Linux but ive never compiled it. If u think thats helpful I can reinstall linux and get my hands dirty-- just tell me what exactly you need me to do or figure out.
I also put out a help thread in android general.

none24 said:
i've had experience decrypting it using Linux but ive never compiled it. If u think thats helpful I can reinstall linux and get my hands dirty-- just tell me what exactly you need me to do or figure out.
I also put out a help thread in android general.
Click to expand...
Click to collapse
I'll try android general. I'm on the Zulip chat for official TWRP support and they're not exactly helpful or free to assist.
If you have experience decrypting that would be a major step forward! Basically data is mapped correctly in the fstab, but TWRP can't decrypt it. I noticed too that none of the files needed to be copied during the build process doesn't copy for some reason so the decrypting script can't find the rc file it needs to modify

JengaMasterG said:
I'll try android general. I'm on the Zulip chat for official TWRP support and they're not exactly helpful or free to assist.
If you have experience decrypting that would be a major step forward! Basically data is mapped correctly in the fstab, but TWRP can't decrypt it. I noticed too that none of the files needed to be copied during the build process doesn't copy for some reason so the decrypting script can't find the rc file it needs to modify
Click to expand...
Click to collapse
and you've tried no-verity-opt-encrypt ?
Whats strange for me is TWRP asks for a password to decrypt data. I've tried everything to my knowledge to get passed it but i cant.
I also cant load any zips to flash the no-verity-opt-encrypt.zip
If you have discord or telegram I can stay in touch quicker

none24 said:
and you've tried no-verity-opt-encrypt ?
Whats strange for me is TWRP asks for a password to decrypt data. I've tried everything to my knowledge to get passed it but i cant.
I also cant load any zips to flash the no-verity-opt-encrypt.zip
If you have discord or telegram I can stay in touch quicker
Click to expand...
Click to collapse
I haven't tried that. I can send you my discord. I'm normally on that

A 0.0.3 is in the works. I will update this post and the main post when it's ready.
A quick changelog:
MTP is on, but nothing can be transferred
System and Vendor directories can be mounted as read-only
Added Decryption TWRP modules (Data (SDCard) can't be mounted or decrypted yet)
Device Tree supports OrangeFox Recovery, currently an ALPHA build (another thread to come later)
EDIT: Main Post updated with Changelog. 0.0.3 image has been uploaded to GDrive

TWRP 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)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​

Thanks for the continued work on this!
I have had it sitting in my drawer until an easier way to root came about.
Has anyone who used this to root with magisk had an OTA fail?

Related

[CLOSED][RECOVERY][dandelion][v3.0.0]Pitch Black Recovery[31/12/2020]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're 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.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: dandelion
Maintainer/Authors build: PBRP Team
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
From previous version or other recovery
Download the PitchBlack zip to your device
Reboot to your current custom recovery
Flash the PitchBlack zip
The device will automatically reboot into PitchBlack Recovery after installation
Enjoy
From PC
Download PitchBlack Recovery flashable zip from bellow
Extract the PBRP zip
Goto fastboot mode in your device
Flash the recovery.img by
Code:
fastboot flash recovery recovery.img
Flash vbmeta (get from fastboot rom)
Code:
fastboot --disable-verification flash vbmeta vbmeta.img
Boot into PBRP by
Code:
fastboot boot recovery.img
or
Code:
fastboot oem reboot-recovery
Boot into PBRP
Copy the zip to internal storage
Flash it
Enjoy
Bugs
- fastbootd
- sideload
Device Tree:- https://github.com/PitchBlackRecoveryProject/android_device_xiaomi_dandelion-pbrp
Downloads
Dropped Support
You Can Build Amd Fix Bugs As Device Tree I have shared
cant wait to try! thanks for your work mate!
touch screen not working plz help me...
dreadmachine said:
touch screen not working plz help me...
Click to expand...
Click to collapse
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR
Mrinalsaha said:
it is working for me
check if touch is working in this https://gofile.io/d/UWjWjR
Click to expand...
Click to collapse
sadly wont boot, i tried flashing it, but its not booting to it
dreadmachine said:
sadly wont boot, i tried flashing it, but its not booting to it
Click to expand...
Click to collapse
it boot but the screen stays black
press power button 2 times to see it when it is in black screen
i did and it worked, but.... when i install system.img of rom, it says no os on system.. sure you want to reboot?
everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either
Rediancool said:
everything functions correctly(mtp,brightness,touch,decryption) but couldn't root with magisk(both with recovery provided one and the official one) it flashes, but when i turn on device and open the magisk manager app, it shows no root. and tried flashing gsi (to super partition) messed up the partition table. didn't try backup. couldn't find a way to wipe system, there was no system entry. couldn't mount it either
Click to expand...
Click to collapse
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases
Mrinalsaha said:
flashing magisk to get root works but you'll have to use the latest 21.2 version
I have tried to flash all the magisk version but only 21.2 gave me root
download from here https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
thanks man it worked. were you successful in flashing gsi?
Rediancool said:
thanks man it worked. were you successful in flashing gsi?
Click to expand...
Click to collapse
how are you suggesting that I would flash gsi ?
Mrinalsaha said:
how are you suggesting that I would flash gsi ?
Click to expand...
Click to collapse
i meant did you flash gsi with this
Is there any way to flash arm64 gsi in redmi 9a? because I want to run google camera which works in 64bit
Rediancool said:
i meant did you flash gsi with this
Click to expand...
Click to collapse
no it cannot be flashed
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
You can't modify system in recovery because of dynamic partition
[/QUOTE]
Rediancool said:
i can not edit system files from any root explorer
or move files in root with pbrp file manager. any suggestions?
several forum post suggested that editing system files is hard in android 10
any way to do that?
(and in magisk log it says that unlock failed with error 13 permission denied)
Click to expand...
Click to collapse
Try this way
Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?
t's sad, but it doesn't feel pressed . the touchscreen doesn't work(
wanlus said:
Wooww!! It worked fine for me... But just to install recovery. I can't root with magisk. No with 21.2 or 21.4 versions, cause the phone goes into bootloop.
No way with supersu.
I'm in MIUI 12.0.10.0 QCDEUXM
Is there anybody who can help me, please?
Click to expand...
Click to collapse
you have to flash vbmeta to avoid bootloop
fastboot flash vbmeta vbmeta.img
Gofile - Free Unlimited File Sharing and Storage
Gofile is a free, secure file sharing and storage platform. With unlimited bandwidth and storage, you can easily store and share files of any type without any limits. Our advanced features, such as CDN support and password protection, make Gofile the ideal choice for individuals and businesses...
gofile.io

[ROM][UNOFFICIAL][11.0] LineageOS 18.1 for Lenovo Tab 4 8 Plus (TB8704F/X/N)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS​
Code:
/*
* I'm 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 the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working:
WiFi
Bluetooth
Audio
Camera
Fingerprint
SELinux enforcing
Encryption
Torchlight
What's not working:
FM radio, at least in the stock app
Wireless display
SIM card not detected on LTE model
Downloads:
TWRP: XDA thread
ROM (latest version): GitHub
Older versions available on releases page.
Installation instructions:
To install you should be running stock firmware, you can restore using the Lenovo Rescue and Smart Assistant (LMSA) tool on a PC, then follow the instructions in the app to rescue the device. Make sure to unlock the bootloader as well.
Now grab a copy of TWRP recovery from here. Install fastboot and adb on your PC by following this tutorial on XDA.
Boot your device into fastboot mode (power + volume down). You should know when you are in fastboot mode as it will show on the screen.
Open up the terminal or command prompt and run:
Code:
fastboot flash recovery <path to twrp.img>
Now turn off your device by pressing power until the screen is black, then boot into recovery (power + volume up).
TWRP should boot up. DO NOT ERASE SYSTEM, OTHERWISE YOUR DEVICE WILL HANG ON THE LINEAGE LOGO. Go to Advanced, tap ADB sideload, then run the following on your PC.
Code:
adb sideload <path to rom.zip>
Once it's finished sideloading, install any additional packages (eg GAPPS) and then go to Wipe and swipe factory reset. Now reboot.
It will take a couple of minutes to load and then you should see setup. You can now setup your device. Enjoy LineageOS 18.1 and Android 11 on your Lenovo Tab 4 8 Plus!
Credits:
lenovo-devs for the original, Android 10 device tree.
LumenReaper for updating the kernel to work with Android 11.
ChasTechProjects for updating the device tree and vendors for Android 11.
Sources:
Device tree: https://github.com/ChasTechProjects/android_device_lenovo_TB8704
Kernel: https://github.com/ChasTechProjects/android_kernel_lenovo_msm8953
Vendor: https://github.com/ChasTechProjects/proprietary_vendor_lenovo
Changelog:
27/10/2021
Initial release
October 2021 security patch
14/04/2022
April 2022 security patch
Сим карта не определена в планшетах с этой прошивкой
Леший83 said:
SIM card not detected in tablets with this firmware
Click to expand...
Click to collapse
Thanks for letting me know, I'll look further into it!
ChasTechProjects said:
Thanks for letting me know, I'll look further into it!
Click to expand...
Click to collapse
confirmed SIM card does not work
Hello,
i am on Lineage 17.1 and i would like to Update to this new Android 11 Version. TWRP 3.4.0-0 is also installed.
Can i just wipe all stuff in TWRP, flash new zip and Setup Tablet again?
ronnybonx said:
Hello,
i am on Lineage 17.1 and i would like to Update to this new Android 11 Version. TWRP 3.4.0-0 is also installed.
Can i just wipe all stuff in TWRP, flash new zip and Setup Tablet again?
Click to expand...
Click to collapse
Hello ronnybonx,
I was in the same configuration before trying this Android11.
Yes, I could boot up after wiping those from TWRP:
Dalvik
Data
Internal Storage
Cache
The ZIP is for sideloading; cannot install from TWRP.
Wiping internal storage maynot be necessary so it is worth to try.
Awesome, I might upgrade from Highwaystar's A10-based ROM. Thank you!
Thank you for your efforts!
Thank you - not having any luck - flashed to stock with Lenovo recovery tool. Bootloader is unlocked
fastboot boot twrp-3.2.3-0-tb_8704x.img
It's not able to mount data
I tried disabling security pin as well. Since data is encrypted its not working.
Failed to mount '/data' (No such process)
Any suggestions please?
FoRealz said:
Thank you - not having any luck - flashed to stock with Lenovo recovery tool. Bootloader is unlocked
fastboot boot twrp-3.2.3-0-tb_8704x.img
It's not able to mount data
I tried disabling security pin as well. Since data is encrypted its not working.
Failed to mount '/data' (No such process)
Any suggestions please?
Click to expand...
Click to collapse
Fastbooting and running this solved the mounting the data partition issue...
Code:
fastboot format:ext4 userdata
But when I attempted to sideload, it never progressed pass 0% hmmm
adb sideload lineage-18.1-20211027-UNOFFICIAL-TB8704.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'lineage-18.1-20211027-UNOFFICIAL-TB8704.zip' (~0%) ^C
FoRealz said:
Fastbooting and running this solved the mounting the data partition issue...
Code:
fastboot format:ext4 userdata
But when I attempted to sideload, it never progressed pass 0% hmmm
adb sideload lineage-18.1-20211027-UNOFFICIAL-TB8704.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'lineage-18.1-20211027-UNOFFICIAL-TB8704.zip' (~0%) ^C
Click to expand...
Click to collapse
Did you tried with twrp 3.4.0-0? ADB Sideload enabled in TWRP. With the command ADB devices, you can check if your Tablet is connected successful.
FoRealz said:
Fastbooting and running this solved the mounting the data partition issue...
Code:
fastboot format:ext4 userdata
But when I attempted to sideload, it never progressed pass 0% hmmm
adb sideload lineage-18.1-20211027-UNOFFICIAL-TB8704.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
serving: 'lineage-18.1-20211027-UNOFFICIAL-TB8704.zip' (~0%) ^C
Click to expand...
Click to collapse
You should be using TWRP 3.4.0.0 for these versions of LineageOS. Using older versions is not a good idea and even if it works, it probably won't work well.
Are you able to wipe the data partition within TWRP?
ronnybonx said:
Did you tried with twrp 3.4.0-0? ADB Sideload enabled in TWRP. With the command ADB devices, you can check if your Tablet is connected successful.
Click to expand...
Click to collapse
K14_Deploy said:
You should be using TWRP 3.4.0.0 for these versions of LineageOS. Using older versions is not a good idea and even if it works, it probably won't work well.
Are you able to wipe the data partition within TWRP?
Click to expand...
Click to collapse
Thank you both - I tried the newer version as you mentioned and same issue.
Here's what I see:
The target line stands out to me since it mentioned TB-8704X ... I have the TB-8704F
FoRealz said:
Thank you both - I tried the newer version as you mentioned and same issue.
Here's what I see:
The target line stands out to me since it mentioned TB-8704X ... I have the TB-8704F
Click to expand...
Click to collapse
Have you tried a different USB-C cable or computer? That could easily be the issue, it was for me (though I came from LAOS 17). I also have an 8704F and it worked.
K14_Deploy said:
Have you tried a different USB-C cable or computer? That could easily be the issue, it was for me (though I came from LAOS 17). I also have an 8704F and it worked.
Click to expand...
Click to collapse
Using a USB-C to A cable. I've tried two cables that I know are good. I'll try doing this from my Mac and report back
Got things to work...I had to flash the recovery partition rather than just fastbooting twrp
Double tap to wake doesn't appear to work. Funny enough double tap taskbar to turn off the screen does work.
I did notice the wifi disconnecting a few times and it initially made me worried and reminded me of when the tablet first came out and couldn't connect to 5ghz wifi.
It seemed like it leveled out after a while, but I couldn't explain it.
Otherwise it's running nicely
thanks all
Thanks a lot for this ROM!!!
I went through the process and everything was a breeze
A brand new tablet thanks to you, have a nice day!
Hi,
Does this build support root ? and does Netflix etc work or do we need to follow the guide on the previous version ?
Thanks
root is supported via Magist Manager. Netflix works also fine on my TB8704F
Regards

[UNOFFICIAL][RECOVERY][PitchBlackRecoveryProject] PBRP For Lenovo Tab 4 8 ( TB-8504X/F )

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* I'm 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.
*/
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.5.2
PitchBlack version: 3.1.0
For Device: Lenovo Tab 4 8 TB-8504X/F
Build by: @Electron.48
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device Trees: Device Trees
Fully native android like UI
Full dark theme with changeable accents
Reorganized menus
Use AromaFM as default file manager
Various tools are include
System debloater available
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions:
Fastboot Method:
Download PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Open Terminal where u have downloaded the pbrp img file
Go into Bootloader
Apache config:
adb reboot bootloader
Flash the recovery image
Code:
fastboot flash recovery PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
Reboot to Recovery and congrats you have successfully installed PBRP.
Flashing ZIP:
You should have a custom recovery already for this method
Flash the PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip in your custom recovery
Press volume down button to reboot to PBRP.
Congrats. You have successfully installed PBRP
What works:
Everything ( May find bugs its in testing phase )
Bugs:
You tell me
Downloads:
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.img
PBRP-TB8504-3.1.0-20220528-1258-UNOFFICIAL.zip
Credits:
TeamWin for TWRP
PitchBlack Team for PBRP
@highwaystar_ru for Device Trees
Status:
Testing
Release Date:
28-05-2022
reserved
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not
ZONTAC said:
Awesome recovery and thanks for tools feature
Only one bug : touch is not responding but turning display off than on fix it.
Question : is it possible to restore twrp backups using PBRP
Click to expand...
Click to collapse
Btw can u share some screenshots...?
Electron.48 said:
Ig it should be possible. Try to copy the backups in PBRP folder then restore. Tell if it works or not
Click to expand...
Click to collapse
Working
it doesnt work it just goes to the normal android recovery after i try to use it after flashing
stinkysockboi said:
it doesnt work it just goes to the normal android recovery after i try to use it after flashing
Click to expand...
Click to collapse
Tell in detail or provide log so that dev can work on it
Electron.48 said:
Bugs:
You tell me
Click to expand...
Click to collapse
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com
deadman96385 said:
So TB-8504F has a touchscreen issue where you need to sleep and wakeup recovery after it boots for touch to work. Like what @ZONTAC mentioned earlier. I was able to fix it on TWRP 3.6.2 that I built for testing. I would imagine it would work for PBRP as well. It does not affect TB-8504X which is why its not commonly seen. The F variant is not as popular. I have not tested it on 8504X mind you but I don't think that flag will be needed by it.
TB-8504F: Remove blank on boot · deadman96385/[email protected]
This flag kills the Himax touch until you lock and unlock on TB-8504F but strangely does not affect TB-8504X
github.com
Click to expand...
Click to collapse
But i have 8504X variant
ZONTAC said:
But i have 8504X variant
Click to expand...
Click to collapse
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.
deadman96385 said:
Your recovery advertises that it supports both variants. That patch will fix the issue on TB-8504F, it should not change anything on TB-8504X but I don't have that version to confirm.
Click to expand...
Click to collapse
If you have build so i can test it on my tab(8504x)
Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?
ch3mn3y said:
Do You have any idea?
Freshly flashed stock, there everything works, but I cannot flash any ROM - tried both crDroid, RR and Ubuntu. Always same error.
Strange is it mounts system at first... And after formatting it can be mounted again, but than I got error, cos no image is there to be patched, I believe?
Click to expand...
Click to collapse
Follow proper processor
In your case :- if you are coming from stock , 1. mount system in stock recovery
2.flash pbrp/twrp
3. do factory wipe(or reset)
4. do advance wipe in which wipe system, cache, delvick ,data
5.after that flash system
6. Still having problem try d/f twrp or contact rom dev
Did a test boot without flashing. System starts but hangs on many tasks, even restarting to other modes hangs the system. My device reports as tb_8504x. I had problem with flashing through TWRP so I wanted to try PBRB.
Hello, I got PBRP to boot into recovery, I have OEM bootloader unlocked and USB debugging enabled. I'm trying to completely format the tablet to install LineageOS 18. When I wipe the process gets stuck on "Formatting system using mke2fs". It's been on it for about an hour now. Is that normal? The device is responsive. I can hold the power button down and get reboot options. I can force a reboot and get back into the recovery and try again but each time it gets halted at the format stage. What should I do?

Development [UNOFFICIAL] LineageOS 20 for the Motorola Edge 30 Ultra (eqs)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
What's working:
RIL (Calls, SMS, Data)
Fingerprint (FOD)
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
Vibration
Wifi Hotspot
Display out
Wireless display
Selinux enforcing
IMS (VoLTE/VoWifi)
What's not working:
Receiving SMS on chinese variants (or just carriers) may not work, more debugging required
Flashing Instructions:
Requirements:​
Unlocked bootloader!
Learn these instructions by heart
PC with working adb/fastboot
Downloaded:
LineageOS zip
copy partitions zip​
optional:
gapps
magisk
<insert other mod here>
Make a backup of EVERYTHING on your internal storage you dont wanna lose
reboot to bootloader
Code:
adb reboot bootloader
or reboot the device, and hold power and volume down
Flash the lineage recovery to both slots
Code:
fastboot flash recovery_a recovery.img
Code:
fastboot flash recovery_b recovery.img
reboot to recovery
use volume keys to select recovery reboot option and press power to confirm
in recovery use volume keys and power to navigate
stock vendor_boot does not contain touch drivers, so live with this for a bit
Select "Apply Update"
Select "Apply from ADB"
If you come from stock, this is REQUIRED:​
Code:
adb sideload copy-partitions-20220613-signed.zip
Code:
adb sideload <lineageos zip>
Go back (Volume up can select the back button)
Advanced
Reboot recovery
You can use touch now
factory reset
-----Optional, Gapps/Magisk------
Select "Apply Update"
Select "Apply from ADB"
Code:
adb sideload <path/to/gapps.zip>
Code:
adb sideload <path/to/Magisk.zip>
Code:
adb sideload <path/to/some/other/mod.zip>
-----End Optional-----
Reboot system now
First boot, especially with Gapps, may take a while
Telegram group: https://t.me/MotoEdge30Ultra
Downloads:
copy partitions: https://mirrorbits.lineageos.org/tools/copy-partitions-20220613-signed.zip
LineageOS 20 (no gapps): https://drive.google.com/file/d/11hDmheZHVUey22upXOC-Yq1IqGC5-Fbq/view?usp=sharing
LineageOS 20 (with gapps): https://drive.google.com/file/d/11k64BFOhVbVl7OsUcpIAPXTRCl-FlViz/view?usp=sharing
Sources:
device tree/kernel: link
vendor: link
Changelogs:​20221119:​
Initial Release
20230523:​
Up-to-date LineageOS sources
common vendor from bronco T1TBS33.32-8-9-7-2
eqs specific from S3SQS32.16-72-31-3 (mainly camera, firmwares)
Main kernel compiled from T1TBS33.32-8-9-7-2
Updated kernel device tree from T1TBS33.32-8-9-7-2
other changes I might have forgotten...
Reserved Post number 2
hola, alguien lo ha instalado?
我是酷安吸引过来看看的,不准备刷,小白鼠先上,我坐等PE系统。
Mod edit: English please!
Google translation:
I was attracted by Kuan to take a look. If I don’t plan to brush, the mouse will go first, and I will wait for the PE system.
Thank you for all your efforts!!! Hoping we could get more custom ROM to run later
Tiene gapps incluidos? I have already seen that it does not have what gapps do you recommend? thanks for the job
Awesome, thanks for your work! Should be possible to compile TWRP with your device tree and kernel now as well, right?!
Would you mind explaining why copy-partitions is needed and what it does?
Any experiences? Does Netflix work?
I have stock ROM, but magisk with unlocked bootloader... Putting it on the zgisk list, and using Safernet module updates via Playstore normally. But without hrd only in SD.
grove said:
Any experiences? Does Netflix work?
Click to expand...
Click to collapse
iron maiden said:
Tiene gapps incluidos? I have already seen that it does not have what gapps do you recommend? thanks for the job
Click to expand...
Click to collapse
I'm using Nikgapps currently
Killuminati91 said:
Awesome, thanks for your work! Should be possible to compile TWRP with your device tree and kernel now as well, right?!
Would you mind explaining why copy-partitions is needed and what it does?
Click to expand...
Click to collapse
Should work, i guess. And for TWRP no special kernel is needed. The recovery partition just contains a ramdisk (the recovery itself), with no kernel. During boot the bootloader merges the available ramdisks (depending on the boot mode ofcourse).
E.g. when you start the device normaly, it will merge the ramdisks from boot and vendor_boot (soc specific kernel modules)
When you start recovery it will merge the ramdisks from boot, vendor_boot and then recovery.
Copy partitions copies all slotted partitions (_a ad _b ones) from the current active slot to the inactive slot (e.g. when youre on slot a, it will copy all of them to their _b counterparts).
This is needed because motorola does not ship the second slot populated. So in case you have a fresh device (no OTAs and so, or you just flashed stock again), the second slot will be completely empty (no bootloader, no nothing). And A/B devices switch slots after every flash of a ROM, so the device would then try to boot into an empty slot, which fails and would kick you into qualcomms emergency download mode (9008).
If blankflash would help you in that state, im not sure.
grove said:
Any experiences? Does Netflix work?
Click to expand...
Click to collapse
Using it for like 2 weeks now as a daily driver. Netflix should work, but as L3 (idk if L1 would work, my device never was L1, so cant test that)
SGCMarkus said:
I'm using Nikgapps currently
Should work, i guess. And for TWRP no special kernel is needed. The recovery partition just contains a ramdisk (the recovery itself), with no kernel. During boot the bootloader merges the available ramdisks (depending on the boot mode ofcourse).
E.g. when you start the device normaly, it will merge the ramdisks from boot and vendor_boot (soc specific kernel modules)
When you start recovery it will merge the ramdisks from boot, vendor_boot and then recovery.
Copy partitions copies all slotted partitions (_a ad _b ones) from the current active slot to the inactive slot (e.g. when youre on slot a, it will copy all of them to their _b counterparts).
This is needed because motorola does not ship the second slot populated. So in case you have a fresh device (no OTAs and so, or you just flashed stock again), the second slot will be completely empty (no bootloader, no nothing). And A/B devices switch slots after every flash of a ROM, so the device would then try to boot into an empty slot, which fails and would kick you into qualcomms emergency download mode (9008).
If blankflash would help you in that state, im not sure.
Using it for like 2 weeks now as a daily driver. Netflix should work, but as L3 (idk if L1 would work, my device never was L1, so cant test that)
Click to expand...
Click to collapse
No SMS received after root
@SGCMarkus does 200Mpx mode works? manual, raw...
ailikes said:
No SMS received after root
Click to expand...
Click to collapse
You on the chinese variant and/or on a chinese carrier?
Currently thats a known issue... needs more investigating. But kinda difficult without more people who test it, as it works here on my (european) device in austria.
TF1920 said:
@SGCMarkus does 200Mpx mode works? manual, raw...
Click to expand...
Click to collapse
MotCamera4 is included, and all features should work.
Hi, I got the phone just now, I wonder what role does the "copy partition" play in the flashing process? Like some modem? or something else?
C_CWang said:
Hi, I got the phone just now, I wonder what role does the "copy partition" play in the flashing process? Like some modem? or something else?
Click to expand...
Click to collapse
Check post #11 here
also will write a FAQ later for that i guess
@SGCMarkus
What are your plans for this ROM ? Will you maintain it for a while ?
SGCMarkus said:
You on the chinese variant and/or on a chinese carrier?
Currently thats a known issue... needs more investigating. But kinda difficult without more people who test it, as it works here on my (european) device in austria.
MotCamera4 is included, and all features should work.
Click to expand...
Click to collapse
Can a telegram group be created
Can you create a telegram? I'm from China. I can help test it. I'm looking forward to it. Come on, developers
Thank you for you sharing your builds, I want flash your rom without using root and I have some questions:
1- did you plan to make offical lineage
2- play store certified or not
3- can we running the bank app without any security issue

[ROM][13][wayne][Kernel 4.19][UNOFFICIAL]LineageOS 20.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Working:​- Wifi
- Sound
- USB tethering
- RIL
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- Camera
- GPS
- Fingerprint
- Dac(usb audio)
Flash guide:​Before you start...​- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
- You need to backup your data, your data partition will be formatted.
Preparations​- Android Debug Tools
- Dynamic Partition Supported Recovery. Download
- super_empty.img Download
- Connet your device to PC
Then...​1. Flash Dynamic Partition Supported Recovery into your device
Bash:
fastboot flash recovery <RECOVERY_PATH>
2. Flash super_empty.img into your device
Bash:
fastboot wipe-super <super_empty_PATH>
3. Reboot to recovery
Bash:
fastboot reboot recovery
4. Format your data partiton in recovery
5. Install Dynamic Partition ROMS into your device by:
Apply update—>Apply from ADB
Now, be sure your device is connected to your PC, and run
Bash:
adb sideload <ROM_PATH>
6. Reboot and enjoy
Picture​
Download:​Release
If you want to give me some money to support my work, please contact telegram @xiaoleGun
Source Code:​device
vendor
kernel
ROM OS Version: Android 13
ROM Kernel: Linux 4.19.271
Compared with A2, the A13 ROM of mi6x is very small. I can see this newly developed version, and I feel that my 6x can survive again. Thank you very much
xiaoleGun said:
View attachment 5823351
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Working:​- Wifi
- Sound
- USB tethering
- RIL
- Sensors
- Bluetooth
- Wifi HotSpot
- MTP
- Camera
- GPS
- Fingerprint
- Dac(usb audio)
Flash guide:​Before you start...​- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
- You need to backup your data, your data partition will be formatted.
Preparations​- Android Debug Tools
- Dynamic Partition Supported Recovery. Download
- super_empty.img Download
- Connet your device to PC
Then...​1. Flash Dynamic Partition Supported Recovery into your device
Bash:
fastboot flash recovery <RECOVERY_PATH>
2. Flash super_empty.img into your device
Bash:
fastboot wipe-super <super_empty_PATH>
3. Reboot to recovery
Bash:
fastboot reboot recovery
4. Format your data partiton in recovery
5. Install Dynamic Partition ROMS into your device by:
Apply update—>Apply from ADB
Now, be sure your device is connected to your PC, and run
Bash:
adb sideload <ROM_PATH>
6. Reboot and enjoy
Picture​View attachment 5823361View attachment 5823365
Download:​Release
If you want to give me some money to support my work, please contact telegram @xiaoleGun
Source Code:​device
vendor
kernel
ROM OS Version: Android 13
ROM Kernel: Linux 4.19.271
Click to expand...
Click to collapse
I follow the installation steps, but the result cannot be installed smoothly. Is there any way to solve it, thank you
mouse723 said:
I follow the installation steps, but the result cannot be installed smoothly. Is there any way to solve it, thank youView attachment 5828119
Click to expand...
Click to collapse
You can try this recovery.img
xiaoleGun said:
- Be sure your partitions size is original, this is **IMPORTANT**, or you may brick your device.
Click to expand...
Click to collapse
How to know if it is? because mine was originaly a Mi A2 that i converted into a Mi 6X like a long time ago (back when guides to do so were fairly new) but haven't had issues flashing any rom on it so
demonoidmaster said:
How to know if it is? because mine was originaly a Mi A2 that i converted into a Mi 6X like a long time ago (back when guides to do so were fairly new) but haven't had issues flashing any rom on it so
Click to expand...
Click to collapse
The size of the system partition is 3221225472 bytes
xiaoleGun said:
The size of the system partition is 3221225472 bytes
Click to expand...
Click to collapse
Had your previous 19.1 build installed but tried flashing this one and it's giving me a liblp error about geometry magic signature being invalid
(Haven't flashed the super wipe zip yet because I wanted to know your opinion about my device type before doing that as mine isn't a oem Wayne model but rather a mi a2 converted into a Wayne model)
demonoidmaster said:
Had your previous 19.1 build installed but tried flashing this one and it's giving me a liblp error about geometry magic signature being invalid
Click to expand...
Click to collapse
try this recovery.img
xiaoleGun said:
try this recovery.img
Click to expand...
Click to collapse
what about their same recovery under the v11 tag ? it's newer than v10.1
EDIT: flashed their v11 recovery and rebooted to fasboot for super-wipe zip flash, then flashed xiaomi firmware in recov, wiped data.cache.metadata tried flashing but still gave dynamic partition error so i just did a quick reboot to recov first to make sure and tried again and sure enough it flashed fine, about to reboot to OS now, gonna edit again if booted
EDIT2: booted, just gotta restart to recov to flash nikgapps
xiaoleGun said:
try this recovery.img
Click to expand...
Click to collapse
trying to flash nikgapps (v13 for android 13) but it keeps failing with error /sideload/package.zip (status1) and i just don't know what else to do, can't even try litegapps++ microg either because it fails with that error too
demonoidmaster said:
trying to flash nikgapps (v13 for android 13) but it keeps failing with error /sideload/package.zip (status1) and i just don't know what else to do, can't even try litegapps++ microg either because it fails with that error too
Click to expand...
Click to collapse
Use magisk module, because we use erofs
xiaoleGun said:
Use magisk module, because we use erofs
Click to expand...
Click to collapse
is there no way to remount as read-write (on my other phone i mount then do mount -o remount,rw /product or such to remount as read-write when needed) ? i don't want magisk on this phone because i'm setting it up to give to someone so i don't want to have it use gapps as a module, besides i don't think nikgapps supports installing as module
demonoidmaster said:
is there no way to remount as read-write (on my other phone i mount then do mount -o remount,rw /product or such to remount as read-write when needed) ? i don't want magisk on this phone because i'm setting it up to give to someone so i don't want to have it use gapps as a module, besides i don't think nikgapps supports installing as module
Click to expand...
Click to collapse
You can repackage the system image
xiaoleGun said:
You can repackage the system image
Click to expand...
Click to collapse
this is honestly getting overly complicated for just trying to set up a basic rom...
just tried flashin magisk but nada doesn't work gives error 127, i'm switching back to a rom that works
hi xiaole cant use gboard on this rom..
Working flawlessly with MicroG and some Magisk modules.
Im very happy with this rom.
cant use wifi, cant use gapps, cant start setup wizard even if the gapps package had setup in it. Camera not work, a lot of bugs for me.
MI 6X released in 2018, can use android 13 smoothly, and no lag, no heat, stable and no self-reboot, all functions look normal so far(The camera app will black out, use Opencamera instead). Very exciting ROM. Looking forward to seeing the double tap to wake feature in the next version.
I can't install MindTheGapps, help! On the Recovery console:
Code:
Low resource device detected, removing large extras
Not enough space for Gapps! Aborting
Cleaning up files
Unmounting partitions
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed wtih status 1.
Installation aborted.
I have tried the following MindTheGapps:
MindTheGapps-13.0.0-arm64-20230408_162909.zip
MindTheGapps-13.0.0-arm64-20230323.zip
MindTheGapps-13.0.0-arm64-20221025_100653.zip
Then I tried NikGapps:
NikGapps-core-arm64-13-20230418-signed.zip
NikGapps-basic-arm64-13-20230418-signed.zip
But both gave errors:
Code:
...
Installing update...
ERROR: recovery: Error in /sideload/package.zip (status 1)
Install completed with status 1.
Installation aborted.
Please help, thank you!
i have problem :/

Categories

Resources