Can you unlock bootloader with the rom 26S?

[F.J.V]

X722 brick can not unbrick now , becaus can not file QFIL , but if your phone can work now , please you downgrade to 20S and flash to 26S , it will OEM will unlock , but you don't update to official 26S, only flash the firmware at the link https://www.needrom.com/download/le...728-multilanguage-rom-unbrick-phone-fastboot/

If a rom 26S does not block bootloader it is because it is a custom rom 26S.

You can do exactly the same with any custom 26S.

Greetings.

P.S. NEVER flash official 26S firmware, contains routine blocking. Only 26S firmware modified that does not activate blocking. The lock is on the official firmware and boot.img, not on the rom.

 

[D1stRU3T0R]

If a rom 26S does not block bootloader it is because it is a custom rom 26S.

You can do exactly the same with any custom 26S.

Greetings.

P.S. NEVER flash official 26S firmware, contains routine blocking. Only 26S firmware modified that does not activate blocking. The lock is on the official firmware and boot.img, not on the rom.

Can you post flashable S26 rom, with twrp or stock recovery, which doesn't lock the bootloader?

 

[tony770101]

Can you post flashable S26 rom, with twrp or stock recovery, which doesn't lock the bootloader?

already unlock bootloader at this firmware .

 

[F.J.V]

Can you post flashable S26 rom, with twrp or stock recovery, which doesn't lock the bootloader?

Any custom 26S, example:

https://xdaforums.com/le-pro3/leeco...d-mods/genesys-26s-lepro3-x722-elite-t3702747

Greetings.

 

[sonia gaizka]

x722

I have a nandroid copy of 20S Shop ROM boot. I made nandroid copies of all major partitions (the same ones that have stock ROM) before installing 26S Stock. I used the TWRP of the X722 version to install the ROM. Everything worked. Then I installed the GApps and gave it some error and rebooted. Now I have the bootloader locked, it does not go into recovery mode and it does not start the system. Totally brick.
And the worst: QFIL does not work here. I have tested on different versions, different computers, different drivers and nothing. He always gives this error:

15:47:28: ERROR: function: rx_data:247 Error occurred while reading from COM port
15:47:28: ERROR: function: sahara_main:924 Sahara protocol error
15:47:28: ERROR: function: main:303 Uploading  Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail

And Windows emits the disconnected device sound.
Here is a detailed log using the command to send the FireHose through the CMD:
Log.txt

Any solution happens to me the same thing is hard or soft brick?
it does not let me do anything, the android logo and there I know that and the bootloader blocked

 

[F.J.V]

Any solution happens to me the same thing is hard or soft brick?
it does not let me do anything, the android logo and there I know that and the bootloader blocked

You have permanent brick of x722.

At the moment there is no solution.

regards

 

[D1stRU3T0R]

You have permanent brick of x722.

At the moment there is no solution.

regards

Why it booted first at first try, if he installed the 26S with twrp? Only first boot is working?

 

[F.J.V]

Why it booter first at first try, if he installed the 26S with twrp? Only first boot is working?

Translation problems

I do not understand well to sonia gaizka.
I do not understand well to D1stRU3T0R :laugh:

But...
Black screen, and bootloader blocked on X722 is permanent brick.

Greetings.

 

[Matheusvsp]

Translation problems

I do not understand well to sonia gaizka.
I do not understand well to D1stRU3T0R :laugh:

But...
Black screen, and bootloader blocked on X722 is permanent brick.

Greetings.

how?

 

[Rubén tato]

Como copias la 20s en la SD

 

[rbcarnevale]

Finally, I could find a old version to replace 5.9.026 and come my phone back to life:
https://drive.google.com/uc?id=1aNIDHOVXbrbOxOLkTvP4jKpE9p-VXwXu&export=download

 

[F.J.V]

https://xdaforums.com/le-pro3/leeco...ides-development--and-mods/qfil-x722-t3846553

 

[ochentoso]

\ V V / (_| | | | | | | | | | | (_| |

\_/\_/ \__,_|_| |_| |_|_|_| |_|\__, |

__/ |

|___/





20:01:01: INFO: ==============================================================

20:01:01: INFO: NOTE: There were WARNINGS!! Repeated here, but please see log for more detail

You provided a contents.xml which specified 'C:\Qfil\Qf722\.\devcfg.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\devcfg.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\devcfg.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\devcfg.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main0.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main0.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\xbl.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\xbl.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main1.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main1.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\xbl.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\xbl.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main2.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main2.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main3.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main3.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\rpm.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\rpm.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\rpm.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\rpm.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\tz.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\tz.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\tz.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\tz.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\hyp.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\hyp.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\hyp.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\hyp.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\sec.dat'

However searching through --search_paths found 'C:\Qfil\Qf722\sec.dat'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\pmic.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\pmic.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\pmic.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\pmic.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\asic\NON-HLOS.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\NON-HLOS.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\adspso.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\adspso.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\mdtp.img'

However searching through --search_paths found 'C:\Qfil\Qf722\mdtp.img'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\emmc_appsboot.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\emmc_appsboot.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\emmc_appsboot.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\emmc_appsboot.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\boot.img'

However searching through --search_paths found 'C:\Qfil\Qf722\boot.img'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\recovery.img'

However searching through --search_paths found 'C:\Qfil\Qf722\recovery.img'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\BTFM.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\BTFM.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\keymaster.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\keymaster.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\keymaster.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\keymaster.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\cmnlib.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\cmnlib.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\cmnlib64.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib64.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\cmnlib64.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib64.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main4.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main4.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\gpt_main5.bin'

However searching through --search_paths found 'C:\Qfil\Qf722\gpt_main5.bin'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\devcfg.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\devcfg.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\devcfg.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\devcfg.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\xbl.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\xbl.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\xbl.elf'

However searching through --search_paths found 'C:\Qfil\Qf722\xbl.elf'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\rpm.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\rpm.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\rpm.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\rpm.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\tz.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\tz.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\tz.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\tz.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\hyp.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\hyp.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\hyp.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\hyp.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\sec.dat'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ sec.dat'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Pmic.elf'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ pmic.elf'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Pmic.elf'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ pmic.elf'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Adspso.bin'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ adspso.bin'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Mdtp.img'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ mdtp.img'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Emmc_appsboot.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ emmc_appsboot.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Emmc_appsboot.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ emmc_appsboot.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Boot.img'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ boot.img'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Recovery.img'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ recovery.img'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Keymaster.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ keymaster.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Keymaster.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ keymaster.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Cmnlib.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ cmnlib.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Cmnlib.mbn'

Sin embargo, al buscar a través de --search_paths se encontró 'C: \ Qfil \ Qf722 \ cmnlib.mbn'

Esta es una FUNCIÓN que le permite anular las asignaciones de contents.xml

Si NO QUERÍA ESTE comportamiento, use --forcecontentsxmlpaths



Proporcionó un contenido.xml que especificaba 'C: \ Qfil \ Qf722 \. \ Cmnlib64.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib64.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



You provided a contents.xml which specified 'C:\Qfil\Qf722\.\cmnlib64.mbn'

However searching through --search_paths found 'C:\Qfil\Qf722\cmnlib64.mbn'

This is a FEATURE to allow you to override contents.xml mappings

If you DID NOT WANT THIS behavior, use --forcecontentsxmlpaths



NOTE: There were WARNINGS!! Repeated above, but please see log for more detail

 

[ochentoso]

Hola, la pregunta es muy simple: ¿alguien que haya instalado la rom 26S en x722 ha podido desbloquear el gestor de arranque o instalar otra rom?
Sabemos que en la rom 20S con la que viene de fábrica puedes desbloquear el bootloader e instalar twrp, sabemos que puedes actualizar a la 26S, sabemos que hay personas que han actualizado a 26S, pero nadie que lo haya hecho. actualizado a 26S ha comentado que se pudo instalar otra rom entonces, solo comentar que el gestor de arranque está bloqueado con el 26S.
¿Todos los que han actualizado a 26S tienen que quedarse con ella porque no pueden cambiar?
Bueno, si alguien ha tenido éxito, sería bueno decir cómo lo hizo.
Saludos.

*** HOY, LA ÚNICA FORMA DE SALIR DE OFICIAL 26S ES INSTALAR LA ROM 01D, QUE DESBLOQUEA EL BOOTLOADER Y NOS PERMITE INSTALAR CUALQUIER OTRA ROM. ***

 

[ochentoso]

Hola, la pregunta es muy simple: ¿alguien que haya instalado la rom 26S en x722 ha podido desbloquear el gestor de arranque o instalar otra rom?
Sabemos que en la rom 20S con la que viene de fábrica puedes desbloquear el bootloader e instalar twrp, sabemos que puedes actualizar a la 26S, sabemos que hay personas que han actualizado a 26S, pero nadie que lo haya hecho. actualizado a 26S ha comentado que se pudo instalar otra rom entonces, solo comentar que el gestor de arranque está bloqueado con el 26S.
¿Todos los que han actualizado a 26S tienen que quedarse con ella porque no pueden cambiar?
Bueno, si alguien ha tenido éxito, sería bueno decir cómo lo hizo.
Saludos.

*** HOY, LA ÚNICA FORMA DE SALIR DE OFICIAL 26S ES INSTALAR LA ROM 01D, QUE DESBLOQUEA EL BOOTLOADER Y NOS PERMITE INSTALAR CUALQU

hola, aunque termine, ok. no arranca

 

[ochentoso]

Qfil es una herramienta de Qualcomm para cualquier teléfono inteligente de Qualcomm, sin importar la marca o el desarrollo.
Qfil debería funcionar para cualquier teléfono con chip qualcomm, otra cosa es que el teléfono requiera alguna configuración específica, o que el zip que se pretende flashear no sea el correcto.
Saludos.

Qfil es una herramienta de Qualcomm para cualquier teléfono inteligente de Qualcomm, sin importar la marca o el desarrollo.
Qfil debería funcionar para cualquier teléfono con chip qualcomm, otra cosa es que el teléfono requiera alguna configuración específica, o que el zip que se pretende flashear no sea el correcto.
Saludos.

Qfil es una herramienta de Qualcomm para cualquier teléfono inteligente de Qualcomm, sin importar la marca o el desarrollo.
Qfil debería funcionar para cualquier teléfono con chip qualcomm, otra cosa es que el teléfono requiera alguna configuración específica, o que el zip que se pretende flashear no sea el correcto.
Saludos.

Hola, tengo un le pro 3 x722 con aicp 15 rom. Cuando lo actualicé a 16, terminó bien, funcionó bien, pero a veces se apagaba, y tuve que reiniciarlo por recuperación, ¡hasta que un día ya no comenzaba !. Hice el unbrick con qfil, pero el celular no arranca, aunque parece que se hizo el flash. Adjunto el archivo de informe txt. por favor ayúdame a recuperar el dispositivo. Muchas gracias.

 

[pi RRe]

Hello
I'm replacing a mainboard on my Le Pro 3 ... and the new card got the version 5.9.026S installed on it.
I'm desesperately trying to activate the OEM unlocking ... the toggle is OK but when I reboot in Fastboot I still have this allow unlock to 0


(bootloader) Device product name: [le_zl0_whole_netcom]

(bootloader) Device tampered: false

(bootloader) Device unlocked: false

(bootloader) Device critical unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Serial console enabled: false

(bootloader) Serial hw output enabled: false

(bootloader) Display panel:

(bootloader) is_allow_unlock: 0

 

[pi RRe]

So my question ... is there a way to reinstall a previous version of the system ? or a newer one .. or another one ... without this mandatory step of "fastboot oem unlock" which is not working for me ?