Question Leave data unencrypted - Xiaomi Poco X3 Pro

Hello! Is there any possibility now to leave data partition unencrypted?
Tried to install miui.eu with PBRB with dfe toggles enabled - no result.
Tried to install same through TWRP + latest dfe - no result
Tried to install havoc treble + dfe - no result.
Am I missing something?
UPD
I've created DFE patch for 12.0.6.0 xiaomi.eu firmware
Original firmware is hosted here
xiaomi.eu_multi_POCOX3Pro_V12.0.6.0.RJUMIXM_v12-11.zip | by Xiaomi.eu for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Patch is here.
Яндекс
Найдётся всё
disk.yandex.ru
You should replace files in original firmware with files from patch and flash it through recovery
I also flashed latest DFE(may be not beeded)
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
And latest stable magisk(may be also not needed)

If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?

kamild_ said:
If your data partition is encrypted right now, you have to format it first, then flash DFE to prevent encryption. I'm guessing that's what you did?
Click to expand...
Click to collapse
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru

Aaaaand I've done it. Works perfectly. Now uploading

What's the pros of leaving data unencrypted?

Do we have to do this unpacking and repacking process for every new version of stock ROM?

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
The only real benefit I know of is being able to switch between different ROMs without having to format data - it would still be recommended to wipe it, but you would be able to preserve your internal storage between ROMs.
Theoretically there's also some performance that you could reclaim by getting rid of encryption, but on such powerful SoC any gains would not be noticable maybe outside of benchmarks.

qwert8988 said:
What's the pros of leaving data unencrypted?
Click to expand...
Click to collapse
Minor CPU performance and NAND lifetime gain. Also if you somehow clear contents of /metadata partition - you will loose all of your files on /data partition ( and internal sd as /data/media too).
Also several years earlier days I've faced a problem when new firmware can't decrypt data after previous one(it was in lolipop times as I can remember). So, if I can preserve /data unencrypted - I'll try to do so.
qwert8988 said:
Do we have to do this unpacking and repacking process for every new version of stock ROM?
Click to expand...
Click to collapse
Seems yes, at least for now. Not for every rom, just for vendor part.
You can apply this patch to any rom based on 12.0.6.0 vendor. You'll only have to edit original dynamic_partitions_op_list file from rom archive - replace "resize vendor" string with
resize vendor 1563119616

Thanks for the work. Confirmed worked on ArrowOS build 2021.05.04. Flashing dfe and masgisk are not necessary

Thanks !!! It works !!! This is what I have been looking for...
{
"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"
}

vodkinagdan said:
Yes, i did it and it was not helpfull. Seems that i've found something. Looks like I should repack vendor image with patched fstab.qcom and then reflash it through fastbootd. Because of superimage dfe patch cannot replace this file(vendor is RO even in recovery mode)
For now i've found this project, seems exactly what I need
®Unpacker Kitchen for Android(UKA). - 4PDA
®Unpacker Kitchen for Android(UKA)., Перепаковка и монтирование образов на телефоне.
4pda.ru
Click to expand...
Click to collapse
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.

Haldi4803 said:
So.... To get an unencrypted phone on Android 12 Custom ROMS you still need to flash patched Vendor?
Twrp 3.6 for 12 can't encrypt System/User data.
So to create backups one would need an unencrypted phone. Correct?
To switch between different Android 12 Custom ROMS with Userdata and system ready to flash back.
Click to expand...
Click to collapse
If rom is based on OSS vendor - for android 11 this patch working well now. You can try it on A12

Related

GSI/DSU Flashing

How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?
ArletPDR said:
How is the proper way of installing GSI images? I have tried TWRP method and Fastboot method, neither of them works. Is it even possible on this device?
Fastboot method gets error @ "fastboot erase system" (remote: Check device console)
BL Unlocked ofc and adb/fastboot is up to date as well drivers
TWRP - i lose all my partitions for some reason and have to MSM back to working state
GSI i tried https://developer.android.com/about/versions/12/gsi-release-notes#downloads
This is my first fully treble supported device and i actually do not know how A and B partitions behave while doing gsi/rom flashing. Perhaps someone can explain it?
Click to expand...
Click to collapse
The 8T is not only an A/B device, it is also a virtual A/B device. I'd be very surprised if you could get a"normal" A/B GSI to boot on an 8T.
Virtual A/B Overview | Android Open Source Project
source.android.com
There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
{
"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"
}
ArletPDR said:
There is this Dynamic System Updates feature, i have used it earlier to test android 12 GSI
But now I'd ike to delete wherever those GSI's stored, so that i possibly can test other GSI there is
View attachment 5374671
Click to expand...
Click to collapse
Click discard on the notification of dynamic system updates.
If no notification then the gsi is deleted
I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)
ArletPDR said:
I did that in hopes that it clears this dsu dialog up from those that is there now, but no, they are still there and i can use them if i want. it's like they are stored somewhere? (i have no other GSI type file stored on my local storage btw)
Click to expand...
Click to collapse
Do you mean that the installation of the dsu is so fast that it is impossible to download a 3gb GSI in such a short time?
Well, i did not know that it requires internet connection, i always tough it uses file from local storage
ArletPDR said:
Well, i did not know that it requires internet connection, i always tough it uses file from local storage
Click to expand...
Click to collapse
It also occured to me, only takes a few minutes to install dynamic system.
To me though, when I discarded the GSI at that instant there will be a few gigabytes freed and that is a sign of the GSI deleted.
For me it takes a while tho
All the DSU magic happens in this folder
Tried deleting the gsi there?
It was empty before i started dsu installation, also i have no dsu install file on internal storage download folder, that proves the fact that is takes dsu file or filename from internet, because when i rebooted i was greeted with OOS, the same i have primarily installed, with only 4gb on internal storage, and i made screenshots there, but they're gone now.. obviously
LR7875 said:
Tried deleting the gsi there?
Click to expand...
Click to collapse
No i did not, discarding from notification panel did just that

Medion (Lenovo) P1060x Tablet - ROM [Stock debloated], TWRP, Magisk Kernel

Hey!
Normal I'm just reading here and don't contribute something, but since I've got that old fully bloated Tablet I'm trying to port something on my own. First because I broke the Tab, now because I have time for some experiment and the tablet was just a gift so never mind if it's broken or not. Hopefully it stays alive.
Till now there is no shiny Custom ROM, but I'm trying to Port! What you found here is a debloated Original System, that's nearly looking Stock Android, a new Splash.img without the Medion branding, and also an Updated TWRP 3.6 that runs annoying slow.
The Files are present as they are, I don't know when I Update things or debug something. It runs on my Tab, maybe it doesn't run on your Tab. Be sure to back up your System with the given TWRP. External SD-Card work even with 128 GB for me. So enough Space to save all partitions. The TWRP doesn't work well with secured data partition, so you have to back up every Partition one by one. The Boot.img is patched with Magisk 24.3
Click to expand...
Click to collapse
U need to install Gapps because I delete all Google Services.
Also, the Obsolete Keyboard and the Launcher is gone from System.img! So if u flash it and can't do anything, u have been WARNED!
Unlocking Bootloader is necessary to Flash boot.img, TWRP.img and so on! Use the Search if u don't know how.
The Image is in Sparse format to used with fastboot, if u don't know how … you know, the Search thing.
just to
Spoiler
Flash things
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash splash splash.img
fastboot flash recovery twrp3.6.1_9.0.img
fastboot erase userdata
Prefer Aroma Installer to be used found on OpenGapps for Google Apps or a Working Keyboard and Launcher, but we don't have that much Space the Full Gapps are at Maximum Capacity.
Downloads: ///Links obsolete, reupload later///
System.img
Boot.img
TWRP.img
Splash.img
TWRP Boot Splash All-in-One
Hint: Right-click on the Download Banner, then "Save as" to Download with that Hoster
Cheers
Everyone likes pictures here, I guess:
{
"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"
}
Changelog:
Update:
0.3
Add Kernel RAW files (Kernel.zip) Not Flashable
0.2
Kernel patched to last Version V3.7 with Magisk Support
Modified Splash.img
Modified TWRP to 3.6.1_9.0 (starts annoying slow, MTP works, Sideload broken)
Debloded System.img
0.1
Modified TWRP 3.2.1.0 (Kernel V3.0)
Enabled ADB Sideload / MTP (unstable)
Disabled Vendor (Tab have no Vendor Partition)
0.0
TWRP 3.2.1.0 - Ported with Team Hovatek Porter (Kernel V3.0)
Do you also maybe have the system image of oreo? i tried flashing a GSI and generic twrp, with your twrp it worked but the GSI didnt want to boot up
vinnievh said:
Do you also maybe have the system image of oreo? i tried flashing a GSI and generic twrp, with your twrp it worked but the GSI didnt want to boot up
Click to expand...
Click to collapse
Sure, here you go! system.img
I didn't try till now what ROM work or not. I'm thinking about porting some ROM, but I'm not that good at programming.
Thank you so much! i have been searching for AGES
not to be stupid but the anonfile link is so. slow. i dont know if its me but it doesent work
vinnievh said:
not to be stupid but the anonfile link is so. slow. i dont know if its me but it doesent work
Click to expand...
Click to collapse
The hoster is slow, yes. What does not work for you?
when not logged in i only get 500 kb/s, and after 1.5gb it says network problem, when logged in only the speed changes 500kb/s more.. but the problem is still there
its really annoying
vinnievh said:
View attachment 5579553
its really annoying
Click to expand...
Click to collapse
That's the stock system.img V3.0 the debloated V3.7 is packed with 7zip and smaller.
Thanks! that should work now
the image works. but twrp keeps saying its encrypted and i cant boot into android. whats the password!?
vinnievh said:
the image works. but twrp keeps saying its encrypted and i cant boot into android. whats the password!?
Click to expand...
Click to collapse
That's because data is not encrypted with the kernel.
Be sure that you delete data partition once you flashed the modified System Partition.
Code:
fastboot erase userdata
Data will be crypted at next full boot, there is no encryption till now. The boot take for me 5-6min.
Hello, its some months ago but im still trying to get it working. i got to a point it boots into recovery saying "Cant load android system, ur data may be corrupt. If u continue to get this meassage, you may need to perform a factory data reset" Its just getting to my nerves and i want this to finally work.
vinnievh said:
Hello, its some months ago but im still trying to get it working. i got to a point it boots into recovery saying "Cant load android system, ur data may be corrupt. If u continue to get this meassage, you may need to perform a factory data reset" Its just getting to my nerves and i want this to finally work.
Click to expand...
Click to collapse
Hey, just been a while not on XDA.
Have you performed a factory reset? You could also use adb commands to do this, or you use AROMA Installer to erase everything if TWRP don't work on ur tablet.

Doogee N20 - Some phones are just hard to modify

After finally unlocking the bootloader, installed TWRP 3.6.0 and rotted with Magisk v23.0. Lets find a custom ROM that suits this phone - WRONG!
I have tried many types of ROM and so far it ends in soft brick. Need advise if you have any. My aim is to install a basic custom ROM , install pico or nano GAPP, and only install like 4 apps on it. phone, sms, navigation, music player etc.
I have tried the following ROM:
Phhusson-treble AOSP andriod version 9, 11 & 12.
GSI arm64 ab ROM
a so call stock ROM
I also tried installing the vendor.img as described here
I would like to use LineageOS but there doesn't seem to be one for this phone
I am now resorting to installing the stock firmware to make the phone work again, instruction here
If anyone has sucessfully rooted this phone using a basic ROM and GAPP please share how you did it and where your download was.
Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.
Fytdyh said:
Why did phhuson fail ? That's the basic gsi, every other gsi are build on top of that. If that doesn't work, nothing will.
Click to expand...
Click to collapse
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .
jackjack1885 said:
I install - system-arm64 –ab
I did some research that the Doogee n20 is a arm64 and a+b .... Unless I got the wrong information.
I suspect there maybe some stock firmware files that needs to be installed as well to make it work properly.
A post said it needs vendor.img, I might try sourcing another copy.
Follow up - I got it un-bricked with the stock firmware (android 9) (link in my original post) .... Back to square one .
Click to expand...
Click to collapse
Search treble info, it will tell you exactly any treble related information.
Fytdyh said:
Search treble info, it will tell you exactly any treble related information.
Click to expand...
Click to collapse
Many thanks, didn't do that step.
Did it now, it shows it needs system-arm64-ab
I got the right one. Not sure about the VNDK 28.0 doesn't really say on the webpage.
{
"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"
}
Tried android 9 (the phones original version) 11, and 12..... No luck.
follow advices from this https://forum.xda-developers.com/t/doogee-n20-twrp.4136331/
and this https://forum.xda-developers.com/t/...loop-after-any-custom-rom-doogee-n20.4357313/
Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot
AtS17 said:
Hey man, did you get it fixed?
Actually this device is A-only, but you should use Gsis A/B.
Most Phh based Gsi works almost perfectly for me.
You can try this:
- Download and install Twrp 3.6.1 here
- Download LineageOS 18.1 (lir) here Choose "arm64 bvZ" version
- Download stock rom here or Y9Plus variant here
- Extract the Gsi, and the vendor image from the stock rom
- I restarted in Twrp, go to wipe and select system, data, cache...
- Go install and flash the Gsi as system image, and vendor as vendor image
-reboot
Click to expand...
Click to collapse
Thanks for the links!
Are you able to add this old firmware please? https://cloud.mail.ru/public/mCzU/5PX4cKPfH
I can't download it, i found it on 4pda (Mod Action: Link removed)
I'm trying to delete the red "TEE key not write" message.

Development [TB-J716F] TWRP for Android 12 / ZUI 14

Hi, people!
Spoiler: Old message:
Porting our TWRP for A12 (ZUI 14.0.127).
Now it's fully working, exept touchscreen. But with mouse connected via OTG you can to do all neeeded operations.
IMPORTANT! The method of decrypting /userdata is not implemented there (different from A11), so you need to install the DFE-NEO patch to make it work properly with your data.
EDITED: New version v5
Added ability adb/MTP on encrypted /data.
MTP works on demand, pressing Disable MTP-Enable MTP, displays SD card only.
UPDATED Febr. 08:
Built a new full-featured version with data decryption from source. For Android 12 - ZUI 14
Decrypts data by default, if the tablet is not protected.
If it's protected by pin/password, it asks for it and decrypts internal storage.
I haven't tried the pattern, see here: https://twrp.me/faq/openrecoveryscript.html (Specific pattern decrypt note), try it yourself.
Device tree lies here: https://github.com/F1tm0t/twrp_device_lenovo_J716F
Many thanks to:
Yahoo Mike - for useful tips on decryption implementation and general support.​LSS4181 - for Q706F device tree, I used it as a basis for mine.​Ungeskriptet - for his J716F device tree for A11, it was useful for me.​TWRP_J716F_A12_DD. img DD means Data Decryption.
Working: Everything, excluding vibration.
MEGA
PS.
Welcome to collaboration.
I have another variant of TWRP with a malfunctioning touch. The pressure points do not correspond to the position of the buttons. It need to add some calibration files or the right firmware or the right driver for the screentouch. This is too complicated for me I'm just advanced user, no guru.
Please, write me in PM if you can help with this issue.
Nice to see some development for the TB-J716 tablet XD since the developer don't want to release the kernel source/ open source to the public.
Die you add the firmware for touch to TWRP? I have it like this in my TWRP port: https://gitlab.com/ungeskriptet/and...tree/android-11/recovery/root/vendor/firmware
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.
Ungeskriptet said:
I suggest you extract the firmware yourself from the latest ZUI, the older versions might not work.
Click to expand...
Click to collapse
Yes, I was trying this.
Thanks for the tip. I have a couple of questions. I'll write you in PM, if you don't mind.
Version with working touch is here:
Файл из Облака Mail.ru
Вам открыли доступ к файлу. Отправлено с помощью Облако Mail.ru.
cloud.mail.ru
and here:
100 MB file on MEGA
mega.nz
Remember, you can't to backup data before using DFE-NEO patch.
Many thanks to Ungeskriptet for helping.
To be continued (I hope)
New version for ZUI 14 with new features:
* added many partitions for backup/restore
* added some partitions for flashing via Install IMG
* A set of partitions is enough to backup/restore an entire OS
Placed here. To see how it works, click here:
Spoiler: Youtube
FFBM mode is my mistake, wrong button pressed, no need
Hello @f1tm0t
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Could you help to edit that value? I tried many tool to rebuild TWP with new prop but no luck, device bootloop
Thanks
phamthanh said:
Hello @f1tm0t
Click to expand...
Click to collapse
Hello, friend.
My TWRP works with adb/MTP quite excellent.
The following is needed:
decrypt /data
permission in the system to debug from this computer
Spoiler
{
"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 your help, I will redownload and double-check again.
Hi @f1tm0t
I re-download and flashed v3 but the same result
Could you help me to check it
Thanks
phamthanh said:
I re-download and flashed v3
Click to expand...
Click to collapse
I offer version 4: https://mega.nz/file/g4VBnIpC#_4_x0b3V-Z6oSoXDA2xbHSN7hBKXRgjnwfFMLfPcYXA
My version cannot decrypt /data, so you have to install the DFE-NEO patch from TWRP.
After rebooting to OS you must to enable USB debugging, it create adb.key in /data.
And after rebooting to TWRP you can use adb/MTP, because TWRP sees adb.key in not-encrypted /data.
phamthanh said:
The TWRP seems unable to use ADB shell due to ro.adb.secure=1
Click to expand...
Click to collapse
Made new version (in the title), adb works by default. Enjoy!
f1tm0t said:
Made new version (in the title), adb works by default. Enjoy!
Click to expand...
Click to collapse
Many thanks
Updated.
New TWRP with working data decryption, see update in topic.

[TWRP][ARM64]Unevirsl Rom Installer for android | Auto Repack Rom | MFP-NEO | Fastboot to twrp flash

Unevirsl Rom Installer for android | Auto Repack Rom | MFP-NEO | Fastboot to twrp flash​Let your device install fastboot rom via twrp​
State - Alpha
Build - 0.0.1
Spoiler: Screenshots
{
"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"
}
Support format rom supported:
fastboot with super into "sparse or row"
fastboot with single sub-partition like Vendor system "sparse or row"
new.dat ( soon )
payload.bin ( soon )
new.dat.br ( soon )
Just specify the name of the ROM archive, or the path to the ROM in the config.txt file located inside the archive, and run this zip through TWRP
Be careful, all image names must match the name of the partition like boot.img|vendor.img|super.img|xbl.img withou slot suffix, if you do not follow this rule, you can get a hard brick. Only available on slot _A, if script is run on slot _B there will be an error​
I was finally able to make a working stub for MFP-NEO either URI or AutoRepack. I made the main logic, it remains to cram the functionality
DOWNLOAD - SourceForge
TG Group
Telegram support chat for quick feedback
Donate only TG link https://t.me/mfpupdate/47
URI summary : Support for installing different ROM versions will be implemented, additional support for reading installation files. "First install - then patch" mode - a function that first installs the ROM using the means that the developers put in the installation package, and only then everything else will be patched based on the already installed firmware, as well as support for factory fastboot ROM formats that manufacturers provide for Miflash, for example, and etc
Summary of DFE-NEO. I'm going to study the wonderful script Zackptg5 Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I used before the implementation of my project, in some cases my script does not work properly on some, those problems that are in DFE-NEO have already been studied and understood because for which it does not work properly, but to implement a set of problems, some parts of the code need to be rewritten, and this is not subject to manual correction by the end user.
My Telegram support group and link to full message blog
LeeGarChat said:
Unevirsl Rom Installer for android | Auto Repack Rom | MFP-NEO | Fastboot to twrp flash​Let your device install fastboot rom via twrp​
State - Alpha
Build - 0.0.1
Spoiler: Screenshots
View attachment 5801927View attachment 5801933View attachment 5801929
Support format rom supported:
fastboot with super into "sparse or row"
fastboot with single sub-partition like Vendor system "sparse or row"
new.dat ( soon )
payload.bin ( soon )
new.dat.br ( soon )
Just specify the name of the ROM archive, or the path to the ROM in the config.txt file located inside the archive, and run this zip through TWRP
Be careful, all image names must match the name of the partition like boot.img|vendor.img|super.img|xbl.img withou slot suffix, if you do not follow this rule, you can get a hard brick. Only available on slot _A, if script is run on slot _B there will be an error​
I was finally able to make a working stub for MFP-NEO either URI or AutoRepack. I made the main logic, it remains to cram the functionality
DOWNLOAD - SourceForge
TG Group
Telegram support chat for quick feedback
Donate only TG link https://t.me/mfpupdate/47
Click to expand...
Click to collapse
Why only in Slot A?
azteria2000 said:
Why only in Slot A?
Click to expand...
Click to collapse
azteria2000 said:
Why only in Slot A?
Click to expand...
Click to collapse
Because the first alpha version does not provide for the reassembly of super, and re-partitioning. if you install fastboot firmware with super included. then this will cause problems, since the system partitions are located in slot _a and everything else will be installed in slot _b
LeeGarChat said:
Because the first alpha version does not provide for the reassembly of super, and re-partitioning. if you install fastboot firmware with super included. then this will cause problems, since the system partitions are located in slot _a and everything else will be installed in slot _b
Click to expand...
Click to collapse
No problem on Android 12 Motorola Qualcomm XT2215-4 SM6375.. For either. Dfe-neo I use every flash to kill decryption at first before I put my custom fstab.qcom in vendor after getting RW thanks to you guys. But I didn't know about the ROM flash tool. Two-part question number one what's going on with the source forge website all the files are missing? And part two, I've got a friend that has a arm7 device and the 64 binaries aren't working any clues there? arm7 binaries?
Accidental double post* stupid full screen immersive gestures ;p
ghettiguru said:
No problem on Android 12 Motorola Qualcomm XT2215-4 SM6375.. For either. Dfe-neo I use every flash to kill decryption at first before I put my custom fstab.qcom in vendor after getting RW thanks to you guys. But I didn't know about the ROM flash tool. Two-part question number one what's going on with the source forge website all the files are missing? And part two, I've got a friend that has a arm7 device and the 64 binaries aren't working any clues there? arm7 binaries?
Click to expand...
Click to collapse
It's alpha, and now not supported arm32. Waiting full release
I got it started till it looks for a system_ext partition. Is there a way to use it without one on my phone
Littlemether said:
I got it started till it looks for a system_ext partition. Is there a way to use it without one on my phone
Click to expand...
Click to collapse
You're going to want that partition if you've got it on your device. As there's a lot of important white list xmls and some of the most important system apps they've got tucked away on that little system partition there. @LeeGarChat tool here is one of the few, in the case of his RO2RW that manages to see the almost non-existent system slot b that even imjtool says is not part of the "Motorola Group" or something that affect. I've noticed you don't need that one it's only 32 KB or something ridiculous you would think and you can live without it but I also believe it's what handles at least the touch on our virtual devices on slot b or possibly even the binary for switching the slots because I have had trouble without it. And that's a 32 KB m possibly unnecessary image now yours is part of the super block and housing important stuff, I'm sure he will work it out in the meantime you might want to just manually flash, then run his others such as RO2RW

Categories

Resources