Develop Bugs

[Solved] Need help with installing Cyanogenmod (Without a PC if possible)

Hi all, new to all of this. Please keep this in mind as you read this thread.
Well first of all I have been reading about Cyanogenmod and how it helps saves battery. I also wanted to use cputuner to overclock my phone a little. I have in the past rooted this phone and installed cputuner not knowing that it could damage your phone if you didn't have a custom kernel that supported overclocking. After I found that out I uninstalled it and unrooted in fear of damage to my phone. Anyways I have a few questions and was looking knowledge, resources, and help about a few things.
Questions:
Is installing a custom rom and things needed to install a custom rom possible with a PC?
Can I safely reroot my device since I unrooted through #SU?
What do I need to do besides reroot my device in order to install a custom rom? (Cyanogenmod)
Thanks in advance!
Other INFO:
My device is a Samsung Galaxy S3 I-747
Firmware 4.4.2 KitKat
Device was rooted before using towelroot but I unrooted using #SU.
.

Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app

jason2678 said:
Ok. To install cm with no computer use, I'd say the easiest way would be to get root again with towelroot. Then install flashify from the play store. use flashify to install a custom recovery. I prefer TWRP.
Next download cm rom and Gapps. Follow the installation instructions for the rom. Generally that's boot into recovery, wipe dalvik, cache, system, and data, flash rom, flash Gapps, then reboot. You can do this from the internal SD, it won't erase that when you wipe. However, an external SD can be really handy for getting out of a jam.
If you haven't done it, a little research on the forums here about backing up your efs might be in order before flashing roms. Hope you never need it, but it could make life easier someday.
Read, read, read the forum here. This was just a real brief overview. If you don't quite understand any part, it should at least help you with what to search to learn what you need to know.
Sent from my LG-V410 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!

KentuckyGuy447 said:
Thanks friend will look into it a little more. So is there a major risk of getting bricked or are chances slim? Also do you have any links to the Cyanogenmod version I'm looking for? I would like it to be 4.4.2, not 5.X.X. And I also need the appropriate gapps file. If you don't know I still thank you for the info friend!
Click to expand...
Click to collapse
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.

dawgdoc said:
Chances of bricking should be slim as long as you follow the instructions closely.
CyanogenMod 11 is based on Android 4.4.X, Kitkat. Nightlies can be found here or here.
Snapshot releases, sometimes called monthlies, can be found here.
There are options regarding Google Apps( GAPPS ) the choices from CM are here.
Some prefer the GAPPS packages provided by Paranoid Android, look here.
Click to expand...
Click to collapse
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.

KentuckyGuy447 said:
Thanks so much! Have been researching like crazy and odds seem pretty good. Problem is I've hit a ditch headfirst. I can't reboot using towering because I updated my kernel sometime through the period when my phone was unrooted (idk when or how this was done.) The date is apast june the 3rd and i read it won't work apast that date. Is there a workaround for this? I have no PC so I would like a non-PC method if possible. I just wanted to say I have tried all the modstrings for toweroot and still nothing.
Click to expand...
Click to collapse
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.

dawgdoc said:
The June 3rd date probably only counts if you took all of the OTA updates, okay rechecked your OP and I see that you are on NE4. I recall that either the NE4 or the NJ1 update patched the kernel to block TowelRoot. I take it when you say Firmware 4.4.2 KitKat you mean baseband, modem, and Samsung stock rom.
With SuperSu you can re-root using it, assuming you unrooted but did not remove the app. I don't know if the same applies to th SU app that comes with CWM. You could try. If you did go back to stock rom and properly formated you may no longer have su on your phone.
Yes, if you have a custom recovery on your phone you should be able to re-root without a PC. Search for the zip version of SuperSu, put it on an external sdcard, and flash it through the recovery. Without a custom recovery I'm not sure of other options not requiring root that do not involve a PC (Windows or Linux) or a Mac. Apps like Flashify require root, so will not work for you at the moment.
Click to expand...
Click to collapse
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.

KentuckyGuy447 said:
Thanks for the info, sadly I did uninstall #SU. Here is a ss of my modem info and such. I think it pretty much confirms I have the NJ1 version but I need you to confirm that.
Click to expand...
Click to collapse
I'm stuck.
You can install a custom recovery without having root, if you have a PC. You would use either Odin, Heimdall, or maybe adb.
You can install a custom recovery without a PC if you have root. You would use an app Like Flashify, Rom Manager, or Goo Manager (if it still exists).
You can flash a rom without a PC if you have a custom recovery, root is not needed.
Some roms, usually stock, can be flashed without a custom recovery if you have a PC.
I don't know the solution until you have access to a PC. I could see it being possible using a live USB with persistence of a Linux distribution, but you still have need for a PC. It's been a while since I created a live USB. The method I used required a small installation on the PC. so I don't see this as an immediate solution for you.

Oh sorry. I don't think towelroot works once you're on nj1, unless it has been updated.
If you get access to a PC, rooting is still fairly easy. You can use download mode and odin or heimdall to flash a custom recovery (be sure to uncheck reboot if using odin, or be really ready to pull battery). Don't let your phone reboot normally, you'll have to pull battery once odin is done.
Reboot to custom recovery, then flash supersu and you'll be rooted again, and set up to do whatever you want with your phone.
Sent from my LG-V410 using XDA Free mobile app

Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?

KentuckyGuy447 said:
Thanks all for your help. I have decided I'm gonna give C-F Root a try as it seems very easy, then use Flashify to get CWM. Correct me if I'm wrong but there's no boot loader for my model type right? Couldn't seem to find anything on the subject except the Verizon variant. I'm gonna still need help deciding which gapps to flash as I'm gonna flash the latest Cyanogenmod monthly build. Is there anything else to be aware of when using a new Rom?
Click to expand...
Click to collapse
excuse for butting in .... but if you dont know your bootloader/modem info. here is an app called 'samsung info' that should tell you.
your question "...... but theres no bootloader for my phone model right?" kinda worried me. its important to know because they should match AND trying to downgrade can brick your device. on the plus side ; i've never seen a custom ROM include bootloader/modem in it.
again , just a thought and not trying to butt in.:good:
https://www.dropbox.com/s/4ka74x02tg1rrn1/org.vndnguyen.phoneinfo-1.apk?dl=0
"all i can really do , is stay out of my own way and let the will of heaven be done"

As mrrocketdog stated, the Samsung Info app will tell you your bootloader and modem. If what you previously stated is correct, they should both be NJ1. You can get the same info by issuing these commands in a terminal emulator on the phone:
Code:
getprop ro.bootloader
and
Code:
getprop | grep version.baseband

Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.

KentuckyGuy447 said:
Appreciate the butting in! You may have just saved me from bricking my phone lol. Maybe I need to do a lot more research because that just lost me. So how do I tell that my phone is equipped with a boot loader? And if it is how do I disable it? I read that in order to flash a new Rom the boot loader must be disabled. (Correct me if I'm wrong) I'm no where near the point of flashing a new Rom (Cyanogenmod) but this is a great furniture reference to me.
Click to expand...
Click to collapse
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"

mrrocketdog said:
every phone has a bootloader , two if i'm not mistaken. the one you're concerned with comes already unlocked on the good 'ol S3. (i bricked my first s3 trying to 'unlock' the bootloader). just find out bootloader/modem version (see posts above) to make sure they match (to avoid issues later) and just dont ever try to downgrade.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
You have lifted a burden off my shoulders friend! Ever since I wanted to flash a custom Rom I've been worried if my phones bootloader was locked! I can now be at ease now that I know its unlocked. Will check upon that info about bootloader/modem.

Here is the info mrrocketdog

Is there a reason you can't use a PC to install a ROM?
I'm asking because I also do not know of a way to install a ROM without having root.
If you are able to root, you could try using the CM installer again.

audit13;5898140 said:
Thanks friend no worries, mrrocketdog helped me figure it out, than to all who helped!
Click to expand...
Click to collapse

KentuckyGuy447 said:
Here is the info mrrocketdog
Click to expand...
Click to collapse
Those are the latest versions of the bootloader and modem. You will be good for CM 12 or CM 11, and other custom ROMs based on CM. Older versions will work with them, but you probably need to edit the updater-script. (The older versions are not likely to include the NJ1 versions in the checks as they were not out when the ROMs were last updated.) NJ1 will also work with any of the ROMs based on the KitKat TouchWiz releases by Samsung.
As soon as you can find a PC to borrow you should be in business. Any chance of using one at a public library?

Appreciate all the help you gave me too friend, providing the links to cm and gapps, gonna borrow my friends laptop Sunday and try to root flash C-F Root through Odin. Thats the part that scares me but I should be good as people has confirmed it works for NJ1. Wish me luck friend. Would you recommend installing CM12? I personally like kit Kat and I know CM11 is based on that but is CM12 better? I guess its based on Lollipop

How to root after you take the OG5 OTA update

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?

5.1.1 root

hey...been here a while...did a quick search, but probably didnt look kard enough...ive always gotten good help here, so thanks in advance. just got a new note 4 through insurance and its on 5.1.1 and i was previously on, well not 5.1.1...so i need to root it. is it hard and could i get a good link? ...and sorry , but thanks again always gottwn good help here

There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk

i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it

tammyjustin said:
i just want to get started with root, so i can get titanium back-up installed and get my apps back,... from there just install an ad blocker and from there that would probably be it
Click to expand...
Click to collapse
The ad blocker, depending on choice may indicate you should go with method 2 or 3.
Adguard from XDA forum would work with method 1 but only works with the browser in free mode. I know that Adaway webserver wouldn't stay enabled with method 1, systemless root.
You may also consider using FolderMount from Google Play to enable write to sdcard if you keep your titanium backup folders on extSdCard. The app patches /system/bin/sdcard and /system/etc/permissions/platform.xml That app would also suggest method 2 or 3 for root.
Mostly stock your preference? Go with method 2. Only real limitation methods 2 and 3 yield us having to update with Odin or try the return to stock for OTA. In theory, return to stock with method 1 and full un-root may actually fix OTA update if attempt to return to stock and OTA update fails for dm-verity or unauthorized modification. No guarantees though. Rooting means we accept the possibility that we may have to wait for a stock tar to update. Best to wait for confirmation that root is possible and what is required first, anyway.
Edit: the minimum links to root with are end of method 2. The instructions for TWRP flash are actually in method 3. Flash the kernel and SuperSU zip in recovery once TWRP is booted.
Sent from my SM-N920P Note 4 via Tapatalk

yea, i mostly just want toot and stock.. so u suggest method 2...thanks...i hope the instructions are clear cut cayse its been a while since ive rooted, dont want toscrrw up

i use the beast mode kernal?

tammyjustin said:
i use the beast mode kernal?
Click to expand...
Click to collapse
You can choose other kernels for root but Beastmode is closer to stock and easy on battery, IMO.
But yes, starting in Android 5.1.1 for our phone, kernel with root exploit became necessary for root. Flash the kernel then SuperSU zips in TWRP recovery together and boot. Rooted stock.
Sent from my SM-N920P Note 4 via Tapatalk

so i odin... flash twrp, kernal then SU?

tammyjustin said:
so i odin... flash twrp, kernal then SU?
Click to expand...
Click to collapse
Correct. You did mean Odin the TWRP recovery and then in TWRP, flash kernel and SuperSU zips, right?
Sent from my SM-N920P using Tapatalk

correct

samep said:
There's actually 3 methods commonly used here with SuperSU superuser. Which applies to you?
1) Stock with Chainfire Auto Root for Note 4 (CFAR) has recently been updated to support Android 5.1 and possibly 6.0 It offers possibility to full un-root and take next OTA update but limits system and recovery to stock using systemless root. It's experimental, patches stock kernel and sort of fragile unless you avoid recovery flashes and mounting system. Custom recovery or mounting system may break the ability to return to OTA for update with full un-root but also, flashing custom recovery may trick you into applying system based SuperSU which would break root by loss of the stock kernel boot and root patch causing boot loop. Even flashing a SuperSU zip package may not help unless also flashing a custom kernel (kernel first). CFAR is not the method to use if wanting custom kernel, flash system mods, unofficial Xposed or custom ROM. You've rooted before so you most likely have your Samsung driver from Samsung mobile support for Note 4 SM-N910P and know to enable USB debugging in Developer mode.
Latest Odin
CFAR-follow OP in thread for instructions if this is best root method.
2) Rooting stock Odex by way of custom recovery and using modified custom kernel with SuperSU for root. It allows for some Odex modifications but not recommended Xposed due to the system .odex extensions making addition of system applications extra work. Have to remove the Wanam unofficial Xposed framework (the one required to use for stock) to install system application mods and reinstall unofficial Xposed. You could still use Odex ROM and Xposed, just use the unofficial Xposed as a finishing touch to your ROM. You could also backup before applying Xposed to restore later if you decide to make a system application change.
TWRP recovery
Beastmode patched kernel
SuperSU 2.52 beta
3) Flashing custom ROMs, usually deodexed which are more friendly with modifications, including Xposed only requires the custom recovery flashed in Odin with latest Odin with auto reboot option unchecked, USB and battery pull 30 seconds after success 0 fail message, and booting into recovery to flash the custom ROM per OP instructions. Watch these stock ROMs for systemless root (SuperSU version greater than 2.52 beta); you may have to swap kernel and SuperSU (together, in that order) if making a change to either.
Knowing what you want to use root for would help but the above may get you started or direct your next question.
Sent from my SM-N920P Note 4 via Tapatalk
Click to expand...
Click to collapse
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!

HarrisY said:
I am in kind of an odd position here. For some reason, I can't root my Note 4. I've tried both methods 1 and 2 you listed, but neither works. I am running 5.1.1, bone stock. I've been running the stock ROM for about a month since I got this phone used, upgrading from my old Note 3. This is really odd, considering I've been rooting/flashing ROMS since my first Android phone (HTC Hero) in 2010, and have had Samsung phones the last 4 years and never run into this issue. Currently, my phone shows that the beastmode kernel has been flashed, but SuperSU is not showing up and Root Checker is telling me I am not in fact rooted.
I really just want to root so I can WiFi tether, I don't mind running the stock Touchwiz ROM. It runs smoothly and I've had zero issues. Is my best bet just to Odin a stock .tar and start over? I'm trying to bypass having to backup a bunch of files. Normally CFAR would do the trick. Any suggestions are appreciated. Thanks!
Click to expand...
Click to collapse
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk

samep said:
Basically, attempting method 2 after method 1 breaks root. If you want method 1, you'd have to start over with Odin.
There are a couple of solutions to get method 2 to work if you're not interested in method 3. Method 3 would be the easier fix though.
Are you interested in some fixes for methods 2?
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.

HarrisY said:
I did it the other way around. I tried method 2 before method 1. I am definitely open to some fixes. However, if it requires a full wipe, I'd rather just backup and go with Odin/method 1 since I am already familiar with that method. Either way, I appreciate the help.
Click to expand...
Click to collapse
Yeah, they're not really that interchangeable as you've discovered. That is why I tried to differentiate the methods to choose a direction and stay the course.
Starting over with method 1 will possibly restore the OTA for update with full un-root. But no guarantee from me. But that's the only way to restore it with that possibility. Using the ##3282# method to get hotspot may break that. I'm not sure but I think flashing the zip in recovery would break that option for two reasons: flashing custom recovery and modifying system. It wouldn't break root, just nullify the reasons to use systemless root when the traditional method is more stable and you have to use Odin to update anyway.
I guess I omitted the hotspot only suggestion should most likely choose method 2? And updated CFAR isn't the traditional system based root we had in KitKat. It's strictly systemless root and experimental as far as Samsung Lollipop is concerned.
Sent from my SM-N920P using Tapatalk

QF1 Recommended thread/instructions for unlock bootloader/root/lollipop

I've been going through the learning curve on rooting/custom ROM/etc. This will be my first time to go through this process. I have the QF1 firmware and the latest version for Sprint Samsung Galaxy Note 4:
Software Version: N910PVPS4DQF1
Hardware Version: N910P.05
Model: SM-N910P
Android 6.0.1
security patch level: June 1, 2017
I tried calling Sprint to unlock my bootloader, but they thought I was asking to unlock the device. Finally, I got to their tech support and they said they didn't do that, and the guy recommended watching a video on YouTube.
It seems that sometimes the instructions you follow need to be oriented towards the version you have. Would anyone be able to point me to the best instructions to follow?
there seems to be a lot of contradicting information, so I thought some general direction to point me off in the right direction would save me a lot of grief in the long run
My thought was to:
1. unlock boot loader
2. using Odin flash a ROM with Lollipop for the Sprint Note 4, maybe the Omega one?
3. depending on the ROM in #2, then I could automatically get root?

Bootloader on Sprint Note 4 is unlocked already.
Custom ROMs usually include root or alternate methods.
Depending on the ROM you choose and as long as it's OG5 and above, it's recommended to use Odin to flash the stock tar that corresponds to the update that the ROM is based on. Otherwise, you may lose compatibility, network connectivity or camera focus.
Edit: you can find stock tar downloads in a thread for Sprint Note 4 in the general forum. Latest recommended Odin can be found in post 1 or 2 of that thread.
I'm not sure what ROM you're referring to but clean install is best practice for ported ROMs or switching between Android versions or switching to and from CM to stock based ROMs. Data may not be compatible so backing up internal memory keepsakes and wiping internal memory may be necessary, where recommended.
That's the general idea but best to follow OP of the ROM you choose.
Sent from my SM-N920P using Tapatalk

How would I go about making my own Custom Rom? I'm thinking of adjusting the Resurrection Remix So it would work on my phone but the specific ROM is on Verizon verison of the Note 4 and I want to port that for my Version for Sprint I know I can change some CSC stuff to get the modems and carriers ready for no signal loss or mobile data or sms issues as I have seen a method for flashing a zip file, but I;m just really curious, as I hope I can rebuild LineAgoe or CM for this Note 4 as I have a lot of time and alot of learning to do.

rayel said:
I've been going through the learning curve on rooting/custom ROM/etc. This will be my first time to go through this process.
Click to expand...
Click to collapse
To add to samep's comment. Here's a few pointers, in no particular order.
1. You only use Odin on PC to flash stock firmware. Or Twrp recovery.
2. Once you have Twrp recovery, then everything else is done through it.
3. Your very important first thing to do, once you flash Twrp. In Twrp, make a full backup of your phone, especially your EFS partition. Keep in safe place.
And if you want to be even more safe, backup your efs every time you upgrade your firmware.
4. READ, READ, READ! Google is your friend. If learning something risky and new, read from a few different sources, make sure it adds up!
GOOD LUCK!
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
IAmTechFreq said:
How would I go about making my own Custom Rom? I'm thinking of adjusting the Resurrection Remix So it would work on my phone but the specific ROM is on Verizon verison of the Note 4 and I want to port that for my Version for Sprint I know I can change some CSC stuff to get the modems and carriers ready for no signal loss or mobile data or sms issues as I have seen a method for flashing a zip file, but I;m just really curious, as I hope I can rebuild LineAgoe or CM for this Note 4 as I have a lot of time and alot of learning to do.
Click to expand...
Click to collapse
This cannot be taught in a response.
If your serious about learning then....
Lots and lots of reading, then try smaller stuff first. And work your way up.

aaron74 said:
To add to samep's comment. Here's a few pointers, in no particular order.
1. You only use Odin on PC to flash stock firmware. Or Twrp recovery.
2. Once you have Twrp recovery, then everything else is done through it.
3. Your very important first thing to do, once you flash Twrp. In Twrp, make a full backup of your phone, especially your EFS partition. Keep in safe place.
And if you want to be even more safe, backup your efs every time you upgrade your firmware.
4. READ, READ, READ! Google is your friend. If learning something risky and new, read from a few different sources, make sure it adds up!
GOOD LUCK!
Click to expand...
Click to collapse
Thank you aaron74! Question, would it be better to install Twrp using Odin, backup (w/EFS partition), then downgrade to stock Lollipop using TWRP? Or would the original order Odin > stock Lollipop > TWRP > backup > root be just as good?

rayel said:
Thank you aaron74! Question, would it be better to install Twrp using Odin, backup (w/EFS partition), then downgrade to stock Lollipop using TWRP? Or would the original order Odin > stock Lollipop > TWRP > backup > root be just as good?
Click to expand...
Click to collapse
I don't think you can downgrade from within Twrp.
But it's definitely safer to install twrp and get your EFS backup first. Just in case. It's extra step but you have your EFS, in case something goes wrong with downgrade. I'm not very knowledge on the downgrade process, never done it.

Root magisk questions

Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.

Kape1234 said:
Hey guys.
I'm reading the forum over and over, reading guides but still can't quite understand few things about magisk root.
1) Is it necessary to use TWRP for root using magisk? I found a guide to patch stock rom boot.img and then flash custom rom without TWRP. This way encryption also works (I read it doesn't if you use TWRP).
What is the purpose to use TWRP at all? What are the pros and cons of each method.
2) How is OTA update handled for Samsung with magisk? Do I have to revert back to stock rom using odin each time a new update appears?
Or I can do download OTA update, apply it, then without reboot, I just reinstall magisk from my phone and everything will work?
3) Can you make signed custom rom for samsung so you can lock bootloader after root, just like people do it for one plus on this forum?
Or it is not possible with samsung?
Thanks in advance for help.
Click to expand...
Click to collapse
Hello,
First off I would just let you know that typically questions like this go in the Q&A section.. This is S20/S20+/S20U Snapdragon Development thread which is usually reserved for people who develop things such as roms, twrp, mods etc. etc. so be sure to ready the rules and other stickied information when considering to post just to be sure you post in the right section.
So next thing I want to say is that in order to use TWRP or root or anything custom really on a usa Snapdragon model (U/U1/W Models) you have to use paid service to unlock the bootloader IF your device is eligible to be unlocked which means you haven't updated to the latest OS, if it is, then you are out of luck for now until new method is developed using new security.
If you are unlocked already, can unlock or just want to know I will try and answer your questions now.
1) TWRP is not necessary. Neither is patching the full ROM. All you need to do (if you don't want to use TWRP) is take the boot.img from the stock firmware, patch it using Magisk app and then flash it in ODIN. Device will wipe most likely if encryption and vbmeta etc. isn't disabled already. I do not know if "encryption" works while just rooted using Magisk patched boot.img or not as I usually disable all that stuff. My guess is that in some form it would be encrypted, just not sure if it's the same thing you are referring to or not.
2) If you are on an unlocked bootloader and complete stock i.e. no root or anything just clean full stock then you should get OTA updates. If you use anything "custom" i.e. Magisk patched boot.img or TWRP installed or vbmeta disabled etc. etc. then OTA updates will NOT work. And no, you don't have to revert to stock in ODIN each time there is a firmware update. It really depends on the update but you can typically use the odin tar with home csc and it should update without wiping but at the same time you would lose root or need to re-patch the new boot.img etc. etc. but wouldn't necessarily have to flash stock first then start over. There's also "safe" updates available some posted by jrkruse in development sections. If you had a usa unlocked device that was unlocked using paid service then you do NOT want to take OTA's because Samsung has changed the way tokens are verified when device boots up so new OS can't read them and most devices have incremented the bootloader so if you did take an OTA you likely would lost your unlock and no way to downgrade.
3) No. In order to do that you would need Samsung's private keys since there is no way to load your own custom key to use.. you can't just sign it with any key.. Also, if you relock your bootloader on a USA model that was unlocked using paid service then you will not be able to unlock again.. either way, it's not possible to use a custom signed firmware then relock the bootloader and have it boot.. not on Samsung anyway..
Hope that clears it up for you.
Thanks