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
hello. in advance sorry for my bad english did the best i could thanks for all the help this is my first post
I own a xt1058 at&t version, bootloader is unlocked and its also rooted, it used to run XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml note that its LPA23.12 not LPAS23.12 it has an (S).
one day it went off(discharged) and now it just turns on and shows bootlogo, bootanimation (both are custom )then it goes black stays there for hours, if i try to go into twrp its stuck on the teamwin image. // un dia se descargo y ahora solo prende me muestra el bootlogo luego el bootanimation ambos son customizados mios y luego se queda en negro al igual cuadno quiero entrar en twrp se queda en la presentacion teamwin
ive tried almost everything I have good Knowledge about flashing // ya he probado casi todo pero necesito de su ayuda tengo buen conocimiento acerca de flashear celulares
tried to flash via rds lite it flashes well it sends the phone to reboot but nothing changes and it stays black after boot image and boot animation so i downloaded more version for it:
XT1058_GHOST_RETAR_5.1_LPA23.12-21.7_cid12_CFC.xml
XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml
XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml
ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF.xml
XT1058_RETAIL-AR_4.4.4_KXA21.12-L1.26_62_cid12_CFC_1FF.xml
XT1058_GHOST_TIMBR_5.1_LPAS23.12-21.7-1_cid12_CFC.xml
FUNNY thing about all is that i have a custom bootlogo and a custom boot animation so when i flash the stock ones, doesnt change a thing and it flashes with no error I WOULD LIKE THAT PEOPLE SEE THIS FIRST AND THE WISE GUYS TRY HELP ME EXPLAIN THIS FIRST lo mas RARO de todo es que como tengo el bootlogo y animation customizado cuando flasheo todas esas rom stock no cambia nada y deberia hacer incluso proba solo con esos archivos a ver si lo delvolvia al warning del bootloader y a el planeta motorola y nada me gustaria que nos enfocaramos en esto ya que puede ser una buena explicacion del por que no esta hagarrando flash
BOOTLOADER DISPLAY:
AP Fastboot Flash Mode (s)
30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
emmc: 16GB sandisk rv=06 PV=07 TY=17
DRAM: 2048 samung s4 SDRAM DIE=4GB
uptime: 2minutes
device is UNLOCKED. Status code:3 (this is highlighted in yellow)
Baterry ok (charging) (this is highlighted in green)
Transfer Mode: USB Connected (highlighted in green also)
PD 1: I always use MFASTBOOT not FASTBOOT but ive tried wit both // he probado con ambos
PD 2: no matter what rom im flashing i always get the same error if i try downgrading it wont let me because of the security thing gpt and stuff, also have modified the lines when flashing with rds nothing works
Got this info in cmd with the following command: fastboot getvar all // esto lo obtuve en CMD con el comando "
fastboot getvar all "
version-bootloader: 30BE
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x1
secure: yes
mid: 026b
serialno: TA1760BX0Y
qe: qe 1/1
unlocked: yes
iswarrantyvoid: yes
max-download-size: 805306368
uid: 9F8110040C000100000000000000
imei: 354984054025132
meid:
sku: 000000000000000
cid: 0x0c
iccid:
date: 11-12-2013
cust_md5:
reason: Key pressed
ro.build.date: Mon Aug 17 05:52:36 CDT 2015
ro.build.id: LPA23.12-21.7
ro.build.tags: bldacfg,release-keys
ro.build.type: user
ro.build.user: hudsoncm
ro.build.version.codename: REL
ro.build.version.incremental: 6
ro.build.version.release: 5.1
ro.mot.build.customerid: att
ro.product.name: ghost_att
ro.build.fingerprint[0]: motorola/ghost_att/ghost:5.1/LPA
ro.build.fingerprint[1]: 23.12-21.7/6:user/bldacfg,releas
ro.build.fingerprint[2]: e-keys
ro.build.version.full[0]: Blur_Version.222.26.7.ghost_att.
ro.build.version.full[1]: ATT.en.US
kernel.version[0]: Linux version 3.4.42-gfff16c8 (h
kernel.version[1]: [email protected]) (gcc version
kernel.version[2]: 4.8 (GCC) ) #1 SMP PREEMPT Mon A
kernel.version[3]: ug 17 06:05:02 CDT 2015
all:
finished. total time: 0.245s
just for recon purposes but everthing still the same error, tried to reflash the twrp with FASTBOOT it says:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery twrp.img
sending 'recovery' (8498 KB)...
OKAY [ 0.769s]
writing 'recovery'...
OKAY [ 0.849s]
finished. total time: 1.619s
NO LUCK STILL GET STUCK also tried a diferent version of twrp same thing.
FLASHING CWM pretty much the same:
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\Root Moto X\Root Moto X
>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.780s]
writing 'recovery'...
OKAY [ 0.869s]
finished. total time: 1.649s
everytime I flash CWM or stock recovery it seens to be overwrited by twrp. Even if I boot right after flashing it. // cada vez que flasheo CWM o Stock recovery pareciera que lo vence el twrp y no se deja cambiar, incluso si hago el flash y de inmediato quiero verificar
MFASTBOOT does give and error with XT1058_GHOST_ATT_5.1_LPA23.12-21.7_cid1_CFC.xml <bootloader> Variable Not supported but not with RSD lite // MFASTBOOT ME DA ERROR <bootloader> Variable Not supported pero rsd lite no da tal error
everyting went just fine but "status" stays on reboot beacause the phone never finish booting so i have to re-enter bootloader so it can say PASS // el rsd todo parece haber ido bien pero el "status" no pasa de reboot debido a que el telefono nunca termina de encender
FLASHING XT1058_GHOST_NIIBR_5.1_LPA23.12-21.7_cid3_CFC.xml with fastboot
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_set
...
OKAY [ 0.130s]
finished. total time: 0.130s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.120s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.359s]
writing 'motoboot'...
flashing tz ...
flashing rpm ...
flashing aboot ...
flashing sbl1 ...
flashing sbl2 ...
flashing sbl3 ...
OKAY [ 5.090s]
finished. total time: 5.450s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash logo logo.bin
sending 'logo' (245 KB)...
OKAY [ 0.310s]
writing 'logo'...
OKAY [ 0.879s]
finished. total time: 1.189s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash boot boot.img
sending 'boot' (10240 KB)...
OKAY [ 1.069s]
writing 'boot'...
OKAY [ 1.348s]
finished. total time: 2.418s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash recovery recovery.img
sending 'recovery' (8488 KB)...
OKAY [ 0.940s]
writing 'recovery'...
OKAY [ 0.908s]
finished. total time: 1.849s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash system system.img
sending 'system' (786432 KB)...
OKAY [ 58.986s]
writing 'system'...
OKAY [ 22.717s]
sending 'system' (663972 KB)...
OKAY [ 50.521s]
writing 'system'...
OKAY [ 19.100s]
finished. total time: 151.327s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash modem NON-HLOS.bin
sending 'modem' (54272 KB)...
OKAY [ 4.180s]
writing 'modem'...
OKAY [ 2.378s]
finished. total time: 6.559s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.459s]
finished. total time: 0.459s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.441s]
finished. total time: 0.441s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot flash fsg fsg.mbn
sending 'fsg' (226 KB)...
OKAY [ 0.330s]
writing 'fsg'...
OKAY [ 0.799s]
finished. total time: 1.129s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase cache
erasing 'cache'...
OKAY [ 0.679s]
finished. total time: 0.679s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.552s]
finished. total time: 0.552s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase customize
erasing 'customize'...
OKAY [ 0.159s]
finished. total time: 0.159s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot erase clogo
erasing 'clogo'...
OKAY [ 0.538s]
finished. total time: 0.539s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot oem fb_mode_clear
...
OKAY [ 0.166s]
finished. total time: 0.166s
D:\Backup\Programs\smarphones\android\Moto X 2012 XT1058\ROM\XT1058_GHOST_NIIBR_
5.1_LPA23.12-21.7_cid3_CFC.xml>fastboot reboot
rebooting...
finished. total time: 0.001s
I tried to cover the most i could so theres no doubt about what im doing please help..!// trate de cubrir el mayor terreno prosible tal vez en cuanto a sus preguntas es mi primer post si falto algo me avisan se los agradezco
sinceros saludos ..almerHDSerViceS:..
Moto X XT1058 (Ghost)
ROM: Lollipop 5.1 Stock (AT&T) | Kernel: Stock | Root: SuperSU | BL: Unlocked | Recovery: TWRP 2.8.6.0
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 !!