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
Related
With Android Pie coming, I am trying to understand why the xperia XZ1 compact or the XZ1 aren't compatible with the Android GSIs that are developped thanks to Treble, whereas other snapdragon devices are. Can Someone explain to me what it would take to make it compatible with a generic system image ? I'm kind of a noob
Thanks in advance for your answers
Not relevant but you can build your own Pie AOSP: https://developer.sony.com/develop/...build-instructions/build-aosp-android-p-9-0-0
augt said:
With Android Pie coming, I am trying to understand why the xperia XZ1 compact or the XZ1 aren't compatible with the Android GSIs that are developped thanks to Treble, whereas other snapdragon devices are. Can Someone explain to me what it would take to make it compatible with a generic system image ? I'm kind of a noob
Thanks in advance for your answers
Click to expand...
Click to collapse
It´s compatible with the thirs party versions. I already tried the AOSP version from phhusson.
See this forum: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
You only must be on stock rom with stock kernel without Magisk installed (you can do this later).
Go to TWRP do a factory reset, format data (not wipe) and install the unzipped IMG-file to system partition (change type to install from zip to image)
Then reboot and you are on GSI. Works well. For camera just install a drm fix in TWRP.
They just published the version Android P versions (very experimental), but it works.
The Android 8.1 versions are very good.
SkyHigh76 said:
It´s compatible with the thirs party versions. I already tried the AOSP version from phhusson.
See this forum: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
You only must be on stock rom with stock kernel without Magisk installed (you can do this later).
Go to TWRP do a factory reset, format data (not wipe) and install the unzipped IMG-file to system partition (change type to install from zip to image)
Then reboot and you are on GSI. Works well. For camera just install a drm fix in TWRP.
They just published the version Android P versions (very experimental), but it works.
The Android 8.1 versions are very good.
Click to expand...
Click to collapse
Ok thank you very much, I can not try this at the moment because i haven't bought this device yet, but i'm planning on doing so
SkyHigh76 said:
It´s compatible with the thirs party versions. I already tried the AOSP version from phhusson.
See this forum: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
You only must be on stock rom with stock kernel without Magisk installed (you can do this later).
Go to TWRP do a factory reset, format data (not wipe) and install the unzipped IMG-file to system partition (change type to install from zip to image)
Then reboot and you are on GSI. Works well. For camera just install a drm fix in TWRP.
They just published the version Android P versions (very experimental), but it works.
The Android 8.1 versions are very good.
Click to expand...
Click to collapse
I can't make any GSI to run on my XZ1C. I tried a few and the result is always the same: bootloop just after the Sony logo, so the phone restart itself all the time after maybe 5-8s.
Any idea what can be wrong? I tried on the very old Stock ROM / Firmware 47.1.A.2.324 and also on the latest 47.1.A.16.20. I do exactly as you write:
1. stock clean ROM
2. factory reset in TWRP
3. format data (not wipe) in TWRP
4. install IMG on System partition in TWRP
I've done GSI installations on other Treble device without a problem. But here it simply doesn't work for me. What do I miss?
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Try to install the stock recovery and ramdisk.
+1
I also have this problem. Wich TWRP works with treble roms? i tryed everything and everytime i get a boot loop.
Please help.
After I flashed a treble gsi, I need to flash stock recovery?
Atiqx said:
After I flashed a treble gsi, I need to flash stock recovery?
Click to expand...
Click to collapse
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
ppdr07 said:
Try to install the stock recovery and ramdisk.
Click to expand...
Click to collapse
ppdr07 said:
Yes. if u still get bootloop flash stock recovery and ramdisk first then flash gsi. make sure u factory reset on stock recovery after u flash gsi.
Click to expand...
Click to collapse
And which TWRP should I use for flashing?.. And how can I flash GSI with stock?
That makes no sense to me sorry
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
ppdr07 said:
Flash via fsstboot. Stock recovery and ramdisk flash via fastboot. Im not using twrp so idk.
---------- Post added at 08:38 AM ---------- Previous post was at 08:37 AM ----------
U can see a tutorial at xda how to flash gsi without twrp. Google it.
Click to expand...
Click to collapse
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
XDA XILFY said:
I googled it, pretty much every source says that you require a custom recovery in order to flash a GSI or any custom ROM.
Click to expand...
Click to collapse
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
ppdr07 said:
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ u will find Flash GSI without TWRP
Click to expand...
Click to collapse
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
XDA XILFY said:
Oh, well that's pretty cool. Either way, I just tried flashing Official Resurrection Remix GSI with no luck. Stock recovery, attempted to flash through fastboot and it just gives me a bootloop, exactly like TWRP does. Followed the guide you linked to etc, just keeps rebooting.
Click to expand...
Click to collapse
Go to openkirin.net/download download the rr beta 3
Atiqx said:
I have the PRA-LX1 with already unlocked bootloader and got it rooted with TWRP + Magisk before the last OTA.
I'm not a beginner with rooting this phone but only got Problems with installing any Treble Rom (tried Lineage and Aosp) and every try ended with a bootloop I don't know what I'm doing wrong.
So please can anyone give me a step by step instruction?
Which Treble Rom is a good one and recommended for this phone?
Which TWRP do I need?
And how exactly do I flash them correctly? What do I wipe?
Sorry for this noob questions but I failed so many times with Treble and don't want to do the reinstall with erecovery for the 10000 time :crying:
Thanks
Click to expand...
Click to collapse
Well, I finally got it all working.
You know the risks, don't blame me if something goes wrong, I did these exact steps to manage to root my phone without breaking it. C432, Dual SIM and PRA-LX1.
Have everything stock before following this short guide: Firmware, all stock recovery etc.
Installing the ROM and GApps
First, download necessary GSI files.
(Personally I got Official Oreo Resurrection Remix, here).
(Although you could find yourself using virtually any other GSI, I like the look and feel of RR, though I'll be changing my boot animation with root). Many people would probably recommend you to use something like an AOSP, or LOS which I was also considering on installing. They may also come bundled with GApps, which would negate the later need for installation or download of separate GApps.
This may include GAPPS but you should understand this from the GSI page, so for example on RR I had to download both the latest base ROM .img and the micro GApps.
So to do this I had to use the right architecture (For the P8 Lite 2017, this is ARMx64, do your good research, since my problem was getting this wrong with my PRA-LX1 (Mine was A-ONLY), this stands for the base ROM and GApps.
After this I actually didn't use TWRP as user @ppdr07 advised. I followed the guide he linked us to and did as so, without following the -u command, since it wasn't working for me (didn't affect anything, try it, if it doesn't work, just take that bit out).
The ROM ended up installing and posting through, everything set up perfectly.
After this I was like "Huh, so what now? How am I to flash GApps on this without TWRP?". I went for it and booted into fastboot where I flashed Askuccio's TWRP for hi6250 devices. At this point I worried that the ROM wouldn't post again - though it did, so from there I enabled dev options and switched on advanced power options just for ease of usage. From there I rebooted straight to recovery which posted fine, too.
At this point, you need to flash the GApps. Go for the one that the original GSI page recommends. Flash it to the System Image partition. Don't wipe anything. At this point I recommend that if you realise that you forgot to transfer any files to the SD card, you should do it from the system. It works better compared to the MTP on TWRP. Either way, that should work properly. Now, reboot the system, and it should work perfectly.
Enjoy, it took me months to get to this point lol
Rooting Your New ROM With Magisk
(Before installing this consider the other root options. I believe there's SuperSU and another possibly that I'm less aware of. Either way, in my opinion Magisk comes with the most benefits so I'll be helping you out with that).
After this I ended up flashing Magisk in order to use Snapchat and other apps similar to it. Firstly you'll want to set up Google stuff which has been newly added to the system, and then you'll want to go to chrome and download the Magisk Manager .apk from here. The main and most reliable place to get it is from the creator's project page found here, all main links stand out in the middle fairly well.
(Remember to enable downloading of unknown apps for Chrome in it's app settings, otherwise it won't download or install.)
If it still doesn't work at this point, I ended up holding down on the Magisk Manager link and pressing Download Link (or something to that effect). From this point just install it as you would any other out-of-store app.
Now, you'll need to download these two files from the Magisk page onto your computer: Stable Installer and Uninstaller. Next, while booted into Android, copy them over to either Internal or External storage and when it's done, reboot into TWRP again, either by advanced power menu or using the button commands for recovery. Personally, I think I need the power options with this phone.
In TWRP, simply go to Install, navigate to /externalsd/***[WHEREVER YOU PLACED YOUR MAGISK FILES]***, then install the Magisk installer .zip. If unchanged, the filename should be something like "Magisk-v17.1.zip". Install it, then give rebooting a go. Hopefully it'll post, if not, go back into TWRP and run the Uninstaller .zip, it's saved me a bunch of times.
Unblocking Apps That Say Something Like "Your Phone is Rooted or Modified, no access blah blah blah..."
(Snapchat is the example used here. It won't work upon login if you don't follow this step. Some apps don't work with this alone however, though somebody may have produced a separate guide or easily installable Magisk module with a solution for it. One that won't be fixed singularly with Magisk Hide is Google Pay).
After posting, if you need to unblock Snapchat or something, go to Magisk Manager (which should now be more green), open the top left context menu, tap on Magisk Hide, and search "snap" until you see the Snapchat logo pop up, then select it, then back out with the back button. It should stay selected in Magisk, and the app should now be usable and shouldn't give you any annoying errors, if not give it a reboot and see if it's solved.
Good luck!
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
Code:
MIUI version: 11.0.1.0 (QFKMIXM) - Is this the global version?
Device model: Mi 9T Pro (128GB, 6GB RAM)
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
KuroRyu said:
Hey,
So after a lot of observation and reading I think LOS 17.1 seems stable enough to be used for a daily driver.
Right now I am on the normal stock ROM, without any modifications, no TWRP, no root whatsoever.
However, I have unlocked the bootloader a few months ago, so that's done already.
Current state of the phone:
I want to install TWRP, I want to root the phone, I want to install all needed modules for a proper camera etc, I want to install LineageOS 17.1 (latest build) and lastly I want to install Immensity Kernel (latest build) because I have heard it works well with LOS and provides lots of battery improvements.
I did lots of tinkering with my phone a couple years back, but I haven't done so in a while, and neither have I done anything with this device, so to make sure I am not breaking anything I decided its the best to ask here.
What steps do I have to provide in which order? Can someone provide my a detailed explanation of all the needed steps?
Also, can I install MicroG on it, or do I have to use GApps?
My guess is, first TWRP and root, then ROM and then kernel?
Also, I have read about some issues with Magisk and Android 10, is that still a problem, or is that solved by now?
Anything else I need to look out for?
Cheers
Click to expand...
Click to collapse
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Robbo.5000 said:
Make sure you are in the latest version of MIUI first.
For TWRP flash the latest Mauronofrio TWRP, he has the official TWRP, but his unofficial, latest version is probably a better option at its a little bit more up to date.
Once you've flashed TWRP you will need to boot immediately in to TWRP without allowing the phone to boot into MIUI, otherwise the phone will detect that recovery had been modified and will restore stock recovery.
When you've booted into TWRP, format data (needs to be format and not only wipe), then wipe cache and dalvik.
Reboot into TWRP, to ensure that the newly formatted data partition is correctly mounted.
Now flash lineage and a GApps package. I've only used Open GApps Pico, but I believe microG should be OK. If you use Open GApps it is still in beta and packages larger than the micro package are likely to cause issues, so stick with micro, pico or nano. (For clarification, micro G is a GApps package, what you are really asking is do you need to use Open GApps or not)
The latest Magisk is fine now. It is recommended to boot into LOS first at least once before flashing Magisk. I can't remember the details but sometimes you may get issues if you flash Magisk after flashing a ROM, without booting to the ROM first. You may be fine if you don't boot the ROM first, but since I've forgotten the reasons and can no longer find it, I now boot the ROM before flashing Magisk, just to be safe.
From here, you should be OK to flash different kernels, personally I've never felt the need to, as I'm happy with the performance of things as they are. My battery life is similar to what it was on stock MIUI. If you want to try kernels other than Immensity, just double check first that it is for AOSP ROMs. There are some kernels that have been created that are only compatible with Stock MIUI.
For the camera, I believe the latest advice for ANX Cam is still version 158 along with the 48MP fix for Q ROMs. There are a few later versions, which are not appropriate for this phone. I don't believe there has been a later version for this phone.
Edit: just noticed your question in the quote.
You have the global version of the phone. AFAIK 11.0.1 is still the latest version of the global version of MIUI.
Click to expand...
Click to collapse
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
KuroRyu said:
Do I also need the force encrypt file? Some people mention it needs to be flashed too?
How do I properly install twrp? I boot into fastboot mode, and then I can flash it, I assume?
In the thread it also states that one should first flash vbmeta?
EDIT: Ok, I flashed vbmeta and twrp, booted into twrp, formated data and wiped dalvik and cache.
Now should I flash LOS next and then gapps ..? Which GApp package is the right one for 17.1? It is not linked in the LOS thread?
I've read that some people had issues when flashing the wrong gapps package
EDIT2: Ok, so far I have persisted TWRP and installed magisk. I flashed LOS 17.1 (latest build) and booted into it. I did not flash gapps yet as I dont know which gapps package to use. Also I would prefer to use microG if possible, but I dont think its possible to install it easiely? If it is, please let me know.
Now, the issue is, for some reason after the clean install of LOS17.1 I still see google apps like google drive (remember, I did not flash gapps). This shouldn't be the case? I did format data and cleared dalvik and cache, so it is a bit weird that this happens...
Also I constantly get "android.process.media keeps stopping" .. I assume that is because some applications try to access google service, which are not correctly available? What did I do wrong?
So my questions are:
1) Is it possible to use microG (opensrc implementation of google services), rather than gapps? If so, how?
2) If I need to use GApps, which one to flash?
3) Why were google apps still present on my device after flashing and formatting data ..?
Click to expand...
Click to collapse
There is no need to flash force encrypt files or vbmeta.
I have never used MicroG so couldn't give any answers about that, however Open GApps are open source too. For android 10 it is still in beta. The beta files can be found here https://sourceforge.net/projects/opengapps/files/arm64/beta/20191209/. Pico is the smallest package that gives Google Play, personally I recommend going with that, then installing any other Google stuff from the play store, should you want them.
No idea why you would be seeing Google apps. I can only suggest formatting data again in TWRP.
If that doesn't work I would start again. Fastboot flash the latest MIUI 11.0.1 global ROM, boot into it once, there is no need to go through the set-up. Then go through the steps given before.
This time don't flash vbmeta, it is not needed.
The fastboot ROM can be found here http://bigota.d.miui.com/V11.0.1.0....M_20191111.0000.00_10.0_global_11d3a1700a.tgz
Edit:
Having seen some of your other posts, I'll give you some more info.
vbmeta is mainly used to persist TWRP. However flashing Magisk will persist TWRP and flashing a custom ROM will persist TWRP. You would only need to flash vbmeta if you wanted to stay on MIUI and not use Magisk. (There are other uses for vbmeta, but you don't need them, so I'll not go into them)
Is widevine L1 available on the ROM? Is the FOD working well?
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.