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.
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Use an exact Moto cable. No substitutes! Check PC drivers or Moto Device Manager.
Sent from my GT-P3110 using Tapatalk
unbrick
zaros104 said:
Bricked my droid bionic about a day ago, and have been looking across the web to find a fix. Here is the current information I have on it:
- Low battery
- Boot mode selection menu 0a.53 (assuming stock recovery)
- Stock recovery options with 'apply update from sd, wipe data/factory reset, and wipe cache partition
- apply update with just about any zip returns 'E: Signature verification failed', including the ROM previously used.
- Able to enter BP sbf flash mode, but decide cannot communicate (maybe cable)
- Able to enter ap fastboot mode, and usb transfer mode is obtainable. Before battery was on low, could program. Now get 'cannot program'.
- In ap fastboot mode, with usb transfer mode active, PC unable to communicate. Attempted with apk, apktoolkit, and RSDlite
- Have backups made by clockwork recovery of the whole device
- Have copy of ROM zip used for previously running android instance.
- XT875 model
Willing to do just about anything to unbrick this phone. I love the phone, and I don't want to replace it. Unfortunately, my job requires me to be in constant communication so I've a need to fix it ASAP.
Edit:
Tried flashing multiple stock ROMs and other things from stock recovery with little luck, most returning invalid signature
Click to expand...
Click to collapse
You are going to need rsd lite on your PC. The fxz files for your current build. A Motorola brand USB cord. And the latest Motorola drivers.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
http://forum.xda-developers.com/showthread.php?t=2728352
See post #7 for the fxz build you will need to use.
Did fxz work for you?
Unbricking
I ran into same problem before, with Motorola it's a pain to do anything especially charging the batteries on it once it's been brick. If you search around this forum you can find a little article about a guy tweaking his ps3 controller to charger his battery. I wouldn't recommend doing this if you don't know what you're doing. But what I did was buy this little device that charges any phone battery I'm not sure if I can link a photo but i'll try it, not i'll give a name. In order to RSD and use ab fastboot mode on the xt875 you'll need at least 70-80 percent battery life, at least that's what the guys here on the forum recommend. But I've been able to unbrick my device only 40 percent battery life. Now once that battery is charge to a reasonable charge. You'll have to download the cdma targa file for your phone. I don't think anyone matters as long as it's the exact same or newer of your phone's original firmware. Extract the targa file and then run RSD lite click the ... button to open file and locate your extracted cfc file. Now you may run into some flashing issues with failure in step 5/10 and if you don't, don't worry about it. but if you do you'll have to open up the cfc file with wordpad and remove a few lines from. here are the lines that need to be removed; <step operation="oem" var="fb_mode_set" /> AND <step operation="oem" var="fb_mode_clear" />....there's another fail that happens but I haven't found anyone that had experience this problem. it seem like I was the only one that experience it. it has to do with something with the fail flash.bin or something I'm not sure. But I left a comment about this fix on this forum somewhere if you care to search for it. once you edit and remove those above mention lines save and run it again and it should operate flawlessly. I have also left a link down there for the edit cfc file and pictures of the device I was referring to about charging your batteries directly.
also you mention that it could be a cable thing. I read a lot of this but I've use the cable wires from my Samsung without any mishaps besides the above mention issues with 5/10 but this was a common problem that even thoses with a Motorola cable had faced. from what I know theses wires are exactly they're usb 2.0 wires and couldn't differ from each other that much. but it is probably better to use the exact cable than a non exact one. the reason it won't communicate is the battery is low as I have mention you'll have to charge this battery of yours to a decent 40 and up for it to run cause the process of re flashing can take anywhere 10-15 minutes and you don't want it to die in the middle of flashing your firmware. cause this I believe can lead to a hardbrick. the stock verification recovery will always have that return that value even from stock roms. Therefore it is recommend to use the RSD lite so you won't face that problem. I hope this helps.
Bricked
I thought my phone was history. The solution was using an actual Motorola USB cable. It made all the difference.
Maybe you installed an incorrect driver.
[Q&A] [SCRIPT] DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!
Q&A for [SCRIPT] DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SCRIPT] DROID 4 Utility XT894 Jellybean -- Windows + Mac + Linux (All In One!). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Still Recipe Failure in AP Fastboot
First of all - great job!!!
This Utility works for me - but I have to test three (!) USB-Ports on my Computer 'til the biggest files (system.img, ...) where flashed without problems!
Now I have the actual STOCK-ROM on it - but I have a Problem (OK - I have it still before this Utility)...
At startup of the DROID4 there is this Error:
AP Fastboot Flash Mode (S) (Recipe Failure)
0A.77
...
I hoped, that this utility will fix this, but it don't.
If I push both Volume-Buttons and Power, then Release Power I can start the STOCK-ROM manually without any problem - but I had to do it always...
Does anbody knows how to fix this error at startup? Maybe I must edit / copy a special config-file or something...?
Roider Tom said:
First of all - great job!!!
This Utility works for me - but I have to test three (!) USB-Ports on my Computer 'til the biggest files (system.img, ...) where flashed without problems!
Now I have the actual STOCK-ROM on it - but I have a Problem (OK - I have it still before this Utility)...
At startup of the DROID4 there is this Error:
AP Fastboot Flash Mode (S) (Recipe Failure)
0A.77
...
I hoped, that this utility will fix this, but it don't.
If I push both Volume-Buttons and Power, then Release Power I can start the STOCK-ROM manually without any problem - but I had to do it always...
Does anbody knows how to fix this error at startup? Maybe I must edit / copy a special config-file or something...?
Click to expand...
Click to collapse
don't know, I would factory reset in Stock recovery and Flashing firmware with RSD Lite
links in my list
sd_shadow's [Collection] of Links for Droid 4
Sent from my XT907 using Tapatalk
---------- Post added at 03:44 PM ---------- Previous post was at 03:40 PM ----------
sd_shadow's How-To Videos for Droid 4
Sent from my XT907 using Tapatalk
---------- Post added at 03:58 PM ---------- Previous post was at 03:44 PM ----------
For AP Fastboot Flash Mode (S) (Recipe Failure) try
1) Fully charged phone
2) Used Motorola cable
3) Upgrade Moto drivers to latest version
4) Use newest Droid 4 Firmware
5) Used RSDLite 5.7 (newer maybe better) with the following settings:
Flash options: Restart after flexing and TI Blank flash
Use image files and delete files on exit
Worked for me !!!
sd_shadow said:
don't know, I would factory reset in Stock recovery and Flashing firmware with RSD Lite
links in my list
sd_shadow's [Collection] of Links for Droid 4
Sent from my XT907 using Tapatalk
---------- Post added at 03:44 PM ---------- Previous post was at 03:40 PM ----------
sd_shadow's How-To Videos for Droid 4
Sent from my XT907 using Tapatalk
---------- Post added at 03:58 PM ---------- Previous post was at 03:44 PM ----------
For AP Fastboot Flash Mode (S) (Recipe Failure) try
1) Fully charged phone
2) Used Motorola cable
3) Upgrade Moto drivers to latest version
4) Use newest Droid 4 Firmware
5) Used RSDLite 5.7 (newer maybe better) with the following settings:
Flash options: Restart after flexing and TI Blank flash
Use image files and delete files on exit
Click to expand...
Click to collapse
Thank you - you made my day!!!
And here are the details, I used (for all the guys and girls out there which have the same problem):
- Fully charged phone
- A normal USB-cable (it was from a samsung-device) - because I have no motorola-cable-
- Drivers "Motorola_End_User_Driver_Installation_6.3.0_64bit.msi"
- Firmware "VRZ_XT894_9.8.2O-72_VZW-18-8_CFC.xml.zip"
- RSDLite "RSDLite6.1.6.msi" with the setting -> Flash options: Restart after flexing and TI Blank flash
- Important! The whole flash-thing takes max. 20 minutes! The longest time it's the system.img and other big files. But I think my problem was, that the USB-Port I used first had problems with the upload of this great files to the phone. So...if your flash takes longer as 20 minutes and "hangs" at the system.img -> forget it on that USB-Port and choose another one!
I hope this can help people who have the same issue.
Great forum - great threads - great software - great people - thank you
Great, this is the first time I have seen someone post that they had a (Recipe Failure) with the Droid 4.
The cause of the problem
sd_shadow said:
Great, this is the first time I have seen someone post that they had a (Recipe Failure) with the Droid 4.
Click to expand...
Click to collapse
The cause of the problem with the Recipe Failure was I - I used RSDlite and wanted to flash the Oiginal ROM, but had problems with my USB-Port (this is what I know NOW after all that tests and a lot of wasted time).
So because the flashing "hangs" at system.img for more than 40 minutes I canceled this...and so the error occours...
Thank you!
i was able to restore my Droid 4 after failing to boot up completely.
A few questions about bricked Droid 4.
1. My droid 4 is stuck at "writing 'system'" for more than 20'. Is there something wrong with the process? I tried both option 1 (wipe) and 2 (not wipe) but neither of them work.
2. Can I charge bricked phone by using wall charger when AP fastboot screen failure appears ? It says "Battery OK", does it mean it's charging?
3. If it charges and when the phone is fully charged, I'll try plug it in USB 2.0 port (instead of 3.0 - maybe that's problem). However, if plugging in USB 2.0 port doesn't solve anything, can I still be able to unbrick my droid?
Oh, anyhow, right now my phone is stuck at:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.77
Thanks in advance :fingers-crossed:
JohnVo said:
A few questions about bricked Droid 4.
1. My droid 4 is stuck at "writing 'system'" for more than 20'. Is there something wrong with the process? I tried both option 1 (wipe) and 2 (not wipe) but neither of them work.
Click to expand...
Click to collapse
Windows 8, has caused issues, if you are using windows 8 try windows 7.
2. Can I charge bricked phone by using wall charger when AP fastboot screen failure appears ? It says "Battery OK", does it mean it's charging?
Click to expand...
Click to collapse
No, battery will not charge in AP Fastboot mode, or android recovery
3. If it charges and when the phone is fully charged, I'll try plug it in USB 2.0 port (instead of 3.0 - maybe that's problem). However, if plugging in USB 2.0 port doesn't solve anything, can I still be able to unbrick my droid?
Thanks in advance :fingers-crossed:
Click to expand...
Click to collapse
Yes, usb 2.0 if prefered, also verify drivers are installed correctly. see Motorola USB Drivers, RSD Lite, Firmware...
The other options is RSD Lite see Flashing Droid 4 with RSD Lite
sd_shadow said:
Windows 8, has caused issues, if you are using windows 8 try windows 7.
No, battery will not charge in AP Fastboot mode, or android recovery
Yes, usb 2.0 if prefered, also verify drivers are installed correctly. see Motorola USB Drivers, RSD Lite, Firmware...
The other options is RSD Lite see Flashing Droid 4 with RSD Lite
Click to expand...
Click to collapse
Just successfully unbricked my Droid yesterday thanks to the utility and fastboot cable I bought on eBay. I'm not too sure but maybe my phone was bricked because of windows 7 64 bit and USB 3.0 :silly:
Bootloader locked
I am currently running 4.1.2 mentor's rom (bought the phone this way) and the bootloader says it's locked and running fastboot oem get_unlock_data returns with unsupported command. Must the bootloader be somehow unlocked first? I was looking around and apparently Modaco Superboot is the only way to unlock the bootloader. Has Modaco Superboot been tested? Is it necessary or will this work as is? Thank you!
edit: The download link I saw for the Modaco Superboot XT894 is a survey, junk page, not legit. Disregard post. Just read the FAQ, apparently you use Safestrap.
NTULINUX said:
I am currently running 4.1.2 mentor's rom (bought the phone this way) and the bootloader says it's locked and running fastboot oem get_unlock_data returns with unsupported command.
Click to expand...
Click to collapse
pretty sure that command does not work with XT894
Must the bootloader be somehow unlocked first?
Click to expand...
Click to collapse
the XT894 bootloader is not unlockable
I was looking around and apparently Modaco Superboot is the only way to unlock the bootloader. Has Modaco Superboot been tested? Is it necessary or will this work as is? Thank you!
Click to expand...
Click to collapse
looks like superboot only roots, and I doubt it works with XT894
After battling with Mentor's ROM, I flashed it using this script and 4G LTE works for the first time. I almost thought my phone was bad. Thank you so much!
You might want to add that ia32 libs must be installed due to adb.linux is a 32-bit app. Simply enabling IA32 emulation in kernel is not enough. ldd ./adb.linux returns missing 32-bit libs if not installed. I had to set up a Debian 64-bit system on another partition with libc6-i386 lib32stdc++6 and I think something else (perhaps lib32ncurses5 and similar)
Using a gentoo 64-bit system with a no-multilib profile will not work. Just wanted to share this in case anyone else had the same problem.
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