UPDATE: Hey guys! Easiest way to update to the new Nougat firmware & reroot with SuperSU currently is to install this debloated rom I just made. It does it all in one flash.
https://forum.xda-developers.com/showthread.php?p=72098300
----------
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADS:(click to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.
{
"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"
}
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
NOTE: If for whatever reason the firmware and TWRP won't flash back to back then just reboot into Download mode again and finish with flashing TWRP. It seems that will happen on occasion on more recent versions of Odin.
3) Once TWRP loads, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health "device has been compromised" or "can't be opened on a rooted device" errors.
1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If this helped you, then please consider hitting the "Thanks" or Donate button. Thank you!
bogarty said:
No doubt, there's already a ton of posts about this, but I decided to make this guide anyway for those who maybe prefer SuperSU over Magisk and just want to update Android and reroot quickly and easily. This method will get you rooted before you even boot up the Nougat firmware for the first time. Just be sure, of course, to BACKUP ALL YOUR DEVICE DATA BEFORE DOING THIS.
NOTE: If you use the Samsung Health app then be sure to read this post through to the end.
DOWNLOADSclick to open links)
Odin
Nougat stock firmware
TWRP
SuperSU Nougat Fix Zip(Do not use the official SuperSU zip. It will result in "stuck at creating image" error.)
no-verity-opt-encrypt(Attached below.)
1) Install & open Odin. Uncheck "Auto Reboot" in the Options tab. Then follow the instructions pictured below to flash the firmware package to your device.



2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.


1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".

4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

[/HIDE]
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.
2) Once it's finished recheck "Auto Reboot" and flash TWRP the same way. IMMEDIATELY AFTER IT REBOOTS and the screen goes blank, hold Volume Up, Home key and power buttons to boot into TWRP. (Otherwise it will launch Android setup.)
3) Once TWRP loads, you should do a full "advanced wipe" of everything(except the internal and usb storages) before moving forward. Afterwards, connect your device and drag and drop the "no-verity" and "supersu" files(from above) to the root of your sdcard.
4) Go to "Install" and select the "no-verity-opt-encrypt" file. Then click the "Add more Zips" button and add the SuperSU file as well and swipe to flash.
5) Reboot into Android and complete device setup.
You should now be rooted with Nougat and SuperSU!
BONUS:
Easy way to fix the Samsung Health"device has been compromised" or "can't be opened on a rooted device" errors.

1) Download an app from the Play Store called "BuildProp Editor".
2) Search for "ro.config.tima".
3) Click on it and change the "1" to a "O".
4) Reboot device.
If I've helped you, then please consider hitting the "Thanks" button. Thank you!

Click to expand...
Click to collapse
Nice guide!
Sent from my SM-N920T using XDA Labs
rmarinella said:
Nice guide!
Click to expand...
Click to collapse
Thank you! Holy OP quote though. Haha!
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I had same problem but it fixed....i am deodexed rooted with magisk clean installed and setup with mobile data thats all i did and works fine for now
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
odin
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.
skills2015 said:
when I try to connect my phone to odin its not reading the phone where it says added. anyone else experience this in this version of odin? I have usb debugging checked, plus oem checked. I have also tried different usb cables and other odin applications.......weird.
Click to expand...
Click to collapse
Try to download the drivers here:
http://org.downloadcenter.samsung.c...G_USB_Driver_for_Mobile_Phones_v1.5.45.00.exe
DrRootso said:
Any problems with Samsung Account after root? Mine works fine unrooted but won't stay logged in after. Curiosity and what not....
Click to expand...
Click to collapse
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.
bogarty said:
I have not experienced any issues myself. Everything should work fine on stock firmware. The only problem I found was with Samsung Health not working with root, but I provided the fix for that in the OP. Maybe try removing the account in Settings and adding it back manually.
Click to expand...
Click to collapse
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
JonathanRAZ said:
I dont think it will let him added it will say session expired even after entering it again....he might have to factory reset and setup again or setup via mobile data
Click to expand...
Click to collapse
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.
bogarty said:
Strange I haven't seen this issue. Is it a Magisk problem? I signed into Samsung Account during initial device setup and its been working fine.
Click to expand...
Click to collapse
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
JonathanRAZ said:
No is not magisk i have it installed and all is fine on this side.....it can be on setup the problem the first time i had i setup with wifi and after changing to mobile dta had session expired....i dont know if is that or not but since i have setup via mobile data it works fine no problems
Click to expand...
Click to collapse
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.
bogarty said:
Weren't you using that unrooted rom from the other thread? Maybe there was a problem there.
Click to expand...
Click to collapse
No i was stock rooted with magisk......then was on my own deodexed rom.....then now i am on that unrooted rom.....and later on will be on a new one i will make after installing windows 10
Sent from my T-Mobile Samsung Galaxy Note5 using XDA Labs
thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!
justin94 said:
thanks for this. sadly volte isnt working for me so ill be using the stock tweaked rom, hopefully it works. but using this root method. thanks again!
Click to expand...
Click to collapse
Still don't get how anyone could be having any issues with any Android features. If you're flashing the stock firmware, everything should work. VoLTE seems to be working fine for me.
bad flash probably. but this root method worked on that stock tweaked rom. everything is working.
Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Sent from my SM-N920T using Tapatalk
I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?
Maximus2102 said:
I followed the steps but it doesn't seem to be working well for me. I can flash the stock FW fine but when I try to flash TWRP odin doesn't go through the process. I shut down the phone and went back into download mode and that allowed me to flash TWRP. I booted immediately into TWRP and flashed the two files (no-verity & Nougat Root SU - no Kernel ) from the links provided. I performed the wipe as suggested before flashing the two files in TWRP. When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing. Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.
geeshiet said:
Anyone know the differences between magisk and supersu? Pros and cons for both.. I was thinking about doing the magisk root but I've always rooted with supersu.
Click to expand...
Click to collapse
I made this tutorial because I've always felt SuperSU to be more reliable personally. The last rom I had forced you to use Magisk and I didn't like it. Magisk just kind of seems like too bulky of a package for me. Too much extra stuff, going on and sometimes(a couple versions back) the package updates can be faulty and even cause device reboots. SuperSU, to me, just seems lighter and more reliable and concise.
Maximus2102 said:
when I try to flash TWRP odin doesn't go through the process.* I shut down the phone and went back into download mode and that allowed me to* flash TWRP.
Click to expand...
Click to collapse
Rebooting is fine, though there shouldn't be a problem flashing both in a row. It does take about 10-20 seconds or so sometimes before it will let you load the next one.
Maximus2102 said:
When I reboot the phone I'm greeted with the message Kernel not seandriod enforcing.* Is it because I'm using the wrong Root SU file?
Click to expand...
Click to collapse
The kernel not seandroid enforcing message has never been anything to worry about. It's just Samsung's of way of telling you that the kernel has been modified to allow for root. You shouldn't have that message though with SuperSU, as SuperSU uses a systemless root method. So if you're seeing that, then you've done something additional that's modified the kernel. What "Root SU file" did you mean? Flashing the SuperSU zip roots the device. No extra files are needed.
Maximus2102 said:
Nevermind. I was able to get passed it but I flashed Magisk instead. I'm up and running with Rooted Nougat.
Click to expand...
Click to collapse
You got rid of SuperSU because you saw "kernel not seandroid enforcing" message? Again that message is nothing to be concerned about. You'll see the same thing if you install a custom kernel, but again, if you were seeing that message during this process, then you did something wrong or did an extra step.
Related
I've had a tough Android learning curve. Before I mess up again I have a few questions. I intend to flash Scott's "Clean Rom 5.0" onto my VZW S3 and don't fully understand his instructions or flashing instructions in general and always get confused during recovery process.
I have EZ Unlocker, twrp and have downloaded Clean Rom 5.0 onto my phone and can navigate to it in GooManage and choose it.
On the installation of the ROM his page shows the following
{
"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"
}
I know that I need to unlock (I have EZ Unlocker). When I click unlock I DO NOT hear "that was easy" (yes, the volume was up) but it only visually shows an "unlocked" message.
Leaving the unlocker using the home button I then I navigate to my GooManage app and and according to the installation instructions I am supposed to reboot to recovery. Here is where I get tangled up and it's because I don't fully understand the process from here. When I reboot into recovery from GooManager it does just that and of course places me into recovery. This is the point where I almost bricked my phone last week. I do not want a repeat of that.
My options in recovery of course are:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
According Scott's guide I only do a data/factory reset within recovery. Do I leave recovery afterwards and twrp to flash the ROM?
drzcharlie said:
My options in recovery of course are:
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
According Scott's guide I only do a data/factory reset within recovery. Do I leave recovery afterwards and twrp to flash the ROM?
Click to expand...
Click to collapse
After reading your post you don't have a custom recovery installed. What you're seeing is the stock recovery. TWRP is an all touch interface with maybe six to eight options (or buttons). Few questions since you're new:
1) Did you root first? If so, what tool did you use?
2) For EZ Unlock, what version did you use? You should be using v1.2
3) Once rooted AND unlocked, follow this step. You need to open GooManager, press Menu, select "install openrecoveryscript" then it will provide two prompts to install TWRP 2.3
4) Open GooManager, select "Reboot Recovery"
5) Now you should be in TWRP, notice the difference? Select "Backup" and save this either to your internal or external sd card. This backup is also known as a "Nandroid."
6) Now I need you to backup your IMEI. Link:
http://forum.xda-developers.com/showthread.php?t=1852255
7) Now that you've backed up your IMEI and performed a Nandroid, it's time to flash CleanRom 5. Reboot into recovery, select "Wipe" then "Factory Reset," next "Wipe Dalvik," then go back to the main Recovery menu and select "install" to put CleanRom in your phone.
8) Done!
Edit: Added the link.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
After reading your post you don't have a custom recovery installed. What you're seeing is the stock recovery. TWRP is an all touch interface with maybe six to eight options (or buttons). Few questions since you're new:
1) Did you root first? If so, what tool did you use?
2) For EZ Unlock, what version did you use? You should be using v1.2
3) Once rooted AND unlocked, follow this step. You need to open GooManager, press Menu, select "install openrecoveryscript" then it will provide two prompts to install TWRP 2.3
4) Open GooManager, select "Reboot Recovery"
5) Now you should be in TWRP, notice the difference? Select "Backup" and save this either to your internal or external sd card. This backup is also known as a "Nandroid."
6) Now I need you to backup your IMEI. Link:
http://forum.xda-developers.com/showthread.php?t=1852255
Edit:
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
1. Yes, rooted first. The tool I used - http://forum.xda-developers.com/showthread.php?t=1875914
2. EZ Unlock Version - Version 1.4
3. As indicated I installed openrecoveryscript just now
4. Wow, yes I see the difference!
5. Back up completed
6. Reading the IMEI link now.
Should I download "terminal emulator" for the IMEI part?
drzcharlie said:
1. Yes, rooted first. The tool I used - http://forum.xda-developers.com/showthread.php?t=1875914
2. EZ Unlock Version - Version 1.4
3. As indicated I installed openrecoveryscript just now
4. Wow, yes I see the difference!
5. Back up completed
6. Reading the IMEI link now.
Click to expand...
Click to collapse
Awesome. I have doubts about EZ Unlock v1.4. [Edited] Use EZ Unlock v1.2, then select "Unlock" and you're all set. Download via Rootzwiki:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
I only recommend v1.2 since we had major issues awhile back with other versions of EZ Unlock.
Should I download "terminal emulator" for the IMEI part?
Click to expand...
Click to collapse
Edit: Yea, its available in the Play Store. You really only need to do the first two IMEI backup methods contained in the thread I provided.
SlimSnoopOS said:
Awesome. I have doubts about EZ Unlock v1.4. Could you reboot your phone and tell me if the Samsung boot logo flashes by super quick? You're properly unlocked if that boot logo flashes by fast. If it does not, uninstall your current version of EZ Unlock, download v1.2, then select "Unlock" and you're all set. Download via Rootzwiki:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
I'd like to know if v1.4 produces the quick Samsung boot logo just for my own piece of mind. I only recommend v1.2 since we had major issues awhile back with other versions of EZ Unlock.
Edit: Yea, its available in the Play Store. You really only need to do the first two IMEI backup methods contained in the thread I provided.
Click to expand...
Click to collapse
When I rebooted the phone showed "Samsung" really briefly then went into the animation screen and finished booting. Is this what you wanted to know?
drzcharlie said:
When I rebooted the phone showed "Samsung" really briefly then went into the animation screen and finished booting. Is this what you wanted to know?
Click to expand...
Click to collapse
Yea, as long as it flashes by quickly and does not linger then you are properly unlocked. If it was stock and locked, the Samsung boot logo will sit on the screen for a few seconds.
I edited step 7 of my previous post to reflect the following:
-While in TWRP, you will "Factory Reset" and "Wipe Dalvik." This Factory Reset will wipe cache and dalvik cache.
EDIT: Use EZ Unlock v1.2 please.
SlimSnoopOS said:
Yea, as long as it flashes by quickly and does not linger then you are properly unlocked. If it was stock and locked, the Samsung boot logo will sit on the screen for a few seconds.
I edited step 7 of my previous post to reflect the following:
-While in TWRP, you will "Factory Reset" and "Wipe Dalvik." This Factory Reset will wipe cache and dalvik cache.
Click to expand...
Click to collapse
Ok, I think I am unlocked properly then. It was just up for a very fleeting moment. I downloaded terminal emulator and did the commands "su" and "reboot nvbackup" the phone rebooted and I returned to android and dismissed Terminal Emulator.
So, I guess I am about to find out if I have a brick or not with my first flash eh? EDIT: I just went back to EZ Unlocker and wanted to recheck unlocked status. It showed the Device Status as "Unknown". To be sure I clicked on "Unlock" THREE different times to get the phone to show a Device Status of "Unlocked" I also still DID NOT get the "that was easy" audio message. Is this a problem? Should I find and install the 1.2 version?
drzcharlie said:
Ok, I think I am unlocked properly then. It was just up for a very fleeting moment. I downloaded terminal emulator and did the commands "su" and "reboot nvbackup" the phone rebooted and I returned to android and dismissed Terminal Emulator.
So, I guess I am about to find out if I have a brick or not with my first flash eh?
Click to expand...
Click to collapse
On second thought, I'm going to go with my gut and tell you to use EZ Unlock v1.2. I would much rather we get this right the first time. Just use v 1.2 and you will undoubtedly be unlocked.
Other than that, everything should be all set.
EDIT: I just went back to EZ Unlocker and wanted to recheck unlocked status. It showed the Device Status as "Unknown". To be sure I clicked on "Unlock" THREE different times to get the phone to show a Device Status of "Unlocked" I also still DID NOT get the "that was easy" audio message. Is this a problem? Should I find and install the 1.2 version?
Click to expand...
Click to collapse
Looks like we posted simultaneously. Yea, use EZ Unlock v1.2. I edited each of my posts so reflect this as well.
SlimSnoopOS said:
On second thought, I'm going to go with my gut and tell you to use EZ Unlock v1.2. I would much rather we get this right the first time. Just use v 1.2 and you will undoubtedly be unlocked.
Other than that, everything should be all set.
Looks like we posted simultaneously. Yea, use EZ Unlock v1.2. I edited each of my posts so reflect this as well.
Click to expand...
Click to collapse
Once downloaded which folder to I place it in?
drzcharlie said:
Once downloaded which folder to I place it in?
Click to expand...
Click to collapse
You actually just click on the apk to sideload it. No need to move it to another folder. So, go to Settings/Security/and make sure "Unknown Sources" is checked. Make sure you uninstalled your current EZ Unlock v1.4. Either using a file manager or the Touchwiz "Downloads" folder, select "EZ-Unlock12.apk" to install it. You should hear the audio "That was easy" now, I just tested it to double check.
SlimSnoopOS said:
You actually just click on the apk to sideload it. No need to move it to another folder. So, go to Settings/Security/and make sure "Unknown Sources" is checked. Make sure you uninstalled your current EZ Unlock v1.4. Either using a file manager or the Touchwiz "Downloads" folder, select "EZ-Unlock12.apk" to install it. You should hear the audio "That was easy" now, I just tested it to double check.
Click to expand...
Click to collapse
I'm having a bit of a problem locating the 1.2 apk. I went to rootzwiki but can't seem to find it doing a search. Still looking EDIT: No luck finding it. Seems 1.4 is the current and I found no earlier version. I have checked back into my version twice and the Device Status shows Unlocked at this time.
drzcharlie said:
I'm having a bit of a problem locating the 1.2 apk. I went to rootzwiki but can't seem to find it doing a search. Still looking
Click to expand...
Click to collapse
In my second response to you, I provided a link to the exact thread already bud:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
SlimSnoopOS said:
In my second response to you, I provided a link to the exact thread already bud:
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Click to expand...
Click to collapse
Dang...sorry about that. Thanks for being so patient with me. My bad.
drzcharlie said:
Dang...sorry about that. Thanks for being so patient with me. My bad.
Click to expand...
Click to collapse
Haha trust me, it's fine. I threw a lot of information at you at once so its actually my fault.
Once this unlocks you, you may need to perform step B from the Backup IMEI thread. Once this is done, you should now have a folder in this directory: /sdcard/synergyrom/backup
!
SlimSnoopOS said:
Haha trust me, it's fine. I threw a lot of information at you at once so its actually my fault.
Once this unlocks you, you may need to perform step B from the Backup IMEI thread. Once this is done, you should now have a folder in this directory: /sdcard/synergyrom/backup
Click to expand...
Click to collapse
Ok, we now have the audio "That was easy" phew! Going to step B from the Backup IMEI thread. EDIT: I downloaded and successfully installed the Synergy Backup HWKeys
drzcharlie said:
Ok, we now have the audio "That was easy" phew! Going to step B from the Backup IMEI thread.
Click to expand...
Click to collapse
How did it go? If that folder gets created once you flash what you need to flash, you can now flash CleanRom 5.
SlimSnoopOS said:
How did it go? If that folder gets created once you flash what you need to flash, you can now flash CleanRom 5.
Click to expand...
Click to collapse
I believe everything is installed properly. I navigated to the file on my internal SD card called "/sdcard/synergyrom/backup" and it is there. I will follow your guide now and try the flash. Fingers crossed.
drzcharlie said:
I believe everything is installed properly. I will follow your guide now and try the flash. Fingers crossed.
Click to expand...
Click to collapse
Great, just reboot into TWRP and Factory Reset/Wipe Dalvik then install CleanRom 5. You will see it change from TWRP to Aroma installer, don't be shocked because this is awesomeness at its finest.
SlimSnoopOS said:
Great, just reboot into TWRP and Factory Reset/Wipe Dalvik then install CleanRom 5. You will see it change from TWRP to Aroma installer, don't be shocked because this is awesomeness at its finest.
Click to expand...
Click to collapse
It's now installing. I will report after it's finished. EDIT: It installed properly and I am now doing a google restore and now it is finished and installed. I don't know how to thank you enough for all the help you provided and the patience you showed along the way. I am bookmarking this guide for future reference. You sir, ROCK!
Pleasure to help you out and get you on your way!
Sent from my SCH-I535 using xda app-developers app
S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
beaver2233 said:
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
dotpage said:
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
Click to expand...
Click to collapse
How did you get back to CM10.1?
AlAmeri said:
How did you get back to CM10.1?
Click to expand...
Click to collapse
Flash it using a custom recovery
Me Gusta!
Me Gusta said:
Flash it using a custom recovery
Me Gusta!
Click to expand...
Click to collapse
So flashing ROM without root is possible?
AlAmeri said:
So flashing ROM without root is possible?
Click to expand...
Click to collapse
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
fcknghst said:
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
Click to expand...
Click to collapse
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
AlAmeri said:
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
Click to expand...
Click to collapse
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
fcknghst said:
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
Click to expand...
Click to collapse
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
So you cant restore your backup, from before 4.3?
fcknghst said:
So you cant restore your backup, from before 4.3?
Click to expand...
Click to collapse
Exactly. I tried searching for stock firmware, couldn't find one. So I thought either I find a way to restore. Or flash an already rooted ROM. You see my dilemma.
{
"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"
}
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
dotpage said:
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
Click to expand...
Click to collapse
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
AlAmeri said:
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
Click to expand...
Click to collapse
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
fcknghst said:
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
Click to expand...
Click to collapse
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
If you find 4.2.2 vanilla(T-Mobile) let us know, I am looking for that ROM....
AlAmeri said:
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
Click to expand...
Click to collapse
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
dont know if this will work for you but here goes. i have a T999L (T-Mobile LTE S3) i have twrp installed on it and i have slimbean 4.3 official build installed on it, i had the same issue with getting 4.3 rooted but i got it figured out first make sure in the developer options you have superuser allowed by adb and apps.
( if you don't see developer options in your settings menu
go to :Settings>About Phone> click on your build number several times until you get a toast that says your almost a developer keep clicking until it says it has been enabled)
then you will use motoChopper to push the exploit to get the superuser.apk added to the system/apps folder once you do this it won't work as they have somehow allowed access for the expoit to push the .apk but not push the binary to the system/xbin folder.
now pull the SU binary out of the motoChopper folder on your computer and place in on your sdcard
boot into TWRP, mount the file system and copy it from your sdcard to the system/xbin folder and voila you are done, when you go to reboot your device from TWRP it will ask you if you want to fix the Superuser permissions just skip and reboot
( all rights thanks and so on go to the original developer djrbliss and i do not take any credit for his work, nor did i get permission to modify his work, i tried but got no response so i modded it for myself to use and i am now sharing, all i did was swap the Superuser.apk and SU binaries he used in his exploit.) @djrbliss if you would like this post removed just let me know and i will pull it!
not sure why the list showed up as 1 1 1 2 but i think you get the point
EDIT: 11/01/2015...This root method will work for OGD...OI6...OJ6... TRIED TESTED AND PROVEN ! ! !
WARNING: Once you USE THIS OI6 TAR OR take the OI6 OTA UPDATE . . . .
You will NOT be able to revert back down to OGD
EDIT: 11/01/2015...If you take OJ6 OTA Update, YOU CAN USE OI6 TAR FILE TO REVERT BACK TO OI6 / STOCK
With this TAR, you will be able to ODIN back to 100% FULL SPRINT STOCK. in the event you develop bootloops or just want to unroot
ROOTING will trip knox and tripping knox WILL kill Samsung pay FOREVER...even if you flash back the stock tar
I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOU PHONE. ... IT IS YOUR DECISION TO TAKE THE PLUNGE.
Anyone that tries this and gets bootloops and cannot recover here is a link to the OI6 stock tar file... flash in Odin AP slot from download mode you should recover very easily DOWNLOAD THE SPRINT N920P OI6 STOCK TARBALL HERE TO RECOVER AND/OR TO RETURN TO OI6 STOCK
WORD OF WARNING>>> AGAIN Once you take the update to OI6 or use the OI6 TAR (get OI6 HERE ) .. YOU CAN NOT GO BACK TO OGD.....
TO ROOT:
Download ODIN 3.10.7
Download FREEZA's BEASTMODE KERNEL HERE
Download TWRP-2.8.7.0-N920P.tar
Download BETA-SuperSU-v2.49.zip
PREP THE PHONE FIRST ...
go to settings>>>about device>>> scroll to bottom and build number 8 times
now press back button once and tap developer options...
make sure USB debugging is on AND OEM UNLOCK NEEDS TO BE ON ALSO .....
{
"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"
}
Place phone in ODIN / Download mode ( press and hold vol down+home+power for a few seconds...then release and press vol up)
plug the phone to the pc....Watch for ID:COM in top left corner to give an ID.......if none is given then check the data cable or try a different one.... NOTE: once you try a flash and "IF" it fails... you will need to disconnect and power off the phone ( to power off press and hold Vol down + power for 10 sec ) and go back into download mode again or you will get "Setup Connection" hangup error when re-trying to flash
Now Click the "AP" button and in the pop up window, migrate to the KERNEL and double click it. Wait for it to verify md5 checksum. If bad, re-download the file.
Now check in the OPTIONS TAB.... make sure ONLY Auto Reboot & F. Reset Time are checked...
uncheck Re-Partition ! ! !
Once these steps are followed, click start and wait till you see PASS in the ID:COM Field
After re-boot, follow same steps and flash TWRP
Then either install SuperSU in TWRP by going into recovery by powering off the phone then press and hold vol up+home+power until you see the TWRP splash .... or just install from the market( the market install "may" give update binaries issues... flash in TWRP )
I have a SPECIAL HANGOUTS thread for SPRINT NOTE 5 OWNERS.
I would like to add ALL of you to it.
PLEASE PM ME YOUR GMAIL EMAIL ADDRESS SO I CAN ADD YOU
So you have rooted, NOW WHAT? . . . You need to flash the best custom rom > > > >
Galaxy Note 5 OI6 & OGD Deodexed Rom
@tdunham has built the best deodexed rom.... CLICK HERE FOR HIS THREAD or CLICK this button
tdunham said:
Galaxy Note 5 OGD/OI6 Stock Deodexed Rom2
This build is based on the stock OGD & OI6 5.1.1 Lollipop builds.
This is a first release. Even though it has been tested, please report any issues.
Features:
- Rooted
- Busybox
- SQLite
- Hotspot enabled
- Knox Removed
- ItsOn Removed
Download Link ---> N920P_OGD.5.1.1.De-Odexed.Ver1.0.zip
Download Link ---> N920P_OI6.5.1.1.De-Odexed.Ver1.0.zip
Changelog:
OI6 Release
- OI6 brings some security enhancements and fixes nothing specific.
- Fixed access to hiddenment dialer codes
- stagefright vulnerability fully patched (for now)
- Beastmode v1.2 kernel already included.
Rom Installation
Preparing the stock rom
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
- Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
- Toggle on both USB debugging and OEM Unlock.
• Copy the downloaded rom.zip file to internal storage
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
Odin3_v3.10.6.zip
TWRP-2.8.7.1-Alpha_N920P.tar.md5
or
philz_touch_6.59.0-820876114.tar.md5
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
• Unplug & Reboot phone directly into Recovery Mode (press and hold Home + Power + Volume Up buttons)
• BACKUP YOUR CURRENT SETUP WITH TWRP
• Do a FULL wipe but do not reboot yet
A full wipe includes:
Dalvik Cache
System
Data
Cache
• Flash rom and reboot.
Going back to the Stock Rom
• Use the same Odin instructions to flash TWRP above but using the stock tar
Credits to my beta testers: @Chaz187 @fsunoles101 @JoeyDuran @GAPO @rlmiller @sml2004
Special Credits to: @tx_dbs_tx
For help with development, the csc & personal mode fixes.
Click to expand...
Click to collapse
to read about it.
.
.
.
.
.
.
.
reserved for later 1
reserved for later 2
reserved for later 3
nice bro, thanks. a lot of people have been waiting for this!
Is there by chance a flashable zip that doesn't affect the bootloader so you can go back to ogd if you want? I know in the past it has been done before, not sure what it takes to accomplish this. Thanks for all your hard work.
Thank you sooooo much, but this definitely should not be in the general section for sure. A mod needs to move this to its proper place, this is a lifesaver.
So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.
Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.
melendez214 said:
Can I flash twrp first and then flash the kernel zip? Because when I try to flash the kernel through Odin it gets stuck before it even starts.
Click to expand...
Click to collapse
Yes, that shouldn't be a problem
rlmiller said:
Yes, that shouldn't be a problem
Click to expand...
Click to collapse
Ok thank you
DarkManX4lf said:
So I got a replacement Note 5. I updated to OJ6 and then followed this tutorial to root. I managed to get root and installed twrp. However, try to flash certain zips in twrp the phone just reboots. This only happens with certain zip files like xposed installer and the volume mod zip. The interesting thing is these zips flashed fine on my old Note 5.
Anyone have any ideas?
Edit: Nevermind, I reflashed stock via odin and went through update and root again. NOw it seems like it's working.
Click to expand...
Click to collapse
Can u get xposed working with OJ6? Stock rom?
drewiskee said:
Can u get xposed working with OJ6? Stock rom?
Click to expand...
Click to collapse
Yeah it works with stock rooted.
DarkManX4lf said:
Yeah it works with stock rooted.
Click to expand...
Click to collapse
I tried and got reboots and had to flash stock rom from lower build.
using twrp recovery
I have the edge + .....can I revert back to oi6 as well? Sorry I'm new at all this! Lol thank you
So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!
wackydroid said:
So, I was a master at rooting/manipulating my phone, but as it was a Note 2 until yesterday, I'm a bit rusty.
My son and I both got new Note 5s yesterday (a 32G and a 64G) and they've got OJ6 on them. I'm not completely sure I understand the instructions in post 1 - do I have to take the phone back to OI6 to be able to root using this method? Is there no root exploit for OJ6?
If I do have to revert, could you post clearly how to do it, please? Once I get past that I should be okay...
I have all these things I want to get done on the new one (getting rid of all the Sprint apps, backing up my messages, moving some program data over, more...) but realized everything I know about manipulating a cell phone is in Root, so I have to do it...
Thanks, in advance, for the help!!!
Click to expand...
Click to collapse
Yes, you can root OJ6 the same exact way as all the current builds.
I'm sure you're familiar with Odin by now so just download the OI6 factory tar (there isn't one available for OJ6 so far, its only available as an OTA update) and have that handy should you wish or need to go back to stock.
Also, if you see the OGD tar, don't bother with that one, you wont be able to flash that factory tar anyway as it will fail checks in odin when it recognizes you're on a newer build.
Additionally:
Since you're going to trip knox anyway by flashing TWRP custom recovery, you might want to keep in mind about wiping your internal storage too if you're having any issues along the way. It probably doesn't apply quite yet for you at this point but you know how it collects tons of extra stuff the longer you run android. There are a couple of deodexed stock builds and a custom rom too should you want additional features not available on stock.
All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...
wackydroid said:
All seemed to go well, BUT
When I boot, in tiny red type at top left, I get a "KERNEL IS NOT SEANDROID ENFORCING", or if booting into recovery "RECOVERY IS NOT SEANDROID ENFORCING".
What is that, and how do I fix it?
[EDIT] - I also just tried flashing the 1.2 version of the kernel and am still getting those messages...HELP...
Click to expand...
Click to collapse
That is normal you can't fix it!!!!!
SkyHigh auto-root kernel
OP.
Another auto root kernel. I've now added support for N920P
[KERNEL] [ROOT] [SM-N920P Exynos 7420] [02 Dec] SkyHigh TW 5.1.1 Kernel [v2.4]
I don't have the device, but I created it to share with users after receiving good feedback on Note5 :good:
Please make no direct download link, but add thread link to your OP (if your desire).
Also, loads of features with Synapse
Cheers,
UITA
THIS IS AN OUT DATED METHOD. A MUCH EASIER METHOD CAN BE FOUND
EMMC 15
EMMC 11
Scroll Down To This Post#3 For Instructions
This is the main thread for rooting (and installing safestrap) on VERIZON Galaxy S5's running
OE1
OK3
OG5
PB1
If your firmware is NOT listed above, you MUST FIRST Follow the section that says "Flashing PB1", This will upgrade/downgrade depending on if you are on any other versions of Android. Yes it will downgrade from marshmallow, so don't ask.
Important Information
One of the apps in this thread "Supersu-me" Is required to complete this process, otherwise you will be stuck with the Kingroot Superuser Manager(which blocks alot of actions we need). You can buy the App here. Supersu-me Pro The new version MAY NOT WORK ANYMORE!!! If you have issues, please message the developer of the app @gatesjunior, we cannot help.
If anyone wants to make a donation make a donation to @GeTex
[email protected]
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
WARNINGSThis Is Very Important!!! Once Your Rooted Do Not Flash Any Firmware Zips Found In My Other Threads Unless They Specify NO_BOOTLOADERS In The File Name!
Reactivation lock MUST BE TURNED OFF!!!
Before Doing Anything Please Install The Latest Samsung Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
YOU MUST DO THIS
General InformationThis is confirmed working on BOK3 Rom with BOK3 Bootloaders, BOG5 with BOG5 Bootloaders, BPB1 with BPB1 Bootloaders and BOE1 with BOE1 Bootloaders!, that were previously unrootable! Just make sure in bottom directions you flash the kernel that matches your firmware!
These files were provided to me by @voices! the files are by CDMA YEMEN TEAM.
I provided the method and editing of files and last but not least @alnazef34 he was the first to tell me about this.
Also would like to thank @gatesjunior for making the Supersu Me app. Please goto his thread and thank him donate to him and go buy his Super-Sume Pro at the playstore and keep a copy for future.
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
Understanding the process
So alot of confusion has surfaced from this thread and how it works and I'd like to explain most of whats going on hopefully without error. When verizon updated the bootloader they made it impossible to downgrade the system back to Kitkat so we could abuse towelroot. Later it was found that while we cannot flash our Systems back we could flash the kernel, allowing us to run the same basic exploit via an ADB terminal remotely and install a root exploit. The end result is that we can then flash our kernel back to Lollipop and then use the exploit to allow kingroot to install it's root method, and then shortly after, we are able to use supersu me to remove kingroot and install SuperSu. Your original kernel is important but for the most part you should all do this on PB1 anyways. NI2 or NK2 are both kitkat kernels and can be used(one is included in the zip)to accomplish this process. because you clearly are not on a Kitkat system it will FREEZE while booting because it's not supposed to boot a lollipop system. So In order for root.bat to work(or root2.bat) you MUST flash a kitkat kernel(NI2 or NK2) and once it succeeds you must flash your original kernel(probably PB1)
Installing PB1
(You will lose all of your app data and apps installed, your internal storage will be fine, backup is recommended anyways
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
2. Reboot to recovery (Power+Volume Up+Home Button) and wipe data from recovery, reboot to bootloader
3. Plug In your phone and open Odin located in the OK3_ROOT folder
3a. Make sure your phone is recognized (In the Odin Screen Under ID:COM the box under will be blue with your com port id #)
4. Click the AP button in the Odin Screen and locate and click on the G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 this is the file that was unziped from the G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip(Everything you do will be flashed via AP!!!!)
4a. This will take a few minutes for odin to load and verify MD5. When done in the odin message box it will say
Code:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS.
5. Under options DO NOT CHANGE ANYTHING (Previously I had you check NandErase but this was part of the problem with root not finishing)
6. Now click on Start
7. When finished you will get a green box that says PASS!
8. Phone will reboot automatically to recovery and finish updating then it will restart
9. When Phone has finished loading and has booted up go through setup and do not add any google accounts or samsung accounts or anything
Rooting InstructionsPlease read EVERYTHING ABOVE BEFORE CONTINUING
This is the BlackCat Update, Hopefully it's better
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
2. Unzip folder.(You need a unzip application like 7z or Winrar)
3. Open The Folder and click Bat file #1, Install APKs, plug in your phone and follow directions
All the Steps for the main rooting process are done ON THE BAT FILES, READ THEM!!!!
If the root process hangs Close the bat, unplug phone pull battery and reboot phone to recovery (VolUp+Pwr+Home). In recovery wipe cache only and reboot. If phone reboots back to recovery instead, pull battery and manually reboot. Now plug phone back in and Launch Bat #3.
IF you get into android and cannot get root, Open bat file #2 and start from there again
If your phone wont reboot, use Bat #4 and try and enter download mode manually(VolDown+Pwr+Home)
4. Open KingRoot.apk Click The Up Arrows a couple of time until you get to Try It and click Try It and that's it don click nothing else just close Kingroot. You should now have root. If It says Root not available and the bat said your were rooted Reboot Phone and open KingRoot You should now be rooted(otherwise reboot phone and check again)
5. Optional: If you Dont want to use SuperSu Me Skip To 6 and try but if it doesnt work then you will have to use SuperSume . Now open SuperSU-Me app (This app is now a paid app so setup Google Play and buy and it will remove kinguser and replace it with SuperSu. If you can't get the Paid version to work. The SuperSu Me 6.7 version worked. So you may have to hunt that one down by asking the Dev of the app) After this process SuperSu will ask to update binary click update normal
6. Copy this G900V_Fix Safestrap.zip (It may come in handy later on) to your SD Card and Internal Storage Copy Safestrap_Flashable_Kernels and Safestrap_Flashable_Firmware and anything else you want to install like the below rom
7. Now open Busybox Installer Allow KingRoot permission click on install
8. Click on Safstrap Allow KingRoot permission then click Install Safestrap after it installs reopen Safestrap and click on install again
9. Reboot phone open Safestrap app and Click Reboot To Recovery. If during this process you every get stuck on samsung screen.
Pull battery reboot phone to bootloader (VolDwn+Pwr+Home) Plug phone into computer open Odin In the AP Slot Flash VZW_BPB1_KERNEL_ONLY.tar.md5 Located in the LOLLIROOT Folder
10. Install This zip Knox_Removal_SU_BB_INIT.D.zip If you dont want a custom rom your done!
11. If you want to flash a custom rom make a backup In safestrap. Then in safestrap Click Wipe then Click Advanced Wipe Then Wipe System,Wipe Data,Wipe Cache Then Install any rom of your choosing as long as it is a Verizon S5 TocuchWiz Based Rom CM builds will not work! If you want you can try this it is stable. If for some reason you get an error flashing zips install this zip G900V_Fix Safestrap.zip in safestrap then you will be able to install roms. That zip wipes system and formats it so you will need to install a rom or backup before leaving safestrap
VZW_BPB1_ODEX_DEODEX_V8.zip This is a fully stock rom just like you had except it is Pre Rooted Knox free Deodexed with Tethering Fix, SDWrite Fix. Other than that all the bloat is still there but now your rooted you can remove it or flash different rom whatever
12. After flashing any rom I would head over to my Safestrap Thread and flash the latest version of Safestrap
Extra InformationExtra Information
If you soft brick your device and you made a backup in safe strap, flashing the NK2 kernel will get you back into safestrap, allowing you to restore your backup
THIS DOES NOT UNLOCK YOUR BOOT LOADER!!! To Unlock the bootloader look at the Sticky in the Development Forum. You cannot flash anything through the stock recovery. Do not try to, you will softbrick!
If you try and flash a rom or anything else, make a backup first, it saves many headaches.
If you cannot flash roms with the error "set_metadata_recursive failed" or something, you likely need to start from scratch BUT with the S5 PIT file(matching your size, there's a 16GB pitfile floating somewhere)
Realize your phone warranty is likely gone after doing this, should anything arise, you can try and get to download mode and flash the stock image again and it may go back to normal status but we cannot encourage fraudulent warranties, no matter how pathetic Samsung's policies are.
If something goes wrong! Here is the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
Here are the new safestrap flashable firmware zips with no bootloaders these are safe to flash on all versions of bootloaders
BOC4_Firmware_No_Bootloaders.zip
BOD5_Firmware_No_Bootloaders.zip
BOE1_Firmware_No_Bootloaders.zip
BOG5_Firmware_No_Bootloaders.zip
BOK3_Firmware_No_Bootloaders.zip
BPB1_Firmware_No_Bootloaders.zip
Here are the new safestrap flashable kernel zips these are safe to flash on all versions of bootloaders
G900V_OC4_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OD5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OE1_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OK3_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip
Wow ...
Chopstix9 said:
Wow ...
Click to expand...
Click to collapse
Edit: Its confirmed Working!!
Need some testers to confirm!
jrkruse said:
Need some testers to confirm!
Click to expand...
Click to collapse
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...
Chopstix9 said:
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...
Click to expand...
Click to collapse
Edit: Confirmed Working!!
Notice I didn't either, but it should work since all you have to do is flash the NI2 kernel which you can still do on the oe1.og5 and ok3 firmwares. They just wouldn't let you flash the ncg system.img
Edit: Confirmed Working!!
Yes it works. However my unknown mistake after achieving root with my bok phone was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.
rnh said:
Yes it works. However my unknown mistake after achieving root with bok was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.
Click to expand...
Click to collapse
Flash the BOK3 kernel it should boot
If it doesnt, Here is the Odin Factory tar image just flash in odin G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip. This does not have the BOD5 bootloaders so it will flash fine for you
Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem
rnh said:
Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem
Click to expand...
Click to collapse
I added the apk above that will work with lollipop
So it seems this works!. The only thing you will want to do is make sure the kernel you flash after you root matches your firmware so you dont get the unauthorized actions message!. And I would get a custom rom flash asap because the stock verizon rom still has knox. I posted in the OP the files you should need to get busybox and lollipop safestrap installed
Edit Root_OG5_V2.zip contained a folder called SafeStrap Flashable Firmwares please dont use these as they contain older bootloaders and may brick your phone. So if you downloaded Root_OG5_V2.zip before i pulled it please dont use those zips
Edit Root_OG5_V3.zip Contains all the files you will need
Tried it, and got stuck after the NI2 kernel update. The batch file would never recognize the device again... ended up having to wipe and recover... more than happy to try again though
***my bad, tried the old method... didn't realize it was updated.
---------- Post added at 07:20 AM ---------- Previous post was at 06:29 AM ----------
confirmed working! You guys rock!
We have a winner! I followed the steps exactly and poof ROOT!
{
"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"
}
Thanks millions
Mine does not reboot after the .bat file fails the first time. I continue on, and when I get to the samsung screen, and I run the .bat once more it gets stuck at 'installing root now' and does not proceed. Help would be appreciated!
Awesome job @jrkruse.
I don't personally need this because I never updated my bootloader but for all of the people out there who updated via OTA or bought a phone that was already updated, you are a life saver.
As always, great work.
---------- Post added at 07:43 AM ---------- Previous post was at 07:27 AM ----------
Actually, I'm quite curious if I may just want to do a full stock Odin flash of OK3 (bootloader and all) since I never plan on going back to kitkat and I can just gain root and deodex the ROM myself for Xposed afterwards.
I've noticed that using the old bootloader with new updates causes my phone's screen to do weird things when I try to charge it while it's off. Using the correct bootloader may fix that.
so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'
Aireos said:
so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'
Click to expand...
Click to collapse
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452
jrkruse said:
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452
Click to expand...
Click to collapse
I have enabled debugging, and have tried different ports. Must've gone over every detail about 6 times total. For now, I just flashed back to factory. Will try again in a few hours if I get some decent replies..
Juust brought my spare to work. Seeems I was on boe1. Is there a kernel for that? I don't think it will do a software update to bok while rooted.
will this keep the phone rooted like it does ever.
to flash the full image and root again is not very easy for me
It seems that no one is gonna take a try, I will and revert.
Just finished upgrading via flash fire. It worked
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
sliding_billy said:
What version of FlashFire? Steps you used. I've been waiting to use it in lieu of TWRP since it does not appear to be a completely GR ready version just yet. I might just continue to use TRWP recovery and still add FlashFire to avoid the rooting step. Does FlashFire remove TWRP during update?
Click to expand...
Click to collapse
bush911 said:
V0.55.1
Extract full stock image file to get image*zip
Copy to phone
Flash firmware package without changing the default settings.
Tarp was removed, now no recovery available
Click to expand...
Click to collapse
Thanks for investigating. I would have thought you would flash the OTA. Doesn't seem to improve the process if recovery is removed but root isn't.
I did. Didn't work. Downloaded OTA. Flashfire kicked in (I'm using FlashFire Pro v0.55.1). It appeared to process the OTA. I flashed. OTA was not successful. I re-flashed SuperSU to restore root.
Flashfire works great
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
I just retook the 7.1.2 OTA but did not restart after download. Opened FlashFire it autodetected the OTA, offered to install and I accepted. Everything went fine. Still have Su and on Sharkey kernal
josephpalozzi said:
I used flashfire 0.55.1. It easily upgraded and kept root.
First dl'd the OTA from Google
Second, open flashfire and ignore it's pop up about the OTA.
Third, hit the + button and select the "flash zip or OTA" option
Forth, direct it to the folder you dl'd the OTA into (probably "data/media/0/Download") I personally did not enable any of the flashing options
Fifth, if you want to easily maintain root, click the "EverRoot" button and at minimum check the box that says "inject Super SU". I also kept TWRP by checking the "preserve recovery" box.
Sixth, click "Flash" or the lightning bolt button, as you prefer, and be patient as it unzips and installs.
Click to expand...
Click to collapse
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
edit: I was able to update to the Feb security patch, but lost twrp in the process. I tried the steps above again, this time I was presented with the ota available pop up screen which I didnt get the first time around. Even with the "preserve recovery" option ticked, it didnt preserve it. I get "no command" when I try to boot into recovery.
Just used TWRP sideload, TWRP IMG, TWRP install and SuperSU install to update XL to February. About to do Pixel. I've got FashFire installed and waiting until it is working in a more stable fashion. No point in fixing what ain't broke for me right now.
llong31 said:
I followed your steps exactly and it failed...after that I tried leaving the "restore boot and recovery images" option checked, and it also failed. Haven't tried removing the "preserve recovery" option. Seems like the "restore boot and recovery option" and "preserve recovery" might cancel each other out. You're positive that you are on the Feb update now?
Click to expand...
Click to collapse
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
mac796 said:
There's also a setting in FlashFire you need to check if you made any mods. It comes checked with keep as original. Maybe that's your problem? Just a guess I have no idea, I'm going to try it today
Click to expand...
Click to collapse
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
mac796 said:
llong31 said:
Not positive, but I'm pretty sure I was on slot A before using flashfire for the OTA, and now I'm on slot B. I had "auto-select" slot chosen in the options before flashing... I'm wondering if that's the issue, I should have kept it on slot A if I wanted to keep TWRP? Everything else went fine, I have the feb update and still rooted.
You would think that would matter being TWRP flashes to both slots. Did you have any mods you made to build prop or system
Click to expand...
Click to collapse
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
llong31 said:
mac796 said:
I didn't see that keep original option. I dont think I have anything that changes the build prop, but its possible one of these does. I have adaway, greenify, elemental x kernal, L speed beta (cant even remember if I have any of the options enabled on that one). ****...as I'm writing this... L speed changes build prop doesn't it? Maybe that was my issue.
Click to expand...
Click to collapse
Maybe I'll try the auto detect see if that helps, in not sure if L speed does. I think most stuff for pixel is systemless
Click to expand...
Click to collapse
Sorry to bump this old thread...how long were ya'll phones 'black' during Flashfire? Mine has been black (but still connected to storage via PC so it's not dead) for like 25 min.
EDIT: After almost an hour, I gave up. I force rebooted the phone hoping Flashfire didn't do anything and it looks like it didn't. Phone booted fine. Going to use the old method and sideload the OTA.
I've used the OTA file from the typical update with FlashFire the past couple months, and I used a file downloaded from Google once before (I don't remember if it was on the phone or a flash drive). The screen didn't stay black very long the times I've used it, I'd guess less than a minute, so apparently something didn't work correctly. Looking through the app and documentation, I'm not sure what you meant by "still connected to storage via PC".