is there a root method, and is it possible, to root the new update (DOK2)???
franchize1989 said:
is there a root method, and is it possible, to root the new update (DOK2)???
Click to expand...
Click to collapse
Use the T3 method posted here.
It is the same now because the only reason the T3 method was different was because T3 was on 5.1.1.
DOK2 is 5.1.1 so now they are the same method.
Just use the BeastMode 1.1.1 kernel to remove the root restriction. (Can't root on a stock kernel after 5.1.1)
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
DeeXii said:
Use the T3 method posted here.
It is the same now because the only reason the T3 method was different was because T3 was on 5.1.1.
DOK2 is 5.1.1 so now they are the same method.
Just use the BeastMode 1.1.1 kernel to remove the root restriction. (Can't root on a stock kernel after 5.1.1)
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
Click to expand...
Click to collapse
Thanks man. I see you can get custom recovery allowing you to use custom roms, correct? What rom do you recommend and what do you use on your 910t on dok2?
I'll root and add custom recovery when I can tomorrow. I will post my success on this thread. Anyone know if I can use cyanogenmod rom once I root and add custom recovery on 910t after dok2 update?
DeeXii said:
Use the T3 method posted here.
It is the same now because the only reason the T3 method was different was because T3 was on 5.1.1.
DOK2 is 5.1.1 so now they are the same method.
Just use the BeastMode 1.1.1 kernel to remove the root restriction. (Can't root on a stock kernel after 5.1.1)
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
Click to expand...
Click to collapse
Thanks. Worked like a charm.
Fyi, kept getting a security warning that would boot me to recovery and also on reboot all WiFi passwords were lost.
To stop the security warning I had to freeze SecurityLogAgent, and for the other I had to change the build prop for "ro.securestorage.support" to false.
Sent from my SM-N910T using Tapatalk
to stop the security message u need to flash the boot img from the stock rom bk to the phone
Mrhunter13 said:
to stop the security message u need to flash the boot img from the stock rom bk to the phone
Click to expand...
Click to collapse
For the N910T? Not the T3.
for either 1 if u have that problem with the security warning when u boot the phone up....the same thing happens when u root the note 5 and s6 edge plus u will not loose root by flashing the boot img back to the phone
You can freeze "securitylogagent" in titanium backup and the message goes away
Sent from my Galaxy S5 using Tapatalk
Check out this thread.
http://forum.xda-developers.com/showthread.php?t=3269755
Sent from my SM-N910T using Tapatalk
If I were to flash the DOK2 update can I ever go back to a previous update and bootloader such as COG2 or ANK4?
Sent from my SM-N910T3 using Tapatalk
There is root for 5.1.1. Once you update you cannot downgrade.
willham said:
There is root for 5.1.1. Once you update you cannot downgrade.
Click to expand...
Click to collapse
I understand, thank you.
Sent from my SM-N910T3 using Tapatalk
CF Auto root has now been updated to support DOK2
https://autoroot.chainfire.eu/
_-..zKiLLA..-_ said:
CF Auto root has now been updated to support DOK2
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Is this system less on stock kernel? Or need custom kernel for cf auto root
Sent from my Galaxy S5 using Tapatalk
Not sure what I'm doing wrong...
Chocu1a said:
Thanks. Worked like a charm.
Fyi, kept getting a security warning that would boot me to recovery and also on reboot all WiFi passwords were lost.
To stop the security warning I had to freeze SecurityLogAgent, and for the other I had to change the build prop for "ro.securestorage.support" to false.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I followed those directions but Odin keeps failing. I got a replacement Note with the new DOK2 build number. Will this method work if the device already has DOK2 on it?
_-..zKiLLA..-_ said:
CF Auto root has now been updated to support DOK2
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Has this been tested/confirmed? I assume this is system-less?
Chocu1a said:
Has this been tested/confirmed? I assume this is system-less?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3269755
DeeXii said:
Use the T3 method posted here.
It is the same now because the only reason the T3 method was different was because T3 was on 5.1.1.
DOK2 is 5.1.1 so now they are the same method.
Just use the BeastMode 1.1.1 kernel to remove the root restriction. (Can't root on a stock kernel after 5.1.1)
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
Click to expand...
Click to collapse
This did not work on my T-MOBILE N910T. Locked the unit boot mode, caused it to overheat. had to resort back to my Nandoid to have a working unit again :crying:
---------- Post added at 07:55 PM ---------- Previous post was at 07:53 PM ----------
Chocu1a said:
Has this been tested/confirmed? I assume this is system-less?
Click to expand...
Click to collapse
This threw my N910T into boot loop - 1st time ever I have this problem with Chainny
willham said:
There is root for 5.1.1. Once you update you cannot downgrade.
Click to expand...
Click to collapse
Is this still an issue? I upgraded my bootloader and modem to DOK2 to run the CMRemix Marshmallow ROM, but because I'm running into some usability issues and random lockup/crashes, I decided to go back to my backed up KitKat-stock-rooted ROM. But ODIN kicks back a FAIL every time I try to install ANK4.
Edit: I realize "5.11" is talking about Lollipop, but I wanted to find about rolling back 6.0.1 Marshmallow.
Related
Just wanted to let everyone know that Chainfire has done it again. His latest SuperSU 1.30 fixes the root issues on MDL. You can use the stock kernel and leave knox alone. No need to freeze seandroid or install the nag fix.
Chainfire's Thread: http://forum.xda-developers.com/showthread.php?t=1538053
Here is the 1.30 zip that I posted on Mudavo's 'how to" thread in the dev section yesterday. http://forum.xda-developers.com/showpost.php?p=41675140&postcount=140 In order to leave Knox alone and use the stock kernel, you will also need SuperSUNoNag-v1.00apk linked here as per Chainfires thread.
troyboytn said:
Here is the 1.30 zip that I posted on Mudavo's 'how to" thread in the dev section yesterday. http://forum.xda-developers.com/showpost.php?p=41675140&postcount=140 In order to leave Knox alone and use the stock kernel, you will also need SuperSUNoNag-v1.00apk linked here as per Chainfires thread.
Click to expand...
Click to collapse
Thank you. Chainfire used to have a disclaimer not to repost his links so I have put a direct link to his thread in the OP. Not sure if he still feels that way or not but I believe it is proper to direct people to his original post.
Edit: Just noticed the NoNag comment. I did not have to install that. I believe that is related to something else. I started over and went back to completely stock MDC, did the OTA to MDL, installed the new SuperSU and did not get any nags. I then updated and installed my rom and still haven't gotten a nag going on 20 hours.
i can confirm this works... i was on MDC and rooted.. used ota keeper and temp unrooted then flashed MDL update and after that i restored root and no errors and no messages ....
profit
Note : the device status now shows custom
So do we flash su1.30 and then the no nag fix? Or just the no nag fix?
opz187 said:
So do we flash su1.30 and then the no nag fix? Or just the no nag fix?
Click to expand...
Click to collapse
You don't need the nag fix anymore. If you are already on MDL Mudavo did this to get it working http://forum.xda-developers.com/showpost.php?p=41714439&postcount=146
Ok so I'm kinda confused. Say I flash back to stock mdc to take the mdl update. I do that little trick and install oudhs recovery on stock mdl. all I have to do is flash supersu 1.30 in recovery and I should be Ok? No need for nonagfix.apk?
opz187 said:
Ok so I'm kinda confused. Say I flash back to stock mdc to take the mdl update. I do that little trick and install oudhs recovery on stock mdl. all I have to do is flash supersu 1.30 in recovery and I should be Ok? No need for nonagfix.apk?
Click to expand...
Click to collapse
You got it.
PapaDocta said:
i can confirm this works... i was on MDC and rooted.. used ota keeper and temp unrooted then flashed MDL update and after that i restored root and no errors and no messages ....
profit
Note : the device status now shows custom
Click to expand...
Click to collapse
It always showed custom when you had custom firmware or a rooted system. I have been told that TriangleAway did work on MDC, haven't confirmed it myself, but I can't get it to work on MDL.
crawrj said:
It always showed custom when you had custom firmware or a rooted system. I have been told that TriangleAway did work on MDC, haven't confirmed it myself, but I can't get it to work on MDL.
Click to expand...
Click to collapse
no not really... on MDC it shows as official not custom and i was rooted then..and i didn't flash recovery or anything just run motochopper root kit...
PapaDocta said:
no not really... on MDC it shows as official not custom and i was rooted then..and i didn't flash recovery or anything just run motochopper root kit...
Click to expand...
Click to collapse
OK maybe I am confused with MDL but I swear I remember seeing custom system while rooted. Having custom recovery/kernel definitely showed custom binary.
Maybe because of the recovery and custom kernel.. I was totally stock with only root no custom recovery or kernel..
---------- Post added at 08:25 PM ---------- Previous post was at 08:19 PM ----------
testing cf-root http://goo.gl/XgI9E
so where can I find the stock Kernel? I flashed shabby's MDL kernel with SetUID disabled.
If I'm not mistaken, I should just be able to flash the unmodified kernel back without having to wipe, right?
Triangle away still shows custom kernel and Google Wallet says "unsupported system".
blarg said:
so where can I find the stock Kernel? I flashed shabby's MDL kernel with SetUID disabled.
If I'm not mistaken, I should just be able to flash the unmodified kernel back without having to wipe, right?
Triangle away still shows custom kernel and Google Wallet says "unsupported system".
Click to expand...
Click to collapse
Yes that is right. I have the stock kernel in my MDL Rom thread but one user reported that it killed his wifi. That is the only user I know have flashed it. No other reports yet. So if you try it please report on whether it worked for you or not.
detection information/seandroid HELP!!
Can anyone please help me I rooted the updated MDL restriction disabled kernal with superuser zip and everything seems to be working but I get this annoying msg from seandroid. Ide like to keep the adittional protection but if the only was to get rid of this msg it to get rid of seandroid I will plz help with walk through..
am I correct to assume that su1.3 allow you to run stock kernel without the need to freeze seandroid?
and if we flashed with a custom kernel, we should flash a stock kernel so not needing to freeze seandroid?
my status: I am on MDL shabby cwm / shabby kernel... I upgraded to su1.3; after defrosting seandroid; I am getting warning seandroid has stopped working.
---------- Post added at 11:10 PM ---------- Previous post was at 11:04 PM ----------
^jeffyxd
try freezing Seandroid; or upgrade to su1.3 (but you might get the same message I am getting afterward) "seandroid has stopped working"
Try this if you are already on MDL and rooted.
http://forum.xda-developers.com/showthread.php?p=41714439
Also custom kernels will still give you a nag. A kernel dev will have to fix that. You will still have to freeze seandroid to clear the kernel nag for now.
Sent from my SPH-L720 using xda premium
if I'm on MDC rooted right now what would be the best way to update to MDL? Thanks
Sent from my SPH-L720 using Tapatalk 2
xchampx13 said:
if I'm on MDC rooted right now what would be the best way to update to MDL? Thanks
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Ohh boy! :banghead::banghead::banghead::banghead::banghead:
Lol I'm j/p... Head to crawrj's thread and check his Op. Takes a bit of time but it took my a bit 40mins to flash back to MDC nd redo the process. Start fresh.
Sent from my SPH-L720 using Tapatalk 2
xchampx13 said:
if I'm on MDC rooted right now what would be the best way to update to MDL? Thanks
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
You can try this. http://forum.xda-developers.com/showthread.php?t=2277480.
If you want MDL AND ROOT that is.
For those of you like myself that took the new update, but may have had second thoughts about wanting to root, I just confirmed that you can flash back via Odin.
I did confirm while I was running the new OE2 update that I was not able to obtain root.
done12many2 said:
For those of you that like myself that took the new update, but may have had second thoughts about wanting to root, I just confirmed that you can flash back via Odin.
I did confirm while I was running the new OE2 update that I was not able to obtain root.
Click to expand...
Click to collapse
patched it right after we got it. boo. ill wait till the next root is achieved before i update. cant live without titanium and greenify
Did you take the update being rooted or unrooted?
done12many2 said:
For those of you like myself that took the new update, but may have had second thoughts about wanting to root, I just confirmed that you can flash back via Odin.
I did confirm while I was running the new OE2 update that I was not able to obtain root.
Click to expand...
Click to collapse
---------- Post added at 01:02 PM ---------- Previous post was at 12:57 PM ----------
What else does the OE2 update do besides patching the way to root OCE?
Where do in get the firmware to revert back? Also will this trip Knox if I decide to revert for root?
Alaris said:
Where do in get the firmware to revert back? Also will this trip Knox if I decide to revert for root?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3106909
No, it will not trip.
done12many2 said:
http://forum.xda-developers.com/showthread.php?t=3106909
No, it will not trip.
Click to expand...
Click to collapse
downgrade kernel and try root
It doesn't block root, it's a new kernel, pingpong dev will need the new kernel to make the root work with it, just they need the kernel for every version that they support.
Sunderwear said:
downgrade kernel and try root
Click to expand...
Click to collapse
Can confirm, this works.
When i use odin to downgrade which one do i coose for the kernel?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
blkghost22 said:
When i use odin to downgrade which one do i coose for the kernel?
Sent from my SAMSUNG-SM-G925A using XDA Free mobile app
Click to expand...
Click to collapse
You need to extract it from
AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5
and package it up as a tar.md5 so you can use it in odin.
Or just wait for pingpong to update, I gave them the updated kernel and stuffs.
designgears said:
You need to extract it from
AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5
and package it up as a tar.md5 so you can use it in odin.
Or just wait for pingpong to update, I gave them the updated kernel and stuffs.
Click to expand...
Click to collapse
You my friend are awesome for doing such so soon.
nookie1916 said:
You my friend are awesome for doing such so soon.
Click to expand...
Click to collapse
hehe
Actually patched the entire firmware offline with the OTA zip
Alaris said:
Where do in get the firmware to revert back? Also will this trip Knox if I decide to revert for root?
Click to expand...
Click to collapse
Check out this page for help with downgrading back to NCE: link
Or, simply try pingpong root after downgrading kernel using NCE's recovery.img, available as Odin flashable, here: link
The beta 6 version of PingPong root will root the new OE2 update. I rolled back to OCE this morning, applied the update and then noticed beta 6 and was successful with rooting.
ElvisExMachina said:
The beta 6 version of PingPong root will root the new OE2 update. I rolled back to OCE this morning, applied the update and then noticed beta 6 and was successful with rooting.
Click to expand...
Click to collapse
Thanks for the update!
ElvisExMachina said:
The beta 6 version of PingPong root will root the new OE2 update. I rolled back to OCE this morning, applied the update and then noticed beta 6 and was successful with rooting.
Click to expand...
Click to collapse
Notice any difference?
teamfresno said:
Notice any difference?
Click to expand...
Click to collapse
Hard to judge since it is new. Screen on time is 5 Hours 50 minutes where before I was getting about 4 Hours 10 Minutes. I removed bloat of course so it was snappy as it was when rooted before. Free memory fluctuates from 900Mb to 200Mb but that was happening with rooted OCE. The main improvement seems to be SOT.
designgears said:
You need to extract it from
AP_G920AUCU1AOCE_CL4351102_QB4488924_REV02_user_low_ship.tar.md5
and package it up as a tar.md5 so you can use it in odin.
Or just wait for pingpong to update, I gave them the updated kernel and stuffs.
Click to expand...
Click to collapse
I tried to ODIN back to stock using the tar.md5 and its giving me md5 hash value is invalid, I redownloaded the rom again and checked to make sure no errors on the file with winrar and didnt find any error but still getting the same error when flashing with ODIN. Any help will be appreciated. Thank you.
ElvisExMachina said:
The beta 6 version of PingPong root will root the new OE2 update. I rolled back to OCE this morning, applied the update and then noticed beta 6 and was successful with rooting.
Click to expand...
Click to collapse
Strange, it didn't work for me.
done12many2 said:
Strange, it didn't work for me.
Click to expand...
Click to collapse
Disregard, I'm just slow.
ElvisExMachina said:
The beta 6 version of PingPong root will root the new OE2 update. I rolled back to OCE this morning, applied the update and then noticed beta 6 and was successful with rooting.
Click to expand...
Click to collapse
Can you please help me to revert back to OCE? I put the tar.md5 to the AP box and keep getting hash invalid error. Thanks.
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Try wiping your caches in recovery. Same thing happened to me for 5.0
Sent from my SM-G900T using XDA Free mobile app
thienbrand said:
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
Click to expand...
Click to collapse
Try doing what Kevin said. Otherwise reflash the update in Odin, download here or mega mirror.
After I installed Recovery or root, I do full wipe.
But remain the same.
Sent from my SM-G900T using XDA Free mobile app
Kevin or lingo, are you saying it works ok for you?
Sent from my SM-G900F using Tapatalk
A better question, are we able to downgrade after installation of this version?
I seen a screenshot of the S6 update screen and it showed that a downgrade would not be possible.
thienbrand said:
After I installed Recovery or root, I do full wipe.
But remain the same.
Click to expand...
Click to collapse
Try downloading the rom from the link I posted and flash it in odin, if you wan't to get out of bootloop.
pnut22r said:
Kevin or lingo, are you saying it works ok for you?
Click to expand...
Click to collapse
I haven't tried it, my S5 is 900F international. And I don't know the procedure for flashing T-Mobile roms on the 900F.
Maybe we can flash the rom but I'm pretty sure the bootloader and kernel is a no go.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
thienbrand said:
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
This is good news, thanks!
thienbrand said:
This is a [WARNING] Don't flash any other thing after you update Tmobile S5 to 5.1.1!
I have just flashed 5.1.1 and tried to flash CF-AUTOROOT / TWRP / CWM / ANY ROOT OR RECOVERY and I stucked at bootloop while the phone kept on ringing 4times at the T-mobile boot screen.
i think Samsung had changed something to prevent from install recovery or root on S5 in 5.1.1.
We should wait for someone to make 5.1.1 root.
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
Try this, run cf auto root, let it reboot, yank the battery, reboot to dl mode and flash ONLY the stock recovery from the update and reboot
thienbrand said:
The good news: You are able to downgrade from 5.1.1 to 5.0 or even 4.4 just by flashing previous firmwares using ODIN.
Without any problem. Full service, imei, SV, .... everything's fine.
Click to expand...
Click to collapse
Add this to your op so people don't freak out lol
I'm sure we'll get a working root method for 5.1.1, iirc I read the S6 running 5.1.1 was easily rooted, even without tripping KNOX
Can anyone post some screenshot of this release? Thanks in andvance!
nfs11 said:
Can anyone post some screenshot of this release? Thanks in andvance!
Click to expand...
Click to collapse
Looks the same as 5.0
ShinySide said:
Looks the same as 5.0
Click to expand...
Click to collapse
Theme support?
ShinySide said:
Try this, run cf auto root, let it reboot, yank the battery, reboot to dl mode and flash ONLY the stock recovery from the update and reboot
Click to expand...
Click to collapse
We don't have the seperate recovery file.
nfs11 said:
Theme support?
Click to expand...
Click to collapse
No theme support. It's still a S6 exclusive.
thienbrand said:
We don't have the seperate recovery file.
Click to expand...
Click to collapse
It's in the tar. I tried it few minutes ago, still wouldn't boot
m_malyszko said:
No theme support. It's still a S6 exclusive.
Click to expand...
Click to collapse
I guess that will be exclusive for a limited time. I hope.
m_malyszko said:
No theme support. It's still a S6 exclusive.
Click to expand...
Click to collapse
That's disappointing, my excitement for 5.1.1 has just disappeared.
Hey guys I create this section for people interested root device s6 , anybody get root for phone please share way for people because I can't used phone without root
I have questions, how to make root ,what's file need to edit , what is kernel.....
Thanks
Have you updated to 5.1.1 yet?
fixy32 said:
Hey guys I create this section for people interested root device s6 , anybody get root for phone please share way for people because I can't used phone without root
I have questions, how to make root ,what's file need to edit , what is kernel.....
Thanks
Click to expand...
Click to collapse
Ya there's root already for 5.1.1.
Go to the unified dev section for GS6 and grab the unified kernel. You'll need to unlock bootloader first in dev options then flash the latest TRWP recovery in Odin. Then flash the kernel and you'll have root.that's the version, so take a look at the details before flashing.
Sent from my SM-G920T using Tapatalk
Yes, He is correct! I followed the instruction and have root on my sm-g920t......awesome!
jzero88 said:
Ya there's root already for 5.1.1.
Go to the unified dev section for GS6 and grab the unified kernel. You'll need to unlock bootloader first in dev options then flash the latest TRWP recovery in Odin. Then flash the kernel and you'll have root.that's the version, so take a look at the details before flashing.
Sent from my SM-G920T using Tapatalk
Click to expand...
Click to collapse
Please share url for the wtrp recovery I'm on 5.1.1 stock
Thanks
fixy32 said:
Please share url for the wtrp recovery I'm on 5.1.1 stock
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...d-development/kernel-stockmod-kernel-t3100395
download the kernel. put phone into download mode. open odin. click ap, select kernel file. click start. fixed.
Im on 5.1.1 and I tried rooting today, got stuck in boot loop. This fixed it right away and now I am rooted.
hope it helps.
Anyone have the stock OF6 G920T kernel, maybe TWRP flashable?
id10terrordfw said:
Anyone have the stock OF6 G920T kernel, maybe TWRP flashable?
Click to expand...
Click to collapse
I just uploaded the tar
https://www.androidfilehost.com/?fid=24052804347771401
i rooted my t-mo s6 with the above method, but the phone feature broke... can't hear the person i'm calling at all. i'm not sure if the mic is broke since i cannot hear the person on the other end...
i should have kept the phone on 5.0.2 @[email protected]
I finally have root, TWRP, call audio and data without tripping knox on my stock GS6 5.1.1. I didn't think it was possible. Am I wrong? Has this been done already and I'm just late to the game?
please share the method you used, because when i root my s6 on 5.1.1, i get no call audio...
I'm wondering if it's even worth rooting this phone. Setup wise I was able to disable and hide all bloatware with a $1.50 app. If I could get xposed working with temp root. I'd be a happy camper.
Sent from my SM-G920T using XDA Free mobile app
dnaL0R said:
please share the method you used, because when i root my s6 on 5.1.1, i get no call audio...
Click to expand...
Click to collapse
I installed the engineering sboot in download mode with odin, then allowed to restart rom, booted back to download mode, then v3 of the unified Kernel for sm-920T in download mode with odin, booted the rom, back up my efs, installed TWRP v12 (g925t_of6_aou_twrp_recovery_v12) with Flashify, rebooted into download mode and flashed g920t_of6_aou_kernel_v1.tar kernel.
I did get the security manager prompt after the restart but there is a way to freeze that prompt with Titanium Back up. I'm looking for that now
Are you sure you still haven't tripped Knox?
GeorgeNYer said:
Are you sure you still haven't tripped Knox?
Click to expand...
Click to collapse
Just checked. KNOX WARRANTY VOID: 0 (0×0000) is what it shows. I installed a custom rom (Xtrestolite) and all I needed to do was reflash the second kernel again to get audio back. Fingerprint is the only thing that isn't working so far.
I can post an image of the bootloader screen if you'd like.
jabreu203 said:
Just checked. KNOX WARRANTY VOID: 0 (0×0000) is what it shows. I installed a custom rom (Xtrestolite) and all I needed to do was reflash the second kernel again to get audio back. Fingerprint is the only thing that isn't working so far.
I can post an image of the bootloader screen if you'd like.
Click to expand...
Click to collapse
I tried it myself and I can confirm it works. Thanks you! And I thumbprint scanner also doesn't work for me but I guess I can wait for that fix
GeorgeNYer said:
I tried it myself and I can confirm it works. Thanks you! And I thumbprint scanner also doesn't work for me but I guess I can wait for that fix
Click to expand...
Click to collapse
Please hit the "Thank you" button if it works for you. You are very welcome. Glad that it worked for you.
GeorgeNYer said:
I tried it myself and I can confirm it works. Thanks you! And I thumbprint scanner also doesn't work for me but I guess I can wait for that fix
Click to expand...
Click to collapse
Fingerprint scanner won't work cause that bootloader is a 5.0.2 bootloader.
jabreu203 said:
I installed the engineering sboot in download mode with odin, then allowed to restart rom, booted back to download mode, then v3 of the unified Kernel for sm-920T in download mode with odin, booted the rom, back up my efs, installed TWRP v12 (g925t_of6_aou_twrp_recovery_v12) with Flashify, rebooted into download mode and flashed g920t_of6_aou_kernel_v1.tar kernel.
I did get the security manager prompt after the restart but there is a way to freeze that prompt with Titanium Back up. I'm looking for that now
Click to expand...
Click to collapse
great job, thanks! could you please make a new post in general to increase visibility?
Remix22 said:
great job, thanks! could you please make a new post in general to increase visibility?
Click to expand...
Click to collapse
Since Sammy issued a DMCA for the sboot, that's probably not a good idea
h t t p : / / bit.ly/1VbaNG2
Password: mymovilar
Use 7zip to decompress
what release is this?
EDIT: nvm, it seems like this is OI5
this is OI5 Or PA1 ??
dbazze said:
this is OI5 Or PA1 ??
Click to expand...
Click to collapse
OI5
sensei22 said:
OI5
Click to expand...
Click to collapse
it works but I need Fille PA1 If YOu Have :good: Thanks
These 4 files, BL, AP, CP and CSC, are already in my "[GUIDE] Soft-bricked, or just looking to unroot (UPDATED 03-06-2016)?" guide; in a .rar file without the dumb password, at the first link.
---------- Post added at 06:35 PM ---------- Previous post was at 06:29 PM ----------
shortydoggg said:
These 4 files, BL, AP, CP and CSC, are already in my "[GUIDE] Soft-bricked, or just looking to unroot (UPDATED 03-06-2016)?" guide; in a .rar file without the dumb password, at the first link.
Click to expand...
Click to collapse
...And for those who are looking to upgrade to PA1, all most need to do is flash the 4 files to OI5 and from there you should be able to OTA.
I thought you could only get OTA if you have an att subscription which is not my case.
Sent from my SAMSUNG-SM-G900A using XDA-Developers mobile app
So does this mean 5.1.1 w/root?
I believe this is unrooted as I flashed it and have no root access
Sent from my SAMSUNG-SM-G900A using XDA-Developers mobile app
I am new to flashing android. Could anybody give installation steps. What problems could I face If something goes wrong and how do I revert back to make my phone usable.
Thank You
instructions
Any instructions for this method .
Thanks.
mr_nike45 said:
h t t p : / / bit.ly/1VbaNG2
Password: mymovilar
Use 7zip to decompress
Click to expand...
Click to collapse
Does this root the s5 running 0f3, I'm confused sorry,.
nisstunned said:
Any instructions for this method .
Thanks.
Click to expand...
Click to collapse
Put your phone into download mode, flash the files with Odin.
DragnSin said:
Does this root the s5 running 0f3, I'm confused sorry,.
Click to expand...
Click to collapse
Im curious about the same exact thing. As im on OF3 running 5.0 and desperately want to root.
from a soft brick running oc4 to a working S5 updated
Thanks for the files!
i originally soft bricked with pa2 update and i did not have any recovery what so ever for it. Downloaded this file loaded odin and it made it work again. i flashed all files.
My stock S5 upgraded to 6.0.1 the other day and I don't like it. Can I flash this to downgrade to lollipop?
serstylz2 said:
Can I flash this to downgrade to lollipop?
Click to expand...
Click to collapse
No, i think not, why? not sure but they say it will brick.
I've been wondering about this myself...
Come to think of it, let's say they did burn a qfuse in this update (which they probably did), then in order to get yourself back in working order you'd need to be able to use odin to flash a working 6.0.1 stock rom, I'd think.
The problem is that, as far as I'm aware, only the update is available not the rom itself...
That'd be a big problem for anyone trying to experiment...
Did anyone here have the problem trying to flash back to 4.4.2 after the lollipop update? This should be the same as far as treatment goes.
Is there a way to tell if the qfuse has been burned? I got a G900A before I realized that the ATT version was locked 6 ways to sunday, and have been sitting on PH3 since I got it.. However I dont know if the previous update to PH3 was applied OTA or not, considering I got the phone already factory unlocked.
Is there an easy way to tell if the current version of my rom was applied via OTA or USB?
invert_nexus said:
I've been wondering about this myself...
Come to think of it, let's say they did burn a qfuse in this update (which they probably did), then in order to get yourself back in working order you'd need to be able to use odin to flash a working 6.0.1 stock rom, I'd think.
The problem is that, as far as I'm aware, only the update is available not the rom itself...
That'd be a big problem for anyone trying to experiment...
Did anyone here have the problem trying to flash back to 4.4.2 after the lollipop update? This should be the same as far as treatment goes.
Click to expand...
Click to collapse