Recovery fail the One - ONE Q&A, Help & Troubleshooting

English :
Good evening, I install the Rom:
12.1-cm-YOG4PAS2QL-bacon-signed-fastboot
in fastboot mode to zero to put my phone
Everything is going well
It is unlocked
When I install the recovery TWRP Touch Recovery 2.8.7.0
the phone does not reboot, I did check the developer and also debugging options, and have clear the update of Cyanogen recovery.
It remains blocked on Cyanogen screen.
Thanks for your help.
J'obtiens un false, avec fastboot oem device-info, pourquoi ?
C:\fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s
French :
Bonsoir, j'ai installer la rom :
cm-12.1-YOG4PAS2QL-bacon-signed-fastboot
en mode fastboot pour remettre mon téléphone à zéro
Tout se passe bien
Il est unlocked
Lorsque j'installe le recovery TWRP Touch Recovery 2.8.7.0
le téléphone ne redémarre plus, j'ai bien cocher les options développeur et aussi de débogage, et ai décocher la mise a jour du recovery Cyanogen.
Il reste bloquer sur l'écran Cyanogen.
Merci de votre aide.
J'obtiens un false, avec fastboot oem device-info, pourquoi ?
C:\fastboot>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.007s

Related

[Completed] Moto g xt1039 doesn't writes anything,

Saludos,
Recientemente compré un MOTO G XT1039 que al principio no entraba al recovery, baje una infinidad de recoverys, ninguno conseguia flashearlo, logré hacerlo con la herramienta Mototools AIOV3, pero no puedo instalar roms, ni recovery, nada, el bootloader esta desbloqueado.
logre bootear el TWRP con el comando
fastboot boot recovery.img
de ahi pruebo instalar los recovery o roms pero no los flashea, cuando enciende enciende como si no hubiera hecho nada. los errores que obtengo flasheando desde fastboot son "hab check failed for boot" "hab check failed for recovery" o "preflash validation failed"
la version de recovery actual el Android System Recovery PLB23.13-17
El telefono antes de morir tenia 5.1
Aca el log de una instalacion de un firmware 4.4.4
C:\4.4.4>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.045s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.357s
EN EL CELULAR: Version downgraded for primary_gpt
(Estoy haciendo un downgrade asique este fallo estaría bien)
C:\4.4.4>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1953 KB)...
OKAY [ 0.124s]
writing 'motoboot'...
Motoboot: Preflash validation for tz
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.406s
EN EL CELULAR: version downgraded for tz
C:\4.4.4>mfastboot flash logo logo.bin
sending 'logo' (1060 KB)...
OKAY [ 0.112s]
writing 'logo'...
OKAY [ 0.086s]
finished. total time: 0.198s
C:\4.4.4>mfastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 0.409s]
writing 'boot'...
OKAY [ 0.647s]
finished. total time: 1.057s
EN EL CELULAR: hab check failed for boot
C:\4.4.4>mfastboot flash recovery recovery.img
sending 'recovery' (10240 KB)...
OKAY [ 0.416s]
writing 'recovery'...
OKAY [ 0.638s]
finished. total time: 1.056s
EN EL CELULAR: hab check failed for recovery
Hasta aca deberia estar una parte
Ahora los comandos, este telefono es europeo asique debe llevar estos
C:\4.4.4>mfastboot flash system system.img_sparsechunk.0
sending 'system' (248267 KB)...
OKAY [ 7.857s]
writing 'system'...
OKAY [ 8.538s]
finished. total time: 16.395s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.1
sending 'system' (248994 KB)...
OKAY [ 7.873s]
writing 'system'...
OKAY [ 7.609s]
finished. total time: 15.481s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.2
sending 'system' (257391 KB)...
OKAY [ 8.132s]
writing 'system'...
OKAY [ 8.055s]
finished. total time: 16.187s
C:\4.4.4>mfastboot flash system system.img_sparsechunk.3
sending 'system' (20588 KB)...
OKAY [ 0.732s]
writing 'system'...
OKAY [ 13.263s]
finished. total time: 13.995s
C:\4.4.4>mfastboot flash modem NON-HLOS.bin
sending 'modem' (59132 KB)...
OKAY [ 1.874s]
writing 'modem'...
OKAY [ 0.985s]
finished. total time: 2.860s
C:\4.4.4>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\4.4.4>
C:\4.4.4>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\4.4.4>mfastboot flash fsg fsg.mbn
sending 'fsg' (710 KB)...
OKAY [ 0.065s]
writing 'fsg'...
OKAY [ 3.169s]
finished. total time: 3.234s
C:\4.4.4>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
C:\4.4.4>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.018s]
finished. total time: 0.018s
pero cuando reinicio solo se queda en la pantalla del bootloader desbloqueado, si pruebo instalando desde el recovery me pone que no hubo fallos pero cuando reinicio no pasa nada.
cuando instalo un recovery no lo instala, los comandos no muestran errores, pero cuando reinicio no cambió el recovery
ya he intentado todo, la unica herramienta que pudo modificarme en algo el telefono fue mototools AIO v3
Hello,
please edit your post with an English translation.
Kind regards
Trafalgar Square
XDA Assist

steps to decrypt firmware and storage on moto E5 play XT1920 - 19 pettyl

first we need to have the correct firmware of the device in case something goes wrong to reinstall again
second step
as you already have the previously installed recovery you must enter the recovery and give it delete to clear cache, delete software and delete internal storage and restart it no matter that it says it has no operating system the device will be in bootlogo or simply restart in the own recovery TWRP at that time that really does not have software the device we put it in bootloader mode.
third step reinstall the correct firmware of the device through ADB with the following commands that appear below
fastboot devices
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
let it restart the software, and once restarted you turn it off again and leave it in bootloader mode you install the twrp right away.
at that precise moment you enter the recovery you configure it and you will notice that already the internal storage is visible and there is no problem of encryption you can restart the software and ready problem solved.
me funciono pero ahora se me queda en el logo de motorola :'''v
Lautii 18 said:
me funciono pero ahora se me queda en el logo de motorola :'''v
Click to expand...
Click to collapse
Bueno amigo tienes que limpiar el sistema como si estuviera restableciendo lo de fabrica a través de recovery si no te funciona reinstalar nuevamente el recovery a veces el recovery da error y no deja arrancar el software
Hello, it does not work for me on a motorcycle e5 play xt1920-18 when I give a deletion system or any other partition it gives me an error and there is nothing you can possibly help me thanks.
Hola, no me funciona en moto e5 play xt1920-18 cuando doy sistema de borrado o cualquier otra partición me da error y no hay nada quiza puedas ayudarme gracias.
telegram... @motoe5dev ...... @Pettyl
juanito1987_9 said:
telegram... @motoe5dev ...... @Pettyl
Click to expand...
Click to collapse
Pode me arrumar ?
is there any solution for this on moto e5 plus. i had a pattern lock and my os crashed and now when i try to inter my storage from recovery it says my data is encrypted and both my internal and sd card isn't showing. now i can't even install new rom. is there any solution?

Moto G8 Plus Root Android 10 Guide|Tutorial

ok so if u have just updated to android 10 u might want to root your g8 plus below i will leave some written instructions and also a video tutorial that u can watch to help you along the way!!
1. Ok so first u will need to unlock your bootloader on motorola's website after u unlock the bootloader then go to https://mirrors.lolinet.com/ and download the same stock android 10 firmware that you have just updated to on your phone download it and save it on your pc preferably the desktop!!
2.u should still have minimal adb & fastboot installed on your pc after unlocking the bootloader if not Download it here https://androidfilehost.com/?fid=746010030569952951
3.Extract the stock android 10 firmare using winrar or any other exctracting program, when extraction finishes highlight all the files & copy them into the minimal adb & fastboot folder
4.Go to Magisk Manager webiste and download the latest magisk manager and install it & do the additional setup then let it reboot
5.Go back to minimal ADB & Fastboot & look for the boot image and copy it to your phones internal storage,Then go back into magisk manager on your phone and select INSTALL >Select Patch A File> Then locate the Boot image on the internal storage>Then make sure patch a file is selected then press LETS GO ,
6.GO to internal storage find the Magisk_Patched file & copy it back into the Minimal ADB & Fastboot folder
7.put the phone into fastboot mode by powering off then holding volume down & power buttons,once in fastboot mode connect usb cable
8. Now with adb fastboot still open find a blank space press shift & right click on mouse to open the black command window & type fastboot flash boot THEN highlight &copy the name of the Magisk_patched & put .img at the end then hit ENTER
9.START the device then go to the playstore download Root Checker and then check that the phone is rooted
Here is a Step By Step Video Tutorial To Help You Through The Rooting Process
madscientistdam said:
ok so if u have just updated to android 10 u might want to root your g8 plus below i will leave some written instructions and also a video tutorial that u can watch to help you along the way!!
1. Ok so first u will need to unlock your bootloader on motorola's website after u unlock the bootloader then go to https://mirrors.lolinet.com/ and download the same stock android 10 firmware that you have just updated to on your phone download it and save it on your pc preferably the desktop!!
2.u should still have minimal adb & fastboot installed on your pc after unlocking the bootloader if not Download it here https://androidfilehost.com/?fid=746010030569952951
3.Extract the stock android 10 firmare using winrar or any other exctracting program, when extraction finishes highlight all the files & copy them into the minimal adb & fastboot folder
4.Go to Magisk Manager webiste and download the latest magisk manager and install it & do the additional setup then let it reboot
5.Go back to minimal ADB & Fastboot & look for the boot image and copy it to your phones internal storage,Then go back into magisk manager on your phone and select INSTALL >Select Patch A File> Then locate the Boot image on the internal storage>Then make sure patch a file is selected then press LETS GO ,
6.GO to internal storage find the Magisk_Patched file & copy it back into the Minimal ADB & Fastboot folder
7.put the phone into fastboot mode by powering off then holding volume down & power buttons,once in fastboot mode connect usb cable
8. Now with adb fastboot still open find a blank space press shift & right click on mouse to open the black command window & type fastboot flash boot THEN highlight &copy the name of the Magisk_patched & put .img at the end then hit ENTER
9.START the device then go to the playstore download Root Checker and then check that the phone is rooted
Here is a Step By Step Video Tutorial To Help You Through The Rooting Process
Click to expand...
Click to collapse
Magisk has updated and it's not flashing the img file. Any way to info Magisk stuff?
Use the boot.img file on the Magisk Canary.
Jukmisael said:
Use the boot.img file on the Magisk Canary.
Click to expand...
Click to collapse
Can give some steps for that ?
X4vier said:
Can give some steps for that ?
Click to expand...
Click to collapse
With the phone running, install the Magisk Manager, Download your model's boot.img, or the entire system "it's good to recover"
It is usually compressed, unzip and copy the boot.img to the cell phone,In Magisk Manager go to install and choose Patch, Choose boot.img (with Internet)
Now in the download folder you have magisk_patched.img, copy to your PC and with your phone UNLOCKED, flash boot.img.
To patch the file, we have some options, I leave the force Encrypt active, but it is more like it.
X4vier said:
Magisk has updated and it's not flashing the img file. Any way to info Magisk stuff?
Click to expand...
Click to collapse
If you believe it is the version of Magisk, use an earlier version, I tested it with Canary and it always worked.
Can use any root RETAIl RETUE RETLA? How can I identify which room download?
X4vier said:
Can use any root RETAIl RETUE RETLA? How can I identify which room download?
Click to expand...
Click to collapse
The cell phone itself gives this information, If there are doubts, run the command "fastboot getvar all 'and look for the system you can usually get an idea by looking at the information.
I got this,
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-doha_retail-7326ad2e6a-201028
(bootloader) product: doha
(bootloader) board: doha
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: LATAM
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZY2276GRBF
(bootloader) cid: 0x0032
(bootloader) channelid: 0x1b
(bootloader) uid: BAF09232
(bootloader) securestate: flashing_locked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805273600
(bootloader) reason: Volume down key pressed
(bootloader) imei: 357207103008538
(bootloader) imei2: 357207103008546
(bootloader) meid:
(bootloader) date: 12-29-2019
(bootloader) sku: XT2019-2
(bootloader) carrier_sku: XT2019-2
(bootloader) battid: SB18C52858
(bootloader) battery-voltage: 4259
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: retla
(bootloader) ro.build.fingerprint[0]: motorola/doha/doha:10/QPI30.28-Q3-
(bootloader) ro.build.fingerprint[1]: 28-26-3/a320d:user/release-keys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_34.30.03.37R DOHA_LATAMDSDS_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ ([email protected]
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Wed Oct 28 14:
(bootloader) kernel.version[3]: 43:37 CDT 2020
(bootloader) git:xbl: MBM-3.0-doha_retail-f16f9625d-201028
(bootloader) git:xbl_config: MBM-3.0-doha_retail-f16f9625d-201028
(bootloader) git:rpm: MBM-3.0-doha_retail-cea405b-201028
(bootloader) git:tz: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:hyp: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:devcfg: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:cmnlib: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:cmnlib64: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:keymaster: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) gitrov: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) git:abl: MBM-3.0-doha_retail-7326ad2e6a-201028
(bootloader) git:qupfw: MBM-3.0-doha_retail-25b246c-201028
(bootloader) git:uefisecapp: MBM-3.0-doha_retail-aa90ac72-201028
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: b
(bootloader) running-bl-slot: _b/_b
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-unbootable:_a: yes
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 6
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C72095
all: listed above
finished. total time: 0.149s
madscientistdam said:
ok so if u have just updated to android 10 u might want to root your g8 plus below i will leave some written instructions and also a video tutorial that u can watch to help you along the way!!
1. Ok, então primeiro você precisará desbloquear seu bootloader no site da motorola depois de desbloquear o bootloader, em seguida, vá para https://mirrors.lolinet.com/ e baixe o mesmo firmware de estoque do Android 10 que você acabou de atualizar em seu telefone baixe e salve no seu pc de preferência no desktop !!
2.u ainda deve ter adb & fastboot mínimo instalado no seu pc após desbloquear o bootloader, se não Baixe-o aqui https://androidfilehost.com/?fid=746010030569952951
3. Extraia o estoque do Android 10 firmare usando winrar ou qualquer outro programa de extração, quando a extração terminar, realce todos os arquivos e copie-os para a pasta adb & fastboot mínima
4. Vá para o webiste do Magisk Manager e baixe o gerenciador magisk mais recente e instale-o e faça a configuração adicional, em seguida, deixe-o reiniciar
5. Volte para o ADB e Fastboot mínimo e procure a imagem de inicialização e copie-a para o armazenamento interno do seu telefone. Em seguida, volte ao gerenciador do magisk no seu telefone e selecione INSTALAR> Selecione um arquivo de patch> Em seguida, localize a imagem de inicialização na armazenamento> Em seguida, certifique-se de patch um arquivo é selecionado e pressione LETS GO,
6. Vá para o armazenamento interno, encontre o arquivo Magisk_Patched e copie-o de volta para a pasta Minimal ADB e Fastboot
7. coloque o telefone no modo fastboot desligando e mantendo o volume para baixo e os botões liga / desliga, uma vez no modo fastboot conecte o cabo usb
8. Agora, com o adb fastboot ainda aberto, encontre um espaço em branco, pressione shift e clique com o botão direito do mouse para abrir a janela de comando preta e digite fastboot flash boot ENTÃO destaque e copie o nome do Magisk_patched e coloque .img no final e pressione ENTER
9.START the device then go to the playstore download Root Checker and then check that the phone is rooted
Here is a Step By Step Video Tutorial To Help You Through The Rooting Process
Click to expand...
Click to collapse
he had his oem unlocked I went to block his oem now he gets stuck in hers bootloader with the oem locked i can't recover the motorola g8 plus
Hi, is this guide still working as of now? Which version of magisk should I use? I ask because i read somewhere that the magisk developer started working on google and removed all the root hiding stuff from it.
Thanks in advance.

Procedura Root

Buongiorno ho effettuato la procedura descritta nel video su un MOTOROLA ONE MACRO XT2016-1 con bootloader sboccato ma eseguendo il comando fastboot flash boot boot.img mi viene visualizzato il seguente messaggio: C:\adb2>fastboot flash boot boot.img target reported max download size of 268435456 bytes sending 'boot' (32768 KB)... OKAY [ 1.302s] writing 'boot'... (bootloader) Invalid partition name boot FAILED (remote failure) finished. total time: 1.314s Qualcuno mi potrebbe aiutare a risolvere tale problema per effettuare il root. Tengo a precisare che non mi è possibile nemmeno installare una recovery TWRP in quanto non esiste per il mio device. Grazie
Amaranto1914 said:
Buongiorno ho effettuato la procedura descritta nel video su un MOTOROLA ONE MACRO XT2016-1 con bootloader sboccato ma eseguendo il comando fastboot flash boot boot.img mi viene visualizzato il seguente messaggio: C:\adb2>fastboot flash boot boot.img target reported max download size of 268435456 bytes sending 'boot' (32768 KB)... OKAY [ 1.302s] writing 'boot'... (bootloader) Invalid partition name boot FAILED (remote failure) finished. total time: 1.314s Qualcuno mi potrebbe aiutare a risolvere tale problema per effettuare il root. Tengo a precisare che non mi è possibile nemmeno installare una recovery TWRP in quanto non esiste per il mio device. Grazie
Click to expand...
Click to collapse
you should not flash the boot img nor the recovery image, you shoud boot fron recovery using fastboot boot "path to trpimg.img "
once in recovery you can flash any twr zip file.

Asus Zenphone 3 ze552KL hard brick

Hello everyone,
I have a big problem with my Asus. I was using Google Chrome, looking for some things on internet, and then my screen just freezed. So I tried to restart my device by pushing start button but only Asus logo (it is white not silver as usual) was showing and the the screen display "Powered by Android" in white and stay on that picture.
So I tried few things, but the recovery mode is not accessible. I can only launche the Fastboot mode(and only with this mode my PC detect the phone).
So I tried the "Kit Root Zenfone 3" available on this site at "http://forum.xda-developers.com/showthread.php?t=2588979".
I followed all the steps, but first the log "0.Install_Driver" can't be executed : windows says "incorrect settings" when I execute it, even in administrator mode.
So i installed manually the driver to see "Asus Android Bootloader Interface" in my device manager. The I launched the second log (all with administrator mode) : "1.Unlock_ze552kl"
And it shows this to me :
Appuyez sur une touche pour continuer...
error: cannot load 'unlock_ze552kl.raw'
rebooting into bootloader...
OKAY [ 0.012s]
finished. total time: 0.012s
...
FAILED (command write failed (Too many links))
finished. total time: 0.022s
###############################################################################
# #
# Device Unlocked #
# #
###############################################################################
< waiting for device >
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
(bootloader) Device is_authorized: false
(bootloader) ssn_num: H3AZCY0586817Z3
(bootloader) isn_num: N0CY1712MB0037886
(bootloader) check_fused: 0
(bootloader) Device resize: false
(bootloader) BOOT_COUNT : 405
(bootloader) SB=Y
(bootloader) Re-partition: false
(bootloader) Device had been rooted: NO
(bootloader) Device has copy fsg to fsgCA: false
(bootloader) Device last copy fsg status: fail
(bootloader) verity_mode: 1
(bootloader) is_ffu: false
(bootloader) verity_counter: 0
(bootloader) total verity_counter: 0
OKAY [ 0.214s]
finished. total time: 0.214s
Appuyez sur une touche pour continuer...
And here someting happens on the screen of my phone : on the right we can see that a thing like a barcode is displayed, not on all the screen but centred in column à right.
Then I ran the "2.FlashRecovery". And I have this message.
###############################################################################
# #
# Please boot your mobile to Bootloader mode, and connect your mobile to PC #
# #
###############################################################################
error: cannot load 'twrp-3.0.2-Z017D.img'
###############################################################################
# #
# Hold the volume down button, and press any key #
# #
###############################################################################
Appuyez sur une touche pour continuer...
rebooting...
finished. total time: 0.014s
Appuyez sur une touche pour continuer...
As I do what it said, my phone just relaunch with the problem I described earlier : only Asus logo (it is white not silver as usual) was showing and the the screen display "Powered by Android" in white and stay on that picture.
And is no more detected by my PC.
So if you have any solution, any things you think I do wrong, please tell me.
I really need help, I tried everything I found but with no success.
Thank you for you help.
Have a nice day.
Take it to autorized service center and let them try to fix it.

Categories

Resources