I would need some more info to be able to help. E.g. exact phone model (see my previous post), and what exactly you did. Did you e.g. really follow the OP instructions 100%, or did you decide to do e.g. things differently?
English, please! (see forum rules)
I did it exactly as written, without the factory reset.
In LineageOS 17.1, the only way to grant root to apps (like e.g. TB) would be Magisk.
Then all fine with ROM signing and flashing. Did you compile your recovery or use the one I have linked?HI,
I am trying to update (via sideolading and preinstalling the reference lineageos recovery) my privately signed rom but I always end up in a bootloop.
rom compiles fine,
sideoladed rom reaches 47% then does the two step install and then I am back to recovery.
If you have a boot loop, either something wrong with your compiled ROM or e.g. using a different signature...?
Tell me, is the animation very slow, or is it moving normally?the only thing funny I noticed my rom suggest me to update via OTA to your rom release (I suppose it is just a matter of yout hardcoded server) I have not updated to it, I suppose it will fail for signature mismatch...
but I always end up in an infinite bootloop in the lineage logo step.
I could downgrade to the working rom, so no big problem but, do yu have any clue why I am stuck?
could it be something related to DATA encryption?
In general: No.Other question...
Do you think it is possible to preinstall a root requiring app, let's say such as appwarden, (and have it working w/o root) by giving at build time, requested privileged permissions?
I have taken a look at the AndroidManifest.xml of the app and tried to push a private-permission.xml and tried to copycat the structure ofthe Android.mk of the privileged droid installer .
But since I cannot sideolad my updated rom I am stuck without having the possibility to try it....
my compiled version,
I thought the same, possibly having mismatched the signatures but the releasekey.x509.pem in the recovery matches the one in the updated roms
I knew the first thing but I learned the second!
Well, it's the same dev, I'll try to ask him.
To be precise, it is called permission white-listing, an XML file listing the privileged permissions needs yo be placed into /system/etc/permissions - see e.g. my repo to include the prebuilt AuroraStore and AitoraServices.
Sure, ask him - I am however pretty sure this app needs root.
That is why the flashing works. But have you changed the ROM' s signing keys between the last and this build?
reference is only for repo sync, as no patches are applied. Default is, if you wish to build "vanilla" LineageOS, microG is omitting the hardened malloc for older devices - so hmalloc is the one to use
no, they are still the same keys. i changed nothing.
just for this troubleshooting session, my goal is just trying to reduce the variables. i will just use the rom for solving the error I have.
If you're interested in keeping the kernel up to date, you could use this one if it's easier. (it's heavily customized though)
Well, whilst I agree to your "oversimplification" point, I still do not see any reason to hurry - the first weeks of any new LineageOS release tend to still getting the system stabilized (which is in no ways meant as a blame, but simply acknowledging a well-known fact), and when I start to work on my ports, I prefer to have a truly stable base. And yes, as I mentioned already, I definitely will work on 18.1.That is quite an oversimplification, but I get your point. While Android 11 is not a massive release as Android 10 was it still is a substantial upgrade from security, privacy and performance perspective - not counting the emojis now ;-)
Add to this changes OOS brought with Android 11 (updates to radio firmware and so on) and numerous changes LOS guys introduced to 18.1 (as LOS 17.1 has not seen substantial update for 6 months or so and is in maintenance mode AFAIK) it's definitely not only GPS permission that was added. But you know it better than me anyway.
Usually no feature-backports in the device-independent repositories. I take over, what is part of the 17.1 tree (sometimes, features are back-ported into the maintenance branch), further - if I see some additional interesting features in other areas or Custom-ROMs, I try to incorporate. Regarding device-specific stuff, I do my best to keep the kernel up to date (for the hotdog, it seems that only the published Oneplus updates are taken into consideration in official LOS, which I aim at improving with my kernel fork...)
Thanks for the positive feedback! Nothing really "blocks" me from doing it, see above and also it is really some work with testing (first emulator testing for the general part, later of course with the device, and then finally also picking the previous kernel-patches). So question of available time, me being in the mood, and as said - as there is no "urgency" by means of missing (security) features or any annoying experiences due to too old version etc., I did simply not give it a priority. This device is my daily driver, and I am maybe the most critical user of my ROM ...
Correct - in fact I have taken, what you mentioned, already as answer in my above comments, so no further comments.
Eh, that was a "he/she" because I don't know you. I have no problem with any of that
fastboot flash recovery_a lineage-17.1-20210118-recovery-microG-signed-hotdog.img fastboot flash recovery_b lineage-17.1-20210118-recovery-microG-signed-hotdog.img
Partition product_b dd: /dev/block/dm-1: write error: No space left on device
Partition vendor_b dd: /dev/block/dm-2: write error: No space left on device
If I may offer my step-by-step guide to root a fresh installation. I am not so sure whether that works in Linux (so I keep an old computer with Windows for this purpose). You won't lose any data or customization.Thank you for your support here. Everything works very fine. Last but not least i need root access for the rom.
is it too late now for root because all is set up now or can i root the phone after all this? If yes, can you point me to the correct img or what ever and explane how to root.
Sorry for getting on your nerves....