Database Develop

[A] Solved the Seven Vibration Brick

\\\Disclaimer: I am not responsible if you mess this up & break your phone///
Checking Your Situation:
*Phone only boots to Fastboot
*Phone does/Doesn't charge
*Power button Seems useless
*Phone Turns on and only shows-
the X screen & Vibrates 7x's
*LED Only shows Green/ Orange
indication light
Things You'll Need:
*Wall Charger
*USB Cable
*Computer (duh)
*Battery (of course)
*FRG83 ROM file http://tinyurl.com/6bym3vg
*Android ADB Setup
*Fingers Crossed
(Tip: if you are using the same Sdcard when the phone messed up, reformat it or use a new one)
Step One:
Download FRG83 ROM file http://tinyurl.com/6bym3vg
and unzip the package into your AndroidSDK Tools Folder
Step Two:
Watch the battery trick video
http://youtu.be/2O5adV-jj64 (Thanks n1newbie)
Once you've analyzed the video enough
plug your phone (while it's off) to the wall
charger and while doing the wall trick !!Make
sure you hold down the Volume-Down Button!! so
you can boot into fastboot.
Step Three:
Once established fastboot, plug the phone
to your computer and let your computer discover the
device.
!!Make sure the device says Fastboot USB!!
Open Command Promt (CMD). If you already
know how to use Android ADB type these commands:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fastboot devices
!!Make Sure You Device ID Shows UP!!
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let the phone run everything through and you should
be one Froyo.
Step Four:
Power down your phone
Reboot into Recovery (to see if your phone is still rooted)
If you are able to get into recovery flash any ROM
you like and Enjoy your UnBricked Nexus One

lilj4321 said:
If anyone needs the fix for this soft brick
let me know so i can post instructions!
Click to expand...
Click to collapse
You might as well write them out. You never know when someone will need them.

taodan said:
You might as well write them out. You never know when someone will need them.
Click to expand...
Click to collapse
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk

n1newbie said:
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
+2, hope it won't occurs

hi lilj4321. thanx for the steps frnd
the youtube link that you provided returns 404 error. so you might use this link for video trick (by myself )
PS- sry if i am wrng. will the device boot into fastboot mode after the seven vibration brick happens
Sent from my Nexus One using Tapatalk

fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.

lilj4321 said:
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
Click to expand...
Click to collapse
oh okies. thanx for using my video buddy
will try this if seven vibration brick happens. but ill pray it shdnt happen
will be helpful for all if it is stickied :thumbup:
just my 2 cents ...
Sent from my Nexus One using Tapatalk

I hoped for something much more useful.
The method of reflashing to stock using fastboot commands has been posted on Nexus One Wiki for 2.5 years now.
And of course, it won't solve any overheating phone, and no "7-vibration brick".
Thanks for trying to help, but the post is kinda (very) useless.

Stuck in fastboot
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.

ajaymkd said:
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
Click to expand...
Click to collapse
After doing all the stuffs, and after fastboot reboot.. The phone on the same state.. Brick state with 7 vibrate + X sign. Why is that so?

Someone please help i think i bricked idk

OMGOGOMOGMOGM SOMEONE PLEASE HELP
I just flashed the aokp rom http://forum.xda-developers.com/showthread.php?t=2250601&page=12 with safestrap recovery thing a majiger cant remember the name of it but anyway, i flashed it and when i tapped reboot it comes up with a black screen showing this format
Invalid flash mode (s)
10..9b(*) (sha-5b08bc, 2012-12-03:10:39)
eMMC info: size 8gb
Device is LOCKED, Status code: 0
Battery Low:
Transfer Mode:
USB connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb Connected
This is exactly whats on my screen right now and its scaring the hell out of me, SOMEONE PLEASE HELP I DID EVERY INSTRUCTION TO FLASHING THE ROM WITH THE RECOVERY IM USING AND THIS HAPPENED.
:crying ::crying: :crying: :crying: :crying: :crying: :crying: :crying: :crying: :crying:

Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
yea i was gonna say the same i also think new people see that safestrap thread thats stickied which is why they install ss and not cmw.
Sent from my MB886 using xda premium

This might help: http://forum.xda-developers.com/showthread.php?t=2231249

deeje00 said:
Face palm man. You need an unlocked bootloader for that rom says so in the info so you clearly didn't follow directions like you said to such as using cwm not safestrap. This is why we must read before acting hastily. You may be able to use rsd to flash stock but don't count on it.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
i actually have the same problem. My phone is unlocked before already, but the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode...
do you know how i can figure this out?

legendnexus said:
i actually have the same problem. My phone is unlocked before already, but the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode...
do you know how i can figure this out?
Click to expand...
Click to collapse
Did you flash a rom using Safestrap too?

audit13 said:
Did you flash a rom using Safestrap too?
Click to expand...
Click to collapse
is it a right source to try?
http://forum.xda-developers.com/showthread.php?t=1995220

legendnexus said:
is it a right source to try?
http://forum.xda-developers.com/showthread.php?t=1995220
Click to expand...
Click to collapse
That thread is for locked bootloaders. Do you have a locked bootloader? Did you flash a rom using safestrap?
Did you try this? http://forum.xda-developers.com/showthread.php?t=2231249
Or this? http://forum.xda-developers.com/showthread.php?t=2262726

audit13 said:
That thread is for locked bootloaders. Do you have a locked bootloader? Did you flash a rom using safestrap?
Did you try this? http://forum.xda-developers.com/showthread.php?t=2231249
Or this? http://forum.xda-developers.com/showthread.php?t=2262726
Click to expand...
Click to collapse
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...

legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
Damn, seems like those are the only two methods that could work.
The good thing is that you can't re-lock the bootloader.
You might want to send a PM to skeevy to see if he can help.
Is there any warranty left on your phone? I've seen posts where people were able to go back to AT&T to exchange the phone or send it in for repair.

legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
How have you tried to get into fastboot? Try turning your phone off, hold both volume buttons and press the power button a few times then use volume down to scroll to "ap fastboot" and use volume up to select.
Sent from my MB886 using Tapatalk

When you plug in the phone to charge do you see at least the boot logo?

may need to connect pins 1 & 4 together in micro usb charger port to phone within the plug itself and it will charge.

Swiftb12305 said:
yea i was gonna say the same i also think new people see that safestrap thread thats stickied which is why they install ss and not cmw.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
I feel like it's causing more problems than it's solving with new people that try to flash their phones, they see light at the end of the tunnel and assume it's the exit, when in fact it's a dadgum train.

legendnexus said:
Yeah i unlocked the bootloader before. so it seems like useless for my case. Plus i cant even boot into fastboot mode, how am i gonna install it lol
And as I said before; the problem is i cant get in to any bootloader or fastboot or anything. I can only tell the phone is on when i plug to computer and rsdlite sees the device, but fails to flash anything because it is not in the fastboot mode.
I tried both methods but they both fail where the phone need to be in fastboot mode, which is apparently not happening...
Click to expand...
Click to collapse
Have you tried a fastboot cable?

audit13 said:
Damn, seems like those are the only two methods that could work.
The good thing is that you can't re-lock the bootloader.
You might want to send a PM to skeevy to see if he can help.
Is there any warranty left on your phone? I've seen posts where people were able to go back to AT&T to exchange the phone or send it in for repair.
Click to expand...
Click to collapse
nope no warranty left..
penser said:
How have you tried to get into fastboot? Try turning your phone off, hold both volume buttons and press the power button a few times then use volume down to scroll to "ap fastboot" and use volume up to select.
Sent from my MB886 using Tapatalk
Click to expand...
Click to collapse
exactly the same way you wrote. but unfortunately it doesnt work.
SVLAN said:
When you plug in the phone to charge do you see at least the boot logo?
Click to expand...
Click to collapse
ahahaha nothing!! no single pixel power up, forget about the logo lol
HD-man said:
may need to connect pins 1 & 4 together in micro usb charger port to phone within the plug itself and it will charge.
Click to expand...
Click to collapse
anthony2424 said:
Have you tried a fastboot cable?
Click to expand...
Click to collapse
I research on that i guess fasboot cable is connecting the pins 1 & 4 together in micro usb cable. I tried that too, however result is the same.
doesnt work.
That was my last hope (fastboot cable), so i even try other combinations connecting different pins together, but it didnt work too )))
I have a beautiful brick as you guys can understand.
I am thinking to order a broken lcd atrix hd online and replace the boards right now. Do you guys think it is logical?
or like replacing the storage with a used one.
I dont know what else to do, out of ideas

I am aware I haven't replied in a while, my atrix had a hardware issue, but I got a nexus 10!! Anyways, when plugging the phone in does the LED light up green?
Sent from my Nexus 10 using XDA Premium 4 mobile app

Nope, no lights
Sent from my Nexus 5 using Tapatalk

Hm sounds like a hardware issue, check the pins in the phones micro USB port if other cables don't make a the LED turn green while the phone is off.
Sent from my Nexus 10 using XDA Premium 4 mobile app

Bricked Razr M

Hi, all. A friend gave me his son's RAZR M (Verizon, US) phone which he totally bricked. I've tried to reinstall a recovery partition, etc. using Motofail2go and Motopocalypse, to no avail. The Daemon runs and just hangs there. I have no way of knowing whether USB debugging was enabled on the phone. The phone stays at:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-03-22 09:18:22)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
Any ideas how I can get past this?
Thanks in advance.

have you tried to use rsd lite?

pbanj said:
have you tried to use rsd lite?
Click to expand...
Click to collapse
Yeah if you can get into AP fast boot try to rsd lite back to stock
Sent from my XT907 using xda app-developers app

since you can get into fastboot your should be able to salvage this. Can you get into stock recovery to verify if your rooted or not? what is happening when you try to run Motopocalypse to unlock the boot loader? Have you tried using Matts utility http://forum.xda-developers.com/showthread.php?t=2249773 to do all this work for you?

I had a similar error when I tried to downgrade my Electrify M by RSD'ing an early version of software. (I found out later its not possible to RSD "down") Anyhow, I was able to get rid of the "flash error" by flashing a new boot image. This "tricks" the bootloader into thinking all is fine. There's some info on flashing boot images here:
http://forum.xda-developers.com/showthread.php?t=2340764
As for Motopocalypse / MotoChopper etc., they need to be ran from a "booted" phone. If all else fails, RSD back to stock.

i think the razr m utility1.2 can save your phone http://pan.baidu.com/share/link?shareid=2491749448&uk=201633670

goodayoo said:
i think the razr m utility1.2 can save your phone http://pan.baidu.com/share/link?shareid=2491749448&uk=201633670
Click to expand...
Click to collapse
Im DOwnloading Now, I'll Tell You What Happens.
---------- Post added at 12:41 AM ---------- Previous post was at 12:30 AM ----------
jleznek said:
Hi, all. A friend gave me his son's RAZR M (Verizon, US) phone which he totally bricked. I've tried to reinstall a recovery partition, etc. using Motofail2go and Motopocalypse, to no avail. The Daemon runs and just hangs there. I have no way of knowing whether USB debugging was enabled on the phone. The phone stays at:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-03-22 09:18:22)
eMMC Info: Size 8GB
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Flash Failure
usb connected
Any ideas how I can get past this?
Thanks in advance.
Click to expand...
Click to collapse
You Dont Need USB Debugging To Be On To Do AP Fastboot, Device is LOCKED. Status Code: 0 Means That The Bootloader Is Still Locked.
Also Try To Use A Droid RAZR Utility.

Do you have the stock usb cable that came with the phone? I had the same issue with my phone; it might just need a charge..
Sent from my XT907 using xda app-developers app

I may be delayed but... if need be and the battery is dead you could buy a factory cable or the team black hat factory adaptor.... if budget is an issue make your own found here (http://forum.xda-developers.com/showthread.php?t=1077414) using a spare USB cable it does work I have made one used on the xt 894 and xt 912 I have yet to use it on the 907 yet I'm sure it works the same...
Sent from my XT907 using xda app-developers app

[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?

Urgent advice needed on Razr i XT890

hi, my phone Razr i XT890 is showing the Red Moto Logo, I tried to factory reset by going into fastboot also but nothing happened, I can find many thread here about the same problem but nothing conclusive could be found in those threads, hence I sent my phone for repairs, the technician hooked it up to a computer and said that most likely it is a software issue and the phone would be ok, after waiting for an hour I was told that the emmc has died and it cannot be replaced and the only solution would be to change the motherboard, since the mother board is not avaible in the market I looked it up on aliexpress and it costs around 70$ where as a new/refurbished phones are listed for 75$, need you guys advice on whether it can be repaired or not and if yes then how. I am a regular user and not an expert like you guys so if you suggest any thing plz do it in detail. FYI its a factory unlocked phone which had jelly bean OS and I never rooted it or did any hanky panky to it. Thanks

What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.

Hazou said:
What u could try to test if the mechanic is right (I suppose he is), is to flash stock firmware by hand and see what the device gives for error.
If the error is an i/o error the emmc is corrupted and we can't help that. It will need a replacement of the motherboard.
To test it, extract all images from the stock firmware. Then flash them while your Phone is in fastboot modes and connected to your pc, like this:
Use a compatible fastboot executable like mfastboot.
- fastboot flash boot boot_signed
- fastboot flash recovery recovery_signed
- fastboot flash system system_signed
- fastboot erase cache
- fastboot erase userdata
Every one of them should return an "OK". If there is an error in one of them that partition is most likely damaged and if u can't boot in recovery there is most likely no turning back.
Click to expand...
Click to collapse
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.

cooljatt18 said:
ok, thanks for the suggestion and say if they all come ok then?? and If an error comes in one of them then what ?? I will only be able to post in detail tomorrow after I have visited the mechanic.
Click to expand...
Click to collapse
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?

Hazou said:
If it all says OK, u should have a working device. No doubt about that. But if one of them doesn't we found the issue. Most likely i/o. Can u still boot to recovery? Or is that even impossible, because u said u tried a factory reset?
Click to expand...
Click to collapse
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !

cooljatt18 said:
I tried factory reset and the same screen appeared, then I tried recovery option in fastboot menu rather then factory reset the android robot with exclamation mark appeared when I pressed volume key I got some options partition cache etc I did that and also there was an option erase all data did that to got message both times that it has been done, then I chose the option of restart and again got the red logo screen !
Click to expand...
Click to collapse
This is most likely solvable. Try that flash methods a few post above and see what happens s

Hazou said:
This is most likely solvable. Try that flash methods a few post above and see what happens s
Click to expand...
Click to collapse
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it

cooljatt18 said:
so I went to the mechanic today and told him to flash with stock firmware and he told be that he did not have it !! Since the phone was never officially launched in my region I am guessing hardly any mechanic would have it, is there any place from where I can download it
Click to expand...
Click to collapse
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk

AGISCI said:
Which country and carrier is it from? That way I can post the link to the correct firmware file for your phone.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !

cooljatt18 said:
It is an unlocked phone, not linked to any carrier I am not 100% sure but most likely England/Great Britain, I remember the Reading GB as in short for Great Britain in the firmware name once !
Click to expand...
Click to collapse
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk

AGISCI said:
http://www.filefactory.com/file/6b396l5ar4tf/CFC_9.8.2I-50_SMI-26_S7_USASMIJBORAGB.xml.zip
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
thanks a ton!!!

hi, guys sorry for posting so late, was super busy, any how haven't got a mechanic to flash the phone, guess I will have to do it myself, request you to answer my queries
.1) a mechanic to whom I went convinced me to believe that the problem was due to a faulty battery and he could fix it in 5 mins flat, He opened the phone did some tinkering with it, I am not sure what but the phone was in same condition ie Red logo on booting. Was very disappointed came back home and I tried to restore it through fast boot and I noticed that the Battery Current was coming as 4.1 V earlier it was 3.7 !!! I am sure that the mechanic messed it up. Now my question is will it harm the phone, battery or any other part?? Should I just leave it the way it is ie 4.1V and not try to rectify it to bring it to 3.7V.
.2) I am not able to get a mechanic who can flash the phone as suggested in previous posts, pl tell how I can do it myself, I am a newbie at this and have zero knowledge of the process, pl tell what all software are needed! And hardware if any. All I have got currently is the firmware posted in previous posts.
Thanks