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

Search This thread

Eric_Lev

Senior Member
Jan 27, 2019
1,380
2,572
Angers
sourceforge.net
Last edited:

sliwka_

Member
Mar 5, 2022
6
0
"adb sideload magisk.zip" while in LOS recovery. Yes on recovery being replaced by LOS recovery.
hey, ive got an OP8T In the end but i think the process is the same. I flashed LOS 19.1 and LOS recovery and its working fine, but when i try to sideload the magisk apk which i renamed to a zip i get a signature verification failure. should i just continue ?
 

HueyT

Senior Member
Apr 3, 2014
4,781
2,164
New Albany, IN
OnePlus 7T
hey, ive got an OP8T In the end but i think the process is the same. I flashed LOS 19.1 and LOS recovery and its working fine, but when i try to sideload the magisk apk which i renamed to a zip i get a signature verification failure. should i just continue ?
If this is so, then you must extract boot.img using payload.bin extract tool and then open up magisk app while in rom and patch boot.img which should be renamed to magiskboot.img. Then move this file into your PC adb folder and flash this by entering phone into bootloader mode and type "fastboot flash boot magiskboot.img" to root
 

barcia99

Senior Member
Sep 22, 2015
160
30
Bay city
It's been a while since I've did adb side load of rom zip, well since I originally put the los on my 7t to be exact. I went to update and see you can't do ota from 18 to 19 like this rom has upgraded. My issue is I cannot remember how exactly the path should look. adb sideload /path/to/zip. Anyway I do it it fails. I renamed it to LINEAGE.zip. so should it be adb sideload /LINEAGE.zip. because this isn't working. Any help would be appreciated. Adb and fastboot are working properly, I'm on window's 10 and OP7t 1905. Thanks in advance

UPDATE: installed lineage and mind the gapps then magisk. appears I've lost root access. any ideas. thanks in advance
 
Last edited:

GuyInDogSuit

Senior Member
Jan 4, 2009
5,873
1,333
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
It's been a while since I've did adb side load of rom zip, well since I originally put the los on my 7t to be exact. I went to update and see you can't do ota from 18 to 19 like this rom has upgraded. My issue is I cannot remember how exactly the path should look. adb sideload /path/to/zip. Anyway I do it it fails. I renamed it to LINEAGE.zip. so should it be adb sideload /LINEAGE.zip. because this isn't working. Any help would be appreciated. Adb and fastboot are working properly, I'm on window's 10 and OP7t 1905. Thanks in advance

UPDATE: installed lineage and mind the gapps then magisk. appears I've lost root access. any ideas. thanks in advance

You still need to patch your boot.img with Magisk, boot that patched boot.img from fastboot, then do a full direct install. LineageOS isn't pre-rooted.
 

GuyInDogSuit

Senior Member
Jan 4, 2009
5,873
1,333
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
guess im not sure how you go about that. any direction would be appreciated.


Extract the payload using something like payload-dumper-go, get the boot.img from the "extractedxxxx" folder, and copy it to your phone. Open Magisk, tap the top "install" button, and "choose a file to patch," and select the boot.img. It will be saved in "Download" in the root of your storage. Copy that "magisk-patched-xxxx.img" or whatsitcalled to your PC, and boot your phone into bootloader, and connect it to your PC. Run the "fastboot boot magisk-patched-xxx.img" command in Command (you can start typing out the "magisk" part and press tab, the rest will be auto-filled). Once booted, open Magisk and install once more, only this time, you can select "Direct install (recommended)" and reboot. Voila, you're rooted.

If you get "device not found" or "waiting for device," make sure your drivers are up-to-date. For bootloader/fastboot, you'd see an unknown one in Device Manager, update the driver for that and "let me choose drivers" and pick Android > Android Bootloader Interface. Try the commands again, and with luck, you're good to go.
 

barcia99

Senior Member
Sep 22, 2015
160
30
Bay city
Extract the payload using something like payload-dumper-go, get the boot.img from the "extractedxxxx" folder, and copy it to your phone. Open Magisk, tap the top "install" button, and "choose a file to patch," and select the boot.img. It will be saved in "Download" in the root of your storage. Copy that "magisk-patched-xxxx.img" or whatsitcalled to your PC, and boot your phone into bootloader, and connect it to your PC. Run the "fastboot boot magisk-patched-xxx.img" command in Command (you can start typing out the "magisk" part and press tab, the rest will be auto-filled). Once booted, open Magisk and install once more, only this time, you can select "Direct install (recommended)" and reboot. Voila, you're rooted.

If you get "device not found" or "waiting for device," make sure your drivers are up-to-date. For bootloader/fastboot, you'd see an unknown one in Device Manager, update the driver for that and "let me choose drivers" and pick Android > Android Bootloader Interface. Try the commands again, and with luck, you're good to go
watched a couple videos about payload dumper and i just cannot figure it out. never used it before. i take the payload.bin file and place it in the extracted payload dumper folder. open cmd from payload folder but here's where Im stumped. not sure what the command should be. sorry if I seem green on this but it's new to me. appreciate a little more input. thank's
 

GuyInDogSuit

Senior Member
Jan 4, 2009
5,873
1,333
40
Sacramento, CA
Nintendo Switch
OnePlus 7T
watched a couple videos about payload dumper and i just cannot figure it out. never used it before. i take the payload.bin file and place it in the extracted payload dumper folder. open cmd from payload folder but here's where Im stumped. not sure what the command should be. sorry if I seem green on this but it's new to me. appreciate a little more input. thank's

I mentioned "Payload-dumper-go" because it's just a matter of dropping the payload.bin on the exe file. No rocket surgery required.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    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:
    5
    Hey guys, for anyone who is interested in installing magisk and is finding it difficult to extract the boot.img, no worries, you can download the latest magisk patched boot images from this thread, ill be uploading the latest magisk boot images weekly for every new release of lineageOS 18.1 hotdogb.
    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.
    4
    Finally, thank you luk
    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.