I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse
Related
Hello. Well to start off I had recently rooted my Droid2 which was running the OTA GB. So I started looking for roms like I use to with froyo and the leaked GB. Was looking for something to change the battery life frame poor to great. Anyway I came upon Cyanogenmod's Rom for Droid 2 For the ota gb. I made a nandroid back up, downloaded it and was ready to flash. Seconds away in boot recovery and while i was looking for the file before I think I hit "apply update" instead of "search for zip file on scdard(or what ever sentence it says) and i got it but it started loading an update. I was like wtf kinda freaked out and I did a battery pull . Now my phone stays at the M boot logo and i have no way to go back. I heard the SBF for GB ota isnt her yet . if anyone can help I would be grateful. Plz Help
Things I've tried/
1.Battery Pull.
2.Hold power button + hold X(doesnt work like froyo Poo)
3.Tried going back with rsdlite 5.3.1 with moto drivers(it won't show my device ;'( )
4.Left this message on xdadev / please help
SOLVEd
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
T3viin said:
{[SOLVED]}
Used bootloader way in by holding power button and up. rsd that way and got it to work.. Guess this is to who ever made my mistake . heres the solution
Click to expand...
Click to collapse
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Charge your battery in another phone like yours. Borrow someones spare battery. Take battery to verizon store and see if they can charge it somehow. There is a thread on here somewhere on how to do a hack job on your cable and hook the wires directly to your battery and charge it independent of the phone. I can't post a link so I hope you can find it by searching.
Sent from my DROID2 using XDA App
dmeadows013 said:
I just tried this on my friend's D2 (I am very experienced with the inc), and I seem to be having the same problem. I have tried Sbfing, but RSDlite will not recognize the phone. I have booted to recovery, nothing (Stock recovery), and the bootloader (Says too little charge)
What can I do?
Click to expand...
Click to collapse
I've had this problem 4 times in the last week. I used a terminal based OS to SBF using ADB.
And in the same step I re rooted my phone. Whole thing takes about 15-20 minutes.
The steps are on the CMWiki.
This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App
Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.
what rom was the phone running when you had the original issue?
Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.
I have the same Problem with my Defy+ what can i do?
I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.
Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
ybuedts said:
So i got the new 4.3 update notification on my phone today. Eager to get it i started the installation (battery level was about 90%). After a while the installation went into a constant reboot, always went untill halfway of the progress bar and then phone went off and started again to same screen. I knew it was ****ed up so i went into recovery mode but then it starts to do the update again and i got the "ERROR" message. So i went into recovery again and now i get the "NO COMMAND". I was running 4.2.2 with everything stock, device was not even rooted...
Any ideas?
Click to expand...
Click to collapse
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
After that, you can relock your bootloader if you want.
abaaaabbbb63 said:
Unlock your bootloader, and flash the stock 4.3 image manually. Download it from here
After that, you can relock your bootloader if you want.
Click to expand...
Click to collapse
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
ybuedts said:
I've got very basic knowledge of android so i don't really know what to do... I imagine if i flash the stock manually i will lose all my data? Because in that case i might aswell go to the store and ask a new one since i still have my warranty...
Click to expand...
Click to collapse
Ok, if you have a store nearby, go to them. They will fix it properly. With basic knowledge, it's pretty dangerous.
Similar Prob
Hey guys,
I have a similar problem. Tried the upgrade to 4.3 and it stucked.... well now i constantly see the Google-X-symbol and thats all. Tried to unlock the bootloader via developer tools (for later flashing to Stock ROM) but there's no connection. Tried to replug it, etc.
When I start the bootlaoder (via Vol-Down and On-Button) I can choose the options (but recovery is not possible) But hm, the bootloader doesn't seem to be broken.
Can anyone help me? I'm not really a developer (although I work for a software-company) but I already unlocked and rooted devices and I have experiences in changing deep settings.
Help would be great!!! I don't want to sent it to google - I am lost without my S-Phone....
Thanks!
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
waynehardy said:
I have a similar issue, I found the update notification on my phone, went ahead with the update and it took ages! The battery was nearly full and the battery fully discharged while it was updating. I was at a friends house so no charger. When I got home I fully charged the phone and switched the phone on and got the nexus cross animation and thats all. I tried to enter recovery mode but got the no command icon.
Any help would be appreciated, I do have experience of rooting and flashing custom roms on my HTC Desire but have not touched the nexus since I got it. So everything on the phone is stock
Heres interesting, My wife tagged me into a facebook post telling peeps my phone was out of order, as she did it, the facebook app on my phone notified me of the tag!! Still got the nexus boot animation showing on the screen!
Click to expand...
Click to collapse
Ha, that's exactly the same issue.... Thank God I'm not the only one (sorry )
I got the "no command" error after my update this morning. My battery was pretty low, but the phone was docked. I just left the phone alone while I came here to investigate, and it eventually rebooted itself. Then it stuck on the loading X for around 5 minutes, but now it is optimizing my apps. Looks like it is going to work after all.
Mine has been on for a while but its not seeming to play. what mkes no sense is that it is switched on in the background but the nexus animation is the only thing it shows
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
justin1701 said:
I'm having the exact issue. I got my update notification this morning and it failed, going into an endless loop. I called google and they didn't know what was happening, so they're sending me a new phone. I don't want to wait for the new one, so I'm trying to fix this one still. I can start the bootloader, but I can't get into recovery. Is there a way to correct this through ADB?
Click to expand...
Click to collapse
When you get to the screen with "NoCommand" on it.
1. Press and hold power button
2. Then once you pressing the power button, press the Vol - Up
Thats it
OrangeNik
Here is the fix for everyone
Ok, I just got off a chat with an Asus rep.
Step 1: Hold the power and volume up/down to get the android with the "start" option
Step 2: Use the volume down to select "recovery mode" It will now power off and power back up with the dead android and "no command" below it
Step 3: While holding the power button TAP, but DO NOT hold the volume up button. You will get an option to wipe all data. Do that.
Blammo the world's problems are solved
LG Nexus 4 E960
Work perfectly for me
Nexus Root Toolkit v2.1.4
I can't post a link because I don't have 10 posts!!!
Need help, going to try and give as much detail as possible so sorry for the long post. I dropped my phone a few weeks ago and the LCD broke so got a refurb warrenty replacement phone. Att S4 - got it 12/24 and rooted using towelroot on NJ4. Everything was fine until sunday or monday when I realized my Beautiful Widget weather was still stuck in NJ where i had been a few days ago and the last time I'd turned locations on, thinking location was still just GPS like it used to be. read up on all the location info of power saver vs full accuracy, and decided I would just set my widget to my home zip code. Within 24 hours i started experiencing random reboots of the phone, with the occasional boot loop. tried turning the location settings back off and that helped for about a day before starting having reboot / power off issues again.
So last night I decided I would give up and try and do a factory reset. First i wiped the cache from stock recovery. Then the phone wouldn't boot past the att screen at best. So I went back into stock recovery and did a full reset. at this point the phone will no longer get past the Custom Samsung boot animation. I tried using the one-click unbrick tool, but my phone wasn't coming up as a USB option and I haven't been able to find any additional trouble shooting to get that to work.
So next I decided to Odin the stock unrooted firmware, which i believe was NB1. Now i can't get the phone into recovery at all. It is hit or miss if the phone will even get to the custom boot animation, but immediately shuts down from there. I can still get into download mode at times. Wondering if there may be a hardware issue either my battery (which was from my original phone) or the power button on the refurb because there were points last night when i would have to hit/hold the power button 5 or 6 times before the phone would do anything, regardless of what other buttons i was or wasn't holding down. that seemed to improve once the phone cooled down for a while.
I really have no idea what else to do. Based on everything i've read the phone should be working at this point or should be totally bricked. any guidance is greatly appreciated. I would try and just warranty it again and claim they sent a bad phone but of course it boots just enough to show the custom animation, even after i odin'd on stock. HELP!!!
dingbat005 said:
Need help, going to try and give as much detail as possible so sorry for the long post. I dropped my phone a few weeks ago and the LCD broke so got a refurb warrenty replacement phone. Att S4 - got it 12/24 and rooted using towelroot on NJ4. Everything was fine until sunday or monday when I realized my Beautiful Widget weather was still stuck in NJ where i had been a few days ago and the last time I'd turned locations on, thinking location was still just GPS like it used to be. read up on all the location info of power saver vs full accuracy, and decided I would just set my widget to my home zip code. Within 24 hours i started experiencing random reboots of the phone, with the occasional boot loop. tried turning the location settings back off and that helped for about a day before starting having reboot / power off issues again.
So last night I decided I would give up and try and do a factory reset. First i wiped the cache from stock recovery. Then the phone wouldn't boot past the att screen at best. So I went back into stock recovery and did a full reset. at this point the phone will no longer get past the Custom Samsung boot animation. I tried using the one-click unbrick tool, but my phone wasn't coming up as a USB option and I haven't been able to find any additional trouble shooting to get that to work.
So next I decided to Odin the stock unrooted firmware, which i believe was NB1. Now i can't get the phone into recovery at all. It is hit or miss if the phone will even get to the custom boot animation, but immediately shuts down from there. I can still get into download mode at times. Wondering if there may be a hardware issue either my battery (which was from my original phone) or the power button on the refurb because there were points last night when i would have to hit/hold the power button 5 or 6 times before the phone would do anything, regardless of what other buttons i was or wasn't holding down. that seemed to improve once the phone cooled down for a while.
I really have no idea what else to do. Based on everything i've read the phone should be working at this point or should be totally bricked. any guidance is greatly appreciated. I would try and just warranty it again and claim they sent a bad phone but of course it boots just enough to show the custom animation, even after i odin'd on stock. HELP!!!
Click to expand...
Click to collapse
Odin back to NJ4 :/ You can boot into download mode so that means your phone isn't hard bricked. If that doesn't work than I think I'll have another idea. Oh, by the way, what ODIN version are you using? If its 3.09 put the .tar in the AP section and for 3.07 and below its PDA. Also, make sure it's the correct image. Anything below NB1 doesn't work for KitKat users.
Sent from my SGH-I337 using XDA Free mobile app
Hi Guys,
I was randomly using my Moto X Pure phone for a while and shut down and when I tried to power it on again it was stuck on the logo screen. I understand that this is a Soft Brick and there's apparently a way to fix this, I'd like someone to help me out with what I should exactly do and what relevant files do I need to solve this problem.
Thanks in advance!
http://forum.xda-developers.com/moto-x-style/help/guide-motorola-moto-x-purestyle-xt1575-t3348673
DejektedZ76 said:
Hi Guys,
I was randomly using my Moto X Pure phone for a while and shut down and when I tried to power it on again it was stuck on the logo screen. I understand that this is a Soft Brick and there's apparently a way to fix this, I'd like someone to help me out with what I should exactly do and what relevant files do I need to solve this problem.
Thanks in advance!
Click to expand...
Click to collapse
I should preface this with I don't mean any offense.. but I find it quite hard to believe you were just "using my Moto X Pure phone for a while and shut down and when I tried to power it on again it was stuck on the logo screen ". Did your battery die? If that's the case you need to hook it up to a charger for a while (30min-1hr) and then unplug it and then try to turn it on. I don't believe quickcharge works in the base states of the phone so it may take a while to get sufficient charge to actually boot android on the phone.
If your phone "suddenly" doesn't boot then 1(or more than 1 I suppose) of a few thing have happened. #1 your bootloader is corrupted (unlikely) #2 your kernel/boot is corrupted. #3 your system partition is corrupted(or you used root and did something bad, or flashed something not quite right with twrp) or #4 you have a hardware failure. Hopefully it isn't #4.
If you're unrooted then I bet your phones battery died and needs some time on a charger before it will fully boot again... or worse you have an actual hardware problem (hopefully not)
if you are rooted then maybe your kernel or system has been screwed up.. However, It's very unlikely even with root that either of those thing "just happened" though. You would have had to be messing with something in the boot and/or system. If that's the case tell us what you were doing.
If you are rooted though... your bootloader is unlocked. So grab the "factory image" for your phone and boot to the bootloader and completely reflash the phone. You can try not doing the "erase userdata" to keep your installed apps/settings, or just flashing boot and system and seeing if it works... but if it still doesn't work then nuke it all from orbit and start again.
@nxtime posted a link in the previous post with some instructions.
Good luck!
DaMadOne said:
I should preface this with I don't mean any offense.. but I find it quite hard to believe you were just "using my Moto X Pure phone for a while and shut down and when I tried to power it on again it was stuck on the logo screen ". Did your battery die? If that's the case you need to hook it up to a charger for a while (30min-1hr) and then unplug it and then try to turn it on. I don't believe quickcharge works in the base states of the phone so it may take a while to get sufficient charge to actually boot android on the phone.
If your phone "suddenly" doesn't boot then 1(or more than 1 I suppose) of a few thing have happened. #1 your bootloader is corrupted (unlikely) #2 your kernel/boot is corrupted. #3 your system partition is corrupted(or you used root and did something bad, or flashed something not quite right with twrp) or #4 you have a hardware failure. Hopefully it isn't #4.
If you're unrooted then I bet your phones battery died and needs some time on a charger before it will fully boot again... or worse you have an actual hardware problem (hopefully not)
if you are rooted then maybe your kernel or system has been screwed up.. However, It's very unlikely even with root that either of those thing "just happened" though. You would have had to be messing with something in the boot and/or system. If that's the case tell us what you were doing.
If you are rooted though... your bootloader is unlocked. So grab the "factory image" for your phone and boot to the bootloader and completely reflash the phone. You can try not doing the "erase userdata" to keep your installed apps/settings, or just flashing boot and system and seeing if it works... but if it still doesn't work then nuke it all from orbit and start again.
@nxtime posted a link in the previous post with some instructions.
Good luck!
Click to expand...
Click to collapse
No joke, I was actually on snapchat for a while and it randomly shut down. I initially tried to turn it back on and it was getting stuck on the boot screen. First, I wiped my cache partition through recovery and it didn't work. Then I factory reset my data and same result. I left it on the charger until it was 100% and tried again, still nothing.
I haven't rooted it or tried to at all so I'll have to rule out #3, out of the other three which one could be the most likely?
If it isn't a hardware failure (sorry for being such a huge noob), should I restart bootloader in recovery or unlock my bootloader and reflash the software by downloading factory image?
I talked to motorola and they said they will issue a replacement, but I figured if it's a software problem then I could reflash it..so there's another option but I live outside the U.S it's gonna take while to process it.
Thanks alot dude Really appreciate your help.
You can get a factory image from moto. I would try that.