Code:
* // Disclaimer! //
*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead OTGs,
* 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. Hard & a lot.
*
As the very first Nokia Android Phone released by HMD Global, it's really a pity that it even doesn't support Project Treble.
Therefore, I brought the new partition table for both Nokia 5 and 6 and hope it will be helpful for your further development.
For all of Nokia 5 and Nokia 6 (TA-1000/1003 only), you'll need to use this partition table file:
Code:
fastboot flash partition ND1-D1C-treble-3295S-800V-gpt_both0.bin
fastboot reboot-bootloader
For other Nokia 6 (TA-1021/1025/1033/1039), you'll need to use this partition table file:
Code:
fastboot flash partition PLE-treble-4095S-800V-gpt_both0.bin
fastboot reboot-bootloader
After flashing, your phone will have vendor partition available for future custom rom building and flashing.
For ND1 and D1C, you'll have 3295MB system partition and 800MB vendor partition.
For PLE, you'll have 4095MB system partition and 800MB vendor partition.
However, I'm not good at building custom vendor image, so it's up to you.
After that, you should not use existing official TWRP for Nokia 6 (PLE) and will need modification, and my pre-modded TWRP is uploaded here.
Android 8.x : TWRP-3.4.0-8-0-PLE-D1C-ND1_treble.img
Android 9 : TWRP-3.2.3-9-0-PLE-D1C-ND1_treble.img (I didn't use the latest on TWRP official site, because it cannot decrypt data and being booted via fastboot boot command properly)
{
"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"
}
Happy modding this device!
PLE (TA-1021) vendor TWRP backup file:
both TWRP are not able to mount vendor partition in nokia 5, but still able to flash
Elvaa said:
both TWRP are not able to mount vendor partition in nokia 5, but still able to flash
Click to expand...
Click to collapse
have you already install gsi rom for this device, did it boot?
JinbrianZ said:
have you already install gsi rom for this device, did it boot?
Click to expand...
Click to collapse
TA-1021 tested A-only ROM, no
i think we need to flash AB-partition GSI because of system-on-root, but i don't want to test
if someone tested it, i'll happily port my kernel mod to support mounting vendor
Removed
xaedoplay.modder.xda said:
TA-1021 tested A-only ROM, no
i think we need to flash AB-partition GSI because of system-on-root, but i don't want to test
if someone tested it, i'll happily port my kernel mod to support mounting vendor
Click to expand...
Click to collapse
I tried AB-partition GSI. It doesn't boot, too.
Everyone can't flash gsi because Stock ROM don't have VNDK for gsi running -.---
xterad2203 said:
Everyone can't flash gsi because Stock ROM don't have VNDK for gsi running -.---
Click to expand...
Click to collapse
As I know, stock kernel can't not find vendor partition because of failed to read fstab from dt. BTW, I tried to flash vndklite gsi, and it doesn't boot too
After doing all these things will my nokia 6 support project treble?
just answer yes or no.
Elvaa said:
As I know, stock kernel can't not find vendor partition because of failed to read fstab from dt. BTW, I tried to flash vndklite gsi, and it doesn't boot too
Click to expand...
Click to collapse
I think we need a custom kernel which can find vendor partition.
Can anyone develope a custom kernel?
Elvaa said:
both TWRP are not able to mount vendor partition in nokia 5, but still able to flash
Click to expand...
Click to collapse
Did you flashed any gsi?
hasnainali2404 said:
I think we need a custom kernel which can find vendor partition.
Can anyone develope a custom kernel?
Click to expand...
Click to collapse
Did you try in custom kernel named kernel plus for nokia 6?
FutureStarz said:
Did you try in custom kernel named kernel plus for nokia 6?
Click to expand...
Click to collapse
No I didn't tried it and can't try because this is my primary device so I dont want to take any risk if you want so pls try it and tell us what happens.
This is also my primary device but I will try after some time. Till then I will wait if a developer may develop it
hikari_calyx said:
Code:
* // Disclaimer! //
*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead OTGs,
* 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. Hard & a lot.
*
As the very first Nokia Android Phone released by HMD Global, it's really a pity that it even doesn't support Project Treble.
Therefore, I brought the new partition table for both Nokia 5 and 6 and hope it will be helpful for your further development.
For all of Nokia 5 and Nokia 6 (TA-1000/1003 only), you'll need to use this partition table file:
Code:
fastboot flash partition ND1-D1C-treble-3295S-800V-gpt_both0.bin
fastboot reboot-bootloader
For other Nokia 6 (TA-1021/1025/1033/1039), you'll need to use this partition table file:
Code:
fastboot flash partition PLE-treble-4095S-800V-gpt_both0.bin
fastboot reboot-bootloader
After flashing, your phone will have vendor partition available for future custom rom building and flashing.
For ND1 and D1C, you'll have 3295MB system partition and 800MB vendor partition.
For PLE, you'll have 4095MB system partition and 800MB vendor partition.
However, I'm not good at building custom vendor image, so it's up to you.
After that, you should not use existing official TWRP for Nokia 6 (PLE) and will need modification, and my pre-modded TWRP is uploaded here.
Android 8.x : TWRP-3.4.0-8-0-PLE-D1C-ND1_treble.img
Android 9 : TWRP-3.2.3-9-0-PLE-D1C-ND1_treble.img (I didn't use the latest on TWRP official site, because it cannot decrypt data and being booted via fastboot boot command properly)
View attachment 5287723
Happy modding this device!
Click to expand...
Click to collapse
how did you mount vendor? I can't mount it in my device.
hikari_calyx said:
fastboot flash partition PLE-treble-4095S-800V-gpt_both0.bin
Click to expand...
Click to collapse
when I flash it, device starts bootloop. i tried flashing 4 times
FutureStarz said:
when I flash it, device starts bootloop. i tried flashing 4 times
Click to expand...
Click to collapse
yes, it will bootloop ur device because of repartitioning from the system. ur os will be corrupted.*
JinbrianZ said:
yes, it will bootloop ur device because of repartitioning from the system. ur os will be corrupted.*
Click to expand...
Click to collapse
but when i flash it for first time, os booted without problem
FutureStarz said:
but when i flash it for first time, os booted without problem
Click to expand...
Click to collapse
In my case, I put this partition table to stock firmware, then I flash "modified" firmware. The stock OS still work normally without any problem
Related
{
"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 (or isn't ? who am I to judge ?)
*
* 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.
*
*/
Team Win Recovery Project 3.4.1 for Realme 6 Pro
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Ported From Realme X50 5G
• by ctapchuk from 4pda
Most Bugless Recovery Right Now
Installation
1. Disable verified boot first
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img which is extracted from current stock rom ozip file
2. Flash downloaded twrp
Code:
fastboot flash recovery twrp.img
3. Reboot to recovery
Code:
fastboot reboot recovery
List of features :
• Decryption of storage works on latest Stock firmware (September security patch)
• Successful installation of any ROM's
• External sdcard & USB-OTG support
• Additional features such as close AVB2.0 (disabled-verify on vbmeta), disable replace TWRP
• Working mounting of dynamic partitions (r/o only)
• Additional backup/restore partitions list (except system, vendor and etc)
Download :
https://drive.google.com/file/d/1NWS74xHgyIKwpTd5sZ6af9ukroXF7VAp/view?usp=sharing
Version Information
Status : Stable
Current Stable Version : 3.4.1b_0507
Stable Release Date : September 30, 2020
Reserved
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Richardo87 said:
The same issue i was getting with the previous TWRP versions, cannot access MTP storage. Also while phone on, cannot copy anything on storage.
Click to expand...
Click to collapse
Please provide screenshots of your problem. I assume that you are trying to copy files to an encrypted internal storage. Decrypt /data or copy files to SD card
Is this compatible with build number RMX2061_11_A.35? Thank you!
Sent from my RMX2061 using XDA Labs
ByinAlbirt said:
Is this compatible with build number RMX2061_11_A.35?
Click to expand...
Click to collapse
Yes
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
No need i guess. Try 'Disable Replace TWRP' and reboot ...
debdeep98 said:
Yes
Click to expand...
Click to collapse
Thank you so much! I have successfully installed TWRP Recovery in my realme 6 Pro build number RMX2061_11_A.35.
Sent from my RMX2061 using XDA Labs
Richardo87 said:
Good work, i was trying to find a proper TWRP for my Realme 6 Pro from lasat week.
Until now i was able to flash updates or downgrades just via Realme Flash Tool.
Do we still need to flash vbmeta_v2 in order for TWRP to work properly?
Testing now.
Update:
It does need the OF_avb-patcher.zip tp be flashed in order to keep TWRP after restart and to decrypt MPT storage and phone corectly.
I did not flashed it and all the time got stuck in a boot loop and TWRP and all phone remained encrypted, was not able to do anything until i flashed Stock Rom via Realme Flash Tool.
Disclaimer: Flashing Stock Rom will make TWRP gone, to preserve it, follow the steps:
1. Flash Stock ROM .ozip
2. Flash patched-vbmeta-v2.img
3. Flash TWRP from above link
4. Flash OF_avb_patcher.zip
6. Flash Magisk via TWRP (If required)
7. Done
Click to expand...
Click to collapse
All you need is vbmeta.img from your stock ROM.
I used above instructions and everything work just fine, including decryption of internal storage.
@Kevin Saiza thank you for your good work.
Everything's working as expected.
Right now I'm using:
Firmware A.35
LR.TWRP 3.4.1B_30.09
Magisk 21.0 (pass safety net check)
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
neoxcool said:
Newer version with all features including fastboot(d) working, ported from Xiaomi Black Shark 3 is on download in pda. Can someone attach download link here for :
LR.TWRP 3.4.2B_05.10 — RMX2061 (from Black Shark 3) .img
or
LR.TWRP 3.4.2B_05.10 — RMX2061 for Windows.zip
Thanks!
Click to expand...
Click to collapse
Coming Soon
Andres88z said:
Junior MemberThanks: 0
Junior MemberThanks: 0
Is this compatible with build number RMX2065_11_A.35? Thank you!
Click to expand...
Click to collapse
Yes why not .
Kevin Saiza said:
Yes why not .
Click to expand...
Click to collapse
Some problem with RMX2063. You try whit RMX2061
Sorry Is 2063
thank's
LR.TWRP 3.4.2B_05.10 for RMX2061 Ported from Xiaomi Black Shark 3 by Ctapchuk & logotoy73
Change extention to .img
https://anonfiles.com/hfcehcd1p9/LR.TWRP_3.4.2B_05.10_for_RMX2061_img
Changelog:
• Port from Xiaomi Black Shark 3
• Upgrade to version 3.4.2
• Fixes in Russian language
• Changed the font for English language
• Fixed fastbootd
• A/B table selection Disabled
• Correct display of the status bar
If i only boot, i need flash vbmeta?
I need urgent help please the twrp does not recognize my otg it only recognizes the sd but the otg does not what should I do to make it recognize it please help
:good:
Can't delete file from phone with root explorer so i tried with TWRP as usualy and for the first time IT DOESNT WORK!! Never seen that before. Though system's not mounted as read only. What to do..?
Do nothing. vendor, product and system partitions are R/O, because they are part of new type partition named "super". It is dynamic partition that is not editable.
Take a look here for details
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
{
"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
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.4Data 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?
{
"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?
{
"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
PictureView 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 :/