XIAOMI POCO X3 NFC - MIUI file system encrypted - Xiaomi Poco X3 NFC Questions & Answers

My TWRP: 3.5.2_10-3-surya When I try to install a ROM, it only shows me confused characters in the directory tree. I already know that I can decrypt the system with -FORMAT DATA-, but then all my data is gone. Is there an alternative or how should one proceed? Or is OrangeFox the better alternative at all? And how does this encoding even come about?

Lohenstein said:
My TWRP: 3.5.2_10-3-surya When I try to install a ROM, it only shows me confused characters in the directory tree. I already know that I can decrypt the system with -FORMAT DATA-, but then all my data is gone. Is there an alternative or how should one proceed? Or is OrangeFox the better alternative at all? And how does this encoding even come about?
Click to expand...
Click to collapse
3.5.2_10-3-surya ist totally outdated. Update your TWRP. Use this one:
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

Related

[UNOFFICIAL][PATCHER][APP] DualBootPatcher for Galaxy S9+ Snapdragon/Exynos

I'm proud to present the first dual boot project for the Samsung Galaxy S9+ Snapdragon version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
NOTE
Treble-based ROMs are NOT supported(yet)! In-app ROM changing may not work on stock ROM (maybe it works, maybe not) so you have to use utilities.zip or flash the boot.img of every ROM! I do not own a S9+ so I rely on you guys!
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy S9+ Snapdragon/Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Epic htc 1 said:
Hello,this sounds too good to be true tbh...can I use this to flash a treble rom on my Verizon s9+ snapdragon phone?? I'm assuming root is needed as well??
Click to expand...
Click to collapse
Yes root is needed, but the patcher does not support treble ROMs at this point. Maybe in the future.
Im not a programmer, I just add support for devices and compile it. The real programming is made by the official devs
please support for exynos
Joad said:
please support for exynos
Click to expand...
Click to collapse
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
simon151102 said:
Send me the logs for Exynos version and I will upload a version with support for Exynos S9+.
GetLogs.zip can be found on https://dbp.noobdev.io/downloads/
Flash via recovery and send the generated .tar.gz file
Click to expand...
Click to collapse
Thanks .
View attachment 20190225.101831.tar.gz
Joad said:
Thanks .
Click to expand...
Click to collapse
Will compile a new version with S9+ Exynos support in the next few days
Update
Support for S9+ Exynos version
Patcher: Download
Utilities: Download
Does anyone have a root for s9 plus (snapdragon)
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Epic htc 1 said:
Does anyone have a root for s9 plus (snapdragon)
Click to expand...
Click to collapse
Use magisks built-in root, works perfect on most devices
Joad said:
getting error 1 when flashing . tried RR and PE for second rom both give same error no matter which slot ( im using one ui csb3 as primary ). log attached
Click to expand...
Click to collapse
I will look into this.
But I cant guarantee for a fix because I have no skills in programming
Thank you very much,if anyone has any information about this plz let me know I'm really interested in this program
Does this work for anyone? and if so, using which roms.
Thanks
cvamoose said:
Does this work for anyone? and if so, using which roms.
Thanks
Click to expand...
Click to collapse
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
simon151102 said:
What do you mean with "for anyone"?
This self-compiled patcher works for S9+ Exynos and Snapdragon, but the official one works with around 150 devices.
One user asked me to make a version of DBP for S9+, so I did. (I dont own a S9+).
It should work with (nearly) every ROM, except for TouchWiz ROMs as second
Click to expand...
Click to collapse
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
cvamoose said:
Sorry, I mean for anyone with an s9+. I only ask because it was my understanding that dualbootpatcher doesn't support treble devices. Then I read this as well
https://github.com/chenxiaolong/DualBootPatcher/issues/1389 where chenxiaolong said treble devices weren't supported.
Edit: I added my device (xiaomi mi mix 2s) and compiled from chenxiaolong's sources, I can patch and flash ROMs, but the secondary roms get stuck in a boot loop
Click to expand...
Click to collapse
Yes, treble devices arent supported (yet?).
I dont know if the S9+ is treble based, but it seems like this version of DBP works for most S9+ users
kykint said:
Original dbp as of now doesn't work on devices that have fstab inside dtb. If you've managed to find a workaround, can you share it please?
Click to expand...
Click to collapse
Sorry, Im not a "real" dev.
All I did was following the instructions from the DBP wiki.
Is there anyone that can make a modded version of this that will work on non rooted phones and it doesn't have to be a dual boot patcher but just to get a different ROM running on top or VNC into and use. Maybe like a dual ROM runner.

[MultiROM] MultiROM for Polaris [28.01.20]

New member, had to post it in this section.
This is a test version of MultiROM.
WARNING
It is DANGEROUS to flash MultiROM to your device. It can cause data loss. If you have important files on your phone, NEVER try to do that.
Introduction
MultiROM is a boot manager that allows you to flash multiple roms into the device.
This port for Polaris is based on Tasssadar's work and Vasishath's modification. It seems to work fine now.
You can refer to Vasishath's original post for installation guide.
Reference Links:
[XDA Thread] https://forum.xda-developers.com/poco-f1/development/multirommiui-custom-roms-gsi-t3868734
[Github][MultiROM] https://github.com/ARTI5T/multirom
[Github][Modified-TWRP] https://github.com/ARTI5T/android_bootable_recovery
Download link is below.
Notes:
* You can use MultiROM only with decrypted devices.
* Flash a patch to disable force encryption after flash a ROM with force encryption.
* Don't manually encrypt your data in any ROMs.
* If you want to flash treble GSI, choose A-only images.
** Flashing A/B GSI is theoretically possible if you flash it to a secondary ROM which supports system-as-root. (NOT TESTED)
* Unfortunately, until now, we cannot update a secondary ROM with treble GSI. Now you can update a secondary ROM with system.img.
* Always backup your file before flashing. Especially boot.img or boot partition.
* Be careful with your lockscreen password. You can only set password in either primary ROM or secondary ROMs. Refer to vasishath's thread for more details.
* Not all ROMs are compatible with MultiROM.
* Android 10 can be flashed as a primary ROM. If you have an android 10 ROM as primary, you need an android 9 boot.img and vendor.img in case you have GSIs based on android 9.
Known issue:
* Sometimes touch in TWRP or MultiROM boot screen doesn't work. If you are in TWRP, just reboot. If you are in boot screen, you can also reboot or use volumn +/- instead.
* If you want to uninstall MultiROM, you may need to flash the stock boot.img (In case it can't boot). So please backup your boot.img before flashing.
* Still some bugs with system/vendor compatibility verification. If you meet such errors, please flash a "base firmware" (e.g., MIUI) first, and then flash your zip in "List ROMs".
* In some rare cases, flashing a zip in secondary ROMs may cause primary ROM damage.
This port is only for DECRYPTED device. Don't flash if your device is encrypted.
Please BACKUP before you flash MultiROM.
We're not responsible for any loss caused by this modification.
Download link:
[Google Drive] https://drive.google.com/drive/folders/1C2d3GQT5WVsw83XU6J5qA_oJOYMxyXNX?usp=sharing
Update Log:
28-01-20: Support Android 10 as secondary ROMs. Fix bugs which in some cases cause error 7 when flashing.
17-08-19: Add "Install system.img/vendor.img" in "List ROMs".
16-08-19: Add "skip compatibility verify". Fix some small bugs.
15-08-19: Merge omnirom 3.3.1 source code.
14-08-19: Initial release
Tested on:MIUI11(Android10);ArrowOS(Android 10);LOS17;Flyme8(Android9)
Fantastic. Will try it tomorrow morning and report. Looking forward to it!
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
edit:
Started completely over from scratch. Completely wiped data, installed latest vendor/firmware/ etc...
Still have the same issue, but different flashing error:
With pixel3rom
"string resource 'zip_compatible_err' not found.
Using default value.
ZIP Treble compatibility error!
invalid zip file format.
And then it just aborts.
With arrow OS:
Zip treble compatibility error
invalid zip file format
And then it just aborts.
Firipu said:
I'm having some issues with flashing error for the secondary ROMS. I always get a different error, but from what I can see, they are "outdated" TWRP errors.
Primary ROM is RR. Appears to work.
When I flash a secondary ROM I get:
Pixel3: Zip Treble compatability error. Invalid zip file format.
Arrow: Zip Treble compatability error. Invalid zip file format.
Downloading a few other roms to test, but probably the same error
Any solution?
Click to expand...
Click to collapse
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
__ART1st__ said:
Yes, the recovery is outdated (version 3.2.3-0). Vasishath's repository hasn't been updated yet. You can try to delete compatibility.zip in the zip file and see if it works. I've only tested some old Roms (RR treble, pixel experience) and they worked fine. I will also try to merge new features from official TWRP. BTW, I am just an amateur developer so maybe it will take some time or even not possible.
Click to expand...
Click to collapse
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Okay. I'll try to update my code. Perhaps a looooooong time
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Now you can try the new recovery.img with version 3.3.1 and let me know the result. It may fix that issue (haven't tested yet myself)
Firipu said:
Tried to remove the compatibility.zip and did it again.
This time I get an error 7 (also has to do with old twrp...)
Click to expand...
Click to collapse
Just remove the asserts lines in updater scripts. That would do it.
Sent from my Pixel 3 using Tapatalk
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
It always happened to me with multirom and dualbootpatcher. You have to delete locksettings files in data/system directory...
paulojorjealmeida said:
I do everything good, only one problem, install both roms good, making boot good,and when I go from one rom to the other the pin thont work,say it's another pin, somebody can help me?
Click to expand...
Click to collapse
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Lucas_Maximiliano said:
Go to /data/system and delete all *.key files.Now you should get in without typing any password.
Click to expand...
Click to collapse
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Thanks men
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Sent from my [device_name] using XDA-Developers Legacy app
paulojorjealmeida said:
Alô,thats its not de solucion,i sink,but you now how to fix the pin problem
Click to expand...
Click to collapse
If you have the password problem, go to vasishath's thread and download a patch to clear password.
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Install fw+vendor 9.7.25.eu,for me resolve the problem
Sent from my [device_name] using XDA-Developers Legacy app
Kripton_ said:
Im having error 7 when installing multirom zip, i am in MIUI EU 9.8.9 now, does that has anything to be with it? im really looking forware to install it but i dint know the issue, maybe it has to be with the updater script, i dont know.
Edit, even tho it showed error 7 when flashing mulrom zip, everything seems to work just fine. Should i reinstall it or is it ok?
Click to expand...
Click to collapse
Are you sure your are using MIX2S Polaris? Not Mi8 or Poco F1 or MIX3?
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Writesin said:
It works fine on my device,I use Android Q gsi for internal,the MIUI is secondary.the problem is higher version of MIUI couldn't boot,it just reboot to recovery after "mix" logo on MIUI stable 10.3.4.0.
Click to expand...
Click to collapse
Did you boot any version of MIUI successfully? Could you try another version to see if it can boot? It can sometimes be the ROM's problem. If it still fails to boot, please tell me the version that can boot and the version which can't boot. But I am a student so maybe not too much time on debugging.

Question Deleted

Deleted
Who is Konabess?
boot_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
zymphad said:
Who is Konabess?
boot_stock.img | by zymphad for OnePlus 9
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Click to expand...
Click to collapse
Konabess is an app for overclocking and undervolting your GPU. Someone on the OP 9 Pro had a similar issue and they had to flash over their vendor_boot.
The author of the app says it works by unpacking Boot / Vendor Boot image, decompiling and editing relevant dtb (device tree binary) files, and finally repacking and flashing.
could I still use this if that were the case?
Using it to undervolt was all fine until I got a bit greedy and added another clock step.
Well that is the Magisk modified boot.img that worked with the February Security update initially installed on shipped OP9.
No idea about Konabess, in the past I always used custom kernel with kernel app modifiers.

[Tutorial] How to install any GSI on doha (g8 plus)

Hello! So this is my first post, i actually just made an account specifially to post this because i noticed there was no instructions anywhere
I have a Moto G8 Plus that's running Lineage OS 17.1, i sucessfully ran AOSP, Havoc and Bliss with a perfect experience across the board, the install process for the GSI is super easy and does not involve TWRP or any recovery for that matter
Software wise, you're going to be needing two things: ADB and FASTBOOT, which can be obtained easily through a google search, then you need the usb drivers for your phone, which should also be easy to find
SO, here's the steps, do backup your phone beforehand as what you're about to do will wipe your phone clean:
1. Power off the device
2. Hold Power and Vol Down to enter Fastboot
3. Now that your phone is in fastboot, you need to flash a stock rom onto it, i used lolinet for my android 10 stock rom (in the RETLA region, be sure you get the right region rom), doing that is quite simple, just copy the g8flash.bat file into the same folder where you extracted your stock rom, open the .bat file i provided and let it do it's thing, it'll close when it's done, you have now installed a stock rom on your phone
4. download a GSI https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list (From android 10 to Android 12, haven't got 9 to work), you should get a .img or a .bin file
5. put the GSI in the same folder as your stock rom and rename the file GSIROM (don't change the .bin or .img, i will put 2 files to deal with this)
6. copy either GSI_INSTALL_IMG.bat or GSI_INSTALL_BIN.bat inside the folder
7. run the bat file and let it do it's thing, once it's done, you are ready to reboot your phone and enjoy your new rom
If you have issues, feel free to post about it and i'll try answering as soon as i can, i wish all of you good luck!
Hey thanks for the post. I tryed to download HavocOS-4.5-official-arm64-ab-gapps.img (3.3153489 KB) but it won't let me install. Error message says flashed image is larger than partition size.
So i check on TWRP -WIPE -partition options for system. and i got this:
Size: 2991MB - Used: 2771MB - Free: 219MB Backup Size: 2771MB
so any tips ? i'm on stock rom right now.
daniel_lvs said:
Hey thanks for the post. I tryed to download HavocOS-4.5-official-arm64-ab-gapps.img (3.3153489 KB) but it won't let me install. Error message says flashed image is larger than partition size.
So i check on TWRP -WIPE -partition options for system. and i got this:
Size: 2991MB - Used: 2771MB - Free: 219MB Backup Size: 2771MB
so any tips ? i'm on stock rom right now.
Click to expand...
Click to collapse
Hi! Did you use fastboot or TWRP? You should have the default recovery after flashing the stock ROM
Make sure to get the latest stock for your software channel (I'm on RETLA) https://mirrors.lolinet.com/firmware/moto/ and flash it in fastboot using the .bat files I provided
Hope that helps!
hi thanks for reply. i did use fastboot and also your files. After i got the error on fastboot, i used a twrp.img to boot just to check the partition but its not flashed/saved in memory recovery. i also download lastest stock rom from your link. mine is RETBR.
i tryed the havoc file without gapps and it worked (file size to flash is smaller and fits partition) but i coudn't get to work google account or play store.
the havoc file with gapps included keeps saying is larger than partition size.
daniel_lvs said:
hi thanks for reply. i did use fastboot and also your files. After i got the error on fastboot, i used a twrp.img to boot just to check the partition but its not flashed/saved in memory recovery. i also download lastest stock rom from your link. mine is RETBR.
i tryed the havoc file without gapps and it worked (file size to flash is smaller and fits partition) but i coudn't get to work google account or play store.
Click to expand...
Click to collapse
Hi, can you try to flash this GSI instead of Havoc? If it works, the problem may be the havoc GSI you're using, if that's the case i'll start looking on my end for a working Havoc GSI:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS.img.xz/download
Make sure to select the right variant when getting a GSI, here i already selected the right one
i got this arm64-ab; is that correct?
HavocOS-4.5-official-arm64-ab-gapps.img file size 3.315.489 KB (coudnt flash duo size)
HavocOS-4.5-official-arm64-ab-vanilla.img file size 2.466.145 KB (it worked but does not work google account)
i'll try your file now
daniel_lvs said:
i got this arm64-ab; is that correct?
HavocOS-4.5-official-arm64-ab-gapps.img file size 3.315.489 KB (coudnt flash duo size)
HavocOS-4.5-official-arm64-ab-vanilla.img file size 2.466.145 KB (it worked but does not work google account)
i'll try your file now
Click to expand...
Click to collapse
Hey there sorry for the late answer, I've been trying out GSI's and from what I've experienced, Google Play services won't work on Android 11 GSI's, at least for the G8 Plus.
I'm currently running an Android 10 version of Havoc and everything is working perfectly
MappleBunny said:
Hey there sorry for the late answer, I've been trying out GSI's and from what I've experienced, Google Play services won't work on Android 11 GSI's, at least for the G8 Plus.
I'm currently running an Android 10 version of Havoc and everything is working perfectly
Click to expand...
Click to collapse
did u even try to report to Phh regarding gapps issue?
hey thanks for reply. Gapps worked after i registred the device id for validation on google's page.
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
Does it root the device?
daniel_lvs said:
hey thanks for reply. Gapps worked after i registred the device id for validation on google's page.
How to Fix the "Device is not Certified by Google" Error
Are you having trouble with signing in to your Google account? Can't access the Google Play Store or use Google apps like Gmail, Maps, Play Music, or Photos? Seeing a "device is not certified by Google" error? Here's how to fix that.
www.xda-developers.com
Click to expand...
Click to collapse
Hey thanks for the info!
jcamelo said:
Does it root the device?
Click to expand...
Click to collapse
Depends on the GSI, if it's not rooted you should be able to use MAGISK using the boot img method
Nice! I didn't even knew about this GSI thing. How far things have come since gingerbreak/kitkat times!
I'll save it for when the guarantee runs out! Thanks!!!!
I just wanted to say thank you for this. I have a xt2019-2 and I couldn't figure out which firmware to download from lolinet so I just did RETAIL and it worked thanks to your instructions.
MappleBunny said:
If you have issues, feel free to post about it and i'll try answering as soon as i can, i wish all of you good luck!
Click to expand...
Click to collapse
Many thanks! succesfully flashed lineage 18.1 on g8 plus!
sorry for the noob question but how do I need to rename the img, just GSIROM or how?
Jairsantana said:
sorry for the noob question but how do I need to rename the img, just GSIROM or how?
Click to expand...
Click to collapse
Nope.
methuselah said:
Nope.
Click to expand...
Click to collapse
So no rename to the gsi?
Hi,
so i was able to flash to stock rom , but any gsi rom i try fails, it stops at the flashing system 1/x, so the phone just boots into the stock rom
Edit : i was able to get havoc android 10 to install , trying the lineage 18 linked in the thread and havoc androind 11 didnt work
lesion said:
Many thanks! succesfully flashed lineage 18.1 on g8 plus!
Click to expand...
Click to collapse
Did bluetooth works?
Thanx

Question What's the point of encryption disablers?

Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
HeliX99 said:
Is there any benefit to doing so? You're nuking your security and that's basically it.
Am I missing something?
Click to expand...
Click to collapse
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
kosmatyj said:
At least one point is that custom recoveries cant decrypt /data on Android 12 based ROMs. So it is just necessary.
Click to expand...
Click to collapse
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
HeliX99 said:
I've read in an Arrow OS flashing guide a step that says "[OPTIONAL] Download the latest version of Encryption Disabler". The "optional" part confuses me, can you flash a rom *without* disabling encryption or does it say "optional" because you could use a different tool for the job?
Click to expand...
Click to collapse
"Optional" - means that you can use this ROM without encryption disabler as usual if you dont planning to do anything in recovery (rooting, backup, restore, etc.). If you are just a normal user with no extra requirements - forget about it. Just flash the ROM and enjoy.
A very useful optional way to see internal contents using twrp based recovery when your using android 12 rom which in current has not custom recovery working in android 12 encryption yet
Where can I read more about encription in android in general and changes in 12?
yasen6275 said:
Where can I read more about encription in android in general and changes in 12?
Click to expand...
Click to collapse
Android 12 | Android Developers
Android 12 now available. Try it today!
developer.android.com
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
AmmarHaseeb said:
The benefit of disabling encryption is, avoiding the need for formatting data every single time you install a new rom. Imo it's a life saver for anyone who has a lot of data stored on their internal storage.
Click to expand...
Click to collapse
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
HeliX99 said:
Do you need to format the data for a "dirty" flash, ie upgrading your existing rom to a new update?
Click to expand...
Click to collapse
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
JSGuangco said:
No you don't need to format data unless it is explicitly stated by the developer/maintainer.
Edit: To dirty flash, you can just use adb sideload (if you're using aosp based recoveries like Pixel Experience Recovery or ArrowOS recovery, or use and External Micro SD Card, or USB OTG (if you're using TWRP or OrangeFox)/
Click to expand...
Click to collapse
Thanks for the info

Categories

Resources