mobile-nixos
mobile-nixos copied to clipboard
NixOS
Razer phone 2 black screen
Hi! I may be pulling a dumb mistake or something here but after I build and flash with the fast boot images it all goes fine but when I boot I get verbose, then a boot logo, and then finally under the bootleg there's a progress bar that says "continuing to recovery menu" and then a black screen. I have no idea what to do, and I tried to reflash countless times. Any solutions?
It's highly likely you successfully booted a "useless and unconfigured" system. Most vendor kernels for qualcomm phones cannot show the fbcon console. So if there is no configuration, there will be absolutely nothing going on on-screen.
It should be noted that SDM845 kernels also require use of DRM, and fbdev doesn't work, to the best of my knowledge.
Can you share the configuration / commands used to build? That would help confirm my assumptions.
In case of doubt, you can build the examples/hello system, and flash the boot/system it creates. These should always boot to something on phones that were merged. If it does not show a "useless" but working app, then something else is amiss.
You should also temper your expectations, at this point in time that phone will not really be useful.
Thx for the reply! I didn't know what needed to be configured so I just followed the guide and then built with the command "nix-build --argstr device razer-cheryl2 -A build.android-fastboot-images" and then flashed using the commands "fastboot flash --slot=all boot boot.img" and "fastboot flash --slot=all system system.img" with the result I described above. I then took your advice and built examples/hello with the command "nix-build examples/hello --argstr device razer-cheryl2 -A outputs.default" and when I reflashed I noticed there was a lot more verbose text but in the end it was the same result, black screen after boot logo and progress bar.
There is an example config for phosh:
- https://github.com/NixOS/mobile-nixos/tree/master/examples/phosh
Though cross-compilation is YMMV.
In addition, I'm not sure it would work with the vendor kernel.
Since you seemingly don't have hello booting right, there might be either a regression, or some difference that somehow affects the system.
Closing since this device was using a vendor-based system, and we are not supporting those anymore.