Related
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?
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
for reference I am using windows 10 home x64
I saw quarx had a cm13 build for the l90 so i downloaded it, flashed it and whatnot. it didn't detect the sim card... okay no problem, i'll just reboot to recovery and reflash cm12.1. I was wrong, it wiped out twrp and installed the stock recovery. Not a single driver I try works, fastboot just loves toying with me. no matter what command i do, (unless it doesn't affect the device) fails with
"Failed (remote: unknown command)"
I zeroed out my laf to enable fastboot, but cant fix that without fastboot accepting commands.
And to top it all off, the phone no longer boots to anything but fastboot... Reeeeal [email protected]#ing convenient
please help..
What L90 model (variant)?
Download mode isn't available either? If you can't enter download mode, I think there are some commands for d405 and/or d415 that allows you to load fastboot img locally using adb. Or you can try the hardbrick unbrick tutorial (needs disassembling the phone).
Happy New Year!
Sent from my LG-D410 using XDA Free mobile app
Same boat
Hey, I am in the exact same boat.
Phone: LG D405n
OS: CM12.1
I had CM12.1 installed, TWRP Recovery, and V20a unlocked bootloader .
I installed Xposed and now Cyanogenmod just is stuck in a boot loop and cant get to recovery either.
I cant even flash the original software since my PC gets a blue screen as I install the LG Driver. Error is lgnetandmodem.sys or something.
If I uninstall the driver the phone can connect to the PC but then LGMobileSupport Tool doesnt detect it.
What on earth do I do?!
Re-installing the latest drivers should fix the BSD on Windows, or you can try flashing kdz using another operational system or computer.
Sent from my LG-D410 using XDA Free mobile app
lfom said:
What L90 model (variant)?
Download mode isn't available either? If you can't enter download mode, I think there are some commands for d405 and/or d415 that allows you to load fastboot img locally using adb. Or you can try the hardbrick unbrick tutorial (needs disassembling the phone).
Happy New Year!
Sent from my LG-D410 using XDA Free mobile app
Click to expand...
Click to collapse
Its a d415, could you link me to those so called commands please?
Im having the same issue after following Lady Vengeance's bootloader unlock tutorial
---------- Post added at 02:45 AM ---------- Previous post was at 02:40 AM ----------
@LaDY Vengeance
Just a heads-up. Upon attempting to fix with the softbrick tutorial I found, my device refused to accept any kind of commands. I gave up. Others may be in different circumstances and may be able to fix it using said tutorial
Ok I'm having an issue with my lg l90 d415 I had kingroot cm13 and twrp about a month ago I did cm13 update it finished it rebooted into twrp I cleared cache then reboot now it just shows the cm13 boot logo and sits there and when I try factory reset it shows the little android but it doesn't do anything usually it shows something words in background now it just resets I can access fastboot but not adb I forgot to enable adb but when I try any kind of fastboot command I get failed remote unknown command I can see the phone when I type fastboot devices it shows but don't like my commands I've tried all sorts of forums on this site thinking it's my drivers but it's not I can force it into qualcomm bulk from test points but qfil I get ap error and dload error so I'm in this endless loop oh and when I typed getvar it says my bootloader is locked but I can't unlock because the fastboot issue and it has snapdragon 400 chip what can I do?
Sent from my Sony D6708 using XDA Free mobile app
If you still can put your D415 in download mode then flash stock KDZ using LG Flash tool. If not then join other threads trying to unbrick a D415. Unfortunately it's not that easy for this model.
Hi to everyone, i have an problem with my old moto g 2014, i can't restore it to stock firmware.
When i try to flash stock firmware through fastboot everything is alright but if i reboot it he is stuck in bootlogo screen.
I've used the commands below and attach the logs.
Some one can help me to restore my titan please?
P.S. Sorry for english
Crix.Ful92 said:
Hi to everyone, i have an problem with my old moto g 2014, i can't restore it to stock firmware.
When i try to flash stock firmware through fastboot everything is alright but if i reboot it he is stuck in bootlogo screen.
I've used the commands below and attach the logs.
Some one can help me to restore my titan please?
P.S. Sorry for english
Click to expand...
Click to collapse
To which version did you try to upgrade?
You need to use a special mfastboot rather than normal fastboot.
https://forum.xda-developers.com/mo...unix-mfastboot-linux-mac-os-x-how-to-t2941888
avrockz11 said:
To which version did you try to upgrade?
Click to expand...
Click to collapse
To last 6.0 official firmware
Crix.Ful92 said:
To last 6.0 official firmware
Click to expand...
Click to collapse
Try the above link by meganukebmp
I've tried with fastboot linked by meganukebmp but it doesn't work
It's better if you install the stock android 5 then sideload the update to android 6
Syberclone said:
It's better if you install the stock android 5 then sideload the update to android 6
Click to expand...
Click to collapse
Another error
Another one
Are you using the fastboot device command first to make sure your phone is being detected ?
Are you using a batch command or are you entering each command manually ?
It seems like you are missing a step ??
Syberclone said:
Are you using the fastboot device command first to make sure your phone is being detected ?
Are you using a batch command or are you entering each command manually ?
It seems like you are missing a step ??
Click to expand...
Click to collapse
- Are you using the fastboot device command first to make sure your phone is being detected ? YES, MY DEVICE IS RECOGNIZED
- Are you using a batch command or are you entering each command manually ? I INSERT THE COMMAND MANUALLY
- It seems like you are missing a step ?? NOPE, NEVER MISS A STEP
Crix.Ful92 said:
- Are you using the fastboot device command first to make sure your phone is being detected ? YES, MY DEVICE IS RECOGNIZED
- Are you using a batch command or are you entering each command manually ? I INSERT THE COMMAND MANUALLY
- It seems like you are missing a step ?? NOPE, NEVER MISS A STEP
Click to expand...
Click to collapse
Use easy installer. Go to YouTube...search how to restore xt1068(i know yours is xt1080 but do it)the video is by ashwin tech. The first comment has a link to it. Download and put it in the extracted folder of the stock ROM files and click on easy installer.bat
The sequence is 1,3,5,4. Click these numbers and voila!
What file format is the Rom ? What are you using to flash the Rom ?
Hopefully CMKdaGreat has you on the right path
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Crix.Ful92 said:
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Click to expand...
Click to collapse
Did you connect your phone without being in fastboot first ?
Make sure you use the administrator command window in the folder that has all the boot.img, rom etc
Crix.Ful92 said:
I can't connect my Moto G2 to windows computer, the connection only work with my MacBook Pro
I have installed Motorola Driver and fastboot
Click to expand...
Click to collapse
Go to Device manager
Go to universal bus something
Update each driver in it
Might solve the problem
Syberclone said:
Did you connect your phone without being in fastboot first ?
Make sure you use the administrator command window in the folder that has all the boot.img, rom etc
Click to expand...
Click to collapse
I can connect only with fastboot mode because the phone does not boot with OS, it only boots into fastboot or recovery (twrp 3.1.1-1)
Crix.Ful92 said:
I can connect only with fastboot mode because the phone does not boot with OS, it only boots into fastboot or recovery (twrp 3.1.1-1)
Click to expand...
Click to collapse
Did you try connecting with the administrator command window ? Some 123 options for rom installation are done with a batch (bat) or execution (exe) files in windows ...also what version of windows are you running ?
I recovered my Moto G from a boot loop after kingroot caused p inblems
Try here ..
https://forum.xda-developers.com/showthread.php?t=2580060
I have the same problem as you with my XT1068, I tried all possible solutions posted here and nothing ...
Did you solved this problem?