My G2 (801 Tmobile) will sometimes have issues with the data handshake as I move from wifi to data and I'll be forced to reboot. When I do this, the phone will essentially bsod Windows style and go back to the Tmobile white boot screen at least 3-6 times. This phone has been doing this over the past couple ROMs that have been released, so it's not just
Unlocked, rooted, twrp recovery and latest version of the stock os. G2xposed and greenify are installed too if that provides any further info.
Sent from my LG-D801 using Tapatalk
Related
I have a verizon S3 on MB1 it was rooted on beans for a while it worked fine. Got a new phone and my girlfriend wanted the S3 so i odin restored it back to stock verizon MB1. The phone rebooted earlier today and now its about every 5-10 mins i found a different stock verizon odin file and restored to it still reboots randomly so now im going to try and flash beans again to see if it works like it did before anyone have any other options the phone seems laggy and locks up at random times and if it randomly reboots more than 3-4 times it tries to reactivate again which makes it sit in the activation screen and it continues to reboot until i boot to manual stock recovery and wipe data. Also no apps are installed but the verizon factory ones
New Update: I rooted/unlocked/ and installed beans rom now it locks up black screens and reboots any help would be great thanks guys!
I would boot into recovery, factory rest, wipe dalvik, and wipe system. Then flash MF1, as MB1 is outdated now.
Sent from my Last Ever Samsung Device.
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Why all the way back to ED1? Do you have everything backed up in case you need to flash with the pit file?
Sent from my SM-N900V using XDA Premium 4 mobile app
beavermjr said:
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Click to expand...
Click to collapse
No, the phone is not dead, it is a bit lag.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
I have following problems with my Nexus 5 16 GB (unlocked, not rooted and everything stock)
1. It keeps rebooting occasionally (more often than I would count as normal) without any apparent reason.
2. Whenever I receive OTA update it fails to complete showing "Error" on while updating.
3. Tried factory resetting several times to no avail all symptoms remain the same.
4. Could not go to recovery mode. It shows a red triangle with exclamation mark.
5. Flashed stock images from Google.
6. Worked fine for few days (seldom reboots, though) and could go to recovery mode.
7. Now recovery is again corrupted. Cannot go to recovery mode and it keeps rebooting every now and then.
I don't know if it is a hardware problem or software. I need to sell this phone but want to be fair so need to exactly what is the problem and what could be a possible solution to perspective buyer.
Thanks for long post. Any help is much appreciated.
shahidhussain said:
I have following problems with my Nexus 5 16 GB (unlocked, not rooted and everything stock)
1. It keeps rebooting occasionally (more often than I would count as normal) without any apparent reason.
2. Whenever I receive OTA update it fails to complete showing "Error" on while updating.
3. Tried factory resetting several times to no avail all symptoms remain the same.
4. Could not go to recovery mode. It shows a red triangle with exclamation mark.
5. Flashed stock images from Google.
6. Worked fine for few days (seldom reboots, though) and could go to recovery mode.
7. Now recovery is again corrupted. Cannot go to recovery mode and it keeps rebooting every now and then.
I don't know if it is a hardware problem or software. I need to sell this phone but want to be fair so need to exactly what is the problem and what could be a possible solution to perspective buyer.
Thanks for long post. Any help is much appreciated.
Click to expand...
Click to collapse
You only have one issue here which is rebooting. If you flashed stock without restoring data /installing apps and it still reboots, send it for repair.
Sent from my Nexus 5 using Tapatalk
rootSU said:
You only have one issue here which is rebooting. If you flashed stock without restoring data /installing apps and it still reboots, send it for repair.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes I flashed everything stock (without keep any data/apps) and it still reboots. Initially I checked by entering into recovery mode and all was OK but now a red triangle. So it is a hardware problem
Thanks for your quick reply
Stock recovery always has that symbol
Sent from my Nexus 5 using Tapatalk
got the same problem since 4.4.3 came out, even got a replacement phone that does the same.. symptom a soft reboot, occasionally hard, every one or two days.
running 4.4 or 4.4.1/2 the problem disappears
only thing i found that helps is turning location on and having mobile settings to allow 3g.. i can go for up to a week like this before a reboot.. my personal settings of 2g only and location off makes it worse for some unknown reason.
bootloader unlocked
MIUI 9.5.19 global ROM installed
Magisk 16.4
Have been using the phone for 2 weeks now it's the second time that the phone shut down because of battery to low. OK so far but it then only is booting into TWRP. Also deleting DALVIK and CACHE i can see it booting and then the black screen with the navigation arrows are visible for a second. It's seems that there is something preventing the system to come up properly. After 5 short attempts with black screen and navigationbar visible it boots into TWRP.
Also re-flashing Magisk is not solving it.
OK I could now re-flash the Global ROM again but it won't fix the general issue why the phone get's stuck once it shuts off because of empty battery and again I would loose all my data.
Anyone with ideas how to fix it or what could be the root cause?
EDIT: It seems that there is really a problem with the system itself. If I instantly hold the power button once booted until the black screen I could keep it running and I see the restart, shutdown, airplane buttons but nothing more.
In Windows I would say it's not starting the explorer.exe
anyone who had something similar?
Have you tried re-flashing with MiFlash?
Bootloop after weeks of normal use is pretty misleading considering that you are using a custom recovery that isn't even official plus Magisk and possibly other mods. You should flash the official stable ROM with the MI Flash Tool and then run the phone without any mods to see if you still experience the same problem. And if you decide to use TWRP again you are better off using it through fastboot so the stock recovery remains installed on the phone.
THx for your replies... I think I've figured it out:
It seems that the alternative launcher is the root cause. I've been using Microsoft Launcher since moths across all my devices (light+fast+sexy). Without it (replaced by Nova now) it seems that the problems are fixed