Related
I was trying out using a keyboard with a cheap USB OTG cable, and all was good. Then all of the sudden the screen went buggy, where ever other line of pixels was shifted to the left or the right, almost like some sort of corrupted video file. It started to reboot itself, and it got to the black screen with the Google logo and then the screen fuzzed in the same way as before. It then starts to reboot and does the same thing over and over again. I find that I can get to the recovery screen with the scroll arrows. From there, if I tell it to reboot into recovery it goes back into the same Google logo bootloop. I then went back to the original recovery screen and I decide to try out adb to see if it works. Sure enough it does, and I unwisely start flashing a stock 4.2 bootloader image. However, while it is flashing the screen does the same fuzz thing and and stays fuzzed. Then it doesn't respond to anything. I take out the battery, and try to restart and with will not turn on at all, no vibration, no light from the screen, nothing. I tried a unbricking methods from there, and nothing can make it come back alive. Any ideas?
Additional info:
GSM tajkju
Bootloader unlocked
Running stock unrooted 4.2 that I flashed manually
Stock recovery
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
AWretchSavedByGrace said:
Hi all, my unlocked and rooted (for the purpose of titanium etc) 5 day old OP3, running latest stock Oxygen is rebooting itself several times a day, but not rebooting back into the OS. It shows a blank screen and the notification light is lit white.
To get back into the OS, I have to power it down and restart. Sometimes it doesnt make it past the boot animation. It freezes, and reboots (again, to a blank screen with white notification light).
I've spent a couple of hours this morning wiping it (all apart from internal storage), and re-flashing.
The problem then got worse, as when flashing the stock ROM from recovery, or side loading it, the phone would reboot when it got to 90%. Whether I use TWRP (3.0.3-0), or stock recovery, I encounter the same problem.
I tried flashing a slimmer ROM (AICP), which flashed successfully, but I'm still getting reboots to blank screen with white notification light.
Any ideas?
P.s. I took a nandroid backup before encountering any issues, however the phone reboots (to the same state) when about 50% through restoring it.
Click to expand...
Click to collapse
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
thelad said:
Same as myself normally while watching YouTube or downloading files is when it hapoens most,so I'm gonna do a factory reset in twrp and see if that helps,ill let you know
Click to expand...
Click to collapse
So done that and got one black screen and the white light,went to work had 3g/4g on all day didn't get one black screen,got home connected to wifi and I got a black screen,so something to the with wifi seems to cause it for me
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Paradoxxx said:
Sounds like a hardware issue.
I'd get my device replaced ASAP.
Click to expand...
Click to collapse
I think I'll have to its pissing me off now,goes great for hour or two then I'll get this black screen 4 or 5 times in a row
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
nono77240 said:
I have the same issue.
I tried some ROMs (cm13, RR, OP3lite) and always the same.
I already contacted the support and they wiped my phone by taking a remote session through my computer.
I now have OOS 3.2.1 stock, not rooted.
I had a reboot since but I will let a few days to see if the issue is resolved
Click to expand...
Click to collapse
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
I don't know how much time after, maybe 6 hours later or so...
I had a freeze yesterday evening and had to reboot my phone.
Everytime it freezes on reboot and I have to wait 3 to 4 tries before the phone really boot.
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
I created a RMA ticket this morning.
My phone will go to repair center
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
My situation
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Breecko said:
Hi there,
This morning I decided to relock my bootloader to give it a complete stock-Android feel to it. I had already unrooted my phone at this point. It was then when I thought it was a good idea, since I unrooted it, to delete the BetaSuperSU rar file as well as the TWRP folder from my phone files. I then opened a command prompt in the AndroidSKDSlim folder and typed: fastboot devices, fastboot oem lock
And then I went on my phone and clicked the power button to confirm the locking. Since then my phone has not booted up yet, and I get no vibration when I press the power button. No button seems to be responding, but the white LED light is permanently on. What should I do now? My computer doesn't recognise my phone either!
Click to expand...
Click to collapse
Have you tried holding power and volume down for a few seconds without the cable plugged into the phone?
thelad said:
How long after the wipe/back to stock did it happen? after a bit of Google search seems to be happening to few sd820 devices
Click to expand...
Click to collapse
acmerw said:
Try to flash stock rom with unbrick solution. If ir does not help, apply for RMA ticket
Click to expand...
Click to collapse
AWretchSavedByGrace said:
I raised an RMA request on July 19th, which was approved July 20th, yet I've still not received return mailing labels from Arvato.
Not even slightly impressed.
Click to expand...
Click to collapse
I received a mail yesterday evening saying that they can't take my phone and I have to do a factory reset.
I replied to this mail saying that I did multiple factory resets and even do a remote session with a oneplus tech support.
They sent me a mail an hour after with a number and the process to send my phone.
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!
tl;dr summary:
- Replaced screen, worked for 1 week
- Randomly switches between hard-brick no response, and soft-brick boot loop
- Boot loops on loading TWRP as well as OS
- Running latest 7.0.0 NBD90W
- Phone is H790 variant
- Flashed Android 7 in the bootloader, not through OTA. This was as soon as Nougat came out, and it worked great for weeks.
- Bootloader unlocked (for temp-booting twrp only, "fastboot boot twrp.img" otherwise kept stock)
- Phone NEVER rooted
- No charging indicator when plugged in
- Battery bent during previous removal, maybe causing issues a week later?
Replaced screen with genuine LG front frame assembly after a running accident cracked my screen/digitizer. Phone worked fine for about a week, then randomly shut off and went into a boot loop.
Now it randomly switches between a boot loop and a hard brick. When it's acting like a hard brick, sometimes it goes back into boot loop temporarily if I disconnect and reconnect the battery. It eventually returns to hard brick.
Hard brick mode:
-- Doesn't respond to any power button presses. Does not indicate charging when plugged in. Entirely unresponsive.
Soft brick mode:
-- Normal boot: normally gets to Google logo and restarts. Rarely makes it to the flashing dot animation. Twice has booted into Android, past the lock screen, and works perfectly for ~10-15 seconds before rebooting.
-- Boot into bootloader: On occasion will reboot itself from bootloader, but rare. Usually works correctly including all adb commands.
-- Boot into stock recovery: Same as bootloader, usually works, sometimes reboots.
-- Boot into TWRP 3.0.2-2 bullhead: boots for a few seconds and then locks up. Has never made it through decryption - will either a) freeze and reboot right after I draw my pattern, throwing an error that it could not mount storage right before restarting or b) freeze and reboot anyway if I take too long before drawing my pattern. It seems to be more time-based than a function of anything I do.
Things I've tried:
Since my bootloader is unlocked, I've re-flashed these partitions with no fix:
bootloader.img
boot.img
recovery.img (stock)
radio.img
vendor.img
I've cleared cache through stock recovery, can't remember if I tried flashing cache.img
I have yet to flash system.img or userdata.img as I have a few files I'm trying to recover... The fact that I can't boot into TWRP, and the sporadic hard-brick behavior, doesn't give me enough confidence that wiping my data will help.
Phone tends to live in hard-brick mode unless I disconnect and reconnect the battery, then it sometimes goes into soft-brick boot loop for a while before once again hard-bricking itself. When hard bricked, no charging indicator appears when plugged in. When soft-bricked and turned off, will sometimes display the battery status after short-tapping the power button. No change when plugged in except only once it displayed the battery with lightning bolt icon for about 2 minutes, before returning to the icon without the lightning bolt.
My best guess is that I damaged the battery during removal.
- The adhesive was really strong, and while I didn't puncture the case, I did bend it somewhere between 30-45 degrees in the process. If I damaged the Li-Po foil, would that make sense for the phone to work, only to go belly-up a week later? I ordered an OEM LG battery for $13 because it's worth a shot at that price point. Arriving next week.
- The reboots sound in-line with it crashing when it tries to draw too much power? Bootloader and stock recovery usually run okay and I assume have a low power draw. The OS and TWRP probably draw more power and that's where it fails? The reboots seem to be more time-dependent than depending on anything in particular that I do, such as rebooting before OR after drawing my pattern on TWRP. And that it sometimes boots into full Android for a few seconds implies to me that the OS is working on at least some level.
Does anyone have any better ideas for when the new battery inevitably doesn't fix it, or things to try in the meantime? Could the common Nexus 5X boot loop under Nougat be causing issues booting into TWRP too? It feels hardware-related to me. I took it all apart and looked for loose/oxidized/bent contacts on all the connections but couldn't spot anything.
My Pixel isn't arriving until Nov 23-25, and to make matters worse I switched to Google Fi 3 days ago and I have no compatible phones to use in the meantime. Oops, lesson learned.
To begin with, the device was rooted with Magisk 18.1 flashed about 2 years ago, running stock OxygenOS Oreo 8.1. Recovery: TWRP-3.2.1-1-cheeseburger. Kernel: RenderZenith OP5T [OOS-O-EAS-V3.7.0]. This was the setup I was satisfied with and running in about a year (a total of 2 years).
However, after the first year, I've tried to update TWRP to version 3.3.1-20190908-0-codeworkx-signed-forcedecrypt-dumpling in order to flash and update to the newer OxygenOS Pie 9.0. Something went wrong after flashing the newer TWRP and I couldn't get into recovery anymore... all I saw was a black screen when trying to get into it. I haven't bothered about this since the system booted and worked fine, so I gave up on the 9.0 update and stayed on 8.1. I was able to use it like normal another year. Everything was running very smoothly until a couple of days ago...
The battery has discharged to 0% and the device shut off by itself. 30 seconds before the shutdown, the UI was much less responsive and a popup about the device turning off popped up. I've put it in charge the whole night and when I woke up in the morning... couldn't boot into the system anymore. Instead, the phone booted into the 'broken' recovery, with constant lit of light blue LED (started to lit a couple of seconds after booting, only in the 'non-visible' recovery), and a black screen. I've looked up the fastboot/bootloader keys combination and went into it, well from there, I've tried the turn-off, start, recovery, and bootloader option. Turn off = Off. Start = Recovery. Recovery = Recovery. Bootloader = Bootloader.
The next step I've done was to connect it through a PC and run ADB on it in order to flash the old TWRP-3.2.1-1-cheeseburger. Re-booted into recovery straight after successfully flash and the recovery started to work again. The light blue LED stopped to lit any longer and I haven't seen it anymore. The first thing I've done in recovery was to clear the cache, dalvik, and do a nandroid backup, then tried to re-boot into the system. Finally, it booted into the system and I was happy like a kid when I saw the OnePlus boot animation again, however after putting my password and SIM pin code, I can enjoy it without any issue for about 30-40 seconds before the UI suddenly starts to be non-response (touch doesn't work), the screen starts to flash, sometimes (looks more like turning the screen on and off), until I see a "Turning off..." popup 20-30 seconds later (the battery is fully charged and disconnected from the power source) and the device is rebooting itself into the 'working' recovery. This is how it works each time I boot up into the system now. However, the power button is working and I can turn the screen off and on while the screen/touch isn't responding, the power menu can be opened by holding it (before it's too late and the "Turning off..." popup appears), from there I can choose to re-boot or power off. Magically the touch is working here. If the phone has been rebooted/turned off manually, by hitting either reboot or power off in the power menu, it reboots into the system instead and the same **** happens - not to recovery like it does when the "Turning off..." popup appears and it's turning off by the system.
I'd like to get everything back if possible, at least for one or two days, to back up all data, do some screenshots, back up browser bookmarks, history, open tabs, sms and calls, then give a fresh custom 11 to it.
Any help I can get from you guys? Is there a solution that I could try? What about flashing the newest Magisk onto it? Might it help or rather corrupt it more? Anything else? I'm out of knowledge in this situation and I'm relying on you.