yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Your assumption is correct - the recovery needs to be signed with the same keys as the ROM.

In addition, and that in fact is all, which I did, it should be built along an "unmodified" LineageOS tree.

As you may know, the recovery.img is anyhow built along the ROM and also included into the 'payload.bin' file - but at least one of the hardening measures, which I apply to the ROM, makes the recovery faulty.

Btw, what do you mean with "resign the bootloader"? You mean maybe "re-lock" the BL?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
yes! relock...

so, using your repository, if I select

./switch_microG.sh default

I shall have to

brunch hotdog

mm -j && m ramdisk-nodeps && m recoveryimage-nodeps

and then sign it?

sorry if I ask dumb queestions but I am learning////
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
When you do 'brunch' you will find the recovery.img in your target/product/hotdog directory, next to the assembled ROM zip. The recovery file in that case will be signed with the publicly known test keys. If you build the ROM as well only with the test keys (the result of 'brunch'), this will fit together.

If you sign the ROM during the build, as I have described it in my little tutorial (using the build script and a directory containing the certs and keys), the recovery.img will already be properly signed.

To be honest, I am not sure how to sign "only" the recovery.img, after building it with e.g. 'mka recoveryimage', so I have built the entire ROM to throw it away, just to get the recovery image. :)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
So if I just do a

./switch_microG.sh default

and ./build_hotdog.sh sign

I will have the recovery correctly signed do to the first rom "switcharoo".

thanks.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Correct - but you need to have your specific keys in the ~/.android-certs directory.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
Thank you again for the hint,

already have it.

Since it's an unofficial lineage build are you, perchance,

planning to have an option to have p*tch*d st*re instead of Fakestore?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Short answer: No.

Longer answer: To get apks from the G* Play store, AuroraStore is bundled. Fakestore is only a stub, to "satisfy" apps having Google dependencies, which check for the "existence" of the Play store without actually using it.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
I understand your point.

Still I have some apps I bought thru in app purchases no way to have it working any other way.

Still I don't want to have a rooted phone anymore.

Anyways very solid work! Thank you again!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
HI, sorry to bother you again but it seems I cannot produce a user (signed) build.

at some points the system spits a long error queue but I noticed a

Enter password for user-keys/platform.pk8 (password will not be hidden): java.lang.NullPointerException

but the script never asks me for a password.

maybe it's a dumb question how should I pass the password to the script or, otherwise, can I do a user build without signing it and the sign it later?

thank you
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I assume, that you have created the keys with a password - for use in builds they should not have a password

Alternatively, yes - you can also create a build signed with the publicly known test keys and then do the signing separately, see e.g. here: https://source.android.com/devices/tech/ota/sign_builds?hl=en

I prefer signing along with building, because - in earlier builds - the signing as separate step sometimes has failed for unknown reasons.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
thank you, you are of great help in my amateur experiments!

yes, for a reason I thought it was better to password protect the signature, instead it's expected I keep my private key in my well protected caveau!

BTW I am trying to integrate oandbackupx into the build so that I can restore/backup my apps and data without having to have a rooted phone, do you think it will work?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
LineageOS integrates already a backup solution: Seedvault. Have you tried?

Of course, you can also include a different solution. Whether it works, depends on the requirements/documentation of that app and how it integrates.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
thank you again, without password on the keys I concluded successfully the signed build.

I like oandbackup since it allows to have a granular control on the apps I backup/restore.

MOreover I want to experiment a bit with privileged apps without root.

Now I am building the signed recovery.

I canceled, after having moved to a safe place ota and plain build zips and issued

$

./switch_microG.sh default

I received this message and input request.

Patching ~/hardenedlineage17.1/vendor/lineage (build signing method)

patching file config/common.mk

Hunk #1 succeeded at 54 with fuzz 2 (offset 53 lines).

Hunk #2 FAILED at 218.

1 out of 2 hunks FAILED -- saving rejects to file config/common.mk.rej

patching file config/common.mk

Hunk #1 succeeded at 61 with fuzz 1 (offset 52 lines).

The next patch would create the file overlay/changelog/amami/packages/apps/Updater/res/values/strings.xml,

which already exists! Assume -R? [n] y

patching file overlay/changelog/amami/packages/apps/Updater/res/values/strings.xml

Should have I zeroed some other folder or it's fine jusst telling the script to overwrite?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Normally, this should not happen!

The script assumes, that the z_patches directory and all directories, it attempts to patch, are checked out for the 'same' branch (I.e. all on 'lineage-17.1', all on 'lin-17.1-microG' or, in case of 'hmalloc', those repos which have a 'lin-17.1-hmalloc' branch being there, otherwise on 'lin-17.1-microG').

If that is not the case, you will get such errors.

There can be two reasons:

Either, you altered something manually, so the branch could not be checked out, or you manually checked out a different branch in z_patches.

Check the code of the switch script and you'll understand.

To fix the situation, do the following:

cd z_patches
git checkout lineage-17.1
./patches_reverse.sh
git checkout lin-17.1-microG
./patches_reverse.sh
git checkout lin-17.1-hmalloc
./patches_reverse.sh
cd ..
./switch_microG.sh reference
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
Yes I added some files in prebuilts/prebuiltsapk folder and

modified ~/android/hardenedlineage17.1/vendor/lineage/config/common.mk to make the system aware of it.

I had not thought it will mess things up.

OK, I'll study.

thank you I'll do it.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] cowgaR:
To address elephant in the room... Are you working on Lineage OS 18.1 version please? Plain vanilla already available but misses all your goodies...as this is certainly best ROM for OP7T Pro

Also, what is the best way to flash Android 11 OOS when on your ROM (which I assume will be required first if you decide to upgrade), will TWRP 3.5.1 do the trick?

Releases · Systemad/android_device_oneplus_hotdog

TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.

github.com

Or it's the more complicated fastboot way flashing each partition of extracted OOS the only solid way to return to OOS?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I am currently not working on 11. Frankly, I do not see any "killer" features, which would make me switch as soon as possible.

To me, besides some nitty-critty details (bubbles, prio chats, use location only once), the only effective difference would be to have the ultimate pleasure to see "Android 11" when picking "about phone" in the Settings app.

To return to Stock, use the search engine of your choice. There is plenty of information available. I haven't done so myself, so I won't point to any specific one.

TWRP isn't officially available for our device yet, and the unofficial builds all lack certain key features. So I am reluctant to comment on TWRP at all.

If you ask me, I'd go for fastboot to return to Stock - but as indicated before, I didn't do so myself, so the risk is on your side.

When it comes to shipping L18.1 for this build, whenever that is going to happen, you should be able to dirty-flash over my current build, I guess.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
New build with May ASB patches available

Hi all,

a new build is available and also offered via the Updater app. For manual download and flashing, see here:

https://sourceforge.net/projects/lin17-microg/files/hotdog/lineage-17.1-20210509-UNOFFICIAL-microG-signed-hotdog.zip/download

ASB Security string 2021-05-05

Bromite System Webview and Browser updated to 90.0.4430.204

Upstreamed microG (no new version)

Update: AuroraServices 1.1.1

Regards, M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] knpk13:
The easiest way is to probably flash stock OOS recovery using fastboot and then flash OOS from recovery. Since TWRP isn't fully functional and fastboot flashing every partition manually is tedious.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Sounds logical - haven't tried (and most probably won't), so cannot confirm.

The bad side of not having a fully functional TWRP is the missing ability for a nandroid backup, which normally allows you to be quite "experimental" in regards of your device - but the 7T Pro is my daily driver, so I don't want to lose my data... ;)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] pa.trick:
@MSe1969 : Thanks for the May update!

Am I the only one having trouble with Aurora?

After the update I am no longer able to connect to Aurora Store: First it says "no connection", upon hitting "try later" it fails to connect indefintely (before the update everything was working fine).

I didn't change anything in Aurora Store App + Aurora Services settings.

Wiping cache and user data in those two apps didn't help.

Any input for further troubleshooting would be much appreciated!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Hi,

Aurora sometimes can make trouble. If the things you've listed already (like "try again later", purge app/cache data and configure again) haven't helped, you may - in case you are using the 'iptables block script' - try disabling and directly re-enabling it.

Regards, M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] pa.trick:
That did the trick :) - thanks for your help!

Out of curiousity: the Google Play services displayed in the screenshot is actually microG in disguise, I suppose?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Yes, that is microG - best is to put it on the ignore list, DON'T "update"!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] pa.trick:
Sure didn't ;)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
I have a big problem..... I can´t get magisk root. If I patch the boot.img I´ll get a pachted img in download folder on device. After copy on my computer, the command fastboot boot magisk_patched.img should do the job. After reboot my device hangs in boot animation very slow. After I reset the device, it boots normal, but no root.

Any help about this pls?!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Did you try to flash Magisk the first time? Or did that work with an older release, but only now it won't ?

You may want to try fastboot flash boot magisk_patched.img - but if that leads to the same result, you have to flash the boot.img from the ROM zip file in the same way to restore.

EDIT: I myself do not use Magisk on this device, so my above proposal is a proposal to try, not an advice.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
@MSe1969

Thank u for ur reply.

Ok, I flashed magisk on every version. And it worked flawless. After update via updater i downloaded rom from link in first page. I extracted the boot.img from payload.bin and patched it with magisk. Then i have the patched version and copied it to my pc. last i installed it with fastboot boot magisk_patched.img. After that phone reboots and i use direct install via magisk. That used to wotk 3 times. now, it didn´t.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
As indicated before, the Magisk install instructions say 'fastboot flash boot magisk_patched.img', which really replaces the device's boot partition (afterwards, you need to manually reboot the device. e.g. via 'fastboot reboot'). 'fastboot boot magisk_patched.img' simply boots the patched kernel, without replacing the boot partition.

EDIT:

Normally, simply booting the patched boot.img shouldn't make the difference - maybe try to really get rid of any Magisk stuff on your device and start from scratch; maybe some module causes trouble?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
No way to get it run. Tried all... I have no more ideas-----------pffffff-------------
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] molekular:
Did you select the beta channel in magisk? It won't work with the stable channel.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Yes, I did that . I got it running now. I had to flash the recovery.img in both partitions and the boot.img with the new version again. That did it. Pfffeuuuu. Hard Job to find out, because i tried all the older versions too.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for the info. Should I mention something about Magisk in my OP?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
I don´t know, if i was the only one who ran into that problem. perhaps it makes sense to state it into the op.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Ok, I updated my wifes phone, she got the same and i did not have that problem. All went normal.

strange, is´nt it?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Yep!

At least: glad it worked out for you.

Normally, in IT, there is a logical explanation for everything - we simply did not find it, yet . . .
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] UnderDroidiana:
Hi! @MSe1969 Sorry to bother you but I ran into a stop and I am needing some help!

I compiled and signed successfully both the rom and the recovery.

I can boot in the user signed recovery (btw even the hardened recovery boots with no problem) then I sideloaded copy partitions and done the whole format, reboot etc..

when I try to sideload my rom I get to 22% then I am kicked out with a adb: failed to read command:Success

take note I can install of your rom seamlessly.

looks like my rom is broken somewhere but I don't really know where.

I tried to recompile without touching anything but no dice.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Hi, I had at the beginning exactly the same issue:

When I used the official recovery downloaded from LineageOS, same as when I used the recovery, which was build along with my ROM (hardened variant). What worked at the end was to build a "vanilla" LineageOS ROM (if you use my repos, as documented, with './switch_microg.sh default'), but with my signature, just to take the built recovery.img.

In fact, everytime, I test a new version of my ROM, I have to first flash my signed "vanilla" recovery, which is linked in the OP, before I am able to flash my ROM. If I try to sideload the ROM directly (which means that the recovery built along with the hardened ROM is active, exactly the same happens, what you describe).

If you say, that you are able to sideload my ROM - I would expect this only be possible, if you had flashed before my recovery...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] T0mu:
hi

if you are on oos 11 you need to downgrade before or you can directly flash the rom?
[Samsung Galaxy Note 20 Ultra Questions & Answers] satva49721:
Can someone explain whether process I go through on tmobile to unlock the bootloader? With the oneplus 8, I had to have 3 months paid off first and from there I could get the unlock code. Is it the same with note?

Thanks
[Samsung Galaxy Note 20 Ultra Questions & Answers] VioNeo:
I would also like to know that.

Hopefully someone can enlighten us on that
[Samsung Galaxy Note 20 Ultra Questions & Answers] coilbio:
That was years ago particular with one plus, they don't have a say anymore with these phones.

You have to pay to get it unofficially unlocked.

Search the forums, I don't know if we're allowed to post pay for unlock link even if theyre on xda.

Also, if your phone is still sim locked and you unlock the bootloader, it will remain sim locked. Only T-Mobile can sim unlock it and if you do sim unlock after you unlock your bootloader, it will relock your bootloader and it's stuck as locked forever.

So I'd sim unlock your phone before paying to bootloader unlocking it.
[Samsung Galaxy Note 20 Ultra Questions & Answers] VioNeo:
Thanks coilbio,

That was helpful and appreciated.!
[Samsung Galaxy Note 20 Ultra Questions & Answers] mindseye0803:
can you please clarify what do u mean by unlock?

If you need to unlock ur phone(network unlock) so that it can be used on any network then u can contact Tmobile to unlock your phone. You can contact Tforce on twitter to get ur phone unlocked. I was able to do that thro them.
[Samsung Galaxy Note 20 Ultra Questions & Answers] VioNeo:
Hi mindseye0803,

By unlock, I meant bootloader unlock,. My bad for not being specific on that.

Thanks for asking and hopefully, for help 😁
[Samsung Galaxy Note 20 Ultra Questions & Answers] mindseye0803:
check out this post - https://xdaforums.com/t/sampwnd-usa-model-bl-unlock-info-u-u1-w.4205981/#post-84374863
[Samsung Galaxy Note 20 Ultra Questions & Answers] VioNeo:
Thanks bro, much appreciated.
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz a30 stable

@physwizz

Zip installer from @Topser

Tester @krithik

-OneUI or GSI

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2080

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk 19.3 - 21.4

-Spectrum support enabled

physwizz - Repositories

physwizz has 284 repositories available. Follow their code on GitHub.

github.com
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Post2
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Post 3
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
why need magisk to flash the kernel?
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] hacker812c:
Thanks for this my friend
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
My pleasure.

I'm trying to work out why it doesn't work for some A30 users.

What is your bootloader?
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Let me know if it works without it
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] onyekurugitti:
can we use it in stock firmware?
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
If it's rooted
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] onyekurugitti:
can you say installation please

edit: i see sorry.
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Can somebody test version 3.35 please
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
dont work without it :(
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
yes.needs magisk
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] onyekurugitti:
bro i flashed infinity os 4.0 and magisk 20.4 can i flash this kernel and magisk again and use it in infinity 4.0?
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Yes
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz-a30-GSI

@physwizz

Zip installer from @Topser

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-CPU overclocked and underclocked

-Big: 312 - 2288

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk 21

-Spectrum support enabled

-mtp enabled
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz a305g GSI Q or R

@physwizz

Zip installer from @Topser

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2288

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk

Any remnant of SuperSU will cause a conflict.

-Spectrum support enabled

-mtp enabled

Sound issue fixed
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz v305g A30(OneUI)

@physwizz

Zip installer from @Topser

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2288

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk

-Spectrum support enabled

Any remnant of SuperSU will cause a conflict.
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
i really wanna try it, but due magisk is needed to use it, is useless for me cuz my bankings apps stop working when dtect magisk and cant be patched
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
You can hide Magisk from the app.

I do it for my superannuation app
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
I've been informed that you should be able to install it without Magisk.

Apparently you just need to ignore the ramdisk error.

I can't test it as I don't have a30
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Ignore the error and reboot
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] tutibreaker:
Done and dont install the New kernel, i just give up
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Ok by thanks for testing
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
My solution for you

Install Magisk

Install kernel

(Install Magisk uninstaller for no root)

Reboot
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
physwizz a30 stable

@physwizz

Zip installer from @Topser

Tester @krithik

-OneUI or GSI

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2080

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk 19.3 - 21.4

-Spectrum support enabled

Install Magisk

Install kernel

(Install Magisk uninstaller for no root)

Reboot

physwizz - Repositories

physwizz has 284 repositories available. Follow their code on GitHub.

github.com
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] physwizz:
Updated

physwizz a30 stable

@physwizz

Zip installer from @Topser

Tester @krithik

-OneUI or GSI

-Most securities disabled

-CPU Governors: conservative, ondemand, userspace, powersave, interactive, performance.

-Interactive is default governor

-SE linux enforcing

-CPU overclocked and underclocked

-Big: 312 - 2080

-Little: 208 - 1690

-GPU: 343 - 1300

-Extended battery life

-Works with Magisk 19.3 - 21.4

-Spectrum support enabled

physwizz - Repositories

physwizz has 284 repositories available. Follow their code on GitHub.

github.com
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] Rtix:
NIce i will test later .....thank you for sharing
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] thaygua8@gmail.com:
Gracias, funcionó perfecto para mí sin ningún fallo.
[Samsung Galaxy A30 ROMs, Kernels, Recoveries, & Ot] thaygua8@gmail.com:
Thanks, it worked perfect for me without any failure.