Razr xt910 morto apos tentativa de atualização - Motorola Droid RAZR

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.