I'm troubled with nothing but security errors no matter the custom rom that I use for my specific model. Sometimes it happens after a reboot or sometimes after all apps are updated. Is there something I'm missing here or something I'm forgetting to do? If you need me to get more specific, I'll try.
Related
I've got reports when for some users, the device would freeze on boot when using older bootloader versions (3.41 I guess?) and custom kernel. This hang apparently disappears if the user upgrades to the newest bootloader.
Does anybody knows why this happens? I know Metallice has this issue with his kernel, so he tells users to upgrade to newest bootloader. Does anybody else have the same issue, maybe pinpointed the reason why this happens?
It doesn't cause any real problems because newest bootloader works okay, but I would still like to know why it happens.
Tasssadar said:
I've got reports when for some users, the device would freeze on boot when using older bootloader versions (3.41 I guess?) and custom kernel. This hang apparently disappears if the user upgrades to the newest bootloader.
Does anybody knows why this happens? I know Metallice has this issue with his kernel, so he tells users to upgrade to newest bootloader. Does anybody else have the same issue, maybe pinpointed the reason why this happens?
It doesn't cause any real problems because newest bootloader works okay, but I would still like to know why it happens.
Click to expand...
Click to collapse
I found after wondering the same question that it doens't actually hang but people are to impatient to wait and see. I also found that on a dead battery even on the newest bootloader even if there is enough charge that it can hang and a reboot is needed to be forced apon.
Google made an announcement that they added some extra suppliers for certain components, I think some different storage chips, that required the new boot loader. That's probably the issue.
[speculation]
There is no hardware reset/change which occurs when the bootloader transfers control to whatever comes next (recovery kernel, OS kernel, etc) other than what the kernel itself will attempt to do on it's own as it begins initializing, so beyond things which are explicitly passed to the kernel from the bootloader (e.g. the kernel boot command argument list), whatever hardware state - clocking configuration, rate, or a whole slew of other device initializations - that the bootloader sets up can be regarded as an implicit set of "hardware state" parameters for the kernel which follows. (It is impossible for the kernel to reset *everything* back to a known state via a hardware reset, as this would just re-launch the bootloader)
So, the scenario described certainly seems feasible enough if the kernel code makes inappropriate assumptions about inherited state, sequences initializations differently, etc.
I was poking through TWRP's kernel log the other day, and was somewhat shocked to see a message about failure to read the mmc device's (Flash Memory!) partition table - followed immediately by an indecipherable message about a clocking change .... and then normal sorts of messages about partitions found. Rather unnerving as that suggests something extremely fundamental for a recovery (partition layout) is being attempted initially in a sketchy fashion.
It does seem rather odd that some mismatch between the kernel's presumption of inherited hardware state would manifest itself in late boot behavior - the boot animation screen for the OS is in /system, no? Seems like if you are seeing things progress that far along the kernel probably has not failed in any dramatic way.
Anyhow - why not just put the question to the M-kernel dev in his thread, or give him the URL to this thread and ask him to comment?
[/speculation]
cheers
[ Edit ] I suppose I should have added that if you experience the problem yourself with a set of kernel mods, you might be able to come up with a hypothesis by bisecting backwards towards a reference commit that doesn't have the problem. Seems like a lot of work though, given that - for lack of Asus bootloader source code - the bootloader's behavior changes between releases are opaque.
I spent a long time trying to figure it out before the bootloader update fixed it. Couldn't. The problem would just appear randomly. I tried reverting patches, resetting git, trying to find a cause, but there seemed to be no definite cause. One patch removal would seem to solve it, and then it would come back after adding another, dissapear when I added back the patch I thought was causing it, etc. etc.
I now don't see it as an issue since any bootloader beyond 4.1.x fixes this.
was on 3.34 when started to experience this the only way it gets fix for me is pressing the up/power button
and the hang was not just in boot even going to the recovery via fastboot also hangs
i think the only fix for this is updating bootloader
In an attempt to deal with massive instability I was able to upgrade from Samsung Stock to SlimKat 4.4.4r1. The instability problems remain but now I can't install apps. I have tried to flash to Carbon ROM but that doesn't take.
Curiously, all of the indications are that the apps and ROMs are installing but they in fact they actually don't.
The device doesn't even stay on long enough for me to alter a Setting, it trips over in a matter of seconds and reboots. Each time, I get the error message “Unfortunately, The process android.process.media has stopped”.
Could this be the Brick Bug manifesting itself? Perhaps if I repair the PIT that would fix it? Luckily I can access TWRP 2.7.0.0 recovery, I have tried to upgrade to TWRP 2.8.0.0 but that has failed also.
Any suggestions would be welcome
Hi, I would like to thank all those who took the time to read my description. Clearly it has you flummoxed too.:laugh:
In the meantime, I tried flashing Stock ROM but no joy and then I tried repairing the PIT, no joy there also.
My options now are either to ask Samsung to take a look or else wait for a functioning Tab with a broken screen to come along. My Tab is in superb condition and it would be a shame to let it go without at least making another attempt at rescue.
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Did you try SuperSU V2.76?
[CENTER[/CENTER]
sandeman11 said:
I was trying to root my OPO by flashing SuperSU Beta_V2.52 but after each flash my OPO goes into a boot loop, flashed several builds of SuperSU (inc; beta's) and all of them result in a bootloop. To be on the safe side i did fresh installs of CM13 via bootloader, no result.
Pulling my hair what the solution will be. Dev's from "Cyanogenmod-team" are aware of this problem but find its not there problem to solve...:
It needs to be said that this issue with SU is something that is outside the scope of official support. We neither recommend or support SuperSU installs, as it opens the device up security wise in ways that most users (not all, some do the homework to understand what's going on) either ignore or are ignorant of. So if there's a bootloop happening, you are going to need to diagnose it on your own, or with others help here. You can also check XDA as well.
Click to expand...
Click to collapse
Happened to me couple of times while switching from cm12.1 to cm13. Turns out marshmallow doesn't really support superSU v2.52. Try v2.76 instead. Worked like a charm for me
P.S.:update your TWRP to version 3.0.
Hello,
I have 2 Mi4i phones and i have to encrypt them for my work (and my wife's work).
With Miui i can encrypt them, but i don't want to use this.
I want CM13 or Lin14.1
Problem is that on both custom rom's, i can choose to encrypt.
After that it shows the Android robot for a second or 2, then reboot's the phone.
After the restart the phone is not encrypted and every time i try it, i get the same result.
Both rom's are clean installed, no extra's are installed (no kernel etc.)
Is this a bug, or do i have to change something to get it to work?
Anybody any idea what is going wrong?
elot01 said:
Hello,
I have 2 Mi4i phones and i have to encrypt them for my work (and my wife's work).
With Miui i can encrypt them, but i don't want to use this.
I want CM13 or Lin14.1
Problem is that on both custom rom's, i can choose to encrypt.
After that it shows the Android robot for a second or 2, then reboot's the phone.
After the restart the phone is not encrypted and every time i try it, i get the same result.
Both rom's are clean installed, no extra's are installed (no kernel etc.)
Is this a bug, or do i have to change something to get it to work?
Anybody any idea what is going wrong?
Click to expand...
Click to collapse
Yes this is a bug :|
Anyway, aosp custom rom based on miui 6.6.10
Which have encryption bug too .-.
So this feature ( encryption ) won't work for now
Hi. I have a modified rom installed (Wycked 2.0) and I like it a lot. However, just as it has happened to me in other modifications, I can not activate the encryption of android. Something does not work well ... I activate the encryption option and there is a good time working and after a few minutes I notice that in reality never encrypted anything. Does anyone experience this same problem? It has happened to me with "Fast rom", "xperience Os 2.5", "onkiller".
If someone can guide me with this problem ... I would like to encrypt my phone, but could it not work with modified rom ?
Greetings.
elsereno said:
Hi. I have a modified rom installed (Wycked 2.0) and I like it a lot. However, just as it has happened to me in other modifications, I can not activate the encryption of android. Something does not work well ... I activate the encryption option and there is a good time working and after a few minutes I notice that in reality never encrypted anything. Does anyone experience this same problem? It has happened to me with "Fast rom", "xperience Os 2.5", "onkiller".
If someone can guide me with this problem ... I would like to encrypt my phone, but could it not work with modified rom ?
Greetings.
Click to expand...
Click to collapse
If you encrypted a phone with any modifications (root, custom rom, etc) you will be put in a bootloop. If you want your phone to be secure and encrypted, uninstall TWRP and any modifications, or better yet flash stock firmware from updato.com
You cant encrypt it through settings because you have flashed some sort of encryption breaker, required to access root without bricking.
Hi .. I have rescued my bootloop phone many times. However, that is not my current problem. I asked if any user of the modified rom that I quoted in my first message managed to encrypt the phone successfully. When I try to activate data encryption, I do not even get an error. It simply restarts the phone after a few moments and everything remains unencrypted.
Any guide will be welcome!
Greetings.