I haven't rooted or made any kinds of major adjustments but still there will be times when it will randoms just restart for reason I'm unaware of. What can I do to track down the reasons for the restart?
On a side note: really considering rooting since it doesn't seem like this tablet is going to get marshmallow. What roms are out there that have good support and still allow me to use the S-Pen?
I don't know how to track down but how about flashing stock 5.1 rom with odin?
Maybe it can solve the problem
Related
On NF1 based roms, does anyone have issues answering calls like I do? I keep swiping to answer and it won't work, most of the time I miss the call. I didn't have this issue on an older build of TW.
No problems here. Bad flash, maybe?
Sent from my SM-N900T
Have rebooted your phone anytime lately? Also, if you have lots of tweaks you may be slowing down your phone responses.
Weird issue. I download two different ROMs from different threads, with the same issue. I don't known what the problem could be. I don't usually run a lot of tweaks on TW, I keep it mostly stock most of the time, except, that it could be related to a custom kernel. I'll try a stock kernel
Haven't had that issue. That's including experiences from 2 different note 3's. Stock and rooted.
Tried stock kernel. Same issue. I'll have to try to go completely stock and see if the problem returns. I don't know what it could be. Everything else is fine otherwise. Am I able to run the older kitkat ROMs with the newer stuff? If I can, I'll try to confirm that I don't have an issue with those.
EDIT: happened to try the Canadian S5 port, and I have no issues with answering calls. I will just use it for the time being.
I'm still having this issue and I'm completely stock. I don't know what's wrong. It doesn't exist when I'm running the S5 port or an AOSP rom. Anyone have an idea?
EDIT: Found out my baseband was outdated. It didn't update with the firmware update from Kies. I rooted the stock rom, and used Triangle Away, then Odin flashed the modem, things are well now.
So i updated my sm-t210r (worst decision ever) and instantly began noticing bugs one of which is my apps stopping at random even system ui and touchwiz home. I used the latest philz touch recovery did a clean wipe and flashed nolekat`s rom and the same thing happen apps keep stopping, so i did a test i flashed the same rom in the same exact way on my sister`s tab (not updated) and what a surprise everything works great on hers, no random stops, great battery life, even the screen and graphics are more whiter than mine, so i concluded that its this 4.4.2 updated that is causing all the problems. So what i ask of anyone is steps to completely downgrade romoving the new bootloader in the process, i already tried flashin the old 4.1.2 through odin but all the issues remain, any help or tips would be apreciated
help guys no matter how tedious the process i really want to downgrade and remove this bootloader
Gonna try my best to give as much information as I can to make it easier for anyone good enough to try and help me with this. So I have an HTC One M9, from Sprint right here in the good old US of A, and it was working fine until I got the OTA Marshmallow update. At that point, apps started crashing like crazy (even after all were updated) and the status bar at the top of the screen and navigation buttons at the bottom would randomly disappear for several seconds after pressing the volume buttons, even after wiping the cache for both the system as well as the individual apps in question.
"No problem," I thought, "I'll just root it and install a custom ROM like I have with all my Android phones in the past." So I did that and tried Android Revolution, ICE, and ViperOne (all the latest versions), and every one of them had the same issues with programs crashing, the volume buttons messing up the screen, and so on. Actually, I couldn't even get through the setup wizards for any of them because those kept crashing too, and I had to use TWRP to rename the HTCSetupWizard.apk just to get to the home screen. Once there, my home button was inoperable, and no notifications or usual buttons like WiFi, Bluetooth, etc appeared when I pulled down on the status bar (which I discovered is what Android does if you don't complete the setup wizard).
At this point, I thought, "Well, maybe it's just a problem where my phone doesn't like Marshmallow for some reason. Let me try downgrading to Lollipop and see what happens." So I got the latest Lollipop versions for each of the aforementioned Custom ROMs, and they all ran smooth as silk, which tells me it's not an issue with faulty or damaged hardware. Only problem was that mobile data wouldn't work, on either LTE or CDMA settings.
I tried changing network modes, popping my SIM card in and out and rebooting in various combinations, but none of it worked. I couldn't even get into APN settings since the phone couldn't seem to detect my SIM card and had the APN menu greyed out. I thought I might have somehow damaged the SIM card with all the time I spent screwing around with the phone, but just to see what happened, I flashed a Marshmallow ROM back onto the phone and, sure enough, LTE service was right back.
I did some more research and saw that the issue may lay in the fact that the firmware (which is currently OS version 3.41.651.4) is not usable for Lollipop OS versions, and since my phone is S-ON (and I'm really not interested in spending $25 to S-OFF it), I'm not able to downgrade the firmware or, I assume, the radio firmware (if that's something you can even do separately from the "regular" firmware. Currently version [email protected]).
At this point, I'm really not sure what to do, and could use some guidance. I feel like my options basically boil down to the following:
1)Find a way to make Marshmallow ROMs more stable, possibly by reinstalling the firmware or some other method someone here might know that I don't,
2)S-OFF my phone, downgrade my firmware to something Lollipop can work with, and try a Lollipop-era ROM (not ideal), or
3)Go back to stock and hope Sprint pushes down an update my phone can use.
After going through all that, does anyone reading this have a recommendation for which of these options would be best (and how to go about them), or possibly offer other ideas I haven't come up with during the week and a half I've been researching and trying to fix it myself? I'm not hellbent on any particular option, I just want my phone to work (all of it) without constant crashes and glitches. Thank you to anyone who read all that and is still moved to offer help!
If you can run lollipop based roms you'd be on Lollipop firmware.
If you're going to mess around with aftermarket software you need s-off. If you don't s-off then you are risking unrecoverable bricks.
Sent from my HTC One M9 using Tapatalk
Okay, so if I'm on Lollipop firmware, would it stand to reason that that's why I'm having trouble running Marshmallow ROMs, including the stock ROM from Sprint? If so, what's the best (and safest) way to update it?
Hello,
I was facing some of the problems everyone is reporting here about random restarts and bootloops even (and mostly) using stock firmwares. As many of you started to have the problems after updates my problem started when I tried to root for the first time when SuperSU was not totally working yet. These problems didn't stop even flashing everything to stock (bootloader, modem, firmware, csc) and other stock firmwares from other countries so I was thinking that my phone was faulty too.
Every reboot my phone asked me for a password that I never set, so there was nothing to put there and I always had to reboot into recovery and flash the "no-verity" script or else I would get stuck in a bootloop or the phone asking me for a decrypt password (that didn't exist).
Sometimes when the phone randomly restarted gave me the "verity encryption" error at the beginning when using the stock recovery, if using TWRP it asked me for a password after semi loading Android (since it didn't found the official recovery to show that error from it), so I always suspected that the Samsung encryption was causing all my problems. Tried everything and even made a post about it (http://forum.xda-developers.com/note-7/help/random-restarts-password-doesnt-exists-t3450678)
So I kept waiting for something that disabled the phone encryption to verify that this was the real cause of this random behaviour before going to Samsung for warranty. Finally @Tkkg1994 came up with the Hydrakernel that disables the encryption so after trying it and formating everything MY PROBLEMS ARE TOTALLY GONE.
My suspects were finally confirmed..... The Samsung encryption was causing all these sh1ty problems (at least in my phone).
So everyone that is flashing stock firmwares even going back to old ones, it seems that doing this doesn't fix anything once you got into this problem for the first time, only disabling the encryption solves it. So my recommendation would be to disable the force encryption from Samsung by using the Hydrakernel and testing again (http://forum.xda-developers.com/note-7/development/kernel-hydrakernel-v1-1-t3452433)
I would like to thank all the devs that are doing their best effort to give us a free Note 7 to enjoy. @Tkkg1994 @dr.ketan @Chainfire it is very admirable that common people like them can solve things that not even Samsung has figured them out yet.
PS: Have you guys flashed this ROM and kernel instead of stock firmwares and continue to have problems with your Note 7??? Give your feedback!!!
Interesting, keep us posted with your phone status...
nice job keeping on testing & we waiting your next result
Ever since the MM update, my wife's SM-T807R4 (US Cellular version) freezes frequently when browsing and using any app which requires touchscreen input. It's almost unusable unless one doesn't mind closing and opening the case every 2 or 3 minutes (or hitting the power button twice.) I have recently rooted it and disabled many of the Samsung apps as well as some Google apps we don't use. It hasn't helped. I have not yet flashed TWRP but I have instructions on how to do so.
I don't know if the MM update caused the problem or there's a hardware issue that just didn't seem to arise until after that update. In any case, I'd like to return to Lollipop and see if that improves things. Once TWRP is available, can I just wipe everything and flash the Lollipop ROM with TWRP or do I have to flash it with Odin? Anything else I need to do to prepare?