yashsingh1/xdaforums huggingface dataset:
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for confirming my assumption - ok, that means I will have to format my /data partition *yikes* !

Yes, regarding TWRP, the only way to be able to access the /data partition in recovery mode is one of the two unofficial TWRP's, which I have linked in my last post.

The way I see it, mauronofrio's 3.4.x TWRP allows to mount/decrypt /data and also offers MTP support, but I would not dare to do anything more with it (as said, backup miserably fails and flashing on an a/b device with a TWRP code base not being able to deal with that isn't ideal), and the linked 3.5. TWRP (important: tag 1.1 only) seems to be "almost" fully functional, except for nandroid backups and MTP support (the newer 1.2 version can't even decrypt, but maybe that is the one to use after having upgraded to Android 11...?)

So in regards to a "backup", I'll follow the below approach:

- Luckily, most apps I can simply re-install, and that's it (plus sometimes, re-logon)

- Contact data I have a synch solution in place with DavX5

- Signal has an own backup/restore solution

- Many apps store their relevant data on Internal memory, so a backup/restore of the Internal memory will do the trick (which however is crucial, as the Internal memory will be gone after formatting /data)

- However, for some apps, I really need to get their app data restored, which are located under /data/data/<java name of the app>

- So I'll make a list of those apps

And here, I will do the following and keep you updated, what worked (could be interesting also for you, @bestouff ):

1. An ordinary copy of the Internal Memory to my PC (as a fall back)

2. adb backup -apk -obb -shared -system

3. adb backup -f <file> -apk -obb <packages...> for each single package, I am interested in

4. adb pull -a /data/data/<package> in recovery mode

5. WiFi data is located under /data/misc/wifi and Bluetooth under /data/misc/bluedroid

Maybe any of you have a further idea on how to come close to a proper backup?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
When i came to that position to make a decision to wipe all my data, i asked myself the question, if it 's possible

to install all the programs first (after a fresh install) and then copy the former copied from the old version (to a hdd) android /data over the fresh data installation. normally all the data should be there..... But i was to faggy to try this..... :cool:
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
OK, I am now on LineageOS 18.1, finally.

Here my test build and an adapted 18.1 recovery (the linked recovery in the OP does its job, too):

lin18-microG - Browse /hotdog at SourceForge.net

sourceforge.net

Indeed, seems it's necessary to format the /data partition, as 18.1 cannot decrypt 17.1 and vice-versa.

Btw, none of the unofficial TWRP is able to decrypt either in 18.1.

So as for restoring the data, I did the following - due to the lack of a working TWRP:

BACKUP

- Made a list of all my apps, also with 'backup categories' (from n/a to crucial to preserve app data)

- Made a contingency plan on how to work-around loosing app data (manual setup, or e.g. registering a 2nd device to be able to re-register my primary device from the secondary device, if needed for specific web service, etc.)

- Copy "Internal Memory" (the 'visible part' when connecting the phone via USB), obviously

- Made an "adb backup -apk -obb -shared -all -system"

- For those apps, where I knew it's really difficult w/o the app data, I also worked with "adb pull /data/data/<java appname>" in root mode

RESTORE

Despite the docu telling differently, "adb restore" would only partially restore the app data, no shared internal memory and no apk files. Hence this is my restore procedure, finally:

- Install all my noted apps (but did not start them)

- Restore (shared) internal memory

- 'adb restore'

- Check all apps and do the manual setup, where possible

- I had some crucial apps, where I had to write back the app data via 'adb push' (in root mode) and afterwards re-do the permissions and ownerships; luckily, most of them worked again like a charm

Next steps:

- Work on the kernel (sec. patches)

- Fine-tune some nitty-critty stuff

Feedback to the test build welcome!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Wow, You're fast as a shark.

One Question,

did you update to OOS 11 new firmware first,or did you leave the "old" firmware on the phone?

I'll try the stuff today, but first I have to get volte and vowifi running.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
@MSe1969

Hi, Mate. Recovery is not working for me. If i flash it via fastboot i stay in bootloader mode (can't enter recovery). If i install 17.1 recovery, everything is well.

I could update to 18.11 with old recovery from 17.1

My device is a native a HD1913

The installation changed my device to HD 1917....

Weird.... Apart from that, all works. I have Volte an Vowifi symobols but it does not work. I got it to work before under 00s 10.

Ok, I went for DOTos (Android 11) after that. That changed my device back to HD 1913.

Under DOTos Volte und Wifi calling works (Vanilla without gapps)..... I dont know why it works there and not under Lineageos...

Went back to 17.1

"EDIT" Got it to work now (vowifi and Volte) under Lineageos 17.1. That's great. And it will work hopefully under Lineageos 18.1

" 2nd EDIT" After 2 Hours lost vowifi and volte after restart....:-(
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
With me, all fine - I observed however, wehn messing around with the TWRPs, that you should unplug the USB cable in fastboot mode, before rebooting...

Yes, the 17.1 recovery does the job as well - I simply wanted to build the most recent...

In fact, this value is "hard coded" and only a string, see the respective comit here:

hotdog: Set correct model number · LineageOS/android_device_oneplus_hotdog@d155446

Set to what is present on stock. Set to HD1917 (Global) since it makes more sense as an enforced model. Enables HDR playback in Netflix since it probably queries a database and only if its present ...

github.com

This stuff also depends on the carrier - unfortunately, this part is nothing, where I can really help...

I'll publish soon the next test build sith September sec. string and patched kernel...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Yeah, That is kinda stuff i got to get cleared. Thy anyways
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
What if I install the official Los 18.1 microg now to play around. If ur new rom is there, do you expect, that i could dirty flash your rom the over then existing rom?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I will upload still today a new 'test build', which in my opinion is "ready to go". I am now on 18.1 with my build and I won't go back. So I'd recommend you to be a little patient :)

To answer your question: The official LineageOS microG is signed with another signature than my build (obviously, that is the meaning of a signature) - so you can't directly "dirty-flash" - you would need to convert the keys first. If you are REALLY interested to go that path, you need to first look at the linesgeos4microg site to obtain the conversion linesgeos4microg => testkey and then I could help you with testkey => my build, but let me tell you: Things can go wrong...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Thank you very much for your advice. I'll wait for your version then. The other way is with a high efford, i think.

And of cause i do not want things go wrong. Did you upgrade firmware to oos 11 before, or did you stay on android 10 firmware?

Thy for reply.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I have upgraded the firmware, to be on the safe side. And here is the promised 'test build' - for me, all seems to be ok, "ready to go" -

feedback welcome

:

https://sourceforge.net/projects/lin18-microg/files/hotdog/lineage-18.1-20210915-UNOFFICIAL-microG-signed-hotdog.zip/download

Sec. string 2021-09-05

Applied many kernel patches on top of the official LineageOS kernel

Vendor blobs and device config updated to latest LineageOS changes

Fixed some minor bugs, which I have noticed during my own testing

Cheers, M.

P.S.: sourceforge has a very annoying "feature" to make uploaded stuff only available with a certain delay (normally between 10 and 30 minutes, in exceptional cases even more than an hour - don't know why), so if the link does not immediately work, be patient...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Many thanks for your outstanding work. I have problems to install Lineageos. Not the install, but if it is installed, the device is not recognized by my System. Unable to open device for local copies etc.

How did you upgrade to firmware OOS 11? Did you fastboot flash like stated by mauronofrio or did you go back to OOS 10 via Flashtool and upgrade to OOS 11? Thank you, Greetz,

Ray

"EDIT" Think I solved it. I am testing. Report later...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I have updated my firmware following the LineageOS documentation as indicated before and I recommend to do it this way, which means no flashing of OOS and no messing around with unofficial TWRP versions:

Get latest OOS (I used the Oxygen updater app for the download, as advised in the LineageOS wiki, but I found later this XDA thread, which in fact might be the better alternative)

Used payload-dumper-go app to extract the partitions to my PC, again as advised by LineageOS docu

Went into 'fastbootd' mode in Lineage Recovery (Advanced - Enter fastboot); the LineageOS docu says, that this

cannot

be substituted by reboot to bootloader

fastboot flash --slot=all <partition name> <partition>.img - see LineageOS docu

It seems that my 17.1 recovery might be better suited, at least I have that impression.

I worked mostly with my 18.1 recovery, but sometimes, I had to re-do the flashing and manually set the active slot via fastboot in order to get it working. I experienced at least two times a situation, where I ended up in an infinite, but normal speed boot animation.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Here are my first impressions.

I updatetd via going back to android 10 and update by updater. I have done it twice, so all went well after the second approach. I used the lineageos recovery 18.1 from your download. All good after second try, I did not sideload copy-partition, because i had problems the first attemp that part of system were unreadable.

Lineageos 18.1 works fluently. I have Volte and Vowifi sometimes. after #*#*4636#*#* and enable the first slider "mobile strenght" it is there. but no Volte or vowifi sign in notificationbar. I miss the advanced restart menu, It is vanished since update....:-( . But....Outstanding work, as I said before, I stay to the 18.1 version if no problems occur. Very smooth, I like it!
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
I also did not do the "copy partitions" thing - this is not necessary in our case. It is in fact necessary for exactly one situation, where you have a device on Stock ROM, which never has received any update and where never a custom ROM had been flashed. (Assuming you take care manually about the firmware)

Btw, the 'Advanced restart' menu option has been moved in LineageOS 18.1 out of the developer options to System => Gestures => Power menu (I had to search for it as well ;) )
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Ahhhhhh :love:
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
LineageOS 18.1

For information: I have created a LineageOS 18.1 thread
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
LineageOS 18.1 - future of this thread

Hi all,

I am now using my LineageOS 18.1 build as a daily driver and I did not experience any issues. Due to the fact, that there is no properly working TWRP for the Oneplus 7T Pro and encryption isn't compatible between 10 and 11, I will definitely not wipe my device again to get back to 17.1 to continue developing for 17.1.

I will therefore provide a final

untested

17.1 build with the October ASB patches and Sec. string 2021-10-01 (i.e. no kernel patches!), when the October ASB will be published and when I will have been able to test the platform changes on a different 17.1 device (e.g. OP3T, for which I also offer a thread).

Nevertheless, I recommend to upgrade to 18.1 in the next weeks and I hope to see you again in my LineageOS 18.1 thread.

Thanks for the interest in my 17.1 build. Please feel free to continue contributing to this thread, but be aware, that I have no possibility any longer to reproduce issues on 17.1. I will still try to support.

Cheers, M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Backup / restore for an upgrade

For an upgrade from 17.1 to 18.1, the /data partition needs to be formatted and there is no working TWRP to do a 'nandroid' backup.

The unofficial TWRP builds for this device are reported unreliable in regards to backup/restore in Android 10 and aren't able to decrypt Android 11. So for a backup/restore, I have worked with the following approach - by far not perfect, but workable:

If you don't use a contacts server (e.g. via DavX5), you can simply export your contacts into a file on your Internal Memory

Go through the list of your installed apps and identify the ones, where you really need the data restored (many apps do not store anything on the device, except for app specific settings).

Many apps offer an own backup/restore solution (e.g. Signal) - simply make sure you trigger a recent backup

Many apps store their data into a dedicated (public) directory on the Internal Memory, other apps store their data their dedicated directory under the Android folder in the Internal Memory

However - some apps only store their data internally under /data/data/<appname>

Have a "Plan B" handy, if you end up not being able to restore the specific data - take your time and make a list, so you don't regret later... (Don't forget browser favorites and such things)

In any case, backup the complete shared Internal Memory to your PC, as this will be gone, when /data partition is formatted!

Create a backup using adb backup (in fact, this is what Seedvault does, so you can also consider Seedvault). Be aware, that this method often does not work, as app developers may decide not to support 'adb backup' and if an app has set flags, that 'adb backup' should not be supported, then it won't work.

If you can't manually restore all the needed WiFi access data, save the file /data/misc/wifi/WifiConfigStore.xml on your device (you need an 'adb root' session for that). You can't restore the file directly, but it contains the WiFi ac cess data to allow you to manually restore the connections

For those apps, where you have no other choice than relying on their internal data (e.g. those apps having an own database), pull the repective /data/data/<appname> contents via 'adb pull' to your PC.

To restore, follow the below sequence:

- Restore the shared Internal Memory

- Re-install the apps (but don't launch them, yet)

- do an 'adb restore'

- perform the app-specific restores offered by the individual apps

- Manually restore the internal app data, where necessary (adb push into /data/data/<appname>), don't forget to restore permissions and ownership

If you have any detail questions, please feel free to ask, I'll try to answer. Unfortunately, this is far from being easy, but that's how it is...
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
FINAL build with October 2021 ASB patches - untested

Hello all,

as announced earlier, here comes my FINAL 17.1 build for the hotdog device:

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

Security String 2021-10-01

Bromite System Webview and Browser updated to 93.0.4577.83

Please note:

This build is untested! As indicated before, due to the lack of a properly working TWRP, I am not keen on wiping my device etc. I went through that pain once to upgrade to 18.1 and the hotdog is my daily driver.

I haven't touched the kernel, that is why I have set the sec. string to 2021-10-01 to indicate this. This means, that no device-dependent component has changed compared to the last build. As only the device independent parts have been updated and are proven to work on other devices, I do not expect any issues.

Nevertheless, I haven't yet activated an automatic OTA update for this build, so you have to manually update your device. This means, you cannot update "by accident", you need to actively decide on doing so.

However - once I receive feedback, that the update went smoothly, I will activate the OTA update for this build. I would therefore like to ask those people manually updating to provide feedback.

As mentioned, this is my

final build

, so please consider updating to 18.1. In my 18.1 successor thread, I will very soon publish the next build with October 2021 ASB patches included.

Regards & happy flashing

M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
EOL

I see no reaction on my last post and also only a very few downloads of my final build, as well as no request to enable OTA for that final build. At the same time, I see reasonable participation in my 18.1 successor thread.

Information about the successor thread and build, as well as tips & tricks on how to upgrade have been posted here as well. So I think it is time to declare the EOL of this thread (and the 17.1 build).

Once again, thanks a lot for your interest and participation - looking forward to seeing you in my 18.1 thread.

Cheers, M.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Well, once again, Thank you for your work here and in 18.1 as well. You performed outstanding roms for our pleasure, safety and conveniance. I hope i can follow these roms in future continuing perhaps with another phone with the same reliability as it's for now and then.

Your roms perform best and are save as well, what fits my opinion in safe use of a smartphone.

Thubs up, therefore ,

Greetz, Ray

"EDIT" I buy an "M" :-)
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Oswald Boelcke:
Thread closed on request of OP @MSe1969
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for reporting back, saves me some time for not needing to test on my end.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] Azev:
Battery life
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Hi, I am new to this Forum, i changed from Mimax 2 to OP7tpro

First of all, Thanks to the developer, I have been looking for a rom like this a long long time.

I used to use HavocOs. But here in this Forums HavocOs comes with Gapps included. A no go for me.

I got some Questions, before i gonna install this rom. I use Netguard on my old phone. Is it obsolete or does this interfear with the Firewall included? Can i use Nova launcher in this rom?

Do I have to host an own server for cloudflare.

These are my questions.

Thanks in advance,

Ray
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Thanks for the positive opinion.

You can continue to use Netguard, but it depends, on which functionality of Netguard you are keen on, to decide, whether you would still need it. The built-in firewall let's you control, which app could access the internet by WiFi or mobile data. The shipped hosts file blocks well-known ad/spyware sites on OS level. And the option to block Google/Facebook uses iptables on OS level to block the traffic. All without launching a local VPN.

Nova launcher: No idea in particular, but Android allows you in general to make use of an alternative launcher. So I'd say: Why not?

Cloudflare is only a "fallback setting": Normally, the DNS is - if you don't set an own "private DNS" - set automatically by your carrier (mobile data connection) or the one provided by the WiFi router (WiFi connection). If no DNS is determined this way, the Android default is 8.8.8.8 (Google). And this default has been changed to 1.1.1.1 to point to Cloudflare instead (considered "less evil"). That's all - no need for any "own server".
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Thank u very much for ur reply.

Due to ur explanations i'll gonna try this rom.

I report, when done. First of all i wait for the shipment aprox wednesday...

Nice rest of the weekend. See ya soon
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] molekular:
Hi,

first oft all thank you so much for sharing this rom with the community. A hardened rom with improved security features is so hard find - especially with the trend among roms for this device that "comfortably" already contain all the proprietary G. code. It is good to know someone else cares and even shares it.

I installed successfully and everything works just fine. I rooted the phone successfully with a magisk_patched boot.img - but I keep losing root upon reboot.

Does anyone have an idea what could cause this? I would suspect this to happen with a locked bootloader, but I am a little lost here. Thank you!

--------------------------------------

Went through complete installation process again - same result, no root after reboot. @Azev_new: Did you get permanent root access?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Allright,

As I stated I am new here. Just to make sure that i got all of the process in the rightious way. I have not flashed a Rom like this before.

I wrote the whole actions to do down. If someone could correct me if i got something wrong would be a pleasure for me.

Here it comes:

1. Unlock Bootloader (no Prob)

2. Flash via fastboot the same recovery into both recovery partitions:

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

3.Then i ll do:

adb sideload copy-partitions-20200903_1329.zip

to get the right partition sizes.

4.Next in recovery mode I make a factory reset and format data / factory reset.

5. I'll continue to main menu

Then i sideload with:

adb sideload lineage-17.1-20210122-UNOFFICIAL-microG-signed-hotdog.zip

After this it should successfully reboot with Lineage hardened?

Correct?

Thy Ray
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] molekular:
This sounds about correct - the official LineageOS hotdog installation Wiki and MSe1969's instructions make this an easy task. From my experience it is helpful to get familiar with the key combinations first and also to be familiar with options if your stuck somewhere in a bootloop, eg. how to get back to stock rom via fastboot. It is easy, but less stressfull if you check that out in advance.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] RayfG:
Thank u for ur immideate reply. I check this out. I only have linux, but i dowload the unbricktool cause my son got an pc with windows.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Correct - just two remarks:

The copy-partitions zip does not resize anything, it simply copies the content from all active partitions to the inactive.

And the reboot after side loading the ROM should be triggered by YOU while still in recovery

EDIT: Corrected myself - copy logic is not a -> b, but active->inactive, which may be a->b if a is active or b->a if b is active.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
Hi,

I can only guess, as I do not use Magisk.

First question:

Did you at the end really flash the modified boot.img via fastboot flash magisk_patched boot.img, or did you only boot it fastboot boot magisk_patched boot.img ?

If you flashed, maybe try explicitly flashing to partitions boot_a and boot_b ?
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] molekular:
Thank you for the quick response. I did boot the magisk_patched.img. I will try to flash it to both partitions and report back.
[OnePlus 7T Pro (Regular & McLaren) ROMs & Dev.] MSe1969:
If you only booted, it is clear that it'll get lost after a restart. If you simply flash to the active partition, it should be ok