HELP I have researched everywhere on the internet and I'm not sure what to do. I have a REDMI 4A wit AEX ROM OREO8.1 installed, TWRP 3.2.2.0 Official (for Redmi 4A on the twrp website) and tried to flash Magisk v.16. Error 1 mount vendor shows up in twrp. Many YouTubers says I should flash boot.img. I've already flashed the boot.img of the given AEX ROM OREO 8.1, but the same error occurs. I tried to search for answers, and what I found was that apprently aosp oreo ROMs usually are Treble ROMs. Downloaded Termux app and checked if ROM was treble = false = NOT Treble! Then others say I have to flash a modded vendor version of twrp. (Link: (add Https here)/androidfilehost.com/?fid=674106145207489212) Haven't tried it out just wanted to make sure if I should or not, bacuse the last time I tried to flash a different twrp, I had to flash the original one back using ADB...
Btw I had given up at some point and I flashed SuperSU successfully. Why Can I flash SuperSU but not Magisk?? I fully unrooted SuperSU and am ready to try flashing Magisk again. If anyone has any idea how to fix this, pleeeeeease tell me I need Snapchat to work while having root (yes I know I could've used Titanium Backup but that not the point rn)
Thanks in advance!!!
Austin:fingers-crossed:
Install TWRP Pitch Black and Install Magisk for Treble ROM
Hi everyone, I have problems starting GSI, I once managed to start the pixel 2 Android Q GSI with Android oreo stock vendor, now I would like to install any GSI with AospExtended Vendor but I can't install any GSI, like I do to install a GSI correctly?
For a gsi you must be on stock rom, no gsi will boot on a custom rom vendor
What if I flash the recovery stock rom and then flash the GSI?
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
hash02 said:
I have been using custom roms for years.
I wanted to try flashing GSI images, and i decided to start with Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img
I installed twrp-3.5.2_9-0-z2_row
I completely wiped everything, system/cache/data etc.
I flashed Havoc-OS-v4.4-20210503-arm64-a-Official-vanilla.img then NikGapps-basic-arm64-11-20210514-signed.zip.
Rebooted.
Phone is instantly resetting right after the ZUK logo goes away. stuck in boot loop. Am i doing something wrong ?
Click to expand...
Click to collapse
Can you send me the link of the thread where you saw your rom?. Pretty sure theres a tutorial in it.. You are missing some important step like flashing create vendor.zip or repartitioner.zip and some other stuff.. Give me the link...
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
hash02 said:
[11][OFFICIAL] Havoc-OS 4.1 [ARM64/ARM/A64][A/AB/AB-VNDKLITE][GApps/Vanilla]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com
Your question is a bit weird because this is a GSI. it's not model specific and should apply to things treble.
So it's not "my rom" it's just a gsi rom that should just work, right ? (unless i did something wrong)
Procedure was standard, clean, no dirty flashing.
Flash img, then gapps, then reboot.
I remember the instructions were for an older version of havoc, i just took the latest build because that's what you usually do ???
Regardless, this is not a HAVOC issue, I later tried with caos build caos-v307-210507-arm64-agZ.img. The exact same behavior happened.
Click to expand...
Click to collapse
Redo the process and try to flash the gsi only without gaps then boot..
r
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot.. You can check this out also maybe it will help? https://forum.xda-developers.com/t/zuk-z2-pro-project-treble-android-10-11-12-gsi-ab.4197355/
Click to expand...
Click to collapse
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
prc.kailas said:
to flash a GSI image first you should wipe all except internal storage.
then install a Vendor ie; Basic roms like AEX, ARROW OS according to the GSI Version
if you GSI image is based on Android 10 then you should flash a android 10 rom from aex or arrow, then flash the gsi to system, then reboot
Click to expand...
Click to collapse
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
ivanjudge said:
Redo the process and try to flash the gsi only without gaps then boot..
Click to expand...
Click to collapse
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
hash02 said:
I already did
right now i am on aospextended android 11 version. since it's not a gsi image it worked. but it is unstable and i really want to try the gsi images and make it work primarily out of technical curiosity
Click to expand...
Click to collapse
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
ivanjudge said:
Try what @hash02 said you can check the link i gave you above to view the full detail and to avoid boot loops reboot to recovery after flashing the gsi then flash the gapss then factory reset then reboot...And dont use nikgaps instead use other Gapps..
Click to expand...
Click to collapse
Well, Ok but where do i find android 11 opengapps ?
I didn't find any other gapps for Android 11.
However I tried your method even if it makes absolutely no sense at all. This device is a-only not a/b. Can you explain that or is that an elephant in the room that you dont want to talk about ?
In any case, the device does not bootloop anymore, it just sits in fastboot mode.
These are the steps to flash a gsi on zuk z2 pro correctly:
Wipe clean all partitions excluding user data
Then flash https://forum.xda-developers.com/t/radio-modem-basebands-for-zuk-z2-pro-only.3715835/ latest baseband
Flash boot image [ linked below - it is the boot image extracted from a mokee 9.0 rom ]
flash vendor image [ copied from another thread ]
flash gsi image [which ever you want]
reboot to recovery again [ sometimes it doesnt work unless you do ]
reboot to system
https://mega.nz/folder/E55iTZQJ#jNsa9d7WxLKr-9q_LFPS1A saved here for anyone else's convenience.
hash02 said:
So, the gsi flashing just copies the image-byte-by-byte to the /system partition ?
Just like dd on linux ? Blind transfer from one direction to the other ?Is this why you recommend flashing "basic roms", so that by flashing the zips all other partitions are updated accordingly ? like /vendor and so on ?Please clarify and keep it technical, i want to learn
Click to expand...
Click to collapse
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
prc.kailas said:
by flashing gsi no vendor is updated or modified. because gsi's are generic rom with only system image, no other partitions. so flashing a basic rom (especially made for your device) , that will update every partition, and then replacing system by gsi system thats all.
Click to expand...
Click to collapse
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
hash02 said:
superior-arm64-bvN-userdebug.img with AEX 7.3 works awesome and stable enough.
Click to expand...
Click to collapse
havoc-arm64-bvN-vndklite.img with AEX 7.3 works
hash02 said:
Thank you, I figured as much as I did a lot of testing trial and error and flashed lots of files yesterday. Got it working booting etc. Unfortunately the ROMs don't support fingerprint scanner out of the box and didn't bother to make it work. Just wanted something stable to use my phone. Thx
Click to expand...
Click to collapse
for me AEX 8.1 is awesome, but none of custom support Uhealth with Sp02 sensor. its very usefull at this time.
Hello. I will describe it briefly:
I'm about to flash my Redmi 6A(cactus), to Lineage OS 18.1 via GSI using OSS(ALPS)-vendor on arm64. I have read some information and it says that installing Magisk could cause a bootloop. I want to know if it is true.
Which image do I want to use - https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
Image - lineage-18.1-20220715-UNOFFICIAL-arm64_bgS-vndklite.img.xz
P.S. I haven't started flashing yet, I want to consider all the little things and conventions before flashing the phone.
Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
MDN2137 said:
Im on my A605FN right now and i have installed AOSP v222 (treble_a64_bvS-userdebug 10 QQ3A.200805.001 200805 test-keys) as my system. Can someone send me a working android 8 GSI? Android 10 is too much for this device and my 3gb of ram cant take it. I dont have time searching for well working GSI's to this phone. I need well optimized system that will use minimum ammount of resources. Thanks.
Click to expand...
Click to collapse
Just try that Lineage R mod - it should work fine. However if you want so old builds, then there is best list with Android 8 Oreo section:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
When i try to install lower android version than 10 my phone boots in download mode... Yes, regular odin mode, no errors, etc. Please help, i want to get rid of that android 10 no matter what version it is, even LineageOs or AOSP, its still android 10 that use a lot of resources to work smoothly
1. Download this and extract.
2. Go to TWRP.
3. Follow this guide (flash this in TWRP, not in Odin).
It should work well. Older Android versions may require older kernel versions to run or you just chosen wrong builds (it needs to be A/B arm32_binder64 (A64 - not arm64) vndklite).
In case that Lineage R mod is not smooth enough do the same with other GSI's from the list from my previous post (always choose arm32_binder64 vndklite (A/B) builds). Some will be lightweight enough for your needs.
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
And i have another great idea, what if i just not install the gapps and run clear CLEAR android
Hmm... Also i can install the most important gapps, I didnt think about that, that should use very small ammount of ram, cpu, etc.
MDN2137 said:
Ye i know build for my phone . I will try the GSI you linked but which gapps should i use to this system?
Click to expand...
Click to collapse
Just use build I linked above. It has integrated Gapps and passes needed certfications out of the box. You can also download vanilla build and flash pico gapps yourself. However option with integrated gapps is just fine and sufficient. Read whole thread - author had the same problem as you and solved it by flashing Lineage R mod with integrated gapps - it's the most simple way.
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
MDN2137 said:
Idk why but when i flash this GSI with no error and then i try to boot to the system it goes download mode. I think i know how to flash GSI's, I'm doing it 100% right. I flashed it in every possible way. It is getting boring
Click to expand...
Click to collapse
Well, flash maybe at first stock firmware via Odin to ensure that kernel and vendor partiton are untouched. And then flash GSI in TWRP two times like it was said in guide.
However the most common cause of such effect (booting to download mode) is just wrong build (wrong architecture - you need to always download arm32_binder64 (A64) builds).
I already tried to flash GSI after flashing ROM via Odin3. Still booting to download mode. Im 420% sure i downloaded right build.
Well, I'm out of ideas. However you can still try to resize system partition in TWRP to make it a bit bigger and then try to flash GSI image (two times). You can also just try to play with different GSI's from the GSI list - just look for the smallest images and try to flash them. If some will properly boot then just go back to TWRP and flash rest of your needs (pico gapps, Magisk, etc.).
I will try that in future