FIRMWARE Original PPKS29.68-16-21-5 XT1941-3 RETBR
DOWNLOAD
ADB commands
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp_a adspso.bin
fastboot flash logo_a logo.bin
fastboot flash boot_a boot.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_a system.img_sparsechunk.6
fastboot flash system_a system.img_sparsechunk.7
fastboot flash system_a system.img_sparsechunk.8
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Mega will not let you download files bigger than 500mb if you do not have an account.
Fala amigo, te falar, instalei tudo certinho nao deu erro no rsd lite, porem nao inicia Startup-Failed
Notei esta MSG: SSM: Boot image roll back 5,6 como se estivesse fazendo um downgrade, porem esta versao que voce postou é a ultima.
Voce tem alguma ideia disto ?
Solução Startup Failed
Blz aconteceu comigo no moto g5s. E consegui resolver, você tem que baixar o fastboot edl. Extrai e coloca na pasta adb junto com a rom. Coloca no momento fastboot e clica em Reboot. Aí roda o fastboot
jefflima1 said:
Fala amigo, te falar, instalei tudo certinho nao deu erro no rsd lite, porem nao inicia Startup-Failed
Notei esta MSG: SSM: Boot image roll back 5,6 como se estivesse fazendo um downgrade, porem esta versao que voce postou é a ultima.
Voce tem alguma ideia disto ?
Click to expand...
Click to collapse
Eu tenho aqui o fastboot edl, coloco dentro da pasta da ROM, starto o edl.cmd e inicio a atualização pelo RSD ou pode ser no próprio cmd ?
Estranho de mais, ainda não peguei este tipo de erro.
---------- Post added at 08:19 PM ---------- Previous post was at 08:01 PM ----------
rbragars said:
Blz aconteceu comigo no moto g5s. E consegui resolver, você tem que baixar o fastboot edl. Extrai e coloca na pasta adb junto com a rom. Coloca no momento fastboot e clica em Reboot. Aí roda o fastboot
Click to expand...
Click to collapse
É amigão, deu certo não, cliquei la no modo edl, reiniciou startei, porem o erro persiste, edl mode acredito que seja para colocar em modo qualcom, tipo os xiaomi em edl mode,
enfim, tentei no RSD e via linha de comando, e nenhum dos 2 deu certo, ele completa a ROM, reinicia aparece MOTO ONE, ai desliga novamente e já volta na tela de fastboot informando
SSM: Boot image roll back: 5,6
Failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
boot up failed
Des de já agradeço a atenção de todos...
Obrigado
Deu certo?
Blz viu os dois tutorial?
jefflima1 said:
Fala amigo, te falar, instalei tudo certinho nao deu erro no rsd lite, porem nao inicia Startup-Failed
Notei esta MSG: SSM: Boot image roll back 5,6 como se estivesse fazendo um downgrade, porem esta versao que voce postou é a ultima.
Voce tem alguma ideia disto ?
Click to expand...
Click to collapse
Hello,
anyone got the XT1941-4 RETEU PPKS29.68-16-21-5 ?
thanks.
Aureal2 said:
Hello,
anyone got the XT1941-4 RETEU PPKS29.68-16-21-5 ?
thanks.
Click to expand...
Click to collapse
Go to mirrorlolinet and go find it
borksek said:
Go to mirrorlolinet and go find it
Click to expand...
Click to collapse
hello, I can't find for my model (XT1941-4 RETEU).
Aureal2 said:
hello, I can't find for my model (XT1941-4 RETEU).
Click to expand...
Click to collapse
You didn't even search then. Litsen. I took my time to get it since your too lazy. https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
borksek said:
You didn't even search then. Litsen. I took my time to get it since your too lazy. https://mirrors.lolinet.com/firmware/moto/deen/official/RETEU/
Click to expand...
Click to collapse
I'm not lazy my friend
in lolinet there is no version I'm looking for: PPKS29.68-16-21-5
bye.
Aureal2 said:
I'm not lazy my friend
in lolinet there is no version I'm looking for: PPKS29.68-16-21-5
bye.
Click to expand...
Click to collapse
It's old. Update.
thanks for your help
so, the last is this: XT1941-4_DEEN_RETEU_9.0_PPK29.68-16-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I unpacked this zip and I see compilation date: feb-19 when the OP ROM (my same version) has mar-19. It's a problem or it doesn't mean nothing?
bye.
Aureal2 said:
thanks for your help
so, the last is this: XT1941-4_DEEN_RETEU_9.0_PPK29.68-16-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
I unpacked this zip and I see compilation date: feb-19 when the OP ROM (my same version) has mar-19. It's a problem or it doesn't mean nothing?
bye.
Click to expand...
Click to collapse
That's not the newest version, it's a corrupted version. No security update no nothing. It's bootable and works good. Only problem is old security update and no updates.
borksek said:
That's not the newest version, it's a corrupted version. No security update no nothing. It's bootable and works good. Only problem is old security update and no updates.
Click to expand...
Click to collapse
thank you borksek.
do you have some advice for ROM to flash or I have simply to wait new upload?
Aureal2 said:
thank you borksek.
do you have some advice for ROM to flash or I have simply to wait new upload?
Click to expand...
Click to collapse
If you know how to take logs and actually test frequently I'll add you to our telegram group for testing.
borksek said:
If you know how to take logs and actually test frequently I'll add you to our telegram group for testing.
Click to expand...
Click to collapse
mmm.. maybe later
for now I need to stick with a official ROM.
There is something not corrupted in lolinet or not?
thanks!
Aureal2 said:
mmm.. maybe later
for now I need to stick with a official ROM.
There is something not corrupted in lolinet or not?
thanks!
Click to expand...
Click to collapse
Yes, every zip except that one I think.
borksek said:
Yes, every zip except that one I think.
Click to expand...
Click to collapse
if I flash a ROM with a previous security patch would I have problems? (I read something in other thread)
or it's only related to downgrade (from Android 9 to 8.1 for example)..
big thanks for your help!
Related
Personal and much regret that I come to ask for help, I bought my RAZR xt910 and after 20 days of use the Jelly Bean tried putting it, ja made many upgrades exchanges roms on android devices, namely first sailor'm not traveling.
is as follows, I have tried upgrade to jelly bean, and the device stuck at boot, did everything right, until then there beauty downloaded the rom it stok to ics 4.0.4 and spent the RSD lite it, it was beautiful, it was returned to the . After one week he discharged. put to load and when I woke up in the morning, he was on the screen with Fastboot mesangem error at boot, system, etc. and locked cdrom device.
Oh my headache started again spent the RDS lite, to my surprise, he did not want to complete the process, was giving error checking, always kept in the boot flash or mbm_signed, etc..
I entered the ADB and went fast boot, and deleted the cache. with the command fastboot erase cache fastboot erase userdata and.
again and spent the RDS Lite and nothing. these attempts was discharging the battery, now think the **** he gave.
with the message he batery low program.
I thought I'd send in assistance until the motorola but here in my city has authorized only collection station. then it would take about 30 to 40 days to settle and look there.
So I took courage to open the back cover of the device and recharge the battery. with the battery charged.
I started doing it again trying to recuparar rom him.
and without success. Now that is the ****. then deleted all the binary files to erase his memory any residue of the old flash I made earlier without success. following files and command that it efetuei:
fastboot erase boot_signed
fastboot erase cdrom_signed
fastboot erase devtree_signed
fastboot erase ebr_signed
fastboot erase mbr_signed
fastboot erase mempodroid
fastboot erase preinstall
fastboot erase recovery_signed
fastboot erase system_signed
fastboot erase logo.bin
fastboot erase mbm.bin
fastboot erase mbmloader.bin
fastboot erase cdt.bin_signed
fastboot erase radio
Delete this file even after he was connected and responding to the command fastboot
but after I despluga usb it already was. He hung up and will not turn over, nor angry with prayer. and the computer does not recognize it anymore.
it recognizes only the OMAP4430 chip, and is detecting and disconnects after 3 seconds and back.
Personal'm desperate, do not know what else to do to recover the device, which a few days and bought expensive by the way.
Who can give me a force there to retrieve the device will definitely rewarding.
__________________________________________________________________
Pessoal e muito pesar que venho pedir uma ajuda, comprei meu RAZR xt910 e apos 20 dias de uso tentei colocar o Jelly bean nele, ja fiz muitas atualizações trocas de roms em aparelhos android, ou seja não sou marinheiro de primeira viajem.
é o seguinte, tentei atualizar para jelly bean, e a aparelho ficou preso no boot, fiz tudo direitinho, ate ai então beleza baixei a rom stok dele a ics 4.0.4 e passei o RSD lite nele, ficou beleza, voltou pra o que era. depois de uma semana, ele descarregou. coloquei pra carregar e quando acordei pela manha, ele estava na tela do Fastboot com a mesangem de erro no boot, system, cdrom device locked e etc.
Ai começou minha dor de cabeça, novamente passei o RDS lite, para minha surpresa, ele não queria mais concluir o processo, estava dando erro de verificação, sempre parava no flash do boot ou mbm_signed, etc.
Entrei no ADB e fui do fast boot, e apaguei os cache. com o comando fastboot erase cache e fastboot erase userdata.
e passei novamente o RDS LIte e nada. nessas tentativas a bateria foi descarregando, pense agora na merda que deu.
com a mensagem de batery low ele não programa.
Pensei em ate mandar na assistencia da motorola, mas aqui na minha cidade não tem autorizada, somente posto de coleta. então ia demorar uns 30 a 40 dias para resolverem e olhe lá.
Então tomei coragem para abrir a tampa traseira do aparelho e recarregar a bateria. com a bateria carregada.
fazendo isso comecei novamente a tentar recuparar a rom dele.
e sem sucesso. agora que vem a merda. então apaguei todos os arquivos binarios da memoria dele para apagar qualquer residuo do antigo flash que fiz anteriormente sem sucesso. segue os arquivos e comando que efetuei nele:
fastboot erase boot_signed
fastboot erase cdrom_signed
fastboot erase devtree_signed
fastboot erase ebr_signed
fastboot erase mbr_signed
fastboot erase mempodroid
fastboot erase preinstall
fastboot erase recovery_signed
fastboot erase system_signed
fastboot erase logo.bin
fastboot erase mbm.bin
fastboot erase mbmloader.bin
fastboot erase cdt.bin_signed
fastboot erase radio
Apos mesmo deletar esse arquivos ele estava ligado e respondendo aos comando do fastboot
mas apos eu despluga-lo do usb ja era. ele desligou e não liga mais, nem com reza brava. e o computador não reconhece ele mais.
reconhece apenas o chip dele que o OMAP4430, e fica detectando e apos 3 segundo desconecta e volta.
Pessoal estou desesperado, não sei mais o que fazer para recuperar o aparelho, que a poucos dias comprei e caro por sinal.
quem poder me dar uma força ai para recuperar o aparelho com certeza vou recompensar.
Interesting, you cooked your first ROM but I can't find a link or I can't read.
blassom said:
Pessoal e muito pesar que venho pedir uma ajuda, comprei meu RAZR xt910 e apos 20 dias de uso tentei colocar o Jelly bean nele, ja fiz muitas atualizações trocas de roms em aparelhos android, ou seja não sou marinheiro de primeira viajem.
é o seguinte, tentei atualizar para jelly bean, e a aparelho ficou preso no boot, fiz tudo direitinho, ate ai então beleza baixei a rom stok dele a ics 4.0.4 e passei o RSD lite nele, ficou beleza, voltou pra o que era. depois de uma semana, ele descarregou. coloquei pra carregar e quando acordei pela manha, ele estava na tela do Fastboot com a mesangem de erro no boot, system, cdrom device locked e etc.
Ai começou minha dor de cabeça, novamente passei o RDS lite, para minha surpresa, ele não queria mais concluir o processo, estava dando erro de verificação, sempre parava no flash do boot ou mbm_signed, etc.
Entrei no ADB e fui do fast boot, e apaguei os cache. com o comando fastboot erase cache e fastboot erase userdata.
e passei novamente o RDS LIte e nada. nessas tentativas a bateria foi descarregando, pense agora na merda que deu.
com a mensagem de batery low ele não programa.
Pensei em ate mandar na assistencia da motorola, mas aqui na minha cidade não tem autorizada, somente posto de coleta. então ia demorar uns 30 a 40 dias para resolverem e olhe lá.
Então tomei coragem para abrir a tampa traseira do aparelho e recarregar a bateria. com a bateria carregada.
fazendo isso comecei novamente a tentar recuparar a rom dele.
e sem sucesso. agora que vem a merda. então apaguei todos os arquivos binarios da memoria dele para apagar qualquer residuo do antigo flash que fiz anteriormente sem sucesso. segue os arquivos e comando que efetuei nele:
fastboot erase boot_signed
fastboot erase cdrom_signed
fastboot erase devtree_signed
fastboot erase ebr_signed
fastboot erase mbr_signed
fastboot erase mempodroid
fastboot erase preinstall
fastboot erase recovery_signed
fastboot erase system_signed
fastboot erase logo.bin
fastboot erase mbm.bin
fastboot erase mbmloader.bin
fastboot erase cdt.bin_signed
fastboot erase radio
Apos mesmo deletar esse arquivos ele estava ligado e respondendo aos comando do fastboot
mas apos eu despluga-lo do usb ja era. ele desligou e não liga mais, nem com reza brava. e o computador não reconhece ele mais.
reconhece apenas o chip dele que o OMAP4430, e fica detectando e apos 3 segundo desconecta e volta.
Pessoal estou desesperado, não sei mais o que fazer para recuperar o aparelho, que a poucos dias comprei e caro por sinal.
quem poder me dar uma força ai para recuperar o aparelho com certeza vou recompensar.
Click to expand...
Click to collapse
Do you realize that xda, specifically this section, is an international forum and english is the primary language? Talking portuguese will lead you nowhere.
You just digg your own grave when you deleted mbm.bin, mbmloader.bin, boot signed and disconnected the phone!!!
You should have reflashed at least, the boot loaders again. I think that you'll have to send it to Motorola, so they can fix with their propper tools.
p34c3m4k3r said:
Do you realize that xda, specifically this section, is an international forum and english is the primary language? Talking portuguese will lead you nowhere.
You just digg your own grave when you deleted mbm.bin, mbmloader.bin, boot signed and disconnected the phone!!!
You should have reflashed at least, the boot loaders again. I think that you'll have to send it to Motorola, so they can fix with their propper tools.
Click to expand...
Click to collapse
Personal and much regret that I come to ask for help, I bought my RAZR xt910 and after 20 days of use the Jelly Bean tried putting it, ja made many upgrades exchanges roms on android devices, namely first sailor'm not traveling.
is as follows, I have tried upgrade to jelly bean, and the device stuck at boot, did everything right, until then there beauty downloaded the rom it stok to ics 4.0.4 and spent the RSD lite it, it was beautiful, it was returned to the . After one week he discharged. put to load and when I woke up in the morning, he was on the screen with Fastboot mesangem error at boot, system, etc. and locked cdrom device.
Oh my headache started again spent the RDS lite, to my surprise, he did not want to complete the process, was giving error checking, always kept in the boot flash or mbm_signed, etc..
I entered the ADB and went fast boot, and deleted the cache. with the command fastboot erase cache fastboot erase userdata and.
again and spent the RDS Lite and nothing. these attempts was discharging the battery, now think the **** he gave.
with the message he batery low program.
I thought I'd send in assistance until the motorola but here in my city has authorized only collection station. then it would take about 30 to 40 days to settle and look there.
So I took courage to open the back cover of the device and recharge the battery. with the battery charged.
I started doing it again trying to recuparar rom him.
and without success. Now that is the ****. then deleted all the binary files to erase his memory any residue of the old flash I made earlier without success. following files and command that it efetuei:
fastboot erase boot_signed
fastboot erase cdrom_signed
fastboot erase devtree_signed
fastboot erase ebr_signed
fastboot erase mbr_signed
fastboot erase mempodroid
fastboot erase preinstall
fastboot erase recovery_signed
fastboot erase system_signed
fastboot erase logo.bin
fastboot erase mbm.bin
fastboot erase mbmloader.bin
fastboot erase cdt.bin_signed
fastboot erase radio
Delete this file even after he was connected and responding to the command fastboot
but after I despluga usb it already was. He hung up and will not turn over, nor angry with prayer. and the computer does not recognize it anymore.
it recognizes only the OMAP4430 chip, and is detecting and disconnects after 3 seconds and back.
Personal'm desperate, do not know what else to do to recover the device, which a few days and bought expensive by the way.
Who can give me a force there to retrieve the device will definitely rewarding.
Haha I am sorry but the translation is hilarious
namely first sailor'm not traveling.
Click to expand...
Click to collapse
:laugh::laugh::laugh::laugh::victory::victory:
romdroid. said:
Haha I am sorry but the translation is hilarious
:laugh::laugh::laugh::laugh::victory::victory:
Click to expand...
Click to collapse
Help pleaseeeeeeeeeee
Im amazed....why did u delete all partitions?
I'm not sure if your phone will ever power on without boot loader and recovery partition...
Really....why u did that?:banghead:
And BTW.....you shouldn't post this here...
Enviado desde mi XT910 usando Tapatalk 2
Honestly, arranges for technical assistance. You really ****ed your device.
Try to send it back to Motorola assistance, i did bricked and disassembled an Atrix, brought it to assistance to quote for repair, after a month they sended back repaired free of charge.
blassom said:
it recognizes only the OMAP4430 chip, and is detecting and disconnects after 3 seconds and back.
Click to expand...
Click to collapse
This sounds like OMAP ROM Code.
{
"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"
}
image from - http://omappedia.org/wiki/Bootloader_Project
Upon boot, OMAP ROM code will search for a 1st-stage bootloader.
Probably in these location order.
1. Internal Storage (NAND Loader)
2. Serial
3. SD Card
Since you've delete your NAND loader...CPU trying the next order
(at least give you 3 second to upload a bootloader via serial)
There's a chance we can load a custom boot loader from sd-card
p/s : someday when I don't need this phone.. I'll kill it this way
If I'm lucky, I'll get to boot an unlocked bootloader.
Help, please
Then I can put files in it's original stock rom to see if you can read the boot?
whirleyes said:
This sounds like OMAP ROM Code.
Upon boot, OMAP ROM code will search for a 1st-stage bootloader.
Probably in these location order.
1. Internal Storage (NAND Loader)
2. Serial
3. SD Card
Since you've delete your NAND loader...CPU trying the next order
(at least give you 3 second to upload a bootloader via serial)
There's a chance we can load a custom boot loader from sd-card
p/s : someday when I don't need this phone.. I'll kill it this way
If I'm lucky, I'll get to boot an unlocked bootloader.
Click to expand...
Click to collapse
Thanks a lot for the schematics & the technical insight. Maybe we can try something in this case..
:good:
blassom said:
Then I can put files in it's original stock rom to see if you can read the boot?
Click to expand...
Click to collapse
Dude, let's try something...
1- Grab a Micro-SD with at least 4GB
2- Format it to Fat32
3- Extract & copy all the files from the 672.180.41 SBF update to it.
4- Put it into the phone
5- Remove your SIM card
6- Plug the usb cable & connect to the PC.
7- Wait to see if it loads the MBM & try to flash again, using the same files that I mentioned earlier.
Did you understand? / Você entendeu?
what computer you have access?? linux?? or windows?
Yes
p34c3m4k3r said:
Thanks a lot for the schematics & the technical insight. Maybe we can try something in this case..
:good:
Dude, let's try something...
1- Grab a Micro-SD with at least 4GB
2- Format it to Fat32
3- Extract & copy all the files from the 672.180.41 SBF update to it.
4- Put it into the phone
5- Remove your SIM card
6- Plug the usb cable & connect to the PC.
7- Wait to see if it loads the MBM & try to flash again, using the same files that I mentioned earlier.
Did you understand? / Você entendeu?
Click to expand...
Click to collapse
Yes ok
Windowa
whirleyes said:
what computer you have access?? linux?? or windows?
Click to expand...
Click to collapse
Windows 8
Does "Yes ok" mean it worked or just that you will try?
I got very close to the stage you are; but reflashed with factory cable instead of deleting partitions. I did not have the balls to charge the battery directly.
Sent from my XT910 using xda premium
I'll try.
doutdes said:
Does "Yes ok" mean it worked or just that you will try?
I got very close to the stage you are; but reflashed with factory cable instead of deleting partitions. I did not have the balls to charge the battery directly.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
I'll try.
what was the result ?
did you succeed ?
did you fix your phone ?
Exactly the same problem.
xtam said:
what was the result ?
did you succeed ?
did you fix your phone ?
Click to expand...
Click to collapse
I believe I have the same problem although it was caused by a wrong step during installing the d-wiz rom. I own a GSM XT910 device and I formatted my main system with the boot menu manager without having copied first the ROM zip in my device (yeah i know i'm an idiot)!
Then when i rebooted I was greeted by the motorola "red eye" logo and then... nothing (no fastboot menu appears or any other menu). Nevermind how many times I have tried to reboot by pressing either "power"+"vol up"+"vol down" or just "power"+"vol up" with or without the factory cable the result is exactly the same: the boot stops after the motorola logo.
I have tried several methods as well as the aforementioned:
(1- Grab a Micro-SD with at least 4GB
2- Format it to Fat32
3- Extract & copy all the files from the 672.180.41 SBF update to it.
4- Put it into the phone
5- Remove your SIM card
6- Plug the usb cable & connect to the PC.
7- Wait to see if it loads the MBM & try to flash again, using the same files that I mentioned earlier.),
but no luck. The problem remains the same.
I have also tried this: http://forum.xda-developers.com/showthread.php?t=2198223 , but had no luck either. The device couldn't boot into fastboot.
Any other ideas?
Proud to announce that the last thread (http://forum.xda-developers.com/showthread.php?t=2198223) solved my problem after multiple times of pressing "power"+"vol up"+"vol down" en=ven after the logo appears and following the steps.
Hello people..
Anyone know how to get root access to this device?
Didn't find any guide about it...
Any help would be appreciated.
Best regards
JRGOFICIAL said:
Hello people..
Anyone know how to get root access to this device?
Didn't find any guide about it...
Any help would be appreciated.
Best regards
Click to expand...
Click to collapse
I DO!!!
No scam frlfrl. Read this carefully. Any cv1 device including this one is eligible to root. It's an LG X210 also known as cv1. So it's firmware is the same but it's a different carrier. The LG Aristo 2, LG Aristo 2+, LG K8+, and the LG Pheonix 4 are all cv1. Previously it was thought that only LG Aristo 2, 2+ and K8+ were the only cv1 devices, but now thanks to AustinGarrick1818, we have now relized that our cv1 TWRP can be used for the LG Pheonix 4 and of cource your LG K9!
I will post a root method soon for all of the cv1 devices.
NonStickAtom785 said:
I DO!!!
No scam frlfrl. Read this carefully. Any cv1 device including this one is eligible to root. It's an LG X210 also known as cv1. So it's firmware is the same but it's a different carrier. The LG Aristo 2, LG Aristo 2+, LG K8+, and the LG Pheonix 4 are all cv1. Previously it was thought that only LG Aristo 2, 2+ and K8+ were the only cv1 devices, but now thanks to AustinGarrick1818, we have now relized that our cv1 TWRP can be used for the LG Pheonix 4 and of cource your LG K9!
I will post a root method soon for all of the cv1 devices.
Click to expand...
Click to collapse
Already posted the method? If you already, could you send me the link? I am very happy to know that there is someone working to bring a root method and the TWRP to the LG K9 TV, I am a long time ago for answers. thank you!
one more here waiting for this guide!
@NonStickAtom785 please give a shout here when it's avaiable
Thanks!
CalangOMudo said:
Already posted the method? If you already, could you send me the link? I am very happy to know that there is someone working to bring a root method and the TWRP to the LG K9 TV, I am a long time ago for answers. thank you!
Click to expand...
Click to collapse
baga13 said:
@NonStickAtom785 please give a shout here when it's avaiable
Thanks!
Click to expand...
Click to collapse
Well since I don't have the device I'm going to need testers to tell me if it works or not.
Method 1:
1. Developer Options
The bootloader should be locked, but you can OEM unlock it in developer settings. Most everyone should know how but just in case goto Settings -> About and find Build Number. Click it 5-6 times and Developer Options should show up in settings.
Goto Developer Option and enable OEM Unlock and usb debugging.
2. ADB Drivers
If you already have adb drivers on your computer just restart your device and plug it into your PC. Open a command prompt in you adb folder and type in "adb devices". If you don't you will need to install ADB Drivers from another forum and do the same as everyone else. You will need to give authorization to USB Debugging once you type in adb devices. If it shows unauthorized then type in adb reboot fastboot. This should prompt that debugging authorization on screen. Click Allow and you device should reboot to fastboot mode. If this doesn't work goto Method B(Bottom of Post)
3. Fastboot
Fastboot should and most likely will come with the ADB Drivers. Instead of using adb we use fastboot commands. So type in fastboot devices to check that your device is connected. If it shows that it is connected then you can move on to the next step.
4. OEM Unlock
From the command prompt type "fastboot oem unlock" or "fastboot flash unlock". This will erase you data but once it's done you will need to do it again because the userdata partition and cache will be encrypted. Type "fastboot erase userdata" and "fastboot erase cache". Move on to step 5 if it works. If this doesn't then go to Method B.
5. Installing TWRP
Download this and install it by typing "fastboot flash recovery TWRP-3.2.3.0-cv1.img". If it works type "fastboot reboot recovery".
Method 2
Note: This is what might have to happen for TWRP to be installed
1. Basic Information
The fastboot partition might be encrypted, adb might not reboot to fastboot, and or fastboot isn't install TWRP.
2. Fix(ANOTHER NOTE: I'M NOT RESPONSIBLE FOR BRICKS)
Power off your phone. Boot into download mode by holding the Volume UP and plugging the device into your PC. You'll need LG UP, to install the Aristo Firmware. Theoretically the cv1 devices are the exact same build as one another just under different carrier names
and build numbers. So flashing the LMX210MAK10 firmware should fix it. Download it and flash it then go back to method 1 to try again.
If you have any questions or comment quote my method and let me know further issues.
Alguém conseguiu?
Darlisson said:
Alguém conseguiu?
Click to expand...
Click to collapse
Fiz o que sugeriram sobre dar flash no lg k9 tv de uma rom supostamente compat
Funcionou?
But there are some problems: The LMX210BMW is the only build that supports dual SIM.
cssobral2013 said:
But there are some problems: The LMX210BMW is the only build that supports dual SIM.
Click to expand...
Click to collapse
Editing above: nevermind the above post. According to LG website, the only builds of LMX210 that support dual SIM are: BMW, EMW, IMW, NMW, and YMW. The BMW we know that the bootloader is hardlocked. So, we need to test which other LMX210 builds aren't hardlocked.
Alguém conseguiu?
CalangOMudo said:
Fiz o que sugeriram sobre dar flash no lg k9 tv de uma rom supostamente compat
Click to expand...
Click to collapse
Deu certo?
Alguém aqui conseguiu instalar alguma ROM, ou ao mesmo fazer o bootloader no K9?
baga13 said:
Deu certo?
Alguém aqui conseguiu instalar alguma ROM, ou ao mesmo fazer o bootloader no K9?
Click to expand...
Click to collapse
Comigo não rolou, definativamente desisti.Ainda teve varias pessoas relatando que não inicializa no bootloader.Acho que o problemas ta nesse modelo com dois chips. Nunca consegui iniciazar no bootloader, simplesmente reinicia voltando pro sistema.Quase perdi o aparelho fazendo o flash da imagem que foi postada, tive que instalar imagem stock pra poder voltar a usar o aparelho.
Também desencanei
rodrigo.ultrazone said:
Comigo não rolou, definativamente desisti.Ainda teve varias pessoas relatando que não inicializa no bootloader.Acho que o problemas ta nesse modelo com dois chips. Nunca consegui iniciazar no bootloader, simplesmente reinicia voltando pro sistema.Quase perdi o aparelho fazendo o flash da imagem que foi postada, tive que instalar imagem stock pra poder voltar a usar o aparelho.
Click to expand...
Click to collapse
Pois é, eu tb desencanei de perder tempo tentando acessar o bootloader.
Para mim era algo relacionado a um bloqueio colocado pela operadora que vendeu o aparelho (no meu caso, Vivo), mas não tenho conhecimento técnico para afirmar se é isso ou o lance dos dois chips...
Se alguém tiver sucesso no processo ou dicas, manda aqui!
https://dianariyanto.com/custom-rom-lg-k9-lineage-os-15-oreo/
Arquivos TWRP
rodrig0128 said:
https://dianariyanto.com/custom-rom-lg-k9-lineage-os-15-oreo/
Click to expand...
Click to collapse
Valeu pelo link, Rodrigo.
Porém os arquivos TWRP linkados na postagem dentro desta postagem estão indisponíveis.
Você conseguiu baixá-los?
São estes aqui:
unsigned_twrp_lg-k9_temp.zip
signed_twrp_lg-k9.zip
Estou googlando atrás deles, até agora sem sucesso.
Caso consiga, posto aqui.
Obrigado!
Any news?
about the root
cssobral2013 said:
Editing above: nevermind the above post. According to LG website, the only builds of LMX210 that support dual SIM are: BMW, EMW, IMW, NMW, and YMW. The BMW we know that the bootloader is hardlocked. So, we need to test which other LMX210 builds aren't hardlocked.
Click to expand...
Click to collapse
i've tested the YMW, and it's hardlocked too.
I HAVE Asus ZenFone 4 Selfie (ZD553KL) WITH LAST OS OREO 8.1 UL-ASUS_X00LD_1-WW-15.0400.1903.508-user
I have unlocked the bootloader. Flashed twrp.img but my device doesnt ROOT WITH Magisk-v18.1(18100).zip AND BETA VERTION Magisk-v19.0.zip
Patch boot.img doesnt work WITH Magisk Manager 7.1.1
Flashing the patched boot img doesnt work on the latest build number. I've tried everything but nothing works. This is sad lol
ANY HELP TO ROOT MY DEVICE
THANK S
How to unlock Bootloader?
Android 7.1.1, device: zd553kl
I can't root to x00ld can anyone help?
SANNZINHOK said:
I can't root to x00ld can anyone help?
Click to expand...
Click to collapse
Just unlock your bootloader and patch boot.img of your rom with magisk
magisk will generate a patched boot.img file in download folder
reboot to fastboot and type with your phone connected: "fastboot flash boot patched_boot_filename.img"
working with and without TWRP in android 7, 8, 9 roms in zd553kl
if you have TWRP installed you can flash magisk.zip in TWRP
juliopolycarpo said:
Basta desbloquear seu bootloader e corrigir boot.img de sua rom com magisk
magisk irá gerar um arquivo boot.img corrigido na pasta de download
reinicie para fastboot e digite com seu telefone conectado: "fastboot flash boot patched_boot_filename.img"
trabalhando com e sem TWRP no android 7, 8, 9 roms em zd553kl
se você tiver o TWRP instalado, poderá atualizar o magisk.zi
nasasky39 said:
EU TENHO Asus ZenFone 4 Selfie (ZD553KL) COM LAST OS OREO 8.1 UL-ASUS_X00LD_1-WW-15.0400.1903.508-user
Já desbloqueei o bootloader. Piscou twrp.img, mas meu dispositivo não faz ROOT COM Magisk-v18.1 (18100).zip E VERSÃO BETA Magisk-v19.0.zip
O patch boot.img não funciona com o Magisk Manager 7.1.1
A atualização da img de inicialização corrigida não funciona no número de compilação mais recente. Já tentei de tudo mas nada funciona. Isso é triste kkkk
QUALQUER AJUDA PARA ROOT MEU DISPOSITIVO
OBRIGADO
Click to expand...
Click to collapse
CComo vcs desbloqueio o bootloader o App da Asus da erro de rede
Click to expand...
Click to collapse
I also accidently checke "Erase All before download".
Now SIM cards aren't recognized and WiFi isn't working properly. I can't go back to Global ROM, I can't update to ZUI 11.1 and unable to find a way to install TWRP and wipe cash and Dalvik. I tried another reflash an nothing changed.
Help! Please!
Global ROM is a manually modified rom made from the sellers, and so it's not available to the public.
In regards of the erased IMEI do you have a backup of the efs folder? If not i would contact the seller to try and organize a repair, unfortunately we can't talk about changing IMEI here, because its illegal in many states.
You can try to search on 4pda for possible methods, it should be the same for all snapdragon models, just be sure to have the original box with the imeis written in it
Ricky0178 said:
Global ROM is a manually modified rom made from the sellers, and so it's not available to the public.
In regards of the erased IMEI do you have a backup of the efs folder? If not i would contact the seller to try and organize a repair, unfortunately we can't talk about changing IMEI here, because its illegal in many states.
You can try to search on 4pda for possible methods, it should be the same for all snapdragon models, just be sure to have the original box with the imeis written in it
Click to expand...
Click to collapse
I don't have any backup, and I have my IMEI and everything in the box. Now I just need the QCN file of any Lenovo Z5 Pro GT, and I'll be able to recover everything.
If you have Lenovo Z5 Pro GT, you can export the QCN file usin QFIL, change your IMEI infos (so you have nothing to worry about) and then upload it for me, and you will save me, and I will be thankful to you for the rest of my life.
I have same problem [emoji58]
please help me to fix it...
Sent from my Pixel 2 XL using Tapatalk
Olá, sou do Brazil. Eu acho que tenho a solução para seu problema, coloque o celular em modo fastboot, pegue os arquivos da pasta da ROM 10.5.340 > persist.img e vbmeta.img e coloque na pasta do ad minimal fast boot, abra o programa e digiten esses comandos:
Fastboot devices - para identificar o aparelho
Depois
Fastboot flash persist persist.img
E depois
Fastboot flash vbmeta vbmeta.img
Depois reinicie o aparelho. Pronto, problema resolvido.
LucasSilva25 said:
Olá, sou do Brazil. Eu acho que tenho a solução para seu problema, coloque o celular em modo fastboot, pegue os arquivos da pasta da ROM 10.5.340 > persist.img e vbmeta.img e coloque na pasta do ad minimal fast boot, abra o programa e digiten esses comandos:
Fastboot devices - para identificar o aparelho
Depois
Fastboot flash persist persist.img
E depois
Fastboot flash vbmeta vbmeta.img
Depois reinicie o aparelho. Pronto, problema resolvido.
Click to expand...
Click to collapse
English??
LucasSilva25 said:
Olá, sou do Brazil. Eu acho que tenho a solução para seu problema, coloque o celular em modo fastboot, pegue os arquivos da pasta da ROM 10.5.340 > persist.img e vbmeta.img e coloque na pasta do ad minimal fast boot, abra o programa e digiten esses comandos:
Fastboot devices - para identificar o aparelho
Depois
Fastboot flash persist persist.img
E depois
Fastboot flash vbmeta vbmeta.img
Depois reinicie o aparelho. Pronto, problema resolvido.
Click to expand...
Click to collapse
I tried your solution
only wifi works
sim not works
hey mate i have the same problem that you have, maybe we can help eachother? i have the qcn the file that we need, i just dont know how to fix it, how to rewrite my imeis to the qcn, do you know how?
hello people. first i'm sorry for my english. i always went to the site but the first time i create an account here this and my first post i'm sorry if i did something or if it is in the wrong place. I have the device listed in the title I would like to know if there is any custom recovery for it and especially some custom rom or if something is being developed for this device. since already thank you very much
Todo sobre TWRP y ROM del Moto e6s. All about TWRP and ROM of the Moto e6s
In spanish
¡Hola! Yo tengo el mismo dispositivo y por mucho que he buscado no hay ninguna versión de TWRP compatible, con respecto a la ROM, puedes buscar alguna GSI cómo está: https://github.com/phhusson/treble_experimentations/releases/tag/v222
Debes de descargar la versión que dice "arm32_binder64-ab". Hay varias versiones, una con GApps, otra sin las GApps y otra en versión "Go".
También está está de Lineage OS en versión GSI: https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
En esta debes de descargar la versión que dice: "treble_a64_bvS"
Aquí está el foro con todas las GSI que hay que talvez te funcionen: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Solo debes de fijarte de descargar la que diga "a64 bv" o "a64 AB", o "arm32_binder64_AB" ya que son las compatibles con este dispositivo, tu eliges si quieres una versión son GApps o sin ellas. Recomiendo descargar las versiones de Android 10 ya que son más estables y al este dispositivo ser de gama baja talvez sirvan mejor.
Por lo que he leido, la mayoría de GSI se basan en la del primer enlace que te di, así que recomiendo probar esa primero para ver si funciona.
Yo no sé si estas versiones funcionarán ya que no las he probado, ya que por más seguridad estoy esperando a que salga una versión de TRWP así me evito posibles errores y es más facil. Así que no me hago cargo por daños ocasionados al celular o por quedar inutilizable.
In english:
Hello! I have the same device and as much as I have searched there is no TWRP compatible version, regarding the ROM, you can look for some GSI how it is: https://github.com/phhusson/treble_experimentations/releases/tag/v222
You must download the version that says arm32_binder64-ab. There are several versions, one with GApps, one without GApps and one in "Go" version.
There is also a GSI version of Lineage OS: https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
In this one you must download the version that says: treble_a64_bvS
Here is the forum with all the GSIs that might work for you: https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Just make sure you download the one that says "a64 bv" or "a64 AB", or "arm32_binder64-AB" as they are compatible with this device, you choose if you want a GApps version or not. I recommend downloading the Android 10 versions because they are more stable and this device being low-end may serve better.
From what I've read, most GSIs are based on the one in the first link I gave you, so I recommend to try that one first to see if it works.
I don't know if these versions will work since I haven't tried them, since for more security I'm waiting for a version of TRWP to come out so I can avoid possible errors and it's easier. So I don't take any responsibility for damages caused to the cell phone or for being unusable.
Any news about TWRP for Moto E6s?
waiting too.
[QUOTE = "vinicius_braga, publicación: 84413777, miembro: 3395422"]
¿Alguna noticia sobre TWRP para Moto E6s?
[/CITAR]
at the moment everything remains the same, in fact Motorola introduced a new device called "moto e6i" but I do not understand why they do not release the bootloader of previous devices.
Try twrp for moto e6plus - its copy e6s. unlock i am try and unlock e6s, bad english i am from ukraine)
we'll have more twrp development once more of us can unlock our bootloaders without paying for dongles
luridphantom said:
we'll have more twrp development once more of us can unlock our bootloaders without paying for dongles
Click to expand...
Click to collapse
i am unlock moto e6s very simple in fastboot and i dont flash recovery i am dont know adress for spft. fastboot still not flash recovery, lk, etc, but spft now flash lk vbmeta but in scatter not partition recovery. sorry my english. Now i am search info how flash twrp. i am edit lk in hex nj remove message orange state and 5 sec and flash lk well work. How ve know adress partition recovery?
P/ C/ and i flash vbmeta from post root e6+ (empty vbmeta)
severagent007 said:
i am unlock moto e6s very simple in fastboot and i dont flash recovery i am dont know adress for spft. fastboot still not flash recovery, lk, etc, but spft now flash lk vbmeta but in scatter not partition recovery. sorry my english. Now i am search info how flash twrp. i am edit lk in hex nj remove message orange state and 5 sec and flash lk well work. How ve know adress partition recovery?
P/ C/ and i flash vbmeta from post root e6+ (empty vbmeta)
Click to expand...
Click to collapse
wait how did you unlock through fastboot? mine cant do it
i'd get the boot/recovery from the firmware files here instead of playing with spft, only use that if you really cant get fastboot to work. the scatter file will be in the firmware files as well
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
luridphantom said:
wait how did you unlock through fastboot? mine cant do it
i'd get the boot/recovery from the firmware files here instead of playing with spft, only use that if you really cant get fastboot to work. the scatter file will be in the firmware files as well
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
i am have firmware and scatter but in scatter not info about recovery
severagent007 said:
i am have firmware and scatter but in scatter not info about recovery
Click to expand...
Click to collapse
might not have a recovery since its a/b partition, will need to double check after work
luridphantom said:
might not have a recovery since its a/b partition, will need to double check after work
Click to expand...
Click to collapse
Yes patching boot and flash by spft! Ypdate magisk.apk and now i am have root))) now i want flash twrp by flashfire
Слава Украине!)))))
severagent007 said:
Yes patching boot and flash by spft! Ypdate magisk.apk and now i am have root))) now i want flash twrp by flashfire
Слава Украине!)))))
Click to expand...
Click to collapse
can you create twrp with no recovery though?
glad you got root! so what are your steps to unlock boot loader? I'm still stuck there. fast boot doesn't allow me to run the oem unlock command. or did you just patch boot and flash with spft without unlocking the boot loader?
stay safe over there and slava ukraini!
luridphantom said:
can you create twrp with no recovery though?
glad you got root! so what are your steps to unlock boot loader? I'm still stuck there. fast boot doesn't allow me to run the oem unlock command. or did you just patch boot and flash with spft without unlocking the boot loader?
stay safe over there and slava ukraini!
Click to expand...
Click to collapse
recovery not partition, recovery in boot! i am repack patched magisk stok boot and replace files from twrp e6+ - twrp work, but flash in slot b( and system boot in slot a! i am search fix for this. Root magisk work in system. I want work twrp. Instruction post I'll write when I'm at home near the computer)
luridphantom said:
can you create twrp with no recovery though?
glad you got root! so what are your steps to unlock boot loader? I'm still stuck there. fast boot doesn't allow me to run the oem unlock command. or did you just patch boot and flash with spft without unlocking the boot loader?
stay safe over there and slava ukraini!
Click to expand...
Click to collapse
[email protected] said:
hello people. first i'm sorry for my english. i always went to the site but the first time i create an account here this and my first post i'm sorry if i did something or if it is in the wrong place. I have the device listed in the title I would like to know if there is any custom recovery for it and especially some custom rom or if something is being developed for this device. since already thank you very much
Click to expand...
Click to collapse
Moto E6S XT-2053-1 Unlock Bootloader, Disable Verity, ROOT Magisk, TWRP
I am perfom this :cautious: Sorry for my english, I am from Ukraine :cowboy: Download archive! We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer. In the smart, turn on the developers menu, in...
forum.xda-developers.com
just followed the link instructions and it works!! bootloader unlocked and root achieved