Database Develop

[BETA][DUK] TWRP 3.1.1-1 [+ROOT]

{
"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"
}
This is only for Honor 8 Pro (DUK)
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x.
Intended for usage on stock emui 5.x in combination with unlocked bootloader .
Installation Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-1-duk.img
3. reboot to recovery!
Rooting Methods
Code:
[B][U]1. Official PHH Superuser Beta 310[/U][/B]
1. download and flash [URL="http://superuser.phh.me/superuser-r310-beta.zip"]official PHH Superuser Beta 310[/URL]
2. install "Phh Superuser" from Google Play
3. Enjoy!
Downloads
Code:
[LIST]
[URL="https://github.com/OpenKirin/android_device_honor_duk/releases/download/3.1.1-1/twrp-3.1.1-1-duk.img"][U]download twrp-3.1.1-1-duk.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 25. June 2017
Q: which H8 Pro models are supported?
A: every model should be supported.
Q: Can i use this TWRP with decrypted /data?
A: Yes you can! (Check FAQ)
Q: Can i install Magisk?
A: No (encrypted /data), Yes (decrypted /data)
Q: Does official SuperSU work?
A: No (encrypted /data), Yes (decrypted /data)
Q: ETAs?
A: No.
Going back from decrypted -> encrypted?
Code:
1. Format /data inside of TWRP
2. Flash eRecovery & Kernel from your currently installed Stock ROM Build
3. Do a factory reset inside of eRecovery
5. Let device boot up
6. Install your current firmware hw_data package & SuperSU using TWRP again
Want to decrypt? No problem.
Code:
1. Format /data inside of TWRP
2. Flash a kernel with fileencryption disabled in fstab
3. bootup your device
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Honor 8 Pro
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin/android_device_honor_duk
Version Information
Status: Beta
Created 2017-06-23
Last Updated 2017-06-25

Reserved
Changelog
Code:
[B]TWRP 3.1.1-1[/B]
* fix twrp on emmc based devices

Man that was fast. Will definitely flash this after I get my H8 Pro.
Sent from my Honor 8 using XDA Labs

Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate

blattes86 said:
Hello,
I tested the package, unfortunately after the flash and first boot impossible to return under android.
If I remember correctly there was a problem of mount point.
To get out I had to flasher the recovery and system partitions of the original rom.
Having to reset my phone I have no log, but if you need anything else do not hesitate.
@ +
Via google translate
Click to expand...
Click to collapse
this should work for every h8 pro utilizing emmc storage:
https://drive.google.com/open?id=0BxWP2gF_0Bd_OHBPWDctZmJCanc
It has been tested.
Regards

Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?

OldDroid said:
this should work for every h8 pro utilizing emmc storage:
It has been tested.
Regards
Click to expand...
Click to collapse
I flashed it, it works fine.
Thanks

adriansticoid said:
Can we use Magisk instead? Or the loop issue back in Honor 8 is also here?
Click to expand...
Click to collapse
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.

-=MoRpH=- said:
Magisk 13 works fine.
Just flashed the Magist beta and installed the Magisch Manager 5.
Click to expand...
Click to collapse
That's great news. Thanks for confirming. :highfive:
Sent from my Honor 8 using XDA Labs

I flashed emmc version and supersu. For going in twrp I've to clic in the middle of the volume button and the power on.

Interesting, i tried to install it but i'm stuck with installion...i know how to enter fastboot mode with phone plugged to my computer with android sdk on, but the adb files look to be missing when i check with cmd...
Can anyone here give a quick tutorial ? Thanks

New Version (3.1.1-1) available - You can find more infos in OP.
This release fixes partition mounting on emmc 5.1 based devices
Source code is now also up and can be built!
https://github.com/OpenKirin/android_device_honor_duk
Regards

Wow that was faster than I could learn to do it.
Great job. May I ask how you got the important informations to build this?
Did you inject su into the image to gain root and then read all the detailed data through terminal or adb or root file explorer?
Just asking cause i train my brain more and more in my spare time and want to get behind the knowledge base to learn. :good:

First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do I need to choose?
Cheers

Would this work on the Chinese V9 variant?

smouker said:
First of all thank you for your work, I got the Recovery, root, Magisk, etc. running.
I have 2 Questions:
1. the internal storage when I boot to the recovery looks like enrypted (lots of random named folders). Is it possible to decrypt it for now, since there is currently no custom kernel available?
2. Can I flash the Firmware update to 130b in TWRP? If yes, wich package do IP need to choose?
Cheers
Click to expand...
Click to collapse
Format the whole internal storage to remove encryption.

adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
can I restore Data via TWRP without problems?

adriansticoid said:
Format the whole internal storage to remove encryption.
Click to expand...
Click to collapse
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt

smouker said:
can I restore Data via TWRP without problems?
Click to expand...
Click to collapse
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
blattes86 said:
After testing, formatting the whole internal storage does not work.
To restart the partition is new encrypt
Click to expand...
Click to collapse
What do you mean to restart the partition is new encrypt?

adriansticoid said:
Yes it should work. Just make sure that both backup and restore destinations are either both encrypted or both decrypted.
What do you mean to restart the partition is new encrypt?
Click to expand...
Click to collapse
sorry for my bad english.
After restart the phone...

[RECOVERY][TWRP 3.4.0.0] Galaxy Note 7 Fan edition [N935F/FD/S/L/K]

{
"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"
}
Unofficial TWRP 3.4.0.0 For Galaxy note 7 FE (N935X)​
Disclaimer:
I do not own this device, however i work on the S7/S7E and there was enough requests for a FE support. so here we are.
This TWRP has been tested on 2 devices so far, it fixes mounting issues, and is based on new device trees. This should pave the way for other S7 developers to join in and add support to the FE since its not that difficult.
My custom kernel (Cronos) and Floyd Q Rom will make it to this thread once they are validated more.
Thanks to @butchieboy and Đỗ Gia Huy for testing
Also moving forward with this thread, you take full responsibility of any modifications done towards your device.
Features: :
Code:
- built from latest Pie source
- built from android-9.0 recovery sources
- fully compatible with Android 8.*/9.0/10.0
- Full F2FS Support for data and cache
- Full support for FLoydQ ROM
- Built with Busybox and resetprop
Downloads:
N935X (N935F/FD/S/L/K) : Download
Instructions:
Odin
Download latest Odin zip from Here
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home + Volume down + Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in your hands, disconnect the usb cable and press simultaneously the Home + Volume down + power until the Download mode pop-up shows
Press volume DOWN (so the phone reboots) then quickly press Home + VolumeUp + Power until the TWRP screen shows up
If it didn`t worked, redo the steps from #1 being more careful. and faster
TWRP (If you have a previous twrp installed)
Download TWRP_*.img, push it into phone storage (or external sdcard if thats not avalible), choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods due to RMM Lock / KG State, make sure you check this thread
Rooting and Internal Storage:
Finally, if you want to be able to read/write to the internal storage, you must format it to clear encryption, take a backup of your stuff before hand.
Go to TWRP > Wipe > Format Data > Type YES.
your data is now usable. if you didnt flash noverity-opt-encrypt or MagiskRoot your data will be encrypted again.
If you want to root your device now, simply download the latest magisk and flash it in your new recovery.
Sources:
Device tee : Github
Kernel : Github
Credits:
TeamWin, corsicanu, morogoku, Shariq3422 and testers
XDA:DevDB Information
TWRP-3.4.0.0, Tool/Utility for the Samsung Galaxy Note FE
Contributors
ananjaser1211, morogoku, corsicanu, Shariq3422
Source Code: https://github.com/ananjaser1211/android_device_samsung_gracerlte
Version Information
Status: Testing
Current Stable Version: V1.0
Stable Release Date: 2020-06-23
Current Beta Version: V1.0
Beta Release Date: 2020-06-23
Created 2020-06-23
Last Updated 2020-06-25

Misc Links:
Telegram Support Group
[*]Telegram news Channel
Latest Magisk
FloydQ Oneui 2.0 Beta ROM + N7FE Kernel

F.A.Q
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Can,t find OEM Toggle, RMM Locked
A : Read this thread
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Make sure you have the latest samsung stock firmware installed (to be on latest bootloader and modem combo)
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Q: How to Use F2FS ?
A : This requires you to be on Floyd ROM and the latest FE CronosKernel build. otherwise you wont be able to boot. Follow these steps
1) Wipe > advanced wipe > Data > CHANGE > F2FS (Your entire internal storage will be wiped out!)
2) Reboot and you will have DATA as F2FS, the same can be done to CACHE as well. Do not do it to SYSTEM
P.S : Again, make sure BOTH your ROM and KERNEL support F2FS.

Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum

Yo ma...man
Well done bro!

USB OTG works. Got this error when formatting data. Restored backup that was generated, everything went fine booted up as normal.
Sent from my SM-N975U using Tapatalk

TWRP-3.4.0.0-gracerlte-20200625
TWRP-3.4.0.0-gracerlte-20200625
* Fix error in SAR disable script (Fixes installing android 9 roms while 10 is installed)
* include resetprop (required for SAR script)
* Add custom TWRP Ver Name
Download : Github
This should fix the error reported above, and fix installing Pie roms while having 10 installed.

Wow, you are all over the place my friend. Thank you..lol[emoji481]
Sent from my SM-N975U using Tapatalk

Error no longer present
Sent from my SM-N975U using Tapatalk

Getting error again when trying to create backup or flash anything
Sent from my SM-N975U using Tapatalk

butchieboy said:
Getting error again when trying to create backup or flash anythingView attachment 5048397
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
Could you try to flash a pie rom while having my Q rom installed ?
the script is there to change /system_root mount point back to /system . which is due to recent TWRP changes
i think the script is erroring due to line endings, but im not sure. let me know if the ROM flashed.
for System backup always use the system image format while dealing with android 10. ill update you if twrp pushes any more updates to this

The only Pie roms that we had for FE caused major issues. Not sure if anyone even uses them there was 1 I think. Developer threw a rom together that would throw malware on your device, lock it up and made device unusable then vanished without fixing anything. So not sure if anything is out there and really don't want to update my bootloader.
Sent from my SM-N975U using Tapatalk

ananjaser1211 said:
Please let me know what issues you find in this TWRP, i am aware it boots, backsup and flashes zips. but do let me know if USB / MTP works as expected or if it needs further work.
I will be working on adding FE Support to all my exynos8890 projects moving forward. hopefulyl putting some life in this forum
Click to expand...
Click to collapse
Installed TWRP 3.4.0.0 on the SM-N930, everything works ... Thanks Bro !!!
---------- Post added at 10:02 AM ---------- Previous post was at 09:18 AM ----------
ananjaser1211,may I ask you to build a core for SM-N930X???...I will be grateful.

I have released my cronos kernel for Pie
For a feature list , they are mentioned on this thread here
So now you can use the same kernel from Q on pie ROMs if you choose so.
Download : Github
Enjoy

Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0

thank you thank you THANK YOU
---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------
It's work

butchieboy said:
Just flashed your Floyd Q 3.0 on Note FE...my friend you are really keeping these older devices alive. Thank you.
NOTE FE FLOYD Q 3.0
Click to expand...
Click to collapse
Did you have issues booting into system after you rooted? I know it's old but I just can't do it after flashing and following the root guide here

Nope sure didnt
Sent from my SM-N975U using Tapatalk

twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar

ripee said:
twrp-3.5.2_9-0-gracerlte.img
twrp-3.5.2_9-0-gracerlte.tar
Click to expand...
Click to collapse
link broken

[RECOVERY][Realme 6 Pro] TWRP Recovery [Stable]

{
"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

Development [ ROM] MIUI 12.5 [PORTED] FROM Mi 10i For Redmi Note 10 Pro/ Pro Max

{
"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"
}
This Rom is For Sweet & Sweetin Both
MIUI 12.5 Xiaomi EU Beta v21.1.28 - PORT | Android 11.
Updated: 06/05/'21
Download | Mirror [2.41 GB]
Blog
Support
Changelog:
• Ported from Mi 10 Lite (monet)
• Ported slightly older version as it's more stable
• Fixed updater-script codenames, now flashable directly on both sweet & sweetin
• Fixed issue stuck on bootanimation, needs force reboot for first boot
• Fixed Notch & Status Bar padding
• Fixed Screen Flickering at 120 Hz
• Other miscellaneous fixes & improvements
Instructions:
• If your device is encrypted then do Format Data otherwise just wipe Dalvik Cache, Cache & Data
• Flash ROM
• Flash Disable DM-Verity & Forced Encryption zip
• Flash Permissiver zip
• Reboot to recovery & flash latest Magisk
• Reboot. Done.
Credits:
• @tito_mz for helping
By @techzoneunique
You Can Watch Video -- Click Here
Subscribe Our YouTube Channel-- Click Here

Welcome !

can i dirty from the latest EU 12.0.14?

yayakuya said:
can i dirty from the latest EU 12.0.14?
Click to expand...
Click to collapse
I dont think so

yayakuya said:
can i dirty from the latest EU 12.0.14?
Click to expand...
Click to collapse
No, you need to format data.

Nice! This seems interesting.

Thanks for your work.
Bugs that i note ambiente display dont work, double tap sensor funciona dont work

Thanks for this rom
This is the first miui 12.... rom that don,t incrypt my phone after a first boot

Is there maybe any new Ported from Mi 10 Lite rom ?

Can anyone help i can't understand ?
i flashed twrp with universal dm verity
then i wipe dalvik/art cache / system /data /vendor
then i format using format data by typing yes
then i copy custom rom either in internal storage or usb otg
then i flash the rom
then clean dalvik cache
then i format typing yes
then reboot to system
it erases my custom rom and reboot to recovery in case of miui 12.5 android 11
but incase of lineage os 18 it does not and boots in os perfectly
can anyone tell why?
also why it is not installing in system partition rather on the internal storage
i am using redmi note 4
rom: MIUI_GLOBAL_HMNOTE4_12.5.9.0-11
Note:why i need factory reset is to encrypt to use banking and fintech apps
factory reset enables encryption after installing
but if i not do the factory reset the does not encrypt in anyway but rom works

LuvSingh98 said:
Can anyone help i can't understand ?
i flashed twrp with universal dm verity
then i wipe dalvik/art cache / system /data /vendor
then i format using format data by typing yes
then i copy custom rom either in internal storage or usb otg
then i flash the rom
then clean dalvik cache
then i format typing yes
then reboot to system
it erases my custom rom and reboot to recovery in case of miui 12.5 android 11
but incase of lineage os 18 it does not and boots in os perfectly
can anyone tell why?
also why it is not installing in system partition rather on the internal storage
i am using redmi note 4
rom: MIUI_GLOBAL_HMNOTE4_12.5.9.0-11
Note:why i need factory reset is to encrypt to use banking and fintech apps
factory reset enables encryption after installing
but if i not do the factory reset the does not encrypt in anyway but rom works
Click to expand...
Click to collapse
Try format data yes and reboot twrp then your procedure:
then i flash the rom
then clean dalvik cache
then i format typing yes
then reboot to system

Laptapper said:
Try format data yes and reboot twrp then your procedure:
then i flash the rom
then clean dalvik cache
then i format typing yes
then reboot to system
Click to expand...
Click to collapse
I strictly followed your suggested procedure but still it is not booting into os rather miui logo flashes for 5 mins then it reboots to recovery. Can you please explain what i am doing wrong or may be it is due to rom designed to be create a partition on mobile sd ext memory (not external sd card) and not on system? These are my initial observation.

LuvSingh98 said:
I strictly followed your suggested procedure but still it is not booting into os rather miui logo flashes for 5 mins then it reboots to recovery. Can you please explain what i am doing wrong or may be it is due to rom designed to be create a partition on mobile sd ext memory (not external sd card) and not on system? These are my initial observation.
Click to expand...
Click to collapse
Which twrp you're using?
If newest then I suggest to start from scratch with stock ROM and flashing via miflash (don't relock bootloader)

twrp-3.6.0_9-0-mido twrp i am using
start from scratch ? Can you suggest which stock rom should i use and why not use twrp?
I think it is the feature of rom to force encryption on device rather then a recovery tool.But i will try as you said.
Thank you for replying to my query. Wishing you a Happy and joyous New year.

LuvSingh98 said:
twrp-3.6.0_9-0-mido twrp i am using
start from scratch ? Can you suggest which stock rom should i use and why not use twrp?
I think it is the feature of rom to force encryption on device rather then a recovery tool.But i will try as you said.
Thank you for replying to my query. Wishing you a Happy and joyous New year.
Click to expand...
Click to collapse
Mido? Here's the sweet thread.
Checkout threads belong to your mido

Links are down, here's a mirror to archive.org: https://archive.org/details/sweet-21128
Yes, it's slow but it's my only way to keep it up without having a risk of it being randomly gone.
P.S. 9.07.2022 RN10PM/RN10PI (K6I/K6P) users, sorry for the bad description! It does work on all sweet(in) boards, however I tested on sweet - K6G.

Development [RECOVERY] [11] [star/mars] [OFFICIAL] TeamWin Recovery Project

Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11 Pro/Ultra
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_star
https://github.com/TeamWin/android_device_xiaomi_mars
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download:
star: https://twrp.me/xiaomi/xiaomimi11ultra.html
mars: https://twrp.me/xiaomi/xiaomimi11pro.html

Wow
Finally, official TWRP for our device, thanks alot to dev

when i flash it ,i can`t mount my /data
my device is mi 11 star

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
Are you on android 12?

Nebrassy said:
Are you on android 12?
Click to expand...
Click to collapse
yes

347111268 said:
when i flash it ,i can`t mount my /data
my device is mi 11 star
Click to expand...
Click to collapse
on android 11 the same......

Edlar said:
on android 11 the same......
Click to expand...
Click to collapse
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt

Nebrassy said:
Send logs
adb pull /tmp/recovery.log
adb logcat > logcat.txt
Click to expand...
Click to collapse
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
did you try if its connected by typing fastboot devices?

jiyuugataki said:
Hi there !
Can't mount /data neither Mi 11 Star on A12 (latest weekly EU Rom), removed password before fastboot boot twrp.img
Tried to adb pull /tmp/recovery.log, but :
adb: error: failed to get feature set: no devices/emulator found
you do this on fastboot mode, right ?
Thank you
Click to expand...
Click to collapse
Try going to mount menu, disable mtp and enable it, then check id adb is recognized

Nebrassy said:
Try going to mount menu, disable mtp and enable it, then check id adb is recognized
Click to expand...
Click to collapse
Worked, here are the logs
Thx !
Edit : That's strange, when i try to attach files, they upload and then disappear when i save
so, recovery :
recovery.log - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
logcat part1 : https://pastebin.com/ZPenY56E
part 2 : https://pastebin.com/6MYkJs5R

marcel112 said:
did you try if its connected by typing fastboot devices?
Click to expand...
Click to collapse
Tried and no problem
But, solved, thank you nonetheless

Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?

datadelrey said:
Hello everyone, I can't access to my data in TWRP completely because I want to flash magisk; any solution?
Click to expand...
Click to collapse
did you remove password or pin?

Great news!
I am wondering if there is a roadmap when TWRP will be available for A12?

{
"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"
}
Everything is fine, a log file appeared after I backed up the boot, I hope it's useful

please make a clear tutorial on how to fix the unable to mount/data
i removed the pin and password before fastboot boot twrp.img, go to advanced flash current twrp, and when i restart the device it goes to fastboot again.

Nebrassy said:
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Click to expand...
Click to collapse
How to update if we are currently use a different TWRP? I mean not "official".

Mi 11 Ultra / star
Using EU 12.5.20 and twrp 3.5.1
Update to 3.6.0 via Install Zip in 3.5.1
Reflash EU rom after update twrp and booted normally now.
Working fine. Thank you.

@hacker738 and now check, which version of TWRP is installed
if 3.6.0 then I'll really congratulate you