First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
sirlancealot77 said:
First of all my Moto X is a stock nothing has been modified. My provider is Verizon running the latest version of android as far as I know.
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone. I first thought it was in an infinite boot loop because no matter what I did from the phone it would not get off that screen. I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android. The battery is now all the way drained and will not charge it seems. The battery is at 0% screen appears sometimes plugged into the charger then the Motorola symbol screen with the powered by android screen will come on until the phone runs out of power. Mind you this is while the phone is connected to the charger via the wall outlet. Also sometimes the phone boots up normally but after 10-60 seconds the phone turns off and returns to the Motorola symbol screen with the powered by android at the bottom.
I have been trying all day to get it to do some things. I have successfully gotten in to boot in safe mode and it still powers off and returns to the Motorola screen with the powered by android. I have got it to boot in recovery mode and I wiped the cache. I have not done a hard reset yet because I cant get it to go past the Motorola screen with the powered by android at the bottom.
I said what the heck and tried to flash a new ROM onto the phone but the phone isn't detected on the computer by gda so I never did anything with flashing.
Any solutions would be much appreciated.
Click to expand...
Click to collapse
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Not modified.
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
I haven't done any modifications to the phone or had anyone do anything to it. Maybe this is the animation screen it is getting stuck on the big M and the powered by android at the bottom? Would you still suggest flashing the system partition?
Q9Nap said:
the stock logo/bootanimation does not say "powered by android", so if yours does, it is modified.
if it doesn't get past the boot logo, you will likely need to flash at least the system partition with fastboot or rsd lite. although, if your battery is very low, flashing will probably not work. here is a solution to allow flashing with a low battery:
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
if it does get past the boot logo, but boot loops on the animation, you probably just need to wipe data and cache in recovery (same as hard reset from the settings menu).
Click to expand...
Click to collapse
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
So any solutions?
Cyphir said:
This in incorrect. Motorola recently updated their apps and in turn changed the boot logo and animation. it is all over the forums.
Click to expand...
Click to collapse
ok, thanks for the correction.
i'm running heavily debloated stock with custom logo and animation, and don't spend a lot of time on the forums.
the information on how to recover from a brick is correct.
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
kj2112 said:
If you didn't modify anything at all....then its probably an app you loaded recently. Perhaps one NOT from the play store???
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
Click to expand...
Click to collapse
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
sirlancealot77 said:
I booted in safe mode that doesn't run any applications except the necessary applications and it restarts about 10-60 seconds in. The time varies.
Can I buy that piece to act like a factory cable locally?
Click to expand...
Click to collapse
I am facing the same problem you are facing? Did you find a solution? How did you boot into safe mode?
sirlancealot77 said:
I tried going into the boot options by holding the power button and the volume down screen this was successful, but selecting any of the options form the list would result in the phone returning to the screen with the Motorola symbol on it and powered by android.
Click to expand...
Click to collapse
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
sirlancealot77 said:
The problem I'm facing is that my phone is stuck on the Motorola M and powered by android screen when you first start the phone.
Click to expand...
Click to collapse
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
JulesJam said:
Are you using volume up to select an option? This sounds like you are using power to select - power does not select it instead reboots your phone.
---------- Post added at 02:54 AM ---------- Previous post was at 02:52 AM ----------
Download and install Motorola Device Manager on your computer. Then put your phone in bootloader mode, then plug it into your computer and start MDM. It should attempt to repair your phone.
Click to expand...
Click to collapse
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested but I do see the advantages of getting it right away for safe keepings. I always make sure to have a copy of my most recent images to return to stock. I have always used fastboot or Mfastboot since the gnex, I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Travisdroidx2 said:
Question, since you have experience with MDM. Do you need to be fully stock to use MDM. For example if I have TWRP will it just write over my previous images or will it fail like a OTA would?
Click to expand...
Click to collapse
I believe it will fail.
---------- Post added at 06:26 PM ---------- Previous post was at 06:24 PM ----------
Travisdroidx2 said:
I agree getting the stock images right away would be nice. I have always received them from Moto within a day when requested
Click to expand...
Click to collapse
From what I am reading on the Motorola forums, Motorola has still not produced the 5.0 stock images, just kit kat.
---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------
Travisdroidx2 said:
I stay away from toolkits, but it sounds like MDM is Moto's version of their toolkit?
Click to expand...
Click to collapse
I don't know what your definition of a tool kit is but MDM is a piece of software produced by Motorola that can run some sort of diagnostic on your phone and either update it to the latest version of the software or repair it if your system is damaged.
Related
So I have a rooted Atrix HD that I tried to restore to stock using the original fastboot files from this thread:
http://forum.xda-developers.com/showthread.php?t=1853522&page=2
I ended up getting error messages with the 1st xml file so I used the modified one in Post #14 of the same thread.
Phone appears to flash properly but gets stuck at AT&T logo and RDS makes me power cycle the phone after an eternity.
When I do and get back into fastboot it says pass and thinks everything is good.
Bad news for me is I'm stuck at the AT&T logo and can't move forward.
I can still get into boot mode selection menu so that appears to be good but I'm at a loss on how to recover this thing into a working phone again.
Anyone have any insight?
Battery life was right around 50% when I started.
Maybe RDS puked since it wasn't at 75%?
Any help would be greatly appreciated.
Make you are using the latest version of RDS 6.1.4 and make sure that your cable is perfect and that your phone is detecting properly.
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
windago said:
I think I figured out part of my problem.
Used the modified xml file for 144 with the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file.
RDS lets it flash but never gets past the AT&T logo.
Now if I try to go back and flash with the right file for the modified XML I get 1/24 flash partition "gpt_main0.bin" -> Phone returned FAIL.
I think I might have borked this phone......
Click to expand...
Click to collapse
That fastboot is not for Retail AT&T devices.
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
jics91 said:
What is the BP tools you mentioned? Because I've known that it's imposible to charge the phone while it is stcuked into bootloop or even being in the Bootloader screen.
Click to expand...
Click to collapse
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
windago said:
BP Tools is the fifth option available when I boot into the boot mode selection menu by pressing Vol Up/Vol Down + Power.
Boot Mode Selection Menu (10.9B)
Available Boot Modes:
Normal
Recovery
AP Fastboot
Factory
BP Tools
I ended up plugging the phone into my Galaxy S3 wall charger last night and then selecting BP Tools when I entered the Boot Mode Selection Menu.
A simple battery icon appeared telling me I had 9% battery left.
This morning after keeping it plugged in all night I had 100% battery.
As I stated earlier after a full charge I was able to flash using RSD lite and now have a working phone again.
Click to expand...
Click to collapse
Congrats. I know exactly how that feels. I was in a similar situation not too many days earlier! It is a little sad that there is very little help online when you get stuck when trying something on this phone. You end up having to figure things out by yourself.
windago said:
Well after booting phone into BP tools to let it charge all night I attempted to reflash this morning with a full battery and a new USB cable using the MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip file and we're back in and now on 4.1.1.
Time will tell if we're back to normal for good.
Click to expand...
Click to collapse
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
ReverseZero said:
So flashing this worked for you? I think someone tried this a week or so ago and it bricked their phone.
Sent from my MB886
Click to expand...
Click to collapse
Please no one try that file... it will only work on bootloader-unlocked Atrix HD devices since it is not a build meant for retail AT&T devices.
Makes sense. Don't think I'll be trying that.
Sent from my MB886
As mattlgroff stated:
Please do not flash the file I linked to/reference to in my OP.
He's a developer and has much more insight into the workings of these files then I do.
I'm not sure why mine worked but I defer to his statement about not flashing that particular file.
I was on stock JB. Rooted with new exploit. Installed bootstrap and custom ROM. Wanted to get back to stock, so I uninstalled bootstrap, and flashed MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27-release-keys-ATT-US_BuildA.xml.zip.
RSD failed with 'getvar' and 'oem'. I then edited the xml, removed 'getvar' and 'oem', and retried the flash. RSD failed at system.img.
I then booted the phone into fastboot and did the whole thing manually thru fastboot and terminal. This time everything went through okay. I rebooted the phone into stock recovery and erased cache. But now the phone is stuck in bootloop on the red m logo.
What am I missing?
I am having trouble to flash back to stock ICS with RSD lite everytime i use it and connect my phone it says USB connected but that is it. I cannot find the associated file anywhere to flash back to stock any ideas?
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
I've heard it called a "sponge" I like that lol
shard111 said:
I think they say as long as you can get to the BOOTLOADER it's not a hard brick. But as far as the issue itself, I have no idea. You said you flashed the factory images and it still didn't help?
Click to expand...
Click to collapse
coldconfession13 said:
U manually flashed the images correct? Any errors when flashing? Are you using the flash all bat script or flashing each file separate?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
rootSU said:
Its all BS, there's not really such a thing as a soft. A Brick is a Brick. If your phone is bricked, the only fix is to send it for repair so the manufacturer can fix it. If it can be fixed without doing that, its not a brick.
Click to expand...
Click to collapse
i flashed each file separately yes no errors when flashing everything went through okay but still wont pass google screen
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
coldconfession13 said:
If it can stay connected while flashing. Does it reboot when connected like charging and stay in bootloop?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no.
but after flashing the factory img, you might have to wipe data for it to boot.
jeromechrome1 said:
They say once your device is turning on, its not a hard brick, well explain this. My motorola Nexus 6 won't boot, when I try to power it on, it shows the Google logo then shuts off immediately. When I plug in the charger from a complete power off, the white battery sign keeps flashing, it shows for 1 second then shuts off then repeats the cycle of showing the battery sign then shutting off. It boots into bootloader/fastboot mode fine, and I have tried flashing the factory image, forced flash each partition individually, YES ALL OF THEM, YES I HAVE THE LATEST SDK YES THE LATEST FASTBOOT AND ADB, YES I CHECKED THE MD5 OF THE FILES, YES I USED DIFFERENT CABLES PORTS AND COMPUTERS. it flashes fine in terminal all the files go through with result ''OKAY'' but it still shuts off immediately while showing the first google logo after i reboot. It won't even boot into stock recovery after the flash, it just shuts off after the google logo. i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C. This isn't my first nexus, in know that flashing factory image should fix 99% of issues, ive been flashing phones and rooting for years and i know that nexus devices are somewhat impossible to hardbrick. i made sure to exhaust every option i knew of before posting here, Ive tried the toolkit and its options countless times ive had many sleepless nights now over this. Please help.
Click to expand...
Click to collapse
NONE of this suggests that your phone is a brick. In fact, it all proves that it is NOT a brick.
*which is not to say that it isn't BROKEN.
"i tried with costum revovery same result. i tried 5.0 LRX210 and 5.1 LRX22C"
Let me ask you this; did it reboot when you booted into a custom recovery? If custom recovery worked, then it seems like the unit can still be saved.
BTW: LRX22C is also 5.0. Specifically, 5.0.1. 5.1 is not available yet.
So a little bit of clarifications first;
HAVE you tried to perform a factory wipe (via recovery) or otherwise FORMAT (not "fastboot erase") the data and cache partitions? No part of your message mentions formatting the data or cache partitions. If the init is unable to manipulate/mount a possibly corrupt data or cache partition (or possibly some other partitions as well), then it WILL REBOOT.
In addition, some logs of the reboot could be useful if you are able to obtain any. A somewhat modified boot image can enable adb and kernel logging at a point from before the reboot occurs.
P.S I didn't purchase officially from google or Motorola, I bought it for $580 from a guy who claimed he bricked it trying to install a font pack ''iFont'' so I figured let me buy it and restore factory image, easy win. Didn't work. He said he rooted it, installed custom recovery and euphoria os rom. Then he installed the fontpack, it told him to reboot to apply changes, and when he rebooted it wouldn't boot past google screen after that. not even to the boot animation, It just shuts off. When its off and u plug in the charger it does the same thing, you just keep seeing the charging symbol over and over because its constantly rebooting. Its a T-Mobile Nexus 6 BTW, model number XT1103. I am now looking at a motherboard for the nexus 6 on ebay which is $300, as this is the only thing i see left to do. Please any help would be appreciated. I can promise a hefty $$$ reward for any individual that helps me recover it to a working state.
Click to expand...
Click to collapse
I don't think you need a new mainboard.
If what he explained to you is correct, then my previous about fixing corrupt data partitions should solve the issue for you.
Agree with the guy above me. Same thing happened to me on my Nexus 9. Manual flashes all successful but could not boot. Booted into recovery and did a factory wipe and all was well. I know this is the nexus 6, but it sounds like corrupted data.
Hi i have a serious problem i am running cm-12-20150217-NIGHTLY-ghost.zip for the last five days. Now this is where my problems started yesterday i flashed a new boot animation after which the device refuses to boot . when switch on i just keep hearing a vibrating sound untill i hold down vol button and go into twrp recovery. I had made a nandroid backup of the functioning cm12 which i know works because i tested it once. But this time it wont work anymore. After restoring the backup i get the same problem vibrates then stops and the occasional flicker of light. i have no idea how to get back to stock i cannot find kitkat .4.4.4 stock for xt1053 anywhere and i think ive bricked the device anyway. I think i flashed the wrong boot animation which may have corrupted sys files.
Any help much very much appreciated im all ears.
I have been getting help from another section but they advised me to post here. Just to update i am still in the same position no matter how many times i wipe everything and then adb push either cm11 or cm12 neither will boot it just vibrates every 2 seconds and i have to force recovery by holding the buttons in.
Your not bricked. Why not return to complete stock via mfastboot or rsd to make sure?
It has been solved!!!! [emoji1]
Sent from my ghost
sam0056 said:
...i have no idea how to get back to stock i cannot find kitkat .4.4.4 stock for xt1053 anywhere and i think ive bricked the device anyway.
Click to expand...
Click to collapse
Just for future reference....
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM (XT1053) and Verizon Developer Edition (XT1060) X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images, along with some instructions/info.
---------- Post added at 08:14 AM ---------- Previous post was at 08:12 AM ----------
sam0056 said:
...Now this is where my problems started yesterday i flashed a new boot animation after which the device refuses to boot . when switch on i just keep hearing a vibrating sound untill i hold down vol button and go into twrp recovery. .
Click to expand...
Click to collapse
Oh, and I've seen this symptom from flashing an incompatible LOGO.BIN, but haven't seen it from flashing boot animation (unless the animation file was TWRP flashable, and included a LOGO.BIN). Usually flashing a known good LOGO.BIN back on your phone fixes it.
fixed
Thankyou very much guys esp Smash2Bash without whom i was very much messed up i believe i flashed a stock logo/bootanimation to cm12 which is what caused my problems. when sent the correct one everything fired up as normal phew. Funny thing is why wouldnt my Nandroid backup work i just dont understand that and also since reflashing a fresh cm12nightly ambient display has started working which didnt work at all before very strange.
Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.
I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)
try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:
This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??
I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.
As i installed update and clicked reboot to apply it, now my system do not boot. Phone always stuck on white NOKIA logo boot screen forever. I tried few times to restart it via VOL-UP + POWER, but it always have same result - never boots. Please give me advice how to deal with it
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
ravkhar said:
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
Click to expand...
Click to collapse
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
gornex said:
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
Click to expand...
Click to collapse
Ach yes, sorry. First it stucked in logo Nokia and rebooting again... VolumeUp+Power does not work normally on Nokia.
It helped procedure found here:
https://forum.xda-developers.com/showpost.php?p=74406267&postcount=34
Then I was able to make factory reset and mobile booted, but worked with various faults.
Did you unlock your bootloader , flashed TWRP and then changed the slot? Slot A to B or vice versa?
If so, then the solution is
How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo appear any more >>
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
Edit: I sucked the juice (mAh electric-capasity) out of the battery quicker with help of OTG-cable and an external USB-powerd fan.
Use almost any external max 5volt USB-powered devices available at home, even charging another phone unless the second phone doesn't reverse-charge, this Nokia can be used as a power-bank.