I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
doctor_evil said:
I need some help. My phone is capable of booting into fastboot mode, but doesn't seem to be able to boot normally.
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
In the fastboot screen whats version is your booloader ?
Sent on my Gummy running Lenoto X
looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.
doctor_evil said:
looks to be the one that I shouldn't have installed the OTA update. why in the F would they send me an update that isn't compatible with my bootloader version?
Well they're getting it back for a repair, I didn't pay 399 for a developer edition phone just to have a dang paperweight because they sent me an incompatible OTA update.
Click to expand...
Click to collapse
They didn't send you a incompatible boot loader, the ota's always come with a new boot loader, so what I like to know is, what version is your boot loader , its Motorola's fault that you accepted the ota while having a custom recovery, had you read my thread here http://forum.xda-developers.com/showthread.php?t=2639102
You wouldn't have any issues.
If you don't want my help, thats fine by me, getting tired of this ota crap anyways
Sent on my Gummy running Lenoto X
Clearly you don't really want us to help or you would have answered the previous posters question. You also gave no details into if you had rooted the phone or unlocked the bootloader.
From the bootloader screen select the "factory" option.
I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk
edthesped said:
I may agree with the op here. Moto supplied me with a 4.4 version for my dev ed. If I take an update, have an issue and moto still only provides 4.4 sbf what a I supposed to do?
However, OP you do need to supply more information as we can only speculate as to what your issue is.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X
flashallthetime said:
Its not moto's fault, its up to the user to make sure you read the sticky notes, read the threads and search, moto puts out the ota for unrooted users.
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
However I purchased a Dev Ed phone. Motorola supplied me with a recovery firmware to restore my device to stock. I therefore expect the Factory supplied firmware to not brick my phone. If Motorola makes changes in an update that would cause previous versions of their software to damage phones when used as supplied Motorola needs to bear some of the responsibility. They can build a failsafe into the update that would prevent an attempt of a downgrade, supply upgrades that can safely be downgraded, add some kind of notification or not market "Dev Ed" phones for mass consumption.
Sent from my SM-P600 using Tapatalk
But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Tx Redneck said:
But the update clearly and concisely says, YOU CANNOT roll back to a previous firmware after applying said update.
Onus is on the user at that point.
Click to expand...
Click to collapse
Does it? I never saw that going to 4.4. As long as they put a new sbf up all should be fine.
Sent from my SM-P600 using Tapatalk
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Did you call Motorola?
Sent from my SM-P600 using Tapatalk
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.
doctor_evil said:
UPDATE:
I tried again to select the factory option in fastboot and unlike the previous times I had tried, this time seems to have fixed it. It booted up into Android OS. I think I'll try the OTA once again and see if this time is more successful, as if it screws up again I have a repair rma number and a fedex shipping label, but hopefully it does better this time.
Click to expand...
Click to collapse
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.
doctor_evil said:
I have version 30.B2 according to the fastboot.
and I had originally flashed my phone with TWRP custom recovery and had rooted my phone. I used rsdlite to flash back to the current stock version then when after setting up wireless,etc. on my phone I checked for the OTA and it said that there was a new version that fixed battery issues,etc. so I downloaded it, then restarted. after it finished flashing and rebooted again is when the flashing android red triangle error message started happening. I tried to flash back to the previous stock version, and even tried re-flashing twrp custom recovery so I could go in and do a factory wipe and clear dalvik and cache, and data but nothing worked.
Click to expand...
Click to collapse
Maybe try this out.. option 2 http://forum.xda-developers.com/showthread.php?t=2446515
doctor_evil said:
ok OTA successful this time.
does anyone know if it's possible to boot the moto-x off a custom recovery using fastboot like we could for the galaxy nexus? I'd like to get root reinstalled but I don't want to mess with the current recovery, which should help I would think in regards to being able to install OTA updates without major issues.
Click to expand...
Click to collapse
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.
nhizzat said:
Unfortunately, I don't believe it's possible to fastboot boot recovery. It's how I did everything with my Galaxy Nexus and Nexus 7. I was disappointed to find out it isn't possible with the Moto X Dev edition even though I didn't buy one.
Click to expand...
Click to collapse
has anyone tried it with the google play edition of the moto-g? I'm wondering if there is a way to convert from a regular retail rom over to a GPE rom for the moto-x after google starts selling it. I remember reading about them going to sell a GPE of it. Hopefully the GPE rom would be friendlier than the retail rom
doctor_evil said:
I am seeing the android laying on it's side with a red triangle with an exclamation point, this keeps blinking on and off. I've tried using rsdlite as well as the flash back to stock options in the moto-x toolkit and nothing is working. I've also cleared the cache and userdata folders but nothing has worked.
Is there a way to fix this or will I need to send my phone back to motorola for a repair?
Click to expand...
Click to collapse
I know you have fixed this now, but if you see the android with the red triangle and ! use the key combination pwr & up vol. That gets you into stock recovery and from there you should be able to boot up.
Related
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
matt99017d said:
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
jayboyyyy said:
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
Click to expand...
Click to collapse
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
matt99017d said:
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
next time just flash the system.img as well and you should have been good to go without losing any data.
I am rooted on vzw 4.4 and have been having trouble returning to stock, to say the least. I tried using the toolkit and it seems to go through the motions, but when the phone finally boots into android it's like it just did a factory reset but I'm still on the 4.4 Rom I was previously on. I even tried installing 4.2.2 to make sure, and when it rebooted after, sure enough I was still on 4.4.
For some reason it doesn't seem to install the Rom. It definitely downloads through the toolkit, but I can't figure out why it won't install.
Oh and to top it all off, I somehow got a notification for an OTA, and being a little tipsy I thought why not, so I tried taking the OTA. Obviously that was dumb because of the recovery issue(?)...So now it's in a bootloop.
I'm trying to wrap my head around the whole "not having a custom recovery" thing. I much prefer actually having cwm or something instead of having to use adb.
If anyone explain how to get back to stock, or just point me to a comprehensive guide for semi-noobs, that would really help lower my blood pressure!
Sent from my SCH-I545 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2603358
A short search or reading the stickies and you would've found this much sooner.
Sent from my N5 cell phone telephone....
This is why I dislike toolkits.
Download the 4.2.2 post-camera or 4.4 OTA sbf file and read up on RSDLite.
nhizzat said:
This is why I dislike toolkits.
Download the 4.2.2 post-camera or 4.4 OTA sbf file and read up on RSDLite.
Click to expand...
Click to collapse
Thanks, I'm going to do this. But regarding the recovery, will I be able to take OTAs after returning to stock, since the sock recovery seems to not exist on my phone anymore?
If you use the full sbf and rsdlite to flash your phone it will be returned to 100% stock condition with the factory Motorola recovery. This means you can accept OTA's in the future without any problems.
Steve-x said:
If you use the full sbf and rsdlite to flash your phone it will be returned to 100% stock condition with the factory Motorola recovery. This means you can accept OTA's in the future without any problems.
Click to expand...
Click to collapse
Thank you!
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
Hasn't this already been discussed in the update thread? Flash the stock ATT JB, then accept the update.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
devilsking said:
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
Click to expand...
Click to collapse
Same here!
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
magocop said:
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
Click to expand...
Click to collapse
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
audit13 said:
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
Click to expand...
Click to collapse
Did you have to call Bell to get that customer recovery? And where can I get one at?
skeevydude said:
Did you have to call Bell to get that customer recovery? And where can I get one at?
Click to expand...
Click to collapse
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
audit13 said:
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
Click to expand...
Click to collapse
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
skeevydude said:
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
Click to expand...
Click to collapse
No worries. Good thing you brought the error to my attention; otherwise, Bell would start receiving requests for the "customer" recovery files:laugh:
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
I probably did when i first figured out how to use custom roms i was trying a whole bunch of them but that was awhile ago and now i dont remember how to flash a stock recovery or where to get it and i did awhile ago use RSD Lite to flash a stock rom onto my phone but that is the last thing I did and know its been sooo long i dont remember how any help from anyone would be greatly appreciated and sorry i have not got back to this post in a few days been busy doing other things but once again if anyone could help me it would be appreciated
Thanks
- Bart
Try using Myth Tools to flash back to stock, take the update, install a custom recovery, and flash a KK ROM.
http://forum.xda-developers.com/showthread.php?t=2262726
So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.
Ill try to keep this short. So my stock Moto X is for some unknown reason stuck in a boot loop. The only thing I can do is get into the fastboot by holding the vol down key however the "Barcodes" option is the only one that will do anything other than go back into this loop. Recovery / Factory / BP Tools all try to start but never make it past the Motorola splash screen, it stays there about 20 seconds or so and reboots.
It is running on 4.4.4 and from my understanding the bootloader can not be unlocked. I spent the better part of the last couple of days trying to figure out if there is any hope of bringing this thing back to life but I am still unsure. I was thinking maybe I could reload the official 4.4.4 but the only place I can even find it anywhere is on MotoFirmware but I cant get it to complete the download, I have tried numerous times with 3 different browsers.
I guess what I am trying to find out is if there is any way to reload the stock firmare or even load a custom ROM or something else I am not aware of yet?
Thanks much in advance for any help you can provide, it will certainly be much appreciated.
rikzjr said:
Ill try to keep this short. So my stock Moto X is for some unknown reason stuck in a boot loop. The only thing I can do is get into the fastboot by holding the vol down key however the "Barcodes" option is the only one that will do anything other than go back into this loop. Recovery / Factory / BP Tools all try to start but never make it past the Motorola splash screen, it stays there about 20 seconds or so and reboots.
It is running on 4.4.4 and from my understanding the bootloader can not be unlocked. I spent the better part of the last couple of days trying to figure out if there is any hope of bringing this thing back to life but I am still unsure. I was thinking maybe I could reload the official 4.4.4 but the only place I can even find it anywhere is on MotoFirmware but I cant get it to complete the download, I have tried numerous times with 3 different browsers.
I guess what I am trying to find out is if there is any way to reload the stock firmare or even load a custom ROM or something else I am not aware of yet?
Thanks much in advance for any help you can provide, it will certainly be much appreciated.
Click to expand...
Click to collapse
What carrier are you on?
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
rikzjr said:
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
Click to expand...
Click to collapse
HAve you wiped cache or factory reset in your stock recovery? When you boot to recovery do you get the dead android guy on his back with a triangle?
You've checked here for firmware?
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
Otherwise, continue trying the site you've tried. It's bound to work eventually. ?
Travisdroidx2 said:
HAve you wiped cache or factory reset in your stock recovery? When you boot to recovery do you get the dead android guy on his back with a triangle?
Click to expand...
Click to collapse
Unfortunately I cant get into the stock recovery. It never gets to the injured android guy, gets hung up on the Motorola logo then reboots.
Thanks Darth I will check there.
rikzjr said:
Verizon.
It seems the more I am reading the more it is looking like I am likely out of luck.
Click to expand...
Click to collapse
The Verizon XT1060 Retail and Moto Maker versions use the same Rom/Recovery Images as the Verizon (VZW) Developer Edition phones. The the recovery images are available by request directly from Motorola. Visit -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images Once you request you will get a link from Moto to down load it. NOTE: it can take 5 min to 24 hours for the link to hit your email mailbox.
You can flash by following Method 2 at -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 (there are steps included which will erase all your data/apps from the phone). Please use mFastboot for All commands, not just flashing system.
However, I recommend flashing by following Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html It has a few extra steps, and a few different ones.
Always make sure you have the latest Android SDK/Platform Tools installed, along with the latest Moto device drivers, and the latest mFastboot. (If you need them, they are listed in the pre-req sections on http://mark.cdmaforums.com/MotoX-ReturnToStock.html ) If you get an error, please capture it, and post what it says.
Since you have 4.4.4 on there, yes you are out of luck from the stand point of unlocking your bootloader, and therefore can't root your phone or flash custom recovery or rom. And do NOT attempt to downgrade your rom! Since you say you have 4.4.4 on there, only use 4.4.4 SBF when flashing.
But you are not out of luck in that you can still flash STOCK Moto Signed Roms. So if its just a software issue, flashing back to stock moto Rom could help fix it. However, since you don't say what was done leading up to the issue, I must say that if this problem just "appeared on its own" and you weren't trying to flash anything, downgrade anything, use the older root processes, etc.. then you may have a hardware issue. BUT if you were trying to downgrade, use the old root processes, etc.. then you might not be able to fix the phone.
Hey KidJoe, Thanks much for the info, I really do appreciate it.
This particular phone was send to me from Motorola as a repair replacement for my original which I managed to drop and break the screen on. Totally my fault so I had no problem paying there $110 repair fee.
I do have to agree there is likely a hardware issue as I had never attempted any kind of modification at all to this phone. I was in the middle of a call when it just restarted for no reason at all. At first the phone would boot all the way up as it normally would but freeze after about 30 seconds then reboot. After reading a bit I tried to boot into the stock recovery to clean the cache and factory reset if I needed to however the first time I tried to boot into the stock recovery it just hung on the Motorola logo then rebooted. Now that is all it will ever do.
Thanks again for all the useful info for all of yall. I really do appreciate it.
rikzjr said:
This particular phone was send to me from Motorola as a repair replacement for my original which I managed to drop and break the screen on. Totally my fault so I had no problem paying there $110 repair fee.
Click to expand...
Click to collapse
How long ago did you get the replacement? Also, what was the purchase date of your original X?
i.e. are you still under the 1yr warranty of the original phone purchase, or the refurb you got for $110 might have a 30-90day warranty on it.
You can still try flashing the stock 4.4.4 rom on there. it MIGHT work. Its worth a try, especially if its completely out of warranty.
KidJoe said:
How long ago did you get the replacement? Also, what was the purchase date of your original X?
i.e. are you still under the 1yr warranty of the original phone purchase, or the refurb you got for $110 might have a 30-90day warranty on it.
You can still try flashing the stock 4.4.4 rom on there. it MIGHT work. Its worth a try, especially if its completely out of warranty.
Click to expand...
Click to collapse
Original purchase date was more than 1 year ago now. The refurb replacement i just received the day before Christmas.
At the moment I am waiting to hear back from Motorola, hopefully they will just replace this one and all will be good.