Original thread.
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software. *This is not entirely true for Realme devices since bootloader unlock or custom rom flash via TWRP or fastboot does not void your warranty but rooting does.
* So I heard. But that's question of detail.
* Same statement for XDA.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Update.:
As you already know development on realme devices suck beacuse of ****ty or incomplete sources, lack of developers interest and biggest reason is lack of community support.
Our man here @BabluS is a legendary developer of Asus Zenfone Max M1 Pro and is willing to compile stable ROMs for our device. But, he needs some donations to buy the device. He has already compiled Android 10 (PE) for our device which is 99% stable. To continue this tremendous work he needs to have the device in hand.
Reasons To Donate:
1. Official PixelExperience ROM
2. Official POSP ROM
3. Will maintain & provide public Device Trees/Sources (So anyone can compile ROMs)
4. More development for realme 5 Pro
Name : Baswanth Madhav Saladi
Donate Using UPI: [email protected]
Donate using Paypal : [email protected]
Send screenshots of payment to @orgasmtron
We have to reach 6-7k in total out of which we have collected 2.6k..
Keep donating & get closer to stable custom ROM experience. Kudos!
All the donations will be public.Anyone can view and verify them.All details will be transparent.
NOTE:
We will update money collection daily evening. All details will be transparent.
List of Donators will get updated here
CLICK HERE TO CHECK!
Has anybody got Android 10 working properly?
tonibm19 said:
Has anybody got Android 10 working properly?
Click to expand...
Click to collapse
Yes. Method is same.
greenys' said:
Yes. Method is same.
Click to expand...
Click to collapse
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
tonibm19 said:
Yeah but I mean, everything is working fine?
Fingerprint? Camera?
Click to expand...
Click to collapse
Dunno. As I said I never tried Android Q. But I presume fingerprint is missing and I'm quite sure no 48mp camera is present either.
What GSI File for Realme 5 Pro
what type GSI Image for Realme 5 pro, A or AB type?
Tegarcs142 said:
what type GSI Image for Realme 5 pro, A or AB type?
Click to expand...
Click to collapse
AB. On Android 9 and above you must use AB variant. It doesn't matter whether or not does your device use seamless updates. If you try to flash A only variant your device won't boot.
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Tegarcs142 said:
I installed GSI resurrection remix on my Realme 5 Pro and when I trying install Gapps get error not enough system partition. So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Nice. Which twrp did you use?
greenys' said:
Nice. Which twrp did you use?
Click to expand...
Click to collapse
3.3.1-0
Tegarcs142 said:
... So I use resize file system in twrp and it worked.
Click to expand...
Click to collapse
Hi, can you please tell me what option you clicked for resizing the system partition?
the steps you did.
I tried doing that but don't find the option in TWRP.
For better experience with using gsi make sure to check Screenshot resolution if it's lower than our Device
Change Resolution :
1) download termux app
https://play.google.com/store/apps/d...?id=com.termux
2) run commands:
su
wm size 1080x2340
3) reboot*device
Enjoy better experience with gsi
greenys' said:
Original thread.
[DETAILED DESCRIPTION]:
I've spent my whole afternoon testing. And found out there are way more well made gsi roms out there and theoretically all of them should work. First, you gotta read this one. Then pick a gsi rom. I recommend one that has everything (must be AB image) since we don't have a working twrp yet thus can't flash opengapps but if the image file contains it then it's good to go. Go there. Pick one. Make sure it has ab-gapps-su in it's name meaning it's A/B partition dependent treble rom. Gapps means it has gapps ofc. Su means it has built in superuser (that you can ignore later for you'll be replacing it with Magisk naturally). After picking a gsi rom image successfully you can download it to your external sd card and flash it via twrp (yes, that half ass twrp for rmq provided on xda) or you can flash it via fastboot flash system system.img. Wiping data, cache, dalvik, system is necessary before doing so. Also formatting data in twrp after flashing the system image helps a lot just as OP said. If you want to try out other gsi roms you must flash stock vendor image file and do the flashing circle again. If you don't flash stock rom or stock vendor img before doing so your new gsi rom won't be able to work with screen lock. At least that's what I got on 4 different gsi roms. And one more thing. These gsi systems doesn't seem to support exfat file system. Meaning they'll want to format your external sd card. This can by bypassed if you flash lineage os boot.img. And then Magisk and at last modified vbmeta.img for RMQ. That file will make realme vendor think nothing is changed and won't try to fck you over with recovery destroyed issue.
[Prerequisites]:
unlocked bootloader
twrp recovery
External SD card
[BUGS]:
Face unlock and fingerprint isn't present on gsi roms which means they cannot work
Screen lock issue in cases when you don't flash stock vendor.img before migrating from one custom rom, be it gsi or zip to system gsi.img
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM OTHER ROM]:
!! Most of these steps are precaution !!
Read these points carefully to have a basic knowledge what you're about to do
Pick a gsi image of your choice (official Android 9 Pie, especially AOSP is highly advised)
Put your image file onto your external SD card for your internal one will likely be erased
You should grab the appropriate vendor.img and boot.img files for your device by decompressing the 7z files
Get the modified vbmeta.img file for spoofing system to boot
Get Magisk
Get SuperSu remover(Beware! It also removes Magisk if installed)
Get Lineage OS boot.img
It's better to be safe than sorry so you better download whole rom package too
Put all these files onto your external SD card
Make sure you have your twrp recovery on your external SD card too
If you done everything well you should have these on your external SD: twrp, desired system gsi.img as AB variant, your vendor.img, modified vbmeta.img, stock boot.img, Lineage OS boot.img, color os flashable.ozip/zip, Magisk, SuperSu remover
Wipe system, data, dalvik, cache
Flash stock vendor.img as vendor
Flash system gsi.img as system
Flash lineage os boot.img as boot
Flash twrp.img as recovery
Flash modified vbmeta.img as vbmeta
Reboot to system (if the device reboots into recovery you'll have to format data sadly)
After reboot successful and you've done the initial google setup steps reboot to recovery and flash superuser unroot
Flash Magsik
Reboot, now you should have a working aosp like system as I do
[STEP BY STEP TUTORIAL IN CASE YOU'RE COMING FROM COLOR OS]:
!! You could have the same files as above just to make sure but system gsi.img,vbmeta.img,SuperSu remover,Magisk and Lineage OS boot.img should be enough if everything goes as planned and system boots for first try !!
Read the frequently asked questions, step one previously
Get your desired system gsi.img
Put your system gsi.img, twrp.img, Magisk, SuperSu remover, vbmeta.img, Lineage OS boot.img onto your external SD card
Wipe data, system, cache, dalvik
Flash system gsi.img as system
Flash lineage os boot.img
Flash twrp.img as recovery
Flash vbmeta.img ad vbmeta
Reboot (if reboots to recovery you have to format data) then do the Android setup
Reboot to recovery
Flash SuperSu remover.zip
Flash Magisk.zip
Reboot
Now your device should have successfully booted up
In case the gsi rom would be stuck on boot logo then you may reboot back to recovery by holding down volume up + power button and flash permissiver_v5.zip. It helped me boot Pixel Experience gsi rom.
Click to expand...
Click to collapse
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Tarikooo said:
Hi
I wanna install fortnite on RMQ
Through epic games I should register a realme account (but I can do that only with a Chinese phone number which I don't have )
Any solution pls
Click to expand...
Click to collapse
Wth no. Idk. It's not even a gsi related thing. I have no idea sorry.
hi guys i tried flashing havoc 3.0 gsi, and it works great. which one gapps should i use?
Does fingerprint and face unlock work?
This method worked on global rm5p.
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Salmankapuas said:
I tried to flash the GSI Miui Erfan, but when entered in the initial settings, the screen cannot be touched.
Click to expand...
Click to collapse
Don't bother with miui. Only aosp or caf.
i flashed GSI rom, pixel, OxygenOS but the system cannot boot, only stuck on boot loading screen, is that normal?? how do i fix it?
I check this in two apps both giving different answers.
Also I saw
andriyhar said:
Thank you.
Flash img ok.
Click to expand...
Click to collapse
He flashed a/b image
I check in the terminal using
getprop ro.build.ab_update
Got false
But when i flash havoc-os a only system it bootloop
So my question is am i suppose to flash a only or ab?
Also if you have used gsi i'd be glad to hear your experience.
Reading this thread
Aonly or A/B
Treble Check tell me Aonly and Treble Info tell me A/B. Which one must I choose?
forum.xda-developers.com
has lead me to believe
That i should flash a/b img
You can actually force A/B by flashing this zip:
MakeMeSAR.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Then it should flash A/B GSIs properly.
Will my recovery support it though.( Orange Fox by bekirakil)
Also I've only got 3.12GB system partition with no way of resizing it as this device has a dynamic partition
Plus the file name is makemesar and I'm sure that my devices is all ready system as root enabled.
This is just for ensuring you have AB, you can ignore it
System partition, hmmm, you can only flash small roms
I can confirm that you are suppose to use a/b img.
I flashed https://download.havoc-os.com/arm64-ab/Havoc-OS-v4.1-20210208-arm64-ab-Official.img.xz.
Unlike A-only img it booted and worked kindof.
I will not recommend this though as there is no way flash gapps for android 11 and not enough space to flash with a/b with gapps.
Also switched backed to lineage as it was causing random reboots.
Any help over making gsi stable will be much appreciated.
This post is meant for another fourm
When I restored the backup it failed but I was able to boot to lineage os which still contain gapps and magisk.
Since it showed failed I clean install everything again. The recovery read something like something something product partition, odm partion, system partiton.
Don't know if these logs are useful but I've attracted them below
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
I have found that resizing GSI system partition could help flash gapps via Ex Kernel Manager directly from the phone.
My big question is if you can resize GSI system partition without TWRP? since Note 2021 does not support recovery, if yes how?
Or can you actually set bigger system partition than system image with this command ? --el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
(following manual steps for gsi installation)
adb shell setprop persist.sys.fflag.override.settings_dynamic_system true
adb shell am start-activity \
-n com.android.dynsystem/com.android.dynsystem.VerificationActivity \
-a android.os.image.action.START_INSTALL \
-d file:///storage/emulated/0/Download/system_raw.gz \
--el KEY_SYSTEM_SIZE $(du -b system_raw.img|cut -f1) \
--el KEY_USERDATA_SIZE 8589934592
what would be number for 20GB size in this command? --el KEY_USERDATA_SIZE 8589934592 how i can write it correctly?
i have enough space to assign big userdata partition.
CyraxMD said:
Is there any fix for this problem? I wish to have phone rooted AND use GSI
Click to expand...
Click to collapse
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
vegan_monk said:
I wish to have at least a working GSI installed lol.. how did u manage to boot into fastbootd ?
fastboot reboot fastboot reboots into normal fastboot/bootloader on my linux machine..
Click to expand...
Click to collapse
was not neccessary, check this guide which i maked how to do it:
CyraxMD said:
was not neccessary, check this guide which i maked how to do it:
Click to expand...
Click to collapse
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
vegan_monk said:
Nice work man. Surely makes life easier for many, but in my case:
I followed all of the steps. After the GSI installation i tapped on reboot on the notification field and it rebooted into fastboot. I can not enter the GSI aswell as the recovery. Only fastboot and MIUI ROM
I installed MIUI13 from official sources via ./flash_all.sh inside the MIUI13 Recovery folder some days ago. I've done this because i think i soft bricked my device or messed with the partitions before, because i tried to flash a system image directly to the 'super' partition, becasue no fastbootd.
Click to expand...
Click to collapse
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
CyraxMD said:
thx mate,
asuming you are trying to do this on Note 8 2021
ensure that you have your bootloader unlocked and your original rom is NOT rooted. You can also before you do anything with GSI custom releases test official GSI which should be available to you via DSU (connect phone via wifi not data services)
Recovery is not supported for Note 8 2021 thats why i havent mess with it despite i would love to have it. Also in my case - recovery was not needed to load unofficial GSI (just pc with adb drivers and sdk platform tools latest version).
fastbootd is not required in this case either
in some cases modified vbmeta.img is required to make it work.
if you somehow soft-bricked your device try https://www.xiaomitool.com/V2/ that should help you recover back to normal state.
Click to expand...
Click to collapse
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
vegan_monk said:
many thanks for your reply mate,
i managed to flash miui12.5 again with flah_all.sh with official sources fastboot ROM via terminal. now i have recovery again. my computer has the latest adb tools installed.
i tried your dsu loader method on miui12.5 again but sadly it says "installation failed". on miui13 it said "installation success" but could not boot into it. I'm a little bit confused rn lol. i tried the phh's AOSP arm64 AB vanilla and phh's AOSP arm64 AB VNDKlite vanilla
and yes, i have the 2021 biloba version of the note 8
Click to expand...
Click to collapse
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
CyraxMD said:
hmm you said you have recovery? do you mean twrp or cwm? if thats the case i want it too
Click to expand...
Click to collapse
sorry to disappoint u mate but its just the miui recovery
GSI has better performance than MIUI? Could you tell the pros and cons that you have found?
CyraxMD said:
Hello everybody,
I have phone Xiaomi Redmi Note 8 (2021)
I have succesfuly unlocked bootloader. I wish to use GSI installed via DSU Loader and i managed to boot default GSI room offered by system this way.
Also i have used app "DSU Sideloader" and succesfuly managed to boot lineageOS GSI.
The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted.
Is there any fix for this problem? I wish to have phone rooted AND use GSI
After countless hours of searching over internet i have not found topic related to this specific issue.
Also I have tried
fastboot flash --disable-verity --disable-verification boot boot.img
and modified vbmeta.img
fastboot --disable-verification flash vbmeta vbmeta.img
no difference
But i have no idea what is holding back boot.... any help would be much appreciated
GSI related info:
Treble and VNDK - device supported
Architecture ARM64
A/B operating system
Dynamic Partitions
Talking about working GSI is there anybody which managed to install GAPPS on GSI installed via DSU? Is that even possible? how without twrp recovery?
i know that GSIs with preinstalled gapps exists i just want modular approach and install just google apps which i use.
Click to expand...
Click to collapse
After seeing your video I understand that you was able to fix your initial problem:
"The issue is when i root the phone. (classic boot.img extraction from stock rom, modification of the boot.img within Magisk aplication, than flash modified boot.img via adb tools)
After flashing modified boot.img i can no longer boot GSI, boot process will stop on MIUI screen. Stock ROM is working fine (rooted or not rooted)
When i flash original boot.img everything is working fine but phone is not rooted."
It seem that you have been able to fix that problem, havent you? Have you had any problem using rooted GSI lineage? I am very insterested in rooting my phone using a GSI rom. I am going to follow your tutorial.
thanks
Hey,
so I'm trying to make a custom twrp recovery for the rmx3363 but I can't seem to find the recovery partition or which other partition is used for such a role.
Does anyone has any idea which partition is used for recovery?
Thanks!
P.S.: I've tried applications like Flashify and the Official TWRP app to make a back up of the stock recovery but neither can find the partition used for it.
This phone doesn't have recovery partition...
you could study about A/B (Seamless) System Updates in follow web page.
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
Virtual A/B Overview | Android Open Source Project
source.android.com
Hello, I am asking you very sincerely for your support. I need your help with Installing/Flashing Smartphone LG G4 H815 - via Recovery TWRP - Pixel Experience Custom Rom.
I am asking for help - in making contact with > @phhusson on the XDA Developers forum.
Please help me with this.
Thanks for the spam. No idea why you would expect any help from me on this.
Ok I see Dear @phhusson - is currently unavailable. Ladies and gentlemen, please help me. I need to know what to do if I get a message saying that Recovery TWRP cannot successfully install/flash - Zip Packages.
phhusson said:
Thanks for the spam. No idea why you would expect any help from me on this.
Click to expand...
Click to collapse
Hello friend, I am very sorry for Spam. I need help can you help me? I have a situation that when I try to flash a zip package with the extension img.xz - Loader built into TWRP Recovery - in LG G4 H815 - does not want to load this zip package correctly - claiming that it cannot recognize this Android image - which is in the zip package . I understand that I am dealing with an Android image that is compressed from the standard img format to the img.xz format. My Loader in TWRP Recovery fails to detect the img.xz image format.
I need to know the name of the application / tool for image decompression img.xz - xz extension - this is the format that says about using Android image compression - do I understand correctly? If at the moment the Loader built into Recovery TWRP is not reading my image file img.xz from Android - what should I do in this situation?
I think you should think about Decompressing the img.xz image - because I got information from a friend - that if by some miracle the Loader built into TWRP Recovery - would correctly detect the img.xz image - from Android - i.e. a compressed image, then after installing this image on the disk - maybe brick the phone. Because in this situation the Loader would drop a compressed version of the Android image, which would mean an unexpected error. Fortunately in this TWRP Recovery - there is a built-in system - security - which stops flashing / installing the zip package - when the Android image is compressed.
I am asking for your help and support for me.
phhusson said:
Thanks for the spam. No idea why you would expect any help from me on this.
Click to expand...
Click to collapse
Can you tell me if there are img images from Pixel Experience available for download - which are not compressed to xz format?
Is an android image in standard img.
I am looking for a Pixel Experience image that is not compressed in the standard img format - because the Loader in TWRP Recovery does not detect compressed Android images - which are packed in a zip package.