FAILED (remote: Command not allowed) while flashing TWRP - Mate 8 General

Hi,
Today i tried to flash TWRP on my Mate 8 (again) and i became this error message:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.727s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.736s
A few information about my device:
Android 7.0
EMUI 5.0
OEM Unlock disabled and greyed out
bootloader unlocked
Sorry for my bad English!

UselessIdiot said:
Hi,
Today i tried to flash TWRP on my Mate 8 (again) and i became this error message:
>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (25236 KB)...
OKAY [ 0.727s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.736s
A few information about my device:
Android 7.0
EMUI 5.0
OEM Unlock disabled and greyed out
bootloader unlocked
Sorry for my bad English!
Click to expand...
Click to collapse
I think u must unlock your phone bootloader again.
Same error happened to me after updated my phone to b580

Ww222 said:
I think u must unlock your phone bootloader again.
Same error happened to me after updated my phone to b580
Click to expand...
Click to collapse
I tried but I became an error message again:
>fastboot oem relock [Unlockcode]
...
FAILED (remote: root type is risk)
finished. total time: 0.007s
Or:
>fastboot oem unlock [Unlockcode]
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
I have my old unlock code but i dont know if it is the same because i have the test key preblem

UselessIdiot said:
I tried but I became an error message again:
>fastboot oem relock [Unlockcode]
...
FAILED (remote: root type is risk)
finished. total time: 0.007s
Or:
>fastboot oem unlock [Unlockcode]
...
FAILED (remote: Command not allowed)
finished. total time: 0.015s
I have my old unlock code but i dont know if it is the same because i have the test key preblem
Click to expand...
Click to collapse
Is USB debugging on?
If yes reinstall stock rom again
If no turn it on

Ww222 said:
Is USB debugging on?
If yes reinstall stock rom again
If no turn it on
Click to expand...
Click to collapse
USB debugging is on.
But is it possible to install a rom without twrp/custom recovery?
If yes, How?
Thank you for your help! :good:

UselessIdiot said:
USB debugging is on.
But is it possible to install a rom without twrp/custom recovery?
If yes, How?
Thank you for your help! :good:
Click to expand...
Click to collapse
1.Unroot your phone if rooted
2.install stock recovery
3.install stock rom using dload method
(Be sure download correct rom to your Device)

Ww222 said:
1.Unroot your phone if rooted
2.install stock recovery
3.install stock rom using dload method
(Be sure download correct rom to your Device)
Click to expand...
Click to collapse
It worked. THANK YOU VERRY MUCH!

UselessIdiot said:
It worked. THANK YOU VERRY MUCH!
Click to expand...
Click to collapse
Wlcm

fastboot flash recovery recovery.img will not work on EMUI-8 the proper method is:-
fastboot flash recovery_ramdisk (filename).img

Related

flashing recovery issues

I have been trying to flash TWRP and CWM on Nexus 7 which would not bootup (similar to sleep of death but when I erased data using fastboot it works) but now after unlocking bootloader I can't flash recovery.
In therminal I get "invalid status" after I execute the comand ...............................
Any ideas?
I would sincerely appreciate all your help!
To be more specific
This is what I get in terminal
sending 'bootloader' (7066 KB)...
OKAY [ 0.905s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 1.308s
Click to expand...
Click to collapse
Rename the file to: Recovery

[Q] writing 'bootloader'... FAILED (remote: (Unknown error code))

My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >​
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s​
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument​
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory​
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s​
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s​
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.

Can't flash TWRP with unlocked bootloader

Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
roelprincen said:
Hiii,
I've read many threads but didn't find my answer, I have an unlocked bootloader but can't flash TWRP recovery.
Tried many different versions but all tries give me an "remote: image verification error"
Device is fastboot mode:
C:\Temp>fastboot devices -l
4<serial hidden>7 fastboot
Bootloader unlocked with official unlock code:
C:\Temp>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.007s
Flash TWRP (failed) and flash STOCK (success):
C:\TEMP>fastboot flash recovery recovery_twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (28928 KB)...
OKAY [ 0.617s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.634s
C:\TEMP>fastboot flash recovery recovery_stock.img
target reported max download size of 471859200 bytes
sending 'recovery' (32960 KB)...
OKAY [ 0.701s]
writing 'recovery'...
OKAY [ 1.102s]
finished. total time: 1.805s
Any ideas... what can I do/ what should try?
Thx!
Strange is when I :
C:\Temp>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ 0.004s]
finished. total time: 0.005s
it say's it's locked, but when I try to unlock with correct code, it gives a message wrong password, so it's unlocked :|
Click to expand...
Click to collapse
same with me ?
Try to relock and then unlock. I've had this problem too after downgrade to mm by official Huawei rollback package. Then phone and other tools shows than phone is unlocked and it was unable to flash recovery.
if it says wrong password it means you got the wrong password. it will say it's already unlocked if you try unlocking it while it's unlocked
My phone was unlocked with Potato v2.0.1, with working TWRP, rooted etc...
I solved this problem that arose after unsuccesfully install custom Rom, restore backup of stock rom, install update through dload and many many other attempts at improvement of my smartphone :-( No more time again!!!
Probably installing update through Dload will relock bootloader, but in the fastboot mode it says bootloader still unlocked.
Before I did all this, I had an original stock rom.
1: Relock bootloader with PotatoNV v2.0.1 (You need to open case and connect tespoint by wire - look on Youtube, i´ve find it there, also you need "Huawei testpoint drivers")
2: Factory reset
3: Install any update stock rom with Dload (Vol up + Vol down + power)
4: Factory reset
5: Developer options-turn on OEM unlock and USB debbuging
6:Unlock bootloader with PotatoNV v2.0.1 - keep password generated by Potato
7:Multitool 8 for Huawei - in the bootloader state unlock bootloader again - use password generated by Potato
8:Multitool 8 for huawei - install TWRP - it says "Succesfully installed" - TWRP works, root is possible. Yeah!!!
May be this is not right way to solve this, but for me it workś..

[ADB & FASTBOOT] Problem with flashing TWRP FAILED (remote: Command not allowed)

Hi Guys! After brick, my p9l have red "menu" at start and text "Failed verificatnion" or smth like this.
I can't flash TWRP because of FAILED (remote: Command not allowed).
Bootloader & FRP unlocked.
Adb isn't working at bootloader, only fastboot is working.
I want to rollback to 6.0. I have dload with file on my sdcard but i can't flash oeminfo without twrp.
How to fix it?
Code:
E:\tele\SRKToolHuawei-STABLE-V1.3-20160619>FASTBOOT flash recovery EliteTWRP.img
target reported max download size of 471859200 bytes
sending 'recovery' (24452 KB)...
OKAY [ 0.618s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.632s
I want to say sorry for my english :/
Try to flash TWRP with P9 lite toolkit

Please assist! P10 lite (WAS-LXA1) bricked.

Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
korval said:
Hi guys,
I had 7.0/5.1 with TWRP installed and root etc. I tried to flash an Oreo ROM but now the phone just remains on a black screen. Holding down either up or down with power button just does nothing. I do have fastboot access though and able to flash but not boot at all!
fastboot devices
2XJDU17719015729 fastboot
sending 'boot' (16612 KB)...
OKAY [ 0.416s]
writing 'boot'...
OKAY [ 0.124s]
finished. total time: 0.540s
sending 'recovery' (35992 KB)...
OKAY [ 0.892s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.540s
fastboot boot RECOVERY.img
creating boot image...
creating boot image - 36857856 bytes
downloading 'boot.img'...
OKAY [ 0.902s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.902s
Click to expand...
Click to collapse
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
eldorado999 said:
The easiest method to install oreo but be careful after this method you will get bootloader locked. If you want method which will not lock your bootloader try HwOta.
Click to expand...
Click to collapse
Thanks for your reply but the phone is permanently stuck on a totally black screen with fastboot. Pressing power+vol keys do nothing. I can't get to erecovery or the normal white screen/bootloader/fastboot screen. I am still able to send fastboot commands.
:crying:
C:\Windows\system32>fastboot oem get-product-model
...
(bootloader) WAS-LX1A
OKAY [ 0.003s]
C:\Windows\system32>fastboot oem get-build-number
...
(bootloader) :WAS-LX1AC432B198
OKAY [ 0.003s]
finished. total time: 0.003s
C:\Windows\system32>fastboot oem unlock
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.001s
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
korval said:
If anyone has any suggestions please share them, I cant believe how easy it was to brick this phone! I've flashed and rooted at least 5x samsung phones prior to this but never bricked one!
Click to expand...
Click to collapse
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Tiagohsoares said:
I don't know if you installed a custom Rom or not, but install the stock Huawei recovery. Than in a microSD card put the stock ROM. Than press vol up+voldown+lockscreenbutton.
Click to expand...
Click to collapse
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
korval said:
I tried to install Elite ROM v7.7 for P10 Lite via TWRP using the zip file. It installed with some errors but after rebooting the phone does not come on at all. Screen is black. but I do have fastboot access. I've tried using the factory ROM in the dload folder but when I hold in the buttons it just makes the USB connect/disconnect sound in windows as if you plug or unplug a usb device, screen stays black. I'm starting to lose all hope now. I just payed a lot of money for this phone only to brick it...
Click to expand...
Click to collapse
If you can flash and boot recovery try with hwota7 to install to install stock rom...

Categories

Resources