Related
hi
can not install magisk 16.0 on lineage 14.1 for i9100 ?
how fix this ERROR ?
Try this (I can not assure you that this will work, since I don't own your device):
1 - Open your LineageOS build zip with some file manager.
2 - Extract the "boot.img" file to somewhere else.
3 - Now go to twrp, tap install, then install image, find and flash the "boot.img" you just extracted.
4 - Don't reboot yet, go back and try to flash magisk, then reboot if you succeed.
It worked with me once. Worth a try.
--
Have you tried the beta version already?:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
sajjads24 said:
hi
can not install magisk 16.0 on lineage 14.1 for i9100 ?
how fix this ERROR ?
Click to expand...
Click to collapse
The S II is quite an old device, and I believe it never got officially updated past Android KitKat, right? Might be why...
Even though the OS is updated by a custom ROM, the boot image may lack the necessary parts for Magisk to patch. At least, that's what your log shows...
You might get more help if you ask around in your device's forum.
Edit: Yup... https://forum.xda-developers.com/showpost.php?p=76705332&postcount=25084
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 wanted to install Aroma because I want the choice of installing whichever app specifically and mainly so that I can replace stock AOSP apps with Google ones. I tried to do that on top of clean flash RR 8.6.2 which does not comes with any pre-built GApps.
But upon installation on OrangeFox it freezes for 2-3 seconds and gives error 255. This is ARM64 Android 10 Aroma so guess I chose the right version but still the error. I can install others like pico, nano, mini and stock just fine but not aroma.
I even tried previous months versions but no luck. Tried installing ROM, set it up and Aroma separately with going to recovery again but still the same error. I am able to flash ANX camera, custom kernel & Fdecrypt just fine but not this one...
If anybody could help what is the issue.
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Skorpyun812 said:
I too am having this issue with the moto edge (racer). Had issues rooting. TWRP went in, flashed lineage 17.1, rebooted, TWRP gone, LineageOS recovery in its place, attached to USB, flashed TWRP ... AGAIN, rebooted, did a root check, root check said "no bueno". Thought that had something to do with it. Finally got a good copy of SuperSU flashed with "success" confimation. NO ERRORS! rebooted. Let everything run its course, for about 10 minutes (way longer than necessary) then tried to flash OpenGapps 10 Aroma and it fails. tried w/ and w/o signature verification, ARM and ARM64. All of it fails! no matter what version, w/sig ver. I get Error 255. w/o it, I ironically get "Zip Signatured Verification Failed!"
Please, somebody heeeeeellllllp
Click to expand...
Click to collapse
UPDATE: For some reason Aroma wasn't giving me error logs but, after trying "full", I noticed the error message was that my device is ARM64. Then, after trying 9.0 and 10 ARM64, (both full versions, not aroma) I found in the logs that there was insufficient space to install. The log for some reason, claims the full version needs 1.7 TB?! So I grabbed a copy of OpenGApps 10 ARM64 pico and that worked. I got basic play store function, that's all I really needed. . . Do not ask why I didn't think of that sooner. Hope this helps poster or anyone else. \m/
The only GSI rom that used to work on my phone was Resurrection Remix Q (8.6.5). Now none of them work. When I flash Android 10 GSIs (A/B A64 vndklite ofc) they only get to the loading screen and they stay there. Android 11 roms don't even boot up. Is there any way to get GSI roms working? FYI, I tried everything (well, almost) to make it work. I tried booting with and without Magisk, I tried flashing with and without GAPPS, I even flashed an ARM64 Treble vendor, and none of it works.
Edit: I'm gonna try flashing a stock Android 11 vendor. I'm gonna keep y'all up to date.
Edit 2: It worked. I managed to install dotOS R 5.2 along with Magisk 24.3 with absolutely no issues.
are there any bugs on gsi rom what works and what doesnt work
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