This has been going on for a while now. I gave up on the phone completely. When the phone turns on, I see motorola dual core screen, then I see the moto animation with the little white circles coming around it, at the end of that animation it freezes. I am no able to get into my phone at all. I have tried RSD lite, I have tried Mythtools, I have tried adb sideload MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA, I have tried everything I can think of. Can someone please talk to me and help me get through this? I am using a ****ty ZTE phone, I am so sick of it. Please help me.
What did you do to cause it?
Sent from my PACMAN MATRIX HD MAXX
Nothing.
deeje00 said:
What did you do to cause it?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I had actually never done anything as far as programming to it, no flashing, no rooting, no nothing. I dropped it a few weeks prior, the screen cracked, but it wasn't bad and worked perfectly after that. Then one day it just started bootlooping. I can get into everything like fastboot and all that, the battery holds a charge because I can unplug it in these menus, idk what to do here. fastboot is in low battery mode, and I cannot get to a charge battery screen. it just bootloops or I can let it sit in recovery or fastboot, after a few hours it will say battery ok.
Just reflash the stock rom in fastboot mode with mythtools
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
PaintballerAlex07 said:
Just reflash the stock rom in fastboot mode with mythtools
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
I have been trying, I can't because the battery is low. I get the Battery low in AP fastboot. :S
Shaneofgamestop said:
I have been trying, I can't because the battery is low. I get the Battery low in AP fastboot. :S
Click to expand...
Click to collapse
You're about to low battery brick yourself. Get a factory cable (or make your own) and you'll be able to flash with a low battery. Factory cable powers the phone directly from USB, skipping the battery altogether. Can actually run some moto phones without a battery with these cables. Google is your friend.
skeevydude said:
You're about to low battery brick yourself. Get a factory cable (or make your own) and you'll be able to flash with a low battery. Factory cable powers the phone directly from USB, skipping the battery altogether. Can actually run some moto phones without a battery with these cables. Google is your friend.
Click to expand...
Click to collapse
Skeevy, thanks for the reply, unfortunately I don't have a factory cable, I have found this solution online. Google surely was my friend, hours and hours and days (continuing as we speak) of google later, I am no closer to a resolution. :/ I have an AC charger at home that will EVENTUALLY get it charged up enough to say battery ok.
I guess I will wait til I get home, lol, I am a dumbass, I just spliced the cable I did have, red and black, screwed it onto the battery posts on the phone, phone came on, went into fastboot before I realized that this was worthless, as I have to have the phone plugged into my pc in order to run the fastboot commands. lol. smmfh. I have given up on this phone for the most part, I would REALLY like to have it working again, I am fairly certain I had ran through the fastboot commands in the past and didn't get anywhere. I am going to give it another shot though.
Shaneofgamestop said:
Skeevy, thanks for the reply, unfortunately I don't have a factory cable, I have found this solution online. Google surely was my friend, hours and hours and days (continuing as we speak) of google later, I am no closer to a resolution. :/ I have an AC charger at home that will EVENTUALLY get it charged up enough to say battery ok.
I guess I will wait til I get home, lol, I am a dumbass, I just spliced the cable I did have, red and black, screwed it onto the battery posts on the phone, phone came on, went into fastboot before I realized that this was worthless, as I have to have the phone plugged into my pc in order to run the fastboot commands. lol. smmfh. I have given up on this phone for the most part, I would REALLY like to have it working again, I am fairly certain I had ran through the fastboot commands in the past and didn't get anywhere. I am going to give it another shot though.
Click to expand...
Click to collapse
You might have to wipe your data and sdcard in fastboot mode if you were running a custom rom first. I've had that issue before -- completely install a system with fastboot only to boot loop. solution is "fastboot -w" if that's the case, maybe even a fastboot erase or two.
skeevydude said:
You're about to low battery brick yourself. Get a factory cable (or make your own) and you'll be able to flash with a low battery. Factory cable powers the phone directly from USB, skipping the battery altogether. Can actually run some moto phones without a battery with these cables. Google is your friend.
Click to expand...
Click to collapse
Can you tell me what I need to type into my command prompt for fastboot when I get to battery ok?
C:\Users\james whittle>fastboot flash boot "C:\Users\james whittle\Desktop\Myth
Tools - AHD\MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_B
uildA.xml.zip"
sending 'boot' (30720 KB)...
OKAY [ 2.380s]
writing 'boot'...
Battery Low!!
FAILED (remote failure)
skeevydude said:
You might have to wipe your data and sdcard in fastboot mode if you were running a custom rom first. I've had that issue before -- completely install a system with fastboot only to boot loop. solution is "fastboot -w" if that's the case, maybe even a fastboot erase or two.
Click to expand...
Click to collapse
I actually do not have an SD card in the phone. I did what you recommended in another post fastboot erase data and cache. I am new to the droid world. I tried for days a couple months ago. Now I am back at it. :S I am so sick of this, the Atrix HD was like the best phone I have ever owned. That thing rocks.
Buy a factory cable man. It's a saver if you mess up.
Sent from my PACMAN MATRIX HD MAXX
Also, adb sideload MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip always returns opening, verifying, installation aborted. :/ I have one at the house I can use when I get there. When I reflash with mythtools there is no change. Says it finishes then goes back to boot loop.
Shaneofgamestop said:
Also, adb sideload MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip always returns opening, verifying, installation aborted. :/ I have one at the house I can use when I get there.
Click to expand...
Click to collapse
You can't sideload a fastboot zip.....
About the sd, I was referring to the internal sd card, not external. If its not setup properly when changing from 4.2 to 4.1 you'll boot loop. Formatting userdata fixes that and allows the rom's init scripts to set it up on first boot properly.
Only time external matters is if your one of the weirdos that does the internal/external swap.
skeevydude said:
You can't sideload a fastboot zip.....
About the sd, I was referring to the internal sd card, not external. If its not setup properly when changing from 4.2 to 4.1 you'll boot loop. Formatting userdata fixes that and allows the rom's init scripts to set it up on first boot properly.
Only time external matters is if your one of the weirdos that does the internal/external swap.
Click to expand...
Click to collapse
lol, I was doing that from the recovery menu, I didn't know I couldn't sideload it. I did fastboot erase userdata earlier, said it completed. I have wiped this phone in like every way i could find online, actually the motorola logo that comes up now is different from my original one, It says the dual core technologies, which it did not say before it bricked and I tried to put a new firmware on it, I think I was able to successfully get through RSD lite a long time ago and it did that, but still just stops on the second motorola logo screen, after the animation.
Shaneofgamestop said:
lol, I was doing that from the recovery menu, I didn't know I couldn't sideload it. I did fastboot erase userdata earlier, said it completed. I have wiped this phone in like every way i could find online, actually the motorola logo that comes up now is different from my original one, It says the dual core technologies, which it did not say before it bricked and I tried to put a new firmware on it, I think I was able to successfully get through RSD lite a long time ago and it did that, but still just stops on the second motorola logo screen, after the animation.
Click to expand...
Click to collapse
Simplest fix is just download the Mex Retail fastboot and flash everything except gpt_main0.bin, of course wiping everything that can be wiped. I do the same thing when I brick, only I use Bell ICS (lapdock user here).
skeevydude said:
Simplest fix is just download the Mex Retail fastboot and flash everything except gpt_main0.bin, of course wiping everything that can be wiped. I do the same thing when I brick, only I use Bell ICS (lapdock user here).
Click to expand...
Click to collapse
Where can I download Mex retail fastboot? And how do I use it? Sorry, and thanks for everything man.
Shaneofgamestop said:
Where can I download Mex retail fastboot? And how do I use it? Sorry, and thanks for everything man.
Click to expand...
Click to collapse
The thread with all you need. Link is about halfway in.
Make sure you download and use the fastboot linked in that post, any other fastboot executable will fail for us.
skeevydude said:
The thread with all you need. Link is about halfway in.
Make sure you download and use the fastboot linked in that post, any other fastboot executable will fail for us.
Click to expand...
Click to collapse
Dude, I don't mean to be a bother, but I don't understand all this, like, I have a couple fastboot files on my pc, should I delete them all or?
also, are these what i need?
File Type: zip kernel-flash.zip - [Click for QR Code] (5.55 MB, 309 views)
File Type: zip recovery-flash.zip - [Click for QR Code] (6.62 MB, 486 views)
Shaneofgamestop said:
Dude, I don't mean to be a bother, but I don't understand all this, like, I have a couple fastboot files on my pc, should I delete them all or?
also, are these what i need?
File Type: zip kernel-flash.zip - [Click for QR Code] (5.55 MB, 309 views)
File Type: zip recovery-flash.zip - [Click for QR Code] (6.62 MB, 486 views)
Click to expand...
Click to collapse
http://sbf.droid-developers.org/dinara/list.php
use the last one, skip flahing gpt_main0.bin
anyways, extract that zip
copy fastboot executable into extracted folder
open up the xml file
Code:
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="7DDA3A0C79737F7980373E25C028F26D" />
<step operation="[B]flash[/B]" partition="[B]sbl1[/B]" filename="[B]sbl1.mbn[/B]" MD5="497EADC7B6A9C37CE7E828E9CDCB2383" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="E892D0369C886C4D8C4C4772A3035739" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="D60717471D584B8FAD41365730512256" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="F44809F0BE9CDF883D007DB2041DCEDA" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="F41F0F575D52B390D576A89BC773DDB0" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="DA04D26F5C34F2A2F7FCF14003E65BF7" />
<step operation="reboot-bootloader" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="ABBD3EE4CB254F620DEDF9A1DB337FF1" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="35F8FBF53B46410B495357EA5CC4225D" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="6463DC057ABF889F3B83A4D3DA4CDD1E" />
<step operation="flash" partition="boot" filename="boot.img" MD5="E7A95F72340F2F3E03EC2E1A4050FCAC" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="FF8CDD711906306D3F876FC69AE0D192" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="C5D0968CC8E8A2003CCDAE4D19F29031" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="FFD273DED204C4388F6907AE0ECDE130" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="14FDDA83BD7AC9DD5B829962A9F4C6BA" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
and go down the line flashing everything the fastboot flashes. I bolded the first fastboot command above, which would be "fastboot flash sbl1 sbl1.mbn" -- fastboot command partition filename is the syntax used here. This is what MythTools does automatically. Skip the oem commands and the reboot-bootloader commands, do the erase ones (fastboot erase tombstones for example)
fastboots on PC -- doesn't matter as long as you execute the ones located on Batakang Ftp (first link in the fastboot guide)
those zips -- only for noobs that can't figure out "fastboot flash recovery recovery.img" or "fastboot flash boot boot.img"....
Can I fix this phone or is it bricked?
Not sure if this is the right forum to post this particular question but I assume my problem is more android specific than model specific. I have an Atrix HD which gets stuck on the AT&T logo when booting. It had been acting up for a little while before it did this. Just about any app I would try to open would either not open at all or it would start to open and then pop right back to the home screen. I would have to restart the phone to get an app to open, but they would still be unstable and not work for long.
I have researched for hours on end over the past week and tried just about everything I could. One of the problems is I'm a complete noob when it comes to tinkering with Android. The phone is not rooted and the bootloader I assume is locked since I haven't played with anything. Stock ROM running 4.1.1. I added very few apps on the phone maybe 3-4 over the 3 years I've had it. I have wiped the cache and have done the factory reset from recovery, but still no luck.
I have tried to use RSD Lite and Minimal ADB and Fastboot to see if I could download the stock ROM online and then use one of those to push it to the phone, but the phone doesn't appear in the device window in RSD Lite, and when I type "adb devices" at the CMD prompt in ADB the list of devices attached is empty unless I choose the option in recovery to "apply update using ADB" in which case it says "TA2490D74Q sideload". I downloaded the updated drivers from Motorola. I was going to try and use MythTools, but I thought I read somewhere that the bootloader needed to be unlocked to use it. Can I use MythTools on a completely stock phone?
I don't know if USB debugging is enabled. I don't remember going into the developer options and doing so myself. Is there a way to tell through either recovery or fastboot?
I have seen countless websites online say that phones stuck in bootloops are considered "soft bricked" and for the most part should be fixable, but for someone whose phone is not rooted, and bootloader not unlocked, is that really the case? I am long overdue for an upgrade, and ordinarily would just do that, but the problem is I am currently out of the U.S. and phones where I am now are ridiculously priced compared to the U.S. so I would prefer it if I could at least fix this phone until I can get back and get a new one.
Sorry for the length. I wanted to add as much useful info as I could. Any suggestions/help would really be appreciated. This s&%t can be really frustrating when everything you try turns out to be a dead end.
Wanting to return stock from a previous custom rom I formatted the phone via TWRP
I put the phone in fastboot mode, the connection to the PC USB, boot RSDLite and load the rom, launch the command of flash that will stop after a few seconds ... with the words FAILED FLASHING PROCESS. UNKNOW FASTBOOT COMMAND
in the box to the left, the phone is not recognized.
I tried aggionare Motorola drivers, I tried to install the new version of RSDLite 5.7, I restarted my pc, I tried anch with another pc with win xp .... nothing to do .....
in the phone there is neither the TWRP recovery nor the stock
What can I do?
panic .....
solved forgot to erase: the line <step operation = "getvar" var = "max-download-size" />
you can delete, thanks
toroloco you "is" loco as hell:laugh:
Glad you are sorted out
toroloco73 said:
panic .....
solved forgot to erase: the line <step operation = "getvar" var = "max-download-size" />
you can delete, thanks
Click to expand...
Click to collapse
I accidentally blocked the bootloader when there was no rom installed in the system, now I am without OS and I have the phone blocked from the bootloader I cannot enter the system and check the unlock box "oem" to flash the system again, I always get the same error * permision denied * I have the motorola code to unlock the bootloader but when entering it by fastboot it tells me to check the oem settings. which I can't do .. it doesn't go into the recovery stock either. and if I flash twrp it returns to fastboot, if I give start it sends a message "the system is corrupt and it won't start apparently the partitions are deleted or corrupted, but if it enters fastboot .. any ideas?
Greetings!
LMSA not working.
HELP PLEASE!!!
Yayo70136 said:
I accidentally blocked the bootloader when there was no rom installed in the system, now I am without OS and I have the phone blocked from the bootloader I cannot enter the system and check the unlock box "oem" to flash the system again, I always get the same error * permision denied * I have the motorola code to unlock the bootloader but when entering it by fastboot it tells me to check the oem settings. which I can't do .. it doesn't go into the recovery stock either. and if I flash twrp it returns to fastboot, if I give start it sends a message "the system is corrupt and it won't start apparently the partitions are deleted or corrupted, but if it enters fastboot .. any ideas?
Greetings!
LMSA not working.
HELP PLEASE!!!
Click to expand...
Click to collapse
have you tried starting recovery and adb sidloading an update?
kewlzter said:
have you tried starting recovery and adb sidloading an update?
Click to expand...
Click to collapse
Hi, I don't really know how to do that you mention ... if it's with twrp I'll tell you that when flashing or booting it, it doesn't run, it sends me back to fastboot or it just gives errors. thanks for trying to help
by the way, I mention that when I enter recovery mode in the fastboot menu I get a message that says "your device is corrupt it can't be trusted and will not boot" and it turns off. when I turn on again it sends me to the fastboot
[QUOTE = "Yayo70136, publicación: 83715617, miembro: 6998495"]
I accidentally blocked the bootloader when there was no rom installed in the system, now I am without OS and I have the phone blocked from the bootloader I cannot enter the system and check the unlock box "oem" to flash the system again, I always get the same error * permision denied * I have the motorola code to unlock the bootloader but when entering it by fastboot it tells me to check the oem settings. which I can't do .. it doesn't go into the recovery stock either. and if I flash twrp it returns to fastboot, if I give start it sends a message "the system is corrupt and it won't start apparently the partitions are deleted or corrupted, but if it enters fastboot .. any ideas?
¡Saludos!: eek:: eek:: eek::confuso:
LMSA no funciona.
HELP PLEASE!!!
[/CITAR]
Can you fix it? I have the same problem
at this point it you may want to try the Motorola tool.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
it may be able to get it back into a workable state.