I just picked up my Note 4 and have not even turned it on yet.
I have a few questions after reading various multi-page threads that i am unclear on.
I was looking at the threads and see that ChainFire is what to use to root.
http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
It states that Stock Recovery is installed, does this mean that I can use that recovery to flash TWRP or will i have to use ODIN for that?
What version of ODIN needs to be used?
Is there any version of Root that does not trip KNOX?
I am confused about the different boot loaders / Broadbands (basebands?).
How do I find out what boot loader / Broadband i am on?
I am reading a lot of reports that 5.x is giving very poor battery life. Is that the Case Still?
Thanks for any help Ya'll can give.
You're gonna have to open her up to see what's I under the hood just don't let it update.
Depending on what build you find, CFAutoRoot is fine to root with up until OG5.
If it has OB7 or less, you can Odin back to KitKat NK2. Don't even try if is above OB7.
OG5 would require Beastmode kernel with exploit to root but you still need to flash SuperSU zip for that OG5 to root once the kernel is flashed.
Sent from my SM-N910P using Tapatalk
Android is 4.4.4
Baseband N910PVPU1ANK2
what other information do you need?
Dragonfyr said:
Android is 4.4.4
Baseband N910PVPU1ANK2
what other information do you need?
Click to expand...
Click to collapse
You're options are wide open, so what I tell you depends on you want.
NK2 is KitKat. You can root and install Xposed or flash a custom NK2 ROM and run Xposed. KitKat does better on battery all around. Kernel can be permissive or enforcing. You can run Xposed on either Odex or deodexed ROM. Lollipop requires mods to run enforcing kernel for some apps to work and Xposed only works on deodexed ROMs.
If you prefer lollipop, I'd need more feedback to advise your best options. Xposed is limited to 5.0.1 deodexed only. If you want to retain the capability to return to KitKat, you'd want the OB7 bootloader if going that far.
Most likely, to root, you can use Odin 3.07 or the latest. Use CFAutoRoot for root. For TWRP, you could Odin or use apps like Flashify or TWRP manager to install TWRP. Once you have TWRP, make a nandroid backup and then you can flash a custom NK2 ROM.
Going to lollipop would require Odin to OB7 stock tar (most likely; because you're one of the lucky ones with bootloader and KitKat as well- although OB7 is almost as good and can be reverted to KitKat).
Maybe that answered your questions and can get you started. It's ok to ask again before you start to be in the know before making a mistake.
Edit: if you settle on a lower build, you can avoid the update prompts by deleting /cache/fota folder.
Sent from my SM-N910P using Tapatalk
Thank You so much for the information
I will stick with KK for now.
How can i tell what Boot Loader i have?
Dragonfyr said:
Thank You so much for the information
I will stick with KK for now.
How can i tell what Boot Loader i have?
Click to expand...
Click to collapse
If you using a stock build.prop, it's listed as build in About device.
Galaxy Tools will tell you for sure on a custom build (sometimes build gets replaced by developer name of ROM).
Sent from my SM-N910P using Tapatalk
how do i stop the software updates?
i already have system updates turned off
Dragonfyr said:
how do i stop the software updates?
i already have system updates turned off
Click to expand...
Click to collapse
Root Explorer
System/priv-app/SprintDM.apk
Remount system folder as Read/Write
rename to SprintDM.apk.bak
Remount to Read only
Reboot phone
thank you any ideas as to what its trying to download?
Dragonfyr said:
thank you any ideas as to what its trying to download?
Click to expand...
Click to collapse
Lollipop OTA
xxSTARBUCKSxx said:
Root Explorer
System/priv-app/SprintDM.apk
Remount system folder as Read/Write
rename to SprintDM.apk.bak
Remount to Read only
Reboot phone
Click to expand...
Click to collapse
Renaming that file did not work,
When i go to WiFi it starts a Software update automatically
Dragonfyr said:
Renaming that file did not work,
When i go to WiFi it starts a Software update automatically
Click to expand...
Click to collapse
Did you uncheck the first box in System update, and leave the second one checked?
yes
id also goto Recovery and Wipe Dalvik Cache and cache.
When my phone starts up after a reboot.. that will appear initially after it connects to WiFi.. but the Important thing is that it Goes Away and isnt downloading the OTA and then throwing the Install Screen in your face.
Can you verify that after a restart(or after the one you just did) that after it connects to WiFi... it will appear.. but then goes away and nothing else appears saying that its downloading the Update? If so, thats what you want to happen.
I did wipe both caches
it keeps saying software update downloading, i let it run for about a minute before i killed the WIFI
Dragonfyr said:
I did wipe both caches
it keeps saying software update downloading, i let it run for about a minute before i killed the WIFI
Click to expand...
Click to collapse
If you're rooted, use a root browser and navigate to /cache, open and long-press fota folder; delete. No more update.
Edit: KitKat is /data/fota
Lollipop is /cache/fota
Sent from my SM-N910P using Tapatalk
there is no /cache/fota folder i can locate
there is a /data/data/com.localfota folder
There is also a /data/FOTA folder that contains update.zip
Dragonfyr said:
there is no /cache/fota folder i can locate
there is a /data/data/com.localfota folder
There is also a /data/FOTA folder that contains update.zip
Click to expand...
Click to collapse
delete that
xxSTARBUCKSxx said:
delete that
Click to expand...
Click to collapse
Deleting the update.zip and restarting just caused it to start downloading again.
Dragonfyr said:
Deleting the update.zip and restarting just caused it to start downloading again.
Click to expand...
Click to collapse
I was waiting for that post.. SprintSyncMLSvc.apk .bak that file too, shouldnt have to but in your case, that needs a .bak at the end as well
Related
I've read as much as I can and I just need a little more help. I want to be able to root my T-Mobile Galaxy S3, SGH-T999.
1. Is there any other way to pull files from /data/data without rooting?
2. Can I just do a simple root and then later root with CWM or TWRP using another option?
3. I thought rooted was rooted, what is the need for "insecure boot"? Is that the only way to get a file image backup of my partitions?
4. None of the rooting options in the Skipsoft Android Toolkit wipe the device, correct?
5. Is the only way to be able to "recover" back to stock by installing a "custom recovery"?
All of the options include "custom recovery". What if I just want to root the device and install a custom recovery later? Or it custom recovery included in all the options so I can get back to stock if I mess up? Thanks!
I am not sure why you'd need to go to such extent.
By your question on Insecure Kernel, I assume, you have Stock 4.3 update. If so, please flash SuperSU Zip via Custom Recovery. You can Also flash Root66 of 4.3 (UVUEMJC ) to get Root as well. None of these methods are destructive and make you loose your data.
As to your other questions, /data/data should be accessible read only to Good File explorers such as ES File Explorer. My Backup Pro should be able to backup those files too. Insecure boot is needed to root as SELINUX Enforcing will not let you have Stable Root. Best Flash ATT Insecure Kernel Posted on this sub forum. I don't understand what you mean by "Recover to Stock".
can't do anything without root
I tried ES File explorer and 2 others, they show /data/data as blank. Most everywhere I've looked says you have to have root
In that case please post your Current Android version and what you see under Baseband. What step we take next depends on this information.
rooting galaxy
perseus71 said:
in that case please post your current android version and what you see under baseband. What step we take next depends on this information.
Click to expand...
Click to collapse
4.3, t999uvuenc2
fdecker said:
4.3, t999uvuenc2
Click to expand...
Click to collapse
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.
Thanks!
jmberumenb said:
Root 66 Will not work you will need Auto Root, CWM/TWRP and Update SuperSU for a complete root.
CF-Auto-Root-d2tmo-d2tmo-sght999.tar
openrecovery-twrp-2.7.0.0-d2tmo
UPDATE-SuperSU-v1.93
DE-SAMSUNGNIZER_KNOX_REMOVAL_SCRIPT_V1.0
For a suceed root and Knox remove.
Click to expand...
Click to collapse
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!
fdecker said:
Thanks, this is great. I rooted the same model phone that was on OS 4.1.2 by uploading root66 with Odin and it worked in one step. I see now that root66 is not the way to go on the 4.3 phone just yet. I will follow your tips. I see too that I have to get rid of Knox and make sure the recovery partition does not get reset. Think I should put busybox out there too, or with TWRP and SuperSU do I have all I need?
Thank you very much for your help!
Click to expand...
Click to collapse
I used the TWRP and SuperSU method no problems so far.
TWRP and SuperSU
jmberumenb said:
I used the TWRP and SuperSU method no problems so far.
Click to expand...
Click to collapse
I'll give that a try then.
busybox?
One last question: Would you load busybox as well?
fdecker said:
One last question: Would you load busybox as well?
Click to expand...
Click to collapse
Nah I wouldn't unless its required by your Rom or something.
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.
Hi,
I got a new update today.
No, it is not android L
It said VoLTE improvement and updated stability.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
If you already updated over OTA to NK3 and want to root without tripping Knox - Use Odin desktop to flash the kernels. It goes in the bootloader section in Odin.
1) Flash the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Use Towelroot - get it from www.towelroot.com
3) Flash the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0.
For some reason, I am unable to open the file. is it always like that? Or did it not download properly?
UPDATE: It flashes correctly - it is just a CSC update.
But: flash at your own risk. I am neither responsible nor probably knowledgeable enough to help you if you brick your phone.
I'll do my best though
I wouldn't be surprised if T-Mobile didn't document a newly locked bootoader and the ability to block rooting while disguising this as just a VoLTE update.
Edit: The download is corrupt on my end too.
Anonymously_Unknown said:
I wouldn't be surprised if T-Mobile didn't document a newly locked bootoader and the ability to block rooting while disguising this as just a VoLTE update.
Edit: The download is corrupt on my end too.
Click to expand...
Click to collapse
Took the plunge. Copied it to the cache folder, selected survival mode in SuperSU and updated.
It is just a CSC and Multi-CSC update. Updated successfully, root intact, Knox still 0x0.
It says cant open from PC and phone file explorers. But while updating, it says footer failed (or something like that) for system, kernel etc.
But for CSC and MULTI-CSC, it says successfully updated.
Steps to update: (I am not responsible for anything that happens)
1) SuperSU -> Settings -> Survival Mode (Not sure if necessary, since it only updates the CSC. I did it for safety)
2) Copy file to device (I copied in original cache/FOTA location)
3) Reboot to recovery (stock)
4) Apply OTA update from cache
5) Select the correct file in the cache/FOTA (or wherever you copied) folder
6) After it completes update, press any key to go back to recovery menu -> restart
7) Verify and enjoy.
CravingMender9 said:
Took the plunge. Copied it to the cache folder, selected survival mode in SuperSU and updated.
It is just a CSC and Multi-CSC update. Updated successfully, root intact, Knox still 0x0.
It says cant open from PC and phone file explorers. But while updating, it says footer failed (or something like that) for system, kernel etc.
But for CSC and MULTI-CSC, it says successfully updated.
Steps to update: (I am not responsible for anything that happens)
1) SuperSU -> Settings -> Survival Mode (Not sure if necessary, since it only updates the CSC. I did it for safety)
2) Copy file to device (I copied in original cache/FOTA location)
3) Reboot to recovery (stock)
4) Apply OTA update from cache
5) Select the correct file in the cache/FOTA (or wherever you copied) folder
6) After it completes update, press any key to go back to recovery menu -> restart
7) Verify and enjoy.
Click to expand...
Click to collapse
Interesting - any difference in About Device screen in Settings? Perhaps share a screenshot? Just curious
dwitherell said:
Interesting - any difference in About Device screen in Settings? Perhaps share a screenshot? Just curious
Click to expand...
Click to collapse
Don't see any difference. VoLTE was working fine anyways.
new update
I just updated too and mine shows the last numbers now of my version as NK3? I have looked to find anything about this update but havent had any success. The latest update i can find any information on is NF9. I do not really see any significant changes to anything UI wise at least but i did just finish the update bout 15 mins ago.
stlstyles said:
I just updated too and mine shows the last numbers now of my version as NK3? I have looked to find anything about this update but havent had any success. The latest update i can find any information on is NF9. I do not really see any significant changes to anything UI wise at least but i did just finish the update bout 15 mins ago.
Click to expand...
Click to collapse
Yep, that sounds right then.
Not much info, but a little is found here anyway.
Update
dwitherell said:
Yep, that sounds right then.
Not much info, but a little is found here anyway.
Thanks bud, i was looking for confirmation that this was a legit build version or if i messed some stuff up. This was the first time i have done an update. I rooted it first hour i had it and havent done any updates because i didnt want to mess with it. I went from NB4 to this NK3. I was expecting to end up on NF9 and was pretty surprised seeing NK3 after it was finished. lol Then googled it and found nothing out there referring to this version, so i was a bit confused.
Click to expand...
Click to collapse
dwitherell said:
Yep, that sounds right then.
Not much info, but a little is found here anyway.
Click to expand...
Click to collapse
This is weird. I did the update and it is still NF9.
The funny thing is, the update page on TMobile says that T-Mobile Free Inflight Texting has been added as a new feature. I already had that. I have used it multiple times in flight.
Sammobile has it now. Looks more than just a csc.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
toastido said:
Sammobile has it now. Looks more than just a csc.
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
Click to expand...
Click to collapse
correct.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
I think I got a corrupt OTA. I had to recover using KIES, lost root.
Re-rooted again:
1) Flashed the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Used Towelroot from www.towelroot.com
3) Flashed the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0. Also updated OP. I only created the kernel for this, since that is all I needed and was in a hurry.
Can you do the remaining files for anyone else who wants it? As you always do an excellent job on that
CravingMender9 said:
correct.
Full firmware is available in sammobile: http://www.sammobile.com/firmwares/confirm/39231/N900TUVUENK3_N900TTMBENK3_TMB.zip/
I think I got a corrupt OTA. I had to recover using KIES, lost root.
Re-rooted again:
1) Flashed the NE6 kernel from here (http://www.mediafire.com/download/q7ri06fz1762zy3/N900TUVUDNE6_KERNEL.tar.md5)
2) Used Towelroot from www.towelroot.com
3) Flashed the NK3 kernel back (http://www.mediafire.com/download/t52121ld63gen6r/nk3_kernel.tar.md5)
This is what I did to get root with knox 0x0. Also updated OP. I only created the kernel for this, since that is all I needed and was in a hurry.
Can you do the remaining files for anyone else who wants it? As you always do an excellent job on that
Click to expand...
Click to collapse
Yeah it's downloading. I'll have the parts up either later tonight or tomorrow. [emoji6]
Sent from my leanKernel 3.12 powered stock 4.4.2 (NF9) SM-N900T
New baseband available?
davwman said:
New baseband available?
Click to expand...
Click to collapse
Here:
http://www.mediafire.com/download/qqng1iw2pzfijhu/modem.bin
can someone provide new OTA File only ?
CravingMender9 said:
Here:
http://www.mediafire.com/download/qqng1iw2pzfijhu/modem.bin
Click to expand...
Click to collapse
Did it have a new NON-HLOS.BIN too? Was getting ready to make a new odin file and saw that file in there from previous update.
NMonster69 said:
Did it have a new NON-HLOS.BIN too? Was getting ready to make a new odin file and saw that file in there from previous update.
Click to expand...
Click to collapse
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin
CravingMender9 said:
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin
Click to expand...
Click to collapse
Can non-hlos.bin be flashed in mobile Odin?
CravingMender9 said:
Here: http://www.mediafire.com/download/7e8elhtsyakbvtz/NON-HLOS.bin
Click to expand...
Click to collapse
I made an odin file using your two files. If anyone wants it let me know.
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Will this process work on the Galaxy s5 with og5 5.11
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Dmary said:
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk
So, its been about a year since I rooted a phone, but I feel like I'm missing something at the beginning of the instructions. In the video
https://www.youtube.com/watch?t=32&v=k2oOvf5tOCY
it goes over the auto root process, but that hasn't been updated. Is that something I need to run first anyway? Wouldn't it not work due to the mismatch of android version?
Oh, never mind. It froze at the TWRP screen, but a restart fixed that.
I would like to know if it's possible on the S5 as well...G900V...Everywhere i've read says it's not.
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
When I try to flash twrp, odin says failed. Any suggestions?
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Newbie_from_NJ said:
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Click to expand...
Click to collapse
TWRP is fine for most. Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
If you decide to flash a custom ROM and get a binary failure, reboot recovery and try again.
Sent from my SM-N910P using Tapatalk
samep said:
Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
Click to expand...
Click to collapse
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Newbie_from_NJ said:
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
From power off, Vol+, Home + Power.
Sent from my SM-N910P using Tapatalk
I am also curious about whether this would work on a G900V.
Anyone try this on their 920v????
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Could you please reply about G900V? I would greatly appreciate it.
AcidBurn22 said:
Could you please reply about G900V? I would greatly appreciate it.
Click to expand...
Click to collapse
I sent the PM to not clutter this thread with off-topic discussion.
Sorry, I don't have this phone, nor have I rooted one.
If you need help or don't know where to start, I'd suggest reading thread below before asking in thread:
http://forum.xda-developers.com/showpost.php?p=61688768&postcount=1
Reading through the OP's threads, the same thing started at OE1 update that started here, you can no longer downgrade in Odin once taking this one and later updates; it progressively worsens. Regarding your carrier, it appears that root prior to OG5 update is a prerequisite as well as steps to keep root in the update process (those do not apply here). But I don't claim to know any more about it than you so read, search and ask in the appropriate thread. Best wishes for success; perhaps it's not as grim as I describe it. I only researched a few minutes, following closed threads to links to next thread, starting here:
http://forum.xda-developers.com/showpost.php?p=61682294&postcount=242
If you have a choice, don't take the OE1 update until you're rooted and clear on how to keep root through updates. But again, I'm not claiming to know any more than yourself, possibly less with the effort I gave.
Anyone else finding this through search, please keep this thread on topic. Refer to your specific thread regarding phone model and carrier. Thanks.
Sent from my SM-N910P using Tapatalk
DaggettBeaver said:
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Click to expand...
Click to collapse
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Reivaj1803 said:
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Click to expand...
Click to collapse
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I wasn't aware of the latest update, thanks for the heads up.
I have never tried Chainfire auto root. I found Chainfire post http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
I'll try this route.
Thank you sir, greatly appreciate it. ???
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Reivaj1803 said:
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Click to expand...
Click to collapse
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
samep said:
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually did remove and disabled most the apps that I was able to. The rest there were not options, other than root.
My preference was to root, maintain OTA capabilities and remove the bloatware.
What option/s would best suit that preference?
Running lolli 5.0.2 on my 8.4 Tab S. I'm rooted with CF Auto with TWRP recovery. Can someone please tell me what this OTA they're trying to push on me will take me to. I'm guessing I'll probably lose root if I go ahead and let install. If I do , can I just reroot with CF combined with TWRP again? I remember that there's a way to disable this OTA by deleting or editing a file or two and I'm searching for that. Appreciate any feedback.
BoJatey said:
Running lolli 5.0.2 on my 8.4 Tab S. I'm rooted with CF Auto with TWRP recovery. Can someone please tell me what this OTA they're trying to push on me will take me to. I'm guessing I'll probably lose root if I go ahead and let install. If I do , can I just reroot with CF combined with TWRP again? I remember that there's a way to disable this OTA by deleting or editing a file or two and I'm searching for that. Appreciate any feedback.
Click to expand...
Click to collapse
The OTA file is found in your /cache directory so obviously you need to use a file manager with RW privileges to / or the one in TWRP to delete the OTA file. Before deleting uncheck Settings - About - Software - Updates - Auto update. As you have likely altered the contents of your /system partition the OTA may fail to apply as it does a detailed check of that partitions contents before it applies changes.
Once you are rooted and OTAs fail then you can use Flashfire to selectively update the boot and system images from the latest firmware for your device but any changes to /system will need to be reapplied. Flashfire will re-root your device during the upgrade. By being selective in which images from the firmware you apply you preserve recovery and userdata.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
The OTA file is found in your /cache directory so obviously you need to use a file manager with RW privileges to / or the one in TWRP to delete the OTA file. Before deleting uncheck Settings - About - Software - Updates - Auto update. As you have likely altered the contents of your /system partition the OTA may fail to apply as it does a detailed check of that partitions contents before it applies changes.
Once you are rooted and OTAs fail then you can use Flashfire to selectively update the boot and system images from the latest firmware for your device but any changes to /system will need to be reapplied. Flashfire will re-root your device during the upgrade. By being selective in which images from the firmware you apply you preserve recovery and userdata.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
The ota.zip was in my fota folder. Deleted it and unchecked auto update like you said. I'm gonna leave it like this as some of that other stuff mentioned is a little over my head. Will check out flashfire but unsure which version to look at as they have a couple of betas. Thanks for your help.
BoJatey said:
The ota.zip was in my fota folder. Deleted it and unchecked auto update like you said. I'm gonna leave it like this as some of that other stuff mentioned is a little over my head. Will check out flashfire but unsure which version to look at as they have a couple of betas. Thanks for your help.
Click to expand...
Click to collapse
Right now Flashfire is in beta so the Dev (Chainfire) includes software which forces you to always use the current version. That helps him with support, so you need to use the latest version of flashfire the previous versions have expired. Join Chainfire's Google+ group for Flashfire for links and news. You should also read what Flashfire does by following its XDA thread.
Sent from my SM-T800 using XDA Premium HD app
You could have flashed that OTA with FLASHFIRE and kept root.
ashyx said:
You could have flashed that OTA with FLASHFIRE and kept root.
Click to expand...
Click to collapse
Still may get a chance to do that. Even though I deleted update.zip from my data/fota folder and unchecked auto update in settings, there's the annoying reminder when I turn back on that update has been downloaded and is ready to be installed. Except now there is no update.zip or I can't find it. Did a search with root explorer and turned up nothing. Tempted to go ahead and touch install and see what happens. It may abort because there is no update file now but if there is I would much rather take your advice and flash it with flashfire if I can find it. Would be happy just to get rid of the pop up.