Database Develop

[RECOVERY]Revolution Recovery Nougat {16-03-17} RC2

{
"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"
}
ONLY FOR NOUGAT FIRMWARE​
Working:
ADB
If can possible make a mount / backup or restore any partition, included DATA, restore, backup, flashing...
The settings are saved on CUSTOM partition, and BACKUP's on external storage
MTP
Dont working:
Tell me
Changelog:
RC2 16-03-2017:
Updated UI
New logo and splash screen
Fixed errors on Backup/Restore
Optimized the code
RC1 11-03-2017:
Updated to TWRP base 3.0.3
Data in whole recovery, mount, unmount, backup, restore, flashing .zip files... NO MORE NEEDED DOWNGRADE TO MM
ADB Now can send command and receive
Optimizations...
b9 15-12-2016:
MTP and ADB works at init thanks to: @LastStandingDroid
ADB Keys working thanks to: @LastStandingDroid
Deleted unneded stuff
b8 14-12-2016:
Reworked MTP
Reworked with kernel B336
Updated banner with correct version of recovery
b7 13-12-2016:
Reworked MTP
Removed unnecesary files
Removed DM-Verity v2
b6 08-12-2016:
New Init logo and banner
Deleted parameters for MOUNTING DATA
Deleted splash2
Reworked init.rc and fstab
b2 03-12-2016:
ADB works but no "auth"
MTP works
Backup & Restore of all patitions working (no DATA backup)
Settings of TWRP saved on CUSTOM partition
b1 02-12-2016:
First version working on Nougat
Images
Attached in bottom of the post.
Download:
For install in Android MM (if dont are now in Android N) or for install in Recovery Nougat b*: https://mega.nz/#!tE1XXIaK!ICq1NO1DpLedfdgB0j5DzH4xtEN6jcz2Di8UXfcqSBE
recovery.img for install with Fastboot: https://mega.nz/#!gU91XJjI!V3RcPQ0tDeFNBJAu04cI1gxMqDypEdxs6TQHGF3h0_o
Regards

BadWolfYe said:
​
Working:
All dont listed in "Dont Working"
Dont working:
ADB
USB MTP
Mount and manage DATA
Download:
For install in FASTBOOT: https://mega.nz/#!JcNCADDA!f4EvXvIJYEPkALmUrG5WDhB-u7pRpcDZ5DvQpQpxlD8
For install in Android MM (if dont are now in Android N):
Im working in fix the error listed up, when i fix all, i work in Revolution Recovery for NOUGAT
Regards
Click to expand...
Click to collapse
Is for VNS-L21 ? Or not?

Why is this called Android Nougat?

The named its called for only work on Android Nougat Firmware....
Adb/mtp fixed...
Working on data partición fix

Oh god i hope you get it sorted, your my last hope with my brick ..... **** me

WTF?
This is no a job, dont need a review for employer's HAHAHAHAHAHA
News:
Data partition still no working...
In this moment recovery save the settings in CUST partition
Backup of all listed partitions CORRECT (tested)
Only can backup to external sd
ADB no work "unathorized" but MTP yes, for activate, go to mount and disable mtp, after, reenable mtp... an boila!
Installation fails at 7 status error (in this moment caused by data partition)
im deleting all unusued stuff on recovery, and upload in the next hours... BETA 2 xd

OP updated

I do not mean to be rude and I appreciate your work, but how is this different from the regular TWRP and from TWRP by Meticulus? I mean there are two rock-solid versions of TWRP, what is the added value of flashing this one?

Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...

BadWolfYe said:
Anyone READ the TITLE?
This is FOR NOUGAT boot only on NOUGAT firmware and another olds TWRP NO... this is the only recovery boot on NOUGAT...
Click to expand...
Click to collapse
My apologies, I feel super stupid now. Thanks for your contribution!

Thanks for your work

Thread cleaned of stupidity. Next time we'll talk privately. :good:
Cheers,
Darth
Senior Moderator

TWRP not picking up internal storage, please help.

Recovery updated and reworked...

Hello
I do not understand, I can not manage to make it work.
He shows me cust 177mb
Internal storage 0mb
Micro sdcard 0mb
And I get to nothing. thank you
I understood

BadWolfYe said:
Recovery updated and reworked...
Click to expand...
Click to collapse
Now can i flash directly on the reworked twrp? Like if im going to reflash the b329 + data files? And also the camera fix?

Is there somewhere already a supersu file for root
Then you could root it and then downgrade with toolkit because the twrp he has fixed and thus you could zip the zip yes
Thank you for your great work

Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?

ExodosPL said:
Hello, I'm trying to install this Recovery for my P9 Lite in Nougatt, if i in ADB send a command:
"fastboot flash RevRecNP9Lite.img"
I have a error:
"unknown partition 'RevRecNP9Lite.img'
error: cannot determine image filename for 'RevRecNP9Lite.img"
Where is the problem? In ADB?
Click to expand...
Click to collapse
It must be "fastboot flash recovery RevRecNP9Lite.img"

Thank You, it works

[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...

[Guide] How to decrypt data partition, and re-encrypt data partition on OnePlus 5

Because there are too many people ask about "how to decrypt data" and "how to re-encrypt data",
I write a guide to tell you how to decrypt/re-encrypt data partition.
[Change log for V2:]
1. Update script to no-verity-opt-encrypt-6.0.zip
2. Decryption support for Android Oreo and Android Nougat
[Why we need decrypt data partion?]
1. Install MultiRom/MultiBoot
2. Some Roms only work on decrypted device
3. For better performance
[Disadvantage]
1. Low security (Cracker can access your file, and remove lock screen pin from TWRP)
2. It need to wipe your data/internal storage to decrypt data partition.
Decrypt data partition with magisk:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer Rom and no_verity_op5_v2.zip to the device over MTP
3. Go to “Install” section, select ROM, and swipe to confirm the flash
4. Go to “Install” section, select magisk.zip, and swipe to confirm the flash
5. Go to “Install” section, select no_verity_op5_v2.zip, and swipe to confirm the flash
6. Reboot
PS. you should format data before flashing no_verity_op5.zip.
Re-Encrypt data partition:
1. Go to “Wipe” section, tap “Format Data”, and type “yes”
2. Transfer stock Oxygen Rom to the device over MTP
3. Go to “Install” section, select the Oxygen rom, and swipe to confirm the flash
4. Reboot
[Proof]
No magic here. What you see is real.
[How it work?]
OnePlus 5 uses FBE(File-Based Encryption) to encrypt data partition.
The latest no-verity-opt-encrypt zip ( https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ ) only replace "forceencrypt" to "encryptable".
It didn't replace "fileencryption", so your data partition is still encrypted.
In order to decrypt data partition, I modified the no-verity-opt-encrypt.zip by myself.
The no_verity_op5_v2.zip will replace "fileencryption" to "encryptable".
boot.img/ramdis/fstab.qcom
{
"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"
}

Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..

aneeshmbabu said:
Mtp transfer means .. I tried after wiping format data I tried to transfer the required file by using my laptop with original data cable , but data transfer is showing but not transferring actually waited a long .. but no transfer happens ..
Click to expand...
Click to collapse
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.

snowwolf725 said:
You need reboot recovery, before you use MTP.
In order to use MTP, you need remount your data partition.
Click to expand...
Click to collapse
Hi thanks for the replay , presently i flashed twrp and magisk also I'm in Franco custom kernel , so can i possible to decrypt data,
I'm very new in one plus 5 , coming from Motorola phones , so kindly give me a step wise process for a beginner .. thanks in advance ..

Does no_verity_op5.zip still work after system update?

sinnbro said:
Does no_verity_op5.zip still work after system update?
Click to expand...
Click to collapse
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.

snowwolf725 said:
[Why we need decrypt data partion?]
4. For better performance
Click to expand...
Click to collapse
Does someone know what "better performances" means ?
I decrypted my OP3 but honestly I didn't noticed any change in performances (except opening TWRP)...

According to this process, can I also decrypt the stock rom?

snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Thanks

snowwolf725 said:
No, you need re-flash it after system update.
Because system update will replace boot with stock version.
If you forget to re-flash zip file, your device will unable to boot.
Click to expand...
Click to collapse
Or worse, the device will boot fine and proceed to encrypt your drive...

Why is magisk required?

ChavitoArg said:
Why is magisk required?
Click to expand...
Click to collapse
You don't need to flash magisk, if you don't want it.
Fif_ said:
Or worse, the device will boot fine and proceed to encrypt your drive...
Click to expand...
Click to collapse
Yes, you are right.
It will also encrypt your device.

So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.

ChavitoArg said:
So in order to remain unencrypted i have to flash this after a custom kernel, dont they include this feature already? Sorry for the questions, but im new to this device.
Click to expand...
Click to collapse
Yes, you have to flash it every time you write the boot partition: flash a ROM or OTA.
Note that if you use Magisk, Magisk by default automatically turns off DM Verity and force encrypt, so there's no need to flash both no_verity_op5.zip and Magisk, just Magisk is fine.

snowwolf725 said:
[Why we need decrypt data partion?]
...
4. For better performance
Click to expand...
Click to collapse
Really ?

I have a few questions for the sake of clarity, as an experience I had makes me question if Magisk handles this. Blu_spark kernel will not boot when flashed with Magisk on my decrypted, stock OOS device - I believe status of encrypted/decrypted and FBE are two separate things based on the reply from eng.stk. it seems to use that kernel while decrypted, I still need to flash no-verity zip, even with Magisk.
This thread states both that you don't need to flash this if using Magisk, but that you need to flash this anytime you modify boot IMG - ROM flash, OTA, etc. I'm trying to nail down when I need this zip and when I don't - very curious if there's some solid info on when to use this in flashing and when not to. Guide is great as is for decrypting - just wanna stay that way.

@wrongway213
Hi,
maybe this will help you: https://forum.xda-developers.com/showpost.php?p=73311252&postcount=114

is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs

HonPig said:
is decryption needed for xposed as official release has come out?
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
No, new version of xposed supports encrypted data partition.

Which twrp is recommended for decrypt device?

Xposed framework not working on my Oneplus 5, Ressurection Remix V 5.8.4

I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
{
"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"
}
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?

Jonathanve said:
I rooted my device,
And Installed the xposed application,
where I flashed the "sdk25 arm64" zip file.
If I open for let's say Snapprefs, It tells me the module is not activated
I activated the module and rebooted,
any help?
Click to expand...
Click to collapse
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard

fjsferreira said:
Your problem is probably the same we encounter in stock OOS of OP5.
Try this:
boot the phone, and then do a soft reboot.
This happens because of file encryption prevents xposed from access the module list in /data/ partition at boot (because files are encrypted, meaning you haven't enter your pass/pin, when xposed tries to read them).
If you do a soft reboot (the option is available in the framework screen), then it will work.
Click to expand...
Click to collapse
Hello, I want to confirm that this was a temporary solution, It seems like soft rebooting device made it work,
thanks

I also use OP5 on stock Oxygen OS 4.5.10, Magisk 14 and systemless xposed 87.3 by topjohnwu. I have the same problem but it doesn't get fixed even if I soft reboot through the Material Xposed Installer app. What exactly am I supposed to do?
Στάλθηκε από το ONEPLUS A5000 μου χρησιμοποιώντας Tapatalk

Jonathanve said:
I noticed that it tells me my phone is encrypted, any idea how to decrypt?
I tryed formatting data and reinstalling the ROM,
It seems it's encrypted by standard
Click to expand...
Click to collapse
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.

Face_Plant said:
To decrypt you need to format data in TWRP then install a kernel that does not force encryption.
Click to expand...
Click to collapse
Or you can run with FDE with: https://forum.xda-developers.com/showthread.php?t=3672477
You will lose the ability to boot unattended, so alarm when phone is off and scheduled boot won't work. And you'll have to format data too...
It's worth the inconvenience in my opinion. Been running this way for several days without any issues.
Full disclosure: I wrote the FDE conversion utility linked above.

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.