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

[BS_FREE_Lollipop_5.0_Rom_BOK3_Based]

This is a modified version of @jrkruse stock BOK3 deodexed ROM with all(or most) of the stock BS removed.
This BS_free ROM does not have two different versions like his previous build. I left only the Samsung apps needed for UPSM and HD calling to work.
INSTRUCTIONS:
I've included the links needed if you want to use xposed and Viper4Android. If you chose not to use these features, then skip them in the flashing process.
I personally prefer using safestrap when clean flashing a ROM, but you can use flashfire if you must.
1) WIPE EVERYTHING!
2) Flash No_BS ROM
3) Flash Extra toggles
4) Flash No_Bootloader_Rooting_Tools_For_S5_Lollipop_V3.zip
5) Flash xposed-v75-sdk21-arm-arter97-snapdragon.zip
6) Flash Viper Policy
7) Flash Viper4Android
8) Flash BOK3 Firmware without bootloader
9) After first boot, open up Viper4Android and install the driver. Note: Sometimes it takes 2-3 times before the driver will install.
I have confirmed that @jrkruse 5-way reboot with Safestrap works on this ROM!!! If you want to use it, add it to the end of the flashing list. 5Way_Safestrap_Reboot_PM. As a side note, if you use 4-way reboot in Wanam Xposed, then that feature needs to be disabled for 5-way reboot to work.
The ROM should boot in about 8 minutes. The music app will force close everytime the device reboots, but it does work normally.
Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
NO_BS_BOK3_ROM_DEODEXED.zip
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.
Update: NO_BS_BOK3_ROM_DEODEXED_V3.zip is now available. The flashing process is the same. I updated busybox and removed SBrowser. I also implemented the signature verification fix by @jrkruse, along with default animation scales set to 0.5x.
Update: NO_BS_BOK3_ROM_DEODEXED_V4 is now available. The flashing process is the same. I updated all apps, except for YouTube(xposed purposes). I added the missing VPN apk as well. Let me know if there is any other issues with VPN related settings.
Update: NO_BS_BOK3_ROM_DEODEXED_V5 is now available. The flashing process is the same. I updated all apps. I added the headphone app notification, voicenote, and SPrintSpooler. I don't use voicenote or SPrint, so let me know if there are any issues with these apps.
Note: Don't pay attention to the 1- prefix in front of some of the ROM versions. I prefix all my flashables in my ROM folder with a 1-, 2-, 3-, ect, so that I have them all in order when I flash them instead of having to remember the order every time lol. I forgot to remove those prefixes when I uploaded the ROMs.

I am looking forward in seeing how this Rom is doing.

Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?

Snoopy679 said:
Question Do i need to install all items list in OP or can i just install first and last as that is all i am needing?
Click to expand...
Click to collapse
First and last will do just fine.

Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.

jjdavis699 said:
Works like a charm! Just wish someone could get Quick Glance working. I've seen it work in MOAR, but the 3minit mod that's included is a complete turnoff for me.
Click to expand...
Click to collapse
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?

CVertigo1 said:
Do you mind elaborating on what Quick Glance is? Are you referring to where you wave your hand and it wakes up the display to show notifications?
Click to expand...
Click to collapse
That's the one.

I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay

CVertigo1 said:
First and last will do just fine.
Click to expand...
Click to collapse
do i need to do a clean install or just flash over @jrkruse work that i am currently using?
[VZW_Stock Based TW Rom][5.0 Lollipop BOK3 Build Deodexed] by @jrkruse ?

I dirty flashed this over his stock BOK3 and it worked, so you should be good.

CVertigo1 said:
I've used this in the past and I wasn't a big fan, but I didn't spend a lot of time trying to get it properly configured. I only tried it to see what it did. I personally don't like motion features.
http://repo.xposed.info/module/com.dvd.android.xposed.enableambientdisplay
Click to expand...
Click to collapse
I actually tried that already. It's honestly not great. Oh well. Maybe if I could figure out a way to strip 3minit...
I fell in love with motion features when someone stole my moto g and I had to pick up a Lumia 640. Great phone, but not an android

I'm on BS_FREE_BOG5_GOOGLE_V2_Deodexed and just updated with @jkruse New Root Tools For S5 Lollipop V6. Already enabled Lollipop Safestrap Recovery again and Flashed Most Current OG5 Firmware_No_Bootloader and current OG5_Kernel. Can I just use that and wipe everything flash this aside from 3Minit Battery without losing Root?
Sent from my SM-G900V using Tapatalk

Just to be clear, are you asking if you can run this on BOG5 firmware?

CVertigo1 said:
Just to be clear, are you asking if you can run this on BOG5 firmware?
Click to expand...
Click to collapse
No, I mean using the V6 Root Tools instead of the V3 as indicated in your directions...
Also, I'm hoping that with a new install I will regain ability to work with Accessibility Options in Settings.
Idk if it makes a difference but I have Original GS5 Rooted, never taken OTA, always ONLY used XDA sources for ROM/Firmware/Kernels.
Sent from my SM-G900V using Tapatalk

My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.

CVertigo1 said:
My rooting tools has the newest firmware, I just forgot to change the version number at the end, but it does say no bootloader.
I wish you luck on the accessibility apps. I never use them, so I don't specifically look for them to work.
Click to expand...
Click to collapse
Ok but all the same, I'm trying to avoid another 300mb DL if I can. As long as it is the same stuff then that's all I need to know.
Sent from my SM-G900V using Tapatalk

Version 2 is now available in the OP.

Universal BS ROM
i would like to know if this BS rom is able to be used on any S5 Carriers or would you consider it in the near future making this a universal rom for other carriers to please. my wife is a T-mobile person and she love the work that you have done here. and is asking me to ask this question. i thank you in advance for your reply.:good:

Forgive my lack of knowing how to make a build thread, since this is my first one, so I'm still learning lol.
Update: NO_BS_BOK3_ROM_DEODEXED_V2 is now available. The flashing process is the same. I encountered an intermittent bug with SuperSU beta with some apps. I downgraded to the latest stable SuperSU with the latest app. I updated all other apps and got rid of the bright/ugly Verizon boot animation. The music app has not force closed since I started using this version.[/QUOTE]
How did you remove the verizon boot animation? id rather not flash this again cause i just got my stuff all installed.

CVertigo1 said:
Version 2 is now available in the OP.
Click to expand...
Click to collapse
I Flashed it last night with @jkruse's No Bootloader V6 Tools and it worked just fine. I also, noticed that my Accessibility Settings works now and a couple other things were fixed as well. I did have a hard time Restoring Poweramp Music Player - I had to reinstall from Play Store but otherwise seems to be working great!
Sent from my SM-G900V using Tapatalk

Rooted lollipop vs marshmallow

What's up guys so me personally I haven't updated to Android m because lack of root but those of you who had lollipop rooted who went to marshmallow
What is your opinion

well i just did a tot recovery cause i had the "lgsetupwizard" crash issue when i did a factory reset on my device. so i have decided to go for the 6.0 update, don't get me wrong root is very valuable but without twrp i can't restore my device if a issue like that pops up again and i very seldom have access to a computer to be able to recover from problems like these. i went 4 days without my phone because of that bug :/ so i'll be sure to chime in with my thoughts about the 6.0 update once i play around with it a bit.

marshmallow is really good especially when it comes to battery life.

I have had alot of crashing issues, mostly when opening the camera app. also when restarting the phone will boot to the at&t screen twice...... EDIT:
AND SNAPCHAT WTF

NicHD4G said:
I have had alot of crashing issues, mostly when opening the camera app. also when restarting the phone will boot to the at&t screen twice...... EDIT:
AND SNAPCHAT WTF
Click to expand...
Click to collapse
So I haven't had any crashing issues on 6.0. The main impression I get with 6.0 isn't exactly better battery life, it's just better stand by time. Knock code now forces 6 taps vs 4 on lp. Permission management is meh. Personally 6.0 w/o root is trash and not worth the sacrifice.

Have had some stutters, a few initial force closes, but have subsided and now it feels more responsive, and battery seems a little more conserved
Sent from my LG-H810 using Tapatalk

Got my phone with marshmallow. But it's really nice. I'm really enjoying the phone so far. Just wish I could root marshmallow.

Marshmallow is horrible... I upgraded my phone and they gave me marshmallow, so I decided to downgrade to lollipop in order to obtain root. Without root a cellular device has no use for me... I didn't have root on my device for a few months and it killed me.. Until marshmallow obtain root, I don't see the use for it; that's just my opinion, but who am I anyways ?...
Sent from my LG-H810 using XDA-Developers mobile app

BTMoneyGang said:
[Snip]
Until marshmallow obtain root, I don't see the use for it; that's just my opinion, but who am I anyways ?...
Click to expand...
Click to collapse
Couldn't agree more!

It aint worth updating to MM until root could be possible. I updated, now regretting. Couldn't get back to LP because it will wipe all the data and I am too lazy to make a backup. Plus, I cannot boot into Recovery/Fastboot mode as well in MM. No idea if its me only or H810 with MM works like that.

Rooting PK1 and unlimited Tmobile Hotspot

I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !

I'm not on the PK1 firmware yet, but I just upgraded from PG1 to PIA.
As far as performance goes, I found this thread VERY helpful: http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
Maybe it will serve well for you as well. As far as rooting is concerned, not too sure from personal experience, but I heard the ENG boot works with the newest firmware and I'm guessing the modified SU should work for it too.
If you would like to try reverse engineering the files yourself, maybe these guides will help out:
http://arm.ninja/2016/03/04/reverse-engineering-samsung-s6-modem/
http://forum.xda-developers.com/android/software-hacking/how-to-reverse-engineer-kernel-t3137384
http://www.fortisfio.com/extract-android-rom-for-reverse-engineering/
In regards to removing bloatware, I prefer removing apps over services because you never know when you might need a service that you accidentally removed from a previous time. Also I've been going through many cases of trial & error with removing bloatware and a few times ended up messing up other apps in the process that would force crash, but with my current setup everything seems to be working well.
If you need help with removing bloatware, there are 3 apps that really helped me out.
https://play.google.com/store/apps/details?id=com.piriform.ccleaner <-- Surprisingly ccleaner is awesome for the android as well as the PC.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en <-- this is very useful as well
Another tool I found very great and you run this from your computer is Debloater: http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
Hope this helps. I'm trying to currently work on a way of creating custom odin flashable roms so I can optimize roms to the best of my ability and provide the community with more options as well. This is still a work in progress though. :S
EDIT:
Here is an output of my program list. It was too long for me to post directly in the message
adb shell pm list packages -f

thanks a lot!
I have read about ENG boot being an improvement as well, yet nobody is stating that it is stable as it is prior to root, just improved lag, performance and stability. I know in my experience, root, for the first time in 8 years of rooting is not worth the benefits. This is sad. Must be stable. (in addition -no roms, no nanroids, no samsung Sumsung Pay..etc..etc..) So I'm hopeful things will change soon, or will be forced away from Samsung. Tmobile privacy invasion issue, and bait-and-switch with their plans is even further less encouraging news. Imagine "unlimited" = less.... wow.

Well said, and I completely agree. I've been a BIG fan of previous Samsung models, but it seems with every new model that comes out there are less and less options for customizations. I'm currently in the process of trying to figure out how to repack tar.md5 files *properly*.
I've gotten close, but then it fails right at the very end. I'm still waiting for a response from someone hopefully with more knowledge than I, but I guess I have to be patient. Here was my thread: http://forum.xda-developers.com/tmobile-galaxy-s7/help/creating-flashable-odin-file-t3500139
Any way, I'd love to see more customization for the S7. I think it's a great phone and it has so much potential. I also love android and always felt it gave users more ability for customization as opposed to Apple. Like you, I just hate all the bloat ware and all the crap that comes on phones these days. Not only that but the markup price is ridicules. Having to pay $600+ for a phone that is "laggy" due to all the bloat on it is frustrating to say the least. This is why I'm trying to give the community more options or at least steer them in a direction to customize their devices easier. Currently despite all the various amounts of software that is provided through this community I feel like there aren't too many people that know how to properly use it.
Any who, good luck with your phone. Let us know if you figure anything out with it. Also, are there any significant advantages with the newest firmware over the PIA? I usually like to hold off from upgrading right away so that all the "kinks" get worked out first since it's difficult to downgrade afterwards.

xena499 said:
I' m hoping some experts can chime in.
I rooted PK1 about 10 days ago. Followed the Verizon S7 forum that had clear instructions, and used the v15 fixes + debloater.
I made sure the governors were set to interactive.
Despite all this, my phone was extra buggy and had lag, compared to stock. It seemed to get worse with time.
Then on day 6, after root, my phone started boot-looping on the tmobile logo and vibrated.
I un-rooted back to PIA, and tmobile still seems to be monitoring hotspot use, I thought was part of the PK1 OTA.
So, my questions are:
1) are those rooted on PK1 stable, like stock? OR is there still stability issues, beyond adjusting the governors to interactive?
2) what are people using to successfully circumvent tmobiles new hotspot throttle. ( .5kbs or pay $25 per month).
xtether module in xposed, or WiFi Tether Router (root). ??
what is working?
thanks in advance !
Click to expand...
Click to collapse
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.

Its bootlooping because you accepted the security update popup.

You know what, that happened to me once, I forgot. What I needed to do is reflash the ENG boot file then when I got back into the phone, remove and reinstall SU. After your phone restarts, go into playstore --> you apps --> and uncheck "Auto Update" for Super User.

KillerClaw321 said:
I was rooted stock and I used the fixes.zip , I stopped using the debloater because my phone had issues after.
Click to expand...
Click to collapse
thanks I tried going back to PIA and used fixes only, as the debloater might be the culprit !

I got it work now here:

@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.

m0d hipp¥ said:
@xena499 How were you able to downgrade the firmware? I tried downgrading through ODIN and it wouldn't let me.
Click to expand...
Click to collapse
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.

xena499 said:
yes. If your using the firmware in the verizon rooting forum, that stumped me too. It doesn't work.
Must be PIA (sept 27) or newer. I got the firmware from here The sammobile site.
and flashed fine with odin. Then used the established root method from the Verizon forum, using only the V15 fixes and NOT the bloatware remover.
Still testing the root stability (2 days driving). Seems ok, but not as stable as stock so far, but acceptable for me. Cool, no battery drain, but have noticed some lag/ and buggy things that I'm deciding whether or not was a settling that was not apparent on stock w/o root.
In addition, when I was given this loaner phone from the N7, the store migrated all my data and apps using the built in sammy prog. I was concerned how this would affect my phones performance in the long run. 3 "upgrades"/ swaps later of the same technique of migrating apps/settings/data between different phones took it toll. So the bootloop issue earlier forced me to unroot and start fresh, without a choice.... The proper PIA flashed on my device (no root of course) was rock-sold stable for the few days I tried it.
Click to expand...
Click to collapse
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?

m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
NO you need the Tmobile files, available in links here, or better from the sammobile.com site i mentioned above.
I would never flash verizon firmware on a tmobile-connected phone.
In addition, are you following the verison unroot method from the verizon s7 rooting guide? the verizon root references for me were just where the best info is for all S7 people, but the software links are to older firmware that didnt work...
Basically, you are using odin to flash ALL files at once (ie AP, BL, CP, CPC), then you are back at tmobile stock as per date of package used (PIA, PG1..etc).
Earlier versions before PIA do not flash, for me. I believe this is b/c i took an OTA security update that did something to prevent this. PIA worked fine for me, and is working not bad.
I'm satisfied for now, and I will wait for stable Nougat before anything else, and done with customizing and playing.
I hope this helps you

m0d hipp¥ said:
Thanks for the response. I have a SM-G930T and the firmware I am running currently is the " G930TUVU4APIA" stock. I just am using the ENG boot file and removed a bunch of apps myself (not using the v15 debloater or fix). Any way, the PIA firmware is still a little sluggish for me, and I was thinking of going back to "G930TUVU3APG1", but every time I try to flash it through ODIN I get an error. Something similar to "SW. REV CHECK FAIL : FUSED : 4, BINARY : 3".
And I didn't think that a verizon firmware would work on a tmboile phone? They're completely different hardware? Like GSM vs CDMA? Or am I missing something?
Click to expand...
Click to collapse
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....

Any luck?
sardor_x_z said:
Getting the same Error while flashing from PK1 to PG1... My phone getting hot after PK1 update. Please help.....
Click to expand...
Click to collapse
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.

silversusanoo said:
I need help with the G930TUVU4APK1 update as well. I can flash the TAR file, but I cannot run the root files.
Click to expand...
Click to collapse
I just rooted mine this morning. I played around with it a few times. What worked for me was run root.bat with my phone unplugged then plug it in. It took a few minutes for everything to go through. Hope this helps.
Sent from my SM-G935T using XDA-Developers Legacy app

Also would like to know bypass for limited tether greatly appreciated
Sent from my SM-G935T using XDA-Developers Legacy app

Question Occasionally crash to "waiting to flash full ramdump"

Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance

Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.

vinotux said:
Hi, sorry if this question was asked before by another user but my phone occasionally crashes to the waiting to flash full ramdump (or something of that sort) out of nowhere. After crashing, I could just force shut down the device using the volume keys and boot up normally again.
This only happens once or twice a week - my phone is unlocked and is sporting the latest kirasakura kernel.
Do you guys have any ideas on how to fix it?
Thanks in advance
Click to expand...
Click to collapse
Did you flash the DLKM module?

MarekPietrzak said:
Hello, I had same issue, it is caused by custom kernel, on .176 firmware both kernels listed on XDA are quite unstable. Just restore stock kernel by using payload dumper on firmware file and flashing boot.img, dtbo.img and vendor_boot.img using fastboot.
To keep root, patch boot.img with magisk before flashing.
Click to expand...
Click to collapse
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.

twistedumbrella said:
You probably shouldn't be starting rumors like that, especially without any legitimate proof. The reports are few and far between, but also addressed promptly. Neither of the kernels is "quite unstable" and the issue has happened on stock.
Click to expand...
Click to collapse
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message. When I restored stock kernel, this issue no longer persisted. I will for sure try again custom kernel, but in two weeks or longer, as ROG phone 5 is my primary device and I need to stay in contact. I will try to reproduce this issue and grab logs. Now I can share my observation, that those crashes occurred when device was idle, and usually on charger.

JazonX said:
Did you flash the DLKM module?
Click to expand...
Click to collapse
Thanks for your response, do I need to? I flashed using FKM and not TWRP

vinotux said:
Thanks for your response, do I need to? I flashed using FKM and not TWRP
Click to expand...
Click to collapse
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
MarekPietrzak said:
I don't intend to insult anyone, I just shared my personal experience, on previous firmware version both kernels worked fine and stable, but on .176 I had constant crashes with "waiting for flashing full ramdump" message.
Click to expand...
Click to collapse
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.

twistedumbrella said:
You honestly shouldn't need it at all anymore. I believe AnyKernel took the lead and fixed the issue, but it was only TWRP that needed it.
No worries. I was only making sure it was clear this was a recent issue and not an ongoing problem. Kirisakura spans a lot of devices and got the reports much later, so a slight delay in the fix should be expected.
Click to expand...
Click to collapse
Great, I'll just reevaluate when the new update rolls out, thank you .

vinotux said:
Great, I'll just reevaluate when the new update rolls out, thank you .
Click to expand...
Click to collapse
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.

twistedumbrella said:
Make sure to perform a backup of anything important, even if you are staying with stock. It appears the issue may go beyond something as simple as installing a custom kernel, assuming the issues reported on both are related.
Finding the common denominator, as they say, might find the root cause, but that is a pretty big task. It would also require more than one report and I only have the one.
Click to expand...
Click to collapse
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .

vinotux said:
Actually I flashed your kernel and it's been smooth sailing since then. I'm a little too busy to diagnose the root cause of the problem .
Click to expand...
Click to collapse
Fair enough. It shouldn't be on you to do it anyway. With any luck, i'll have debugging sorted out before the end of the weekend with proper instructions to avoid all the guesswork.
Asus Proprietary Logs
In trying to debug kernels, I realized that Asus has rerouted the location of some of the more important logs to make them "easily" accessible. Disclaimer: This is not a complete list of every file included, but lists the more "useful"...
forum.xda-developers.com

An error happens, the kernel logs the issue, the device reboots. This is how things are supposed to work. When disabling debugging, an error happens and the device reboots. The logging step is skipped, but life continues.
The problem is when debugging is partially disabled, but still attempting to write. This is basically why there is a "waiting for ramdump" message. It is waiting for the logging to complete to proceed to the next step.
Asus Power Debug: guard debugging so it can be disabled · freak07/[email protected]
Contribute to freak07/Kirisakura_ANAKIN_ROG5 development by creating an account on GitHub.
github.com
This commit set the stage for a future break, which happened in the .176 update when printk_buffer_rebase replaced get_last_shutdown_log.

Hi, just a quick update.
I had been experiencing major issues and the waiting to flash full ramdump debacle had gotten extremely frightening. The phone wouldn't recognize the IMEI of the device, wifi wouldn't work, etc. The error happened multiple times a day. I took it to ASUS and they basically told me to f off due to my phone being unlocked.
As a last resort, I flashed the .151 RAW firmware and I swear all of the problems vanished. If I was a betting man, I'd say that the .176 update caused all of the problems since I've used the device for a week now without any problems thus far.
Major thanks to @twistedumbrella and others for replying to this thread.

I don't doubt you are right about that. 188 improves things a bit, but they definitely broke something significant in 176. I have never crashed as much as on that build.