yashsingh1/xdaforums huggingface dataset:
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Successfully used OTA to update from 20200103 to 20200118 (still on Lineage recovery).

A few things to note. Even before the update, my Razer phone would occasionally have problems waking from sleep and then reboot by itself (and would not finish the startup sequence until I unlocked the phone). This problem interrupted the OTA update procedure twice as the phone screen shut off when it was preparing the install. The workaround I used was to enable caffeine for like 30 min to let it finish preparing and installing. Then it asked to reboot. After rebooting it asked for wifi to finish setting up (I think it checks such the app data backup on google), so be sure you have wifi available when you use the OTA.

The problem of waking up once occurred again after the update, so still don't know the cause.

On another note, the gcams that I gave been using with 20200103 would occasionally refuse to save my photos. A restart seemed to help, but not very practical if you're trying to capture the moment.

Magisk Hide (I.e. Repackaging the app to a different name) which caused a loop in starting up the repackaged Magisk on 20200103 appears to now work fine.

Next step (postponed indefinitely): install TWRP (do backups) and try OTA to see if it still works.

EDIT (29 Feb 2020): couldn't seem to find enough info on installing TWRP after having Lineage all set up... So although not ideal (e.g. No complete backup ability using TWRP, if that's still a thing nowadays), OTA updates has been working, wifi is working... Only issue is the device hangs every so often throughout the day upon waking from sleep and then restarts by itself.... Hopefully that's an issue further Lineage OTA updates can resolve.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] sinkoo1979:
can't get the wifi to work.

steps:

flash boot.img to both partitions

flash lineage recovery to both partitions

wipe data / factory reset

flash lineage

reboot to recovery

flash mindthegapps

flash addonsu

reboot

but still no wifi (I was using stock android 9 with November security patch)
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] guillermohs9:
I don't think it matters, but this step is not in the official guide. You must do

fastboot flash boot <recovery_filename>.img

on the active partition (read the guide if using windows). It's worth noting that I've tried to flash a couple of times without success. I want to flash LOS so bad, I will try with TWRP and get some logs next time, in case anything goes wrong.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Zankard:
Do OTA updates work with TWRP?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] wap32:
Same issue here, followed these steps but I get graphical glitches and no wifi.

If I flash the Android 8 Razer image, and follow the exact same steps, then I'm able to get wifi working, so I'm guessing some firmware from the android 9 image (bluetooth, modem? idk) isn't compatible with the current LineageOS 16 kernel.

However, even if I flash Lineage from Android 8, one thing that still does not work for me is 120Hz.

I'm using the super-simple Gears demo from F-Droid, but it won't go over 60FPS.

Also, compared to the official firmware, it's noticeable that things are definitely not running at 120Hz.

Does anyone know how to enable 120Hz, or is this a bug or known problem?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
Official android 9 firmware is not compatible with 16.0. You will have to wait for lineage 17.1 to have compatibility with the new firmware
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] guillermohs9:
Just out of ignorance and curiosity... Why is that? Seems weird that stock Pie isn't compatible.

Also... Would it be safe to flash stock MR2 over stock Pie? To properly try LOS.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Seems like LineageOS 17.1 is ready to go. Manual update required. Will give it a go over Easter.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Flashed 17.1 today and everything seems to be working great! didn't expect it to be so feature heavy when it just launched.

Side note ADB did report the flash failed (stopped at 47%) but it worked fine.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Is magisk causing your bootloop? I don't use root or magisk and just flashed a clean build of 17.1 and micro gapps.

FWIW the in built OTA updater won't work and I can't seem to install files from the recovery Internal storage.

Reboot shuts the phone off too instead of actually rebooting.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
My attempt #7 seemed to have ruled out the problem being magisk. But good to know micro gapps can work.

Did you wipe your data when flashing 17.1?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Yeah that's true.

I did yeah I was on the latest stock build before I unlocked the bootloader and flashed it but since it's not installing any updates I may have to clean flash again.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
So I'm still setting up my Razer Phone using Lineage 17.1 (20200410) after wiping data and system. So far so good (power button, restart seems to work).

Magisk (20.4) seems to work too but it took me a while to find out that from 20.4 you need to turn on MagiskHide in settings (it used to be on by default) to pass SafetyNet ctsProfile (used by certain apps like banking apps). I note that there are articles saying Google recently changed the attestation process for SafetyNet, but at least right now MagiskHide still works.

Double tap to wake still doesn't seem to be working though.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] sinkoo1979:
Anybody got battery drain issue? My RP1 lost 8% in 10 hour stand by or it could be just degraded battery.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Is your inbuilt OTA working?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
I'll get back to you on this later...

In an extremely unfortunate turn of events, after setting up EVERYTHING, I restarted one more time before hoping to give OTA a go.... Stuck on boot screen again (10+ min)!

Holding down power button to interrupt the ever running boot screen and restart still the same problem.

Finally decided to plug into the computer again to go into recovery. Before going through the entire process again, I went into Advance > power off. Powered on again... And it booted!

Repeated this issue. I suspect it has to do with the whole A/B partitions but I don't know enough about this setup just yet. Anyone can shed some light on this?

After this is sorted, I'll give OTA a try.

Edit: decided to live with this until the weekend. In the meantime, I've enabled developer options so that I can select restart to recovery when using the power button. Also found out I can use a usb-c to usb-c cable to connect to another phone to get the Razer to go into recovery mode... I shall call this "jump-starting" the phone... Guess I'll carry a cable with me wherever I go this week.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Definitely not as stable as I first thought. Installed the 12th update via ADB and phone wouldn't boot so had to factory reset and alas the 13th update won't install via OTA either.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
I was away for a few days so I missed the opportunity to announce 17.1. There should be no issues with updates however, I have tested upgrade multiple times locally and it worked fine, I will have to investigate more. Don't wipe your data yet :eek:
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Cheers Mike I'll probably try again in a day or so, stay safe!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
Hi and thank you for a good job!

I've got los 17.1 installed without any trouble. Awasome.

But, I couldn't install magisk, no way. Tried to flash via adb, direct I los recovery, nothing helped. Have someone any solution?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Which 17.1 build date did you use?

Noting I have booting issues (which I believe is unrelated to Magisk) as mentioned in my posts above, I broadly did the following (under Lineage Recovery) to get Magisk working:

after flashing Lineage, reboot to recovery

apply update, ADB sideload gapps

right after gapps, ADB sideload Magisk

normal reboot to start your first boot to Lineage

Magisk manager should already be installed as an app

to pass safetynet CTS profile (for now), enable Magisk Hide, you may also need to change the device fingerprint to a certified Razer device fingerprint and change the boot stage
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
Hi!

I've got boot loop, when installing magisk via adb. the los build I run now is 12.04
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
If you have boot loop, does booting back into recovery and then selecting reboot/restart get you out of boot loop? For some reason that seem to work for me as a temporary fix.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
To reinstall los build is what i do to solve the bootloop issue. It looks like I have to wait for better days with better builds. Yesterday I tried to install the ota update, it failed. Thanks for responding.:good:
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Wifi hotspot issues on 17.1 (20200410)

Still on 20200410 build. Noticed wifi hotspot would not turn on. Anyone else has this problem?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Wired headphone volume

Just remembered another issue on 17.1 (20200410), the initial call volume using wired headphone via the Razer usb-c adaptor does not correspond to the volume setting prior to the call.

For example, I set the call volume to the lowest, hit dial, the actual volume is quite loud but the volume setting shows it bring at the lowest. I then have to adjust the volume setting up and then back down to bring the actual volume down.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
OTA works, but still have previous boot loop problem

Alright, files and documents backed up. Going to try OTA from 20200410 build. Will report back soon.

Edit: I see what [MENTION=4249546]Rox598[/MENTION] and [MENTION=10717405]666zam[/MENTION] meant by OTA does not work. Mine would not even download the OTA on the updater (see attachment). Going to try to copy the URL in the updater and see if I can download it that way.

Edit 2: it appears the copied URL results in a bad URL and does not point to a file.

Edit 3: turns out I didn't refresh the updater. Now downloading 20200417 build.

Edit 4: and the mystery continues.... OTA works for me. Now I'm on 20200417.... However, my booting problems continue. So after the OTA installed and I reboot, it was stuck in boot loop like on 20200410 (described in my posts over the last week). Then I forced it to reboot into recovery using the "jumpstart" method (later again using the usual usb plugged into a computer) and then normal restart... Then it booted. Root is maintained. Magisk still shows passing SafteyNet.

Not sure what else to try to fix the booting problem at this point. Luckily, at least on 20200410, Lineage 17.1 was stable enough after booting to not freeze or spontaneously reboot to cause it to be stuck on boot loop.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
Same here. I'm on 04.16 build. That's not borough me, but unable to root does.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
Just to confirm, you installed gapps no problem though right? Because I installed Magisk immediately after gapps using the same method as gapps before the first boot.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
Yes, everything just as smooth as honey, but magisk. I tried to install right after gapps, reboot into recovery after gapps and install magisk, install from SD card in recovery. Nothing succeeded.:confused:
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
Magisk currently causes bootloop if you reboot on most 17.1 devices. We've been trying to figure it out with no luck so far. The workaround is to reboot into recovery and boot into android again.

OTA should work normally after 20200417 build, fixed by https://review.lineageos.org/c/LineageOS/android_device_razer_cheryl/+/272985
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] osva567:
Razer Lineage

I'm trying to install Lineage OS 17 on my RP 1 9.0 and it gets stuck on 47% and it cancels the installation on adb sideload any help?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
My understanding from my jump to Lineage (see my post) is that 47% is a Lineage Recovery bug but in fact it's 100%.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] osva567:
Razer Lineage

I tried this:

PS C:\Users\osva5\Desktop\ADB\platform-tools> ./fastboot set_active a

fastboot: error: Device does not support slots

Also tried this:

]PS C:\Users\osva5\Desktop\ADB\platform-tools> ./fastboot flash boot_a lineage.img

Sending 'boot_a' (23501 KB) FAILED (Status read failed (Too many links))

fastboot: error: Command failed

And when I try to wipe from the area that says Wipe data/factory reset I get this:

E:Failed to mount /mt/vendor/persist: Permission denied
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] 666zam:
It looks like it stuck, but in fact its installed successfully.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] osva567:
The thing is, it keeps booting me into normal Razer OS
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
Nice thanks Mike!
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] -SKYLINE-:
If I understand you correctly, you're at the flashing the Lineage Recovery stage (not yet flashing LineageOS) according to the official installation guide.

A few things to double check when flashing the Lineage Recovery:

you've followed the official installation guide in unlocking the bootloader (which you done in Download Mode / Bootloader either by

adb reboot bootloader

or

from power off, holding Volume Down and plugging in USB.)

when flashing Lineage Recovery, you are again in Download Mode / Bootloader.

before you flash Lineage Recovery, check that you are accessing your phone from your computer by

fastboot devices

after flashing Lineage Recovery, you are to boot to Lineage Recovery (either by (a) selecting reboot to recovery in the Download Mode / Bootloader or (b) from power off, holding Volume Up and inserting USB cable) to continue with the instructions to flash LineageOS.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] osva567:
It just gives me this error when I try to flash the img:

PS C:\Users\osva5\Desktop\ADB\platform-tools> ./fastboot flash boot lineage-17.1-20200418-recovery-cheryl.img

Sending 'boot' (23501 KB) FAILED (Write to device failed (Invalid argument))

fastboot: error: Command failed
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] brownah92:
Is there any way to install this rom without the use of the screen? My screen is smashed and unusable.

I think I could hook up a USB mouse and hdmi to select unlock bootloader in the dev options

Would I be able to use recovery somehow via adb commands?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] Rox598:
OTA is working now as Mike said.

Although the installation percentage wouldn't increase for me with the screen off it was so weird oh and the phone still won't reboot on it's own I have to turn it back on myself.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] guillermohs9:
Are there any logs or something we can supply to help get "double tap to wake" working?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
17.1 thread is finally up https://xdaforums.com/razer-phone/development/rom-lineageos-17-1-razer-phone-t4087619
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] yuhacrowsqq:
Hi

Is this rom fix the L/R sound channel inversed problem?

The razer phone 1 play video,Game,music,stereo sound come out is Right Channel on the top,Left Channel on the bottom.Whenever rotate phone to any angle.

And most other android device is R channel on the bottom,L channel on the top.

I have a xiaomi 10,It can swap the stereo channel with the rotate angel.

I know razer phone 2 had fix this problem in official pie last year.

So will razer phone 1 get this fix in lineage 16?

Thank U .Sorry for my bad English.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] rogerrulez:
Yeah same here. Tried the older version of twrp and same thing. Anyone have any ideas ?

---------- Post added at 10:03 PM ---------- Previous post was at 09:29 PM ----------

From the log ...

Installing zip file '/sideload/package.zip'

I:AB zip

I:has_legacy_properties: Could not open /tmp/updater: No such file or directory!

I:Legacy property environment not used in updater.

E:Can't execute '/sbin/update_engine_sideload': No such file or directory

Updater process ended with ERROR: 255
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
That was fast work now I'll backup and test it ?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] REAVER117:
Same here, formatted as FAT32.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
Don't use TWRP.

When in fastboot mode, flash boot.img then reboot to recovery (I did this by typing "fastboot reboot" and before pressing enter, press and hold vol up button. "Fastboot reboot recovery" doesn't seem to work? There may be an easier way, that worked for me) This will boot into the recovery built into the Lineage boot.img. Then you can go ahead and sideload the zip :good:

Peace.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
I can confirm that the sdcard isn't being mounted and also the Netflix app refuses to work even with magisk hiding root etc. I'll try and grab some logs for you
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] rogerrulez:
Excellent ! That worked. Thanks. I didn't know how to boot into the lineage recovery and found it strange how it was continuously booting into twrp using the standard method.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] javelinanddart:
Yeah, y'all are right: sdcard does indeed seem to be broken. It's really strange, the device doesn't even detect that a card is inserted at all. Seems like we screwed something up kernel side.

On an unrelated note:

Is anyone brave enough to try relocking their bootloader with Lineage installed? You should be able to fastboot oem unlock if things go sideways (so long as you don't disable the OEM unlocking toggle), but there are no guarantees. It will also wipe your /data, if you didn't know already.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
I might try that when I finish night shift. Also think I've found another bug when rebooting sometimes WiFi/BT and ril refuses to work and requires a couple of reboots to get going again and the signal strength for ril seems to ether be very low for me or the signal bars are not giving accurate information as you can see in the pic below. My signal seems to be very low compared to when I'm on stock where it would be just over half way at my current location.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
Could I be wrong but I just check the one plus common repo for the same msm8998 chipset as are phone and I have noticed that some radio flags are missing on this build not sure if that would fix the low signal issue

https://github.com/LineageOS/androi...ab0582cd3803f530c151851f0/vendor_prop.mk#L198
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
Signal fluctuation is only a visual bug. It's present on a lot of devices and it doesn't affect actual connectivity. More info here: https://piunikaweb.com/2019/01/22/x...tual-cellular-signal-strength-from-end-users/
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
Something is definitely killing my download speeds as I normally get the same download speeds as I do upload but that's not the case and I tried different locations using different signal towers
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
Like this rom so far - apart from the obvious lack of sdcard functionality, which will hopefully be fixed soon - all connectivity works fine for me, 4G, WiFi, Bluetooth all good, decent enough camera and battery life so far so good. Had one minor freeze/reboot, couldn't take logs as was out and about, early days tho...

Peace
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
My Netflix issue have a workaround if you put the device is permissive mode Netflix will allow you to login and watch what you like.

Also WiFi hotspot errors when I try to enable it I'll also grab what logs I can for that bug.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] parksy152:
cant access SD card , any help please?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
It's currently unavailable in the latest build.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] javelinanddart:
Hotspot is working for me on the latest build, what build are you on?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
I'm on this build I just noticed there's new builds up how do they get flashed without using adb since I'm not at home at the moment cause I noticed lineageos recovery can seem to flash zips from the as card
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
Any change log for the new builds? Fixes?

Peace
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] mikeioannina:
Fixed SD card detection, it was broken due to me disabling MMC support in kernel :facepalm:

Next build will probably include the fix, along with a kernel panic fix caused by wifi driver update.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] javelinanddart:
I don't know how to flash updates without a computer handy. You could try USB OTG, but I dunno. Sorry.

Indeed, new build is up with both of those fixes. That should fix some random reboots.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eoghan2t7:
I'll have a look in the morning when I finish night shift. Have you got a link to the proprietary blobs and I'll have a look at doing tests?

Edit: never mind found them on mike's GitHub ?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
New builds can be dirty flashed over previous (lineage) build?

Peace

Wiped cache and flashed, all good, SD card detected now ?
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] MusTangKKK:
So can you now brush this ROM and boot through TWRP？
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
No, use method in first post
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] jckpn:
I'm getting quite bad stuttering unless I have the performance set to the highest option in the battery settings, and even then there's some stutters every now then. It's still 120 fps for sure but every second or so it'll dip down to what feels like 30fps and then back up to 120. Any potential fixes? It's bearable with the performance setting but terrible if it's anything less.

Other than that this ROM is great, huge thanks to OP.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] chris5s:
Double tap to wake doesn't work. Double tapping the status bar puts it to sleep tho.

Peace
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eddro22:
Was wondering why we can't use twrp to flash it would be the same as essential phone my build pc took a dump or I would try to build with latest Razer kernal July witch should let us flash with twrp seeing as that's how twrp is loaded and the kernal has to match to boot.
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] eddro22:
Edited. Nevermind just seen it is pie and the latest Razer kernal is 8.1 one to many already lol sorry
[Razer Phone ROMs, Kernels, Recoveries, & Other Dev] UnfixableExploit:
Works really well, I would love micro g support, and I like the oero version more as magisk works fully and being able to disable dm would be nice too, thanks for being some more life into are razer phones <3