Database Develop

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire

muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix

thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon

Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option

thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.

Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?

thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.

delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question

thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.

@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.

Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find

Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.

muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.

Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.

muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?

For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.

bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

Downgrade from Lollipop to Kitkat without tripping knox SM-G900F

Hi all!!
After spending a huge amount of hours, searching the forum, I still have doubts...
Is it possible to downgrade from Lollipop, to kitkat, without tripping knox (warranty void) in the S5???
Some say, that flashing with Odin it's ok, others say that will go in a loopboot, others say that the bootloader is not compatible, and flashing a new rom will trip knox, others say that if the rom is official, will not trip knox...
What to believe??????
If there is a way to downgrade, safely and without tripping knox, please show me how, in a step-by-step process, I really appreciate it.
Here are the mobile phone data:
SM-G900F
Firmware: G900FXXU1BOD3
Thanks in advance!

Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
Hi Detection!
Thank you for your enlightement, but tell me, you flashed your device using Odin, right?
Thanks!

Yep, ODIN 3.10.6

*Detection* said:
Yep, ODIN 3.10.6
Click to expand...
Click to collapse
Ok, will give it a go!
Thanks Detection!

And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.

cichy20a said:
And how did it go?? Did You safely downgraded to KK?? I was thinking about it, got my S5 with pre-installed Lollipop but without root I can't block adds and stuff - it's rather annoying.
Click to expand...
Click to collapse
You can root lollipop, but it'll trip KNOX
CF Auto Root

Yeah i know that CF-AutoRoot works on lolly but I'd rather keep my warranty void Guess no new method on gaining root w/o tripping knox was introduced to S5 design If i recall S6 is rootable now without knox messed up but no go for S5

I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.

*Detection* said:
Downgrade away, I have the G900F, and flashing KK over LP works fine and does not trip KNOX
You only trip KNOX by flashing custom stuff, stock ROMs are signed by Samsung so do not trip KNOX
The only issue I had was having to flash KK twice, first flash worked but wouldn't boot, flashed again, booted first time
Click to expand...
Click to collapse
gluecks said:
I flashed my S5 a few months ago from 5.0 back to 4.4.2, and last week the same thing, but on my gf's Note3.
It's kind of easy and safe to do, if you do some research in advance:
- find exactly which ROM you need (the wrong one won't work and make ur phone temporarily unusable).
- download the official stock ROM
- KNOX won't trip if it's an official stock ROM.
- Boot the phone in recovery mode to wipe the cache partition and do a factory reset (after backing up the important data).
- Flash with Odin. There's many youtube tutorials on that one.
Enjoy.
If you didn't do a factory reset, wipe cache partitions etc you'll almost certainly get stuck in bootloop after flashing. In that boot up in recovery mode again, do those wipes and then restart.
Click to expand...
Click to collapse
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!

you need to disable the FOTA processes, but I'm not sure you can do that without root

Ok guys so let me get this straight - I only need proper KK image, provided by Samsung (their signature and so on) with my CSC (in my case Polish XEO)? Then connect my phone with PC, start ODIN (any particular version?) and what to choose, what check and what not? Sorry for this only had HTC before (and Sony and LG but those are wifes phones) and flashing on it was a bliss, especially when You had S-OFF.

dicemaster said:
Hi all!
Tell me something, after flashing KK, software update is allways trying to update to LP... is there a way of avoiding this, without root access?
Thanks in advance!
Click to expand...
Click to collapse
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really

*Detection* said:
Not stop, but you can delay it indefinitely by clearing the cache in recovery each time it has the update ready for you to install
Then boot back into droid, and hit the install button, which will fail because you just deleted the update in recovery
Rinse and repeat
You can root KK without tripping KNOX though, so no reason to not root it really
Click to expand...
Click to collapse
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!

dicemaster said:
Hi Detection!
I know we can root without tripping knox, but I am afraid of doing something wrong...
Can you tell me how to do it, in a safe way???
Thanks in advance!
Click to expand...
Click to collapse
Either make sure your KK ROM is a pre June 2014 build, if not, either flash with ODIN, or read up on how to downgrade only the Kernel to a pre June 2014 KK kernel, then use towelroot app to root it, and flash your original Kernel back
All the info you need is here on XDA, might take a bit of reading, but you should really learn as much as you can before blindly flashing things anyway

I read in another thread, someone said that if your S5 came with LP out of the box, you can't downgrade to even official samsung KK without tripping knox. I'm not sure how true is this or whether that person is just blowing smoke.

What is the purpose of the Root Genius application?

I know that one step in the rooting process is to use application like Root Genius.
Curious as I am, I would like to know what exactly this application is doing?
I would like to know whether whatever this application does, I can do by hand.

Depending what firmware you are right now on it may be possibly (definitely possible with any B6xx and higher rom) to flash the newest SuperSU.zip through a custom recovery. This way you gain root access. To be full rooted you may also delete the set_immutable on B6xx roms.
So, I'd definitely recommend to use the recovery-methode..

l3Nni said:
Depending what firmware you are right now on it may be possibly (definitely possible with any B6xx and higher rom) to flash the newest SuperSU.zip through a custom recovery. This way you gain root access. To be full rooted you may also delete the set_immutable on B6xx roms.
So, I'd definitely recommend to use the recovery-methode..
Click to expand...
Click to collapse
So, actually step for using Root genius, iRoot or Kingo android root is not necessary.
If I flash custom recovery, than supersu, I believe that I have to flash rooted boot partition as well.
Still I would like to know what these applications do.

root

hi,
I would love to root my sm-g800f.
Which guide should I follow?
Thanks

What ROM? You can try flashing the correct CF Auto Root for your phone model and Android version using Odin if it using the latest Lollipop.

lfom said:
What ROM? You can try flashing the correct CF Auto Root for your phone model and Android version using Odin if it using the latest Lollipop.
Click to expand...
Click to collapse
I have to look, so, for 'CF Auto Root' for G800FXXU1BPC3 Lollipop MR1 and
Odin.
Odin goes on PC and
CF Auto Root goes on device.
Am I right?

Both files go on PC, you used Odin to flash CF Auto Root into mobile. Seek for the files in the official page:
https://autoroot.chainfire.eu/
There are many videos on YouTube about it as most Samsung phones are rooted this way. Just make sure you use the correct file for your phone (G800F).
Backup everything you can first in case something goes wrong you may need to wipe mobile data and reflash stock ROM.
The other option is to use Odin to flash TWRP and then flash SuperSU zip from Chainfire. First, TWRP goes on PC then SuperSU Zip on phone, that you flash using TWRP. I am sure there are tutorials here about it, just pick TWRP for G800F, SuperSU is universal but some version may be needed according to your Android version. Can't help more because I have G800H and not rooted as Marshmallow was released for it and it has all I need. Good luck.

lfom said:
Both files go on PC, you used Odin to flash CF Auto Root into mobile. Seek for the files in the official page:
https://autoroot.chainfire.eu/
There are many videos on YouTube about it as most Samsung phones are rooted this way. Just make sure you use the correct file for your phone (G800F).
Backup everything you can first in case something goes wrong you may need to wipe mobile data and reflash stock ROM.
The other option is to use Odin to flash TWRP and then flash SuperSU zip from Chainfire. First, TWRP goes on PC then SuperSU Zip on phone, that you flash using TWRP. I am sure there are tutorials here about it, just pick TWRP for G800F, SuperSU is universal but some version may be needed according to your Android version. Can't help more because I have G800H and not rooted as Marshmallow was released for it and it has all I need. Good luck.
Click to expand...
Click to collapse
first way, I think, should be more simple.
How silly, I would root to change fonts on device.
And of course to free space, delete junkie and have control of my device.
Marshmallow is going to make me regret rooting?

You can change fonts using atock, no root needed. Also use Debloater to disable junk, no root needed either.
You can't use OTA to upgrade to MM when it arrives as it usually won't install or bootloops, so you will need to flash MM to go back to stock and upgrade then root again. Flashfire from Chainfire would be able to install OTAKU and keep root, but support to S5 mini is unkonwm, and no reports of success as far as I know.
Last but not least, flashing anything other than stock ROM through Odin will trip a Knox security counter and you'll lose warranty.

lfom said:
You can change fonts using atock, no root needed. Also use Debloater to disable junk, no root needed either.
You can't use OTA to upgrade to MM when it arrives as it usually won't install or bootloops, so you will need to flash MM to go back to stock and upgrade then root again. Flashfire from Chainfire would be able to install OTAKU and keep root, but support to S5 mini is unkonwm, and no reports of success as far as I know.
Click to expand...
Click to collapse
I don' t uderstand.
I'm stock. If I'll root I'll not be anymore stock.
If I don't root, will MM arrive OTA?
lfom said:
Last but not least, flashing anything other than stock ROM through Odin will trip a Knox security counter and you'll lose warranty.
Click to expand...
Click to collapse
I know

dezuha said:
I don' t uderstand.
I'm stock. If I'll root I'll not be anymore stock.
If I don't root, will MM arrive OTA?
Click to expand...
Click to collapse
Yes, when it's available for your phone model, as long as you're stock. Sorry, wasn't clear before.

lfom said:
Yes, when it's available for your phone model, as long as you're stock. Sorry, wasn't clear before.
Click to expand...
Click to collapse
you are joking!
You are very nice in answering to my questions.
''fonts using atock'', I think I can't.
I can only use payment monotype fonts

dezuha said:
you are joking!
You are very nice in answering to my questions.
''fonts using atock'', I think I can't.
I can only use payment monotype fonts
Click to expand...
Click to collapse
This is using stock MM on my G800H, I don't remember on Lollipop but I'm almost sure there was a similar option:

http://forum.xda-developers.com/galaxy-s5-mini/general/guide-easiest-method-root-g800h-t3340949
http://forum.xda-developers.com/galaxy-s5-mini/general/sm-g800f-rooting-guide-t3164859
I have found these two guides.
Which one do I have to follow?
lfom said:
This is using stock MM on my G800H, I don't remember on Lollipop but I'm almost sure there was a similar option:
Click to expand...
Click to collapse
I have those 5 ones.
But I would like other fonts.

TWRP/Root & Official Stock Firmware

Hi.
Is it possible to flash TWRP and root with magisk, and then flash relevant stock firmware updates from Samsung using Odin as and when they come?
If so, would flashing said firmwares remove root and TWRP, and/or wipe data? Requiring re flashing TWRP and rooting again after each update?
Basically I'd like to stay relatively stock, just with root and TWRP. But I want to be able to keep the phone up to date without having to use custom ROMs.
And yes, I know once TWRP or root are used Knox is tripped and there's no way to get it back or magically make the warranty valid again. I don't care about that.

beta546 said:
Hi.
Is it possible to flash TWRP and root with magisk, and then flash relevant stock firmware updates from Samsung using Odin as and when they come?
If so, would flashing said firmwares remove root and TWRP, and/or wipe data? Requiring re flashing TWRP and rooting again after each update?
Basically I'd like to stay relatively stock, just with root and TWRP. But I want to be able to keep the phone up to date without having to use custom ROMs.
And yes, I know once TWRP or root are used Knox is tripped and there's no way to get it back or magically make the warranty valid again. I don't care about that.
Click to expand...
Click to collapse
One month no answer, this forum is quite dead

dryspuri said:
One month no answer, this forum is quite dead
Click to expand...
Click to collapse
Yep, it's not great...

Instead of waiting, you could do a search on your own. This stuff is not from yesterday.

The answer is in s8, s8+, note8, s8, s9+ section. Basically someone has discussed it since Sammy introduced 7 days oem lockout, and ways to circumvent it... Those that know, don't feel like repeating endlessly, when time and search do the job.
The rest discuss wallpapers, screen protectors, cases, and justifications why root is no longer necessary (this from North American users, as if they could).
Sent from my phone