I've successfully booted and tested @phhusson's AOSP Android 11 GSI
Note: This is a 100% stock to AOSP Android 11 GSI 'guaranteed' to work guide. If you're having issues coming from different roms, kernels, etc. you can give this a shot. It's the only way to truly know what works in the GSI Rom vs. changes after the fact fixing issues inherent in the GSI Rom.
Most things are working!
So here's the things that are not working for me:
SIM Card/VoLTE (on Verizon... others may have more luck on different carriers)
Bluetooth (moving or deleting BluetoothResCommon.apk from /vendor/overlay fixes Bluetooth immediately for audio (couldn't test phone calls since they don't work for me)
Compass
Directions are located on the GSI Wiki: https://github.com/phhusson/treble_experimentations/wiki/Razer-Phone-2
I simply flashed the image vndklite IMG through twrp.
Rebooted, All was working.
Booted back into twrp, resized system partition, flashed nikgapps core.
Everything on my end working flawless, except magisk.
Seems magisk according to phh isn't compatible yet.
Every variation and/or version of magisk results in bootloop, And I require magisk. Besides that everything works great.
I had no need to alter vendors I only flashed system image coming from working havoc android 10 gsi. So Bluetooth is working on my end
liammc83 said:
I simply flashed the image vndklite IMG through twrp.
Rebooted, All was working.
Booted back into twrp, resized system partition, flashed nikgapps core.
Everything on my end working flawless, except magisk.
Seems magisk according to phh isn't compatible yet.
Every variation and/or version of magisk results in bootloop, And I require magisk. Besides that everything works great.
I had no need to alter vendors I only flashed system image coming from working havoc android 10 gsi. So Bluetooth is working on my end
Click to expand...
Click to collapse
Good to know! I'll update my post to explain that this is a 100% stock to Android 11 GSI Rom guide that is 'guaranteed' to work, as I've seen many posts where folks have had issues with the Razer Phone 2 and GSI Roms in general.
Related
topjohnwu:
Pixel, Pixel, Pixel
If this update is working fine just as expected, I'll finally put full force into working on Pixel (XL) support. I've already done some brief research, hopefully I can pump out official support soon lol.
Click to expand...
Click to collapse
-> Source
-> Download
Not working it can't mount system in twrp, and it still can't mount system when I mount it manually in TWRP
Also tried to patch the boot.img flash it to both slots, still nothing, tried to mount system again in twrp and flash the magisk.zip and still got the error
Report this pleased in für Magisk Thread, The Dev need to know
You guys are jumping the gun here. 14.0 still doesnt support Pixel devices yet. If you read his post it states that if there are no major issues with 14.0 he will finally begin official support for Pixel devices. In its current form, the official Magisk still DOES NOT support Pixel devices.
Hi All,
I have been running Lineage OS since it became available for OnePlus 5 with the Safety Net successfully being passed using Magisk and using firmware and modems from jamal2367.
That was up until Lineage required an updated firmware/modem to 5.1.4 and I found jamal2367 has stopped doing the firmware and modem for the OnePlus 5. I installed the firmware from shadowstep the new firmware provider and now I fail the safety net checks.
I have tired the following:
Flashing multiple weekly releases of Lineage OS
Flashing new version of TWRP
Flashing new version of TWRP blu_spark
Flashing new version of TWRP codeworkx
Flashing the ElementalX-OP5-3.10.zip
Flashing Boeffla-Kernel-2.0
Flashing blu_spark_r132
Flashing OSS 5.1.4
Flashing OSS 5.1.5
all with Magisk 17.1 installed
All with full wipes including the sdcard
The only thing that worked was installing OSS 5.1.5 with and relocking the bootloader.
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
alrighte_then said:
Does anybody know what I have missed and how I can get the Safety Net to pass the ctsProfile.
Thanks in advance.
Click to expand...
Click to collapse
Relocking the Bootloader will of course work but you didn't need to do that.
What you missed:
That version of Magisk is clearly not working well with your setup and not hiding your Bootloader state properly. (Providing you set it up correctly).
Had you done all those steps without Magisk it would have passed. The custom Kernels alone would have gotten you a Pass due to them ignoring the Verified Boot state.
So, LOS+Kernel = Pass. If you need Magisk, try to find a version that is working properly with your setup. With Magisk working properly the custom Kernel is then optional.
Also, TWRP has nothing to do with it. Just use the latest Codeworkx.
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
alrighte_then said:
Hi Dirk,
Thanks for your response, I have just tied to install it in the order you suggested
I install TWRP (twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img)
I wiped everything including sdcard
I installed Element Kernel (ElementalX-OP5-3.10.zip)
I installed Lineage OS (lineage-15.1-20180903-nightly-cheeseburger-signed.zip)
I installed Gapps (MindTheGapps-8.1.0-arm64-20180808_153856.zip)
I installed a safety net tester called safetyNet 'attest'
When I run the safetynet test I am still getting CTS profile match: false.
Any ideas what I can do next to make this work?
Thanks for any help
Click to expand...
Click to collapse
You flashed the Kernel before the ROM, so you overwrote that Kernel with the LOS one. Flash LOS then the custom Kernel.
On Magisk.. i've seen many people complain that they can't get the latest version to pass Safetynet. Again, it could just be people not configuring it correctly, or it might be better to try the previous version. Just to make sure you should tell us what you do to set it up.
You need to Hide Play Store, Banking Apps etc, and Magisk Manager too i believe. If you install Magisk and set it up when your current state is 'Uncertified', you will need to clear Data/Cache on Play Store for it to change to 'Certified'.
Also, don't rely on 'Safetynet Checker' apps. If the Play Store settings say 'Certified' try an app like Google Pay. It should work fine.
If you get cts profile mismatch. Download CTS props config from magisk modules and you will pass
Download magisk 17.1
Hi All,
Just to give you an update one where I got to with this.....
You where right the newer builds of Lineage OS do not pass safety net but the older ones do.
So after much playing around I and many flashes and wipes I found it impossible to boot a Lineage with a custom kernel, I believe this is probably down to the forced encryption.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.
The thing that worked for me in the end was installing "MagiskHide Props Config" and changing the figure print, I am it is very similar to the module Jamie suggested.
So I now have Lineage OS working fully with root, magisk and passing SafetyNet
Thanks everyone for you help.[/QUOTE]
Hello; can you explain to me in detail, step by step, how to do it? Thanks in advance.
" changing the figure print"
I have a Moto E4 XT1768 running Resurrection ReMix. I wanted to return to stock to take advantage of the Moto actions. My nandroid must have been corrupt because restoring to my stock backup failed. I then attempted to reflash the original stock firmware with RSD Lite but that failed on spareschunk_3 (multiple times)...even when flashing the files individually with adb.
Finally, I was able to flash the newest firmware PERRY_NPQS26.69_64_8_cid50_XT1768_7.1.1_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip with RSD Lite. I was able to root it and install Magisk, but I could not install any modules. Also, I was unable to install Xposed. The security patch was from July 2018. Does the newest security patch break Magisk/Xposed? Since there were mods that I wanted installed but couldn't, I wound up reverting back to my Resurrection Remix backup...and that's where I am again.
Anyone have any idea why Magisk modules failed, and why Xposed woud not install?
P.S. I had even flashed the latest CR Droid from the telegram group, and it worked wonderfully (security patch July 2018)...but again, Magisk modules failed to install. Didn't really need them with that ROM, but what gives? On a side note, the in-call volume on CR Droid was so crazy high I had to go back to Resurrection Remix again. It was literally blowing my ears off. Editing the mixer_paths.xml did not work either.
mn1968 said:
I have a Moto E4 XT1768 running Resurrection ReMix. I wanted to return to stock to take advantage of the Moto actions. My nandroid must have been corrupt because restoring to my stock backup failed. I then attempted to reflash the original stock firmware with RSD Lite but that failed on spareschunk_3 (multiple times)...even when flashing the files individually with adb.
Finally, I was able to flash the newest firmware PERRY_NPQS26.69_64_8_cid50_XT1768_7.1.1_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip with RSD Lite. I was able to root it and install Magisk, but I could not install any modules. Also, I was unable to install Xposed. The security patch was from July 2018. Does the newest security patch break Magisk/Xposed? Since there were mods that I wanted installed but couldn't, I wound up reverting back to my Resurrection Remix backup...and that's where I am again.
Anyone have any idea why Magisk modules failed, and why Xposed woud not install?
P.S. I had even flashed the latest CR Droid from the telegram group, and it worked wonderfully (security patch July 2018)...but again, Magisk modules failed to install. Didn't really need them with that ROM, but what gives? On a side note, the in-call volume on CR Droid was so crazy high I had to go back to Resurrection Remix again. It was literally blowing my ears off. Editing the mixer_paths.xml did not work either.
Click to expand...
Click to collapse
On stock, most Moto devices including this one have the f2fs loopback bug. You'll need to look for the f2fs workaround module. It's a magisk module but it needs to be flashed in TWRP.
That will allow all of your magisk modules to install properly.
Here I found it for you
https://forum.xda-developers.com/ap...icial-version-including-t3577875/post71554247
After flashing ROMs and moving around to different systems, if you want to restore one of your old stock backups, you'll probably have to format data. Not just wipe, Format.
I will look into it
TheLastAlphaUK said:
Just use sp flash tool ull never have this problem.... Fyi soon as you unlock the bootloader and flash a custom recovery just back up all partitione of the stock firmware so you can just restore no matter what happens
Click to expand...
Click to collapse
His device is Perry not Woods. So Qualcomm not mediatek
I tried again going back to stock. Used RSD lite to flash. Installed TWRP and rooted fine with Magisk. Installed the f2fs loopback patch. Seemed to work. Installed ios beta icons as a test and it installed fine. Rebooted and both Magisk modules disappeared. Tried redoing the f2fs patch again but it never showed up in the modules section, and all other Magisk modules failed to install.
I restored my Resurrection Remix back up and will stay on that.
mn1968 said:
I tried again going back to stock. Used RSD lite to flash. Installed TWRP and rooted fine with Magisk. Installed the f2fs loopback patch. Seemed to work. Installed ios beta icons as a test and it installed fine. Rebooted and both Magisk modules disappeared. Tried redoing the f2fs patch again but it never showed up in the modules section, and all other Magisk modules failed to install.
I restored my Resurrection Remix back up and will stay on that.
Click to expand...
Click to collapse
I've seen some people have that issue on the Moto G6 but not the E4. Make sure you're not wiping cache at any point. If you installed the f2fs fix it should still be in your download folder just install it through TWRP not magisk manager.
madbat99 said:
If you installed the f2fs fix it should still be in your download folder just install it through TWRP not magisk manager.
Click to expand...
Click to collapse
Tried. Didn't work. No interest in trying anymore. Sticking with Resurrection Remix.
Thanks for the replies though.
mn1968 said:
Tried. Didn't work. No interest in trying anymore. Sticking with Resurrection Remix.
Thanks for the replies though.
Click to expand...
Click to collapse
Cool.
Found a Pie GSI that seems to be working great. It can be found at https://forum.xda-developers.com/pr...9-0-0-android-p-pixel-features-kirin-t3833879
Looks like source is located here https://github.com/Huawei-Kirin-Project if someone smarter than me would like to continue the other person's work.
How I installed.
1. Started directly from OpenKirin Lineage with TWRP and Magisk patched kernel.
2. Wiped System, Data and Caches.
3. Flash the img to System Image with TWRP.
4. Flash OpenGapps Nano.
5. Flash Magisk again even though the kernel was already patched.
6. Wipe Caches and reboot to system.
You need to enable Developer Options and choose a Webview implementation. None is chosen automatically. That's why some apps would just close initially. This fixed my Gmail and Amazon app issues.
Issues:
WiFi Hotspot not working.
What I've found so far:
Magisk is working.
Amazon apps force close.
AMI Music won't install. Says it's not available on this device. Could probably restore it from a backup if Titanium worked.
I haven't looked for any solutions yet.
Sent from my BND-L34 using Tapatalk
Edit:
Titanium Backup works after flashing Magisk. I originally didn't flash it because my kernel was already patched and I didn't expect the rom to actually work. When it booted, su was working for everything but Titanium so I assumed flashing Magisk wasn't needed in my case.
AMI Music works after restoring from a backup.
Amazon Alexa and Shopping still close. Amazon Music works.
Can an admin fix my subject line please .
Sent from my BND-L34 using Tapatalk
I've been using this a DD for three days with no issues. It actually runs better than the OpenKirin Lineage build I was running. The developer was supposedly part of the OpenKirin team who quit.
Sent from my BND-L34 using Tapatalk
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.
Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...