4 replies to this topic

[sfgueller]

Ok, just to get it out of the way, I'm stupid.

 

Now, my problem.  I have a Motorola XT901 (Electrify M) that during my research, everyone says is the same as a Razr M (XT907).  I unlocked the bootloader, installed a custom recovery, and was running CM10.1 for quite a while, but wanted to upgrade to CM12.1.  I kept having errors, and got to where the phone would sit at the CM loading screen and do nothing else.  I went back in to recovery (first using TWRP, and then changing to CWM) and no matter what ROM I loaded, it either gave me the same results or failed.  In an attempt to fix it, I used ADB and flashed a stock XT907 image to the XT901 (using instructions found at

Please Login or Register to see this Hidden Content

).  I got excited when it originally loaded to the "set up your new phone" screen, but the touch would not work.  I immediately rebooted the phone, and now it won't do anything, just a blank screen.  Upon further research, I understand that this was a very BAD thing to do, and I essentially bricked my phone.

 

I have the phone now that when I plug it in to my PC it shows up as Qualcomm HS-USB QDLoader 9008 (COM3), and can be seen by QPST.  My problem is I don't know what to do next.  I do not have any of the files that QPST is looking for to send to the phone, BUT I do have a working XT901 (had purchased under BOGO deal) that I can pull files from if necessary, although I do not know how to do that.

 

I am hoping someone here has either accomplished a fix that would work for this, or could point me in the right direction.  I know I wasn't thinking when I did this, but I am by no means computer stupid, I understand file systems, and can easily follow directions.

 

PLEASE HELP!

[spainter]

Ok, just to get it out of the way, I'm stupid.

 

Now, my problem.  I have a Motorola XT901 (Electrify M) that during my research, everyone says is the same as a Razr M (XT907).  I unlocked the bootloader, installed a custom recovery, and was running CM10.1 for quite a while, but wanted to upgrade to CM12.1.  I kept having errors, and got to where the phone would sit at the CM loading screen and do nothing else.  I went back in to recovery (first using TWRP, and then changing to CWM) and no matter what ROM I loaded, it either gave me the same results or failed.  In an attempt to fix it, I used ADB and flashed a stock XT907 image to the XT901 (using instructions found at

Please Login or Register to see this Hidden Content

).  I got excited when it originally loaded to the "set up your new phone" screen, but the touch would not work.  I immediately rebooted the phone, and now it won't do anything, just a blank screen.  Upon further research, I understand that this was a very BAD thing to do, and I essentially bricked my phone.

 

I have the phone now that when I plug it in to my PC it shows up as Qualcomm HS-USB QDLoader 9008 (COM3), and can be seen by QPST.  My problem is I don't know what to do next.  I do not have any of the files that QPST is looking for to send to the phone, BUT I do have a working XT901 (had purchased under BOGO deal) that I can pull files from if necessary, although I do not know how to do that.

 

I am hoping someone here has either accomplished a fix that would work for this, or could point me in the right direction.  I know I wasn't thinking when I did this, but I am by no means computer stupid, I understand file systems, and can easily follow directions.

 

PLEASE HELP!

The error your seeing indicates the files that were necessary to run fastboot or operate the system are gone.  The QD Loader files are not available outside of Qualcomm.  It is like blank flashing the bios on a computer.  You have to replace the chip. In this case replace the main board in the phone.  I have not ever seen anyone fix this problem.

[sfgueller]

I guess I don't understand....in response to your reference, if there is an error flashing the bios on a computer, the majority of them have some sort of fail-safe mechanism to fix it.  I have found threads of other people fixing this same situation with other brands of phones, just not Motorolas.  I understand what you are saying though, that I probably won't be able to get the files that I need...maybe someone else has seen it fixed?

[spainter]

I guess I don't understand....in response to your reference, if there is an error flashing the bios on a computer, the majority of them have some sort of fail-safe mechanism to fix it.  I have found threads of other people fixing this same situation with other brands of phones, just not Motorolas.  I understand what you are saying though, that I probably won't be able to get the files that I need...maybe someone else has seen it fixed?

I have not heard of anyone fixing this problem short of changing the main board.  It use to be that an error flashing the bios chip on a computer was it completely distroyed the information on the computer that tells it what it was and how to boot the OS rendering it a brick.  You had to replace the chip in order to get the information back in place to get it to boot.  Safe guards didn't appear until fairly recently (few years).  Good luck on fixing that error and if you do I would sure like to hear about a good out come.

[xKroniK13x]

The tools are available to fix it, but the files are not. Someone needs to find a way to extract the files from a working device or leak them. I've tried using various tools to extract them from my xt907 with no luck.

Sent from my Moto X 2014 Pure Edition using Tapatalk