Develop Bugs

[Q] Newbie (kinda) help rooting my note

I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?

koker93 said:
I've been rooting phones for a few years now (my evo and my Note 2.) I had my note 2 rooted for about a year and while having performance issues with Sprint (hate sprint) I flashed back to stock and updated everything, including the firmware. Ugh, I updated the firmware to the new knox firmware. Not knowing I was up a creek, I reflashed my phone with the tools I already had and had already used and triggered knox and cant get a recovery to stick. As far as I can tell the phone is still stock with knox tripped and I cant get any farther. I've spent a few hours reading now and I cant seem to find a way to either reverse knox or root the phone with knox tripped. I tried the cf auto root in the origional development section and couldn't figure it out.
Anybody got any advice, or a link to a thread started post knox so it talks about how to deal with it?
Click to expand...
Click to collapse
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

g_money said:
You shouldn't be up a creek. What recovery did you flash? Try the latest Philz for note2. Unchecked auto-reboot in Odin before flashing it, and when it's done pull the battery then put the battery back in and do the power button/home button/volume up to get into recovery...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
I've been using the unified android toolkit. It seemed to work flawlessly before knox. Now it just stalls. Odin installs the custom recovery, the phone reboots, and goes into the stock android recovery. So I unchecked the auto reboot option, flashed CWM, and while looking nervously at the do not power down device screen, pulled the battery. It booted into CWM fine, flashed Paranoid Android and gapps fine, and rebooted into the new ROM just fine.
Not really sure why I was having problems, or why the pull the battery step is necessary, but it seems to have worked. I did not flash any SU files. Is that necessary?

I would download 1 of the root checker apps, or just install an app that requires root.
Usually (though I can verify not always. Lol) you have to reboot directly into download mode to finish the install of the custom recovery. If you let your phone reboot, stock recovery will over-write the custom recovery that you're trying to install...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.

koker93 said:
I ran a root checker and it says I do not have root access. But the phone is running paranoid...so what am I missing here? I thought I needed root access to install the recovery and install a ROM. Seems I do not. Should I care about the lack of root access? Because all I really wanted was to replace the ROM, and that seems to have worked.
Click to expand...
Click to collapse
PA Roms work funny with root access on my device also. Just download and flash the latest SuperSU zip. If you already have it installed wipe the data first.
Sent from my SPH-L900 using XDA Free mobile app

Noob idiot here need help

Ok I dont know the fancy terms so please bear with me as I explain what I did.
I wanted to root my note 4 I downloaded odin v 3.07 and followed the "easy" online steps.
so it did its thing odin said pass then the phone started resetting this just looped and looped. so I tried and tried again and no success . I factory wiped the phone and still nothing, I fear I bricked this thing can someone help me I feel like a complete idiot. Thanks

From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the exploited kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk

samep said:
From the top, what update version were you rooting? What did you Odin?
If you're on a recent update OE1 and up, the bootloaders have a reactivation lock that keeps you from successfully downgrading. Even the OG5 bootloader will prevent going back a single update from what I've read. You should be using Odin 3.10.7 or latest using the OEM unlock in option tab. The ROM itself may be locked to reactivation in Settings/Security. You should also enable developer mode and make sure USB debugging is enabled.
Also, OG5 stock kernel blocks typical root methods. You need the rooted kernel for that plus SuperSU zip. Technically, you'd only need custom recovery flashed in Odin then flash either the zips or pre-rooted ROM with the kernel and SuperSU included in flash.
There's even a guide posted for that:
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I believe i had the latest update 5.1.1 I got the phone working again. I found the latest Md5 and used odin 10.7. I am so new to this its stupid its taken me 2 hours to fix my first mistake I basically lost everything but im ok with that. Thanks let me give this another try i was scared id be at sprint in the morning buying a new phone.

Stuck in boot loop

I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1

Thuganomics said:
I recently tried to root my phone using CF Auto Root and its now stuck in boot loop. The phone is a sm-n910p running 5.1.1. Is there anything I can do to fix it? I have been trying to use stock roms but they either fail in odin or they cause odin to freeze up without doing anything. The only error I can see is SW Rev check fail fused 4 binary 1
Click to expand...
Click to collapse
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin to flash custom recovery would be a prerequisite for rooting stock with those zips or custom ROM zip.
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk

samep said:
Stock ROMs getting flashed in Odin? Stock tars full and partitions from tar ball or custom recovery is all you should flash with Odin.
If you're trying to flash custom OG5 ROMs, that would require TWRP or CWM recovery flashed in Odin.
CF Auto Root was suggested until Android 5.1.1/OG5 update. Root now requires kernel exploit like Beastmode kernel by freeza plus SuperSU zip to root stock flashed in custom recovery.
Odin would be a prerequisite for rooting stock with those zips or custom ROM zip.
Custom OG5 ROMs only require custom recovery to flash because they're pre-rooted with those during flash.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I was able to flash the TWRP 2.8.1.1 and im able to access the menu in recovery mode however I still get stuck on the boot loop with no kernel even though I had one on the phone before starting the process

Have you flashed the Beastmode kernel and SuperSU zip linked in the post I linked you to above? Are you getting a message indicating no kernel installed? A ROM flash or those zips would get a kernel onboard.
If you're stuck, just try OBAR ROM on a clean install. You can find it in development forum.
Sent from my SM-N910P using Tapatalk

I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
The link is live in the post above. Scroll down to where SuperSU zip is linked as well. Flash both those in TWRP recovery.
You'll still need to freeze or remove Knox. There's some other notes that apply to stock in that post, like the build.prop edit.
Sent from my SM-N910P using Tapatalk

Thuganomics said:
I was able to do a complete reinstall after a few hours of stock rom and it seems ok as of right now still back on 5.1.1. How do I root it but still keep everything as close to stock as possible?
And yes i have checked out the beastmode however the link is down.
Click to expand...
Click to collapse
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.

jhill110 said:
@tx_dbs_tx has 2 stock, prerooted, odexed & deodexed roms. They are completely stock excepting Knox & sprint itson and as I said are prerooted.
If that sounds like what you are looking for here is the link :
http://forum.xda-developers.com/showthread.php?t=3185274
These roms are flashed in recovery.
Click to expand...
Click to collapse
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?

Thuganomics said:
Thanks..i was able to get twrp 2.8.7.0 loaded on and the beastmode kernel..however the phone seems to be draining battery extremely fast even with my zerolemon extended battery..in about 5 hours I'd normally go from 90-80% with average usage where as today I barely used it and it dropped from 65-20%. If I'm trying to remain as close to stock as possible but just have root permissions with the bloatware removed which one would I want the odexed or deodexed? Do i have to flash the ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB56 91107_REV00_user_low_ship_MULTI_CERT.tar.md5 before flashing one of those?
Click to expand...
Click to collapse
Odexed is better for performance, deodexed is a better choice for moding. I always use deodexed as the performance of this device is outstanding.
As for the battery issues, I use GSam battery monitor (there are many others). It helps you see what is using up battery.
Go through the system settings and turn off things that aren't necessary for you. Many of them contribute to battery drain. It's a drip, drip, drip thing... Not any one thing. A process of learning what helps and what doesn't. There's no catch all answer... You've got to work at it.

Flashing AllianceROM to my stock, but rooted Note 4

Hello, I am new here and could use a little help please.
I would like to flash AllianceROM for my Sprint Note 4 N910P - NK2. It is running the stock Kitkat 4.4.4 and has been previously rooted via Odin.
I read that if I am coming from Kitkat, that I need to "Odin Lollipop with modem and bootloader..", and I have a vague idea what that means but no idea how to go about it.. What im not clear about is, does that mean I need to update only the bootloader and modem, or also the OS?
I really appreciate all of your help!

It's as simple as:
Odin OB7 stock tar and Odin TWRP. Flash ROM. Get stock tar and Odin from link below. PC driver will be at Samsung mobile support for Note 4.
http://forum.xda-developers.com/showthread.php?p=59483780
TWRP recovery for Odin:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
But the 3 things to consider or note before you begin:
1) if you update beyond OB7, the bootloader gets upgraded to one with a reactivation lockable bootloader. That will prevent you from being able to Odin back to KitKat. You need to disable auto update and stop the update notices before they start; otherwise the nags persist and you may accidentally update.
2) the lollipop file system is different than KitKat do better off formatting your data and wiping cache and dalvik-cache and powering down and pulling battery prior to Odin OB7 stock tar. Let it boot and setup wizard prior to Odin of TWRP (uncheck auto reboot for recovery flash only), boot into TWRP recovery and flash the ROM.
3) dalvik gets built on initial boot of lollipop ROMs; the stock tar still not much quicker. You'll likely see the phone hang at the second boot splash screen with blue LED slowly blinking before you see the app optimization and app start pop-ups. You can expect that with lollipop. Give it 30 minutes to boot before you panic. To avoid CPU heating and slowing the process, remove your phone from its case and ventilate if it gets too warm. You need to start with battery charged to about 80% to full to be safe. It's best to not try and update apps or restore apps until you've flashed and booted the custom ROM. More apps means the process takes longer. You can format the data again prior to flashing the custom ROM to speed things along. If possible, backup your media, and downloads that you want to keep and wipe internal sdcard to get a cleaner start with lollipop. That's optional but don't lose your keepsakes. What you flash should be on extSdCard to avoid the wipe-loss if it.
BTW, the post you're referring to may have been an attempt to recover phone after attempting to downgrade to OB7 or KitKat. It's since been discovered that although Odin wouldn't downgrade, there's a possibility to flash older ROMs in recovery and immediately flash a 5.1.1 rooted kernel to get it to boot without looping. That doesn't have to apply to you; the general rule is to Odin flash the tar that matches the ROM you want to flash in recovery. But again, if you upgrade beyond OB7, you cannot go backwards with Odin. Only few exceptions apply; generally it is forward, not backwards. OB7 is the divide that separates the simple from more complex conditions. So these last 3 paragraphs shouldn't apply to you as long as you're wanting to stay with OB7 or KitKat.
Just for an idea of what to consider in other lollipop updates. The ram optimization got a bit crazy after OB7 and continued until it improved in OJ6. Personally, I think OJ6 and OK1 updates are the best lollipop updates yet. You'll certainly find more security updates in those updates. But lollipop 5.1.1 also introduced the need to root the kernel but Chainfire has recently brought us a patch to use stock kernel again; it's married from experimental to beta. I've mostly ran with stock kernel on my phone, especially before lollipop 5.1.1
Long post but felt the long threads needed some explanation. Things were once simpler but got a tad more complex as time and updates followed OB7.
Sent from my SM-N910P using Tapatalk

Wow that was an incredibly detailed post and I think it will be exactly what I needed to know, so thank you for that!
The original post I was reading was here by the way - http://forum.xda-developers.com/not...-0-1-allianceromn910p-18-themes-huge-t3066673
I will get going with this a little bit later today and let you know how it turns out, again thank you for that awesome reply! :fingers-crossed:

Just to follow up, with your instructions it went on without a hitch!
Thank you!

Currently Alliance ROM want to go back to Stock

Title sums it up. Currently on AllianceROM 5.0.1 OB7. Want to go to stock (rooted probably) so I can get MM when it (if it ever) drops. Do I need to do anything special or can I just wipe everything in TWRP, then Odin the stock zip? I get a little weary reading about bootloaders locking above OB7. What does that mean for flashing ROMs if I upgrade the bootloader? Also, does the hotspot fix work on the most recent stock ROM?
Thanks for any help. I have three little kids and no time to research this fully, otherwise I would.

If you're looking to stay OTA capable without going through Odin again to update to MM (weeks to go possibly, IDK?), you most likely wouldn't be able to add hotspot mod without losing OTA capability.
- Use the updated Chainfire Auto Root for Note 4 mostly stock with OTA capability.
*You'd use the full un-root option in SuperSU to update. It's supposed to work if no system mods or system mounting occurs but no guarantee or confirmation I'm aware of on that. You could test that with OJ6, full un-root and take OK1 OTA update if so inclined to test it.
==================================
If upgrading to the reactivation locked bootloaders, alternate ROMs really have little limitation if done without Odin downgrading (only where the ROM you seek or return to is on an older update- that applies to alliance whether you're restoring a backup or flashing a ROM zip). But that also requires Odin again at some point unless you wait and do it only when necessary. You must flash ROM zip or restore a backup and flash a 5.1 kernel like Beastmode rather using Odin to downgrade. The kernel had to be flashed in order to get it to boot. Only limitation that I'm aware of is that your screen may not auto-dim on handset call when you put phone to ear. I had that issue with OB7 ROM with 5.1 kernel; I used the power button to dim the screen but you can't have power button set as an option to dismiss call or that happens when you don't want it to.
=================================
Moar 2.1 ROM is coming soon. That may help with the anticipation of waiting long for MM. But again, that means Odin for OK1 update, then Odin for MM. There's a chance that OTA to MM could be achieved even if dm-verity gets detected in stock recovery while trying to OTA. I think you'd have to clear and download the MM OTA again but first root with Chainfire Auto Root, full un-root in SuperSU app then try the OTA again. Odin OK1 by itself may not clear the modified status but systemless root and un-root may clear it. Just thinking ahead though; no guarantees. May have to wait for MM stock tar.
If not interested in current or future Lollipop rooms, you could just wait, Odin OK1 and OTA to MM when the update is available. Easy?
To answer the Odin question, you're correct on the update though. I tried to answer any questions you might have but may confuse you. I'd need more information on direction you're considering to answer more thoroughly if that leaves more questions.
Sent from my SM-N920P using Tapatalk

I'll have to find a time when I have time and can be without a working phone for a few hours and try to play around with some of this stuff. I'm sure I'll be back on here with questions at some point. Thanks for the initial guidance.
Sent from my SM-N910P using Tapatalk

Okay. I think today is the day. I've downloaded MOAR 2.1 and am going to try this for now. I also have the OJ6 stock (I know it's not the absolute most current) downloaded and ready for standby if I so choose. Here is my plan.
1) Wipe Factory Reset in TWRP 3x's (actually include internal storage as well, correct?)
2) Install TWRP 3.0 via Odin (currently 2.8.5)
2a) Per MOAR install instructions, install stock OJ6 via Odin and activate, etc, etc. Ensure everything works, maybe take the OTA to OK1.
3) install MOAR via TWRP from micro SD card
4) Profit!
If I want to install stock, all I need to do is install the stock ROM via Odin and I will be able to update OTA since I will by default be unrooted, correct?
Thanks for the help. I plan to attempt this later today.

I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk

samep said:
I don't know if the whole OTA capability appeals to you, you didn't mention it so I won't bring it up again.
You can find the link to OK1 stock tar in page 2 of that Moar thread.
I'd suggest you follow that OP closely. Particularly the recommended wipes. The developer prefers a clean approach, wiping the data and setting up as a new device. With ports, that's important.
If GPS is important, there is a bug fix release anticipated very soon. You may consider waiting for that but you can update to OK1 and back that up in TWRP while you're deciding. May not be long at all.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?

pilotmills said:
Well, I've got TWRP 3.0 installed. However, I've tried each stock (OJ6 and OK1) and each says that there is no update-binary in the zip files. Ideas?
edit: the zip files have a xx.tar.md5 file. Do I need to extract, rename it .tar and flash via odin?
Click to expand...
Click to collapse
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk

samep said:
The stock tar is for Odin. Look for the thread in Sprint Note 4 General Forum for better direction.
You should verify the md5 against the zip, then extract only tar.md5 for Odin flash in download mode. But wipe and power down first. Use latest Odin with Odin defaults.
You'll have to install TWRP again.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I think I need to slow down my postings . I looked around and found out basically what you just told me. Flashing the stock OK1 now, then I'll redo TWRP. Thanks for the timely replies. I'll try to keep it to only issues I run into that I can't resolve after some Google research. I really do appreciate the help.

Progress, but now I can't get the GPS to lock. Tried GPS status app, GPS Status and toolbox. Occasionally I get one or two satellites that show a signal being received, but never locking onto them. Eventually they will drop completely to zero signal. On the other hand, somewhere between OB7 and OK1, Samsung actually addressed the barometer issue that had plagued the N4 since launch where above about 3,000', it would not register anything but a sea-level pressure. Baby steps. . .

Is GPS failing to lock on stock OK1 tar update or the port? The port has GPS a release with fixes pending. But most were only reporting GPS navigation in Google Maps lagging or losing sync during navigation.
Sent from my SM-N910P using Tapatalk

Sorry, should have specified. I'm on stock OK1 now.

pilotmills said:
Sorry, should have specified. I'm on stock OK1 now.
Click to expand...
Click to collapse
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk

samep said:
Have you tried activation or data and PRL update in system update? Try those with Wi-Fi off.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
The GPS chip in this phone is horrible. I had the phone up against the window as a last resort and still nothing from the GPS. Went outside and it grabbed a lock within 30 seconds. I didn't opt for the anti-NSA snooping coating on the windows when we had them installed either. . . Backing up OK1 in TWRP now, then attempting to flash MOAR.
Thanks again. Stay tuned. . .

Got MOAR up and running. I had an activation issue the first time which was strange since I was able to send and receive texts and calls, but I kept getting an activation not complete message popping up and persisting. I did exactly as posted in the OP as well. Anyway, went back to OK1 stock and waited even longer after the data established before reflashing MOAR. Works like a charm now. Thanks for the patience and assistance!