Database Develop

Nexus 6 Stuck at AndroidAnimation

hello everyone. i got my at&t nexus 6 today. the first thing i did was unlock the bootloader. after that i rebooted. the phone boots up with the at&t sign and sound but it gets stuck at the little balls moving in a circle for the android animation. it's been doing that for 20min now. i tried to fastboot flash the system again but it's still doing it. i tried to get into the recovery but at the little android with the exclamation point i hold down power+volume up and it just reboots the phone after 10s. no recovery options. if anyone has any insight into how to fix this i would greatly appreciate it. thank you.

i was able to get it fixed. after not being able to get into android default recovery i decided to flash twrp. i did then then rebooted to bootloader and then went into twrp. it booted right up and then i did a factory reset in there. the first try cache wouldnt mount. so i manually mounted cache and did the factory reset again and it finished with no errors. i restarted my nexus 6 and it booted up the the welcome. thank god. i thought i was going to have to take it back. hope this info helps anyone else that comes across this same issue.

Stock SM-G925V Bootloop after 5.1.1 OTA

My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .

same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.

I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse

Kindle Fire HD 7" Stuck flashing the teamwin screen.

So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?

I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.

I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.

nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
You probably didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM.
usn.mustanger said:
I'm having the same exact issue. Mine started after doing a factory reset from the system settings to try to alleviate some Play Store issues.
I'm just replying in the hope that someone will see this and help us out.
Click to expand...
Click to collapse
Both of you, you can't factory reset a rooted device from the system settings, this usually wipes out the whole OS because with root the device has access to system partition, when you reset it wipes everything it has permission to remove(with root it has permission to everything).
Factory reset from settings on a nonrooted device doesn't wipe the OS because it doesn't have permission to alter system. That's why it doesn't harm the device and only wipes the data you've put on the phone.
Try flashing TWRP and see if your devices will boot to recovery then. If not, you may have to use fastboot to flash the stock firmware.
boy201 said:
I got the same issue, I tried to factory reset the system and now mine keep flash at the teamwin screen. I cannot connect to the PC neither. Please help.
Click to expand...
Click to collapse

nicarasu said:
So after trying to install the cyanogenmod nightly, my device started displaying repeated errors about different processes stopping. This would not stop, so I tried to reboot the device. Now the device is attempting to load into the recovery section, but it has just reached the teamwin screen and just keeps going black then flashing back to the screen. Any way I can recover it, or should I finally retire it?
Click to expand...
Click to collapse
Strange... is your tablet at least recognized by a computer?
Make sure you connect it to a USB 2.0 port

Issue returning N6 to stock - I've done it all

Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?

Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.

Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.

usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?

Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.

Moto E4 Plus (XT1773 Nicklaus) stuck in boot loop - bricked?

Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)

fernandocg30 said:
Hello everyone, how do you do?
I've got this phone that was running perfectly the stock rom, but I have that addiction to customize every phone I land my hands into (I guess some of you either haha).
But
This time something horrible happened, and I just can't back this phone to work. I'll tell what did I've done and I'm hopping you to help me (just paid a lot to fix the broken screen, don't want to buy a new board...)
Here we go: yesterday, several times I've tried to unlock the phone, and figure out that the fastboot command to do that have changed to fastboot oem unlock (at least in this phone), and had no need to copy that code into Motorola's page. After unlock, tried to install TWRP Recovery, several times, and finnaly got one that worked here. Okay. Ready to go. Also had difficulty to find a ROM that is compatible with this phone (I wanted some with Android 9, or 8.1, at least). I was capable to install the Lineage OS 15 Unnoficial for Nicklaus, but got stuck in Lineage OS Logo Screen. Fine. Downloaded the Lineage OS 14 Unnoficial (Android 7.1), flashed, and everything went fine! The ROM was installed, configured, but... My phone has the OnScreen Buttons for Navigation... And this ROM doesn't appear to get this to work... Every time I went to settings page and tried to enable this feature, the Settings Application stucks and phone restarts. So, at this point, I thought that the ROM was with some code problem, whatever, decided to download another. And (that was a HUGE MISTAKE). Downloaded the DotOS ROM here.
After flash, the ROM loaded up fine. Settings, ok, system, ok. But, the same problem with the Navigation Buttons. What? Again? Yes. Tried to enable via settings, but I realized that some configurations of Lineage OS installation is still there - forgot to wipe data before flashing ROM... But at this time (I guess it was 2AM) I had no patience to reboot, wipe, boot, configure, and decided to factory reset using the option in Settings menu. The DotOS shows me a logo saying "Wiping data". The phone reboots. And reboots. And reboots. But, the TWRP stills working, and tried many, many times to flash all sort of ROMs with no success at all.
I was going insane, you know, WHY I CAN'T FLASH THE ROM I'VE JUST FLASHED MINUTES AGO?? Got a clue: somehow when wiping data, DotOS bugged my /data partition (in TWRP, when wiping data, got an error in this partition, and cant fix it using TWRP fix menu). Tried a lot of tutorials over the internet to fix that partition, with no success. And, unfortunately, at that point my /system and /cache partition got broken too.
But, I had my secret weapon: THE STOCK ROM. Yes. Everytime all went wrong, is quite simple: just install the factory's ROM, and you will be fine. Right? Wrong. Really don't know why, I was not able to flash some images of the ROM (boot, recovery, system also). Thought I've downloaded the wrong Stock ROM. Tried another. And another. No success. What the hell? At this point my mind was not lucid enough, and decided to STUPIDLY FORMAT PARTITIONS BY MY SELF. Reboot Bootloader. Connect Cable. Fastboot.
fastboot devices -> OK
fastboot erase boot -> OK
fastboot erase userdata -> OK
fastboot erase system -> OK
That's it! Fixed! Now is just reboot, and... Reboot. Reboot. Reboot. Reboot.
Ok, Vol Down + Power. Nothing. Ok, Vol Up + Power. Nothing. Ok, Vol Up + Vol Down + Power, Vol Power + Dow Up, Fingerprint + Screen + Two Punches + Power. Nothing.
Stuck in boot loop. My worse nightmare. Thinked: okay, lets remove the battery, and... Remember I've just fixed the broken screen? Yeah. Out of lucky, the assistance tried THREE TIMES to change my screen, because the screen's provider at first provided a screen with ghost touches, at second a screen that had light glitches. At third, a correct screen. Don't want to loose my warranty, you know. If this third screen has some problem either? The assistance put that tag over the screw, you know. Can't take my battery off. But I really don't know if removing the battery will really help, because I've erased my boot partition. I hate me. My wife too (but she hated before). Now, got this tutorial: Ultimate Guide for [Bootloop Recovery] Noob Friendly, that is a little outdated, and can't help me. But gave me some hope: So, my phone isn't bricked yet! I can fix it!
But I really don't know how.
I hope someone helps me, and that this topic can be useful for any one who got stuck in Boot Loop from here to eternity.
Regards,
Fernando Garcia (sorry for my bad english, I only speak JavaScript)
Click to expand...
Click to collapse
Hey, download the stock rom for your from here:
https://motostockrom.com/motorola-moto-e4-plus-xt1773
And follow this process to flash the rom on to your phone:https://androidmtk.com/flash-stock-rom-using-smart-phone-flash-tool
Warning for this phone flashing process:
In SP flash tool, "do not" select 'format all+ download'(the phone will be bricked). Only select 'Download only'.
Secondly deselect preloader after adding scatter file(flashing it will also brick the device).
This all warnings are already given in the flash guide, i just want you to give proper attention while doing it.