[OpenGApps] Getting error 255 when installing OpenGApps 10 Aroma - Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe

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/

Related

SuperSU & CM13

Is it actually possible to make SuperSU work on CM13 without bricking your device etc?
I have spent the last 2 days googling this and reading various (mostly old, outdated) posts about how it's a bad idea or maybe not, but they are typically from 2.5x or 2.6x or earlier SuperSU versions.
My tablet, the only actively developed non-stock rom available for it is CM13. That is literally it.
However, I would like to have SuperSU features, especially compatibility with SUhide etc.
So, I am wondering if it's possible?
Do the current (2.78+) SuperSU versions play nice with CM13?
Can I just flash it in from the SuperSU app (I have bought pro version if that matters)? or Flashfire? or from TWRP recovery, whichever way is best? And, do I need to do anything else first?
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
DryEagle said:
Wellll, I went ahead and did it. Happy to report everything's working fine. So that's that.
Click to expand...
Click to collapse
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Warlock_SVG said:
Wanna share how you did it ?
. . . I'm running the latest CyanogenMod 13 om my GT-N5100 ( Samsung galaxy note 8 ) and can't get i to work without bricking the device.
Click to expand...
Click to collapse
Well, I downloaded the latest supersu zip (2.78), installed the supersu app from market, installed supersu pro from market (i already bought this long ago), then used flashfire to flash the zip. and it just worked. i'm using latest cm13 nightly on nvidia shield.
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Warlock_SVG said:
Got it working I downloaded "BETA-SuperSU-v2.77-20160827190633.zip" and Installed it in TWRP, systemless mode.
Click to expand...
Click to collapse
you can download 2.78 zip here: https://download.chainfire.eu/1001/SuperSU/UPDATE-SuperSU-v2.78-20160905010000.zip the 2.76 or 2.77 had some problem, dont remember which one, but 2.78 is completely solid
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
[Lemmy] said:
How do I install SuperSU in "systemless mode"? I have a google nexus 10 running the latest CM13 Release + gapps.
Click to expand...
Click to collapse
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Warlock_SVG said:
I used supersu-v2.78-201609011115 for my CM13 devices http://forum.supersu.com/topic/152/supersu-v2-78-release/2 the installer decide if it needs to be installed in "systemless mode" so no need to worry about that
You might need to install the SupperSU app from the store yourself.
Click to expand...
Click to collapse
does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
[Lemmy said:
;68885779]does that work with the "official cyanogen recovery" as well, or should I install TWRP first?
...ok with the cyanogen recovery it did _not_ work, the installer said something about "patching sepolicy failed".
Any other suggestions?
Click to expand...
Click to collapse
Install twrp.
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Will follow-up with you on the next post...
ALI EHTISHAM BUKHARI said:
Spent my 6 hours in trying this crap.....after installation, my phone doesn't reboot rather says "secure boot error" installed cm13 6 times and faced the same problem.....now I won't install it unless I get a tested and confirmed procedure
Click to expand...
Click to collapse
Here's what I do to get my S3 going...
With the latest TWRP as always since running into issues with flashing when i had CWM quite some time ago.
There are 3 files i place in my external MicroSD...
CM13, Open Gaaps for Android 6 (i use the pico) and the SuperSU 2.78 SR1 zip file directly from the official website (though 2.76 should work).
First, when in TWRP, select wipe then advanced then the top 5 selections leaving the bottom 2 alone. When completed, hit the bottom center home selection to go into the main menu. Again, select wipe then select the data option to the right of the advanced tab you were in before. It requires you to type yes then proceed. Once that is done, go back to the main menu and be sure you do this exactly! Select the reboot and then recovery. Once your back into the TWRP recovery then select install and go to the MicroSD card with the 3 files... Now select the order of files to flash beginning with CM13 then add zip then the GApps then add zip then the SuperSU then begin the flash process. Be sure to wipe the dalvik cache then reboot the system.
SuperSU reboots it again shortly afterwards as part of its installation process.
Once your all done setting up the initial system setup you should go directly to the SuperSU app to set up what you need to.
Though my personal procedure is a bit more involved, this is as basic as it gets.
For your specific system, i can't say that i have ever even used it so please pardon me deeply if I left anything out and if someone can chime in with anything else, I'm sure it would be much appreciated.
Good luck.

Magisk fails!

Device info: Xiaomi redmi note 4 Qualcomm, arm64,sdk25
1. I have successfully installed lineage OS 14.1 with pico gapps.... Everything looks good.. but the ROM has lots of bugs... Device get hanged, network issue etc...... So i decided to replace it with RR ROM... Now lots of problem occurs...
2. I have successfully installed RR-O-v6.0.0-20180514-mido-Official.zip with stock gapps arm64..... Now it's trun to install Magisk... But the latest redwoolf twrp shows... Failed to install Magisk and Error 1... So the device cannot get rooted
3. So I decided to install updated version of lineage OS with stock gapps.. now Magisk installed without any problems... But the Magisk fails to install BusyBox and xposed framework in it... Why???
First rule of fig... *ahem* posting about issues:
Provide logs.
Installation logs are always good. For example, the "error 1" message in TWRP means absolutely nothing if you don't also provide the recovery log from when it happens.
And saying that installing busybox and Xposed fails, without any further details also makes it quite hard to help. Are you installing them as Magisk modules? If so - provide installation logs. If not, please explain further what fails, and possibly provide a logcat as well.
Edit: and of course, the Magisk log and/or magisk_debug.log are often quite useful as well.

PP3 Compatibility?

Magisk worked fine on the Android P PP2 beta. Just upgraded to the new PP3 and Magisk 16.4 doesn't seem to work. It flashes fine in TWRP, but Magisk Manager says it's not installed. Just want to check if others are experiencing the same before I assume it's just me and start troubleshooting.
I'm running a Pixel XL.
Same in my pixel 2 XL
I tried patching the boot.img and I got an error
I flashed 16.4 on my Pixel with PP3 and it installed fine. Root seems to work as expected, but modules dont install.
Having the s ame issue. Can't unpack and patch boot.img.
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
SirLoinOfBeef said:
I was able to fix this by disabling phone encryption (set unlock to swipe as opposed to pin, print etc'), re downloading the latest Magisk image, flashing it with TWRP, booting Android, running Magisk Manager (which only half worked a this stage), then finally rebooting Android. All is working fine now and I have been able to re-engage encryption and register fingerprints without further issue.
Click to expand...
Click to collapse
I flashed 16.4 and for some reason worked... but only couple of minutes then suddenly root dissapeared :/
For me works with no problems.
I disabled all modules (just to avoid problems), dirty flashed dp3 over dp2, removed lockscreen password (again, just to avoid possible problems with twrp).
Booted twrp img, then in recovery:
- flashed latest twrp.zip
- rebooted recovery
- I flashed Flash Kernel just because I like it
- Straight after magisk 16.4
- rebooted.
Then I re-enabled all modules and set the password back. Super smooth and zero problems, root survives every reboot, no crashes or freezes of any kind. Also if I download modules they all works.
Still can't get it installed. I am trying to patch the boot.img file via Magisk Manager.
I get:
Code:
- Device platform: arm64-v8a
- Extracting files Failed!
! Installation failed
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
djuniah said:
Installation went fine for me and root/safetynet work, however after a few minutes it all fails. Rebooting will get it working again for a little while but it will eventually fail after a short time.
Click to expand...
Click to collapse
I assume you installed through TWRP?
joderme said:
I assume you installed through TWRP?
Click to expand...
Click to collapse
Yes, i flashed through TWRP. I basically have done the same thing TENN3R mentioned above minus a kernel install. I've tried it a few times now with no luck. Pixel XL btw.

Magisk bricks my phone

I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).
The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.
If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.
I've tried a number of different ways around this:
1. Choosing the Magisk option in the Aroma installer.
2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.
3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.
4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.
5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.
All of the above options - every way I can think of - results in bricking the device.
Is there a way to make this work?
Edit:
1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).
2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.
3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.
Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
I've been having zero luck getting this to work. Does anyone have any ideas?
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
yung40oz84 said:
Maybe you should read this, https://forum.xda-developers.com/ap...7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
Click to expand...
Click to collapse
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.
In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.
So whatever is causing this does not appear to be aroma related.
Haphim said:
So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.
Click to expand...
Click to collapse
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Didgeridoohan said:
It would be interesting to see the recovery log from that...
It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
Click to expand...
Click to collapse
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.
If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?
In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.
Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.
Otherwise, if there are any other ideas, I would love to hear them.
Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.

Unsupported Magisk Version - Cannot Upgrade to 18.x from 6.x, but can't open Magisk 7

Rooted Pixel 2XL 9.0
No TWRP
Upgraded Magisk to 7.2 - get error, "Unsupported Magisk Version"
trying to upgrade to 19.x manually, but all guides say, "Then go open Magisk on your phone", which I can't do.
If I downgrade to 6.x, I cannot upgrade to 19.x. So what to do?
Apologies if this has been addressed, but I cannot find a solution
With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).
Didgeridoohan said:
With your old version of Magisk and Manager installed, download the the update and flash it manually from the modules section (the "+" button).
Click to expand...
Click to collapse
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.
The Manager version shouldn't really matter when installing like that (it is a known working solution for your exact problem). You might have a module acting up and causing issues. Might be a good idea to uninstall Magisk and start out clean.
Booting TWRP and flashing the Magisk zip there could also be a thing to try.
Walsh_M said:
did that, and ended up in a boot loop.
It would seem that with version 6.x, (or anything lower than 7.x), you can't upgrade to 18.x or higher. I tried this 2-3x and same result. Had to flash old patched_boot.img and was back where I started.
Click to expand...
Click to collapse
I tried again, and it worked
1. I downgraded to 6.1 and when prompted to reboot, I just closed, and restarted.
2. I then upgraded to 18.1. Again, when prompted to reboot, I closed and then restarted manually.
There seems to be a bug with regard to rebooting straight from upgrading.
It's only a bug if you can consistently reproduce it, and preferably provide logs showing it happening. Until then it was just gremlins...

Categories

Resources