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.
(~EN)
Hey,
I have an Atrix 4G from AT&T (and a Brazilian one as well, in witch I haven't tried the procedure yet) and I installed the CM 10 in it. But I am having a lot of problems with the camera (slow movie and camera stops all the time), with the fingertip, and sometimes the mobile gets really hot. So, I am a bit tired about test different ROMs and I would like to put the original one (motoblur) back. I got this one that is supposed to be the official one by AT&T (is it correct?)
<1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012>
but all the time that I try to install, the installation abort by itself and I have no idea why. I can install all the CMs but I can't install the olympus.
Does someone have the original ROM or knows why I am having this problem? I've rooted my MB860 and I am installing from the SDCard. Before installing, I am doing the full wipe (include cache and anything else).
Thank you
(PT-BR)
Olá,
Eu tenho um atrix 4g da AT&T (e um brasileiro que eu ainda não tentei o procedimento) e eu instalei o CM 10 nele. Estou tendo vários problemas, principalmente com a câmera, leitor de impressão digital, aquecimento, etc. Cansei dessas coisas e quero o Motoblur novamente, ainda que seja mais lento. Eu baixei uma ROM que, aparentemente, é a oficial da AT&T (cujo nome está descrito acima). O meu problema é que eu tento instalar essa ROM e a instalação para por si só.
Alguém sabe o porquê deste problema e se aquela ROM é mesmo a oficial?
Eu estou instalando pelo sdcard e antes eu faço full wipe e limpo tudo, inclusive a cache.
Obrigado
thats a sbf file. if you're trying to flash it via cwm, you don't belong using it. go find a fruitcake rom, much safer for someone who thinks sbfs are meant for cwm flashing.
not trying to sound rude, but giving advice to keep you from destroying your device.
Sent from my MB886 using xda app-developers app
marcelomirbas said:
(~EN)
Hey,
I have an Atrix 4G from AT&T (and a Brazilian one as well, in witch I haven't tried the procedure yet) and I installed the CM 10 in it. But I am having a lot of problems with the camera (slow movie and camera stops all the time), with the fingertip, and sometimes the mobile gets really hot. So, I am a bit tired about test different ROMs and I would like to put the original one (motoblur) back. I got this one that is supposed to be the official one by AT&T (is it correct?)
<1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012>
but all the time that I try to install, the installation abort by itself and I have no idea why. I can install all the CMs but I can't install the olympus.
Does someone have the original ROM or knows why I am having this problem? I've rooted my MB860 and I am installing from the SDCard. Before installing, I am doing the full wipe (include cache and anything else).
Thank you
(PT-BR)
Olá,
Eu tenho um atrix 4g da AT&T (e um brasileiro que eu ainda não tentei o procedimento) e eu instalei o CM 10 nele. Estou tendo vários problemas, principalmente com a câmera, leitor de impressão digital, aquecimento, etc. Cansei dessas coisas e quero o Motoblur novamente, ainda que seja mais lento. Eu baixei uma ROM que, aparentemente, é a oficial da AT&T (cujo nome está descrito acima). O meu problema é que eu tento instalar essa ROM e a instalação para por si só.
Alguém sabe o porquê deste problema e se aquela ROM é mesmo a oficial?
Eu estou instalando pelo sdcard e antes eu faço full wipe e limpo tudo, inclusive a cache.
Obrigado
Click to expand...
Click to collapse
Evite ao máximo flashear sbf no atrix da AT&T, pois pode dar hard-brick, use os fruitcakes (zips com a rom oficial). Já no brasileiro, use o rsd lite e flasheie o 2.3.6 oficial do brasil.
Try to not flash sbf on AT&T Atrix, because it can hard brick, use the fruitcakes instead (zips with official rom). On the brazilian atrix, use the rsd lite and flash the brazil official 2.3.6.
LimaBEERRE said:
Evite ao máximo flashear sbf no atrix da AT&T, pois pode dar hard-brick, use os fruitcakes (zips com a rom oficial). Já no brasileiro, use o rsd lite e flasheie o 2.3.6 oficial do brasil.
Try to not flash sbf on AT&T Atrix, because it can hard brick, use the fruitcakes instead (zips with official rom). On the brazilian atrix, use the rsd lite and flash the brazil official 2.3.6.
Click to expand...
Click to collapse
I've also tried to use the .zip file. But I've gotten the same problem. But, does is change, even if inside the .zip package there is a .sbf? Does someone have a link for the download of that (fruitcakes and brazilians official roms as well)? I tried on the motorola's webpage but I couldn't find anything.
Eu tenho tentado com os .zip também mas tenho sempre o mesmo problema citado. Mas existe alguma diferença, mesmo havendo um arquivo .sbf dentro do pacote zip? Alguém teria o link para baixar as rooms oficiais, tanto a da AT&T (fruitcakes, como informado) quanto as brasileiras?
Thanks
Obrigado
das8nt.com/downloads
Sent from my MB886 using xda app-developers app
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.
Hi!
Today I unlocked bootloader and tried to root the phone. After flashing Magisk patched boot.img phone did boot but touch screen did not work. Me being silly, tried different things and right now phone doesn't boot. I can still get to bootloader and recovery. Is there any way for me to flash full stock rom to fix that?
I know I was stupid.
Hoping that somebody can help me,
mectax
Try https://support.motorola.com/uk/en/...oto-g-family/moto-g8-power/documents/MS140571 see if it helps
pamplinas said:
Try https://support.motorola.com/uk/en/...oto-g-family/moto-g8-power/documents/MS140571 see if it helps
Click to expand...
Click to collapse
Thank you very much, I'll give this a try tomorrow!
EDIT: PROBLEM SOLVED - Used Lenovo's Rescue and Smart Assistant
pamplinas said:
Try https://support.motorola.com/uk/en/...oto-g-family/moto-g8-power/documents/MS140571 see if it helps
Click to expand...
Click to collapse
Will this rescue a hard bricked device??
If the touchscreen didn't work then that usually means you flashed a different version of the kernel / signed differently. If you can get the stock boot.img and flash it...it should recover itself also.
Adge40 said:
Will this rescue a hard bricked device??
Click to expand...
Click to collapse
Any info on this please?
darko454 said:
Any info on this please?
Click to expand...
Click to collapse
Hard bricked as in no bootloader or can you get to the bootloader. If you can't get to the bootloader does a computer recognize anything in the device manager when its plugged in?
I was having issue with google services on my new phone that i got from Amazon. So I did factory reset few times but still having issue so i thought flashig might help and i used Mototola tool Rescue and smart assistant and found correct version of moto g8 power lite XT2055-2. But after flashing my phone just hard brick. No power on, not going to recover model, don't charge when plgged in and don't even recognised by laptop when i plug in. The only thing i can see when plug into laptop or power source is red tiny light whic you normally get while charging. other wise phone is dead. I tried SP flash tool but got error as soon as click download. And error is ;
ERROR: STATUS_BROM_CMD_SEND_DA_FAIL_(OxC0060003)
Can somebody please help. I did eevn used for a single day. I bought it open box like new.
coolarun1980 said:
Eu estava tendo problemas com os serviços do Google no meu novo telefone que recebi da Amazon. Então, eu fiz a redefinição de fábrica algumas vezes, mas ainda com problemas, então pensei que o flashig poderia ajudar e usei a ferramenta Mototola Rescue e o assistente inteligente e encontrei a versão correta do moto g8 power lite XT2055-2. Mas depois de piscar meu telefone apenas tijolo duro. Não liga, não vai recuperar o modelo, não carrega quando conectado e nem é reconhecido pelo laptop quando eu conecto. A única coisa que posso ver quando conecto o laptop ou a fonte de alimentação é uma pequena luz vermelha que você normalmente obter durante o carregamento. outro telefone sábio está morto. Eu tentei a ferramenta flash SP, mas recebi um erro assim que cliquei em download. E o erro é;
ERRO: STATUS_BROM_CMD_SEND_DA_FAIL_(OxC0060003)
Alguém pode por favor ajudar. Eu eevn usado por um único dia. Comprei caixa aberta como nova.
Click to expand...
Click to collapse
OLÁ AMIGO ESTOU COM O MESMO PROBLEMA MEU APARELHO É O MOTO G8 POWER NAO CONSIGO ENTRAR NO BOOTLOADER NAO CARREGA QUANDO CONECTADO NO CARREGADOR NEM O PC RECONHECE ELE NAO LIGA, VOCE CONSEGUIU RESOLVER OU ALGUEM PODE ME AJUDAR?
I was researching how to root this cell phone, I only find complex ways that don't seem very safe to me, if anyone can help me with this I would appreciate it, I already have unlocked bootloader, I don't want to have my phone bricked
you can try this tutorial。
[RMX2202] Realme GT 5G (UI2.0 & UI3.0) - ALL ROOT
forum.xda-developers.com
worked, thank you. for those who are going to try, use the twrp11 file even though you are on android 12, the android 12 file does not enter twrp
Let's face it! not work.
I fave a stupid new phone, and by an accident i make upgrade, now i have UI3 instead of UI2.
NOW i fave Factory version RMX2202domestic_11_C.15_20220311****************
It seems First version is was RMX2202domestic_11_A.14_20210410**************
I read all from this site, nothing work to UNLOCK BOOTLOADER; this is first think need to do.
after command: adb reboot bootloader , phone reboot and apears some china chars for 1{ONE) second, and reboot again in normal mode.
How to work FASTBOOT command if you are not in bootloader??
I think first step is to run In.depth / deep testing apk, but i can't install any version that i find.
APP WITH SAME SIGNATURE ALREADY INSTALED.
If i falow strait path to download DEEP TESTING APK i finish in baido ****ing com.
I see good peoples here, some one have new in.depth / deep testing apk for this domestic version?! with another SIGNATURE?
I whant to change my rom to GDPR or INDIAN.... Android auto not connect to car, even GOOGLE PLAY SERVICES is seems not work.
OR same chinese people to try to download real in.depth/deep testing apk from baido.com
cferoiu said:
Vamos encarar! não funciona.
Eu gosto de um novo telefone estúpido e, por acidente, faço uma atualização, agora tenho UI3 em vez de UI2.
AGORA eu gosto da versão de fábrica RMX2202domestic_11_C.15_20220311****************
Parece que a primeira versão é RMX2202domestic_11_A.14_20210410****************
Li tudo deste site, nada funciona para DESBLOQUEAR BOOTLOADER; isso é primeiro acho que precisa fazer.
após o comando: adb reboot bootloader , phone reboot e aparece alguns caracteres da china por 1{ONE) segundo, e reinicie novamente no modo normal.
Como trabalhar o comando FASTBOOT se você não estiver no bootloader??
Acho que o primeiro passo é executar o apk In.depth/deep testing, mas não consigo instalar nenhuma versão que encontro.
APP COM A MESMA ASSINATURA JÁ INSTALADO.
Se eu falow strait path para baixar o DEEP TESTING APK eu termino em baido ****ing com.
Eu vejo gente boa aqui, alguém tem novo apk in.depth / deep testing para esta versão doméstica?! com outra ASSINATURA?
Eu quero mudar minha rom para GDPR ou INDIAN.... Android auto não conecta ao carro, mesmo GOOGLE PLAY SERVICES parece não funcionar.
OU mesmo povo chinês para tentar baixar o apk real in.depth/deep testing de baido.com
Click to expand...
Click to collapse
deptestin apk doesn't work on RUI 3.0 android 12, you need to revert to android 11, you will succeed in unlocking bootloader