I'm going to give a solution for this problem (Note: I don't know if there is another solution, please if you know another fix post it here). I'm doing this post because i had this problem and there wasn't any guide on how to fix it, but wil too much patience and experimenting with my AGS2-W09 i could finally fix it . I'm going to post this on English and Spanish. I'm not a developer, I just want to share this with all that may have this problem, hope this work for you . / Voy a dar una solución para este problema (Nota: no sé si hay otra solución, por favor, si conoce otra solución, publíquela aquí). Estoy haciendo esta publicación porque tuve este problema y no había ninguna guía sobre cómo solucionarlo, pero con demasiada paciencia y experimentando con mi AGS2-W09, finalmente pude solucionarlo. Voy a publicar esto en inglés y español. No soy un desarrollador, solo quiero compartir esto con todos los que puedan tener este problema, espero que esto os funcione también
* First of all, we have to download some things:
- PotatoNV: https://github.com/mashed-potatoes/PotatoNV
- Hisuite Proxy v3.3.0: https://github.com/ProfessorJTJ/HISuite-Proxy/releases
- Huawei Update Extractor (v0.9.9.5): You can download it on this post on XDA
- Huawei test point drivers: https://androidfilehost.com/?fid=14943124697586361242
- Firmware files: Get them on Huawei Firm Finder
- Minimal ADB and Fastboot Tool (V1.4.3): https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
- 7-zip: https://7-zip.org/
* Process:
1.- Ok, first we have to download, extract and execute Hisuite Proxy, because you'll need it to be able to download the firmware (It's important to keep it open)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.- Now, we have to download the firmware for our exact model. I will be using the firmware for the AGS2-W09 model but it work for AGS2-L09 too. We're going to get these files from the Huawei Firm Finder site. HERE, there is a list with all region codes
We have to type our exact model on "Phone Model" ( As I said, i'll be using the AGS2-W09 ). On region..., well our region XD, I'll be using the C432 region code.
Now, click on the three dots on the last firmware avaliable ( I'll be using AGS2-W09 8.0.0.328(OCEC432) ). Click on "Check Rom Status" and it should say "Approved for Installation", if it doen't say that, try another firmware.
If it said Approved, we can continue by clicking on "Download Rom" an downloading all files. It should say something like this:
3.- Extracting Process:
Now, I hardly reccomend to use 7-zip, because WinRAR sometimes cause problems at this step.
Extract update.zip on the folder with the same name and extract update_full_XXX-XXX_xx_xx.zip on a folder with same name. ( For example my update_full file is update_full_AGS2-W09_hw_eu)
Now, go into the update folder, right click on UPDATE.APP and extract the file: 7.oeminfo.img. Flash it onto the tablet using fastboot flash oeminfo (drag here that oeminfo.img file)
4.- Huawei Update Extractor:
Now open Huawei Update Extractor, go to settings and uncheck Verify header checksum and verify file checksum. It should look like this:
Now go back to Extract and on update file, select the UPDATE.APP from the update folder:
Right click on any of them and select "Extract All", then create a folder where you want and extract these files there. After extracting them, go back to Extract and select the UPDATE.APP on the update_full_XXX-XXX_xx_xx folder (In my case it's update_full_AGS2-W09_hw_eu) and choose the UPDATE.APP, then extract them the same way as you did with the other UPDATE.APP, but you have to extract this UPDATE.APP on the same folder you've extracted the other update.app.
5.- FASTBOOT
Now, we are ready to flash all IMG files we've extracted on the tablet. We have to do this one by one in order, I know there are a lot of files but I did that and worked for me. NOTE: There some files that it'll say that it couldn't be flashed but it's not a problem, just continue on flashing. FOR EXAMPLE: fastboot flash cache (drag and drop cache.img here) or fastboot flash recovery_ramdisk (drag and drop recovery_ramdis here)
6.- FINISHING PROCESS
When you finish flashing all files just do fastboot reboot and it should turn on. At this point I recommend you installing a custom rom like LineageOS, LeaOS or crdroid. List of compatible roms for this tablet
I hope it works for you as well, like I said earlier I'm not a developer, I'm just a person who likes technology and had this problem. I just share this because it helped me and because I didn't see any post here explaining something. As I said if you now another fix feel free to comment. / Espero que te funcione también a ti, como dije anteriormente no soy un desarrollador, soy solo una personal que le gusta la tecnología y tuve este problema. Comparto esto porque me ayudó y porque no vi ningún post explicando porqué pasa o como arreglarlo. Como dije si sabes de otra solución, por favor coméntalo.
I'll add the Spanish steps soon. / Añadiré los pasos en Español pronto.
(Reserved)
(Reserved)
Is there an order that these need to be flashed in? I have 33 files (ignoring the header files) and I don't know all of the partitions that the files need to be flashed to. This is the list I have so far, do I need other files and do I have the correct partitions?
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash cust CUST.img
fastboot flash dts DTS.img
fastboot flash erecovery_kernel ERECOVERY_KERNE.img
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
fastboot flash erecovery_vbmet ERECOVERY_VBMET.img
fastboot flash erecovery_vendor ERECOVERY_VENDO.img
fastboot flash fastboot FASTBOOT.img
fastboot flash fw_hifi FW_HIFI.img
fastboot flash fw_lpm3 FW_LPM3.img
fastboot flash ptable HISIUFS_GPT.img
fastboot flash kernel KERNEL.img
fastboot flash odm ODM.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash sha256rsa SHA256RSA.img
fastboot flash system SYSTEM.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash version VERSION.img
fastboot flash verlist VERLIST.img
fastboot flash product PRODUCT.img
fastboot flash xloader XLOADER.img
You have to flash them on the same order they have extracted. Example: first cache, second CRC, etc. And the partition hace the same name as the IMG files. Example: fastboot flash xloader xloader
Thx bro very nice tuto . All works for me
woofer50 said:
Thx bro very nice tuto . All works for me
Click to expand...
Click to collapse
Glad it helps
The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?
Kaparroz said:
The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?
Click to expand...
Click to collapse
You have to use the minimal adb and fastboot tool to flash all the .img files.
Thank you very much, I'll try it.
I have other Huawei devices with locked Bootloader, I managed to update from download mode without any problem, with the first Firewall downloaded. But this AGS-L09 is burning me to excess and I have never achieved anything until now. There may be some version of Firewall with Android 7.0 that can be installed from download mode from MicroSd. I have two AGS-L09 one with Android 7.0 and one with Android 8.0 which includes a lot of unnecessary problems.
Related
Hello,
First sorry for my English is so bad because I am Brazilian and I do not write well.
I have a Xperia SP and he had a ROM, I was changing the ROM and she was not installing for reasons that I'm trying to install a different version of my possible to XSP. Thus I uninstalled the old version and unwittingly I turned off my phone and now it is stuck in the logo of Sony.
Searching here and reading some many forums found some solutions put any work on my mobile.
Steps to follow:
1: I have installed FlashTool and tried to download the file * .ftf the original Xperia SP, however not sure gave the program is returning error in system.sin file and does not run the flash completely.
ERROR:
17/029/2015 23:29:58 - INFO - Flashing data
17/030/2015 23:30:00 - INFO - Closing TA partition
17/030/2015 23:30:00 - INFO - Opening TA partition 2
17/030/2015 23:30:00 - INFO - Processing system.sin
17/030/2015 23:30:00 - INFO - Checking header
17/030/2015 23:30:01 - ERROR - Processing of system.sin finished with errors.
17/030/2015 23:30:01 - INFO - Ending flash session
17/030/2015 23:30:01 - ERROR -
17/030/2015 23:30:01 - ERROR - Error flashing. Aborted
17/030/2015 23:30:01 - INFO - Flashing finished.
17/030/2015 23:30:01 - INFO - Please unplug and start your phone
17/030/2015 23:30:01 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
2: researching a little more found something to extract the file * .tft zip in and try to flash but with FASTBOT only file system.sin however this step earlier returned mistake and now it does not load the file so any. If I try to give fastbot in kernel.sin it performs regular put in system.sin not run.
However after I run fastbot the kernel.sin the phone it tries to connect however he stands on the logo of Sony yet, but now it off and try to connect again, as if he had not found the systen.sin (which imagines that is the operational system)
3: I tried to correct the Sony PC Companion put it reports that there is a system installed on the phone and it is not possible to recover.
Another problem not appear that the phone is charging, it apparently is entering mod flash in and out even when connected to power .
Here is my problem, my cell phone does not come out of the Sony screen and I can not access the CWM in any way to try to install something for him.
I wonder if there is a solution to this problem.
Solved - resolvido
Hello everyone,
after a long break your head finally managed to solve the problem ( thank God !!!)
I discovered the fastboot and researched more about it and after many attempts almost breaking all here , figured out how to solve the problem.
First I realized I was only installing Kernels via fastboot so I basically looked for a way ta install something via Fastboo was then I found this turorial : http_://theunlockr.com/2014/03/04/install-custom-recovery-sony-xperia-sp-12-1-0-266/)
leading to an XDA link to download a file that reinstalava .elf CWM on your phone.
With so I reinstalled the CWM and insert the ROM again.
Well what was the mistake that I hope no one else comet.
PLEASE DO NOT TURN YOUR CELL AFTER ERASE A ROM BECAUSE THE PHONE WILL NOT FIND OPERATING SYSTEM AND NEITHER WILL ON.
If you make the same mistake you download this file and use the fastboot .
Thank you all
Obrigado pela ajuda pessoal.
olá a todos,
depois de muito quebrar a cabeça finalmente consegui resolver o problema (graças a Deus!!!)
Eu descobri o FastBoot e pesquisei mais sobre ele e apos muitas tentativas quase quebrando tudo aqui, descobri como resolver o problema.
Primeiro percebi que somente estava instalando Kernels via FastBoot então eu basicamente procurei uma forma ta instalar algo via Fastboo foi então que encontrei este turorial: http_://theunlockr.com/2014/03/04/install-custom-recovery-sony-xperia-sp-12-1-0-266
que levava a um link do XDA para download de um arquivo .elf que reinstalava o CWM no celular.
Com isso eu reinstalei o CWM e inseri a ROM novamente.
Bom qual foi o erro que espero que ninguem mais cometa.
POR FAVOR NÃO DESLIGUE SEU CELULAR APÓS APAGAR UMA ROM POIS O CELULAR NÃO VAI ENCONTRAR SISTEMA OPERACIONAL E NÃO VAI NEM LIGAR.
caso você cometa o mesmo erro que eu baixe este arquivo e use o fastboot.
Obrigado a todos
Ou com flash tools você podia fazer flash de um kernel e ligar o celular sem formatar '-'
Hello, to start my English is very bad so I'll try to explain what's going on with my device.
I bought the XT1068 defective, apparently in the photos would be simple the process, I would install the ROM stock and it would remove the message bootloader and ready. I've tried absolutely everything
It appears the error "Invalid boot image header!"
If I try for a ROM on it it gives some errors, for example "failed to validate ftm image that means its not fih mode load and validate boot image" other "version is downgraded primary_gtp" (this when I tried for the ROM 4.4.4 ).
When I try to install the ROM on mfastboot so it appears these errors "C: \ Users \ PEDRO \ Desktop \ adb> mfastboot flash partition gpt.bin
Reported target max download size of 536870912 bytes
sending 'partition' (32 KB) ...
OKAY [0.050s]
writing 'partition' ...
(Bootloader) Preflash validation failed.
What do I do ?? please help me
---------text in portuguese----------
Olá, pra começar meu ingles é péssimo então vou tentar explicar o que está acontecendo com meu aparelho.
Eu comprei o XT1068 com defeito, aparentemente nas fotos seria simples o processo, eu instalaria a ROM stock nele e tiraria a mensagem de bootloader e pronto. Já tentei absolutamente de tudo
Ele aparece o erro "Invalid boot image header !"
Se eu tento por uma ROM nele ele dá alguns erros, por exemplo "failed to validate ftm image that means its not fih mode load and validate boot image" outro "version downgraded for primary_gtp" ( isso quando eu tentei por a ROM 4.4.4 ).
Quando vou tentar instalar a ROM no modo mfastboot ele aparece esses erros "C:\Users\PEDRO\Desktop\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed.
O que eu faço ?? por favor me ajudem
Can someone help me with full image backup of partitions eMMC?
I can try unbrick my rp2 with full backup mmcblk0 on sd card due my phone don't enter in fastboot anymore, only i see Qualcomm HS-USB QDLoader 9008 when connecting usb
I also tried buying unbrick files from this site
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
but they are scammers!! they only sent me an empty folder on google drive
------Update-------
(Razer Phone 2 don't have mmcblk0)
Now i have other Razer Phone 2, i have full backup now of partitions sda, sdb, sdc, sde, sdf...
but i have new problem, how i merge theses partitions "cutted" to my flashdrive?
theses partitions have same header looking in hex viewer comparing with gpt_both files
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also i used EDL Generator to create xml files if someone have prog_firehore
looking systeminfo_a or _b in txt, you see name of firehose used i think
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
oh jeez
does the phone boot at all? like can you even get it into fastboot? or is it just stuck on the splash image? did you unlock the boot loader?
Jordan5900 said:
does the phone boot at all? like can you even get it into fastboot? or is it just stuck on the splash image? did you unlock the boot loader?
Click to expand...
Click to collapse
bootloader is unlocked but don't boot more, only show Qualcomm HS-USB QDLoader 9008 when connect usb on PC
FellpeSoares said:
bootloader is unlocked but don't boot more, only show Qualcomm HS-USB QDLoader 9008 when connect usb on PC
Click to expand...
Click to collapse
Okay yeah I've been here before,
Follow this post
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/amp/
Before you try doing everything try just getting the drivers and using CMD to boot into bootloader or try system, once it's in bootloader, if all your files are gone, get ur factory ROM and reflash EVERYTHING MANUALLY. Like to into the flash all.bat and do every flash command it shows in that order - I had the trouble that the phone doesn't keep android-info.txt on it so reflashing everything manually will bypass using the flash all.bat and it failing.
Jordan5900 said:
Okay yeah I've been here before,
Follow this post
https://forum.xda-developers.com/android/development/guide-fixing-hard-bricks-t3403868/amp/
Before you try doing everything try just getting the drivers and using CMD to boot into bootloader or try system, once it's in bootloader, if all your files are gone, get ur factory ROM and reflash EVERYTHING MANUALLY. Like to into the flash all.bat and do every flash command it shows in that order - I had the trouble that the phone doesn't keep android-info.txt on it so reflashing everything manually will bypass using the flash all.bat and it failing.
Click to expand...
Click to collapse
thanks for helping, but this don't work because razer phone 2 don't use TOT files, these files are for LG
FellpeSoares said:
¿Alguien puede ayudarme con la copia de seguridad de imagen completa de las particiones eMMC?
Puedo intentar desbloquear mi rp2 con copia de seguridad completa mmcblk0 en la tarjeta sd debido a que mi teléfono ya no ingresa en fastboot, solo veo Qualcomm HS-USB QDLoader 9008 al conectar el usb
También intenté comprar archivos sin ladrillos de este sitio.
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
pero son estafadores !! solo me enviaron una carpeta vacía en google drive
------Actualizar-------
(Razer Phone 2 no tiene mmcblk0)
Ahora tengo otro Razer Phone 2, ahora tengo una copia de seguridad completa de las particiones sda, sdb, sdc, sde, sdf ...
pero tengo un nuevo problema, ¿cómo fusiono estas particiones "cortadas" en mi unidad flash?
Estas particiones tienen el mismo encabezado que se ve en el visor hexadecimal en comparación con los archivos gpt_both
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
También utilicé EDL Generator para crear archivos xml si alguien tiene prog_firehore
mirando systeminfo_a o _b en txt, ves el nombre de la manguera de incendios utilizada, creo
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
Click to expand...
Click to collapse
¿Podría resolverse el problema? Tengo un error algo similar
FellpeSoares said:
Can someone help me with full image backup of partitions eMMC?
I can try unbrick my rp2 with full backup mmcblk0 on sd card due my phone don't enter in fastboot anymore, only i see Qualcomm HS-USB QDLoader 9008 when connecting usb
I also tried buying unbrick files from this site
https://www.aryk.store/2019/07/razer-phone-2-unbrick-files.html
but they are scammers!! they only sent me an empty folder on google drive
------Update-------
(Razer Phone 2 don't have mmcblk0)
Now i have other Razer Phone 2, i have full backup now of partitions sda, sdb, sdc, sde, sdf...
but i have new problem, how i merge theses partitions "cutted" to my flashdrive?
theses partitions have same header looking in hex viewer comparing with gpt_both files
gpt_both0.bin -> sda
gpt_both1.bin -> sdb
gpt_both2.bin -> sdc
gpt_both3.bin -> sdd
gpt_both4.bin -> sde
gpt_both5.bin -> sdf
Also i used EDL Generator to create xml files if someone have prog_firehore
looking systeminfo_a or _b in txt, you see name of firehose used i think
RCL-0-VV-prog_ufs_firehose_8998_ddr.elf, RCL-0-0016-prog_ufs_firehose_8998_ddr.elf
Click to expand...
Click to collapse
so the soc for rp2 is sdm 845. i saw the firehose img in text that you saw but it just makes no sense for 8998 to be in system img when 8998 is the wrong chipset...RAZER enjoys playing games or something...ive been talking with and edl firehose exploiter and may be making progress
ATACELITE said:
so the soc for rp2 is sdm 845. i saw the firehose img in text that you saw but it just makes no sense for 8998 to be in system img when 8998 is the wrong chipset...RAZER enjoys playing games or something...ive been talking with and edl firehose exploiter and may be making progress
Click to expand...
Click to collapse
Any update on the progress?
After the official end of Razer support, I think it's more difficult to get these files now, dev's must be the only one who can have at hand in this moment.
Details of compatible Firehose that we need
HWID: 0008B0E101400003
MSM_ID: 0008B0E1
OEM_ID: 0140
MODEL_ID: 0003
CPU: SDM845
PK_HASH: 074DDB00C617690187503D8C795F497005C760965F8F48A7A8955271E4BF826B
Code:
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
Issuer: C = US, ST = CA, L = San Francisco, OU = Razer MBU, O = Razer, CN = Razer Attestation CA
Validity
Not Before: Mar 5 02:12:06 2019 GMT
Not After : Feb 28 02:12:06 2039 GMT
Subject: C = US, CN = Razer Subsystem Signing User, L = San Francisco, O = Razer, ST = California, OU = 01 0000000000000000 SW_ID, OU = 02 6000000001400003 HW_ID, OU = 04 0140 OEM_ID, OU = 05 00000228 SW_SIZE, OU = 06 0003 MODEL_ID, OU = 07 0001 SHA256, OU = 03 0000000000000000 DEBUG, OU = 13 0001 IN_USE_SOC_HW_VERSION
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:a6:82:5a:af:ba:3e:b3:8b:e0:25:13:e9:02:cd:
1b:a4:d9:e0:78:a6:89:09:2d:8e:84:4c:b7:52:18:
a9:fa:a1:c9:6f:6e:92:8c:30:88:a0:89:99:45:dd:
b3:1c:23:45:17:82:db:c7:1e:c7:45:f4:1f:12:ce:
bd:5e:50:b2:75:18:cb:07:c5:23:9d:14:ba:04:95:
b2:b9:3c:1f:32:60:3f:0f:f5:7c:d6:de:43:69:10:
9c:9f:55:9c:b4:35:ea:e9:b8:d7:5e:e1:f8:1c:05:
f2:97:d2:06:1b:b0:14:37:9d:de:a8:b3:14:0c:f8:
42:cc:c9:ec:42:c2:ec:c8:41:fb:12:67:2c:8b:5c:
cd:ca:a9:ea:db:30:89:4c:56:f7:b4:73:0c:46:7a:
30:0a:e5:9d:33:b6:3d:04:c4:41:87:9c:41:58:2d:
f8:e6:66:a6:52:a5:01:35:9a:92:dc:51:a1:28:e8:
e7:a5:11:ca:ec:a8:1f:0c:cb:58:bb:f9:61:59:46:
0d:92:05:cb:ce:2d:1e:7b:dc:08:93:f1:61:f5:ad:
72:20:a9:db:86:6d:0b:75:63:6c:04:54:a5:5e:89:
91:13:b9:23:da:ad:55:0e:4f:15:08:0c:19:39:56:
25:c2:94:6e:97:4f:b4:fa:10:b4:32:25:ea:40:6f:
d8:47
Exponent: 65537 (0x10001)
X509v3 extensions:
X509v3 Authority Key Identifier:
keyid:CA:43:84:0F:CD:A4:7B:D8:06:12:D2:BF:89:31:6B:93:35:00:DC:F2
X509v3 Basic Constraints:
CA:FALSE, pathlen:0
X509v3 Key Usage:
Digital Signature
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
06:46:11:a4:82:07:1e:d7:d0:67:eb:16:89:08:04:48:82:a8:
91:3d:9d:5e:32:60:f2:ba:11:c7:d1:6b:99:a1:40:ee:41:ad:
e4:e5:95:06:8e:86:59:a5:ad:bd:63:e0:30:9c:d2:f8:75:57:
b3:1d:86:a7:eb:a7:e1:a9:6f:da:70:74:0d:82:ed:7a:ec:1a:
ae:83:d4:0f:25:b6:ba:ae:ac:e0:9a:94:4c:25:6d:38:6e:61:
8d:59:15:73:24:a7:d4:34:2f:41:ae:51:38:d0:46:cd:90:63:
44:9c:d7:c3:64:7b:44:3e:7c:cb:c9:0d:c0:d4:d7:4a:95:fd:
d9:1b:8b:50:a9:38:bf:cf:a7:b2:8f:b6:9e:83:e3:2e:a0:02:
f2:57:60:cd:9e:ab:27:2c:c6:00:f1:dd:c9:2f:9a:bb:fe:4f:
9d:10:66:be:d1:61:d1:77:71:37:a6:de:e1:1f:55:14:0a:16:
2f:54:f3:a5:6b:0e:10:2c:2e:18:28:d0:e7:d2:19:fb:0c:7b:
61:5b:96:7b:48:7e:36:7a:1c:4c:36:07:9d:40:27:7a:ce:05:
9f:23:88:47:69:14:d6:1b:e9:3d:72:1c:91:ed:ab:45:e3:10:
22:a2:8a:67:db:dc:61:02:32:74:58:49:de:0e:ad:87:e9:62:
59:72:13:95
FellpeSoares said:
After the official end of Razer support, I think it's more difficult to get these files now, dev's must be the only one who can have at hand in this moment.
Details of compatible Firehose that we need
HWID: 0008B0E101400003
MSM_ID: 0008B0E1
OEM_ID: 0140
MODEL_ID: 0003
CPU: SDM845
PK_HASH: 074DDB00C617690187503D8C795F497005C760965F8F48A7A8955271E4BF826B
Code:
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1 (0x1)
Signature Algorithm: rsassaPss
Hash Algorithm: sha256
Mask Algorithm: mgf1 with sha256
Salt Length: 0x20
Trailer Field: 0xBC (default)
Issuer: C = US, ST = CA, L = San Francisco, OU = Razer MBU, O = Razer, CN = Razer Attestation CA
Validity
Not Before: Mar 5 02:12:06 2019 GMT
Not After : Feb 28 02:12:06 2039 GMT
Subject: C = US, CN = Razer Subsystem Signing User, L = San Francisco, O = Razer, ST = California, OU = 01 0000000000000000 SW_ID, OU = 02 6000000001400003 HW_ID, OU = 04 0140 OEM_ID, OU = 05 00000228 SW_SIZE, OU = 06 0003 MODEL_ID, OU = 07 0001 SHA256, OU = 03 0000000000000000 DEBUG, OU = 13 0001 IN_USE_SOC_HW_VERSION
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
00:a6:82:5a:af:ba:3e:b3:8b:e0:25:13:e9:02:cd:
1b:a4:d9:e0:78:a6:89:09:2d:8e:84:4c:b7:52:18:
a9:fa:a1:c9:6f:6e:92:8c:30:88:a0:89:99:45:dd:
b3:1c:23:45:17:82:db:c7:1e:c7:45:f4:1f:12:ce:
bd:5e:50:b2:75:18:cb:07:c5:23:9d:14:ba:04:95:
b2:b9:3c:1f:32:60:3f:0f:f5:7c:d6:de:43:69:10:
9c:9f:55:9c:b4:35:ea:e9:b8:d7:5e:e1:f8:1c:05:
f2:97:d2:06:1b:b0:14:37:9d:de:a8:b3:14:0c:f8:
42:cc:c9:ec:42:c2:ec:c8:41:fb:12:67:2c:8b:5c:
cd:ca:a9:ea:db:30:89:4c:56:f7:b4:73:0c:46:7a:
30:0a:e5:9d:33:b6:3d:04:c4:41:87:9c:41:58:2d:
f8:e6:66:a6:52:a5:01:35:9a:92:dc:51:a1:28:e8:
e7:a5:11:ca:ec:a8:1f:0c:cb:58:bb:f9:61:59:46:
0d:92:05:cb:ce:2d:1e:7b:dc:08:93:f1:61:f5:ad:
72:20:a9:db:86:6d:0b:75:63:6c:04:54:a5:5e:89:
91:13:b9:23:da:ad:55:0e:4f:15:08:0c:19:39:56:
25:c2:94:6e:97:4f:b4:fa:10:b4:32:25:ea:40:6f:
d8:47
Exponente: 65537 (0x10001)
Extensiones X509v3:
Identificador de clave de autoridad X509v3:
clave:CA:43:84:0F:CD:A4:7B:D8:06:12:D2:BF:89:31:6B:93:35:00:DC:F2
Restricciones básicas de X509v3:
CA: FALSO, ruta: 0
Uso de la clave X509v3:
Firma digital
Algoritmo de firma: rsassaPss
Algoritmo hash: sha256
Algoritmo de máscara: mgf1 con sha256
Sal Longitud: 0x20
Campo de tráiler: 0xBC (predeterminado)
06:46:11:a4:82:07:1e:d7:d0:67:eb:16:89:08:04:48:82:a8:
91:3d:9d:5e:32:60:f2:ba:11:c7:d1:6b:99:a1:40:ee:41:ad:
e4:e5:95:06:8e:86:59:a5:ad:bd:63:e0:30:9c:d2:f8:75:57:
b3:1d:86:a7:eb:a7:e1:a9:6f:da:70:74:0d:82:ed:7a:ec:1a:
ae:83:d4:0f:25:b6:ba:ae:ac:e0:9a:94:4c:25:6d:38:6e:61:
8d:59:15:73:24:a7:d4:34:2f:41:ae:51:38:d0:46:cd:90:63:
44:9c:d7:c3:64:7b:44:3e:7c:cb:c9:0d:c0:d4:d7:4a:95:fd:
d9:1b:8b:50:a9:38:bf:cf:a7:b2:8f:b6:9e:83:e3:2e:a0:02:
f2:57:60:cd:9e:ab:27:2c:c6:00:f1:dd:c9:2f:9a:bb:fe:4f:
9d:10:66:be:d1:61:d1:77:71:37:a6:de:e1:1f:55:14:0a:16:
2f:54:f3:a5:6b:0e:10:2c:2e:18:28:d0:e7:d2:19:fb:0c:7b:
61:5b:96:7b:48:7e:36:7a:1c:4c:36:07:9d:40:27:7a:ce:05:
9f:23:88:47:69:14:d6:1b:e9:3d:72:1c:91:ed:ab:45:e3:10:
22:a2:8a:67:db:dc:61:02:32:74:58:49:de:0e:ad:87:e9:62:
59:72:13:95[/CÓDIGO]
[/QUOTE]
How to load this code in the razer phone 2?
Click to expand...
Click to collapse
I DONT UNDERSTAND HOW DEEP YOU GUYS GET INTO THESE RZRS. WHENEVER I HAVE A PRBLEM I FLASHALL.BAT. AND IT REFRESHES THE PHONE THEN I RESTART WHATEVER IWAS TRYINA DO. HOWD YOU GET SO DEEP INTO THAT WHOLE OF BEING BRIICKED
itz_jordann said:
I DONT UNDERSTAND HOW DEEP YOU GUYS GET INTO THESE RZRS. WHENEVER I HAVE A PRBLEM I FLASHALL.BAT. AND IT REFRESHES THE PHONE THEN I RESTART WHATEVER IWAS TRYINA DO. HOWD YOU GET SO DEEP INTO THAT WHOLE OF BEING BRIICKED
Click to expand...
Click to collapse
yes I know, but it's all to have control of it
Cremosidad said:
yes I know, but it's all to have control of it
Click to expand...
Click to collapse
wow. man. is it cause of twrp? cause i always go the easy route n use magisk.
Cremosidad said:
yes I know, but it's all to have control of it
Click to expand...
Click to collapse
i feel like magisk is enough control itsself easy to get away bloatware and all the BS. and other simple ****. but it seems like yall are over here trina putta backdoor trojan into the pentagons servers or some **** lmao
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
@alanduda65 Please use the English language!
XDA Forum Rules:
Spoiler: Rule No. 4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hi!
Same thing here, Asus zenfone 5 ZE620KL, after trying to install twrp, phone got stuck in fastboot mode, can't get anywhere else, not recovery or boot to OS
Tried on AMD pc and Intel too, any ideas on how to get the phone working again?
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
asusasus55 said:
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
Click to expand...
Click to collapse
Do we really need to open the back?
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
Hello, I have been researching all day how to solve the problem I have with my Realme x2 pro and I cannot find a solution despite everything I have tried.
I had installed the version "f.14" with A11, I went to enter the recovery mode to try other different roms and it did not go to recovery, but to fastboot, so I decided to install recovery through fastboot ("fastboot flash recovery recovery.img), when The flashing finished I wanted to restart in recovery and went back to fastboot, I tried to restart the mobile to the operating system and to my surprise the screen that I leave below came out ...
I have tested it using fastboot ("fastboot flash boot, dbto, vbmeta, system etc ...), also with tools like Realme Flash Tools (install the entire OFP file, but the mobile does nothing) and the Msm download tool, the latter the tool asks me for a Scarret file (or something like that) that I have no idea how to get it Can anyone explain how I could fix it? Except when I go into fastboot mode this damn screen always appears
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only have the option to enter fastboot mode. Recovery does not work either, when I try to enter recovery mode automatically (without touching anything) it enters fastboot. Has he definitely died?
Thank you very much in advance.
------------------------------------------------------ SPANISH ----------------------------------------------------
Hola, llevo todo el día investigando cómo solucionar el problema que tengo con mi Realme x2 pro y no encuentro una solución a pesar de todo lo que he intentado.
Tenía instalada la versión "f.14" con A11, fui a entrar a modo recovery para probar otras roms diferentes y no entró a recovery, sino a fastboot, entonces decidí instalar recovery mediante fastboot ("fastboot flash recovery recovery.img), cuando terminó el flasheo quise reiniciar en recovery y volvió a fastboot, probé a reiniciar el móvil al sistema operativo y para mi sorpresa salió la pantalla que os dejo debajo ...
Lo he intentado mediante fastboot ("fastboot flash boot, dbto, vbmeta, system etc ...), también con herramientas como Realme Flash Tools (instala todo el archivo OFP, pero el móvil no hace nada) y Msm download tool, esta última tool me pide un archivo scarret (o algo así) que no ni idea como conseguirlo Alguien podría explicarme cómo podría solucionarlo? Excepto cuando entro en modo fastboot, siempre obtengo esta maldita pantalla
Sólo tengo opción de entrar en modo fastboot. Recovery tampoco funciona, cuando intento entrar en modo recovery automáticamente (sin tocar yo nada) entra en fastboot. Ha muerto definitivamente?
Muchas gracias de antemano.
Has he definitely died? Can someone tell me please?
Impakto88 said:
¿¿Definitivamente ha muerto?? ¿Alguien me puede decir porfavor?
Click to expand...
Click to collapse
English is the preferred language in the forums, but you can always use google translate!
Please help us to respect the forum rules.
orb_selektor said:
English is the preferred language in the forums, but you can always use google translate!
Please help us to respect the forum rules.
Click to expand...
Click to collapse
I've already edited the message and translated it, sorry.
Impakto88 said:
Has he definitely died? Can someone tell me please?
Click to expand...
Click to collapse
To get rid of this message and boot normally to system or recovery, Flash the vbmeta.img for your f.14 global firmware with this command in fastboot (bootloader ) mode:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Eng.Raman said:
Para deshacerse de este mensaje y arrancar normalmente en el sistema o en la recuperación, actualice vbmeta.img para su firmware global f.14 con este comando en modo fastboot (gestor de arranque):
fastboot --disable-verity --disable-verificación flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Could you tell me the steps one by one please? I'm pretty clumsy. Sorry.
Impakto88 said:
¿Podrías decirme los pasos uno por uno por favor? Soy bastante torpe. Perdón.
Click to expand...
Click to collapse
boot your device into bootloader mode by holding power button+volume down then flash your vbmeta with the command in my previous post, if you didn't know how to extract vbmeta.img from the ofp firmware use this one attached.
Impakto88 said:
I've already edited the message and translated it, sorry.
Click to expand...
Click to collapse
Impakto88 said:
¿Podrías decirme los pasos uno por uno por favor? Soy bastante torpe. Perdón.
Click to expand...
Click to collapse
Please check your browser (or whatever you use)! You posted again solely in Spanish.
Regards
Oswald Boelcke
Senior Moderator
Eng.Raman said:
boot your device into bootloader mode by holding power button+volume down then flash your vbmeta with the command in my previous post, if you didn't know how to extract vbmeta.img from the ofp firmware use this one attached.
Click to expand...
Click to collapse
I just wrote that command with that last file you sent and I pressed "start" ... It remains the same
Has he definitely died? I need to know please
Impakto88 said:
Has he definitely died? I need to know please
Click to expand...
Click to collapse
No, I told you just need to flash your vbmeta ( extract it from your global f.14 ofp firmware ) with the command that i have mentioned.
If the above suggestion doesn't work for you, Try flashing this boot patched img attached with the latest magisk alpha ( vb disabled ) may solve your issue using this command in bootloader mode:
fastboot flash boot boot_patched-0f71edee.img
Then after successfully booting to system install the magisk alpha app.
Good luck.
Eng.Raman said:
No, le dije que solo necesita actualizar su vbmeta (extraerlo de su firmware global f.14 ofp) con el comando que he mencionado.
Si la sugerencia anterior no funciona para usted, intente flashear este img parcheado de arranque adjunto con el último magisk alpha (vb deshabilitado) puede resolver su problema usando este comando en el modo de cargador de arranque:
fastboot flash boot boot_patched-0f71edee.img
Luego, después de arrancar con éxito el sistema, instale la aplicación magisk alpha.
Buena suerte.
Click to expand...
Click to collapse
It doesn't work for me either. When I finish flashing it, I reboot into recovery and the same screen of "The current image ..." still appears.
I do not have any operating system nor do I have any type of recovery, and no matter how many attempts I make, absolutely no method works for me ... I only have fastboot
If anybody know what will be doing if fastboot not working only Recovery and options there not working with no one new published ota firmware like RMX1931EX_11_OTA_1380_all*
Eng.Raman said:
No, I told you just need to flash your vbmeta ( extract it from your global f.14 ofp firmware ) with the command that i have mentioned.
If the above suggestion doesn't work for you, Try flashing this boot patched img attached with the latest magisk alpha ( vb disabled ) may solve your issue using this command in bootloader mode:
fastboot flash boot boot_patched-0f71edee.img
Then after successfully booting to system install the magisk alpha app.
Good luck.
Click to expand...
Click to collapse
How am I going to install this file using magisk if my system does not work? ...
I tried to do the these steps by following this guide (with EU version, i´m from Spain):
[STOCK][FASTBOOT][CN|EU|IN] Fastboot Flashable Images For RealMe X2 Pro
Disclaimer : * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Your warranty will be void if you tamper with any part of your device /...
forum.xda-developers.com
And this is my summary in fastboot:
C: \ ADB and Fastboot Legacy> fastboot devices
c2d59fb1 fastboot
C: \ ADB and Fastboot Legacy> fastboot flash boot boot.img
Sending 'boot' (98304 KB) OK [2.455s]
Writing 'boot' OKAY [0.577s]
Finished. Total time: 3.032s
C: \ ADB and Fastboot Legacy> fastboot flash dtbo dtbo.img
Sending 'dtbo' (24576 KB) OKAY [0.625s]
Writing 'dtbo' OKAY [0.063s]
Finished. Total time: 0.703s
C: \ ADB and Fastboot Legacy> fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/7 (771038 KB) OKAY [19.244s]
Writing sparse 'system' 1/7 OKAY [0.000s]
Sending sparse 'system' 2/7 (770709 KB) OK [20.034s]
Writing sparse 'system' 2/7 OKAY [0.000s]
Sending sparse 'system' 3/7 (736128 KB) OKAY [19.207s]
Writing sparse 'system' 3/7 OKAY [0.000s]
Sending sparse 'system' 4/7 (765542 KB) OK [19.987s]
Writing sparse 'system' 4/7 OKAY [0.005s]
Sending sparse 'system' 5/7 (782863 KB) OK [20.323s]
Writing sparse 'system' 5/7 OKAY [0.016s]
Sending sparse 'system' 6/7 (755973 KB) OK [19.398s]
Writing sparse 'system' 6/7 OKAY [0.016s]
Sending sparse 'system' 7/7 (293921 KB) OK [12.900s]
Writing sparse 'system' 7/7 OKAY [0.005s]
Finished. Total time: 140.173s
C: \ ADB and Fastboot Legacy> fastboot flash vbmeta vbmeta.img
Sending 'vbmeta' (8 KB) OKAY [0.009s]
Writing 'vbmeta' OKAY [0.003s]
Finished. Total time: 0.028s
C: \ ADB and Fastboot Legacy> fastboot flash vendor vendor.img
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/3 (773808 KB) OKAY [19.509s]
Writing sparse 'vendor' 1/3 OKAY [0.000s]
Sending sparse 'vendor' 2/3 (757497 KB) OK [19.649s]
Writing sparse 'vendor' 2/3 OKAY [0.000s]
Sending sparse 'vendor' 3/3 (64732 KB) OK [10.325s]
Writing sparse 'vendor' 3/3 OKAY [0.000s]
Finished. Total time: 52.433s
Even doing all these steps I cannot get the phone to boot with its operating system (RealmeUI). I have to say that after doing this that red triangle with the error no longer appears ... But even so I only have fastboot, I don't even have recovery
Impakto88 said:
How am I going to install this file using magisk if my system does not work? ...
Click to expand...
Click to collapse
I assume you have system and recovery because you mentioned in your first post that you flashed f.14 ofp via realme flash tool. Did you erase data after flashing ofp or not?
If Not, then erase data with this command: fastboot erase userdata
Then flash your vbmeta with the command that i have mentioned.
Eng.Raman said:
I assume you have system and recovery because you mentioned in your first post that you flashed f.14 ofp via realme flash tool. Did you erase data after flashing ofp or not?
If Not, then erase data with this command: fastboot erase userdata
Then flash your vbmeta with the command that i have mentioned.
Click to expand...
Click to collapse
You have a private message mine, please read it
Impakto88 said:
You have a private message mine, please read it
Click to expand...
Click to collapse
Okay bro.
After several unsuccessful attempts I had a conversation with @Eng.Raman in which he told me that there was a person who completely restored the phone by remote control. He sent me the page to get in touch with that person and feel free to do so.
I have to say that I had ABSOLUTELY NO PROBLEMS with the person in question, quite the opposite, it was all kindness.
What that person did was access my computer and through their tools (Realme's own, I think) ... FIXED MY PHONE! IT'S A GOD !!!
Here I leave the page in case someone has the same problem or a very similar one.
Latest Flash Files And Frp Unlock - GSMMAFIA
www.gsmmafia.com
THANKS TO @Eng.Raman AND THE OTHER PERSON !!