Here is a fresh userdebug build with test keys. Use it at your own risk and not in production!
I haven’t gotten developer access on Android File Host yet, but for now fastupload should be sufficient.
If you got the camera working, could you share it with other projects, like CalyxOS? I’d very much like to use the full resolution and wide angle lens there…
If you installed my previous build with test keys and want to migrate without loosing your data, you can use the “migration.sh” file and follow the “Using a script” instructions at Signing Builds | LineageOS Wiki.
Otherwise, just flash the new build and do a factory reset afterwards.
With your guide here I successfully rooted my phone
But now I am confused. Next I want to install the build from mmustermann.
Do I need to follow the entire steps here or hook in at step 7?. I am still confused why mmustermann uploads a “normal” file and a recovery file. When do I use what?
Or do I completely misunderstood and the boot.img should be the LOS.img from mmustermann? So I “simply” root with this file?
The post you’re refering to is about installing Google Pay on a rooted device, not about rooting. But I suspect you just linked the wrong post.
Anyway:
I think you there’s a misunderstanding as to the purpose of rooting: rooting is not required to flash a rom build, it is an optionnal step that one can do afterwards to gain more control, but it is not in any way required if you have no use of it.
The build you’re refering to is signed, which means it probably can’t be flashed as an update of your current system even if you’re alread running LOS.
So you’re going to need to follow all steps indeed.
As for the role of the files:
the recovery.img is needed to provide your system the ability to sideload (ie upload, read, extract and install) a custom rom, which would normally not be possible with the one provided by the oginal system.
the boot.img contains - among others - the kernel of the system, it is already embedded in a full rom file like the one provided by mmustermann.
However when used as an independant file, it can be “patched” with magisk and reflashed on top of the system to gain root capabilitie. Again, totally optionnal.
In “short” you only need to follow the steps 1 to 5 with mmustermann rom file instead of mine. You will lose all data in the process.
Afterwards, if you want to root your device, you can follow the next steps, but you’re going to need the boot.img file specific to mmustermann’s rom in order to do so.
In recovery: wipe data / Factory Reset - there’s no way back to FPOS (for now) after this
Still in recovery: Apply Update → ADB Sideload → Install from ADB and run: adb sideload mmustermann.zip
I don’t need GApps
a. Install Magisk apk on your device
b. Extract the payload.bin from mmustermann.img using payload-dumper-go to $ ./payload-dumper-go path/to/payload.bin (Linux)
c. From the created folder extract the boot.img and copy to your phone
d. Patch the boot.img with Magisk on your phone and copy back the create magisk_boot.img to your computer
e. Run adb reboot bootloader
f. Run fastboot boot /path/to/magisk_boot.img(Do not flash that boot.img!!!)
g. Open Magisk and run direct installation
h. Reboot out of Magisk suggestion
If you just want to become root, you can enable root debugging in the developer options (it’s a userdebug build). You can then use adb root and adb shell to access the root shell.
