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?
Related
Hello everybody.
I am a Defy Red Lense user with a recently flashed PA 2.14 build (coming from 2.00 version of same ROM). At first 3-4 boots everything was ok, till I made some changes on phone config (namely enabling 16 bit transparency as recommended by it's maker, and then some small changes in Paranoid Android Settings) and asked me to reboot. Ok so I went to reboot and as usual, it booted me into bootmenu, and I chose "boot" and "2ndinit" as usual. After a odd bootloop (where the phone wouldn't go through the blue, then green LED sequence and would then reboot, show Moto logo boot animation, rinse and repeat, etc) that I ended by pressing vol - and entering, again, into bootmenu, I chose again boot and 2ndinit and then something really weird happened:
After almost half an hour i'm still stuck at the very ROM booting animation (the Paranoid Android one, no the Moto logo), just like the guys that tried that new kernel that were reporting 15+ min first boot times. As a clarification, my first boot with just flashed 2.14 took, at most, 5 minutes. And there is another odd vehaviour, concerning the PA boot animation: it gets randomly stuck for a few secs and continues as usual, with no looping from 0 just like the normal loopboot.
So here comes the questions:
- What is really happening? is it really booting or the phone is just stuck in ROM bootanimation? How long should I wait to consider shutting it down?
- Is there some way to get out of it/shutting it down without damaging the device? Can I just pull the battery off without bricking the device?
Looking fowardd for some theories behind this issue :good:
Well, seems like it was OK to unmount the battery while on ROM booting animation, since I haven't had mayor problems after doing so and rebooting. Now the phone works just fine.
Tho im still curious the reason behind this pseudo-bootloop. Thanks for reading anyways :good:
Hello everyone!
My brother sent me is MX 030. It is the original Meizu MX HK version with the unlocked bootloader. Two weeks ago, he found his phone had crashed. The screen was black and he powering it off and then back on would not do anything (black screen - only vibrates on power on).
I got it today and first thing I did (after charging it-the charging mode works and displays a battery logo) was boot into recovery mode (or update mode on Meizu phones) and I was able to reach the menu. It let me mount the drive onto my PC. I downloaded the latest firmware and put it on the drive. I pressed upgrade and cleared data. The software seemed to install fine, but then the phone rebooted to a black screen - again.
Then I tried installing older versions which I found on the meizu website. They all install and I can see the recovery mode is different, but they all boot into black unresponsive mode (which drains the battery).
Having had other android devices before, I feel the phone is stuck in reboot loop.. I don't know what else to try or attempt. I feel am running out of options. The fact that the phone still responds to some commands and allows me to flash firmware should indicate that the phone isn't brain dead quite yet, right? Anyone else experienced a similar situation?
Thank you,
Oli
After having re-installed my apps from Google Play, my device went on loop boot (or almost).
It takes 2 or 3 loops to be able to boot correctly.
First boot only take 10 seconds after the Samsung logo. Once on lockscreen, the device restart, takes longer time to boot, and then reboot ...
And when GNote3 finishes correctly the boot sequence, some of the folders i have created are empty.
Another bug is the lockscreen ink effect : colors changes are not taken in account.
I thought that the boot issue was due to one of my app (but what the hell ! all of them were running smoothly on my previous GNote2) but i think the problem could be related to bad data management ...
Nani said:
After having re-installed my apps from Google Play, my device went on loop boot (or almost).
It takes 2 or 3 loops to be able to boot correctly.
First boot only take 10 seconds after the Samsung logo. Once on lockscreen, the device restart, takes longer time to boot, and then reboot ...
And when GNote3 finishes correctly the boot sequence, some of the folders i have created are empty.
Another bug is the lockscreen ink effect : colors changes are not taken in account.
I thought that the boot issue was due to one of my app (but what the hell ! all of them were running smoothly on my previous GNote2) but i think the problem could be related to bad data management ...
Click to expand...
Click to collapse
I had a continuous boot loop problem after installing a few apps. It freaked me out as I spent a long time getting everything looking good on the phone. I thought it was going to be a case of hard resetting.
I removed the SD card and suddenly all was OK! I had been using the card in a different phone. So I removed any system folders from the card and everything worked fine. That is until I reinstalled some other things and the problem came back. So I reformatted the card in the phone and now it all seems to be working.
I also had problems with changes not sticking on the lock screen. They too are now working after I did the above.
Hope this helps.
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.
New phone. Opened the box and this is what's been happening.
The phone stays in a bootloop (first screen, followed the the blinking Samsung logo, back to first screen - repeat).
After a while, sometimes, it actually boots into Android. I see the Welcome screen that is seen at first boot on new Samsung devices. At this point, I can tell the phone is really hot right above the SIM slot (no SIM in phone, nor memory card). It stops responding to touch and gets stuck. I have to pull out battery to restart.
Once it restarts, it's back to the bootloop. Then again after some time it might randomly go into Android, get hot, reboot.
Is this a hardware issue? Or is this fixable?
I've already:
Flashed stock MM
Reset
Wiped cache