Hi.
There is a device that is start up so: youtube.com/watch?v=w5RGTD2xE0E
Blink logo on the screen confuses me.
Perhaps someone can tell this is "normal" bootloop behavior or a possible hardware (screen ?) fault.
I got an offer to buy the device in this state for recovery.
Thanks for answers.
PS Blink logo actually occur. It is not the fault of video record.
The blinking Google logo seems more indicative of a hardware problem . A "normal" bootloop generally refers to the ROMs boot animation looping, which occurs after the Google logo. A normal bootloop can usually be fixed by reflashing a ROM, but if it's hardware related that's a whole different problem (one that I wouldn't want to mess with unless someone gives me the device for scrap).
I can't say definitively, but that's just my two cents from looking at it.
Related
Hello I am trying to fix a friend nexus 7 first gen
the problem is that it keeps flashing the white google logo like its boot looping , the system doesn't even seem to be restarting just a flash on flash off google logo , no nexus logo or anything else at all.
I cannot get into recovery it will just shutoff everytime i try even from the bootloader menu
tablet doesn't have debugging mode on so only thing I can do is work via fastboot
already tried to flash like 5 different versions of android and everytime it finish (succesfully) and goes to restart it just keep doing the same on the google screen.
any help is greatly appriciated, and I have been searching all around the internet for hours now and have seen many solutions to bootlooping which I have pratice before on many of my other android devices but nothing like this problem.
thank you and pardon my english.
When you turn on the tablet with the power button and the screen's backlit turns up, press the VolDown button. This way you can boot into bootloader and flash a factory image provided by Google.
yup like I said before I did got into bootloader and flashed factory stock images like 10 times now and still having the same problem, this is what i usually do when I get into bootloops with any other android device but for some reason this time is different.
its not idle at google and I dont even get to see the nexus logo it just shows the google logo for one second and screen goes black then again the google logo and black screen like infinite restarts with one second delay.
Then it maybe hardware related (corrupted nand/partition/etc) so you might consider to send it to Asus/Google to repair.
I messed up with my LG G2 D802 and i need help because i believe it's a software problem.
When i was installing the latest cm12.1 nightly, after trying a few other roms, i also installed, by mistake, an old jb bootloader/bootstack.
As result the phone entered in Bootloop, but not a normal bootloop, on the screen start appearing some crazy interferences and then the phone boot up, but the screen not. The phone made sounds and the touchscreen work, but the screen was black/off.
I've managed to solve the problem with an unbrick method, but now i have a huge problem: the screen, on the rigth side, from the top to the botton has 6/7 black lines. I have no idea how to solve this and if is a hardware problem ... I've read it's an kernel problem, not hardware, but don't know how to solve the problem :/
Picture:
https://meocloud.pt/link/58d13900-ffa8-4114-8957-8c4b973bad1a/IMG_20150916_020454.jpg/
I feel your pain
Hi mate
Same thing happened to me.
Background info: I had successfully upgraded to CM12.1 , was running fine for a few days then I wanted to update my TWRP, updated the recovery and just went to check that I had OTG cable support then boom, boot loop.
It didnt just loop it just loaded loaded loaded, then the screen made some funny sounds. and then shut down. I hard reset to recovery and reinstalled CM12.1 and was able to successfully exit the loop. but damage to screen had occurred in the exact same place, and method right side of the screen.
Tried rinstalling original jellybean software from my backup. no success, and also flashing other versions of CM12.1 nothing.
After some research I saw that this is a manufacturing fault and that this occured quite often. it appears that the best solution is to buy a new screen as it is the actual hardware that is damaged in the screen digitizer. I might be wrong, and I pray that I am because I want to fix it too. in the end I just bought a new note 4 (not note 5 as i wanted SDcard storage). Phone was 2 years old and a new screen costs a fortune. But i miss my little G2 and its super fast speed and simpleness. :crying::crying:
If someone else has the solution to this problem on the forum we are all ears.
http://forum.xda-developers.com/lg-g2/help/phone-bricked-t3380584 is the start of this.
The story is: two identical D802s purchased at the same time. One works fine. (DirtyUnicorns 6.0.1 v10.2). The other had the problems in the link above. Currently, when it boots, it looks like it it getting into a boot loop: black screen --> LG Logo --> Black Screen --> LG Logo. It does the LG logo a random number of times, sometimes 2 or 3, sometimes 10 but eventually the OS loads (DU logo) and it's fine from there. So, it is not a true boot loop.
What I have done is done a full TWRP backup of a working phone, copied it to the other and then restored all partitions except EFS. When I reboot the dodgy phone, it still does it pretend boot loop thing and eventually boots up. (The working phone of course boots normally.) I'm not sure where the differences are. If I swap the SIMs between the working phone and the dodgy one, the problem remains with the dodgy phone. Faulty phone hardware maybe?
(NOTE: for non-native English speakers: "dodgy" = not completely broken but partially broken!)
Any thoughts?
No one?
Hi,
I was using my phone when it suddenly turned off and got stuck on a bootloop, every time the bootup stops a the white Google logo at the start. I accessed Fastboot and can't do anything beyond that, it doesn't launch recovery. I tried to flash it with the latest google images but to no avail, the process goes as usual but when the phone restarts it gets stuck gain.
What should I do? Is this the Nexus 6P's bootloop problem I've been reading about on some blogs?
_________________________________________
Update : this solution helped me boot my device and it's working again https://www.xda-developers.com/nexus-6p-bootloop-fix
MrMestiri said:
... What should I do? Is this the Nexus 6P's bootloop problem I've been reading about on some blogs?
Click to expand...
Click to collapse
Yes, BLOD and no recovery mode. It is a hardware issue. Nothing can be done from a software/flashing perspective. Hopefully you have a warranty of some type. Otherwise it's time for a new phone.
My note 4 suddenly froze when I'm using it normally, I had to take out battery then boot up again, now just won't pass the logo Samsung screen, download mode still work but when I tried flashing stock rom it just keep stucking at logo screen ((
I cannot enter recovery mode either, same stucking at logo. Please help, I want to know if my phone can still be saved or should I let it rest forever. Thank you.
Try to change the battery, galaxy note 4 is infamous for its boot loop because of battery failure. I've had experienced it.
UnknownPlanet said:
Try to change the battery, galaxy note 4 is infamous for its boot loop because of battery failure. I've had experienced it.
Click to expand...
Click to collapse
I was thinking the same.
Only thing is he got away with (?) flashing it whick would indicate reserve battery capacity.
Regardless replace old or degraded batteries before they cause issues especially Li's. Just part of necessary routine maintenance...