Database Info

[DISCUSSION][4.3] Knox Bootloader

As most users know, people who flashed Sammy's 4.3 stock with ODIN have the infamous and (yet) unremovable Knox bootloader. This bootloader is known for causing numerous FC's, freezes and random reboots to people who flash custom roms/kernels.
For me (and for most users, I believe), the custom roms/kernels are the main reason why I love Android (and xda too), thus the Knox bootloader has became one hell of a headache for me and other people who unfortunately have been naive enough to flash stock 4.3 in the early days.
It doesn't matter if we have flashed the Knox bootloader by oversight, or just because we didn't know it was included in the stock 4.3 (as the i9300 stock 4.3 was Knox free). What does matter, is that many people are now having problems in enjoying their favorite custom roms and kernels thanks to this evil invention by Samsung.
Therefore, and as I didn't see any thread like this one, I created this thread so we can discuss what we can do to, at least, minimize the problems cause by this bootloader. I am not even dreaming with restoring our warranty. At this moment, I just want to peacefully enjoy the custom roms and kernels that the great developers of xda release for our beloved I9305.
Although I haven't seen many developers talking about this problem in our device's threads, I noticed that some have already tried to trick the bootloader and avoid the FC's (like @Hbohd, for example). However, I think that this is a huge task and should be done with the help of everyone. I know by first hand that we have many talented developers working for our device (and for others too) and I'm sure that we, united, could, at least, try to do something about this and teach Samsung not to mess with our devices. I have always stood for the policy that says "I've paid for my device, thus I should be able to do anything I want with it".
Note: If any of you developers have some idea but don't know how to test it because you don't have the Knox bootloader, I don't mind to test it on my I9305 (and I'm sure that other users don't mind too). I'm using Alliance ROM v2+ with Boeffla Kernel v5.1+ and Knox bootloader.
Let's start the brainstorming: (I warn you guys that I don't know much about Android developing, so please bear with me if I say any stupidity)
- As we know, our brother i9300 doesn't have Knox included in stock 4.3. As one the main differences between I9300 and I9305 is the RAM, maybe this Knox thing is something that uses some RAM?
- I can reproduce a FC that only happened to me since I have Knox (I am supposing that Knox-free 4.3 users don't have this FC): everytime I benchmark my I9305 with AnTuTu, it FC's in the 3D test. Always. Maybe Knox is related to Mali drivers?
- Can we trick the Knox bootloader by changing SELinux status or Samsung root restriction status? @Hbohd already tried something like that but it didn't seem to be conclusive. But I guess that at this point no possibilities should be eliminated.
- And what about restoring the old bootloader from 4.1.2? We already know that restoring previous nandroid backups or flashing stock 4.1.2 from ODIN are useless...
So, what you guys think?
Please, be free to say anything you want, as long as it is on topic. In my opinion, we are currently far away from the solution so any help is welcome

I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I have Knox and running cm 11 no problems here..
Flash counter is at 6 maybe its The boeffla ?
Tested antutu no problems here
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
Well, that's a surprise to me, thanks for informing.
Regarding what you said, it seems that Knox only brings problems when you use a custom stock based ROM or Kernel (or both).
However, you (and other people who have Knox + non-stock ROMs) would still benefit from a possible solution that would revert our bootloader and restore our warranty. If that is ever possible

My counter is on 4 but for knox there is a special/ extra counter.
Maybe some modders can try let the boot loader think that the
moded kernel is an original stock kernel?
name installation scripts with original kernel letters
and is it possible to make the modded kernel with same filesize
like stock kernel?
regards
sonic76

I think is custom kernel wich causes all your troubles . I experienced same problems , even network signal loss with custom kernel .
Lately I am using kenar2's deodexed , rooted rom with kernel replaced to the original . I have no problem and battery life is great . I uninstalled all bloat including Knox software .
Let's give custom kernels some time to mature and I think we can continue to use them and custom roms like we used to do.
Of course we have to live with voided warranty .

I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app

Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?

oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Did you tried different version of boeffla and the yank kernel to.

Why do you think you have knox bootloader? Even if you have it, question is does it work in a way it works on newer devices, where according to Samsung, bootloader uses eFuse to flash/check knox flag.
When you reboot into download mode, do you see knox flag mentioned. Counter someone above mentioned has nothing to do with knox, and can be set zero with triangle away, chain fire's app.
Sent from my GT-I9505 using Tapatalk

You cant set Knox to 0×0
Only ROM counts :thumbup:
Sent from my GT-I9305 using xda app-developers app

toeterbaas said:
I do use a custom ROM.
Its cm 11 but The kernel is standard and i have zero problems here.
I used other roms to no problems.
I had problems with stock ROM rooted and boeffla kernel.
So it must be The kernel.
I am not affraid of The waranty because never ever one of nu phones broke from Samsung and i had a lot of Samsung phones
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
On AOSP roms there are no problems. They appear on 4.3 Samsung Stock roms + Knox bootloader + custom kernel.
oswade said:
Not sure if anyone has mentioned this before, but I will describe the FC/freeze behaviour in a bit more detail, based on my experiences running boeffla for at least a few days. My config is stock rom (self-rooted), knox bootloader. I do run a few xposed mods but turning xposed off doesn't seem to affect the problem.
- At boot everything is perfect. I can open any app without force close.
- After an hour or two, or it may be related to the number/type of apps opening, force closes or freezes will begin.
- Some apps seem to force close more than others. Chrome force closes often but other apps like stock internet seem generally OK.
- Often, after the first FC (or a few), the app will not be able to run again (launching it results in immediate FC or black screen).
- The longer the phone is on (or perhaps in use), the more FC's will occur. Eventually, I even had system apps (e.g. Settings) FC/refuse to open and the phone becomes unstable enough to reboot. It doesn't seem to get much worse when idling though - phone generally stays stable overnight (if it was stable when I went to sleep).
BTW, has anyone requested updated i9305 sources yet from samsung or knows the best process to do so?
Click to expand...
Click to collapse
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!

Hbohd said:
Thanks for your input, that is something new man !
In fact, I have just seen a new sourcedrop for our i9305 - might be interesting!!!
Click to expand...
Click to collapse
no worries .
Nice, i hope the sources provide us with an easy fix!

Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk

Edit: forgot to turn on logger

Goldie said:
Post some of the dumpstate_app_error.txt.gz from data/log after the fcs
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
Here is mine, right after AnTuTu FC in 3D test.
I rebooted the phone, forced the FC by doing a 3D benchmark and then uploaded the file. I hope it is what you want

Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk

Goldie said:
Thanks but you need to turn logging on in boeffla settings first
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
You're right... My bad! Here it is again, same procedure...

I have an idea how to restore knox-free bootloader, maybe all we need is unbrick SDCARD (like for i9300 http://forum.xda-developers.com/showthread.php?t=1916796) made on i9305 with 4.1.2 room. I have heard of several cases where I9305 came into SDCARD mode and overwrite curent bootloader with data of the sdcard. For go in to SDCARD mode they hold volume up + volmne down + home + power in the same time.
All I need is dd image for unbrick SDCARD for i9305 and I will try.
Sorry for my english.

guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.

oswade said:
guys try out boeffla beta 12. i think it has fixed the knox bootloader problems but itll be good if someone else can confirm.
Click to expand...
Click to collapse
I have Internet FC, Gapp's FC, my mobile was 2 times down means display black and mobile won't wake up,
no reaktion by long press power button so i have to pull out the battery....!
I have boeffla beta 12 with no tweaks over boeffla app!
regards
Sonic76

[Android 5.1] Random reboots.

Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.

Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.

Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app

I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?

I don't know exactly what undevolting implies. Could you give me more details please?

vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.

I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?

vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.

I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.

vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.

My n5 reboot today without any reason

That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?

I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance

vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615

having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.

Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.

How to cancel an OTA update that has started to download?

Hello,
I have a Galaxy S6 running the latest 6.0.1 XEF stock ROM (no root) before Nougat.
I have choosen not to update to Nougat for the moment as I prefer to wait for better Nougat releases.
I was quite sure the settings of my S6 were set in order to disable search/install of updates. But yesterday, while connected to my network using Wifi, my S6 has started to download the Nougat updates! But, as I said, I don't want it for the moment. I stopped Wifi, then it stopped downloading the updates. I tried to go to the update settings of the S6 to disable updates but it is not possible now to go the "About device > Software update". And each time I connect to WIFI, it resumes the download of the update .
In the application manager, I found 2 apps related to "Software update": for only 1 of them it is possible to stop it and remove cache and data, which I did. I thought I would have cancelled the download of Nougat update and bring me back the possibility to disable update. But unfortunately, it has no effect. I also tried to wipe cache partition, but the same: it has no effect and each time I connect Wifi, it resumes the download of the update.
So, how I can cancel the download of the update and be able to access to the settings to prevent from downloading/installing it??
Thank you for you help!

There's no need, Nougat is stable now.
If you still doesn't want, let it download the update (because you can't cancel it) then block notifications from both updates apps from the settings.

iDroid27210 said:
There's no need, Nougat is stable now.
Click to expand...
Click to collapse
Really? Latest release for XEF has still the same changelist and I read several complains regarding battery life and lags into the Gallery app for example...

stephg27 said:
Really? Latest release for XEF has still the same changelist and I read several complains regarding battery life and lags into the Gallery app for example...
Click to expand...
Click to collapse
I had very bad battery life on Nougat, i was on UAE firmware. When i bought this second S6 i made a decision to stop using custom roms so i tried to flash another firmware, took the last XEF ( from April) and flashed it 2 weeks ago, my battery improved a lot specially in standby , no issues or whatsoever.

Thanks for your feedback!

phone is full, now what?
Sorry to hijack this thread, but it seems the best fit.
Basically the same question as above: "How do I cancel an OS update download in progress" on my Samsung S6
Reasoning is a little different though. Accidentally I started the update process but during the download my phone ran full.
And as you might know, with a full phone some apps dont work.
Of course Android gives me the option to remove files and apps but immediately the free space is occupied by the running update....
Any ideas?
tia!

Android Nougat ROMs List for the BLU Life One X 2016

This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.

Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.

elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.

BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.

elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.

review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.

BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.

Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?

tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.

elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?

tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.

elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?

tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.

elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?

tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).

Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.

Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.

tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.

Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]

tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.

Since Android 8.0 its lagging

Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT.
So i just let Google and Samsung restore all my stuff. Then i installed TWRP and root via the no-verity-opt-encrypt-6.0.zip and magisk v16.0.
After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags.
e.g. opening of Snapchat. Like it's closing so hard in background, that all services need to restart.
Instagram and OneDrive are shown many time as stopped working and i don't know why. Maybe Instagram caused by XInsta?
Okay i recognized OneDrive isn't even working anymore. Was already on Android 7 a problem. Does not seem to be compatible to something else.
You have any ideas or need any information? Let me know

try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.

achour7 said:
try a factory reset. Personally, I use a modified stock rom (light rom) and it is very stale and very fast.
Click to expand...
Click to collapse
Antutu Benchmark gives me 164336 points, so it seems literally to be normally, but i know all loading times of Snapchat and Instagram and so on are so much longer.
I will try to flash it again and to start clean. Just the copying of the WhatsApp folder needs so much time.

So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???

CptDayDreamer said:
So I'm asking again. Nobody else got problems? I still dont get the data mount error fixed, because when I install Magisk it's broke again and my whole phone seems to lag. I dont know if it's because of my Xposed modules or Magisk modules. But for example with the update everythings goes slower even if Antutu says something else. Snapchat needs years to start. Is it cause of dual messenger? But I don't think so. Or when i'm in the car and using Google Maps and Poweramp and tapping skip on my car radio for skipping in bluetooth there is a delay of 20 seconds sometimes so wtf.
Any speedups for S7 or Android 8 on S7???
Click to expand...
Click to collapse
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.

achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3

CptDayDreamer said:
I like TouchWiz. Is there any ROM that is similar? And never heard of another kernel to fix that. Is that kernel better? Last time i changed kernel and stuff was with my Galaxy S3
Click to expand...
Click to collapse
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.

achour7 said:
Try an other rom ( official or custom ), m'y S7 exynos is smooth and stable.
For data partition, dis you flashed Tgp kernel ?
You Can finde a custom recovery in Tgp kernel thread, it fix that issue.
You need to download flashify from play store to flash the custom recovery.
Click to expand...
Click to collapse
achour7 said:
Tgp kernel gives a good battery life ans smooth UI.
If you didn't flashed a kernel, you need to wipe data partition by writing ''yes''
And you will Lost all you data, so you need to save you data on external storage, hard Drive or computer.
Click to expand...
Click to collapse
Works it without problems? Bro do i just need the kernel or also like I found out this THE GALAXY PROJECT ROM ? It looks like TouchWiz ha?

I have stock phone without root and my phone is getting really extremely hot since it was updated to Oreo.
Even by doing something like being here in the forum is getting so hot that is uncomfortable on my hand

CptDayDreamer said:
Hey guys. Two days before i updated my phone manually via ODIN on a german version G930FDBT2ERG2_DBT... After that i installed XPosed via the XPosed Installer app. I think since i did that or maybe before, every app needs hours to start and lags...
Click to expand...
Click to collapse
If on stock then resources being consumed with bloat. If issues began around installation of xposed wouldn't it make sense to uninstall modules and xposed and see if improved over the next day? Restoring apps and data and rooting and moding is a lot of stress on device all at once, then it gets so warm it starts to go glitch. I've been there too. Best thing is to let it sit 30-60 min after set up finishes to cool off. Reboot too once restored data completes.
Almost makes me miss the rip out and replace with cool fully charged battery days of my S4 [emoji91]
Sent from my SM-G930W8 using Tapatalk