• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][OFFICIAL][hotdogb][11] LineageOS 18.1

Search This thread

cher81

Member
May 31, 2008
30
7
Hmm, ok. Are you creating and flashing your own manually each time you update, or are you using the Magisk built-in method after installing an OTA?
Previous time when I performed OTA update it was seamless. I didn't even notice the difference before and after the upgrade. Updater said that the build has been installed and that I can delete it.
the problem happened only after the last OTA update build 20210620. I was able to sideload that zip and was able to get it recovered but Magisk and MicroG were not working anymore. I just performed factory restore from the Lineage Recovery and got Magisk reinstalled through built-in method.
 
What were the steps you took?
Based on research, you must do the normal Lineage install with the SIM already installed.

You will never get a recognized SIM if you install LOS without the SIM pre-installed on HD1907 (verified with multiple attempts). Additional reading, people are saying you can never take the SIM out of your phone either or it will stop being recognized.

I'm now trying (and failing) to get the install working with TWRP 3.5.1_10-0 (beta). Then at least I can backup and re-flash my system image if I need to remove the SIM. Will share steps if successful.
 
You need to either flash a Magisk-patched boot image or use the Magisk built-in installer to keep the boot image current. If changes are pushed to the image and you use an old one, you can get issues like what users are currently experiencing.

The ideal way to keep Magisk installed and everything up-to-date is to:
  • Download and install the latest OTA, but DO NOT REBOOT
  • Launch Magisk > Go to Magisk > Install > Install to Inactive Slot
Once you do this, Magisk will install itself into the latest OTA and then reboot. This is the method I've been using, and was able to update to this week's build without issue.

EDIT: As an aside, if you do have issues with an update, you can boot to Fastboot, then run
Code:
fastboot set_active other
to swap to the pre-update partition and give updating another shot without losing data.
That means if i haven't done it the last two times, the boot image theoretically and luckily for me was kept? Because i had no issues and magisk is working properly.
 
You need to either flash a Magisk-patched boot image or use the Magisk built-in installer to keep the boot image current. If changes are pushed to the image and you use an old one, you can get issues like what users are currently experiencing.

The ideal way to keep Magisk installed and everything up-to-date is to:
  • Download and install the latest OTA, but DO NOT REBOOT
  • Launch Magisk > Go to Magisk > Install > Install to Inactive Slot
Once you do this, Magisk will install itself into the latest OTA and then reboot. This is the method I've been using, and was able to update to this week's build without issue.

EDIT: As an aside, if you do have issues with an update, you can boot to Fastboot, then run
Code:
fastboot set_active other
to swap to the pre-update partition and give updating another shot without losing data.
I followed your advice and it booted after update. Thank you!
 
  • Like
Reactions: Ssayerr

Mogster2K

Senior Member
Jun 25, 2011
342
65
For those unhappy about the camera app situation I've found that the stock Oneplus camera app can be installed and used with a few caveats. This was tested on the May 30th LOS build, below I list a few notes to keep in mind for anyone interested:
  1. In my limited testing, APKs with version number 3.X.X are the newest ones that can be installed and actually work. Specifically 3.8.116 is the most stable I've found. The apk can be download here (APKMirror link).
  2. The app will always crash upon normal launch. In order to use it you must long press on the app icon and select one of the popup shortcuts (Pro, Take a video, Selfie, or Portrait). Launching from any of these shortcuts the camera app will work and so far I believe all the camera features work.
  3. There might be occasional crashes mostly due to switching between camera modes too much (Most notable on other 3.X.X versions).
  4. In Photo mode (not Pro mode) the aspect ratio button works only on 4:3 and 1:1, switching to fullscreen will render photo mode unusable as the app will crash upon switching to it. Other modes will still function as normal and Pro mode can use fullscreen aspect ratio without issues. If you accidentally switched to fullscreen aspect ratio in photo mode then it can be fixed by clearing the app data.
  5. The gallery button does not work, likely due to the missing oneplus gallery apk. Probably it will work with it installed but I haven't tested that yet.
  6. Systemlessly installing the app to the system folder does not improve anything. So installing the apk as any other normal sideloaded app is probably the best option.
I'm not sure if the rom can be tweaked to prevent the normal launch crash. Though I'm not expecting anything from the dev about this. The app works without much issue and I'm trying to workaround the launch issue with tasker. Hopefully I'm succesful with it.
I wonder if installing some libraries from the stock rom would fix the problem.
 

gcatto

New member
Jan 20, 2020
3
1
Is it just me or the device's MAC address randomizes on every reboot with 'Use device MAC' selected from Wi-Fi Privacy section? I only encounter this issue on the stock kernel, and flashing a custom kernel fixes it.
 
Last edited:

damianesteves

Member
Aug 17, 2015
8
0
Trying to install using instructions from the wiki, but after flashing the recovery from fastboot, when I reboot into recovery I just get the stock oneplus recovery.
I'm not letting it boot to the OS between flashing and booting recovery.
Running the flash boot command shows me it's writing to boot_a, do I also need to flash it to boot_b manually?

Any ideas?
 
Last edited:

Ssayerr

Senior Member
Oct 23, 2015
135
47
@damianesteves, using "fastboot flash" without specifying a partition automatically sends it to the active one. I think, instead, that there's a typo in the official instructions. You're flashing a recovery, so you should be flashing it to recovery, not boot. So, try "fastboot flash recovery <filename>" and see if that works.
 

damianesteves

Member
Aug 17, 2015
8
0
@damianesteves, using "fastboot flash" without specifying a partition automatically sends it to the active one. I think, instead, that there's a typo in the official instructions. You're flashing a recovery, so you should be flashing it to recovery, not boot. So, try "fastboot flash recovery <filename>" and see if that works.
That did the trick. Thanks a bunch.
Side note, should I be worried about the state of my boot partition now?
 
@damianesteves, using "fastboot flash" without specifying a partition automatically sends it to the active one. I think, instead, that there's a typo in the official instructions. You're flashing a recovery, so you should be flashing it to recovery, not boot. So, try "fastboot flash recovery <filename>" and see if that works.
There's a couple of those typos. On the T-Mobile version "Volume Down" + "Power" goes into the bootloader. You have to type "Volume Up" + "Power" for the LOS recovery. It's a pretty good guide, just a little loose in some sections.

I just rebooted until I get to the right partition to get through this part. Will definitely reference your instructions if they ever patch the T-Mobile LOS!
 

Ssayerr

Senior Member
Oct 23, 2015
135
47
There's a couple of those typos. On the T-Mobile version "Volume Down" + "Power" goes into the bootloader. You have to type "Volume Up" + "Power" for the LOS recovery. It's a pretty good guide, just a little loose in some sections.

I just rebooted until I get to the right partition to get through this part. Will definitely reference your instructions if they ever patch the T-Mobile LOS!
You can also get to the recovery through the bootloader by using the Volume Up/Down keys to change what happens when you push the power button. Ran into that same thing myself.
 

Top Liked Posts

  • 1
    About GCam:
    FYI, I use Nikita's NGCam 7.4.104 (NGCam_7.4.104-v2.0_eng.apk)... No sweat so far.
    In attached file, my config file for Nikita's NGCam 7.4.104.

    About updating firmware on hotdogb:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
  • 2
    Thanks mate.
    I updated through OTA and updated Magisk too, but the mic problem is still there. I'll probably have to try a non-LOS based rom.
    Flash retail firmware and mic will work fine. See: https://gitlab.com/LineageOS/issues/android/-/issues/3933
    1
    I too bought what I thought was a refurb HD1905 and ended up with a T-Mobile HD 1907. I upgraded it straight to OOS11 then LOS 18.1 which I later understood to be bad practice, skipping the global rom, but I had a Google FI data sim in the whole time and there was no problem with cellular data. But same deal with fax machine sound. I don't have a windows machine for MSM tool and it doesn 't run for me on WINE. I couldn't find the official T-Mob image for payload dumper so I used the two of the flashable roms that are referenced by the Go back to Stock T-Mob procedure even though those say not for branded phones. That was a Boot loop both times, manual flash of all images listed in flash-all.bat of the Global Rom. Even though it looped I hoped that something was different when I re-installed LOS but now still Fax machine sound. Did you ever resolve this, was it fixed after MSM tool use?
    I also got the 1907 from B&H. Unlocked bootloader, flashed global rom with this guide


    but never rooted it. I then ran an update or 2 before moving to this rom. I haven't had any of the described calling issues. Haven't really found any issues at all. Once in a while I can't get VLC to kill audio streaming, but that could be the app (?).
    1
    Please someone help any ROM I install phone mic does not work. The other person only hears a loud ringing noise. I can hear them tho. Anyone else having this issue?
    1
    Please someone help any ROM I install phone mic does not work. The other person only hears a loud ringing noise. I can hear them tho. Anyone else having this issue?
    Nope, flash stock and see if hardware prob
    1
    About GCam:
    FYI, I use Nikita's NGCam 7.4.104 (NGCam_7.4.104-v2.0_eng.apk)... No sweat so far.
    In attached file, my config file for Nikita's NGCam 7.4.104.

    About updating firmware on hotdogb:
    If needed, you can download the required files for updating your firmware here (unzip and follow the official instructions ... use LOS recovery in fastbootD mode)
  • 50
    2okPze5.png


    LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device.

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

    Instructions :
    Downloads :
    Reporting Bugs
    • DO NOT Report bugs if you're running a custom kernel or you installed Xposed
    • Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
    • If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
    • If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
    Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.

    Code:
    What is your--
    LineageOS version:
    LineageOS Download url:
    Gapps version:
    
    Did you--
    wipe:
    restore with titanium backup:
    reboot after having the issue:
    
    Are you using--
    a task killer:
    a non-stock kernel:
    other modifications:
    
    Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
    4
    Latest August 1st Update seems to have screwed up the fingerprint unlock.

    Re-scanning the fingerprint works, but the issue is unlocking the phone with the fingerprint.

    It almost always says "Not recognized".

    This was not an issue before this update.
    4
    For those unhappy about the camera app situation I've found that the stock Oneplus camera app can be installed and used with a few caveats. This was tested on the May 30th LOS build, below I list a few notes to keep in mind for anyone interested:
    1. In my limited testing, APKs with version number 3.X.X are the newest ones that can be installed and actually work. Specifically 3.8.116 is the most stable I've found. The apk can be download here (APKMirror link).
    2. The app will always crash upon normal launch. In order to use it you must long press on the app icon and select one of the popup shortcuts (Pro, Take a video, Selfie, or Portrait). Launching from any of these shortcuts the camera app will work and so far I believe all the camera features work.
    3. There might be occasional crashes mostly due to switching between camera modes too much (Most notable on other 3.X.X versions).
    4. In Photo mode (not Pro mode) the aspect ratio button works only on 4:3 and 1:1, switching to fullscreen will render photo mode unusable as the app will crash upon switching to it. Other modes will still function as normal and Pro mode can use fullscreen aspect ratio without issues. If you accidentally switched to fullscreen aspect ratio in photo mode then it can be fixed by clearing the app data.
    5. The gallery button does not work, likely due to the missing oneplus gallery apk. Probably it will work with it installed but I haven't tested that yet.
    6. Systemlessly installing the app to the system folder does not improve anything. So installing the apk as any other normal sideloaded app is probably the best option.
    I'm not sure if the rom can be tweaked to prevent the normal launch crash. Though I'm not expecting anything from the dev about this. The app works without much issue and I'm trying to workaround the launch issue with tasker. Hopefully I'm succesful with it.
    2
    Finally, thank you luk
    2
    for installing magisk, I always follow the following:
    • install magisk manager in the phone
    • extract the boot.img from the payload.bin
    • upload to phone
    • use magisk manager to install magisk to the boot image
    • fastboot boot the rooted boot image
    • when the phone boots again: you have root. Use magisk manager again to do a direct install to the current slot
    • reboot
    • profit