Database Develop

[Q] Can't Boot - continuous crash on boot

Hi
Got an HTC for my son 2 weeks back. He used it for a day, but then got an update. After downloading the update, I restarted at the prompt and got a message that the download was corrupted. Switched off the phone and after sometime, restarted, but without the update. I then downloaded it again and got it running for him.
A week later and the phone just crashed and switched off! Charged it and switched it on, but it just crashes and boot loops. Since my son is now not with me, I instructed him to do a reset using hardware buttons (since it does not boot and thereby allow him to do a factory reset from within the phone. I told him to:
Turn off your phone.
With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.
Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.
Press VOLUME UP to start the factory reset.
Click to expand...
Click to collapse
According to him, this too does not seem to help and it is still crashing (boot loops).
Can someone please suggest something. Problem is that to claim warranty I need him to bring the phone back (as it is a regional warranty) and the earliest he can get it to me is in about 3 months!
Thanks for any help/ suggestions

Does the phone have an unlocked bootloader and custom ROM?
If so then he needs to re flash the rom using Mike's thread:
http://forum.xda-developers.com/showthread.php?t=2265618
http://forum.xda-developers.com/showthread.php?t=2265618
or a more user friendly method is hasoon2000's here:
http://forum.xda-developers.com/showthread.php?t=2183942

Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.

Paparasee said:
Can you please let me know how to check if the bootloader is locked?
It's brand new ... not rooted, nothing .... clean phone 2 weeks of which 1 week has not been used as it was not booting.
Click to expand...
Click to collapse
If it's new and clean, then the bootloader will be locked. You have to manually unlock it.
Try going to fastboot and then running "fastboot erase cache".
Though most likely, you may have to take it to a repair center for them to bring it back to stock, without you having to go through the hassle; Especially since it's only 2 weeks old.

[Q] Moto X stuck in a boot loop

Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE

darylbu said:
Hi,
So recently KitKat is released for AT&T Moto X's. Excited, I decided to upgrade the phone to KitKat.
I was previously rooted with RockMyMoto, and before updating to KitKat, I went to unroot the phone through the SuperSU app that was installed.
As I was unsure if it was really unrooted, I opened up Titanium Backup (which required root) and it popped up with an error that Titanium Backup wouldn't work because my device was not rooted.
So with this confirmation (a really noob way to check), I went ahead to download the update through the default system settings app. After the download, I proceeded to install it.
Before installing the update, it said the phone will shut down and proceed with the update, which takes around 20 minutes, and it will be done once it boots up again. And this is where the problem comes. After the phone switched off, the phone just reboots immediately, as if it was just restarting. And after 30 seconds or so, the phone switches off and restarts again. Initially, I thought this was normal, but it kept on restarting and I knew something was up.
I don't know what to do now. I have tried holding down the volume buttons and power button to reboot into recovery, but every time I select the recovery option, the phone just reboots like normal and does not reboot to recovery. I even tried to "race against time" and restore my phone through settings app, but it doesn't allow me to.
What can I do? Please help me
I looked up on the internet, and it seems that I have to remove the OTA cache from the cache folder, but how can I do it? I don;t have root access anymore...
EDIT: FIXED, PLEASE DELETE
Click to expand...
Click to collapse
How did you fix it?

I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?

Recovery
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.

MikeNaples said:
Are you able to hold power + volume to get in to your recovery?
Then you can reinstall your nandroid. Or, then you can flash a different rom.
Click to expand...
Click to collapse
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache

serophia said:
Or he can also boot into bootloader with adb by doing adb reboot bootloader then typing fastboot erase cache
Click to expand...
Click to collapse
This process seems to work quite well.
I'd recommend to use MFastboot. With your phone off, you can boot into fastboot by holding power and volume down for a few seconds, release and it will boot into fastboot. Connect the usb cable, and first try "fastboot erase cache". If that doesn't work by itself, repeat the process but also use "fastboot erase userdata" (THIS WILL ERASE ALL YOUR DATA!) but at least there is a chance you might get it to boot normally. It´s like a factory reset, you will have to start from scratch.
I know my answer is out of date but it might be useful for someone coming for this same solution.

Moto x Stuck in TWRP loop
pls help me guys it just goes on restarting it dose not even goes in recovery mode

Guys.. I got struck at unlocked boot loader. Flashed TWRP on 5.1 ( GB retail rom). And its not booting now and not able to flash any rom.. kindly Help...!!!

[Q] Cant boot to recovery

I have the CM 11 build from 10th May with the 3.4.0-g14fe8eb kernel.
I tried to update to the 21st May update, but the phone does not boot to recovery. I tried restarting via the quick boot app and while the phone is turned off, but when it turnes on, I dont get the sony logo, nor do I get the LED indication to press volume up.
Is the recovery missing?
I never had this problem and I have been tinkering with android for the past 4 years. :crying:
P.S.
I am running a windows 8.1 PC, so if some actions from the PC are needed, take this in consideration please. I know some programs have issues with win 8.1

lujo_zgb said:
I have the CM 11 build from 10th May with the 3.4.0-g14fe8eb kernel.
I tried to update to the 21st May update, but the phone does not boot to recovery. I tried restarting via the quick boot app and while the phone is turned off, but when it turnes on, I dont get the sony logo, nor do I get the LED indication to press volume up.
Is the recovery missing?
I never had this problem and I have been tinkering with android for the past 4 years. :crying:
P.S.
I am running a windows 8.1 PC, so if some actions from the PC are needed, take this in consideration please. I know some programs have issues with win 8.1
Click to expand...
Click to collapse
Flash the recovery again via fastboot method.
Recovery is not missing might have been corrupted.
Hit thanks if helped :good:

Soft-Bricked Moto G (2014) won't move beyond Fastboot

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.

Phone in bootloop please help...

So i wanted a new rom for the awesome features so after i had rooted and installed twrp custom recovery i downloaded cm12 then created a nandroid. I put my phone into recovery wiped everything except internal storage and installed cm12 and gapps. This is where my problems started, as much as i liked the new rom it wasnt connecting to my cellular network so i thought ok ill just recover my nandroid so i wiped everything except the internal storage and then started the recovery when it finished i rebooted and it goes to the warning bootloader unlocked screen and sits for about 15 seconds the goes black and repeats. My phone is a motorola moto x 2014 victara, any help is much appreciated.

Please give us more details:
1) can you access recovery? Try holding the "power" button for like 20 seconds and trying to reboot into recovery when the phone boots.
2) can you access fastboot mode on the phone? maybe you lost your custom recovery but can access the bootloader and that makes things easier.
3) what is your device number? (xt1097, xt1095, xt1092, etc)

You are going to want to factory reset. Most times coming from a customer rom to another or even back to stock you will need to do a factory reset in order to wipe out anything that may have been left over that could cause issues.