Database Develop

Help me please! 0x56

Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English

Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX

iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.

skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command

skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk

Ota KitKat update?
What phone do you have?

I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk

[Q] Need Help-VZW Dev Edition (I've read)

I got a Dev Edition from Swapp. It was unlocked, rooted, with TWRP - PRE-camera update.
I struggled many hours last night to finally get it to where it is now. I now have: unlocked with Kit Kat
BUT, can't reboot into recovery. I've tried pushing the new TWRP in several different ways. (wanting that AND root). When trying to go to recovery, it simply goes to Any on his back ("no command"). I can from there push buttons and reboot back into the phone so it is usable.
I had to use the Toolkit to install TWRP...(at least I think it's installed - can't get there to really tell).
I went through so many things last night to get it to it's current state. It took a while to get the thing back to stock recovery and stock firmware...then I let it download camera update and then Kit Kat.
Just having a time with this TWRP thing. I can't Fastboot OR mfastboot. PC says missing aAdbWinApi.dll....not sure how to rectify. I've downloaded Moto Device Manager. I just downloaded Android SDK bundle to see if that would get me what I needed for fastboot. But, I'm not sure what to do with that Zip (too many things in it...no "install" that I see).
Work is going to kill me today because my mind is NOT going to be where it should be.
I sure would appreciate someone taking the time to point; state; show; give specific links; something if possible to get my TWRP and root going.
That was alot. Now I have to get my kids out to school.
Thanks!

http://forum.xda-developers.com/showthread.php?t=2536200
[HOW-TO][DEV EDITION ONLY]Root on 4.4 KitKat
Sent from my XT1060 using Tapatalk 2

One of the important things in the thread chaoslimits posted the link to is the newer twrp that is 44 compatible. It was released just overnight, after KK offically got pushed out by VZW.
Before that, there was a TWRP with 44 in its name, but it would hang if you tried to boot into it after you've rooted. The new version works.
So you might just be able to fastboot flash recovery with that newer TWRP and be good.

KidJoe said:
One of the important things in the thread chaoslimits posted the link to is the newer twrp that is 44 compatible. It was released just overnight, after KK offically got pushed out by VZW.
Before that, there was a TWRP with 44 in its name, but it would hang if you tried to boot into it after you've rooted. The new version works.
So you might just be able to fastboot flash recovery with that newer TWRP and be good.
Click to expand...
Click to collapse
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me. But, you'd think it would at least boot into normal recovery if it had not been able to work.

Dburgessme2 said:
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me.
Click to expand...
Click to collapse
If you got TWRP on your phone, fastboot & adb should have been working. Did something change on your PC? How does the phone show up on your PC in Device Manager?
Dburgessme2 said:
But, you'd think it would at least boot into normal recovery if it had not been able to work.
Click to expand...
Click to collapse
Also, not sure I follow what you mean because by flashing TWRP you overwrote the normal recovery. So booting normal recovery would no longer be possible after you flashed TWRP on.

Dburgessme2 said:
I'm pretty sure I had the newest TWRP last night. I think it's my ADB & fastboot that's killing me. But, you'd think it would at least boot into normal recovery if it had not been able to work.
Click to expand...
Click to collapse
Shut the phone down and reboot into fastboot mode (volume + power). The connect it to your PC. Open a command prompt and change directory to your fastboot location under AndroidSDK. Enter:
"fastboot devices"
and see if your phone shows up.

chaoslimits said:
Shut the phone down and reboot into fastboot mode (volume + power). The connect it to your PC. Open a command prompt and change directory to your fastboot location under AndroidSDK. Enter:
"fastboot devices"
and see if your phone shows up.
Click to expand...
Click to collapse
Yes, it shows there.

Dburgessme2 said:
Yes, it shows there.
Click to expand...
Click to collapse
Have you put the recovery IMG in the same folder that fastboot is located, fastboot cmd window type fastboot flash recovery twrp.2.6.3.1-ghost-4.4.img
Sent on my Moto X

Dburgessme2 said:
Yes, it shows there.
Click to expand...
Click to collapse
I AM ROOTED with TWRP! yay! (did it from my work Win XP machine)
Thanks to ALL!

Dburgessme2 said:
I AM ROOTED with TWRP! yay! (did it from my work Win XP machine)
Thanks to ALL!
Click to expand...
Click to collapse
Congratulations, I was wondering if you ever got it up and running, enjoy!!
Sent from my XT1060 using Tapatalk

In need of xt1060 dev 4.4.4 sbf

So here is what happened...
my phone was running krypton 1.4.1 (4.4.4) rom. i decided to try a cm12 rom. the cm12 rom was bootlooping so i decided to go back and restore a nandroid. however my phone was encrypted on the 4.4.4 rom and when i went back into twrp and it asked for my password before the nandroid, it said wrong password. i was basically locked out and couldnt nandroid restore.
i then did some readying to try to push the rom adb but that wouldnt work. so i did a user erasedata to get rid of the encryption (it worked). so then i tried multiple different things for adb and fastboot to try to fix it. my device would not show up in adb so i tried to reinstall drivers. they installed but my phone will still not show in adb.
at this point it just bootloops at the twrp screen or i can just have it sit at bootloader....
does anyone have the xt1060 4.4.4 sbf? all the links do not have it anymore.
thanks

Check Motorola's website

Skeetch79 said:
Check Motorola's website
Click to expand...
Click to collapse
they dont have the sbf. i downloaded the whole zip from them already. they just have the file for adb. i cannot get adb working since phone is messed

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf

Skeetch79 said:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf
Click to expand...
Click to collapse
oh ok this is what i downloaded from them. i didnt see an sbf file in it though. is the whole package considered the sbf?

I think this is only OTA, but it's the only thing I could find..
http://motofirmware.center/files/file/151-vzw-xt1060-444-kxa2112-l126-cfc-1ffxmlzip/
I'm sure someone has a copy of the SBF that they had downloaded somewhere.

Also refer here: http://www.droidrzr.com/index.php?/topic/61124-House-of-Moto-[4.1]
Use the link to the zip file and the above link to restore your device

Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/

the problem i have is adb wont detect my device. i think it was because when i flashed cm12 i was not able to boot it up and select debugging even tho i have the drivers installed

fury683 said:
Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/
Click to expand...
Click to collapse
thanks i got it downloaded. rsd lite wont detect my device though. either will adb.

@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd

Skeetch79 said:
@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd
Click to expand...
Click to collapse
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...

sruel3216 said:
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...
Click to expand...
Click to collapse
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.

KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
All i can get to is bootloader. however adb and fastboot will not detect my phone is plugged in even when i power off and hold down volume + power.
I cant really get to twrp. all it does is bootloop at the twrp splash screen
I have all drivers, sdk, etc installed on my comp and it worked earlier that day. once i went back from 5.0 rom to 4.4.4 rom, the encryption i had on my phone got all messed up and it got screwed up from there

KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition

sruel3216 said:
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition
Click to expand...
Click to collapse
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.

KidJoe said:
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.
Click to expand...
Click to collapse
Sweet got it all rooted again and running. thanks a lot!

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

[Pro Help Needed with restoring phone to factory settings]

Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.

e4noob said:
Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
Click to expand...
Click to collapse
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.

madbat99 said:
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
Click to expand...
Click to collapse
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.

e4noob said:
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
Click to expand...
Click to collapse
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!

madbat99 said:
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
Click to expand...
Click to collapse
Thanks. That helps a lot.

e4noob said:
Thanks. That helps a lot.
Click to expand...
Click to collapse
Good luck!

madbat99 said:
Good luck!
Click to expand...
Click to collapse
Again, appreciate the help a lot.
So I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas?

madbat99 said:
Good luck!
Click to expand...
Click to collapse
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )

e4noob said:
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
Click to expand...
Click to collapse
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.

madbat99 said:
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
Click to expand...
Click to collapse
Yes the same version. I have it on fastboot when connecting (also tried normal bootup and pc recognizes phone just fine). Good to know there is the bat file option for last resort. I'll try installing android sdk and may be it'll solve this driver issue. So I'll have to ask you for the steps to make the the bat file and how to make it work.

You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.

Ragarianok said:
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Click to expand...
Click to collapse
What does it do and how do you use it?

e4noob said:
What does it do and how do you use it?
Click to expand...
Click to collapse
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.

Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
I'm gonna try it out if it works for moto g6. Thanks, man.

Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?

e4noob said:
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
Click to expand...
Click to collapse
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.

Ragarianok said:
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Click to expand...
Click to collapse
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?

e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Yup! That's completely normal.

e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Do you really need it locked?

Ragarianok said:
Yup! That's completely normal.
Click to expand...
Click to collapse
I'm getting this message.
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.010s]
finished. total time: 0.011s