Related
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
shartwell said:
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
Click to expand...
Click to collapse
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
flashallthetime said:
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
shartwell said:
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
Click to expand...
Click to collapse
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
flashallthetime said:
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Follow what flashallthetime is suggesting.
btw, Rogers firmware is correct for your phone as there is no Fido specific firmware.
shartwell said:
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Click to expand...
Click to collapse
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
flashallthetime said:
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
Click to expand...
Click to collapse
Getting somewhere...
The command prompt can seemingly now interface with my device. It runs commands but clearing the cache didn't fix the problem. I've ran the command though so if there is a next step...
EDIT: Okay it's charing and I can interface with it via cmd. I can now use RTDlite with it as it's battery is charging. Should I flash the other Rogers now? I have my unlock code for the bootloader if that's what I've got to do first.
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Steve-x said:
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Click to expand...
Click to collapse
It's all fixed up. Thank you everyone who contributed to this! Time to enjoy my phone.
Last thing would be flashing twrp. Does someone have a link to the proper files?
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
flashallthetime said:
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
Click to expand...
Click to collapse
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
shartwell said:
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
Click to expand...
Click to collapse
Here's twrp http://forum.xda-developers.com/showthread.php?t=2458449
Flash with fastboot( fastboot flash recovery twrp 2.6.3.IMG)
Place the recovery image in platform tools folder. After it flashes make sure you go directly to recovery by pressing the volume up bottom to make it stick
Sent on my Moto X
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?
Did something stupid and bricked my 2013 Moto X. When plugging it in, the QHSUSB_DLOAD does not show up. If I unplug the battery and plug the phone in, it connects for a second and disconnects.
From researching, I found that I need to ground a pin to kick the phone into QHAUSB_DLOAD mode. Does anybody have experience in this and know what pin needs to be grounded?
core2kid said:
Did something stupid and bricked my 2013 Moto X. When plugging it in, the QHSUSB_DLOAD does not show up. If I unplug the battery and plug the phone in, it connects for a second and disconnects.
From researching, I found that I need to ground a pin to kick the phone into QHAUSB_DLOAD mode. Does anybody have experience in this and know what pin needs to be grounded?
Click to expand...
Click to collapse
If you were trying to root using the "brick" method, then it's advisable to check with OP and follow the instructions completely. I believe the next step in that thread was to use a script to bring it back to life.
Actually I had a Dev Edition Bootloader Unlocked XT1060 that a friend flashed to an XT1053 4.4.4 software. Obviously it failed at all system updates so I tried to restore it to the XT1060 5.1 software. That failed at flashing system.img so I reflashed from the start to 4.4.4 XT1060 software. Ran OTA once the phone was back up and it bricked.
I am getting it into the QHSUSB_DLOAD mode however I believe I have the newest 30.BE bootloader. Trying to unbrick using the following method doesn't do anything. Step 0 completes successfully however RSD can't get the phone into fastboot mode.
http://forum.xda-developers.com/mot...loader-v30-t3153725/post62367508#post62367508
I have the same problem. Did a system update and now the screen does not wakeup. Cannot go into bootloader. No charging indication nor responds to buttons. Just black screen. Followed the guide. Step 1 completes successfully but RSDLite says phone failed to switch to fastboot mode. I am using a Verizon Moto X 1st Gen Developer Edition. Bootloader is unlocked before the problem happened. Appreciate any help.
firstly my moto x was running on android 4.4.4,,,,,then i have updated it to 5.1,,,,and i was using it normally,,,,,,now i wanted to use android 6.0 on phone,,but motorola has officially stopped any more updates on my cell,,,,so i thought to it the other way....,,,i have switched on my developer option and enabled usb debugging from settings of my pone.........and i unlocked my bootloader through motorola site using fastboot and I also flashed twrp recovery....and then i tried to flash cyanogen mode 13.1,,,,,,but it didnt got flashed,,,,,i thought that the cyanogenmode file which i have downloaded was corrupted,,,,,so i downloaded the 13.1 cyanogenmode file for my moto x from many other sources and tried to flash them but it always showed error,,,,,,,,finally i tried to flash 12.1 cyanogenmode for moto x and 11.0 cyanogenmode foe moto x,,,,,,but nothing was getting flashed,,,,,i was totally frustated about what to do now,,,,,,finally i have seen a video on you tube saying that ""How To Factory Restore Your Moto X (2013 only) Using Fastboot!"",,,,,,,with[/url] the help of the video,,,,,by using flashboot i can flash my moto x into its stock rom,,,,and i applied the method as shown in the video,,,,i have downloaded stock rom(version 4.4.4) for my moto x and executed the syeps as shown in the video,,,,and it really worked,,,my phone was now running on stock android version 4.4.4 and i was very happy,,,,,,,,now my phone asked for system update,,,,and i hve downloaded the system update and then it showed me to install the update,,,,,so i clicked on install,,,so my phone satarted to get switched off,,,,,after getting switched off,,,,,now my phone is not starting,,,,it is stuck in boot mode,,,,i cant do anything,,,,i tried to go in factory settings or recovery but nothing is happening it is coming to the same boot mode screen.....i tried to boot unlock my phone again through the motorola site using fastboot....but even that is not happeneing,,,it says "could not unlock the data".....i dont know what should i do now,,,,,,i think now m not unable to unlock the bootloader because this time before my phone shut down i didnt switched on the developer option on my phone.....so please tell me how to switch on the developer option through fastboot,,,,,or tell me some other method through which i can run my device normally,,,,,,,it can be android version i dont care,,,i just want my phone to get back to normal,,,,,please help me with this.......
Hi all, I need some help
I have a Moto G7 which I thought was a PLUS. It was enrolled in my company's MDM and one thing lead to another, I failed to provide the right PIN and now Android does not start at all. When it boots up, it goes straight into the boot loader and no matter what option I try to select (switch tools, start, restart bootloader, recovery mode...) none of them brings up the phone so I am stuck in FASTBOOT FLASH MODE. It does also say "OEM-LOCKED", not sure what that is.
So I tried many things, but now I am trying to get re-imaged with RDS LITE and the software does not see the device. "adb devices" does not see any devices, but "fastboot devices" does.
At this point I hope to get RDS LITE to work and burn the sock image to the phone, but I need help.
Also, although I bought this as a G9 PLUS, when the phone starts into the bootloader it shows:
BL: MBM-2.1-river_retail-437e1163***-200***
Baseband: M6_41.178.01.156RRiver_NA_CUST
What image do I need to use?
What is the easier way to get the phone loaded with the Motorola stock image?
jluyt said:
Hi all, I need some help
I have a Moto G7 which I thought was a PLUS. It was enrolled in my company's MDM and one thing lead to another, I failed to provide the right PIN and now Android does not start at all. When it boots up, it goes straight into the boot loader and no matter what option I try to select (switch tools, start, restart bootloader, recovery mode...) none of them brings up the phone so I am stuck in FASTBOOT FLASH MODE. It does also say "OEM-LOCKED", not sure what that is.
So I tried many things, but now I am trying to get re-imaged with RDS LITE and the software does not see the device. "adb devices" does not see any devices, but "fastboot devices" does.
At this point I hope to get RDS LITE to work and burn the sock image to the phone, but I need help.
Also, although I bought this as a G9 PLUS, when the phone starts into the bootloader it shows:
BL: MBM-2.1-river_retail-437e1163***-200***
Baseband: M6_41.178.01.156RRiver_NA_CUST
What image do I need to use?
What is the easier way to get the phone loaded with the Motorola stock image?
Click to expand...
Click to collapse
Try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
RSD Lite doesn't work with windows 10 use 7
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk