Database Develop

[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] Stuck in a reboot loop, can't get into recovery, what to do?

I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!

brasstongue said:
I recently upgraded to an HTC One, on Verizon in the US. I promptly used rumrunner s-off to get S-OFF, unlock the bootloader, and obtain root. I also flashed the latest ClockworkMod recovery, with the intent of installing CyanogenMod, but decided I'd try out the stock ROM for a few days first, since my old phone was still on Gingerbread.
Everything was working fine until I decided to remove some Verizon bloatware. While I did back up each app before removing it, I forgot to make a nandroid backup. I only removed things that seemed nonessential -- such as the NFL Mobile app, Slacker radio, and My Verizon, which I'd also removed without issue on my old phone -- but apparently that was not the case, as after rebooting, I got stuck on the Verizon logo during the boot sequence.
I then attempted to perform a factory reset in CWMR, and it appeared to be stuck on "wiping cache", so -- like the impatient idiot I clearly am, as I later found a few threads explaining that this part of the reset process can just take a very long time -- I rebooted the phone to try again. This resulted in CWMR throwing errors about failing to mount several partitions, but it finally seemed to finish the reset on the second try. However, upon reboot, it just sat at the HTC logo forever.
After about an hour, and no success in finding anything on the internet indicating that it should take this long to boot up after a reset, I powered the phone off and back on again. After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols. I could still get into recovery, and could still access the device with fastboot, so I decided to try to reflash the stock ROM, using the RUU zip found here.
Due to some problem (this was all about 6 hours ago while I was at work, and I was quite frustrated at this point, so I don't remember what exactly was the problem here) and based on the advice of another forum thread, I decided to try TWRP instead of CWM. But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM. Afterwards, my phone went into a reboot loop -- the HTC logo comes up, the phone vibrates shortly, and then after a few seconds the screen turns off and it does the same thing over again. If I hold the power button down for long enough, it will power down, but if I try to turn it back on, it will either go into the loop again, or just sit at the HTC logo (left it there for upwards of an hour at one point).
I have found several threads about similar boot loop issues, but as I can't get into hboot/fastboot or recovery, I can't try to apply any of the solutions. I cannot connect from my computer with fastboot or adb -- "devices" lists nothing, and all other commands return either "error: no device found" or "waiting for device". No amount of power+volume down makes any difference, nor does holding the phone under a bright light as several threads suggested. Occasionally it will go to a black screen (not off, just black) that maybe it thinks is the bootloader menu, but it doesn't display anything, and after about 30 seconds it will reboot itself.
Does anyone have any suggestions for getting into recovery and trying to reflash.... something?
Alternatively, if I return it to Verizon at this point, will they be able to tell that it's rooted/unlocked/S-OFF?
Any ideas would be much appreciated!
Click to expand...
Click to collapse
Can u get into bootloader?? Press power + vol down??

brasstongue said:
After rebooting, the bootloader screen displayed "OS" in red followed by some random symbols.
Click to expand...
Click to collapse
that means your firmware is either in a state of limbo, or you corrupted one of your partitions.
so I decided to try to reflash the stock ROM, using the RUU zip found here. Due to some problem
Click to expand...
Click to collapse
which ruu, and what was the problem
But, TWRP wouldn't go any further than its logo splash screen, so I re-flashed CWM.
Click to expand...
Click to collapse
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt

Thanks for the reply.
nkk71 said:
which ruu, and what was the problem
Click to expand...
Click to collapse
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
nkk71 said:
Did you flash the correct recovery for Verizon (M7_WLS), it's different than international (M7_U/UL)
Click to expand...
Click to collapse
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
nkk71 said:
as @khandelwalsiddharth mentioned you need to get to bootloader if a fix is even possible, so POWER OFF your phone completely, then HOLD VOLDOWN and POWER, when it boots up let go of POWER but keep holding VOLDOWN until you get to bootloader
Click to expand...
Click to collapse
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
nkk71 said:
then you need to have working "fastboot devices" (if you're on Win8.1, you probably need to use another computer with Win7 or use a Linux Live USB)
Click to expand...
Click to collapse
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
nkk71 said:
if you can't get to bootloader, then I don't think this is fixable, cause hboot is corrupt
Click to expand...
Click to collapse
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>

brasstongue said:
Thanks for the reply.
Oh, I guess I forgot to make that a link... I had downloaded the only VZW one on this page but I'm not even sure why I bothered to mention it, as downloading it to my computer was the only thing I ever did with it; I was never able to get as far as flashing it to the phone, so it actually had nothing to do with the problem...
I was under the impression that Verizon was m7vzw, in which case yes, I was using the correct recovery (6.0.4.7 version listed next to "HTC One (Verizon)" on this page) and it was working just fine the first time I flashed it.
Yeah, I've tried this about 100 times, and the only thing holding VOLDOWN does is occasionally interrupt the boot loop to send me to the black screen for 30 seconds before going back into the boot loop. I did find one thread where the poster was able to get into the bootloader after letting the phone sit overnight, so I'll try again tomorrow, but I'm not very hopeful.
I'm on Win7, and "fastboot devices" was working the other day, so I know my drivers are all set up properly and functioning. The phone just isn't booting far enough to connect to the computer.
So... should be safe to take it back to Verizon and ask for a replacement, since they won't be able to tell it's unlocked? >_>
Click to expand...
Click to collapse
my bad, thought I read Sprint, not sure if Sprint and Verizon use same recovery, but that doesn't really matter now
unless you can get to bootloader, you're stuck, sorry.
If your pc does see "fastboot devices" then it must be in bootloader and flashing a ruu.zip (if available) could (that's a very big could) get the device working again.

[Q] Nexus 6 not booting up after random shut down

Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.

chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.

did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.

Butterfly S run to home screen then reboot - unrooted

Hi Guys, I come to the point where I need help please, I have very long experience in rooting but this issue I could't fix and/or find a solution for it since the 901S is unrooted there is no EXE RUU not been touched. This is my wife phone and I had same issue with main a year ago but since my phone was rooted I could fix it.
The issue is when the phone start rebooting by it self at once, nothing was done to cause that like installation app or what so ever. It start and when reach home screen, few sec it reboot from 0.
phone data: S-On, Hboot-1.61.0000, Radio 4t.31.3218.26, oS-5.16.709.4
I have tried this:
-Unlocking with unlock_code.bin, is give me the yes/no screen when I click yes it reboot to stock recovery then nothing, (it show the message about missing E bitmap)
-uploading rom stock or any other didn't work, not by using fastboot or any other method I know.
-run into save mode help give few more secs but nothing, it reboot here too
-factory reset from device didn't work as I click okay but it keep resetting.
-order *#*#3424#*#* and factory reset also nothing.
-the device memory is 95% full, I tried to format data or system or from fastboot or by deleting files also nothing get deleted all stock and after restart I see ever thing like it was.
any suggestion here?
thx all,

Any help any one

No one no help!!

ONE PLUS 3T - OOS 4.1.3 stucked in bootloop after flashing SuperSu

I have update my rooted OP 3T by flashing the complete rom through TWRP.. But the problem is whenever I flash the Supersu version : SuperSU-v2.79-201612051815 or SR3-SuperSU-v2.79-SR3-20170114223742, I am getting bootloop.
Please anyone advise me.
I checked that without flashing SuperSU phone is able to Boot safely.
Thank you in advance.

It's normal if it bootloops once or twice
But if it's more than that then it's problematic
So which one is it
Another thing you can try is try magisk root instead of supersu and see if gets the same result

Phone was stucked in bootloop for an hour without any reboot.
I am not fond of magisk yet... So dont have any plan for it.
Just want to know if this happens to only me or there are many others with same issue.

Edit:
Finally installed Magisk for root... Issue closed.

help!?
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
plzz can anyone help me

amber sachdeva said:
hi guys i am amber
yesterday i was trying to unroot my device [op3t] i locked the boot loader but after that my device started
bootlooping i was able to get to fastboot but none of the commands were working i can not boot into recovery coz there is no recovery on my device i am not able to flash any thing .
Click to expand...
Click to collapse
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.

redpoint73 said:
That is not the proper way to unroot (go back to stock). Relocking the bootloader while rooted was asking for trouble. There is a guide on how to return to stock in the Guides section.
Also, fastboot commands will only work while in fastboot mode, if the phone is looping, or otherwise stuck on any other screen/mode, than fastboot commands will not work. It's also a bit irrelevant, as your ability to flash anything with a locked bootloader is very limited. That's the whole purpose of a locked bootloader.
I'd start by making sure you are in fastboot, get fastboot working, and unlock the bootloader again. Then follow the proper process to return to stock.
Click to expand...
Click to collapse
well i tried unlocking bootloader but it says failed (remote: oem unlock not allowed)
Iam i stuck here for ever ?
can u tell me the command that i can try on an phone with a locked bootloader

I forgot this is an edit the first time Gentlemen, I am absolutely at wit's end now I am no geek with a capital G however I have been modifying phones for some 3 years now and I can't even tell you how many times I flashed ROMs my beloved 3T 3T has had been acting glitchy lately like when I would reboot the circle that turns - instead of just turning evenly it would twitch, it was such a small thing I ignored it but I think now that that's must be have been indication something was not right few other things like that. I flashed the Freedom ROM cuz I'm so sick a Google and Google Assistant when I came out I was in a bootloop so I wiped everything except OTG everything and formatted data did the ROM Flash again the a boot Loop still abides and I've done it a dozen times now sometimes a couple of times it it just it kept recycling the bootloop another time and got hung up on the OnePlus it just sat there on the logo and if I miss something obvious I do apologize I'm tired and I'm at wits end because I'm not used to not being able to solve my own problems I guess so any help at all or just even a heading in the right direction would be so much appreciated that I don't even know how to call it quantify it thank you
By the way I seldom post or even post questions but when I do I always pretty much say the same thing you guys are the best this is the one place I can come for Andrew Android advice or or guidance and I just I absolutely trust what I read so thank you thank you thank you thanks for being there
Edit - I'm so tired I forgot the first time I went to reflash the ROM it told me that my 3T was in fact not a 3T that it was a three and I read someplace so I'm XDA that that's just Corruption of the install script so I downloaded it again I ran 7-Zip it said it was coherent so I flash it again if that's important but thanks again

Help required
kunal1540 said:
it's normal if it bootloops once or twice
but if it's more than that then it's problematic
so which one is it
another thing you can try is try magisk root instead of supersu and see if gets the same result
Click to expand...
Click to collapse
sir, i have oneplus 3t a3010. Last night my phone was crashed and after crashing it restarts and jumps to recovery mode. In recovery mode i wipe all data and restart my phone. But i still doing the restart thing. Please help, what to do now.
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz

My oneplus 3 is stuck in recovery mode
My bootloader is locked
Everytime i switch on my phone there is a message
Which is on photo below