Develop Bugs

[Q] Problem with fff(I assume)

Ok, so I decided to flash my KF with CM10. To do this I did the standard KFU superuser, installed TWRP, and fff. After I flashed with TWRP the Google apps and CM everything worked okay, but I noticed that my Google apps are nonexistent. So, I thought I would reflash with TWRP, which is where the problem lies. Whenever I reboot my device I get the KF logo, except white and blue, telling me to press power button to change boot, which I have tried but to no avail, and it goes straight to the CM10 boot. I thought okay maybe I can get around this by downloading Goo Manager onto my device to flash the GApps. This didn't work. So finally I just assumed my TWRP screwed up so I downloaded the recovery package from Goo Manager. This also didn't work. Also, KFU doesn't recognize it.
Right now I'm assuming the problem is fff because I've never seen this blue boot screen. If someone could help me just get TWRP back to working or even just stock KF I would be much obliged.

If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.

votinh said:
If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.
Click to expand...
Click to collapse
From what Brandon is saying, I think you hit it on the head.
One note: it takes several seconds to access the recovery from the fff 1.4a blue kindle fire logo. Once that screen pops up, hold the power button for about three seconds till recovery is selected at bottom.
It doesn't appear that you actually have a problem, either, but just a misunderstanding of what your kindle should look like.
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!

votinh said:
If I understand you correctly, I then think you have no clue what TWRP or at least FFF is about. I hope I am wrong.
Alright, after installing FFF, you will DO SEE the Kindle Fire logo with blue (the Fire is in Blue) and it will ask you to press the power button to get into either normal boot, recovery boot and one more which I forgot. That's what it should be. I don't know what your problem is.
Anyway, from that Kindle Fire blue screen, press the power button and select boot to recovery to get in TWRP.
I might speak entire wrong here, though.
Click to expand...
Click to collapse
When I attempt to boot to recovery I get no TWRP. The screen flashes then the normal Kindle Fire boot screen shows, then another flash and back to blue sccreen

Again, I assume you know how to do it, how to boot into recovery.
If you do it correctly and still can't get in then reinstall FFF using KFU.
If you don't know how to, then search Youtube, there's tons of videos showing how.

votinh said:
Again, I assume you know how to do it, how to boot into recovery.
If you do it correctly and still can't get in then reinstall FFF using KFU.
If you don't know how to, then search Youtube, there's tons of videos showing how.
Click to expand...
Click to collapse
Except as I said earlier KFU doesn't recognize my device. I mean I'll check my drivers, but looks doubful.

brandonstrat said:
Except as I said earlier KFU doesn't recognize my device. I mean I'll check my drivers, but looks doubful.
Click to expand...
Click to collapse
Did you bother to try what I suggested?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!

jma9454 said:
Did you bother to try what I suggested?
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
Click to expand...
Click to collapse
Yeah and it worked, but after restoring back to stock kf it kept sayin that process had stopped working and never allowing me to actually set the damn thing up. So reflashed CM10 and it keeps looping the boot screen, showing a quick image of the home screen then restarting the process. Long holding the power restarts the device, allowing me to get to fff but I still can't seem to get TWRP to show up unless I tell it to fast boot on the computer and since it never actually gets to TWRP or the OS I see no way to mount it.

brandonstrat said:
Yeah and it worked, but after restoring back to stock kf it kept sayin that process had stopped working and never allowing me to actually set the damn thing up. So reflashed CM10 and it keeps looping the boot screen, showing a quick image of the home screen then restarting the process. Long holding the power restarts the device, allowing me to get to fff but I still can't seem to get TWRP to show up unless I tell it to fast boot on the computer and since it never actually gets to TWRP or the OS I see no way to mount it.
Click to expand...
Click to collapse
How did you restore to stock? That isn't what I told you to do...
When you plug it into the computer, what happens?
And also, when you reboot it, and you hold the power button at the blue screen with the menu at bottom, what happens? Does it cycle through three choices? If it does, wait till it selects the second one and let go.
Sent from my Amazon Kindle Fire using Tapatalk HD

jma9454 said:
How did you restore to stock? That isn't what I told you to do...
When you plug it into the computer, what happens?
And also, when you reboot it, and you hold the power button at the blue screen with the menu at bottom, what happens? Does it cycle through three choices? If it does, wait till it selects the second one and let go.
Sent from my Amazon Kindle Fire using Tapatalk HD
Click to expand...
Click to collapse
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.

brandonstrat said:
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.
Click to expand...
Click to collapse
Follow what you are saying is really a headache. You keep saying you did this and did that and that and this and I'm lost. Slow down.
Go one by one, answer what jma asked.
Forget what you have done to your KF, tell us what it is like now.
1. Can you get into the recovery? I ask again 'cuz you previously claimed you knew how to, then you didn't then you did.
2. During power up, do you see Kindle Fire with blue logo?
3. Right after that do you hold the power button?
4. Do you see it cycle through the menu of 3?
.
.
.

votinh said:
Follow what you are saying is really a headache. You keep saying you did this and did that and that and this and I'm lost. Slow down.
Go one by one, answer what jma asked.
Forget what you have done to your KF, tell us what it is like now.
1. Can you get into the recovery? I ask again 'cuz you previously claimed you knew how to, then you didn't then you did.
2. During power up, do you see Kindle Fire with blue logo?
3. Right after that do you hold the power button?
4. Do you see it cycle through the menu of 3?
.
.
.
Click to expand...
Click to collapse
Alright, sorry bout that I guess
1. If by recovery you mean TWRP, then no I don't believe so
2. Yes
3. Yes
4. Yes, but all options take me to the CM10 boot except recovery which takes me to regular stock orange kf boot for a few seconds then back to blue without the options but just boots
Hope that's a bit more clear, I guess I'm kindave panicking with my kindle being on the fritz and all. But you my good sir have been very patient and for that I thank you.

brandonstrat said:
Well I did do what you told me to do I reinstalled TWRP and fff and tried to install gapps. Well long story short nothing happened. So I did do what you told me to do. Anyways, the only thing that happens when I hit recovery is it strangely goes to the normal orange kf boot for a couple second, back to blue kf boot but with no boot option and back to annoying CM10 boot loop I previously described.
Click to expand...
Click to collapse
Okay, two things:
1) The reason you keep getting stuck at the CyanogenMod logo is because you're not wiping data (factory reset) before installing the ROM.
2) I'm very concerned because it seems that you may not know what generation of Kindle Fire you're using. You are posting in the 1st generation KF forums, but by your description you seem to have a 2nd generation KF. You need to clarify which device you have before someone gives you directions that would permanently brick your device.

soupmagnet said:
Okay, two things:
1) The reason you keep getting stuck at the CyanogenMod logo is because you're not wiping data (factory reset) before installing the ROM.
2) I'm very concerned because it seems that you may not know what generation of Kindle Fire you're using. You are posting in the 1st generation KF forums, but by your description you seem to have a 2nd generation KF. You need to clarify which device you have before someone gives you directions that would permanently brick your device.
Click to expand...
Click to collapse
1. That would make sense because I was I'm a hurry
2. It's first gen, I would have clarified had this not been a forum specifically geared towards first gen, but I appreciate your concern.

brandonstrat said:
1. That would make sense because I was I'm a hurry
2. It's first gen, I would have clarified had this not been a forum specifically geared towards first gen, but I appreciate your concern.
Click to expand...
Click to collapse
Well, you never know around here...
Since that's the case, it seems like you have a bootloader installed on the recovery partition. Your device's original bootloader is working as it should (orange KF logo), but when you change the bootmode to recovery, it boots into what should be the custom recovery, but instead is the FireFireFire bootloader. BUT...that's a best guess based on what I can piece together from the information you've provided. (I've avoided responding to this post for exactly this reason).
The problem is, your information is all over the place and much of it contradicts itself. In one post, you say you have the blue KF logo, but then in the same post, you say don't. Then you say you used TWRP to install a custom ROM, but then you can't access TWRP? But then you say you restored the device to stock using TWRP, and yet you can't access TWRP after that.
Perhaps you could explain in a clear and concise manner what your problem is, being as detailed as humanly possible, because as it stands now, you're not making any sense.

soupmagnet said:
Well, you never know around here...
Since that's the case, it seems like you have a bootloader installed on the recovery partition. Your device's original bootloader is working as it should (orange KF logo), but when you change the bootmode to recovery, it boots into what should be the custom recovery, but instead is the FireFireFire bootloader. BUT...that's a best guess based on what I can piece together from the information you've provided. (I've avoided responding to this post for exactly this reason).
The problem is, your information is all over the place and much of it contradicts itself. In one post, you say you have the blue KF logo, but then in the same post, you say don't. Then you say you used TWRP to install a custom ROM, but then you can't access TWRP? But then you say you restored the device to stock using TWRP, and yet you can't access TWRP after that.
Perhaps you could explain in a clear and concise manner what your problem is, being as detailed as humanly possible, because as it stands now, you're not making any sense.
Click to expand...
Click to collapse
Okay I'll try again, the only times I have actually been able to use TWRP is when installing it in kfu. I don't believe that it actually installed anything but it just sends it to fastboot, now I could be incorrect but what I believe is happening is the kfu is telling the kf to go to fastboot to install but TWRP is already installed because nothing ever downloads.
Is that what normally happens when you hit recovery on the fff screen? Does the TWRP require fastboot or is mine just really messed up?

brandonstrat said:
Okay I'll try again, the only times I have actually been able to use TWRP is when installing it in kfu. I don't believe that it actually installed anything but it just sends it to fastboot, now I could be incorrect but what I believe is happening is the kfu is telling the kf to go to fastboot to install but TWRP is already installed because nothing ever downloads.
Is that what normally happens when you hit recovery on the fff screen? Does the TWRP require fastboot or is mine just really messed up?
Click to expand...
Click to collapse
Something about this just doesn't add up.
Try this...
1) Download the recovery flashable .zip of FireFireFire1.4a
2) Reinstall TWRP using KFU and boot into it.
3) Use TWRP to flash the recovery flashable fff-u-boot_v1.4a.zip and reboot.
If the problem persists, take a video of it, and post it here so we can get a better idea of what's actually going on.

soupmagnet said:
Something about this just doesn't add up.
Try this...
1) Download the recovery flashable .zip of FireFireFire1.4a
2) Reinstall TWRP using KFU and boot into it.
3) Use TWRP to flash the recovery flashable fff-u-boot_v1.4a.zip and reboot.
If the problem persists, take a video of it, and post it here so we can get a better idea of what's actually going on.
Click to expand...
Click to collapse
Ok but when could I actually mount the device

brandonstrat said:
Ok but when could I actually mount the device
Click to expand...
Click to collapse
Better yet, go ahead and post a video of the problem. I need to confirm something before you flash FFF.

soupmagnet said:
Better yet, go ahead and post a video of the problem. I need to confirm something before you flash FFF.
Click to expand...
Click to collapse
note: the screen that flashes is from my previous rom sooo, yeah. Factory wiping is a good thing.

[Q] Stuck at blue kindle fire screen never finishes

So I teas trying to get a jb rom on here. I'm stuck at the blue boot screen and it never fully boots up and I followed all the directions but I'm pretty crappy at all this stuff. I forgot to put the rom and gapps on before and So I got into twrp and every time I try to get adb side load to work it never works just get caught at starting side load feature or whatever and never changes .
I know there's stuff somewhere on the forum but it's all to confusing to me. I've had this thing for one day and now I've got a pretty sweet paper weight
I followed a video by zedomax on YouTube
Not to good at cmd prompts either so be easy on me

jhillyer253 said:
So I teas trying to get a jb rom on here. I'm stuck at the blue boot screen and it never fully boots up and I followed all the directions but I'm pretty crappy at all this stuff. I forgot to put the rom and gapps on before and So I got into twrp and every time I try to get adb side load to work it never works just get caught at starting side load feature or whatever and never changes .
I know there's stuff somewhere on the forum but it's all to confusing to me. I've had this thing for one day and now I've got a pretty sweet paper weight
I followed a video by zedomax on YouTube
Not to good at cmd prompts either so be easy on me
Click to expand...
Click to collapse
Stunts did a write up on just this thing. This link http://forum.xda-developers.com/showthread.php?t=2459498 will get you fixed up.
1. To get into recovery, turn the KFHD off (hold power button for 20 seconds.)
2. Now turn it on and when you see the yellow Kindle Fire screen push up on the volume until the Kindle Fire logo turns blue and hold it for three seconds, then release the volume up button.
3. Now that you are in TWRP you can push the ROM and Gapps and will you be sorted out.

Didn't want to start a new thread, so I'll ask here. I had the same problem as the OP, but the thing was I couldn't get into the recovery. Kindle just booted up to blue logo, and then nothing happened. I tried to install CM, and everything was fine, but after having installed TWRP and 2nd bootloader I couldn't get into the recovery, and ADB suddenly stopped recognising my Kindle. I tried to install/reinstall the drivers, but to no avail... So I ended up recovering Kindle via SRT, and now I have 8.1.4 device (I went through red screen problem and at some point I wasn't able to flash anything even via fastboot)... I still want to install CM, what can I do to ensure that the recovery works correctly? Now Kindle is shown as portable device in device manager and there also is a line "android composite ADB interface", is it ok now? Thanks in advance.

I can't believe you pulled it back from the red screen. That does not happen often, good job. Did you wait until you saw the KF yellow logo and push up on the volume rocker and hold it for three seconds after the blue KF logo and let go? That's how you have to into TWRP.
Did you flag or push the files last time?
Sent from my Amazon Kindle Fire HD running Paranoid Android using xda app-developers

LinearEquation said:
I can't believe you pulled it back from the red screen. That does not happen often, good job. Did you wait until you saw the KF yellow logo and push up on the volume rocker and hold it for three seconds after the blue KF logo and let go? That's how you have to into TWRP.
Did you flag or push the files last time?
Click to expand...
Click to collapse
Thank you for the input! I think I did, I tried many times.
Well... I followed Hashcode's bootloader & TWRP installation tutorial step by step, so pushed the stack file and it went well.
Now my device seems fine running 8.1.4_user_1413620 and even rooted, the only issue is that it doesn't detect my home wi-fi network for some reason.

Erentel said:
Thank you for the input! I think I did, I tried many times.
Well... I followed Hashcode's bootloader & TWRP installation tutorial step by step, so pushed the stack file and it went well.
Now my device seems fine running 8.1.4_user_1413620 and even rooted, the only issue is that it doesn't detect my home wi-fi network for some reason.
Click to expand...
Click to collapse
Hmmm, if that continues, you may have to do a factory reset to see if that fixes the issue and then retry again.

I've connected the device to another network, it updated and now wifi is perfectly fine. Maybe it had something to do with OS version. Now my Kindle seems to work flawlessly, and I can start experimenting from scratch
Sent from my DROID RAZR Maxx HD using xda app-developers app

Kindle fire First Gen Brick any help appreciated

Hi all,
First let me say that I am new to this site so bare with me. Okay so my first tablet was a first gen Amazon Kindle Fire. After using the device for years upon end I decided that I disliked the Amazon Kindle OS and even the reading capabilities of it. Upon getting an Android phone the Kindle seemed to pale in comparison as it's apps were hardly ever updated and its app store was a disaster. So taking a leap of faith I decided to look up how to flash an Android ROM onto the device. So using the Kindle fire utility I troubleshooted flashing TWRP onto the recovery boot. However for the life of me I could not get the drivers to communicate with the Kindlea and the boot status was "unknown". Being the ignorant and impatient person I am (haha) I decided to use an app called flashify to flash the TWRP into recovery mode on my Kindle. Well little did I know that flashify was not the best option or it wasn't compatible, so I ended up in a boot loop with a device that could no longer connect to my computer using ADB composite device drivers. Frustrated I bought a factory fast boot cable and plugged it in. Now I was able to get out of the boot loop and use fast boot commands to boot and flash images. I flashed TWRP onto the device (finally) and it quickly, without user interaction, brought me to the "wipe device" button. I knew that I had to do this so I tapped the button but the Kindle did not respond, actually not responding to any touch or tap regardless of where on the screen. I quickly understood that I was unable to use the version of TWRP that I have. Unfortunately even after booting up every version of TWRP otter and blaze I still am not able to have any touchscreen capability. If I press the power button it locks the TWRP screen like expected but since the touchscreen doesn't interact with the Kindle I am unable to unlock the device and have to hard reset the Kindle(holding power down for 20 sec). So I tried flashing cannibal open touch recovery and the touchscreen worked (yay!) However it worked in a weird way where I was not able to select an option. I was only able to move and browse my cursor through options. So once again a dead end. So guys I am at a loss right now. I refuse to believe that my Kindle is just a paper weight and I feel like I'm close to being able to flashing an Android ROM. Any help would be appreciated!!!
Thanks so much
Josh

HELP - New Update Bricked 5x

Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?

Moonboots said:
Today I downloaded the new firmware update for the 5x. I installed using fastboot as normal, knowing that boot.img, vendor.img and system.img had changed.
I used fastboot to flash all three, then booted to TWRP and flashed SuperSU 2.76, ElementalX kernel and the AdAway file hosts.
The phone booted as normal and was running just fine for about 2 hours. Then, while playing music, I attempted to unlock the screen with the screen passcode. The device froze.
Attempting a reset only allowed it to get to the "Google" screen with the lock on the bottom, then the screen would go black. I could hard reset into bootloader mode. I attempted to flash back to stock, but the same freeze on the "Google" screen happened upon reboot.
Now, the device will not even get to bootloader mode. Holding the power + either of the two volume keys renders nothing on the screen, nor does plugging into USB on the computer. I'm fearing the device is hard bricked. Any recommendations?
Click to expand...
Click to collapse
There is a post 4 down from yours on fixing bricked phones.

Tulsadiver said:
There is a post 4 down from yours on fixing bricked phones.
Click to expand...
Click to collapse
Hi Tulsa,
Unfortunately, that post doesn't apply to this situation, as my bootloader is unlocked, and I can't even get to the stage of having the drivers recognize the phone, because the phone will not turn on to bootloader mode, recovery or download mode.

UPDATE:
The phone reached the point last night where it would not even power on, access bootloader or download mode. Any button presses/holds left the screen black.
Today, for whatever reason, the device booted into fastboot mode. I was able to flash the complete stock factory image for the August security update Android 7.0 - the first stable build. However, when the device began to boot, it once again does not get past the Google page with the lock on the bottom. The screen goes black after that without entering the boot animation.
I've called Google to get a warranty replacement unit sent.

I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659

quadracer06 said:
I was having a similar situation last night, gave up after trying for a few hours...the googs is sending a "new" refurbished one. I had 1 month left on the factory warranty
http://forum.xda-developers.com/nexus-5x/help/bootloop-enter-recovery-wont-stay-t3456659
Click to expand...
Click to collapse
Thanks for the reply, quadracer. I'll be taking the same path you are - Google already has the reorder on the way. Still trying to tinker in case there's a chance. Luckily, all the pictures from my engagement this past weekend were backed up to Photos or I'd be devastated.

Nexus 5X stuck at Google Screen. Won't boot stock recovery.

I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?

Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.

Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?

What was the latest Build you had when it was working fine?

To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does

Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.

blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.

This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!

Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.

Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!

Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies

This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.

Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk

Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.

I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?

Same HERE !!!!

the samed for me, and still now i can't light it up

sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.

Same deal for me and they are sending a replacement. This is a MAJOR blackeye!

Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!