> Attention!

We strongly recommend to readRules section "Android - firmware"

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



HTC U12plus - Firmware



Rep: (1651)
HTC U12plus - Firmware
PictureHTC U12
Description | Discussion пїЅ | Purchase пїЅ | Accessories пїЅ | Camera talk пїЅ | Modification and decorations пїЅ | Firmware пїЅ

Important information!
To select RUU, be sure to read:Information about phone versions for choosing stock firmware based on MID and CID

Before asking a question in the topic, you need to collect data about the phone using the 'fastboot getvar all' command in download mode and plus provide a photo from the screen of download mode itself and lay out (without IMEI) all this together with the question.
You need to upload data under the spoiler.

The authors of the manuals or anyone else on this forum is not responsible for what you have done, all responsibility lies only with you !!!


Drivers and Utilities
Firmware
Firmware
RUU firmware

U12 + (IMEGINE)

1. SKU 401 . For DUGL ( Dual sim ), Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__001, HTC__002, HTC__034, HTC__J15, HTC__A07

2. SKU 411 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID : HTC__A07

3. SKU 401 . For Uhl ( Single sim ), Product id : htc_imeuhl, MID : 2Q5520000, CID s: HTC__001, HTC__M27, HTC__034

4. SKU 617 . For UHL (Single Sim) , Product id : htc_imeuhl, MID : 2Q5520000, CID : BS_US001

5. SKU 709 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__621, HTC__626

6. SKU 708 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID : HTC__622

7. SKU 400 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__060, HTC__059, HTC__039


Exodus1 (EXODUS)

1. SKU 2401 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID s: HTC__001, HTC__J15, HTC__A07, HTC__034

2. SKU 617 . For UHL (Single Sim) , Product id : htc_exouhl, MID : 2Q5520000, CID : BS_US001

3. SKU 709 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID : HTC__621

4. SKU 708 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID : HTC__622

5. SKU 400 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID s: HTC__060, HTC__059, HTC__039


Ota update

U12 + (IMEGINE)

1. SKU 401 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__001, HTC__002, HTC__034, HTC__J15, HTC__A07

2. SKU 411 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID : HTC__A07

3. SKU 401 . For UHL (Single Sim) , Product id : htc_imeuhl, MID : 2Q5520000, CID s: HTC__001, HTC__M27, HTC__034

4. SKU 617 . For UHL (Single Sim) , Product id : htc_imeuhl, MID : 2Q5520000, CID : BS_US001

5. SKU 709 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__621, HTC__626

6. SKU 708 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID : HTC__622

7. SKU 400 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__060, HTC__059, HTC__039


Exodus1 (EXODUS)

1. SKU 2401 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID s: HTC__001, HTC__J15, HTC__A07, HTC__034

3. SKU 709 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID : HTC__621

4. SKU 617 . For UHL (Single Sim) , Product id : htc_exouhl, MID : 2Q5520000, CID : BS_US001


TWRP backups of stock firmware

U12 + (IMEGINE)

1. SKU 401 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__001, HTC__002, HTC__034, HTC__J15, HTC__A07

4. SKU 617 . For UHL (Single Sim) , Product id : htc_imeuhl, MID : 2Q5520000, CID : BS_US001

5. SKU 709 . For DUGL (Dual Sim) , Product id : htc_imedugl, MID : 2Q5510000, CID s: HTC__621, HTC__626


Exodus1 (EXODUS)

1. SKU 2401 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID s: HTC__001, HTC__J15, HTC__A07, HTC__034

3. SKU 709 . For DUGL (Dual Sim) , Product id : htc_exodugl, MID : 2Q5510000, CID : HTC__621



Custom firmware


Instructions, Useful Information
Instructions

Useful information


Custom Recovery TWRP
On U12 +, Exodus1 no longer has a recovery partition. Stock recovery is sewn into boot.
There are two options for custom recovery:
I) . TemporaryTWRP .img
You can boot into it from the bootloader command:
fastboot boot twrp.img

This is a great opportunity to boot into TWRP without changing boot.img. On this device, an opportunity is opened for experienced users to launch TWRP and have a 100% full drain with a locked bootloader, which allows a lot, for example, such as: forced rollback to the software below, make / restore your data backup , removing phone lock keys, accessing system files, etc.
After rebooting, the temporary TWRP disappears.
Ii) . Permanent (Permanent)TWRP .zip loaded into ramdisk.
There are two main options for installing a permanent TWRP (the bootloader must be unlocked, Unlocked):
1. From the temporary TWRP.img, flash TWRP.zip
2. Install TWRP.zip from Magisk Manager (click + in the modules section).
Due HTC introduced an additional check in touchscreen driver, when loaded into TWRP display will be inactive. For this purpose, after flash TWRP constant need to immediately flash patch for core stock hex patcher (boot patches both slots), it can be sewn from both TWRP, and from Magisk Manager. Custom kernel have been going to patch this problem, flash the hex patcher in the presence of a custom kernel is not required. At the core of katabatic with hex patcher will not work in the command boot recovery "adb reboot recovery", also loading in the recovery of Magisk Manager and to load the recovery of the most TWRP. Booting into bootloader recovery of buttons.
After installing a permanent TWRP, you need to reinstall Magisk, if you need a root, then flash magisk.zip. If the root is not needed, then go to Advanced and select Fix Recovery Bootloop in order to avoid a bootoot when entering the system.
TWRP needs to be selected and installed according to its security patch.

Unofficial TWRP from Team Venom:

Informal TWRP from @CaptainThrowback:


Route access with Magisk
Route access to U12 + can be obtained from Magisk. You can install it in two main options:
Initial data: Unlocked Unlocked bootloader configured by PC for adb utilities.
1. Installation option with TWRP.
1a. Flash magisk.zip from TWRP. The Magisk Manager application should be installed during firmware. If not, install MagiskManager.apk. Done, the root is installed.
1b. Another installation option by firmware from TWRP patched boot.img
- Install the application MagiskManager.apk
- Copy to the phone the original untouched boot_signed.img corresponding to the current software.
- In the Magisk Manager application, double-click Install ->Select and patch the file.
- Select the untouched boot_signed.img stored on the phone and wait for the patch to finish, we get the patched patched_boot.img
- We are rebooted in TWRP. Click reboot to see the active slot. We switch to inactive and back to the active slot.
- In the menu, select Install - Install img - choose to install the received patched patched_boot.img, wait for the end of the process.
- We are rebooted into the system. Done, the root is installed.

2. Installation option without TWRP.
- Install the application MagiskManager.apk
- Copy to the phone the original untouched boot_signed.img corresponding to the current software.
- In the Magisk Manager application, double-click Install ->Select and patch the file.
- Select the untouched boot_signed.img stored on the phone and wait for the patch to finish, we get the patched patched_boot.img
- In any way, copy the patched boot file on the PC to the folder where the adb utilities are. Or:
- Connect to the PC and transfer the file to the PC in the adb folder, execute the command:
adb pull /sdcard/MagiskManager/patched_boot.img

- We load in download mode:
adb reboot download

- Check the current slot:
fastboot getvar current-slot

- We use the received active slot in the teams as a prefix. The following commands, depending on the active slot, flash the patched boot.img into the active slot:
if slot A
fastboot flash boot_a patched_boot.img

if slot B
fastboot flash boot_b patched_boot.img

- We are rebooted into the system:
fastboot reboot

Done, the root is installed.
After installing the root, you need to restore the phone to unlock by face, Photo Password (Face Unlock),according to this instruction.


Custom Kernels
mini FAQ
Question - "B"
The answer is "O"

AT . What is A / B Parition on our phone?
O . Additionally, the second discrete region, for example, B, allocated on the phone’s internal memory and designed for seamless and guaranteed receipt of updates to it, when the first, in Example A, with all the data saved is active. In details on xda , or for example here

AT . I do not find the recovery section on the phone, should it be?
ABOUT . There is no longer a recovery partition on this device. Stock recovery is sewn into boot. Therefore, custom recovery can be downloaded temporarily with the "fastboot boot twrp.img" command or flashed the permanent (permanent) TWRP.zip to ramdisk from the temporary TWRP.img or installed from Magisk Manager.

AT . What is RUU and what is OTA?
ABOUT . RUU is a complete stock stock ROM firmware signed by HTC keys: ROMUpgradeUtility . Set completely, with all the phone except extSD. RUU is sewn in the current slot.
OTA, the abbreviation FOTA -FirmwareO ver T he A ir, Signed by the next update HTC stock ROM specific keys. It flies through the air on phones Sidamo. Installation does not remove user. Sewn into the other slot and after successful prshivki current slot is changed from a to b or vice versa.

AT . Do I need to close the bootloader before RUU firmware?
ABOUT . No, this is not required. For a long time on devices after HTC One M7 RUU is sewn with any bootloader status, Locked, Unlocked, Relocked.

AT . I decided to flash RUU from an extSD card, but it says in download mode that it was not found. What is the reason ?
ABOUT . First: Make sure that the external card is formatted in FAT32 or exFAT format. Second: U12 + does not see large-sized extSDs of all manufacturers. Try to swipe a card of another brand or use a 32GB card, or even less. Or use OTG (the flash drive must be formatted in exFAT format). Or use one of the RUU firmware options from a PC.

AT . Can I convert my one-character U12 + into a two-character?
ABOUT . No you can not. Any forced attempts to remake Single Sim into Dual Sim with S-ON or S-OFF and vice versa Will lead to the scorching of the phone and a trip to the SC! Single Sim can only be converted to Single Sim, and Dual Sim only to Dual Sim method with S-ON replacing CID within one MID or c S-OFF with replacing CID and MID.

AT . Another OTA has arrived, but I have the root installed. What is needed to get OTA and do I need to close the bootloader?
ABOUT . Conditions for obtaining OTA or installing it manually: a completely untouched stock system, in particular the system partition and Boot. The bootloader state (Locked, Unlocked, Relocked) does not affect the receipt of OTA. From the root, you can copy the received OTA.zip file from the folder /data/data/com.htc.updater/files on SD and share in the subject. To return to the untouched stock state, you need to flash it according to your CID, MID and software number in the Untouched Backup header (user data is not deleted). Or flash your RUU with the removal of everything on the phone, except extSD.

AT . I do not find firmware in OTA as in previous phones, only payload.bin How to get Boot.img stock?
ABOUT . U12 + is already different. There is no classic firmware in OTA, and you won’t get signed partitions from there. The header is: "How to get pristine stock Boot and System.Image, create Untouched Backup." From there, you can take it if you need to rename it to Boot.img

AT . What is an Untouched Backip Untouched System?
ABOUT . Archive created from TWRP net drain pristine System.Image and boot partitions on this phone (or collected arms and adapted to the format of the backup TWRP these sections obtained from decoding RUU or ADB commands before installing Root). Designed to recover from TWRP (or renaming of files for each separate firmware via ADB) for the removal of Ruth and return to the state of the stock for the next OTA. It is packed in zip-file only for the convenience of downloading. Restoring does not delete the user data.

AT . I want to unlock the bootloader to get the root, but the procedure goes with the factory reset. Can I backup all of my own before this?
ABOUT . Yes, on U12 + this is possible. With a temporary TWRP and at full drain with a locked bootloader, you can make data backup for subsequent recovery. Instructions in the header, full stock example .

AT . I restored my data backup and can’t log into the system with a password, it doesn’t correspond to mine.
ABOUT . The data backup was created incorrectly, you must always delete all fingers, pins, passwords, etc. before creating it. Can flash key removal script . Or manually from TWRP to delete in the file manager along the path / data / system all files locksettings. * (With various extensions). Unlike previous HTC, on U12 + the procedure is available at full 100% drain with a locked bootloader due to temporary TWRP.

AT . After restoring your data backup, some data from the internal memory, levels of some games, photo messenger, etc. were lost. How to do it right?
ABOUT . Creating data backup alone is not enough. it does not save multi-media on SD and user folders and program folders with downloads. For full recovery, do according to the instructions in the header: How to properly save / restore all your user data.

AT . Is it possible, with Ruth, get another OTA without restoration TWRP Untouched Backup and without loss of data on your phone?
ABOUT . Yes, U12 + possible. You can not return the current system in pristine condition for PTA. Suffice it to switch to another slot for OTAs. Instrkutsiya in the header.



There is no curator in the subject. For questions about filling caps, please contactmoderatorssection through a buttonPictureunder the messages to which you want to add links.

Post has been editedziand - 26.06.20, 22:00
Reason for editing: OTA 2.55.401_R



Rep: (1651)
* ovstanislav I agree .. itself for a long time looking at it with a new pleasure every time. I never thought that at first it seemed everything was so difficult, and in fact became lighter and such concessions from HTC ... so many possibilities and full drain, which wanted to buy this phone [/ S]
Come on, pictures, stop torturing people .. and patskovyvat out with illustrated instructions, and even misunderstood. His fingers on the can tomorrow will edit.

Post has been editedziand - 20.09.19, 23:17



Rep: (954)
ziand @ 20.09.19, 23:13*
that wanted to buy this phone

Do not rush: yes:
That's fresh news
Attached Image


Posted on 20/09/2019, 23:24:

ziand @ 20.09.19, 23:13*
come on now

It is not izzhazhdnosti, lack of time, plus the need to further their experiment a bit: yes:



Rep: (954)
dianamavrik @ 20.09.19, 23:40*
Frenchman appointed

Yes already read :)



Rep: (146)
ovstanislav @ 21.09.19, 05:23*
Monday late afternoon, everyone,

... Spoiled weekend. : Rofl:



Rep: (954)
Restore the system integrity for further updates on the PTA while retaining all of their data


This method is suitable for any of the modified system, in addition to the one at which a permanent rekaveri was installed. The only condition - for your CID must be of OTA software on where you are now. For example, you are now number 1.68 software, then you need to OTA 1.68 - 1.53
For the case with sewn DC rekaveri fit only vostanovlenie using TWRP_Backup_Untouched_System_Image
If you are planning to use this method, you must first flash the RUU, unnecessarily even after the restoration of TWRP_Backup_Untouched_System_Image stock rekaveri you remain only in one slot, and for this procedure should have stock rekaveri in both slots
: yes2:

Before any manipulation make sure that the phone is charged for at least 50% and preferably 100%

Manual for OTA
If all the necessary conditions are present it is possible to start - went to: yes2:

To save the data you need to upgrade to versionSoftware 1.68 Before you save the backup data If you use votsapom, to make a backup copy of the chat (if you need them) and make cleanup that when recovering of the backup you do not need to confirm the telephone number.
If you are using Magisk make sure that all modules are working and do not break the functionality of the device (in my example YouTube Vanced unit broke partially functional camera recording, but learned of it only later).
Activate the Developer menu. Turn OEM - unlocking and debugging via USB

So we do updated backup.
We usesd before 32 gb
Download and throw on your desired sd OTA
Download and put in a folderadb Attached filerecovery.img (30.89 MB)
On the other I did not check. I advise you to use just that. This is a temporary, extreme official: yes2:
1. Download the phone inBootloader
guaranteed to enter the first time doing so. Turn off the phone. I connect to the power supply or to a computer. When the screen displays the battery to charge percentage, power clamp. Once the charge indicator goes off in the upper right corner, hold the key vol- and without hesitation I am loaded in Bootloader


2. Enter the command (if a folderadb and Fastboot The utility is called as that of another, adb place write the name of your folder)

CD C: \ adb

fastboot boot recovery.img


3. The first time you click to select the language and then cancellation
Attached Image

4. Go to section<<Backups>>
Attached Image

5. Put a check mark only against data
Attached Image

6. In the drive selection choose sd.In order to be able to use this backup to 9 android need to keep it on the sd to 32 gb
Attached Image

7. Make a backup copy.

8. Then go to the section<<Reboot>>
Attached Image

9. Choose<<Loader>>
Attached Image

10. After downloading go todownload mode
Know your current slot on line(Bootloader) current-slot: a and RUU number in this slot (Bootloader) version-main: 1.53.709.1
fastboot getvar all

We obtain a certain result
C: \ adb>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_imedugl
(bootloader) version: 1.0
(Bootloader) max-download-size: 1.092 billion
(Bootloader) serialno: FA8671F01362
(bootloader) slot-count: 2
(bootloader) current-slot: a
(Bootloader) imei: 000000000000000
(Bootloader) version-main: 1.53.709.1
(bootloader) boot-mode: download
(Bootloader) version-baseband: sdm845-000201b-1807311356
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2Q5510000
(Bootloader) cid: HTC__621
all:
finished. total time: 0.078s


11. Depending on the team give him, if you currentlya , The change in the b and vice versa if the b then on a
For this KnopVol + or Vol- go to Bootloader We reaffirm the power button.
Attached Image

Then give the command
fastboot --set-active = a

or
fastboot --set-active = b

12. Then lower the ON
To do this again sews temporary rekaveri
CD C: \ adb
fastboot boot recovery.img

We give the command. I have 10 windsurfing they do not always take place. To have successfully completed the team had to reboot com: yes2:
adb shell "dd if = / dev / zero of = / dev / block / bootdevice / by-name / misc bs = 1 seek = 2208 count = 16"

It should look like this
16 + 0 records in
16 + 0 records out
16 bytes (16B) copied, 0.007466 seconds, 2.1KB / s

13. Repeat steps 8 and 9
14. After downloading go toRecovery
15. When the red triangle pushVol +
Next keysVol + or Vol- choose an item <<Apply ypdate from SD card>> Hit the power
Attached Image

16. Then select the OTA file and press the power
Attached Image

17. If you have correctly downloaded your file OTA you begin the process and run the white line. It will take no more than 10 minutes.
Attached Image
Attached Image
Attached Image

On completion of the process you will see the initial screen
Attached Image

GetPie c your data.

17a. If you want to install Magisk then repeat step 2
Downloading stableMagisk Download the installation zip rename it magisk put in a folder adb and give the following command
adb kill-server
adb push magisk.zip /magisk.zip

Then go to<<Installation>>
Attached Image

Swipe from the bottom, we find there a filemagisk and install it.
Attached Image


Who does not like the new black background manager put this modAttached fileapp-release-beta06.apk(3.74 MB)

For this mod thankvsmhell

Bright background of this mod
Attached Image
Attached Image
Attached Image

Dark background fashion
Attached Image
Attached Image
Attached Image

If in the future that goes wrong you can always safely flash the RUU and restore your backup data to 9 in the following manner
18. Go toBootloader
19. Repeat steps2
20. rekaveri go into masonry<<Cleaning>>and select the format of data at the bottom right, and confirm the action teamyes
Attached Image

21. Go back to the main screen rekaveri and go to the tab<<Restoration>>and restore previously saved backups and boot the system. Georgia will be long and boot you will see the screen even primary boot. Do not worry, all of your data back: yes2:
Attached Image

If anyone is to begin with RUU firmware put on the same sd and all the OTA, just rename them, what would become when sewing hands do not confuse them. And before you sew the RUU, do not forget to backup data: yes2:


For this method, do not forget to thank ourguru

Post has been editedovstanislav - 03.10.19, 20:36
Reason for editing: Added to cap.



Rep: (1651)
dianamavrik @ 21.09.19, 13:50*
or can not do

U11 captain too silent ... he wrote that he could not yet. Probably need the source code from HTC.
We have the SW.* mikalovtch Also silent.
That has to dodge other methods ...



Rep: (1651)
dianamavrik @ 21.09.19, 14:14*
we can not help !!

Not
And why is it you want? Here are straining to other possibilities ...

Post has been editedziand - 21.09.19, 14:15



Rep: (954)
dianamavrik @ 21.09.19, 14:17*
understandable chef will then wait in silence

ovstanislav @ 21.09.19, 11:03*
In order to be able to use this backup to 9 android need to keep it on the sd to 32 gb
пїЅ#

Patience is one, only patience :)

Post has been editedovstanislav - 21.09.19, 14:31



Rep: (954)
* dianamavrik You probably do not understand - data can and 9 vostanovt: yes:



Rep: (954)
* dianamavrik , Write, and you already own reshesh;)



Rep: (342)
ovstanislav @ 21.09.19, 12:55*
I write, and you already own reshesh

* ovstanislav,
yes my friend, everyone decides you're right !! I repeat Khimich many smart: D
backup date and permanent TWRP me as air is needed and there is one himself rezhisyor
p.s Respect to you with the boss for the work: yes2:



Rep: (954)
Here it is already
Attached Image

https: //play.google.co...velopments.volumepanel

Post has been editedovstanislav - 21.09.19, 18:39



Rep: (1651)
instructions to edit "Pullback on the other slot. How to get the update OTA Root, preserving user data."In addition to the instructions" in pictures "by* ovstanislav Both add to his cap.
Pleasant to use ..: thank_you:



Rep: (954)
Fixed a typo in the manual: yes:

Posted 09/22/2019, 2:01:

ovstanislav @ 21.09.19, 11:03*
The only condition - for your CID must be of OTA software on where you are now. For example, you are now number 1.68 software, then you need to OTA 1.68 - 1.53


Post has been editedovstanislav - 22.09.19, 02:01



Rep: (342)
utility for download OTA updates from 8/21/19
tryAttached fileHTC_OTA_Downloader.exe(32.5 KB)

https://github.com/sab...TA_Downloader/releases

Post has been editeddianamavrik - 22.09.19, 02:22



Rep: (954)
Backup_Untouched_System_Image for HTC__621
TWRP_Backup_Untouched_System_Image _ + _ Boot_1.68.709.7_IMAGINE_DUGL



Rep: (954)
added item17a installation Magisk Manager



Rep: (954)
TWRP_Backup_Untouched for HTC__621 Exodus
TWRP_Backup_Untouched_System_Image _ + _ Boot_1.74.709.2_EXODUS_DUGL



Rep: (146)
Tonight drove samogonchik already finish
Attached Image

for one has decided to reset the phone to the CID 034 Exodus system with updates to the current feng shui (the opportunity to restore the OTA update), ie starting with the installation2Q55IMG_EXODUS_DUGL_O80_SENSE10GP_HTC_Europe_1.57.2401.6 to OTA 1.68.2401.4 then restore Data, and then upgrade to 1.74.2401.2_R3
Thank Komrad* ovstanislav and * ziand for writing the various manuals and a separate + * ziand for cap threads.
For the reasons mentioned in the first line, I forgot to restore the Data, but on a net okontsovkeTWRP_Backup_Untouched_System_Image _ + _ Boot_1.74.2401.2_R3_EXODUS_DUGL.zip (My internet will fill it to the Yandex disc recording will be clickable for download).
* ziand perezalil archive on androidfilehost.com
Attached Image

And let's hope for TWRP early exit for security from July 1, 2019.
Well, the most funny is that restoring the DATA and receiving firmware version 1.74.2401.2_R3 I zhmaknul to check updates in the hope of getting the top corner, but got the bug fix
Attached Image

Interestingly, he came out of the latest update, or before?

Post has been editedGoryna - 27.09.19, 17:31
Reason for editing: the download link



Rep: (954)
Goryna @ 25.09.19, 22:10*
I forgot to restore Data

Vocstanovi on a small SD of 1.74 for the last time rekaveri

Posted on 09/25/2019, 22:35:

Goryna @ 25.09.19, 22:10*
Interestingly, he came out of the last update

Previously, a week ago


Full version    

Help     rules

Time is now: 25/09/20, 12:39