Develop Bugs

2 XL flashing stock images, target didn't report max-download-size

Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan

jan_ruc said:
Hello,
I managed to screw something up, and now my phone is in a bootloop.
I have already posted a question somewhere else on this forum, but I got a suggestion to post it here.
Here is the link to the thread.
https://forum.xda-developers.com/ge...ges-target-t3803741/post76807253#post76807253
Please, I really need to get this phone up and running again.
I'm going to try everything that is suggested.
Thank you very much,
Jan
Click to expand...
Click to collapse
Where are you at right now, and what have you all tried besides the skipsoft?

Badger50 said:
Where are you at right now, and what have you all tried besides the skipsoft?
Click to expand...
Click to collapse
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.

jan_ruc said:
I tried downloading the official(8.1.0) and the latest version of P beta from Google, and ran the flash-all.bat. Running that said that the max reported download size was not reported and failed. As far as I know Android should still be installed, TWRP still works and thats pretty much it.
Click to expand...
Click to collapse
Try a different USB cable.

ilal2ielli said:
Try a different USB cable.
Click to expand...
Click to collapse
I don't have any other cables. I will ask my friend to lend me his and try that. But what if that doesn't work?

I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.

Ariac Konrel said:
I had this issue on my old tower. Plugging my phone into USB 3.X ports didn't allow it to flash images via fastboot with the same error. I plugged it directly into the case's 2.0 ports and it worked perfectly. My new tower doesn't do that, though. Oh and I had two brand new cables.
So basically try a different port/cable.
Click to expand...
Click to collapse
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?

I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.

dabaang_khan said:
I had a similar issue. I had to use a different PC to get my phone back to work. Try restarting the pc or a create a different user in Windows and see if that helps. Also there is a very useful script called Deus script on the forums here for bootloops try it.
Click to expand...
Click to collapse
Do you mean Deuces? I tried it. Should I try it again on a different computer?

jan_ruc said:
Thank you very much.
I will try every port I find on every device I find.
What shoul I do if I find that it works somewhere?
Should I simply run flash-all.bat?
I want to go back to full stock.
It's weird because that cable and that port work very well for data transfer and adb actually works. Fastboot works as well...
Is the problem in that command only?
Click to expand...
Click to collapse
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.

Ran into the same issue few days ago, changing cables and ports didn't help but restarting the computer several times did.

Ariac Konrel said:
Yeah, the case was the same for me.
Super weird issue.
OH, there's one more thing I can think of. What OS are you running? If it's Windows 10, it could also be that. MS and their automatic updates override Google's driver so I always disabled that. It's weird, but that was another issue I had at some point.
You might see a LeLand driver or something similar for it, I don't remember the exact name. So that's also something to look into if you can.
For full stock run flash-all.bat, this will erase all the phone's data though.
Click to expand...
Click to collapse
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...

jan_ruc said:
I do have a laptop that is running Win 7 and my father's laptop that has Vista on it for some reason.
Also I relaized my friend has a Type-C port on his desktop so will probably give that a try, and use the original cable.
I forced a Google backup before I messed it up so I don't really care about the data.
By the way what's the matter with the
"fastboot: error: Device does not support slots"?
Is that anything critical? Or just another weird error because of the cable/port?
Also: I did some digging throu the system files with TWRP and most of the root directories are empty...
Click to expand...
Click to collapse
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok ?

Badger50 said:
See, look at all the advice you got. From what I've read, your USB cables appears to be your #1 issue. Like others have said, get a good USB A to USB C cable, and you'll likely be ok
Click to expand...
Click to collapse
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!

jan_ruc said:
Indeed, thank you! I'm actually kinda stuck installing the newest ADB and drivers right now... Can someone share a link to the latest 8.1 image avadible for this phone and the adb that I need, please? This laptop is currently quite clean and I really don't want to mess around anymore.
Thank you all!
Click to expand...
Click to collapse
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface ?
https://developer.android.com/studio/releases/platform-tools

Badger50 said:
Here's the factor image page. Just look for Taimen, June image at the bottom of the section. Use the OPM2 unless your on T-Mobile.
https://developers.google.com/android/images
And this is the SDK/platform-tools that I use that also has the adb interface
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?

jan_ruc said:
Thanks! Now I simply extracted the platform-tools in a folder C:\adb.
Downloaded the image, but the phone won't show up when I run adb devices...
On Windows 7... On my desktop it shows up the sec I run it.
Installed Google drivers as well.
Say could I simply "adb push" the image on the phone and flash it from TWRP?
"adb push" works. I just tried and pushed the image on the phone. But it says "invalid zip file format".
Could I extract the zip and push all the images one by one?
Click to expand...
Click to collapse
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.

Badger50 said:
You've got to get in the mindset that though adb and SDK/platform-tools are part of each other, they are also different. Adb is mostly used when your device is on, whereas sdk/platform-tools is used as your bootloader interface, where you do your fastboot commands.
After you installed the SDK, there should be a folder within SDK named platform-tools. That's where your extracted files from the factory image go. You don't put the full factory image in there. The pics should give you an idea what I'm taking about. You'll actually open your command prompt on the platform-tools folder so you can execute your fastboot commands.
Click to expand...
Click to collapse
Now I have installed Android Studio and selected the SDK tools that weren't selected before and installed them.
Still my question remains... Since the USB cable is the problem, could I flash it from TWRP? I don't mind keeping TWRP installed so if I could just reinstall the OS. That would be lovely.
On the other hand. Tell me what to do, and I'll do it.

Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img

CyberpodS2 said:
Another route to go of your struggling with paths is my convoluted method that works for me. Every month I download the latest factory image and the latest platform tools and extract both to the same folder. I also put the TWRP.img file and also dueces script there too. So each month I have a stand alone installation. I have used the dueces script the last two months with good results. (I just like having both slots up to date in case I install a custom Rom). If you choose to go the route with the script there is an additional zip file to extract. At the end, all the loose files are in one directory beside some folders for platform tools. Let us know if you need additional info. Note for June they changed something in the syntax so dueces made a new version of the script. Here are the files in my latest dir.
deuce-flash-all-v4.5.bat
platform-tools-latest-windows.zip
taimen-opm2.171026.006.c1-factory-21236059.zip
Twrp-3.2.1-2-taimen.img
Click to expand...
Click to collapse
At the moment all I really want is to get this phone working...
I just re-ran the flash-all.bat with the same set of folders as you have and got this:
< waiting for any device >
Sending 'bootloader_a' (36380 KB) OKAY [ 0.937s]
Writing 'bootloader_a' FAILED (remote: Flashing is not allowed for Critical Partitions
)
Finished. Total time: 0.947s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.002s
fastboot: error: Failed to identify current slot
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12g
getvar:version-baseband FAILED (remote: unknown command)
fastboot: error: requirements not met!
Press any key to exit...
So I guess that means criticlal is locked?
I ran fastboot flashing unlock_critical:
fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.002s
EDIT*: I rebooted the phone in hopes of you know... Any progress. It seems to be stuck on the "G" loading screen.
From this point could I just flash a custum ROM via TWRP?
I just want it to work.

NOST - Improved Version of OST LA 6.0.4 (v0.6, 02. Mar 2019)

"NOST" - short for "No Service Tool" (or "Nokia Service Tool" but that sounds too official and boring ) is a small hobby project I've been working on in the last couple of days.
It aims to make the service tool for Nokia 8 (and HMD Phones in general) more useable, user-friendly, and straigtforward to use, and after having to test it myself, and also
making a small beta test in the Telegram group for Nokia 8, I feel like posting it here so others can try it out too if they want.
First, to be clear: NOST is not completely my work. It is based on OST LA 6.0.4, which was made by HMD/Foxconn. Unlike the previous OST Patches, NOST does not replace
the executable with a hacked one, but instead wraps it and patches the methods that need patching at runtime. The result is that the changes are completely opensource
and readable by others, while the underlying OST files are not modified at all. I tried to base it on a different (i.e. newer) version of OST, but those are pretty much unpatchable,
at least not with a serious amount of reverse engineering, which brings not only time issues but legal ones as well.
NOST changes a couple of things, compared to the unmodified OST LA:
It removes the need for authentification against HMD/FIH servers (really, shoutout to the one who made the original hack, even though I could not use their code)
Moved the logs folder to the same folder as the application, as opposed to somewhere on the system to make debugging easier
The options for flashing firmware images appear reliable now. (At least for me they only appeared sometimes if not never on the original OST).
Removed one of the options that if it appeared crashed the flashing process ("Check System AP Status")
One user of the Telegram group had issues where OST would crash because it detects an invalid locale setting in Windows. NOST just catches that issue and defaults to english
Removed the "Edit Phone Information" button. It never worked and it's only purpose was to make the "Next" button appear, which works like it should now as well.
NOST refuses to flash your phone if your bootloader isn't unlocked critically. The old OST would just try to flash but never make any progress which confuses inexperienced users.
Perhaps the most important change: NOST allows to flash modified firmware images without the need to extract and modify them by hand.
With the original OST, people who wanted to reflash their phone had to download a firmware bundle, extract and edit it to be able to use it with OST LA 6.0.4, since the newer versions
had unpatchable issues that prevent using them. Repacking the images in a format OST expects wasn't possible either since that enabled some sort of signature algorithm on the modified
images and caused the flashing to fail. NOST solves this problem by allowing the use of a different packaging format. Those binaries still need to be extracted but it is done transparently in
the background without the user having to download any other tools. The formats that can be used in images are .zip and .qlz
.zip Firmwares:
.zip firmware files are simply archives of the (edited) files that would normally be extracted from an .nb0 file. This means, if you extract a .nb0 with the extractor found on XDA, the contents
of the *_unpacked folder it creates should be the contents of your .zip.
.qlz Firmwares:
.qlz files are based on QuickLZ compression, which gives them a small size but also a low decompression time.
The tool to generate them is called exdupe. Generating these images is pretty straigtforward. Assuming you are on windows, download the exdupe
tool from the link above (or take it from the NOST Tools/ folder) and copy it into the folder that contains the unpacked .nb0.
Code:
- exdupe.exe
- <nb0 name>_unpacked/
- <nb0 name>.mlf
- ....
Open a commandline in that folder, and run the following command:
Code:
exdupe.exe <name of the folder to compress> <name of the firmware file>.qlz
You should already see how fast it compresses the firmware folder now. As a reference: Compressing the latest Nokia 8 firmware (about 4GB) takes maybe 30 seconds and yields a 2GB file.
Repacked Firmware Bundles:
I created .qlz images of the May and November firmwares, as well as one of the various Pie Maintainance Releases.
You can find them here: https://tmsp.io/fs/xda/nb1/firmware
I already successfully reverted from December Security Patch to November using NOST, and then updated back using OTA Sideloading without problems.
As always when working with flashing tools, proceed with caution!
How to unlock to critical:
KonikoO said:
For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Download:
The actual tool: https://github.com/StollD/NOST/releases
Drivers: https://github.com/StollD/nokia-driver-installer/tree/master/out
Source Code: https://github.com/StollD/NOST
License:
OST LA 6.0.4 is copyrighted by the respective authors. It is not modified permanently.
The custom NOST code is licensed under the GNU General Public License.
Icon by Freepik © Flaticon

I tried this is working,nice tool.
Thanks dev.

Thank you THMSP! very cool?
Sent from my TA-1004 using XDA Labs

Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?

Lee Castro said:
Can flash the May and November update but cannot flash latest Pie with this tool. I flashed Pie but returned back to November update?
Click to expand...
Click to collapse
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?

THMSP said:
Yes, you can revert back from Pie to Oreo using this. What is the issue with Pie for you?
Click to expand...
Click to collapse
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.

Lee Castro said:
What I mean is if I flash the Pie file you provided I just returned back to Android 8.1 Novemeber update no changes at all. Maybe there something wrong with the Pie file you uploaded. But the rests are all working fine with the tool.
Click to expand...
Click to collapse
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.

THMSP said:
Thanks for the hint, I will take a look. Probably just derped when pulling partitions and renaming the images (might have worked in my November folder by accident).
EDIT: I repulled the images from Pie (I indeed somehow worked in my November folder when making the image), repackaged them and updated the version in the drive folder. You should now be able to flash Pie. Sorry for the mistake.
Click to expand...
Click to collapse
Thanks again,This is really a big help.

Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.

hey there! wonderful tool to have. Thank u so much

Not working in my laptop say a software need a to update

Blackhacker07 said:
Not working in my laptop say a software need a to update
Click to expand...
Click to collapse
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.

THMSP said:
If you have dependency issues I would suggest to install OST LA 6.0.4 first, so you get its dependencies, until I can make a proper installer for NOST.
Click to expand...
Click to collapse
Could you perhaps figure out how to get rid of the unlocked bootloader message?

ironman38102 said:
Could you perhaps figure out how to get rid of the unlocked bootloader message?
Click to expand...
Click to collapse
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).

THMSP said:
Are you talking about the error message that appears when you press the Next button to start flashing?
If yes, your bootloader needs to be unlocked to critical, then the message won't appear.
If you are unsure if your bootloader is unlocked to critical, do "fastboot oem device-info", it will tell you.
If you mean the message that your phone displays when booting with an unlocked bootloader then sorry, I doubt that's possible (I think it is embedded into the bootloader).
Click to expand...
Click to collapse
Actually its in splash.img that can be dumped. Its the hex editing possibly that might be a problem for someone not familiar with it

How to flash it's says this...

Blackhacker07 said:
How to flash it's says this...
Click to expand...
Click to collapse
What do you mean?

KonikoO said:
Wow, this is something we've been all seeking for a long time now ! For those who wonder how to unlock into critical state :
Reboot into bootloader download mode and execute those commands :
fastboot flash unlock *unlock .bin*
fastboot flashing unlock_critical
Afterwards you should be able to flash provided .qlz with NOST.
Click to expand...
Click to collapse
Thank you so much for this advice. I wouldn't have ever figured out how to unlock critical on my own and that was the thing that was preventing me from flashing. I tried searching the other OST LA flashing threads as well but this info seemed to have been missing, or then i completely missed it. Thank you so much anyways. If anybody else is trying to figure out why their OST LA or NOST is giving them the se_err_adb_cmd_get_fail_result error, this should help. I just used the unlock.key in place of the *unlock.bin* in your command and it worked.

Can you please upload Oreo December update stock and patched boot image. TIA

Yesterday I noticed that my Pie Image was still not quite useable, since it contained a corrupted system partition.
This seems to have happened because of my Magisk Setup and me only replacing the boot partition image and not uninstalling Magisk completely.
I rebuilt the image, to be fully stock, and also included the latest B07 update that @hikari_calyx uploaded yesterday. You can get it from the drive link in the OP.

T-Virus - Infect your Nokia 8 with Project Treble (2019-07-02)

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research about modifying your android system before flashing this!
* YOU are choosing to make these modifications, and if you point the finger at
* me for messing up your device, I will laugh at you. Hard. A lot.
*/
(if you expected the Resident Evil references to stop, you just got gnomed)
What is this?
T-Virus (for treble-virus) is a tool that takes a stock Nokia 8 firmware and "infects" it with various parts from the Nokia 8 Sirocco firmware, generating a firmware bundle that is compilant with Project Treble and that can be flashed to a Nokia 8 using NOST.
Firmware Sources
The base of T-Virus is the stock Nokia 8 firmware image (5150 / April Security patch at the time of writing). When being run, the build script takes those files and replaces the partition table with the one from Nokia 8 Sirocco. This required for creating a vendor partition that the stock Nokia 8 does not have. The vendor image is taken from the Sirocco firmware as well. During the build, the vendor image is mounted as rw, and various files are copied over from the stock Nokia 8 system image, or get patched to properly support the minor hardware differences between the two phones. Those actions are defined through very basic scripts inside of the vendor folder in the repository.
The boot image is a modified version of my umbrella kernel, which has support for early mounting vendor. It also includes a TWRP build with full support for Project Treble.
SELinux Hell
Because Android does some very weird stuff with SELinux contexts, you cannot launch a service file when it has an unknown context. We have to fix that by force-setting the SELinux context manually, but due to how SELinux works, this is only possible on a Linux system without SELinux. This means, that you cannot build this on a distribution with SELinux (Fedora in my case). I fixed the problem by building the images in a Ubuntu VM.
How to build?
First you have to download the latest firmware image from https://tmsp.io/fs/xda/nb1/firmware, and the exdupe tool from https://www.quicklz.com/exdupe
Extract the firmware into a folder and then clone the repository, like this:
Code:
$ mkdir firmware
$ ./exdupe -R ~/Downloads/NB1-5150-0-00WW-B03.qlz firmware/
$ git clone https://github.com/resident-nokia/t-virus
$ cd t-virus
The build script has two options you have to set: a version and the path to the extracted firmware. This means you have to run it like this:
Code:
$ ./build.sh --version v0.1 --firmware ../firmware
Leave it running and when it asks you, enter your sudo password. This is required to mount the Android ext4 partitions and edit the files that are only accessable by the (Android) root user, and retain their permissions.
When the script has finished the flashable firmware image will be inside of the out folder. You can optionally package this as a .qlz file again using exdupe.
What works?
It boots
Data decryption in recovery
Flashing GSIs / OpenGApps in recovery
WiFi
Mobile Data
Bluetooth
Sound
Vibration
Calling
Hardware buttons
Fingerprint
Camera
GPS
NFC
SDCard
Multi SIM
4k Video
What doesn't work, or isn't tested
Haptic feedback for Hardware buttons
Bluetooth headphones don't get registered properly
Nokia OZO audio support is missing
Fingerprint sensor is reported as being on the back of the phone
There might be issues with USB transfer under Windows
VoLTE (untested)
How to install?
WARNING: This might not be useable as a daily driver. Continue only if you are able to troubleshoot things if neccessary (bootloops, bricking the phone, causing the alarm app to declare nuclear war)
You can download the latest release from the releases page on the repository. It is a .qlz firmware, so you will have to flash it through NOST. You will need a completely unlocked bootloader. When flashing, make sure to select the "Erase Userdata" option, not doing this will most certainly bootloop the phone.
After the installation completed, your phone will reboot into phh's AOSP GSI. If you want to use a different GSI (you most likely will), follow these steps:
Download your favorite GSI
Unpack every form of compression, so you end up with a .img file
Boot into recovery
Copy the .img to the internal storage of your phone, or to your SDCard
Select "Install" -> "Install .img", select the image file you copied and flash it to your system partition
Then install OpenGApps or any other modifications you like.
Wipe /data to allow the new system image to boot properly and then reboot
To update to a newer version without having to erase userdata, download the zipped vendor image from the release page, and flash the image inside in TWRP.
If you want to go back to stock, simply download the 5150-revert firmware and flash it with NOST, with the "Erase Userdata" option enabled. It will revert all changes T-Virus made to your phone. Firmwares from https://tmsp.io/fs/xda/nb1 will not work.
Links?
Repository: https://github.com/resident-nokia/t-virus
Download: https://github.com/resident-nokia/t-virus/releases
Reverting to stock: https://github.com/resident-nokia/t-virus/releases/tag/5150-revert
What if I have a bug?
Upload a proper bugreport. This means logcat and dmesg. If you don't know how to get them, google it. Also, describe the issue and provide steps to replicate it. Everything else will be ignored.
I don't daily drive this phone anymore. I am doing this just because it is an interesting technical challenge. I don't have as much motivation to fix bugs than someone who daily drives it.
I want to say thank you!
I usually don't do this, but since this involved a lot of work on my side, I would be grateful if you would want to say thank you by buying me a coffee (or two): https://paypal.me/thmsp

Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?

kosmatyj said:
Ok. After the flashing we have a phone "infected" by the Project Treble. But what it gives to end-user? What is profit of this?
Click to expand...
Click to collapse
The ability to install GSIs (Generic System Images). Basically everything from here: https://forum.xda-developers.com/project-treble/trebleenabled-device-development

Oh! Sounds pretty good! Thanks. Will think about it. Really expands posiibilities and needs to be tested.
---------- Post added at 10:54 ---------- Previous post was at 10:29 ----------
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?

kosmatyj said:
Q: Should Ihave an Android Pie be installed first or it can be flashed over ony ROM version (I currently have Nougat ROM installerd on my Nokia 8)?
Click to expand...
Click to collapse
It could work, since it is a modified firmware for reflashing, but just to be sure, update to Pie through OTA. That's what this has been tested with and you won't update your bootloader in the process which eliminates some possible incompatibilities.

What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?

kosmatyj said:
What is password for t-virus-20190703.qlz? Should I flash the TV-20190703-vendor.zip before or t-virus-20190703.qlz is all I need?
Click to expand...
Click to collapse
It's all in the instructions. There is no password on the qlz file. You can't extract it, you have to flash it using NOST. The zip is for updating from previous versions and not for the initial installation.

Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.

kosmatyj said:
Oh, I understood. No need to unpack, just download and flash over NOST, right? Thanks ones more. It is new for me, that`s why I have so much questions.
Click to expand...
Click to collapse
Yes. Just follow the instructions in NOST and select the T-Virus .qlz when it asks you to. Also, make sure you select the "Erase Userdata" option in the drop down menu that appears after selecting the .qlz.

Thank you for this - hope you enjoy the couple of coffee's

Amazing work. Can the current Android Q GSI be used?

comatrices said:
Amazing work. Can the current Android Q GSI be used?
Click to expand...
Click to collapse
When I tried it it didn't boot. Your mileage may vary, but you probably have to wait until the source code for Q has been published and people can build real phh GSIs from it.

Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.

kosmatyj said:
Hello! Author, don`t you planning to build the same but for Android 8.1? Your work is great anyway but would be just amazing to have an Oreo in this appearance. Thank you.
Click to expand...
Click to collapse
Just flash an Oreo GSI? I know you can run Pie GSIs on Oreos vendor, so it should work fine the other way around.

Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).

kosmatyj said:
Nah! Didn`t work. After "android" logo it drops into download mode. AOSP 32 (last version of A 8.1 GSI).
Click to expand...
Click to collapse
I am not exactly sure if I understand you correctly, but Nokia 8 is not an A-only device, it is an AB device. You need to flash the AB image of AOSP, not the A one.

Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.

kosmatyj said:
Right, I did exactly like you said. system-arm64-ab-vanilla-nosu - image that I flashed couple minutes ago. Downloaded from here: https://github.com/phhusson/treble_experimentations/releases/tag/v32
I`m sorry about my English. I`m Russian.
Click to expand...
Click to collapse
Ok, then it probably doesn't work the other way around (Oreo with Pie vendor). An Oreo-based T-Virus is unlikely to happen though, because Siroccos Oreo vendor has some problems (calls not going through properly), and I dont want to maintain two versions of it because, as said in the OP, I don't use my Nokia 8 anymore. It seems like Pie is all you can get with this for now, sorry.

Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i miss something? Whats with Security Enabled Linux?

just4me12 said:
Hi all. Just to make it clear. The procedure for the Nokia 8 is:
1. Unlock Bootloader
2. Do "critical unlock" (fastboot flashing unlock_critical)
3. Flash "t-virus-20190703.qlz" with NOST?
Did i missed something? Whats with Security Enabled Linux?
Click to expand...
Click to collapse
That's right. Don't forget to add "erase data" option while flashing t virus with NOST otherwise you'll end up in a bootloop.

UBports - Ubuntu Touch - Titan - Installation 2021

This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms
​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!

Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
I just finished installing UBtouch, without any problem

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.

Arthur Mateo said:
Hi, I'm new on the forum and I don't understand a lot about apps and systems development, but I would like to learn. I followed the entire tutorial for installing Ubuntu touch on my moto G2, but the phone starts on the ubports recovery screen (I left images below).
what should i do after the phone boot on this screen?
I also apologize for my english.
Click to expand...
Click to collapse
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart

Zarosky said:
do not touch anything and look at the computer that continues to do its work, when the cell phone is finished it will only restart
Click to expand...
Click to collapse
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.

Sanizol said:
Hi, I'm new here and if i am honest joined just to ask questions here. I have tried what you said (many thanks as I wasn't sure what to do after finding the link for the rootfs tarball was dead), it is the same command Walidham stated for installing 16.04 but that didn't come with the commands for installing the flashing tools for this method and I probably wouldn't have noticed that command anyway in the original post as I was mostly paying attention to the original instructions for 15.10. Anyway, I tried this method and it all seemed to be going fine but every time when it gets to a certain point it says on the phone that there is insufficient space for pushing one of the files. I am actually using a Moto G2 4G LTE Thea, not Titan so it may not work but I thought I'd try it anyway and I don't know that this error is to do with that as it is to do with running out of internal storage, though I know sometimes error are diagnosed as totally different errors so that might be happening, I don't know.
Mine is 8GB but there is nothing smaller than that. I have changed the data partition format to ext4 by the way and I have tried running this with and without wiping system, data and cache partitions beforehand. The flashing process only gets anywhere when they are present and not wiped, otherwise it complains that it cannot boot recovery. I also noticed that the folder that seems to be referenced by the command has new files even from today (the 25th that is) and when I ran the command it was trying to flash version 779. When you did it it would have been an older version as the files relating to 779 seem to be brand new. I also assume these files are probably experimental. So I don't know if this is a non-working combination, or if I am doing something wrong, or if there is a way to change which version it is trying to flash, or if I can get a rootfs file that will work (I don't know anything about them or what exactly they do) and do it manually. I am also not a developer and am low on technical knowledge (as much as it hurts my ego to say it) if I am honest and I am using Linux mint 20.1 on the PC side of things, which of course is Ubuntu/Debian based so I imagine shouldn't be a problem here.
Thanks for the guide, thanks Walidham for the port, and if you know anything about my error or something else to try I'd appreciate it if you got back to me. Thanks!
Click to expand...
Click to collapse
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.

Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!

Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.

Arthur Mateo said:
Thanks for the feedback. Really, I think I need to be more patient, but my anxiety doesn't help (lol).
I wait for the computer to finish its work, but the terminal returns the error "Failed to enter Recovery" and the cell phone keep in the ubports recovery screen.
If you have any tips, I appreciate it.
Click to expand...
Click to collapse

Arthur Mateo said:
Update: It works!
I actually succeeded in installing the system on the 7th of this month, but I just said it now.
The system has several bugs. The bluetooth, the flashlight and the GPS doesn't work, for some reason the cell phone restarts when I connect to the wifi at home (which doesn't happen when I connect to my main cellphone's wifi in router mode), the notifications and settings bar seems to be cropped, and whenever I turn on the screen the option to turn off or restart the phone appears.
Anyway, I really liked the system, and I would like to contribute to it by solving or notifying the presence of these bugs in the software.
And thanks for the help.
Click to expand...
Click to collapse
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
In the device it looks like this:
Yeah, I think it goes back to Ubuntu Recovery Interfaces

Sanizol said:
I wasn't sure at first whether it was meant to be left alone when it brought up the ubports recovery screen but eventuslly concluded it was. I'm busy this weekend but I will try and get some screenshots of my error when I can. I had settled back into using Android for the time being. I'll try what you said you did as well when I get the time. Thanks!
Click to expand...
Click to collapse
Hello bro, did you succeed ？

Zarosky said:
This is an installation mode that I use - This method I took from the Moto g2 Titan telegram group: https://t.me/TitanRoms​​I did it from a debian-based distribution
(1) Download these two files:
click-ubuntu-policy_0.1_all.deb
drive.google.com
https://drive.google.com/file/d/1LHqKyr_pOFiRz9IhXHiyQkru0y7rrTSl/view?usp=sharing
(2) open the terminal and go to where I download the files, and install them with the following commands.
sudo apt install debsig-verify kpartx
sudo dpkg -i click-ubuntu-policy_0.1_all.deb
sudo dpkg -i ubuntu-device-flash_0.34-0ubuntu1_amd64.deb
(3) Put your moto g2 in bootloader mode (power button + volume down) and connect it to the PC
(4)Put this command in the terminal and press enter, wait for the whole process to finish.
ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
If everything goes well, in a few minutes you will be using UBtouch on your moto g2 titan.
Many thanks Walid for this Port! and https://t.me/TitanRoms for sharing this installation method​
Click to expand...
Click to collapse
Have you ever encountered such a situation?

Arthur Mateo said:
About that insufficient space error you had, I think I also had a similar problem, but I'm not sure. It would be nice if you put images or prints of these errors, or give more details.
The insufficient space error that occurred to me actually wasn't in the cell phone as I thought, but in the Linux cache. I manually cleared the linux cache, and the error disappeared.
Click to expand...
Click to collapse
Upon finally trying again, this is the error that I was getting. This occurs whilst the phone has booted to the ubports recovery menu but obviously files are still being pushed.
Do you mean you cleared the linux cache on the PC?

xxdgagag said:
Congratulations !!! But I according the tutorials and it's failed . Can you help me ?
Here's what it shows in terminal, which I think is done
View attachment 5575483
In the device it looks like this:
View attachment 5575485
Yeah, I think it goes back to Ubuntu Recovery Interfaces
Click to expand...
Click to collapse
Hi, I did not succeed, no. Mine gets to the stage of displaying that screen but I'm not sure if yours gets further or not as far. Mine seems to make a big deal about copying this one file and ultimately always fails. Yours seems to say it boots to recovery and then stops, though I find it difficult to read what it says on your screenshot because it is low resolution.
Did you succeed in the end by any chance since you last posted?

is there a way to install Ubuntu touch manually? Like using twrp for example.

For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)

Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards

walidham said:
Hi all, many thanks to use and install UT on titan, i have bricked my device, i can't repair it. Thats why i stopped work on it, i'm trying to find one her in my country, but not success
Best regards
Click to expand...
Click to collapse
Ok. Good Luck! It seems like you were working on it until quite recently though by the repository. Thank you for all the time you have invested so far!
Magzk said:
For anyone having problem installing this is How i did it.
First You Need to do the installation as ROOT.
I use Ubuntu.
Open a terminal and type
sudo su passwd root
Then Go ahead and set a password for root, after that type
su root
And put the password you Just created, Now you proceed with installing ubtouch by using SUDO, like this
sudo ubuntu-device-flash --verbose --server=https://system-image.ubports.com touch --device=titan --channel=16.04/community/walid/devel --bootstrap
Hopefully after this there Will be no problem. (PS: i dont speak english)
Click to expand...
Click to collapse
Thank you. I will try this out soon. I perhaps mistakenly assumed I would get away with just using sudo.

Question Problems with the connectivity on Poco F3 LineageOS + Magisk

I using my Poco F3 since a few month with lineageOS and I'm quite happy. The only problem: Wify and mobile data. Most of the time there is an exclamation mark in the topline on the icons for wify and mobile data.
I tried all the normal stuff:
– reboot the mobile phone (which sometimes really works)
– reboot thr router
– check the settings
– swap the sim cards (because sometimes I was only able to call somebody with one of the sim cards
With the last update of lineageOS it seems that the sim cards work again properly for calls, but not for mobile data.
Despite the exclamation marks surfing und emails works fine. I just can't synchronise my calendar via DAVdroid.
Any hint is appreciated.

are you using the recommended firmware version?
i had some issues with sounds with newer firmware versions

Good question.
I didn't change the firmware. How can I check, which version is runing on my device?

Idk how you'd check the firmware version but you could install the latest firmware for your region regardless.
Or if LineageOS recommends a specific FW version, install that instead.
Xiaomifirmware.com is one place where you can find official MIUI ROM versions and Firmware (/vendor).
You can just install it in Recovery, install itself takes a couple of seconds since Firmware is around 100 MB.

Isn't there an official site to download the firmware?

RunnersHai said:
Isn't there an official site to download the firmware?
Click to expand...
Click to collapse
xiaomifirmwareupdater.com is a reputable source for official Xiaomi FW and ROMs.
Xiaomi do have a website where you can DL ROMs but it's bad.

Perfect, thx a lot. I will try,if it works. Keep fingers crossed ;-D

Sorry, I don't get any further. I only find complete Roms with 3.1 GB and more. But not a vendor with the code POCO F3 Global - V13.0.3.0.SKHMIXM as mentioned on the website of Lineageos.org (https://wiki.lineageos.org/devices/alioth/fw_update). Even the direct link downloads a complete Rom.
And can I install the vendor with my linux computer or should I switch windows and the mi-tool as mentioned on some websites?
Thanks for your help.

Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.

RunnersHai said:
Okay, I'm a little bit further. As far as I understood it. I download the whole Rom but install just a few parts via adb. Following the instructions here: https://wiki.lineageos.org/devices/alioth/fw_update
I should install the payload-dumper-go to unpack the zip-file of the ROM. But I don't know how to start the programm
I downloaded it from github for Linux, but I don't know how to get any further.
Click to expand...
Click to collapse
You're right. I checked out that website and those links are indeed full Recovery MIUI ROMs, not just firmware.
Those instructions show you how to manually flash just the firmware from a ROM.zip
However, you don't need to do that. Here is a link to just the firmware for that exact ROM:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
v13.0.3 seems rather old to me, but if it's their recommendation, then I guess go ahead. After all you simply want these problems to go away.
How to flash:
Simply boot into Recovery and do ADB Sideload
"adb sideload firmware.zip"
If you want to use the Payload Dumper anyway:
In your Linux Machine, open the Payload Dumper folder,
right-click an empty space in the folder, click "Open in Terminal",
type "payload-dumper-go -o . " and drag & drop the MIUI_ROM.zip into the Terminal (this will autofill the path to that ROM),
Hit Enter.
Then, open the created folder where all the extracted partition-images are. Open that folder in Terminal, and do the fastboot commands listed on the LineageOS-website that you linked to me.

Great thanks a lot for your help. New stuff to learn – that's great.
Unfortunately I figured out that the reason for the problems could be a wrong setting in my AFWall+. I will double check that and if it's not the reason, I will follow your instructions. Thanks a lot for your work – awesome.

heres the firmware archive,no need for full rom and fastboot commands
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com