Database Develop

[Q] Almost as good as a brick - No wipe, no SBF

Yesterday I had a received a phone call from a friend and upon ending the call I could not hang up. The screen had locked on the call screen. I waited and tried to use the power button to turn the screen off and then on to see if that would clear it but to no avail, so I had to do a battery pull.
I restarted the phone and first thing I noticed was that it was now telling me that I had 5% of my battery remaining, where the phone had been around 80% before the battery pull. Then pretty much everything started force closing, and it rebooted on its own. Upon restart it came up with the dialog box stating that "UIDs on system are inconsistent" and that I should wipe data, and has a button stating "I am feeling lucky". Then it’s endless pop ups of force closes. I finally get it to a point where I can try a factory reset via "Privacy" in settings but nothing changes.
I go into recovery and wipe data and cache partitions and it says it does so successfully, but when you reboot it has not. The phone goes into my "normal" home screen and settings, nothing has been restored back to outta the box state, and it does not prompt you to go through setup.
Other than I used Petes One Click root about 4 months ago the phone is stock, with no new apps installed just before this issue.
If you try to remove any applications, it says they are removed successfully, but when you reboot the phone they are all back as if nothing had happened.
Plug the phone into any computer and it is recognized, but the phone does not seem to know it is plugged into a PC... no "charging" or "mount SD" info.
I tried to do a factory image restore via RSDLite 5.6.4 using
cdma_solana-user 2.3.4 5.5.1_84_D3G-55 110812
It gets to step 3/18 and then tells me:
"Failed Flashing Process: 3/18 flash mbmloader "mbmloader.bin" Phone returned Fail"
I've used RSDL for flashing my OG, D2 and Dx's before with no issues.
RSDL's Flash error log shows:
Line 1041
ERROR: Phone[0000]: Unable to retrieve initialization values from INI file.
File: D:\GitProjects2\hdt_windows_flash\flash\code\flashdll\PST_FP_FlasthThread.cpp
Device ID:0
03/13/12 00:48:51 New Log Started For Software Download.
03/13/12 00:54:21 00001db8 Phone.cpp 1750 0 ERROR GetTechnology failed: ERROR.
03/13/12 00:54:46 The FlashLog key is turned off.
03/13/12 00:54:52 Multi upgrade started for 1 phones
03/13/12 00:54:57 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
03/13/12 00:54:58 [Device ID: 0] 2/18 reboot-bootloader
03/13/12 00:55:03 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin"
03/13/12 00:55:04 ERROR: 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL. - on device ID 0.
03/13/12 00:55:04 [Device ID: 0] 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.
03/13/12 00:55:04 ERROR: Failed flashing process. - on device ID 0.
03/13/12 00:55:04 Multi upgrade finished.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
03/13/12 00:55:04 00001db8 Phone.cpp 514 0 ERROR Generic failure when sending command.
03/13/12 00:55:04 00001db8 Phone.cpp 1655 0 ERROR GetPhoneID failed: ERROR.
I then try Petes "One Click" easy unbrick and the command lines go through fine, all stating OK, and then it reboots the phone as it should. However instead of rebooting to the screen with the software box and the android with the yellow install bar, it goes to the white triangle with the exclamation point and little android. It will not go any further from that.
You can reboot the phone and it boots to the home screen, no set up, no removed programs...it looks as it did a few days ago before the issues started. However you will still get the force closes in a matter of minutes, the UID errors, and all the other issues.
Going to phone info shows the following.
System - 5.6.890
Baseband - N03.18.29P
Build - 5.5.1_84_D3G-55
I even tried to flash CM recovery and it will not do it. If you flash CWR through ROM Manager it will say it downloads and flashes successfully but it does not.
It seems as if the system has become unformat/flash/wipeable.
Suggestions? Clues!?

So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

DoubleYouPee said:
So you're on .890?
I'd try this first:
http://forum.xda-developers.com/showthread.php?t=1339816
File mirror: http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
That has already been tried, as noted above.

Ianscape said:
That has already been tried, as noted above.
Click to expand...
Click to collapse
It says you used RSDlite

DoubleYouPee said:
It says you used RSDlite
Click to expand...
Click to collapse
And then after it says I did the Fast/Easy unbrick
Ianscape said:
...I tried to do a factory image restore via RSDLite 5.6.4 using
....
I then try Petes "One Click" easy unbrick...
Click to expand...
Click to collapse

Did you try removing the ones that give you error from the .bat?

did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip

Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?

Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
~SU!C!D3~ \,,/.(*_*).\,,/
Sent from my UnLocked XT862 Droid 3 with full XT883 2.3.6 on Straight Talk GSM

I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/showthread.php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.

gierso said:
did you started in the correct flash mode?
power + M
ap fastboot??
Use the one in my signature, its also psouza but is different (the one in psouza thread never worked for me)
this one (post by chaoticweaponry file by roots wiki) works in the mode i ssaid
the multiupload link is dead i think, but in the last posts there is a dropbox
http://dl.dropbox.com/u/61707107/Ve...izon+DROID+3+OTA+5.6.890+to+phone_psouza4.zip
Click to expand...
Click to collapse
Yes it was in ap fastboot. I will give the one in your sig a shot, as I have been using psouza's original zip. Maybe it will work *crossfingers*
redsox958 said:
Pete's One Click Easy Unbrick sounds like a mash-up of his root tool and the quick unbricking script. Just to clarify, it was the MS DOS looking window that comes up after clicking "CLICK HERE TO FLASH etc."?
Click to expand...
Click to collapse
Yes, it' the psouza Fast/Easy unbrick, using the moto-fastboot files, etc.
queberican351 said:
Hold "X" and power. When u get the triangle press both volume up and volume down @ the same time. Wipe data a couple times followed by wipe cache a couple times. Pull the battery, then use the easy unbrick method in fastboot. You will want to find a way to have a good if not full charge before you unbrick. Should do the trick.
Click to expand...
Click to collapse
That has been done several times, with no changes to the system. While Recovery states that it completes the wipe, it does not appear to wipe anything. I'm going to try the link gierso posted to see if this helps.
mikedyk43 said:
I have bricked my phone numerous times recently and have found a very simple way to recover from it, without even having to plug it in to the computer. The OTA leak found here: http://forum.xda-developers.com/show...php?p=23223061 can be put on the root of your SD card and installed using the stock recovery. Power + x followed by volume up/down, wipe data, wipe cache, install zip from sd and selecting the OTA zip. I have recovered several times with this and it is pretty handy to be able to do it where ever you happen to be. Of course you will still have to root and reinstall your other goodies, but it works.
Side note: This OTA leak can NOT be rooted with the standard D3 root methods. You must use the D4 root method to gain root privileges.
Click to expand...
Click to collapse
Good to know that you can try it from the SD. I may give that a shot as well. I have bricked my D2 over and over F'ing with it and have always been able to recover from it easily...figures that the first time my D3 does it and it tells me to go pound sand.
Thanks on the D4 note.
-
I'm setting this thing down for a day I need to take a step back so I can try the other file that gierso posted without throwing this thing against a wall.

Had this happen to my wife's Droid 3 and saw 1 post on another forum about a user it has happened to. After conversing with Motorola regarding my "Groundhog Day" issue (ie - no matter what you do, nothing changes on the phone... kinda like the movie Groundhog Day starring Bill Murray), the tech support reps came to the conclusion that somehow the NAND because write-protected. Neither RSD nor the Fast-FBZ nor Safe Mode would let me alter the phone in any way. I had to have the handset exchanged out under manufacturer's warranty...

Try on "AP Fastboot" mode
moto-fastboot -w
moto-fastboot erase system
moto-fastboot erase preinstall
moto-fastboot erase cache
moto-fastboot reboot-bootloader
now use the Psouza Fast/Easy unbrick.
If this does not help. than it would be better to go for a replacement.

[Q] yet another soft bricked bionic

I love my bionic, and it has plenty of life left in it. Except for the fact that I screwed it up. Here's what happened: I had it rooted, had bootstap installed, backed up my system using the bootsrap recovery, and then tried to install a CM 10.1 zip file I found from somewhere on these forums. It gets to the load screen and then I see the blue CM wheel that NEVER stops turning (at least not within the 4 hours or so I let it run). No problem I say, I'll just reload my backup. Oh wait, you need a working system to do that. DOH!! So now, if I let it boot normally I get the perpetual CM boot screen. I've downloaded several other ROMs and tried to use the stock recovery to install them but it keeps saying "signiture not verified" or some such other nonsense which leads me to believe that's not an option. I've spent quite a bit of energy googling and going through forums on how to fix this, but all I can find are how to's with old outdated links.
If someone has a current link to whatever .xfz file I need or some other magical way to fix this, I would be indebted to you. As I said, I love this phone (it still looks and functions like new otherwise) and it seems like in it's current state I should be able to fix it somehow but I may be on my way to the Verizon store a little earlier than planned if I cant figure this out. Any takers?

Sounds very similiar to my issue.. no response to mine yet either.

Here's a link for your RSD
http://sbf.droid-developers.org/cdma_targa/VRZ_XT875_6.7.246.XT875.Verizon.en.US_CFC_01.xml.zip
Use RSD Lite to restore your phone. Google is your friend. Read & follow all instructions. I am in no way responsible for what you do to your phone.
Best of luck!

Low battery when trying to program bootloader.
Ok, I made somewhat of a noob mistake here. I read somewhere that there was an ICS ROM that could be flashed on the safe side using Bootstrap. Thing is, I couldn't remember or find the one I'd read about. Long story short, I flashed Icarus 1.8.3 on safe side using Bootstrap, which didn't work. I wiped everything there is to, including System. Big No No. Phone no likey Icarus on safe side (I know, the instructions said Safestrap 3.11 only). My question, other than buying a spare battery charger to charge the battery without the phone, can I charge it using the phone? I can boot into stock recovery, bootloader, and the screen where you select Normal Boot, Fast Flash, etc. I'll buy the charger if need be, but I'd rather not shell out the $50 or so for it if I don't have to. Thanks in advance.

:thumbup:

Edited to reflect personal unbrick success:
For those of you looking for a way to flash the SBF/FXZ file from within a Linux environment:
There's a "manual" method suggested at a different site using fastboot; unzip the zip archive (SBF file) and flash the listed/pertinent files/images individually to the device. It's still written up with windows-users in mind, but I don't see why it wouldn't work in Linux. Hope that helps someone.
Here's the jist of the commands that were involved in succesfully unbricking my Droid Bionic using the appropriate SBF file for my Android version:​
Code:
fastboot flash mbm allow-mbmloader-flashing-mbm.bin
fastboot reboot-bootloader
fastboot flash mbmloader mbmloader.bin
fastboot flash mbm mbm.bin
fastboot reboot-bootloader
fastboot flash cdt.bin cdt.bin
fastboot erase cache
fastboot erase userdata
fastboot flash lbl lbl
fastboot flash ebr ebr
fastboot flash mbr mbr
fastboot flash devtree device_tree.bin
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cdrom cdrom
fastboot flash preinstall preinstall.img
fastboot flash webtop grfs.img (skip this step if you are using a JB fxz)
fastboot flash radio radio.img
fastboot reboot
Obviously, don't forget that you have to be in fastboot mode to use the `fastboot` command (Hardware keys: VolUp +Power)
**Once again, I was lucky enough to stumble upon a posting by someone else on androidforums. Feel free to check it out at the above-mentioned link, perhaps you could adapt it to your own situation in times of despair.

Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic

Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Yup...they have a neatly organized list view of the SBF files, for all of the different android versions for the Droid Bionic (XT875), as well as a huge number of other devices.
Here's the section for the Bionic: http://sbf.droid-developers.org/cdma_targa/list.php

I can't exactly speak for how to solve the original problem, but for others who may search here. I use safestrap on my phones (3 between the kids and I all Bionics) and I put a newer version of Cyanogenmod on one phone just yesterday and I had the same problem. after trying a few things and still having the stuck boot, I deleted the ROM1 (this was the ROM slot I was using) slot and re-created it. Next I reinstalled CM10.1.3 and it booted. Safestrap is a great way to flash custom ROMS in my opinion I would recommend it highly!

Thanks for this one
Mr. HQ said:
Remember, that RSD file is an ICS ROM. If you already have JB on your Bionic, (most do) do not attempt flashing the ICS RSD or you will most likely "hard brick" your Bionic
Click to expand...
Click to collapse
Glad I read this post....

Xt875 hard brick
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery

SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse

Have a external battery charger
hugh a said:
SPheDaGhost said:
I know that this thread is pretty old and I figure I'd try it out just incase. I hard brick my droid bionic and now it does not boot up at all i tried to install a firmware and I believe it was the wrong one and now the screen is blank there's still a lot of battery life in it before it brick how can I fix this. Is this where I use the jtag or whatever it's called to unbrick. Phone does not boot up can't access ab fastbooy or recovery[/
are you sure your battery is good? you need to externally charge your bat, sometimes when phone is not functioning properly the bat will rapidly discharge, i dont know how clever you are but you can cut the end off an old charger and achieve a recharge by cleverly connecting the cut off leads to the bat
Click to expand...
Click to collapse
I have a external batter charger (see attachment) already, although I do know how to make one myself. It was less time consuming to go to the store and buy one. Plus it was only 5 bucks which isn't that bad. This external battery charger also displays the percent of battery life remaining. But I'll do what you suggest and see if that works out. Another strange thing is that if I plug the usb cord without the battery the charging (white) light comes on, which before it never did.
I know that the bionic droid xt875 uses the targa firmwares. I crashed my device flashing the spyder given to me by a source here on this forum. I was trying use my bionic with a gsm network so I follow this other guide. before I had followed this guide I had run through the proper proceedures of edit build.prop and radiocomm nv edit...etc.etc.. I was only managing to get no service on the HWB so I found an article pertaining to my particular model and tried it and subsequently it failed and now I'm stuck with a nice little paper weight.
Any other suggestions with this matter would be greatly appreciated. I'll keep you posted if the conditions changes.
Click to expand...
Click to collapse

[Q] [ q ] how to repair bricked (bootloader) moto x 1052

How to repair my bricked moto x xt 1052
Hi everybody...
Im new here.
I hope someone resolve it.
My moto x xt 1052 is bricked, means it is not powerup normally, no any screen displayed, no boot image, boot animation, but goes into fastboot mode sometimes on trying to go in it using hardware key pressing i.e. Power and volume down keys.
Here is the brief description what was happened......
My moto was on stock kitkat 4.4.4 for upgrading it to lollipop On 19th jan i was tried to flash cm12 over cm11 nightly as described in that thread , for that i was unlocked my bootloader, rooted it, flashed CWM touch recovery, flashed superSu zip file and flashed cm12 nightly over cm11 as described. But my device was stucked at boot logo. For resolving that issue i was flashed boot.img of prev nightly release(i.e. 1/15) through command promp using commands '' cd Downloads... cd fastboot... fastboot flash boot boot.img.
It flashesh image file successfully and device is booted successfully. I was used it till last 4days and regularly updated cm12 nightly via cmupdater.
But 4days back i was tried to remove warning message of device is ulocked bootloaded which was irritated me using same flash method and logo.bin files which was given in another thread by other members. But my BOOTLOADER IS DAMAGED and no any display was seen. I read many threads to repair it but no anyone give easy step by step guide. I was tried to repair it using motoflasher given in 1 thred. But as shown there no my device was not shown in device manager asQUSB****9** THERE is only adb interface in device manager. Also it says in motoflasher that no device was connected and output was incorrect COM port, which was refused to flash bootloader. Another thred of rescurrection of bootloader is not so easy and also download links are not useful,shows item was removed.
There is no another way, i thought bootloader is a kernel, so i was flashed zwiel kernel by same flashing method by cmd.
The problem remaims same, moto care told thay it will cost 6k for repairong which is too high. The descreltion is given in details for anyone who finds my mistakes and tell me angd give me suggestion. Xda is big deveopers forum, i know someone will help me.. So plzzz help me.
HOW CAN I REPAIR MY BOOTLOADER AND SAVE MY MOTO which will not useful then usable as a paperweight.

Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.

I am having a similar issue with a Sprint Moto X (1st Gen). I am able to get to fastboot mode and I have flashed the stock image for 4.4.4 using mfastboot (also re-did it using RSD lite as the boot.img gave errors using mfastboot) but the phone only still boots to a dark screen and vibrates roughly every 15 seconds.
Anyone have an idea on what else I can try? I've been scouring the boards and youtube, but haven't really come across anything on this type of issue.

Has been RDS flashing process totally completed without any errors?

The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.

​
chousue said:
The flash finishes with no errors when it goes to reboot the phone I end up at the same spot of a black screen that vibrates like its powering on then repeats every 15 seconds like its stick in a loop. Odd... I never get the smallest hint to a picture on the screen.
Click to expand...
Click to collapse
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395

Thanks for the suggestion.
I tried a dew different logos but the end result is still the same. Vibrates on power up, no display at all and repeats until I hold the volume down and count to like 10 when the next buzz cycle would happen so I can get into fastboot mode again. I should note that I can't see anything in this screen as well. I was starting to wonder if it was the screen that was the issue but the bootloop has me thinking otherwise.
I have another one with a bad screen and a replacement is on the way. I guess I can test it on this one as well but I'm sure the result will be the same.
I took a gamble on this one thinking I could bring i back to life, I figured the last owner just soft bricked it and flashing the latest stock would override what mess they did. I'll tinker around some more if there are some other options otherwise I can just flip it for parts i guess.
If I run the fastboot getvar all I get all the phone info so it gives me hope that something can be done, I just don't know what, it seems like I keep cycling through the same few processes hoping for a different result. I even tried the power + Volume down for two minutes thing that's supposed to bring up the "other" recovery menu, but with no display, i don't know what happening.
In a last ditch effort I did a tear down and connection check for all the parts so everything has been removed and firmly re-attached, certainly was nice to do that there instead of on the one I know will work once I replace the screen, but it sucks to still come up empty handed. Sorry for the long rant, it's just been a long few days of trying to find ways to bring this phone back to life.

Solved with downgrading
Sorry for bad english.
I had same issue.
But solved prev saturday hole day.
Using manual method instead of rsd.
Make sure u properly installed adb and mfastboot. For that open cmd and type adb. It shows command lines and then mfastboot. It also shows command lines then you are ready to go. If not, google it for how to install adb and also for mFastboot
Then download proper stock firmware for ur device. unzip it, u will get files of system, boot etc. Copy all this files and paste into mfastboot folder. Open command prompt in that folder by pressing shift and right key of mouse.
Then boot your moto into fastboot mode by pressing power and volume down key for a seconds. If u will not get in to fastboot mode try for many times unless u get it. I will get it after trying half hour.
Connect ur device to pc and run commans given in the following link. http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
End with-- fastboot adb reboot. It will reboot ur device.
Enjoy.

Thanks for the steps, I feel like I have done that already save for the few end steps with the oem commands.
So I flashed the print image using that guide and it still vibrates every 15 seconds and no display. I grabbed the retail file from the motorola site (oddly enough they only have TMO on the file name for some reason) and I flash this and it doesn't vibrate every 15 seconds, but still no display... Maybe in the end the display is bad after all...
Like mentioned before, I already have one coming in black for the one that works for sure...so I guess I'll test it on this one as well. Just wish it was as easy to disconnect/connect as my Nokia Lumia was, that took less than 10 minutes!

So, in the end it was the display afterall. I ended up getting another replacement screen as I really did not feel like attaching it and detaching it (yeah, I'm lazy sometimes). After setting up the new screen I plugged it in to charger and what do you know, battery at 0% then the motorola bootloader unlock screen after 5 or so minutes.
Now I have two phones, lol. One screen came without the speaker on the to fro some reason... And I think I just messed up my main phone removing the frame to add in that piece so lint and such doesn't get into the phone so easily... Dang it!
Edit - Yep, now it has a nice rainbow line display across the bottom where the navigate soft button would be... Guess I have to get one more screen!

could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app

sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
Go to the General Forum there's a dedicated thread with official roms for your particular model. Use download the ROM and flash through rsdlite. Always make a backup since it will wipe your internal storage clean.
Sent from my XT1058 using Tapatalk

sadik2112009 said:
could you please help me??
Iam using moto x XT1052 indian retail model...Many days b4 I have installed 5.1 brazalian lollipop backup via twrp but now i wanna come back to stock rom 4.4.4 kitkat via rsd lite..will it work or will my phone will brick bcoz of degrading process from 5.1 to 4.4.4??
plzz answer me if yes plz tell me the method to come back to kitkat
Sent from my XT1058 using XDA Free mobile app
Click to expand...
Click to collapse
If you installed 5.1 by using one of the TWRP backups, and did NOT flash the leaked OTA zip files, then you should have only touched /system and /boot partitions.. in that case, it would be safe to flash 4.4.4.

thank u so muchh......
KidJoe said:
​
Your symptom I'm quoting is what I've seen when a bad logo.bin has been flashed to the phone.
Can you try another? Some are in http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
thank you so much... this post saved my moto x...... i am facing this issue from last 15 days. so many pages visited but nothing help, but, after doing this it rebooted. may god bless you!:angel::angel::angel::angel:

Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
I also tried typing mfastboot in all commands.

Having same problem.
Please help if anyone can!
I can't resolve it by Fastboot in cmd.
dont display anything
not charging not boot not start anything

Travisdroidx2 said:
Have you tried to simply re flash your stock 4.4.4 firmware via fastboot since you say you can get into fastboot mode? Or rsd your 4.4.4 firmware. If you can get into fastboot mode I think you should be able to fastboot your stock 4.4.4 and be back up and running.
When in fastboot mode and phone plugged in and you type "fastboot devices" does it display a string of numbers for your device? If yes then you are good to go.
Click to expand...
Click to collapse
I have a moto x of my friend xt1053, dont not what he has done with it.
but
it is in Encryption Unsuccessful Condition.
When I connect to pc. Windows show that motorola xt1053 is connected. device manager shows MTP device under portable devices.
Mototrola USB drivers have been installed successfully.
I can not boot xt1053 into fastboot mode or recovery. Neither by adb/fastboot nor by buttons. (volume down + Power).
adb devices command does not show any numbers as it normally does when device is connected.
how get it back to working condition. any expert to help or happen to be in the same boat?

mb886 hard bricked with no salvation yet

Hi friends, first of all I am here because I don't have another options to try or I haven't found it yet here or in internet, I have a MB886 unlocked from AT&T, it was running AOSB 1.3.4(kk 4.4.2) had philz touch recovery and it just stays in infinite boot loops only turning off by entering in the ap fastboot option, from the causes I could mention the installation of the EB40 battery, but it was trouble free, and the cleaned of cache and dalvik from recovery, maybe a bad charge of static when installation? or a failure in philz touch?...
After search all about the problematic, download drivers and the computer ( windows 8) recognizing the fastboot quinara s from my cellphone, this is what I did:
-firstly, followed this post http://forum.xda-developers.com/showthread.php?t=2334000 and nothing positive, then this http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 and nothing positive with the fastboot commands and rsd lite doesn't recognized my cellphone fastboot in wondows 8.( tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml, MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml)
- I tried MYTH tools too, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml it shows commands like "varable not supported" or "target reported max download size of" but finished the flashing and still bootlooping.
-Followed this guide: http://forum.xda-developers.com/dro...-bricked-razr-m-4g-xt907-hd-preflash-t3135462 by fastboot, windows 8 and the motorola factory cable( pin 1 and 4 with +5v) could flash sucesfully MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml it works like a charm but was while it stayed connected to the computer, after this, flashing process only could be with the gpt_main0 file from the nextel firmware.
- Even in a sometime, I dont remember after how many flashings of the nextel firmware but was using the motocable, I could entered to my twrp recovery, cleaned all and did a clean install for AOSB KK from my SD, rebooted and bootlooping, then, I flashed again and entered to TWRP again and did a factory reset, and nothing.
- I tried MYTH tools again, but it doesn't work, tried to flash MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml and ATT_MB886_4.1.1-9.8.0Q-97_MB886_FFW-28_CFC_1FF.xml with the file gpt_main0 from the nextel firmware and in one time only reach the AT&T animation then froze.
- I combined the method from the razrs and the another one for the AHD to flash all the files from the firmwares and nothing happened, even the moto cable stops of functioned , because it showed responds from the fastboot like "varable not supported" "target reported max download size of " "FAILED (remote failure)"and with a normal usb cable everything was well flashed and nothing.
- flashing with rsd lite 6.1.6 in win xp used to get Error with MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml because the step of flash gpt_main0.
- I substituted gpt_main0 from MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml and it work with rsd in win xp (says SUCCES), just the last step when rebooted the phone, the phone stayed in boot loop.
-flashed MB886_niimx-user-4.1.2-9.8.2Q-50_MB886_NII_TA-2-16-release-keys-NII-MX.xml with RSD in win xp and fails in the last step when reboot, it stays bootlooping even when rsd says "SUCCES".
-tried to flash in ubuntu(fastboot method) with moto cable and a usb cable but never was like in windows 8, just boot loop and more boot loop.
so, here is the history of what I did it to my cellphone and he doesn't want to live anymore, so the question is, what I missed out? or what I can do it?, discarding throw it to the trash or having like a nice paperweight...
Any kind of help, suggestion, comments, or hardware modification will be appreciated and sorry for my english, I wrote the best I could.
P.D: always had a good porcentage of charge in the battery while did the flashings,charged it with 5v and 500ma directly to the battery and tested with multimeter when fastboot alarmed low battery, and anytime while phone had been flashed with AT&T relase keys rom, bootlooping was with the advertisement about the bootloader unlocked, and when had been flashed with nextel firm it shows motorola dual core logo boot loop.

I don't remember the exact name of the thread but search Atrix HD command line and you should find another guide that always worked for me. I never had luck with rsd lite or mythtools.
Sent from my LG-D850 using XDA Free mobile app

failed flashing partition gpt_main0
thank you for the help, I found that post: http://forum.xda-developers.com/showthread.php?t=2259661 and following the instructions, but I don't have more than a "FAILED" message in the first step when I try to flash gpt_main0 partition, with att release keys and with nextel firm, even when I use "mfastboot" instead of fastboot, it gets error message, there is a newer firmware version than the nextel one? or the partition is corrupted?... thanks.

The nextel firmware is the newest. There was an ota from att for the heartbleed bug, but I think that's all that was in it.
Sent from my Nexus 7 using XDA Free mobile app
---------- Post added at 11:06 PM ---------- Previous post was at 11:04 PM ----------
Are you sure you have an atrix HD? You mentioned TWRP in the op, but we don't have a fully functioning twrp.
Sent from my Nexus 7 using XDA Free mobile app

Philz touch instead twrp
Ok, thanks again buddy, and yes , the cellphone is an atrix hd, but you are right I used to have a philz touch recovery instead twrp (my mistake), the only error I have is flashing gpt_main0 partition and if I flash completely there is no more fails, with "mfastboot" every flash step is running like a charm and with "fastboot" shows messages like bootloader variable not supported or maximum size errors, the cellphone turns on bootlooping but stills enter to boot menu selection and ap fastboot mode...

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk