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
Related
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Been there, done that
midnighteight said:
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Click to expand...
Click to collapse
This happened with me too but only after updating to KitKat 4.4.2 with Odin, I tried a couple of times and even used firmwares for other regions (mine is international version unlocked so it should work with no problems), I then Initialized the device using Kies 3 to the latest firmware available for my region for the SM-T211, it went OK, I still get crashes, I mean the problem hasn't totally been solved, but it's much much less crashes now than before when device was flashed with Odin (may I say that it was the same stock rom with the same build number from both Odin and Kies 3, still the one from Kies 3 was much more stable)
Hello,
I'm having a weird issue with my Note 7 that I didn't have at all until tried to root for the first time....
It randomly restarts, sometimes is very often and sometimes it take a few hours to do it, but when it does it just restarts out of nothing and when Android loads again it asks me for a password that doesn't even exsits
"To start your device, enter your password" (Picture attached)
This started to happen after used the rootable kernel that was published before SuperSU 2.77 Beta but even reflashing the stock firmware, bootloader, modem, CSC it keeps doing it even when my Android is not yet configured (at the first Welcome screen before setting the phone up), so there is no password at all at this point. I've tried my Google account password, but it doesn't work.
This message is the same that comes up when you select "Secure Boot" so you need to enter a password or PIN to decrypt your data and be able to load it, but I don't have that option checked, and could not be checked when the phone is not even configured.
The way to work around this issue is flashing the no-verity-opt-encrypt mod that is not supposed to be needed anymore after SuperSU 2.77 has been released. So flashing this mod will get me into my Android home screen but it will eventually restart again and I need to flash this mod again.
This is what I've tried so far and it keeps happening:
- Flashed the rootable kernel when it was published and the no-verity mod. I formated data as indicated in the post. Then this problem appeared.
- Flashed stock firmware, bootloader, modem, csc thinking this would remove any trace of the mods I flashed, but kept happening.
- Factory reset from the Samsung recovery, had the "no verity" errors sometimes and sometimes not.
- Flashed other firmwares, bootloaders, modems, csc from other countries but for the same model N930F and kept happening.
- Flashed custom ROMs, formated system, data, everything.
- Flashed stock firmware again.
- Flashed custom ROMS again with the new SuperSU 2.77 and keeps happening.
I have done every single flash that actually exists for the Note 7 and formated everything with no luck....
Has anyone have this issue or had it at all at some moment? If so... How did you manage to get rid of this message?
I hope someone can help, If it was faulty phone I think it would restart at any point even in Recovery or Download mode, but only happens inside of Android.
Seems a common problem I think?
http://forum.xda-developers.com/showthread.php?t=3444510
Sent from my Nexus 6P using Tapatalk
Yep, saw that post... But never seen anyone complaining about the phone asking for a password when reboots (only when it crashes) its like it was asking for a password to decrypt the phone.
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
Hi guys,
I have been having issues with my Australian Moto Z PLay. I have been Romming for a while now and tried to first return the phone to stock using the adb method. Which didnt work (I cant remember why, I think I finished it all and it would only boot to bootloader or recovery). Then tried updating only the modem using this method https://forum.xda-developers.com/moto-z-play/how-to/update-bootloader-modem-to-flash-stock-t3818253 then I tried flashing a few ROM's
The issue now is that the phone turns itself off and on a few times a day. I have launcher crashed quite often and the battery seems to have less life in it.
In short I'm not too sure what I have done wrong. Maybe a few things. Can anyone help me get back to a point where I can install custom ROM's like before relatively safely and reliably? I have tried a few different rom's and had lots of similar issues with each.
ROM - AOSP Extended v5.8 Official
Android - 8.1.0
Baseband version - M8953_10238.63.04.83.01R
Kernel Ver - 3.18.71-OPN28.49-2-g04699f27af49
SELinux Permissive
Hardware - Moto Z Play purchase in Australia retail from Harvery Norman
Boot messages
"There's an internal problem with your device. Contact manufacturer for details" (appears twice, once before needing password, once after. Never needed pin code before)
Thakn you in advance!
....also lots of lag. I'm going someone can guide me to the modem etc settings that should be in my device
EDIT: Apparently this was a result of using the wrong setting for enabling hotspot in PropsConfig. Because all that stuff was set during bootup, deleting apps wouldn't change the situation. Setting worked fine on my Pixel XL, but not here. Changed the setting and all is well.
--------------------------
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Might be quicker and easier to back up your required files and just factory reset.
Texan1 said:
Might be quicker and easier to back up your required files and just factory reset.
Click to expand...
Click to collapse
*sigh* I kinda made this post to avoid that step.
somethingsomethingroot said:
*sigh* I kinda made this post to avoid that step.
Click to expand...
Click to collapse
I know, it's just that it sounds like you've already disabled some things that could be causing it, which hasn't helped. If it was me, with something like constant reboots, I'd want to start fresh just to make sure they are eliminated for good
somethingsomethingroot said:
So, this is a weird issue I was curious about and may have missed on my searching. Every time I reboot the phone, when I got to log in it immediately follows up with a soft reboot. It's been happening for a while, and I'm not sure the source of the issue.
Running stock 12 ROM and rooted, but I disabled SU, modules, and Nova and am still running into the issue.
Click to expand...
Click to collapse
I've seen reports of "random" (=not intentional) reboots after
+ booting up the phone
+ using the FP scanner
+ making videos or shooting photo
+ doing a firmware update (I've seen both reports of ppl that "officially" OTAed & used manual flashing)
+ doing nothing
+ doing something
Some were able to fix their issues by factory resetting, some needed replacement devices. Some reported that even after a factory reset, the issue still persisted, but they were able to fix it by NOT using a backup via cable, some reported that even the Google Drive backup "corrupted" their phone (fix after setting up everything by hand from scratch). Some even reported their issues to get fixed via a software update.
So it seems to be connected to hardware (= replacement device) and/or software simultaneously (=fix via reset).
Strange this is since there are also numerous reports of Samsung owners that upgraded to A12 about random reboots. So it might even be something Android 12 related, or it's just Samsung also implementing similar bugs without it being A12 related (unlikely, since the reports seem to be centered around people using the new A12 update).
I also had the random reboot problem (~ 6 times a day, when doing nothing, it just rebooted when the phone layed on the table in idle). I wasn't able to fix it via a reset, so I got a replacement device.
I also have the "random" reboot problem on my Pixel 3 since upgrading to Android 12 (never had any issues all the years I've been using that phone), so that issue is clearly caused by A12, but I haven't troubleshot it/ tried to solve it, since I don't actively use the phone currently.
Aside from trying a factory reset and minding the backup issue (especially backups that you got from phones that did NOT have Android 12), there is not much more that you can do (ofc you could also use the Pixel repair/android flash tool to do a "clean" install of Android on your phone). Next step would be to contact Google.