Has anyone experienced random data drops on .15? Not hand-off but going from 3G/4G to nothing, no data at all, for several seconds at a time.
This has been happening randomly since the OTA, and I would like to know if it's just me or the firmware.
I'll flash the update in the morning and keep an eye on the data... Ever since it decided to try and update which resulted in a, idk, kinda boot loop till i deleted the ota in the cache I've been having issues that looks like the display reboots so I need to update anyhow...
Edit..sorry buddy wife went into labor last night so it'll be a few days till I can flash...
We cannot teach people anything; we can only help them discover it within themselves.
I have been experiencing this same issue ever since I downgraded back to the JB BL. I'm currently on CM nightlies.
Just to follow up.
Along with the random data drops, I had a few random reboots and a significant heat issue (at times it would reach 127°F). To relieve these issues I simply flashed the .10 boot.img (kernel) and all is well with the world again.
If anyone is suffering from these issues on .15, I've attached the 183.46.10 boot image.
Extract and use Mfastboot or Flashify to flash to your device.
Code:
mfastboot flash boot boot.img
Related
Been having this problem with the latest 4.4 kitkat roms, (GE & AOSP)
when i was back on my old bootloader (whatever it shipped with) and modem (XXUEMJ5) i would always get a random force shutdown when just using my phone through daily use, it would either:
A) Boot for a short time with several apps having lost all their data (such as usernames and passwords). Then shortly after shutdown again into a constant bootloop. (Upon entering Recovery the phone would display 0% battery)
B)Shutdown into a bootloop only recoverable by wiping the /data partition or reflashing the rom (or any other rom).
So then i heard good news from the new bootloader and modem from the XXUFNA5 Leaks throughout the forums and decided to flash them and also test the leaked TW rom. Being me the rom was laggy as hell and i quickly reverted back to Jamal's 4.4 RC 1.1
Unfortunately the force shutdown bootloop problem continued but when it would shutdown i could plug the phone into a power source and boot without problems? not very convenient if you ask me.
just recently i flashed Brood's AOSP pre-RC4 which was working fine until i was signing into some apps then it force shutdown and as i tried to boot the phone went to "Updating apps 1 of 1" and then instantly shut down again.
I went into recovery and wiped /data, /cache and Dalvik then rebooted, the phone would reach the final stage of booting (just before the lockscreen shows) and would reboot and repeat the process all over again.
I went to flash a different rom so i could atleast have a working phone for the day and upon fully wiping, etc. the phone would not boot and continue the reboot process. i suspected a bootloader problem so i reflashed the bootloader and roms now boot. im guessing the bootloader was corrupted somehow and i think the process will just repeat itself.
Anyone got any ideas? I'm stumped and frustrated as the process of setting my phone back up every day is getting extremely boring.
Hey all,
First post here on XDA and I'm hoping someone with more experience than me will be able to give me a hand! Until last week or so, I was running an up-to-date version of Lollipop (5.1.1), when my tablet started randomly freezing up on me, requiring "soft resets" to get it going again, or simply shutting off on me. Thinking it was software related, I tried wiping the cache with no success, so ended up doing a full factory reset. The issues *seemed* to clear up for a day or so, but came back, and so figuring it was Lollipop related, I wiped out the OS and installed CM12.1 (which was my first experience working with ADB and fastboot, and first time installing a non-stock ROM) with a TWRP recovery. A few days later, the freezing and shutting down issues began popping up again, with the shutdowns *usually* happening during sleep, but the freezing happening at anytime from initial "Google" logo to boot animation, to the middle of running an app. I had made a backup on TWRP when I got CM12.1 configured the way I wanted it, so I performed a soft reset when it froze on me, and booted into the bootloader. The tab kept freezing in the TWRP window before I could select a restore, so out of desperation I tried just doing a factory reset from within TWRP. Long story short, something must have happened during that reset, because it kept hanging on the boot screen. I thought I may have unknowingly messed something up, so I tried downloading and flashing a stock KitKat (4.4) ROM from Google's site, but kept encountering bootloader errors during the flashing and ended up only being able to boot to the bootloader screen (apparently got a faulty 4.3 bootloader in that ROM, which gave me a headache until I was able to get straightened out). I have been able to get a stock bootloader (4.23) up and running now, along with a stock recovery (going with Lollipop now, so stock for LMY47V) going, but that's it. I've tried flashing the stock lollipop image via shell script (I'm running a Fedora 23 machine), via individual commands, and via "fastboot update -w factory_image.zip" without success. ADB sideload still works via recovery, but I wasn't able to sideload the OTA packages for 5.1 either. The common errors that pop up seem to indicate an error (corruption? fragmentation?) on the cache partition, but I'm not a dev when it comes to Android, so I'm at a loss here... I keep getting "E: failed to mount /cache (Invalid argument)", and other errors associated with accessing/opening files further down the /cache tree. Would this error be more likely to be a hardware issue, or would it be a software/firmware issue? I've had similar errors before with USB drives, when they would start to bad and partitions begin failing, but have always been able to rebuild them and get my data back. If something like this is happening on my N7 and the cache partition has indeed become somehow corrupted and failed (but not physically....), is it possible at all to rebuild partitions on Android in a similar manner? I've scoured the web, but haven't been able to find anything that can help me out with something like that, so I figured my best bet before condemning the N7 to the junk drawer was to see if any of the pros around here had any words of wisdom that *might* get me back up and running. Thoughts and advice much appreciated!!
Thanks!
(Oh, I apologize for the lengthy post, but I wanted to be sure to provide enough background info..... Sorry for the lengthy read!!)
Honestly that sounds more like a hardware problem than a software problem.
During the early stages of booting, everything that happens is extremely deterministic - meaning that it should be completely repeatable in terms of the order & timing in which activities occur.
So, for it to behave erratically during early boot suggests that it is not software, but marginal hardware. If hardware is barely meeting logic levels or timing requirements, a small amount of random noise (which is always present) can cause a fault to occur at any time - and that sounds approximately like what you are observing.
Further, you replaced your ROM entirely and the problem persists - again suggesting that the problem is hardware, not software.
The most cost effective way of dealing with repair of a $200 tablet is - unfortunately - disposing of it and buying a replacement.
Sorry.
Thanks for the reply!! Shoot, that's what I was leaning towards too. What is the life expectancy of these tablets? I mean, I got 3 good years of use out of it, so I'm not going to complain, but it seems like they should have lasted longer... Would it be worthwhile to maybe grab a cracked screen N7 off eBay for parts and try to get my tab working with those parts maybe? I'm hoping the rumors are true about Google coming out with a new tab this fall, but I'd love to get mine working before then lol...
Hey there,
I am having a recent issue with my phone, where everytime I reset it or do a power off and reboot, the phone will constantly get to the boot logo (in this case cyangemod) and reboot after 5-10 seconds.
It ends up working but only when I let it do this cycle for about 30 minutes or so.
I have looked everywhere, I cannot find someone who is having a similar problem as me.
I am running the latest Cyangemod nightly rom, because I thought the issue was the ASUS rom, I have tried wiping cache, doing a factory reset etc... but no luck.
I also have the latest TWRP recovery and unlocked bootloader.
Any help would be gladly appreciated, Thank You.
Let me know if any video evidence is needed to further clarify, the problem I am having.
Fa7aLX__x said:
Hey there,
I am having a recent issue with my phone, where everytime I reset it or do a power off and reboot, the phone will constantly get to the boot logo (in this case cyangemod) and reboot after 5-10 seconds.
It ends up working but only when I let it do this cycle for about 30 minutes or so.
I have looked everywhere, I cannot find someone who is having a similar problem as me.
I am running the latest Cyangemod nightly rom, because I thought the issue was the ASUS rom, I have tried wiping cache, doing a factory reset etc... but no luck.
I also have the latest TWRP recovery and unlocked bootloader.
Any help would be gladly appreciated, Thank You.
Let me know if any video evidence is needed to further clarify, the problem I am having.
Click to expand...
Click to collapse
Sorry I don't have good news or a solution for you. Just wanted to chime in that you aren't alone. This randomly happened to me on Sunday in the car - I noticed that I suddenly had no signal in a pretty well developed area that I frequent, so I tried restarting and I've been down ever since. Unlike you, I didn't wait it out too long, maybe 5 minutes at the most, when the phone started to get warm.
I have tried going back to stock recovery and firmware and have seen no success. Contrary to other people reporting problems, I hadn't done anything to my phone leading up to this. I think I upgraded the modem several days before, but other than that, everything was running pretty smoothly.
same thing was happening to me after a bad flash. Stock recovery, stock lolipop, wipe data and cache, boot once, reboot to recovery, flash latest MM package on asus's site.
This is the only thing that fixed the bootloops.
Hey all! I'm having a strange issue regarding boot looping that I can't seem to find an answer to on here or anywhere else, I hope you guys can help.
So my T-Mobile Samsung Galaxy S5 (SM-G900T), purchased in May 2014, while perusing Facebook the other day, randomly shut down in the middle of perfectly normal use and started bootlooping. I had never had the problem before. The device had been rooted for months (I forget what method I used) but it was running a stock Lollipop rom. The first thing I did was factory wipe and cache wipe through Android stock recovery. It worked!... for a couple hours. Then the bootloop started again.
I went and sought a new stock rom, believing that somehow mine had been corrupted, and flashed it via Odin. I also flashed TWRP. Clean wipes, new rom, dalvic/etc. wipes, and booted into stock Marshmallow. It worked!... for a couple hours. Then it started bootlooping again. I went into TWRP and tried to wipe just caches and whatnot, but it wouldn't start again. Long battery pulls sometimes allowed the phone to boot, but it started looping again after ~5-10 minutes.
So I installed the Twisted Lollipop but couldn't even get that to boot. I went back and found the earliest available firmware for my device (as I bought mine right after it came out) and flashed it. Wipe wipe flash wipe whatever, and a succesful boot. It was looking good! I was able to install a number of OTA updates. I was at Android 5.1 when I decided to call it a night and hold off on the further OTAs for today. Today I got up and got ready for work, all's well. As I'm getting ready to leave, I allow Google to update some apps, and begin installing Facebook, Spotify, Cap Metro (for my area's public transit system) and maybe something else, I don't remember. Anyway, as the updates are downloading or installing and I'm checking my email, boom, crash, bootloop.
What's going on here? I've never heard of hardware causing boot loops, but could it be that? I dropped my phone (although protected by a Spigen case) earlier this summer and it cracked the screen-- could it have messed with the motherboard in some substantial way? I had noticed it getting hotter and the battery lasting less than usual, but I attributed that to the device's age.
Any help, any advice, any direction you could give would be extremely appreciated. I don't have the capital to replace the phone right now, and I use it all the time. Thanks folks!
Hi all,
For the last 3/4 weeks my Moto X Style XT1572 has been randomly rebooting, usually this is when it is not in use and either in my pocket or desk.
I was running AICP and tried a couple of factory resets. This did not help.
I then factory reset and installed Dirty Unicorns (last weekly). Again this hasn't helped. No overclocking, undervolting, just stock kernels and I have tried handbag kernel.
Still rebooting.
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
rowlers said:
Hi all,
Anything else I can try before throwing it in the bin?
Motorola are not interested in repairing due to unlocking the BL.
Thanks
Click to expand...
Click to collapse
Flash the newest stock 6.0.1.
Without botloader, gpt, no oem commands(don't lock BL).
You need stock system to recognize: hardware or software problem.
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
I seem to have resolved the issue by using the Chill governor. Fingers crossed, but I've not had a reboot for 2 days now...
radon222 said:
I was going to say that my wife's MXPE has been doing the same thing with multiple random reboots and losing constantly losing all her Bluetooth pairings. But her phone is completely unrooted and OEM Marshmallow OS.
Click to expand...
Click to collapse
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
JustLok said:
Mine is doing the exact same: random reboots and it loses all Bluetooth pairings and have to redo them. Running TruePure ROM but nothing else so far.
I did a Dalvik/Cache wipe and it calmed down a bit now, it randomly reboots about 1-2 times a week (over it doing it 1-2 times a day) and when it does reboot, so far, it hasn't lost the Bluetooth pairings yet.
Gonna see if I can go back to stock and install the latest updates and then take it from there, when I get a chance to.
Click to expand...
Click to collapse
Moto X Style , Android 6.0 , Not rooted, pure stock, exact same symptoms as you guys with the random reboots while not in use , losing Bluetooth pairings... Did a factory reset, didn't change a thing. Sometimes, I can get 2 days without reboots, then have 2 in the same hour the next day. It sucks. I'm hoping the Nougat update will fix this, if it ever gets released for my version...
Got 1 doing the same stuff, all stock, gets warm, reboot itselfs, wrong date and time, and no bt pairing
Mine is still doing it too. Not as bad as it was but at least once per day, when idle, sleeping it just reboots for no apparent reason. Not ROM, Kernel and I have factory reset.