Kind of got stuck taking the NK2 official update, trying to port a tmobile rom. Yes, odin did not work for me. Needed to take stock to fix my problem. Anyways, when I first tested this rom, fingerprint scanner did not work. hmmmm. But this was when I was on NIE firmware. So today, after the update, I decided to flash it again. What do you know. Everything works. So, moral of the story is. If you want the stock NK2 rom and everything to function, you must take the official update. Then reroot and recovery. tx_dbs_tx and I had suspicsions that may be the bootloader and firmware lol
LINK>>>> https://www.androidfilehost.com/?fid=95857557620392391
pongoface said:
Real quick and simple. Stock, rooted, no knox, busy box, init d, dedeox, private mode good, Thanks to tx_dbs_tx
https://www.androidfilehost.com/?fid=95857557620392391
YuP
Click to expand...
Click to collapse
testing lets see what's in side.:good:
---------- Post added at 08:51 PM ---------- Previous post was at 08:48 PM ----------
pongoface said:
Real quick and simple. Stock, rooted, no knox, busy box, init d, dedeox, private mode good, Thanks to tx_dbs_tx
https://www.androidfilehost.com/?fid=95857557620392391
YuP
Click to expand...
Click to collapse
kasey348 said:
testing lets see what's in side.:good:
Click to expand...
Click to collapse
you forgot the version is NK2?
you forgot the version is NK2?
Click to expand...
Click to collapse
Thanks all set lol, it's barebones stock but with everything you need, I believe. Hot out the kitchen.
Let's see thank you I'm looking for fully working Room to theme some of the green samsung crap,
whats removed?
It's stock with it all the futures looks like everything works simple,,,,
---------- Post added at 09:26 PM ---------- Previous post was at 09:16 PM ----------
barebones is good developer but i didn't see him on the international note 4
Fingerprint scanner is borked on this release, I may pull link
pongoface said:
Fingerprint scanner is borked on this release, I may pull link
Click to expand...
Click to collapse
You don't have to pull the link, If the fingerprint scanner is the only thing is borken,just clarify that fingerprint does not work, we can get a work around, maybe in v2 will work.
pongoface said:
Fingerprint scanner is borked on this release, I may pull link
Click to expand...
Click to collapse
I don't see any issue with fingerprint is working fine the only thing is missing is a few toggles.
I believe the fingerprint scanner issue is caused by flashing the NK2 rom using the original NIE bootloader. This is why it works for some and not others. Some people never took the NK2 OTA and never odin flashed the NK2 tar. I'm one of those who doesn't want to update my bootloader but io might have to anyway because even when Lolipop releases for our phone I'm sure the old NIE bootloader will cuase even more problems.
pongoface said:
Fingerprint scanner is borked on this release, I may pull link
Click to expand...
Click to collapse
tx_dbs_tx said:
I believe the fingerprint scanner issue is caused by flashing the NK2 rom using the original NIE bootloader. This is why it works for some and not others. Some people never took the NK2 OTA and never odin flashed the NK2 tar. I'm one of those who doesn't want to update my bootloader but io might have to anyway because even when Lolipop releases for our phone I'm sure the old NIE bootloader will cuase even more problems.
Click to expand...
Click to collapse
You are right i have 2 note 4 and i update one with odin NK2 then root and flash different rooms and no issues the one with the NIE bootloader doesn't work and the ram is always over than 2gigs the NK2 is on 1.7gigs ,
Why do our posts keep getting cut of? LOL! Anyway. If you have the original NIE firmware/bootloader and DO NOT install the NK2 OTA or NK2 .tar, you will have a non working fingerprint scanner if you flash a NK2 rooted rom via recovery. On the other hand if you did take the NK2 OTA or flashed the NK2 tar with Odin then you can flash a custom rooted NK2 rom and the fingerprint scanner will work. I was afraid of the new NK2 bootloader but it looks like we have no choice but to upgrade our bootloader or else we can expect to have issues like this in the future. This happened to note 2 users a while back and I finally figured out the cause with some troubleshooting and trial and error. I initially had thought it was the custom recovery breaking charging when powered off but I later learned it was the mismatched bootloader/system.
pongoface said:
Fingerprint scanner is borked on this release, I may pull link
Click to expand...
Click to collapse
Seems to work for me.. only question i have is did installing the nk2 bootloader fix private mode. For me it did not. I had to use the fix.
MasterZen88 said:
Seems to work for me.. only question i have is did installing the nk2 bootloader fix private mode. For me it did not. I had to use the fix.
Click to expand...
Click to collapse
It worked for me for odex roms. That doesn't work for deodex roms however
Private/personal mode fix is unrelated to the bootloader. It works for odexed or deodexed systems. The way I did it was strictly with the apk. However im willing to bet that if your on the old NIE bootloader and running the NK2 system then it might break it. I don't believe the personalpager app was updated in the NK2 OTA so using the same one iI shared on AFH is fine. I assume pongoface shared the file/link?
tx_dbs_tx said:
Private/personal mode fix is unrelated to the bootloader. It works for odexed or deodexed systems. The way I did it was strictly with the apk. However im willing to bet that if your on the old NIE bootloader and running the NK2 system then it might break it. I don't believe the personalpager app was updated in the NK2 OTA so using the same one iI shared on AFH is fine. I assume pongoface shared the file/link?
Click to expand...
Click to collapse
The one on AFH looks like the PersonalPageService.apk is not a deodex version.
Not sure if anyone notice but when you extract PersonalPageService.odex, most of the files have the wrong bootclass reference for smali. You will notice that the code references files that dont exist.
However the version you have within AFH is a stright apk with no odex dalvik extraction. But it seems this version is working and the knox is canceled out through a smali edit.
Can u safely take the NK2 Ota if I'm rooted on NIE?
shawn01 said:
Can u safely take the NK2 Ota if I'm rooted on NIE?
Click to expand...
Click to collapse
If your rooted you cant install the OTA update, i Odined the stock NK2 tar and rooted the same way as i did on NIE with no issues
So I can just installed the OTA no problem than re root? I'd rather not Odin and wipe my entire phone and possible lose pictures so on and on.
shawn01 said:
So I can just installed the OTA no problem than re root? I'd rather not Odin and wipe my entire phone and possible lose pictures so on and on.
Click to expand...
Click to collapse
Take the OTA, no probs man. Reroot and reinstall twrp. You won't lose anything..... MaGic
Related
My apologies if I missed a thread. I am new to these parts as I just got a brand new S4 tonight and I had the dumb idea of taking the OTA that popped up right when I turned it on ,which is UVUFNH7, without a thought for the potential consequences. The build is from 8/27/14 and I can't even find it on samfirmwares.
Am I one of the first few to get this update or did I miss something?
I don't see any threads or links in the stickies about an official TW 4.4.4 update. I intend to get off TW for a GPE rom ASAP so I'm hoping I didn't screw anything up.
Could you post few screenshots, s4 t-mobile is the first to get 4.4.4 from s4 family
What was the size of ota for 4.4.4 ?
http://support.t-mobile.com/docs/DOC-5887
It's not a big update, mainly WiFi calling improvements plus whatever 4.4.4 and 4.4.3 adds on to 4.4.2
hare89 said:
Could you post few screenshots, s4 t-mobile is the first to get 4.4.4 from s4 family
What was the size of ota for 4.4.4 ?
Click to expand...
Click to collapse
Here you go. The OTA was 400MB+. Can't remember exact size anymore
I have the update copied from /cache/fota but can't install it through recovery. Would I have to flash stock recovery to be able to flash the update.zip? Is there some way to flash it through CWM? Just curious? Nothing in 4.4.4. That I absolutely need but if I could do something and upload it for everyone let me know.
Can anybody check is there option now in developer options to change runtime from dalvik to art ??
Daistaar said:
I have the update copied from /cache/fota but can't install it through recovery. Would I have to flash stock recovery to be able to flash the update.zip? Is there some way to flash it through CWM? Just curious? Nothing in 4.4.4. That I absolutely need but if I could do something and upload it for everyone let me know.
Click to expand...
Click to collapse
You need to be fully stock and unrooted to apply an ota.
hare89 said:
Can anybody check is there option now in developer options to change runtime from dalvik to art ??
Click to expand...
Click to collapse
I see nothing for ART
Does this update break TowelRoot?
Sammobile release full firmware
http://www.sammobile.com/firmwares/3/?download=34779
Can someone download and pull the radio? I can't download it,dunno why.
acey_zero said:
Does this update break TowelRoot?
Click to expand...
Click to collapse
I was previously rooted on stock 4.4.2 via CF-Auto-Root.
After the 4.4.4 update, it initially broke root but I was able to reroot by flashing CF-Auto-Root via Odin again. Works just fine
I wonder how this will work with the older bootloader, sans Knox.
Don't want to update to trip it.
The last LTE radio didn't work with it for audio.
Updated to Sammobile's snapshot of 4.4.4 and my radio and wifi isn't working, any suggestions?
trying yr luck said:
I was previously rooted on stock 4.4.2 via CF-Auto-Root.
After the 4.4.4 update, it initially broke root but I was able to reroot by flashing CF-Auto-Root via Odin again. Works just fine
Click to expand...
Click to collapse
Thanks, I don't want to trip Knox though. If anyone can confirm whether this breaks TowelRoot please let us know.
https://mega.co.nz/#!VMBiAaLZ!_Sd7P7GVlb8w_I6esHYXZuRZ38Xn71rgQH1DC2bkOf8
xXchrizhurtyXx said:
I will have this post with a link to mega to download soon because sammobile takes quite a while.
Check back for the edit soon.
Click to expand...
Click to collapse
Does anyone have the ota file?
M919n users gotta be pissed....their still 4.3 haha
xXchrizhurtyXx said:
I will have this post with a link to mega to download soon because sammobile takes quite a while.
Check back for the edit soon.
Click to expand...
Click to collapse
Thanks. I just want a flashable of the radio
BoboBrazil said:
Thanks. I just want a flashable of the radio
Click to expand...
Click to collapse
LINK IS UP. I had to flash the file twice because i had radio/wifi issues the first time. So try flashing twice and you will see it work.
edit - never mind initial dl finally finished
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new N900TUVUFOB6 (Lollipop!) firmware release for the SM-N900T.
IF YOU NEED NE6 (KK) FIRMWARE, GO HERE:http://forum.xda-developers.com/showthread.php?t=2846074
IF YOU NEED NF1 (KK)FIRMWARE, GO HERE: http://forum.xda-developers.com/showthread.php?t=2789932
IF YOU NEED NF4 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
IF YOU NEED NF9 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/not...900tuvudnf9-extracted-stock-firmware-t2873520
IF YOU NEED NK3 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/showthread.php?t=2952883
Bootloader: http://www.mediafire.com/download/1h3olod7h3tgd0x
CSC: http://www.mediafire.com/download/2qbxsaju7vh9nps
Kernel: http://www.mediafire.com/download/48x9cj8c58bvqwu
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/yfxoxii8xxmzmtr
modem.bin: http://www.mediafire.com/download/f0qr4yknd4gktc6
NON-HLOS.bin: http://www.mediafire.com/download/bnobf4xi58nfm5p
Recovery: http://www.mediafire.com/download/83gdup3425b4d44
Full Stock Image N900TUVUFOB6: http://www.mediafire.com/download/cuoz62g1ca6id9t
If you have trouble getting the bootloader and/or Modem to stick, ipower off your device for 10 seconds, then boot direclty into download mode, and re-flash them with Odin 3.09 and they should stick.
To verify, you can download "Phone Info - Samsung" and make sure that all 4 items say N900TUVUFOB6 (Bootloader, Baseband, PDA and CSC).
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
NOTE: I do not know if MOP and/or Triangle away works properly with 5.0/Lollipop yet - use at your own risk.
Enjoy, and as always, slap that Thanks button!
toastido said:
Here's the MODEM+NON-HLOS (both together and as separate files), Bootloader, Kernel, CSC, and Recovery I extracted from the new N900TUVUFOB6 (Lollipop!) firmware release for the SM-N900T.
IF YOU NEED NE6 (KK) FIRMWARE, GO HERE:http://forum.xda-developers.com/showthread.php?t=2846074
IF YOU NEED NF1 (KK)FIRMWARE, GO HERE: http://forum.xda-developers.com/showthread.php?t=2789932
IF YOU NEED NF4 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
IF YOU NEED NF9 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/not...900tuvudnf9-extracted-stock-firmware-t2873520
IF YOU NEED NK3 (KK) FIRMWARE, GO HERE: http://forum.xda-developers.com/showthread.php?t=2952883
Bootloader: http://www.mediafire.com/download/1h3olod7h3tgd0x
CSC: http://www.mediafire.com/download/2qbxsaju7vh9nps
Kernel: http://www.mediafire.com/download/48x9cj8c58bvqwu
Modem + NON-HLOS (Combined): http://www.mediafire.com/download/yfxoxii8xxmzmtr
modem.bin: http://www.mediafire.com/download/f0qr4yknd4gktc6
NON-HLOS.bin: http://www.mediafire.com/download/bnobf4xi58nfm5p
Recovery: http://www.mediafire.com/download/83gdup3425b4d44
Full Stock Image N900TUVUFOB6: STILL UPLOADING - NOT YET AVAILABLE
If you have trouble getting the bootloader and/or Modem to stick, ipower off your device for 10 seconds, then boot direclty into download mode, and re-flash them with Odin 3.09 and they should stick.
To verify, you can download "Phone Info - Samsung" and make sure that all 4 items say N900TUVUFOB6 (Bootloader, Baseband, PDA and CSC).
Triangle Away by @Chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Phone INFO ★Samsung★ by @vndnguyen: https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
Mobile Odin Pro: https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro
NOTE: I do not know if MOP and/or Triangle away works properly with 5.0/Lollipop yet - use at your own risk.
Enjoy, and as always, slap that Thanks button!
Click to expand...
Click to collapse
Didn't use your files, updated on my own. But I can confirm that this method works to keep Knox 0x0 with lollipop
Spoke too soon. lost root
CravingMender9 said:
Didn't use your files, updated on my own. But I can confirm that this method works to keep Knox 0x0 with rooted lollipop
Click to expand...
Click to collapse
Don't understand, what do you mean by "don't use your files" ?
Pp.
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
TOASTIDO your the "toast" of the XDA town. :sly::thumbup:
Pp.
PanchoPlanet said:
Don't understand, what do you mean by "don't use your files" ?
Pp.
---------- Post added at 10:01 AM ---------- Previous post was at 09:54 AM ----------
TOASTIDO your the "toast" of the XDA town. :sly::thumbup:
Pp.
Click to expand...
Click to collapse
I didn't say "Don't". I said that I didn't use his files since I used my own.
---------- Post added at 10:18 AM ---------- Previous post was at 10:06 AM ----------
@Toastido
Were you able to keep root?
CravingMender9 said:
I didn't say "Don't". I said that I didn't use his files since I used my own.
---------- Post added at 10:18 AM ---------- Previous post was at 10:06 AM ----------
@Toastido
Were you able to keep root?
Click to expand...
Click to collapse
You confirmed "this" method worked, but what is "this" method?
Sent from my LG-D415 using XDA Premium App
CravingMender9 said:
@Toastido
Were you able to keep root?
Click to expand...
Click to collapse
I got a bit overexcited last night and blew my entire phone away to try out the lollipop, so.....
I'm in the process of restoring a nandroid of NK3 (since I realized I had way too much stuff to lose) and will try it when Its done restoring. I *THINK* you may have to use MOP and inject root into the full image to keep root if you're worried about Knox 0x0, but IDK; I've tripped Knox long ago .
toastido said:
I got a bit overexcited last night and blew my entire phone away to try out the lollipop, so.....
I'm in the process of restoring a nandroid of NK3 (since I realized I had way too much stuff to lose) and will try it when Its done restoring. I *THINK* you may have to use MOP and inject root into the full image to keep root if you're worried about Knox 0x0, but IDK; I've tripped Knox long ago .
Click to expand...
Click to collapse
Yes, I did that. Used MOP to inject itself and supersu. After starting for the first time, it asked to update supersu and the su binary.
When I did that, it tried updating the binary for some time and finally gave up. In short, I lost root even when I used that option in MOP.
I do care about knox status due to enterprise reasons. So I'll try to downgrade, re-root and upgrade again (to see I didn't do anything wrong.)
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
googlephone said:
You confirmed "this" method worked, but what is "this" method?
Sent from my LG-D415 using XDA Premium App
Click to expand...
Click to collapse
Sorry if I wasn't clear. The method I refer to is what I used to update all previous versions and keep knox 0x0.
It has been discussed after every update and effortless comes up with a tutorial as well. Unfortunately, with 5.0, this doesn't work properly (no root).
Why... just WHY?
I had to download NK3 after midnight because this wasn't online and now I am going to update via Kies, JUST WHY!!!!
@toastido thanks brotha u helped me root my device. Cf auto root messed up my phone originally because it installs kitkat recovery at the end with your Odin flash able recovery I was able to use Cf auto root then before booting flash stock recovery. Right now I'm on completely stock rooted. Just what I wanted.
For those who want to upgrade from rooted kitkat to lollipop and keep knox 0x0 and root, follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=59223071&postcount=1
Thanks to vladeco and toastido! Not me. I just put them together.
I just flash using Kies 5.0,but i like to root have some way to do?
NFC!!!!
I have not rooted yet, but I can confirm that NFC is at least accessible to the system (I was able to send files to the guy next to me).
I will try wallet at the gas station @ lunch.
Just to pop in and say your the boss, @toastido. I unrooted yesterday, took OTA, have rooted with c f auto root. Works, and to be honest, it's sweet. Runs very fast. Unfortunately, I'm back on Tweaked cause there are things I can't live without for now.
overkillthemighty said:
I have not rooted yet, but I can confirm that NFC is at least accessible to the system (I was able to send files to the guy next to me).
I will try wallet at the gas station @ lunch.
Click to expand...
Click to collapse
NFC works. Google Wallet Tap to Pay doesn't
CSC version is N900TTMBF0B6 correct?
Just making sure because the original post says that the bootloader, baseband, pda, and CSC are supposed to be N900TUVUF0B6. They all are except the CSC version. That one is different. Is this correct?
any root flashable zip??
raulg15 said:
CSC version is N900TTMBF0B6 correct?
Just making sure because the original post says that the bootloader, baseband, pda, and CSC are supposed to be N900TUVUF0B6. They all are except the CSC version. That one is different. Is this correct?
Click to expand...
Click to collapse
Yes. That is correct.
CravingMender9 said:
Yes. That is correct.
Click to expand...
Click to collapse
Okay thank you.
I flashed the full image once and the baseband and bootloader stayed NK3 but everything else upgraded to F0B6, then I flashed the full image again and everything updated to F0B6. So far everything else seems to be good.
I'm thinking about flashing the full image and factory reset. Can anyone confirm twrp recovery is working, and root can be obtained after full re-flash? Thanks.
kgptzac said:
I'm thinking about flashing the full image and factory reset. Can anyone confirm twrp recovery is working, and root can be obtained after full re-flash? Thanks.
Click to expand...
Click to collapse
I was not able to get twrp to stick. Odin said it was done but never actually booted to twrp just the stock recovery came up. To root this is what I did:
1) be on lollipop update via Ota
2) flash cf auto root via Odin
3) reflash ob6 recovery that @toastido so graciously provided.(for some reason cf auto root reflashes nk3 recovery and my phone would not boot hence why I had to flash ob6 recovery)
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
balistic2 said:
Hey Joe, your link about the info is broken. Also your 'click source' on #2. is not a link.
Click to expand...
Click to collapse
Fixed!
koop1955 said:
I think that this is the link: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
If I read Chainfire's notes correctly, this is only for systems running Marshmallow, which would let us out for a while. But....
Once Samsung updates our OS to Marshmallow or they get CM 13 working on our phones (currently a work in progress) this could allow us to use Android Pay on a rooted phone.
Click to expand...
Click to collapse
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
JoeFCaputo113 said:
I do not believe it is MM only bc it's posted in the international S6 general forum too (and they obviously aren't on MM yet either).
Click to expand...
Click to collapse
I wasn't sure if CM13 is already working on International phones.
I only know what I read....
From Chainfire's post:
Rooting procedure:
- flash/upgrade to Marshmellow
- flash modified boot.img
- flash/boot TWRP and sideload latest...
Joe, be careful if you try this. Looks like you need to Odin back to stock.
Does this still void knox?
1619415 said:
Does this still void knox?
Click to expand...
Click to collapse
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
koop1955 said:
That is the key question. Also, would Google detect the phone as being rooted.
For the Knox part, someone with a "virgin" phone would need to test. Both Joe and I have already rooted using the current method, so Knox is already tripped.
Click to expand...
Click to collapse
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
1619415 said:
Seems to work on Note 5, just flashed TWRP with ODIN and then flashed SuperSu and there is no text while booting
---------- Post added at 09:19 PM ---------- Previous post was at 08:29 PM ----------
Thank you for posting this, now we have a method of rooting that A: Does not require custom kernels #Marshmallow and B: May not trip Knox
Click to expand...
Click to collapse
Well Merry Christmas!
JoeFCaputo113 said:
Well Merry Christmas!
Click to expand...
Click to collapse
You to
---------- Post added at 01:52 PM ---------- Previous post was at 01:01 PM ----------
Has anyone tried rooting with this method and trying samsumg pay?
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
todivefor said:
Decided to give this a try. Odin flashed OL1. Booted OL1 with no problem. Odin flashed TWRP, without reboot. Rebooted directly into TWRP and flashed SU beta 2.65. It booted without problem with root access. When I go into SU, it says there is an update available, but I just cancel out.
I was hoping android pay would work as I could never get it to work except stock unrooted. I started android pay and got the message "android pay cannot be used." I realized I needed to unroot in SU. I did that and still get the same message.
EDIT: Tried it again. Odined OL1, rebooted and android pay worked fine. Odined TWRP, booted into TWRP, fine. Rebooted into rom, bootlooped at Samsung logo, over and over. Rebooted into recovery and flashed SU 2.65. Rebooted into rom with no problem. Android Pay no longer works.
Click to expand...
Click to collapse
Try Number 15
1619415 said:
Try Number 15
Click to expand...
Click to collapse
Thanks. Been there done that.
Sent from my SM-T710 using Tapatalk
For those asking about whether this root method trips knox or not. Yes this will trip knox. Anytime you use odin to flash non official Samsung firmware/software then it forever trips knox. Therefore flashing any custom recovery will absolutely trip knox... forever.
Samsung and Android pay apps will not work on rooted devices. Period. The pay apps are intended for official factory software for obvious reasons. Security is the main focus with these types of apps that deal with your personal banking/credit card information. Hence a rooted device is not considered "secure".
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
yaibakt said:
using this method and my S6 is rooted without custom kernel which i prefer.
however, it seems like i cant use titanium backup to restore any backed up apps. Titanium app just runs endlessly.
Click to expand...
Click to collapse
Try installing/updating busybox and try removing titanium backups root access them regrant it
JoeFCaputo113 said:
**IGNORE POST #1 ONLY FOLLOW POST #2-#4!!!**
Info and DL on SuperSU v2.6x and Systemless Root
1. MUST flash a 100% stock (Odin) firmware.
2. DL SuperSU v2.6x
3. Install custom recovery
4. Install new SuperSU zip
5. Let it run through the process then reboot.
Click to expand...
Click to collapse
Nice work will give this a go soon.
1619415 said:
Try installing/updating busybox and try removing titanium backups root access them regrant it
Click to expand...
Click to collapse
thank you. ill give it a try. :good:
This may be a weird question, but we don't have a stock kernel to flash. Would there be a way to make a zip of a stock kernel and then use this to get root? I'd like to have a custom ROM but with the stability of a stock Kernel. This is the first phone I can think of that I've owned that didn't have a stock kernel with root.
Any idea what's in the new update that's rolling out?
Sent from my SM-N910V using XDA-Developers mobile app
My mom was also pushed an update yesterday. Havnt read anything about it yet
Darca said:
Any idea what's in the new update that's rolling out?
Sent from my SM-N910V using XDA-Developers mobile app
Click to expand...
Click to collapse
Looks like a security update but thanks for the heads up. If you are unlocked and rooted I made a safe upgrade to PJ2. I removed aboot and the stock recovery so it's safe to flash.. Grab it here if you want to flash it with Odin. This is stock so you will need to flash supersu after it reboots to recovery mode and then after you reboot you will need to remove the OTA updater and bloat.
EDIT: Here is the update for the Non Rooted Retail version DO NOT flash this if you want to stay rooted and unlocked!!
View attachment 3964458
Misterxtc said:
Looks like a security update but thanks for the heads up. If you are unlocked and rooted I made a safe upgrade to PJ2. I removed aboot and the stock recovery so it's safe to flash.. Grab it here if you want to flash it with Odin. This is stock so you will need to flash supersu after it reboots to recovery mode and then after you reboot you will need to remove the OTA updater and bloat.
EDIT: Here is the update for the Non Rooted Retail version DO NOT flash this if you want to stay rooted and unlocked!!
View attachment 3964458
Click to expand...
Click to collapse
I took the update over-the-air on my unrooted Note 4 and the IR Blaster stopped working. The phone was only a week old and I I'm sending it back to eBay for a refund. Did anyone have any problems with their IR blaster?
doctor-cool said:
I took the update over-the-air on my unrooted Note 4 and the IR Blaster stopped working. The phone was only a week old and I I'm sending it back to eBay for a refund. Did anyone have any problems with their IR blaster?
Click to expand...
Click to collapse
Bummer, I haven't had a problem with mine.
Misterxtc said:
Bummer, I haven't had a problem with mine.
Click to expand...
Click to collapse
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.
doctor-cool said:
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.
Click to expand...
Click to collapse
I noticed that too and do not like it. I didn't mod it at all other than removing the stock recovery and aboot. Now I wonder if removing the stock recovery is causing the issue... I'll make a new one with the stock recovery and see if that fixes it.
doctor-cool said:
I used Odin to flash your PJ2_Stock_Restore on a different/ rooted note 4 and it worked. Only thing was it put that quick connect drop down in the notifications. I re-flashed your PJ2_Stock_Restore using FlashFire, System and Cache only and it removed the drop down. I don't know why? So it worked both ways but I liked the results better with FlashFire.
Click to expand...
Click to collapse
I'm pretty sure not adding the stock recovery added the quick launch. Here is another with the stock recovery, I tried it and didn't have the quick connect after a factory reset.
VZW_PJ2_DEV_ED_Stock_Restore
Misterxtc said:
I'm pretty sure not adding the stock recovery added the quick launch. Here is another with the stock recovery, I tried it and didn't have the quick connect after a factory reset.
VZW_PJ2_DEV_ED_Stock_Restore
Click to expand...
Click to collapse
I had also taken out the recovery from the one you posted above, but I didn't get the quick connect in the notification drop down. I wonder if the csc isn't getting added. When I was playing around with the data fixes I noticed that if you take the customer.xml out of the mix it changes a bunch of stuff and adda that quick launch.
My wife is using this phone on the Rogers network up here in Canada. Other than being carrier unlocked, it is completely stock. I know that before she inherited it from me, I had manually updated it a couple of times with the stock recovery.
Although it was two phones ago, I'm sure I can figure out how to update with these latest patches. Can someone please tell me which, if any, of the above listed links can be safely used to update the phone with the stock recovery without root or tripping knox?
Any help would be greatly appreciated..
crutzulee said:
My wife is using this phone on the Rogers network up here in Canada. Other than being carrier unlocked, it is completely stock. I know that before she inherited it from me, I had manually updated it a couple of times with the stock recovery.
Although it was two phones ago, I'm sure I can figure out how to update with these latest patches. Can someone please tell me which, if any, of the above listed links can be safely used to update the phone with the stock recovery without root or tripping knox?
Any help would be greatly appreciated..
Click to expand...
Click to collapse
If it's the 910V use this file if you are NOT and will not be rooting or flash this one if you rooted and unlocked. Do a factory reset after you flash either of these with Odin.
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Old Dude said:
Here is what I did from stock 5.1.1 on a rooted verizon Note 4 (Using PaulPizz MMB29M.N910VVRS2CQB2):
Using Oden I installed:
VRS2CQB2_modems.tar.md5
VRS2CQB2_Bootloaders_NoAboot.tar.md5 and
VRS2CQB2_NoAboot.tar.md5
The phone boots into 6.0.1 (Kernel 3.10.40) and I have access to TWRP, ADB, ODIN, and root.
Paul suggested "You need to update your aboot partition to 6.0.1. the wifi driver is in the new aboot"
I am a noob and I don't understand what this means. Can anybody give me a list of steps to follow? I think I might be in over my head and returning to stock 6.0.1 might be acceptable.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Old Dude said:
dhplap, I appreciate the link to a different process but there seems to be too much assumed knowledge for me to try again (like what am I supposed to do with a .7z file). I am afraid I'm gonna brick the phone. I have flashed back to stock 5.1.1 (BPA1), verified the WiFi was working again and then flashed the stock CQC1 ROM from SamMobile. I really just wanted to get the latest security patches and have found a way to do that. My CID is still 150100523231384d4100657e54fc1200 which may be helpful in the future.
I am done for now with custom ROMs. I may take another swing at it when I have more time to educate myself. You may close this thread. My sincere thanks for your help.
Click to expand...
Click to collapse
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
mojoswagger1980 said:
You need to either flash the stock mm or lp rom you lost your WiFi do to the fact that your device while I'm certain it says 6.0.1 is in all reality 5.1.1 with the toolchain updated to mm . If you want a stock system with working radio Odin the stock firmware either api works
Click to expand...
Click to collapse
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
dhplap said:
He did flash stock mm. It was the last thing he flashed according to his list. He needs to upgrade his bootloader to mm.
Click to expand...
Click to collapse
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
mojoswagger1980 said:
What ? Your High champ he said he flashed w/o aboot. That's the safe upgrade if he had flashed stock the bl would have updated itself
Click to expand...
Click to collapse
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
dhplap said:
First of all your wasted. If he flashes stock mm he will lose root and lock his bootloader again and have to go back to bpa1 and start all over. Hence upgrade bootloader. Or he could stay on lollipop.
Click to expand...
Click to collapse
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
mojoswagger1980 said:
He did lose root bud he wants to. If u followed the thread to this point u would know that. You read the first and last post and your responses show that .
Click to expand...
Click to collapse
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
dhplap said:
I guess we both missed that he already flashed the stock bpa1 already. I just went off of you telling him to flash stock after he said he already did it. Have a good day bud!
Click to expand...
Click to collapse
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
mojoswagger1980 said:
No u missed it . I was telling him the radio is in the bl he didn't flash . IDK what u we're suggest but at least don't actlike this is mutual in any way . We Aren't disagreeing on Minor details.
Click to expand...
Click to collapse
That's for sure. Read the second post buddy. That's what he needed to do to update his bootloader and keep root if he wanted too, or he could have just flashed a lollipop rom. Understand or no? Sorry, can't play with you anymore right now, gotta go to work. I'll be back later though if you have any questions.