Moto X -XT 1053 camera not working - Moto X Q&A

I bought Moto x -XT 1053 from ebay.com thinking that it was US T Mobile version. On recieving the phone I found out that it was Mexico edition of Xt 1053 with 4.2.2 jellybean rom with no kitkat update. I unlocked the bootloader by getting the key from Motorola site and installed TMobile 4.4.2 rom from SBF DROID DEVELOPER site using the following commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
Everything is working fine except the camera which is not at all working. When I launch the app I get a camera error message. Sometimes i can switch to the front camera which seems to be working at times.But rear camera is not at all working
I could not get it to work even one time. Tried rebooting , erasing cache ,safemode etc. I have not installed any 3rd party apps from playstore also.
What could be the reason for this ?Please help me. I am attaching the necessary screenshots and log file.

You should try flashing the t mobile image with rsd
Sent from my XT1053 using Tapatalk
edit: Also, did the camera work before or did the fastboot flashes "break" it? I'm using a 1056 with the 1053 ODIN flashed onto it right now and the camera works fine.... (As you can see even Tapatalk and mtp think this phone is a 1053)

thundercles said:
You should try flashing the t mobile image with rsd
Sent from my XT1053 using Tapatalk
edit: Also, did the camera work before or did the fastboot flashes "break" it? I'm using a 1056 with the 1053 ODIN flashed onto it right now and the camera works fine.... (As you can see even Tapatalk and mtp think this phone is a 1053)
Click to expand...
Click to collapse
Tried with RSD Lite also but facing the same problem.
Also I did not check whether the camera was working initially with the Mexican Rom. Flashed the new KitKat Rom as soon as I got the phone.

It sounds like the camera might have a physical issue like a loose connector...
Sent from my XT1053 using Tapatalk

thundercles said:
It sounds like the camera might have a physical issue like a loose connector...
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Is there anything else which i can try? Can you share the rom which you have installed?

I've flashed all kinds of Roms stock and aosp of all moto x versions onto this 1056 trying to see if any of them knock out that Sim lock and I have never had trouble with the camera. That being said I have kept just under 4.4.2 because ability to have root is critical for me at this time so most everything I have put on here has been 4.4/4.4.1 I have had some issues getting the phone to take 4.2.2 roms sometimes but never camera issues just sometimes the phone just refuses to be flashed with parts of or a whole 4.2.2 Rom.
Edit: oh an easy potential culprit could be permission issues. In your custom recovery select "fix permissions" and clear the data and cache partitions. An rsd flash does NOT clear these out, I still have pretty much all the crap I had when I was running the sprint Rom earlier today on my phone even though I used rsdlite to flash the stock t Mobile ODIN a few hours ago.
Sent from my XT1053 using Tapatalk

Tried clearing the data and cache partitions but in vain. This could most probably be some hardware issue as you mentioned may be like a loose connector.
Anyways thanks for your suggestions.

Related

[Q] xt1056 Sprint, wont connect to network please help

while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help

Coverting Moto X 1097 Telus to Pure hab check failed

I'm trying to convert my Moto X 1097 to 1095 pure. When I try flashing files with mfastboot I get hab check failed for boot and hab check failed for recovery. It's running 4.4.4 pure but I assume still has old recovery as it won't boot into recovery. I have abd all and downloaded mfastboot v2. Why am I getting these errors? Bootloader unlocked.
Are you trying to flash 4.4.4 or 5.0?
Motoboot and gpt can never be downgraded, some files will always show they failed the hab check even though they are ok as they aren't the original files.
If you flash the entire 4.4.4 or 5.0 Pure firmware package you will have no radio at all and will need to use the original NON-HLOS.bin from the matching Telus package to get it back.
If you want to try the Pure 5.1 soak/leak then flash the full Pure 5.0 package and then apply the soak update via stock recovery. At that point your radios will work as the 5.1 soak appears to include a modem/radio that works with the XT1097.
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple.
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
matt1515 said:
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Stop using the power button to try to select recovery like you would on a Nexus device - use the volume up button and you'll be fine
Hahah dang I feel dumb
So just to conclude if I did want to go back to fresh stock Telus. Would these [fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img still not work and not be needed? I understand motoboot is bootloader but what is got.bin?
If you go back to Telus firmware those two files likely won't update. I recommend you always go through the motions and if they fail it is fine to continue with the other files. When Telus 5.1 is released you will likely be able to update those two files again - it doesn't seem to really matter though with the 2014 Moto X.
Ok good information one question I have to ask. Does it really matter what fastboot I use and if so what is the best one to use for this phone?
Do you mean fastboot versus mfastboot(motorola specific version) ?
It only matters with the system image which is too large for regular fastboot and required the Motorola specific version which can handle the larger files and/or the sparse files.
Exactly the answer I was looking for. Thanks a lot!
Sent from my XT1095 using XDA Free mobile app

[Q] screen locks problem with Moto G 2014

Hi everyone,
I have a problem with my Moto G 2014:
Many times the screen locks, and when i try to slide to open it, it will not open but gets locked again and again and I can't use the phone.
I had this issue with 4.4.4 and also after i updated to 5.0.2.
I tried:
1) factory reset.
2) clear cache partition.
3) I try to slide the option bar ad get to the settings but its not alway working to bypass the lock.
4) I tried also to cancel the "slide" option in the security setting to "none" but it still get locked..
what causes the issue? problem with the system? with some sensors? is it a fixable problem?
Did you try to flash stock/ custom rom?
Is your bootloader unlocked?
Have you tried re flashing the firmware. It's just a guess but your system partition may be corrupted.
Thanks you both
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
gifnooky said:
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
Click to expand...
Click to collapse
Well, restore to stock firmware with adb and mfastboot at it should be fixed.
Which model are you using? (XT1064 usa single sim, XT1068 international dual sim etc. etc)
The site for the official moto g stock firmwares is down so it is pretty hard to find a legit stock firmware file these days.
Here is one for the xt1064 http://www.rootjunkysdl.com/files/M...AWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
and one for XT1068
http://d-h.st/VOw (use the BLUE download now button not the orange download button. the orange one tries to get you to use dev host's bad download manager)
You can flash it by installing this 15 second adb installer by Snoop5
http://forum.xda-developers.com/showthread.php?t=2588979
If the latest version does not work then use 1.3
After you have everything downloaded open a terminal at the location you extracted the firmware. Reboot you device into bootloader mode by powering it on while pressing both volume buttons. Plug it into the computer and let the drivers install.
Run these commands. It is normal that the first two give you error if you are currently on 5.x firmware.
Code:
fastboot.exe flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.sparsechunk.0
fastboot flash system system.img.sparsechunk.1
fastboot flash system system.img.sparsechunk.2
fastboot flash system system.img.sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
My model is XT1063
Is there a trusted original firmware to this version?
No solution found yet after searching for 2 months .
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
gifnooky said:
Is there a trusted original firmware to this version?
Click to expand...
Click to collapse
sumondhk1 said:
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
Click to expand...
Click to collapse
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
ethanchow said:
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
Click to expand...
Click to collapse
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
sumondhk1 said:
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
Click to expand...
Click to collapse
I know the screen ghost touches is hw problem but u asked for the original firmware.

baseband missing

Hi I been flashing the CM 12.1 nightlies, starting from the mexican 5.0.2 stock firmware for a while. Suddenly, the power button and the screen got unresponsive.... i've tried to flash back to stock several times, either kitkat or lollipop, with the same results... The only different thing I noticed was when I started the bootloader menu the baseband line was empty. One of the times I flashed to stock it came back and start working correctly, but when I flashed CM again the same thing happened.
Now I have the baseband line black and the OS keeps crushing....
I tried flashing the radio only with the same results....
Any thoughts?
PS: RSD lite 6.2.4 doesn't recognize my devices so I flash with cmd and mfastboot using these commands:
mfastboot getvar max-sparse-size
mfastboot flash motoboot bootloader.img
mfastboot flash radio radio.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot erase cache
mfastboot erase userdata
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
Please help!
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
TheSt33v said:
I had a similar problem with my XT1254. I was using a modified stock 5.1 system image (since that's all we can do with our locked bootloaders...for now. Our hope lies with you, jcase and beaups!) and after months of using it without any issues, it crashed. I got it working again by using similar steps to what you did to flash 4.4.4, but with a few exceptions:
1. I used fastboot instead of mfastboot.
2. I flashed something called gbt.bin I think to the "partition" partition. I'll re-download the firmware that I used and confirm that. I was following the flash sequence in the full firmware's xml file.
3. When the phone finally booted (it seems like it took between 5-10 minutes), I went through the initial setup, and I noticed a notification that said "complete uninstall." I clicked on it, and it said that it wanted to restore the motorola sensor firmware to a previous version. I said okay, and it did whatever it needed to do and rebooted the phone.
Now the phone boots fine (phew), but the baseband line in the bootloader is still blank. It might be related, but I remember that the moto app and also the moto actions (I think?) app updated itself recently, so maybe that sensor firmware update is the cause of the problem?
EDIT: Here are my exact flash steps. Keep in mind that this is for a Droid Turbo, not the Moto Maxx that you must be using. I'm not sure if that matters.
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
fastboot flash system system.img_sparsechunk5
fastboot flash system system.img_sparsechunk6
fastboot flash system system.img_sparsechunk7
fastboot erase ddr
fastboot erase cache
fastboot erase userdata
fastboot reboot
EDIT2: I set up my 5.1 image just to see if I could replicate the crash and sure enough, once I updated Moto Actions, everything fell apart.
Click to expand...
Click to collapse
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
TheSt33v said:
EDIT3: I just noticed that on Rootjunky's video, his baseband appears blank too, so maybe it was always blank and we just didn't notice before.
---------- Post added at 10:39 AM ---------- Previous post was at 09:41 AM ----------
Did you ever fix your problem? If so, how? Because my phone is messing up again and my previous method isn't working.
Click to expand...
Click to collapse
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
andrescarre87 said:
Yeah I was Ok for a few days without the moto updates, but then it started crashing again... I don't know how to fix it... the baseband keeps going on and off in the fastboot mode and everytime it goes off the problem arise
Click to expand...
Click to collapse
That's weird. I got a warranty replacement from Motorola that appeared to be brand new and before I modified it, I checked the bootloader. Baseband was blank. So even on a stock, unmodified phone, it can be blank. Here's my thread that details everything that I tried to fix this problem: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to temporarily fix it, but it always broke again once I reflashed 5.1. I posted the system image that I made that temporarily fixed the problem, but remember that is for an XT1254, so I don't think it will work for you.
Hello Sir
I was about to update to computerfreak's .49 rom (version 1.37 that is). Prior to that I wanted to update to the latest modem, So i flashed the modem cleaner, and then the radio from firstencounter's thread
(http://forum.xda-developers.com/droid-turbo/development/droid-turbo-xt1254-bootloader-radio-t3259327)
Since then my baseband is unknown. I can't connect to wifi and my sim isn't being read
You seem to have fixed the problem? I was on computerfreaks 1.35 till now with no issues (except GPS wouldn't lock)
Hi all.
I just wanted to share my finding regarding this problem.
I realise that this may not fix the problem for everyone, but searching the forum, I have found MANY folks that have tried all the things that I have to no avail..
So I am posting this in hope that some of them might see this and hopefully cure their "Unknown Baseband", "No IMEI" and "No SIM card"
I recently upgraded to RR Marshmallow witch fixed some other problems I have had with my XT1254 Droid Turbo (Bluetooth related)
I also upgraded my Radio.img from 02r to 03r (44 to 49?)
While this fixed my Bluetooth problems and everything was running really well for 2-3 days, out of nowhere, in the middle of a phone call, I got: No IMEI, Unknown Baseband and no SIM card...
I searched the forum (and google) and have tried just about everything..
Upgrade / downgrade firmware
Install stock rom
Backup/restore EFS / IMEI partition
Different radios
A few third party programs
Loads of ADB commands (learned a lot in the process though!)
I was kinda ready to give up and buy a new phone, so I thought I might as well try something daring WITCH FIXED MY PROBLEM!!!
I sprayed a little electrical cleaner into the SIM slot and let it dry out. When I pushed in the SIM card, I felt some resistance that definitely wasn't there before! I know this for sure because I removed / inserted the SIM card a LOT of times to see if it would connect.
My guess is that there is a mechanism that pushes the SIM connection points away from the SIM card when it is being pushed in, and when it is al the way in, it will snap back up against the card. (or some other mechanism that tells the phone that a SIM card has been inserted. I don't know)
This mechanism must have gotten stuck and the cleaner must have removed whatever was keeping it from moving.
I DO NOT recommend people doing this, since it may damage your device (I suppose if you are really unlucky, it might even blow up your battery?¿)
A more gentle approach would be to pray off the back cover (haven't tried this myself, but youtube suggest this is fairly easy) and clean / massage the mechanism in a more controlled manor.
Best of luck to all of you! I hope you find a fix for your problem!
^GaMbi

Soft bricked XT1052

Soft bricked when trying to flash stock 5.1 back from CM13. Somehow managed to wipe the entire phone and now all I have access to are fastboot and TWRP recovery. I have no ROM ZIPs to access in TWRP since internal storage was wiped. I tried ADB sideload but says it can't mount /data/. My computer recognises the phone as a fastboot device but not as an ADB device.
Is there any coming back from this?
I've downloaded the retail GB stock image file for XT1052 but I can't flash the partition as I just get error 'update gpt_main version failed' 'preflash validation failed for GPT'
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I've downloaded the RetGB for 5.1 for XT1052 from here: https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1052/
But it seems to be missing a number of key files that are described in option 5 of the link you posted. Am I missing something? I'm also still getting errors each time I try to flash the partition except now CMD is just showing:
"target max-download-size: 768MB error: cannot load 'gpt.bin': no error. Any ideas? Thanks.
My only other thought at this point is to try and flash a ROM in recovery using USB-OTG. Could that work? For example, if I download stock ROM or even the CM 14 I had on previously before everything got wiped and put that on an external drive and flashed in TWRP?
varunpilankar said:
Flash stock via mfastboot.
Try this link http://mark.cdmaforums.com/MotoX-ReturnToStock.html.
Proceed to option 5.
Sent from my XT1060 Dev Ed
Click to expand...
Click to collapse
I just moved cmd.exe into my platform tools folder where everything else is and tried again to flash the partition. Instead this time I get:
C:\Android-SDK\platform-tools>mfastboot flash partition gpt.bin
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.335s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.328s
And then on the phone itself in the fastboot screen it shows:
"downgraded security version. update gpt_main version failed. preflash verification failed for GPT'. I thought this would mean the bootloader I'm trying to flash would represent a downgrade but I checked against the info.txt file in the recovery image zip and it says 30.BE which matches the 30.BE in my fastboot screen...
OK I've now got an OS. Managed to reinstall CM14 using usb-otg. Figured that was the safest bet given it was the last OS installed.
Problem I now have is that I can't get any service (I could previously on CM14 before all this happened). Is it possible that when I managed to completely wipe the phone that I would the relevant modem/radio files?
Thanks
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Sent from my XT1060 Dev Ed
varunpilankar said:
Try downloading stock file from
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
fastboot method is mentioned in the above link.
Replace fastboot by mfastboot with all its necessary components in place.
Click to expand...
Click to collapse
That doesn't have my version - xt1052.
Would this be to return my mobile service? I've got back on CM14 but all my IMEI and sim data has wiped so I can't get service. Not sure if I need to use the 5.1 factory image I have and just flash modem files. Seen elsewhere that I could try
Fastboot flash modem NON-hlos.bin
Fastboot erase modemst1
Fastboot erase modemst2
Fastboot flash fsg fsg.mbn
Would that do the trick do you reckon?
Take a nandroid backup & try doing it!
There is also a 5.1 stock zip Rom & try that too, might be helpful.
Sent from my XT1060 Dev Ed
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
hachamacha said:
Hi,
You'll eventually find your way back to 5.1 or even 4.4.4. I've broken just about every rule while I was doing some dev work on a moto x 2013 and from a beta of cm14, managed to pretty quickly get all the way back to 4.4.4 (which for me, is by far the best for a) battery and b) motion detection and c) everything works).
There was nothing after 5.1 for 2013, so there's no way you couldn't at least go back to 5.1, but there's always one way that works for you better than the rest. If that last thing didn't work, then try "liveroy's" way as in here: http://forum.xda-developers.com/moto-x/moto-x-qa/guide-faq-how-to-downgrade-5-1-to-4-4-4-t3182118 .. That way was actually based on an xt1052. I doubt if the radio files are going to make much difference heading in that direction, but are worth a shot before doing this.
I followed the first post in there and was un-"bricked" in ~20 minutes or so. Cheers // good luck,
Click to expand...
Click to collapse
Thanks. Will give that a look as I would like to know how to easily go back to stock in the event of catastrophe - I've been trying to flash back using both fastboot and TWRP but it fails every time due to 'downgrade security' etc. even though I know I'm using the same bootloader as in the stock ROM.
I managed to get my IMEI and service back by flashing
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
I've now got Resurrection Remix on as I thought I'd see if that would fix my service issues (it didn't - so still had to do the steps above). But have managed to learn a lot over the past few days to bring my phone back from death! I'm mainly used to Sony phones so this has been an experience.

Categories

Resources