Database Info

[N900W8] Safely upgrade to Kit Kat without blocking flash back to 4.3 and retain 0x0

This is reserved for W8 only! If you have any other model, this will not work​
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3, it allows you to retain knox 0x0 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock. I already had knox 0x1 but i was alble to keep his at 0x0.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. It seems as the MD5 from all modems for all canadian carriers match exactly, so the model for rogers also applies to Bell and Telus
If you are coming from a non-canadian W8, you can extract your modem directly from stock firmware. Here is how:
This is just an example on how to extract a modem from a stock firmware:
Use winrar to:
1- extract firmware downloaded on sammobile.com or other (please use latest firmware), should output an MD5 file.
2- Rename that file from xxxxxxxxxxxxxxx.tar.md5 to xxxxxxxxxxxxxxxxx.tar
3- extract .tar firmware and locate modem.bin file
4- compress the modem.bin, it should give you a modem.zip
5- rename that modem.zip to modem.tar
6- You not have your flashable odin modem
Click to expand...
Click to collapse
Upgrading to Kit Kat and downgrading back to 4.3 does not trip knox, and rooting using my instructions either. Be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Download all the files, PIT, BL, AP. CP and CSC, the flash via ODIN 3.09. Then flash CF-Root and CWM if you wish. I did not check re-partition in ODIN, it worked for both of my Notes, most users didn't check it either, but a small few said the flash failed until they checked re-partition, either way, it should not brick your device.
Here are the links to the files:
PIT: http://pc.cd/K7H (MD5: e2dba603c963443660b369e04b07d574)
BL: http://pc.cd/gXH (MD5: 1bce2f5a137901e2fb206379d3e7ae11)
AP: http://pc.cd/7kH (MD5: 08443eb20702a975fc0be85f7e9c439d)
CSC (this one is for Canada only, if you have any other carrier please download yours): http://www.mediafire.com/download/xn11kh614eag7ir/Canadian+Multi+CSC.tar
(MD5: beae61ca1628b303657c40e14cac3fb6)
CP: http://www.mediafire.com/download/1oias85eoz8ykuh/Rogers+Modem+(CP).tar (MD5: 45522799eb027108fa1c493cbd83abf5)
ODIN: http://uploaded.net/file/hwtdrpll
CF-Root: http://download.chainfire.eu/352/CF-Root1/CF-Auto-Root-hlte-hltexx-smn9005.zip?retrieve_file=1 Don't use included ODIN in CF-Root, use 3.09 and flash via AP
CWM: http://d-h.st/gb3 (MD5: 31e4a86b58837ba87bfa1bf2073371db)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enjoy!
Thanks to Oogar for a more complete version of this process. This method does break WiFi and NFC so head over to his thread for the patch and a proper thanks

I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.

radicalisto said:
I can confirm after testing this a few times on the N9005 that it is only working on the N900w8.
Click to expand...
Click to collapse
That's too bad, but at least there are other ways for you guys!

There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow

radicalisto said:
There will be a way around it I think, especially as the w8 can do it. Shows it's possible somehow
Click to expand...
Click to collapse
is there any official 9005 firmware? I saw today that besides poland, russia also got the firmware which is exynos based, also deployment in eastern europe is under way, can't we apply this method to the 9005?

Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.

radicalisto said:
Only the .pl firmware currently, status on sammobile shows AFG (Afghanistan) region is pending apparently, so I expect a wide roll out any time soon.
Click to expand...
Click to collapse
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible

polish_pat said:
Whats different from the other other upgrade threads? This one doesn't block you from going back to 4.3 and it's safe.
Just tried this, worked perfectly. I came from X-Note 7.0 and did this on my friends Note 3 and he was on stock.
As of now, this has only been tested on W8 model as it takes the files from the Telcel firmware (mexico). You can use this method on any W8 model, the only thing you will have to change is substitute my modem (CP) by the modem from the latest 4.3 firmware of your carrier. You can take the official tar file and extract the modem.bin and re-zip it back to a tar file and use that.
This does not trip knox, be sure to turn off reactivation lock before flashing this. This method gives you an easy way to official 4.4.2, once you're there, you can flash any 4.4 rom.
Also, and this is an important factor for a lot of people, this doesn't block you from going back to 4.3. If ever you want to go back to Jelly Bean 4.3, just flash back to it via ODIN
Enjoy!
Click to expand...
Click to collapse
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk

Canadoc said:
Rogers user here. Stock. To clarify.
Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?
Will this reset my phone?or will my data and apps still be intact?
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
I hope you,re kidding for this "Can I flash these files and well be in 4.4.2? Without tripping Knox? And can go back to 4.3?" If you were not able to confirm this information while reading the OP, i'm not sure anything else but a drawing will help you. No offence
And as for your last question, yes, your phone will be wiped clean

Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk

Canadoc said:
Well I was under impression that flagging would upgrade the bootloader from which you couldn't go back.
Also wanted to be sure the included files were good for Rogers without me needing to separately including my own modem
Sent from my SM-N900W8 using Tapatalk
Click to expand...
Click to collapse
Yes, you're good to go! Enjoy
EDIT: also for anybody wondering, i was able to revert back to 4.3, i actually screwed up the rooting process, i used the ODIN included in zip from chainfires site instead of ODIN 3.09 and it gave me bootloop, so i tried to revert back to 4.3 using ODIN 3.09 and it worked. I'm going back to kitkat now

Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk

Canadoc said:
Do you cause a wipe? Cause I am not ripped so have no backup. Unless you know how to root and preserve knox
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
I'm not sure i understand what you want, i dont know what causing wipe or being ripped means unless you're talking about muscular mass, but i can tell you there is no way of doing this process, or any other and not wiping the device.

polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
I tried, but it just bootlooped for me. Was slightly afraid to force the BL incase I hard bricked it. However I may try again today at some point.

Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk

Canadoc said:
Normally flashing am update leaves your data intact. All I am asking is whether fleshing this will effectively factory reset my phone.
If so,,if I root before and don't trip knox, will I be able to flash this with mobile Odin and preserve root with tripping knox.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
This wipes your phone, call ir how you want, factory reset, format, restore, your data, root and everything else is GONE

polish_pat said:
in that case, can we apply this method and substitute the mexican files for the polish ones? It seems technically possible
Click to expand...
Click to collapse
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:

And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app

radicalisto said:
OK so... I just done this again and whatever I done this time around must have differed from last time Because I just Hard Bricked big style :silly: - My advice is no one try this on N9005 -- Now for the fun of restoring life to my device or playing the dopey card with my retailer! :good:
Click to expand...
Click to collapse
radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How did you unbrick a hard brick?
The SDcard image method?
I was under the impression that that one doesn't work on the N9005

radicalisto said:
And fixed. no defeating me!!
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I doubt you were hard bricked if you got out of it that easily. There are two experiences devs that hard bricked their phone, by hard brick, i mean no power or screen whatsoever, no download mode or recovery, NOTHING. They tried a few methods (micro SD and motherboard shortcut method) and both ended up servicing their phone by samsung.

How to restore warranty at sammy custom roms 4.3, 4.4.2, updated added ZSUFNJ2

First a big thanks to anyone who is cooking roms writing apps scripts etc here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom.
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such as everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use them or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
4.4.2 XXUFNG4.rar - 27.4 MB
4.4.2 XXUFNG3.rar - 15.0 MB
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB
4.4.2 XXUFNI4.rar - 15.0 MB
4.4.2 ZSUFNJ2.rar - 15.6 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with any custom rom (sammy base)
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]

Great stuff
vagsvag said:
First a big thanks to anyone who is cooking roms here and to user faria for the param.bin file.
Now the point, i found a solution to restore warranty at custom roms and i like to share with you.
This checked and working at any 4.3, 4.4 sammy rom (only at latest 4.4.2 XXUFNG4 i haven't test it)
Now what u need
1) mj5 bootloader
2) a rom compatible with mobile odin
3) mobile odin (i am using pro but i think is not necessary such us everoot is not necessary, don't forget if u don't use pro u have to download with app and the proper mobile odin kernel from chainfire's post)
4) triangle away
5) the files attached at end
6) stock kernel and recovery ( u can extract them from same version original rom, attention don't use other rom with other version stock kernel because u will have not wifi)
Ok now the procedure install and open mobile odin
Put at the place is saying param the param.bin file
Put at the place is saying kernel the stock kernel
check to wipe the dalvik cache (is not necessary but do it)
Flash and reboot
Check root, is ok 99% but if is not ok flash with your custom recovery supersuupdate
and after reboot check again root
If ok open again mobile odin and
put at the place is saying recovery stock recovery and flash it
After reboot install triangle away follow dev instuctions and reset the counter.
Thats all after reboot shut down your phone enter download mode and check your warranty.
Now i am attaching the param.bin file (u have to extract with winrar)
and some ready packets (kernel, recovery, param.bin) for some 4.4.2 versions, u can use it or use your own with param.bin file).
The srvr is paid but u can download as free user too (is not necessary to pay)
Thanks for reading and again to user faria for the param.bin file.
Files:
4.4.2 XXUFND3.rar - 15.1 MB
4.4.2 XXUFNE1.rar - 15.1 MB
4.4.2 XXUFNE2.rar - 15.2 MB
param.rar - 877 KB
Click to expand...
Click to collapse
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.

xbean said:
Great stuff. :good:
Waiting for 4.4.2 XXUFNG4 version.
Click to expand...
Click to collapse
Thank you, u can try it with XXUFNG4 too 99,99% will work extract kernel and recovery from original rom and use and the param.bin file with the posted procedure.
It is the same param.bin file everywhere. You can use this procedure at 4.3 too.

1rst post updated
Ok guys i checked at 4.4.2 XXUFNG4 and working
I am attaching kernel recovery and param.bin (by mistake i uploaded and the modem ignore it)
Link:
4.4.2 XXUFNG4.rar - 27.4 MB
And some new important info.
I tried to a rom not compatible with mobile odin (the mobile odin didn't restart to flash the kernel etc)
I rebooted at once manual with 4way reboot to recovery without closing the app and mobile odin worked made the flash.
After reboot i tried to see if my custom recovery was ok and was everything ok.
After i flashed stock recovery and made the same didn't restart,i restarted again with 4way reboot at recovery and made the flash safe.
And know the good one, it did the same with triangle away, i checked reset counter and didn't restart, i restarted at recovery at once with 4way reboot and worked.
Custom Binary Download No, official, official, warranty bit 0 with DEEP IMPACT ROM v2.3
This is a personal experience which i am sharing with u, i am not a developer or something other and i am not responsible if something goes bad.
Use it with your own responsibility.

hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u

Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.

JGKUMAR1976 said:
hi dev,
my note2 has xxufng4 bootloader,
i am noob for this work pls give with screenshots for safe side
thank u
Click to expand...
Click to collapse
tonylee000 said:
Is this a method to reset the warranty bit from 1x1 to 0x1?
My warranty bit is 1x1 since I flashed the mk9 bootloader and then a custom recovery. I've since updated the bootloader to ND3.
Click to expand...
Click to collapse
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no

vagsvag said:
@JGKUMAR1976 Sorry this is working only with mj5 bootloader
@tonylee000 Sorry i don't know a way to change warranty bit, this guide is resetting Custom Binary Download from any number to no
Click to expand...
Click to collapse
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?

tonylee000 said:
Ok cool. That's what I suspected. I don't see the point in the risk involved? If you've not flashed a bootloader newer than mj5 then its a simple case of flashing a stock rom from sammobile, root, triangle away, unroot. Job done. Then your phone is in a condition where it can be returned for repairs under warranty. If you return it with a custom rom installed then it's gonna be obvious the warranty been violated or is there something I'm missing here?
Ifyour not returning the phone to use warranty then you don't need to bother?
Click to expand...
Click to collapse
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2

vagsvag said:
You missed a point, the point is that most of us have phones with faulty emmc chip etc and many of our phone die suddenly, how do you flash your 9 months phone when is totally dead and goes only in download mode? Impossible, the next thing is to sent it 4 repair to change motherboard. The first thing they look at service is your binary count, if is ok your repair is free if is not 180 euro from your pocket goes away. I hope you understand the meaning of all this now.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate

tonylee000 said:
I wasn't being funny with you was wondering what the end game was. I wouldn't worry too much about the Emmc problem. If your phone is only 9 months old you should be fine. Early note 2s had the dodgy chip or 'insane' chip. My note 2 is one of those. There are apps you can get off the play store to tell you if you have an insane chip or a safe one. If the service centre can see download mode and see the binary counter is 0 then wouldnt they be able to see the warranty bit too? Unfortunately my warranty bit is now set to 1 so my warranty is probably not valid. I've had mine for 22 months now so I only have 2 months left on the warranty anyway so its not really a big problems for me now. As i recall the 'insane' emmc problems occurred because of a kernel issue in android 4.1.1 that burnt the chip out which was fixed in the 412 uodate
Click to expand...
Click to collapse
The warranty bit at mj5 bootloader is cosmetic 1000 flashes to do 0 will stay. Mine is 18 months old.
The fix they made is dirty fix and not really fix also the kernel hadn't any problem at 4.1.1 the problem was the chip and the fix they made was to setup the newer kernels to don't write at certain blocks which had the problem..If you search little about this you will see and "safe" emmc chips 1301 etc have also sds symptom.
The secret with these faulty chips is i believe to don't fill all the internal memory, and also if you have warranty to be active.

First post updated added support for XXUFNG3
4.4.2 XXUFNG3.rar - 15.0 MB

First post updated added XXUFNH2, XXUFNI1
4.4.2 XXUFNH2.rar - 15.0 MB
4.4.2 XXUFNI1.rar - 15.0 MB

Does this still work??
Very Curious!! :crying:

Bunny2rock said:
Does this still work??
Very Curious!! :crying:
Click to expand...
Click to collapse
Working like a charm.
Sent from my GT-N7100 using Tapatalk 2

Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
I too wanted to know same...

teddyteddy92 said:
Do I understand it right that with this method you can reset knox_warranty_void to 0?
Everyone is saying that it is not possible! That would be very nice
Click to expand...
Click to collapse
mietens said:
I too wanted to know same...
Click to expand...
Click to collapse
No guys this method reseting the flash counter (custom binary download from any number to no even if you have custom sammy based rom installed) not the knox warranty void and working with mj5 bootloader and older. At mj5 bootloader the knox warranty is cosmetic, 300 flashes to do 0 will stay. If you have installed newer than mj5 bootloader don't try it you'll loose your time.
Sent from my GT-N7100 using Tapatalk 2

First post updated added support for XXUFNI4
4.4.2 XXUFNI4.rar - 15.0 MB

First post updated added support for ZSUFNJ2
4.4.2 ZSUFNJ2.rar - 15.6 MB

New Samsung user, where do I start?

Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313

misfit0313 said:
Hello everyone, from my new Galaxy S6 Edge on Sprint. I've been with Sprint for 15 years and have been on Android since the HTC Hero. Every time a HTC fagship device on Sprint came out, it found its way into my pocket. I finally decided to jump ship from HTC and give Samsung a shot.
With the Samsung S6 Edge being my first Sammy device, there seems to be a lot I need to learn. Are there any tips or tricks that I should know?
I'm on a cross country drive and picked up the phone in Yakima WA last night. It will be several days before I have access to a PC, so when my trip ends in Wisconsin. I want to have everything researched on how to root and install TWRP.
First of all is this KNOX thing something I should be concerned for? What is the go-to method for root? Best Buy ran the BOI1 update on me yesterday. Is there a one click root available? Anything special needed to know for installing TWRP?
Thanks, misfit0313
Click to expand...
Click to collapse
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.

Soooperstar said:
First you're on the wrong thread. You should be in the Q&A section. First you may need to install the Samsung drivers to your computer. Download the preferred Odin 3.10.6 flashing tool. Go to your phone settings/build number, and tap 10 times until you see developer options enabled. Next go to settings/developer options, scroll down to Oem unlocking and turn it on. Next, to root you will need to use the odin tool to install the custom rooted kernel. Once that's complete, you can install TWRP. I'll include my link to twrp and kernel. Remember to Odin kernel first, then twrp. I don't think I forgot anything.
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=3102034
Edit:
Knox will be tripped rooting your phone. Will not be able to use Samsung pay, voids your Samsung warranty so you cant send back to Samsung, but does not void your carrier warranty, you can take it to them. Nothing else to worry about knox, doesn't affect anything.
Click to expand...
Click to collapse
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???

JediMindTrixx said:
Hey, I have a question... If he's on OI1 can he root and flash TWRP or should he Odin to OH1 then root and flash TWRP and then rom???
Click to expand...
Click to collapse
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G925P using Tapatalk

Soooperstar said:
No! He should do the normal root process. According to the OI1 update you can't go back. The rom works on OI1 according to reports View attachment 3492662
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That's right forgot about not being able to go back. Thanks! :good:

Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Yea I had the OG EVO back in the day. I know all about it. Samsung is much simpler when it comes to rooting

misfit0313 said:
Thanks Soooperstar... There's a reason why you shouldn't app and drive at the same time, you accidentally post in the wrong thread.
I've rooted, installed recovery, and S-off'ed every single HTC that I owned, the talk about Odin and KNOX threw me off a bit.
Click to expand...
Click to collapse
Odin is like RUU and Knox is Sammy's security...
Sent from my SM-G925P using XDA Free mobile app

This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001

misfit0313 said:
This looks like the correct kernel to flash to obtain root? http://forum.xda-developers.com/showthread.php?t=3166293
[KERNEL][925P/R4] UniKernel v8-0001
Click to expand...
Click to collapse
Correct.... Be sure to get the 925p

Thank you again. I'm rooted and have TWRP installed. A message popped up afterwards ”unauthorized actions have been detected galaxy s6". It was taken care of by freezing "SecurityLogAgent" with TiBu.

SM-G930T Root Doesn't Void Warranty

The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
This root works on all Marshmallow versions on Android on the T-Mobile S7
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

method
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?

dantehalo said:
Can you provide us a link to the method that you used to root the device. Also will you make a video tutorial for rooting the sm-g930t?
Click to expand...
Click to collapse
Yes I am planning to make a video tutorial.
Also I used the method provided here (this is Max Lee's website)
And for now here is great video tutorial (also created by Max Lee) The Video

So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.

revulv said:
So, this works? I'm reading a lot of comments on the page you linked saying that users are having bootloop issues and issues across the board... Nothing I read in the comments section suggested ANYONE got this to work flawlessly. Are you on the T-Mobile variant of the S7? If so, can you post a video of your phone, with clear root and explain in depth your step by step procedure? I literally just got this phone and don't want to **** up a phone I'm paying on.
Thanks a bunch! All the files are downloaded and ready to go on my PC. Just waiting to confirm this will work.
Click to expand...
Click to collapse
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.

Month later
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
KillerClaw321 said:
I apologize for replying so late ... Ive been busy. But this does work 100%, only a backup is required(before root because root will most likely put you in a bootloop and you have to factory reset after)... Hopefully my video will be out before July 30. But, before you root I also want you to be aware that the root uses an eng kernal which is not meant for daily use and causes lag, but you can optimize the phone to work as it did when it was stock.
Click to expand...
Click to collapse

djdubyah said:
Hi KillerClaw,
So it's been a month since your last post. Is this still preferred root for this device? My device encrypted storage upon setup wizard, don't know if i hit something or it did on own. Should I unencrypt before attempting root?
Thank you!
Click to expand...
Click to collapse
It is the only root method so far. It is not required but you can unencrypt before rooting. Rooting while already encrypted won't cause any harm since /data is encrypted not /system . But I still recommend unencrypting so you don't run into any issues.

Does this work for the latest November 1st update APK1?

Hello, I too would like to know if this is still the current root method and if there have been any changes?

GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.

i cant root my sm9307
KillerClaw321 said:
The latest root method for the Samsung Galaxy S7/S7E (AT&T/T-Mobile/Verizon/Sprint)
Does not void warranty and also does not trip the KNOX counter.
In order to remove root (un-root) you can flash the original firmware in Odin.
Also to answer any further questions the root does work on the latest T-Mobile update for the S7
(G930TUVU3APG1).
Click to expand...
Click to collapse
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me

seattlestexan said:
GeorgeNYer and kimber1982: The short answer is "no".
I did try this on my phone, and it acted like it worked (I could get the unlocked padlock with "custom") but I could never actually grant anything root access. That was when it was usable. The first round didn't get stuck in a bootloop. After I figured out that I didn't have root, I wiped the phone and started again, and again didn't get a boot loop, but did a factory reset anyway. After that point, it was too laggy to even try to use. I fought with it for a couple of hours trying to figure out a work around, but got fed up and DLed the APK1 stock firmware from Sammobile, and Odin'd the phone back to stock.
This is the first time I've used an non hacked phone since my iPhone 3G way back when. It feels really weird.
Click to expand...
Click to collapse
Did the attempt trip your Knox counter?

GeorgeNYer said:
Did the attempt trip your Knox counter?
Click to expand...
Click to collapse
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.

seattlestexan said:
No, no Knox flags. Technically the engineer boot is official, even if done in a not so official way. Once I flashed back to stock APK1, it looks like it did right out of the box.
Sadly enough.
Click to expand...
Click to collapse
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
---------- Post added at 09:55 PM ---------- Previous post was at 09:52 PM ----------
GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
I would try it myself but I'd hate to start over from scratch, I just wanna know if you tried all that is in the video, if not then I would try
Sent from my SM-G930T using Tapatalk

GeorgeNYer said:
Did you try everything in the video though?
https://youtu.be/GNInTlCpv8E
Sent from my SM-G930T using Tapatalk
Click to expand...
Click to collapse
What I listed is what I was able to do. I'm not certain it ever had root access. When it showed "custom" at boot, I couldn't grant anything root access. When it acted more laggy, like was described, the lag was so bad, it wasn't usable. Mind you, these instructions were written prior to the APK1 firmware that was on my G930T from new.

jveewee said:
i cant find any evidence that its even possible to root sm930t if there is somebody who can let me in on this big secret please indulge me
Click to expand...
Click to collapse
It's smg930t, just search smg930t root max lee

I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.

troby86 said:
I can confirm that this method does indeed work. You need to be careful and follow the instructions, but it will root your device. You may notice lag after rooting. Just install a kernel tool and set it to on-demand.
Click to expand...
Click to collapse
And Knox counter wasn't tripped??

GeorgeNYer said:
And Knox counter wasn't tripped??
Click to expand...
Click to collapse
Nope.

Can CF-Auto Root G930F really do no harm instead of G930W8

Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to Marshmallow 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?

isnull said:
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to lollipop 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
Click to expand...
Click to collapse
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F

MAX 404 said:
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
Click to expand...
Click to collapse
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?

isnull said:
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
Click to expand...
Click to collapse
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo

MAX 404 said:
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
Click to expand...
Click to collapse
Oh, thanks, neat little app. And yeah, exynos indeed:
screenshot

isnull said:
Oh, thanks, neat little app. And yeah, exynos indeed:
Click to expand...
Click to collapse
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3

MAX 404 said:
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
Click to expand...
Click to collapse
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought

isnull said:
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
Click to expand...
Click to collapse
Hi
1 That is right
2 I thought so...
3 Yes 35MB is about right ....is not the whole rom is only patching some modifying

MAX 404 said:
Yes 35MB is about right ....is not the whole rom is only patching some modifying
Click to expand...
Click to collapse
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to

isnull said:
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
Click to expand...
Click to collapse
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/

MAX 404 said:
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?

isnull said:
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
Click to expand...
Click to collapse
Up to you mate......mine is in unlock position

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
Oh cool, thanks. Think I'm ready now, will post a screenshot when I'm done, after re-reading a couple of things (Samsung Pay (which I don't use anyway), etc). You've been a huge help!

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

isnull said:
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
Click to expand...
Click to collapse
Yeah he deserve it !!!
Cool mate glad for you.

@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.

Just in case someone was going to reply to this here, I moved the "Software update" question here since it's a whole other story.

isnull said:
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Click to expand...
Click to collapse
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA

MAX 404 said:
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
Click to expand...
Click to collapse
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!

isnull said:
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
Click to expand...
Click to collapse
Hi mate
If your only modification to the system is just root and you do not notice any thing strange let it be do not flash dm verity zip , that error is caused by a "flag" set by the kernel as far as i know it should not be a problem , actually latest SuperSu should take care of it also