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!
Hello, everyone!
The problem is that when booted, the phone only vibrates and turns off immediately. The screen never enables, LED for charging never enables. When connected to a charger, just vibrates. Tried to follow the steps here : installed the Soc driver, plugged the phone, tried to power it off - device manager recognized the phone for a couple of seconds and then it's gone.
Long story short: I tried to install official firmware upgrade using TWRP > Install > .zip. The installation was going on for a couple of minutes and then the screen blacked out. Since then, the phone does not boot.
So, I got bored of my Android 5 and decided to install a custom ROM, but I had to upgrade official firmware before that.
At first, I dove into how to install custom ROM tutorials, so I did the rooting first:
I downloaded a BootLoaderUnlocker program from the official Asus website and unlocked the BL. Then, I followed a tutorial for one-click-root, and succeded. Then I installed TWRP and flashed the Recovery to the latest available img for my phone and tried to install the Lineage OS 14.1 but got status 7 error, meaning something is incompatible.
This post states, that in order to install Lineage OS 14.1 I have to have a firmware at least MM 4.21.40.xx which is Android 6, so I went to the official Asus website and downloaded the Firmware upgrade. Since, I probably had the wrong BL at that point, I flashed the bootloader with TWRP for Z00A (Lollipop) 2.8.7.3 from here, which is the same website from which the post suggest to download a BL for MM (Android 6). I thought, since I currently have the Lolipop, should install the BL for that, just to be sure. Then I started the firmware upgrade, which rebooted the phone into the BL, I didn't think, and just pressed Normal Boot and the phone booted as usual in the old Android. Then I tried to initiate the instalation again but couldn't (it's supposed to auto-detect the file in the storage root), so I got an idea to just boot the Recovery, maybe it will continue. So, I did that, and the TWRP showed up (I forgot about it already and thought that the instalation would just continue), so I just pressed Install and chose the firmware upgrade zip manualy. The installation was going on for a couple of minutes and then the screen blacked out.
Since then, the phone does not boot. If I try to, it vibrates like it is going to boot, but then nothing happens (not even a logo).
I even tried to disconnect the battery: removed all the screws, removed the back panel and manually disconnected it. When I put it back the phone vibrated like it was going to boot, but nothing happened again.
P.S. I tried to boot into the Recovery, but that just does not work, and even did not work before the firmware upgrade (I googled, that I must press power and volume up and hold until the logo appears, but that doesn't happen).
upd: plugged into the charger, periodically shows the battery icon on the screen.
upd: I went to a service and the dude said I might have screwed up the `preLoader`, so some might say it's a disastah
https://forum.xda-developers.com/showthread.php?t=3452785
Sent from my ASUS_Z00AD using Tapatalk
Resolved
So, I went to a service and turns out I messed up the PreLoader, that boots the BootLoader. Sometimes this cannot be restored and costs a bunch of money to replace the memory block, but I got lucky and got the phone repaired.
P.S. Do not install official firmware with programs like TWRP, use only your manufacturer's SoftWare
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
elkay said:
Not my first rodeo on this.. running latest beta on my Essential Phone.
I just got a Pixel 2 XL tonight (refurb, was on May 8.1 when I booted it) and I was able to get into Android and toggle OEM unlocked. Did both normal and critical unlocks fine. Flashed latest P beta and after reboot I got a red text screen saying the device was corrupt (not the regular orange text bootloader warning message). Device booted to white Google logo screen with lock (in locked position). It rebooted on its own and same error messages, then got to Google white logo screen with the same lock and sat there for at least 15 minutes before I power cycled it. Same happened again. Went into recovery and factory reset. Same thing, stuck at white screen. Flashed back to 8.1 July update. Same 2 error messages on boot. Did the first short boot to white screen again and reboot again. Stuck at the white logo screen again on 8.1. Started the process over flashing latest P beta again. Same results.\
I should note that my Essential Phone never saw that red message even with leaving the bootloader unlocked, only the orange one. That phone is still working fine on latest beta. That also means I know my USB ports and USB cables are sound.
I'm totally stuck at white screen on boot no matter what I do after flashing. I can't even get 8.1 booting anymore. Flashing all seems to work for both P and 8.1, no errors. Tried a different USB cable and also different USB port. No luck. What's going on? Why can't I get this thing to boot at all past the logo now? Help!
Click to expand...
Click to collapse
Most likley an issue with the boot.img if your doing flashall.bat make sure you have the newset adb/fastboot files
Does essential have a and b partition?
I know the pixels do and is part of the reason these roms are trickier.
Sent from my Pixel 2 XL using Tapatalk
Fixed it. Caused my own pain (sort of). Path to my platform-tools was changed to an old version (not sure what changed my path grrrrr).
Lucky of 2 things: 1) That I didn't blow out my bootloader and 2) Nothing else caused permanent partition issues.
Anyway, I would recommend anyone else that runs into this issue to be absolutely sure you're running the current version of the platform tools (*all* of them, not just fastboot.exe). Now my device just booted up and with only the usual orange message. Red message is gone.
Hello!
the issue:
My device s4 mini (serranoltexx) does not boot further than the initial Samsung logo (showing the "normal" warranty kernel in the left top end of the screen), and then turns black. I can't do anything beyond this stage. When I take out the battery and insert it again, the device boots /starts automatically until the samsung sign and turns black again.
the background:
Last year in July, I flashed mys4 mini (serranoltexx) using odin, twrp and one of the latest official lineageOS Roms 14.1 (July 2018), with nano gapps. But since this morning (10. of January 2019), I can't start my device anymore. The latest update, which I did for the ROM was in July. Due to work reasons and since the official maintenance expired, I did not follow any other Lineage updates for my device, e.g. on this website. But I could use my device daily without any problems until this morning, when I started an app (music player) and after a few tones, the music stopped and the device turned black. Since then I could not enter or boot my device properly. I use a 32gb sd card as an integrated storage.
steps already done:
I tried to enter the recovery mode. When switching it on (taking the battery out and back in), I can enter the initial screen of the recovery mode, but after may be 3 to 5 seconds it turns black again. Saying nothing. I intended to flashed fresh using odin and twrp, and then the latest lineageOS ROM versions from your website. But the same sequence happened again: After using the key sequence for entering the download mode, I can enter it and push the volume up button, but then the device turns black again, saying and reacting to nothing. I changed the batteries (I have several), but it did not change anything. And this puzzles me ....
I know that my device updated trwp yesterday - when my device was still working - but I turned it off and I could turn it one this morning functioning well until I used an app.
the question /the request:
Is there any possibility to fix this problem? Could anyone help me on this issue, please. I really like my s4 mini, I do not want throw it away. I would really appreciate any advice which would possibly fix my problems.
Many thanks in advance for your replies and help
Not my phone, but a friend that rooted their friend's phone.
Goal: Unlock the bootloader and root the Redmi Note 8 Pro (Global)
Steps:
- Unlocked bootloader.
- Flashed TWRP. (it worked & booted)
- Installed Magisk (worked, phone booted with Magisk)
- Update Magisk through the Magisk Manager
This is where the problem occured:
The moment they clicked on Update in Magisk Manager, before the update process could even begin, before the update file would be downloaded, the phone rebooted (vibrated as if it was force rebooted) and the display never came back on.
This makes me believe it was a coincidence and the phone just rebooted on its own anyway.
The phone seemingly appeared to not work, as the display was off and would not turn on, but the phone does actually boot into MIUI and vibrations can be made using the screen.
The phone is detected in ADB according to my friend.
I am unsure whether fastboot or recovery works, but I would assume that if the system boots, fastboot would also work.
We tried looking this up online and we get all sorts of stuff about bricks and whatnot, but nothing about a display not working but the phone booted.
This isn't a brick, as the phone boots, but there is no visual output, not even the Mi logo on startup.
Anyone have a clue?
The user isn't comfortable with messing more with their phone to fix it, but they would like to charge my friend even if the repair ends up free. This is stupid.
Should try fastboot mode and flash the stock boot of the current rom