Related
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
mahendru1992 said:
Do you get a pre verification error? I just posted this question yesterday, and I was helped out. I had exactly the same issue as you had, i think
http://forum.xda-developers.com/moto-g-2014/help/help-asap-fastboot-preflash-validation-t2949337
Click to expand...
Click to collapse
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
MortaLPortaL said:
Funny thing is, it was the firmware I was using along with ADB not being installed.
I got everything up and running. Rooted w/ TWRP. But I am unsure if I can unroot and lock the bootloader so I can hopefully get the OTA to 5.0
Click to expand...
Click to collapse
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
mahendru1992 said:
You don't need to lock your bootloader to receive the update. What you need is stock recovery, stock rom which in essence is everything stock. Just let the bootloader remain unlocked as I've heard that there still isn't a way to unlock the bootloader if you upgrade with it locked.
Mind you this is all heresay
Click to expand...
Click to collapse
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
MortaLPortaL said:
I tried to flash the recovery with the recovery.img and it worked until it showed the android with the red triangle. never goes any further than that. Reflashing TWRP is fine but stock is a no go.
Click to expand...
Click to collapse
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
smitharro said:
The Android with the red exclamation sign IS your recovery! To see the options: press the volume up button for 10-15 seconds. Then press the power button with it, and let go! Voilà: your stock recovery! It's hidden, because it's not meant for the 'common user'.
Click to expand...
Click to collapse
haha well thank you!
I feel hella stupid in a sense..but I appreciate you guys for being awesome and patient.
MortaLPortaL said:
I managed to successfully root my phone and install a custom recovery..but I wanted to restore it and that is when all hell broke loose.
I now have no service/wifi and my phones stuck on airplane mode. It came with stock 4.4..4 OS. It's a 2nd gen US Moto G and even though I launch the fastboot flash mode, anytime I try to flash something I get; hab check failed for primary_gpt. I can not flash the Primary GPT at ALL. The firmware I downloaded was Android 4.4.4
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US and nothing will flash through cmd.
Am I totally boned with a $179 dollar paperweight?
Click to expand...
Click to collapse
your post helpme to find what i was doing wrong.
in my particular case, i just needed to find my own Firmware (stock version) of kitkat 4.4.4 for my country, COLOMBIA. and that just went great. after that, again, flash Titan 2.0.3beta, that was it. Smooth as a criminal!
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.
Hello,
I did a reboot and now I can't use my phone anymore. I see the Boot animation but after the Boot up, the screen just turns black. I receive notifications and active display is working, also I can start my camera with the twist but I can't take picture because the touchscreen does not respond. On active display or the power off pop up, the touchscreen is working. So I did a cache partition wipe but this hasn't fixed my problem. The strange thing is that after a couple of frustrated reboots, the Boot animation changed to the old animation with the spinning world. I want to reset the phone via recovery but first I need to backup my data. I have very important Data on my phone like whatsapp log or Photos and videos.. I can't connect my phone to the computer because I have a pin... How I can Backup my data and what caused the black screen?
If your bootloader is unlocked you can flash TWRP. TWRP has the ability to decrypt userdata if you have the password. I don't know if it can decrypt the moto x or not, because TWRP only officially support ASOP type encryption, if motorola uses a different technique for encryption it will say the password is wrong. If it works you can browse and backup files from TWRP recovery.
If it says the password is wrong or you don't have the bootloader unlocked, then you are SOL and have lost everything.
In either case doing a factory reset will hopefully fix your issue.
Sent from my XT1095
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
rupro327 said:
So I did a factory reset now. But I stuck in Bootloop, i just see the M logo. How I can fix it? And no, my Moto X is stock like out of the Box.
Click to expand...
Click to collapse
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
same issue today
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
AGISCI said:
After the factory reset bootup takes longer than normal, how long did you wait?
If that is not the case, what model moto x do you have? For example mine is xt1095. Also what version of android do you have? 5.0, 4.4.4, 5.0.2, 5.1, etc?
Sent from my XT1095
Click to expand...
Click to collapse
I've waited about 30 minutes, in this time my phone just bootet into the recovery by his self. I've contacted Motorola and I'll send my device to repair.
It's a xt1092 with 5.1 RETDE.
I personally think that this issue is caused by the Boot animation update.
swankylaxplayer said:
This exact same thing happened to me. Updated to 5.1 about a week ago via the OTA. Wiping cache did nothing. Diagnosing it as a software issue, I attempted to sideload the official 5.1 OTA that's posted elsewhere in the forums. It came back as installation aborted, so I gave up on any hope of keeping my data and did a factory reset. Now all it does is bootloop, sometimes settling on the prone android no command screen for a little while. I can boot into recovery and the bootloader, but thats it. Really hoping someone can come up with a solution. XT1096.
Click to expand...
Click to collapse
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
JulesJam said:
Flash the stock 5.1 logo, kernel, system, modem, baseband and recovery for the XT1096 - the full image files are available.
Click to expand...
Click to collapse
Thank you! I don't know how I missed that! Back in business now.
nrsmsn said:
also have the same issue, black screen after reboot. moto voice, active display/notifications are responsive, camera too when twisting the phone. moto voice says "unlock your phone to continue" but i currently don't have any screen locks or anything, just swipe. i have a pure edition running on 5.1. Skeptical about a reset since the phone is still responsive.. tried looking for other fixes, but looks like this issue is just coming up today...
Click to expand...
Click to collapse
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
kunal_07 said:
I have the exact same problem. Any fix?
Edit: Can't get adb to recognize phone. Phone is rooted.
Click to expand...
Click to collapse
Have you tried reflashing the system image from the bootloader?
is that possible without adb? If so, can you tell me how?
kunal_07 said:
is that possible without adb? If so, can you tell me how?
Click to expand...
Click to collapse
You still do everything through terminal. You have to cd to your folder that has adb and fastboot enclosed, usually platform-tools. Instead of starting each command with "adb", you'll start with "fastboot" and you'll be flashing these while your phone is at the fastboot screen.
The full image files are in the forums, and all the commands you'll need, in order, are posted in this thread earlier
I have found that some time the fastboot from Moto wouldn't recognize the phone. I, then, use the mfastboot-v2 found somewhere around this forum works great.
Me too faced this problem few days back. Only option left to do was factory reset.
Read below just to go through of what i faced:
( I had gone through bunch of articles for restoring my data but i had a pin lock because of which while connecting to pc it couldnt detect phone.
Other things i tried includes flashing lockscreen bypass zip via stock recovery. There i faced signature verification failed error because i had done it through stock recovery where it doent let u toggle signature verification on/off as in CWM. )
And for those who wants their data back , i found many articles of data recovery after factory reset. But it needed your device to be rooted. All you have to do is after factory reset dont make use of phone and after rooting you can recover your phone by software as EASEUS android recovey, Dr fone android recovery. Thats all .
I am too facing this issue as of last night,, I have the verizon version (complete stock, no root, locked bootloader) and I am not sure how to go about fixing this without losing all my data.. I tried wiping cache but it did nothing.. Can anyone provide some kind of troubleshoot guide please? It would be much appreciated.
A friend of mine is also having the same issue.
I tried the 5.0 image and it won't flash.
I'm locked and without root. Is it even possible to flash even the factory images? (And yes, I've tried to go to the Customer Portal for the Moto X and that isn't giving me anything)
Edit: Finally got it to flash the stock image. Didn't help. Factory reset fixed things.
Note: I had this problem and was able to fix it through a factory reset, but I had to do it through minimal adb and fastboot. The bootloader factory reset option didn't work.
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Hello guys,
I'm using Evercoss A65/Sprout 8. And I'm using CyanogenMod 13 (Official Nightly - January, 21 Build)
And, I'm using TWRP as Recovery.
Last night, my phone is on low battery, and then I charge it.
Then, I leave it charged when I'm asleep.
In the morning, I check my phone and it was on the black screen, just like a boot loop.
I tried to reboot it several times, unplug the battery, sim, and sdcard. But, these things just doesn't work out.
I have try to going into Recovery, and it shows standard menu which has; reboot normally, reboot recovery, fastboot mode, options..
I've tried every single option, like normal reboot, reboot into recovery, etc. and it come back again into the blank black screen.
(So I can't get into Recovery)
I try to find the solutions, but I have found nothing
Can I use USB Debugging to reinstall the ROM and start the phone normally?
I never have this problem before, need to solve it very soon..
I need your help,
Any helps is very appreciated!
Many Thanks! :good:
Try to flash from fastboot, it work on my htc
mfawonkpo said:
Try to flash from fastboot, it work on my htc
Click to expand...
Click to collapse
Does it has Android M or L ? Is it rooted or unrooted ?
JainMayurD said:
Does it has Android M or L ? Is it rooted or unrooted ?
Click to expand...
Click to collapse
It uses android L, and yes... I rooted it
This is nothing to do with the ROM, ur battery has completely empty that y when u power on it blink then off again n if u goto bootloader,then select any option also it will blank
Solution- Charge ur handset leave it for more than half an hour,and check again,if still problem persist,try to power on with other battery.
I tried to to root evercoss A65 with Android 6 using "android one toolkit (updated)".
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Rooting was successful as per tool and device rebooted. Device got hung at the android logo and did not come up. I waited for 2-3 hr, but no success. To recover the device, I did, factory reset but nothing help. It got stuck.
No clue what went wrong
Thank You!
-Mayur
JainMayurD said:
I tried to to root evercoss A65 with Android 6 using "android one toolkit (updated)".
http://forum.xda-developers.com/cro...oolbox-android-one-toolkit-one-click-t3030165
Rooting was successful as per tool and device rebooted. Device got hung at the android logo and did not come up. I waited for 2-3 hr, but no success. To recover the device, I did, factory reset but nothing help. It got stuck.
No clue what went wrong
Thank You!
-Mayur
Click to expand...
Click to collapse
Make sure you have custom kernel
where can I find custom kernel ?
Here: (Kernel topics are labeled [KERNEL])
http://forum.xda-developers.com/cro...vice-development-original-android-development
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
You don't downgrade Motorola phones!
Sent from my iPad using Tapatalk
Is your device fixed now?
mlspot said:
Hi guys.
I have a moto X 1058 which I bought to someone about 3 months ago, it's an used phone so I can't rely on warranty.
I received the phone with Android 5.0, no root, bootloader locked, perfect conditions.
I installed Android 5.1 through an OTA update. Soon after the update, the phone began to boot suddenly every now and then with no apparent reason. Because of this I decided to downgrade to Kitkat 4.4.4 (The rom I downloaded is called: RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF) (I am from Colombia and the firmware of the phone is from Brazil). I used RSD lite, unlocked the bootloader, USB debug, etc. However the installing took way too long so I booted the phone while it was still installing (If i didn't do this, the installing would have probably taken 8 hours or so, because the system.img file was too big to download to the phone which is why i guess it took RSD so long). Anyways, I don't know why this happened, I just decided to boot it and see what happened. It went in a boot loop. I no longer have access to the bootloader screen. After two boots I can press POWER+VOLUME UP to get access to the screen "Android system recovery". Where the only options are:
reboot system now (takes me to the boot loop again)
apply update from sdcard (does nothing really)
aply update from ADB (My pc won't recognize my device anymore, RSD litle doesn't recognize my device either, I tried with mfastboot manually but it says "waiting for device" and does nothing)
wipe data/factory reset (tried this option as well, but nothing)
wipe cache partition (nope).
What can I do? I think this means my phone is soft bricked. How can I fix this? How can I get the bootloader screen back? I can't even turn off my phone, it's stuck in this bootloop. The only thing i can do is to stay in the system recovery screen, but i don't know what to do next. I don't handle Android systems at all, everything I did was based on youtube tutorials, so I'm a little slow to understand the basic concepts. Can someone explain me?
Thank you very much.
Click to expand...
Click to collapse