Related
Hi, anyone have the OTA for Android Oreo for our model?
I'm tired to wait VIVO release the upgrade
Please?
https://androidfilehost.com/?fid=746010030569947760
here is the complete fw
Xt1789
El firmware que colocas es para el Xt1789-05? Es una ROM libre de operadora?
Piztache said:
El firmware que colocas es para el Xt1789-05? Es una ROM libre de operadora?
Click to expand...
Click to collapse
si, es libre y si, es para el XT1789-05
Muchas gracias por responder
x-geo said:
si, es libre y si, es para el XT1789-05
Click to expand...
Click to collapse
Gracias por la aportación y por la respuesta
Piztache said:
Gracias por la aportación y por la respuesta
Click to expand...
Click to collapse
Hi Piztache,
Did you manage to install the FW? is it working fine for you? I thinking to do the same with my moto.
----------------------------------------------------------------------------------------------------------------------------
Hola Piztache,
Instalaste el FW? Esta trabajando bien? Estoy pensando en hacer lo mismo en mi moto.
Thanks
Saludos!
Muy bien
Si instale la actualización,aunque como libere el bootloader, actualice todos los archivos , eso hizo que el bootloader se regresara a cerrar, y no me dejaba iniciar el teléfono, lo cual se solucionó, volviendo a abrir el bootloader, el teléfono funciona muy bien y en mi experiencia mejoro la duración de la batería
[email protected] said:
Hi Piztache,
Did you manage to install the FW? is it working fine for you? I thinking to do the same with my moto.
----------------------------------------------------------------------------------------------------------------------------
Hola Piztache,
Instalaste el FW? Esta trabajando bien? Estoy pensando en hacer lo mismo en mi moto.
Thanks
Saludos!
Click to expand...
Click to collapse
darthxa said:
Hi, anyone have the OTA for Android Oreo for our model?
I'm tired to wait VIVO release the upgrade
Please?
Click to expand...
Click to collapse
I have the last Fullflash with the January Patch. I flash in my VIVO via fastboot and it worked normally without the need to have the bootloader unlocked.
djsboy said:
I have the last Fullflash with the January Patch. I flash in my VIVO via fastboot and it worked normally without the need to have the bootloader unlocked.
Click to expand...
Click to collapse
Thanks mate, I did too...and unlocked and rooted with Magisk patched boot image that I made myself with Magisk manager
where do I find the latest ROM with the January patch. I download the file on post #2 and it only has the December patch update
x-geo said:
si, es libre y si, es para el XT1789-05
Click to expand...
Click to collapse
Como le haces para la instalacion? te metes al bootloader del telefono , o usas un software en pc? soy nuevo en el tema, y no se si me podrias explicar paso a paso. te lo agradeceria mucho
darthxa said:
Thanks mate, I did too...and unlocked and rooted with Magisk patched boot image that I made myself with Magisk manager
Click to expand...
Click to collapse
Can I do root on oreo?
lacerdajr said:
Can I do root on oreo?
Click to expand...
Click to collapse
Yes mate. There is a lot of guides here about root this model, what model is yours?
HI, i downloaded the rom stock, but i have the bootloader unlocked and TWPR installed . how can install the firmware via FASTBOOT?
adamantem said:
HI, i downloaded the rom stock, but i have the bootloader unlocked and TWPR installed . how can install the firmware via FASTBOOT?
Click to expand...
Click to collapse
Just use RSD
darthxa said:
Just use RSD
Click to expand...
Click to collapse
I have installed RSD lite 6.2.4, but when i select the zip file i get an error "get decompress file size error"
Can i try it via Fastboot with this? the order is correct?
:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erease userdata
fastboot erase ddr
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
adamantem said:
I have installed RSD lite 6.2.4, but when i select the zip file i get an error "get decompress file size error"
Can i try it via Fastboot with this? the order is correct?
:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erease userdata
fastboot erase ddr
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
First unzip, then try the .xml files in rsd. The flashfile.xml is for resetting and will wipe your data, the servicefile.xml is for upgrading and should leave your data intact.
Sent from my Moto Z (2) using XDA Labs
skywalker-live said:
First unzip, then try the .xml files in rsd. The flashfile.xml is for resetting and will wipe your data, the servicefile.xml is for upgrading and should leave your data intact.
Sent from my Moto Z (2) using XDA Labs
Click to expand...
Click to collapse
The rsd closes as soon as it enters fastboot mode and does nothing. The steps listed by adamantem are correct? Or it could be done only with the command "fastboot flash all? Tks
Dorian Bathory said:
The rsd closes as soon as it enters fastboot mode and does nothing. The steps listed by adamantem are correct? Or it could be done only with the command "fastboot flash all? Tks
Click to expand...
Click to collapse
I answered myself. The steps listed adamantem are fine.
I put the rom without problems by fastboot. Thanks for contributing.:good:
My baseband is <not found> on the fastboot screen and i have no signal or wifi. i was hoping the firmware would correct this, but it didnt. I couldnt use RSD so i did fastboot flash one step at a time,
Any other ideas?
Couldnt get RSD to recognize device and ive read that RSD doesnt play nice with Windows 10
Hello friends, I unlocked the bootloader to install a custom recovery (TWRP) on my phone everything went well until the time of flashing the TWRP, I got an error:
"E:\Nueva carpeta>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 0.439s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.446s"
I tried to flash it to solve the problem but I followed an incorrect tutorial and it only made the problem worse, now the phone does not start, but I still have access to the FASTBOOT MODE
Every time I try to flash it I get the error "target reported max download size", I have no idea what firmware I should use or the correct order of the BAT to flash it, I only have the data of the phone:
BL: MBM-3.0-nash_retal-b48569f-170817
BASEBAND: M8998_20207.117.02.41R NRS
PRODUCT: XT1789-05 64GB PVT
OEM_LOCKED
SOFTWARE STATUS: Official
Could someone please tell me what I can do to solve the problem?
English only please. It is in the forum rules.
Solo inglés por favor. Está en las reglas del foro.
SPANISH
Hola amigos, desbloquié el bootloader para instalar un custom recovery (TWRP) en mi telefono todo fue bien hasta la hora de flashear el TWRP, me daba un error:
"E:\Nueva carpeta>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 0.439s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.446s"
trate de flashearlo para solucionar el problema pero segui un mal tutorial y solo empeore el problema, ahora el telefono no inicia, pero aun tengo acceso al FASTBOOT MODE
cada que trato de flashearlo me da el error "target reported max download size", no tengo idea de que firmware debo usar ni el orden correcto de como flashearlo, solo tengo los dato del telefono:
BL: MBM-3.0-nash_retal-b48569f-170817
BASEBAND: M8998_20207.117.02.41R NRS
PRODUCT: XT1789-05 64GB PVT
OEM_LOCKED
SOFTWARE STATUS: Official
por favor alguien me podría indicar que puedo hacer para solucionar el problema?
Tsuyoecchi said:
Hello friends, I unlocked the bootloader to install a custom recovery (TWRP) on my phone everything went well until the time of flashing the TWRP, I got an error:
"E:\Nueva carpeta>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 0.439s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.446s"
I tried to flash it to solve the problem but I followed an incorrect tutorial and it only made the problem worse, now the phone does not start, but I still have access to the FASTBOOT MODE
Every time I try to flash it I get the error "target reported max download size", I have no idea what firmware I should use or the correct order of the BAT to flash it, I only have the data of the phone:
BL: MBM-3.0-nash_retal-b48569f-170817
BASEBAND: M8998_20207.117.02.41R NRS
PRODUCT: XT1789-05 64GB PVT
OEM_LOCKED
SOFTWARE STATUS: Official
Could someone please tell me what I can do to solve the problem?
Click to expand...
Click to collapse
this phone has no recovery partition. you need to "fastboot boot twrp.IMG"
este teléfono no tiene partición de recuperación. necesitas "fastboot boot twrp.IMG"
Uzephi said:
this phone has no recovery partition. you need to "fastboot boot twrp.IMG"
este teléfono no tiene partición de recuperación. necesitas "fastboot boot twrp.IMG"
Click to expand...
Click to collapse
thank you very much
* and how can I solve the problem of corrupt partitions?
boot with "Your device is corrupt, it can't be trusted and will not boot"
i can't upload picture
Tsuyoecchi said:
thank you very much
* and how can I solve the problem of corrupt partitions?
boot with "Your device is corrupt, it can't be trusted and will not boot"
i can't upload picture
Click to expand...
Click to collapse
try to enter with the TWRP image and the phone froze for a while, restart it a couple of times while pressing VOL- and manage to enter the android recovery and restore the system.
E:\Nueva carpeta>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.440s]
booting...
OKAY [ 0.022s]
finished. total time: 0.466s
I can use my phone again, Thanks for the support!!
Estou com esse problema após instalar a stock ROM 8.1 no meu Moto G5S (Montana) XT1792. Não aparece a bandbase, IMEI desconhecido e não reconhece o chip. Não ser um problema de hardware pois estava funcionando normalmente após eu fazer o procedimento de instalação da stock ROM. Já fiz downgrade, já instalei uma custom ROM e nada, então por não saber mais o que fazer venho pedir ajuda aos membros do XDA. Desde já obrigado!
Tradução/Translation
I have this problem after installing the stock ROM 8.1 on my Moto G5S (Montana) XT1792. The bandbase does not appear, unknown IMEI and does not recognize the chip. Not to be a hardware problem as it was working normally after I did the stock ROM installation procedure. I've already downgraded, I've installed a custom ROM and nothing, so for not knowing what else to do, I'm asking XDA members for help. Thanks in advance!
same problem ( mesmo problema, amigo, aqui somente em ingles,), problema comigo bootloader esta bloqueado, ate eu sei arrumar
meu telegram @eds_Mat
Tradução/Translation
same problem (same problem, friend, here in english only), problem with me bootloader is blocked, even I know how to fix it
my telegram @eds_Mat
1Josueh said:
Estou com esse problema após instalar a stock ROM 8.1 no meu Moto G5S (Montana) XT1792. Não aparece a bandbase, IMEI desconhecido e não reconhece o chip. Não ser um problema de hardware pois estava funcionando normalmente após eu fazer o procedimento de instalação da stock ROM. Já fiz downgrade, já instalei uma custom ROM e nada, então por não saber mais o que fazer venho pedir ajuda aos membros do XDA. Desde já obrigado!
Click to expand...
Click to collapse
edsmat said:
same problem ( mesmo problema, amigo, aqui somente em ingles,), problema comigo bootloader esta bloqueado, ate eu sei arrumar
meu telegram @eds_Mat
Click to expand...
Click to collapse
Other than English languages are not allowed on xda, so please read rules of xda and follow them.
Hello people!
I found out how to recover the chip (recognize), it will be necessary to install the latest rom stock (h t t p s : / / mirrors.lolinet.com/firmware/moto), there look for MONTANA, then click OFFICIAL and find it by RETAIL (h t t p s : / / mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/), perform the flash procedure after downloading the ROM (more updated with the commands below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot flash logo logo.bin
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
fastboot reboot
lopesgang said:
Hello people!
I found out how to recover the chip (recognize), it will be necessary to install the latest rom stock (h t t p s : / / mirrors.lolinet.com/firmware/moto), there look for MONTANA, then click OFFICIAL and find it by RETAIL (h t t p s : / / mirrors.lolinet.com/firmware/moto/montana/official/RETAIL/), perform the flash procedure after downloading the ROM (more updated with the commands below:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot flash logo logo.bin
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash boot boot.img
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
Muito obrigado! Sua dica resolveu meu problema!
Tradução/Translation
Thank you very much! Your tip solved my problem!
1Josueh edsmat clewbber
Como podem observar foi adicionada tradução aos vossos posts anteriores mas esse trabalho deve ser feito por vós conforme ditam as regras do forum
Aconselho vivamente que as leiam e tirem qualquer duvida que possa existir junto da equipa de moderação!
Tradução/Translation
As you can see, translation was added to your previous posts but this work must be done by you as dictated by the forum rules.
I strongly advise you to read them and remove any doubts that may exist with the moderation team!
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, downloaded the linked driver & installed it. Now Fastbootd works
Edit #2: Turns out Mi Flash has the same drivers! You just need to disable Driver Signature Enforcement before installing the drivers, otherwise it won't install *all*.
tomxyz said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Click to expand...
Click to collapse
Try to reset using MIUNLOCK application.
There is a tool to set first time fastboot setting .
tomxyz said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, enabled Test Signing & downloaded the linked driver & installed it. Now Fastbootd works
Click to expand...
Click to collapse
I think this is exactly my problem. I have tried many roms but was only able to get the roms that had fastboot installation to work.i was thinking of trying arrowos next. Why didn't you like it?
Edit this was not my problem i had to assign drive letter in-order to install twrp.
jackscagnetti said:
I think this is exactly my problem. I have tried many roms but was only able to get the roms that had fastboot installation to work.i was thinking of trying arrowos next. Why didn't you like it?
Edit this was not my problem i had to assign drive letter in-order to install twrp.
Click to expand...
Click to collapse
"Was only able to get Fastboot ROMs to work" So they worked for you? Or typo?
I did try out ArrowOS, it's really nice and simple. I saw that it has Blur effects in the UI compared to the other ROMs which don't. But it doesn't have many other features, it doesn't have *any* Sound effects at all, unfortunately.
I tried out Xiaomi.eu, ArrowOS, Havoc OS and Syberia OS. Lastly I'll try out crDroid.
I think of going back to Xiaomi.eu which is my daily driver. I don't like MIUI, but I really like all the Camera features, the Dolby Atmos Sound (important for me), and the Font thiccness setting
your thread helped me a ton. wasn't able to flash fastboot roms before
thx a ton!
m0lly. said:
your thread helped me a ton. wasn't able to flash fastboot roms before
thx a ton!
Click to expand...
Click to collapse
Awesome! I'm glad it helped you!
dreamytom said:
Penso che il mio PC non disponga dei driver Fastboot corretti. Qualcuno può portarmi da loro?
Il mio problema è che ogni ROM personalizzata con una ROM Fastboot non funziona. I loro script Install&Format.bat non funzionano correttamente.
Il loro script farebbe i suoi compiti, fino a "fastboot reboot fastboot". Si bloccherebbe su " In attesa di qualsiasi dispositivo ", perché il mio PC non rileva i dispositivi Fastbootd, ne sono molto sicuro.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Invio 'boot_a' (196608 KB) OKAY [ 4.674s]
Scrivendo 'boot_a' OKAY [ 0.259s]
Finito. Tempo totale: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Invio di 'vendor_boot_a' (98304 KB) OKAY [2.399s]
Scrivendo 'vendor_boot_a' OKAY [0.125s]
Finito. Tempo totale: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Impostazione dello slot corrente su 'a' OKAY [ 0.003s]
Finito. Tempo totale: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Riavvio in fastboot OKAY [0.003s]
< in attesa di qualsiasi dispositivo >
[/CODICE]
[B]Modifica: [/B] poco dopo aver pubblicato questo post, ho risolto il mio problema. avevo ragione. Il problema era infatti un driver Fastboot mancante o guasto in Windows.
[URL unfurl="true"]https://c.mi.com/oc/thread-3312019-1-0.html[/URL]
[B]Ho seguito quel sito Web e disabilitato l'applicazione della firma del driver, abilitato la firma di prova, scaricato il driver collegato e installato. Ora Fastbootd funziona[/B] :)
[/QUOTE]
GRAZIE! Ho usato il metodo che hai usato tu. Funziona! ora win10 riconosce il mio poco f3 in fastboot e fastbootd. grazie per averlo condiviso! grande!
[ATTACH type="full" alt="Icona di Verificata con community"]5399187[/ATTACH]
Click to expand...
Click to collapse
THANK YOU! I used the method you used. it works! now win10 recognize my poco f3 in fastboot and fastbootd. thanks for sharing it! big up!
dreamytom said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, enabled Test Signing & downloaded the linked driver & installed it. Now Fastbootd works
Click to expand...
Click to collapse
Hi
also found the same Guide....
Did you also use the latst instruction or not ?
bcdedit /set testsigning off ... ?
So far i have only ever managed to get into FastbootD by conection via ADB.
open Power_Shell - via "shift + Right mouse klick"
Run Command : adb reboot fastboot.
phone (mi11lite5g) is then in FastbootD mode.
Could this be because i already flshed miui-eu 12.5.3 via fastboot ( non stock Recovery ? )
still get some partition not found error...
If i use the "fastboot reboot fastboot" method (as described in the How_To)... nothing happens...
FYI.. also its impossible to connect to the phone with the MiPCSuite or the Mi-Flash tool
The Mi-Flash tool recognises the device, But i cannot flash any stock image to the phone, as this results in an Error.
any advice Much appreciated.
dont use cmd command to reboot into fastboot it will surely reboot to fastbootd try manuall pressing power and volume down in order to get fastboot spelling
metaxo said:
Hi
also found the same Guide....
Did you also use the latst instruction or not ?
bcdedit /set testsigning off ... ?
So far i have only ever managed to get into FastbootD by conection via ADB.
open Power_Shell - via "shift + Right mouse klick"
Run Command : adb reboot fastboot.
phone (mi11lite5g) is then in FastbootD mode.
Could this be because i already flshed miui-eu 12.5.3 via fastboot ( non stock Recovery ? )
still get some partition not found error...
If i use the "fastboot reboot fastboot" method (as described in the How_To)... nothing happens...
FYI.. also its impossible to connect to the phone with the MiPCSuite or the Mi-Flash tool
The Mi-Flash tool recognises the device, But i cannot flash any stock image to the phone, as this results in an Error.
any advice Much appreciated.
Click to expand...
Click to collapse
Yes, I got FastbootD only through ADB, but there might be other ways as well.
I found out that enabling Test-Signing is not necessary.
dreamytom said:
Yes, I got FastbootD only through ADB, but there might be other ways as well.
I found out that enabling Test-Signing is not necessary.
Click to expand...
Click to collapse
Yep.. Finally got it working..:
Had to put the adb folder on C:
And run it from there using CMD..!!
Not power-shell..like I was
Everything worked fine after that...
Thanks..
Thanks for the tutorial. It finally worked and solved my issue.
Hi, please bare with me, haven't posted on here in years.
I would like to flash the phone wiping all the partitions and rebuilding it entirely, as if it were new. The phone is not currently bricked.
My bootloader is unlocked (can lock if needed).
Everything I tried, and miserably failed so far.
Realme flash tool. Central directory not found.
Next, I tried italorecife/OppoRealme-OFP-Flash, which, in short, failed to extract the OFP file.
I tried both OFP's located in both the Indian and Global packages, them being 11a26 RMX3241, (can paste exact file names if needed).
Since all that failed, I tried to extract the OFP, (that worked) and I tried a good old fastboot flash -all. That told me my device does not support slots?
To eliminate driver issues etc, I even tried fastboot flash -all on a macbook via terminal, USBC to USBC only to be presented with the same error...
What am I missing please? Would be happy to provide further information where necessary.
Am willing to use regular fastboot commands, but I'm confused on the multiple part IMG files. Would also be happy to do TWRP, but I don't know if that natively supports installing realme zip files, and or OFP files? Any clarification there would be appreciated.
Many thanks for any pointers!
Hlo I am happy to share that I have found a way to fix hardbrick and softbrick of realme 8 5g.
REALME 8 5G SOFTBRICK SOLUTION
1ST STEP
GO TO FASTBOOT (BOOTLOADER) MODE AND CONNECT TO PC OPEN PLATFORM TOOL CMD PROMT THEN ERASE ALL IMG USING CMD LIKE (FASTBOOT ERASE BOOT)
(FASTBOOT ERASE VBMETA)
(FASTBOOT ERASE SUPER)
OK NOW YOUR ALL IMGS REMOVE YOUR PHONE THEN FLASHING START NOW
FLASH (FASTBOOT FLASH BOOT /DRAG BOOT IMG
FASTBOOT FLAHS LK /LK.IMG
FASTBOOT FLAHS SUPER /SUPER28726.IMG LIKE OK THEN ALL IMG FLAHS SUCCESS FULLY THEN TURN ON
Iska dhayan rkhna ki super IMG 3 hogi toh tino flash karna ok or agr aapka phone on n ho sab FLAsh karne ke baad toh 1st super IMG ko ek baar or FLAHS kar dena then reboot ur phone and enjoy
Any help contact me telegram @rom1developer
Krishnaxda91 said:
SOLUCIÓN REALME 8 5G SOFTBRICK
1ER PASO
VAYA AL MODO FASTBOOT (CARGADOR DE ARRANQUE) Y CONÉCTESE A LA PC ABRA LA HERRAMIENTA DE LA PLATAFORMA CMD PROMT LUEGO BORRE TODAS LAS IMÁGENES UTILIZANDO CMD COMO (FASTBOOT ERASE BOOT)
(FASTBOOT BORRAR VBMETA)
(FASTBOOT ERASE SÚPER)
OK AHORA TUS TODAS LAS IMGS QUITA TU TELÉFONO LUEGO PARPADEA COMENZAR AHORA
FLASH (FASTBOOT FLASH BOOT /DRAG BOOT IMG
FLASH DE ARRANQUE RÁPIDO LK /LK.IMG
FASTBOOT FLAHS SUPER /SUPER28726.IMG ME GUSTA OK ENTONCES TODAS LAS FLAHS DE IMG SON EXITOSAS LUEGO ENCIENDA
Click to expand...
Click to collapse
Hola mí realme 8 5g no reconoce los operadores de mi país Venezuela después de flashear con una rollback india , quiero flashear pero no pudo , usó la herramienta REALME flash TOOL y dice directorio no encontrado,
Krishnaxda91 said:
Any help contact me telegram @KRISHNA32413242
Click to expand...
Click to collapse
Hello, can you help me about my Realme 8 5G after i downgrade it doesn't have a data connection.
what frmware flasher for realme 8 5g urgently need an answer??????
can you help me also. ive flashed india firmware while downgrading. now i dont have network
Krishnaxda91 said:
REALME 8 5G SOFTBRICK SOLUTION
1ST STEP
GO TO FASTBOOT (BOOTLOADER) MODE AND CONNECT TO PC OPEN PLATFORM TOOL CMD PROMT THEN ERASE ALL IMG USING CMD LIKE (FASTBOOT ERASE BOOT)
(FASTBOOT ERASE VBMETA)
(FASTBOOT ERASE SUPER)
OK NOW YOUR ALL IMGS REMOVE YOUR PHONE THEN FLASHING START NOW
FLASH (FASTBOOT FLASH BOOT /DRAG BOOT IMG
FASTBOOT FLAHS LK /LK.IMG
FASTBOOT FLAHS SUPER /SUPER28726.IMG LIKE OK THEN ALL IMG FLAHS SUCCESS FULLY THEN TURN ON
Click to expand...
Click to collapse
New
Add bookmark
#9
can you help me also. ive flashed india firmware while downgrading. now i dont have network