Develop Bugs

[Q] Rooted, updated phone (stupidly) with Att OTA update, tried to install custom Rom

Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!

wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
Download the file below file to your S3 and install it via Mobile Odin to get CWM back.

Well, from what I read, you aren't rooted anymore.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

wickbok said:
Hello,
So I recently had my SGS3 rooted until I stupidly installed the OTA update that Att released. Everything was good, but now my phone was unrooted and I was unable to reroot using conventional rooting methods. Now, I figured that it would be good to install a custom ROM in order to re root my phone and put jelly bean on it. However, when I went into the Clockwork mod recovery, it gave me a status 7 error while trying to install the latest nightly build of CyanogenMod 10. I also cleared out all the caches and did a factory reset. Does anyone know what I might be doing wrong?
Thank you very much for your help!
Click to expand...
Click to collapse
If I recall correctly, Status 7 means you have an older/not-supported version of CWM installed. Your best bet is going to be to download the Samsung Galaxy S3 QCom ToolKit, and use that to install the proper CWM version. Then you will be able to wipe/install a custom ROM.

Updating(OTA) to 4.3 with root?

I have looked around and can't seem to get a straight answer about this. I have a stock rooted gn2, if i update over the air will it brick it? At the moment i have the att updater frozen with titanium backup. Any insight would be greatly appreciated, happy holiday!

where have you been searching? This has been covered dozens of times...

sorry
could you possibly provide a link sir?

generally speaking you can NOT take/install any OTA update when you are rooted...most OTA updates wont install if a custom recovery is detected.
99% of the time it wont work, .09% of the time it might install but you will have all sorts of issues, and .01% of the time it will work..
I think that pretty much covers it; you should probably just be patient and wait until the dev's incorporate it into a custom rom, and then you wont have to unroot to "enjoy" what ever the wonderful features are that ATT was so kind to include in their update..

And the install checks for stock system

You can install if you have stock rom. Root doesn't matter. My phone was rooted with stock room and twrp recovery. I just flashed stock recovery back. I had my superuser integrated in system partition. After Ota, i upgraded superuser apk. It then disabled Knox and download latest su binary.
So successful update with root preserved. Pm me of you need help
Sent from my SAMSUNG-SGH-I317 using Tapatalk

WARNING :
If you take the official OTA to 4.3 while root is present...you WILL trip the KNOX counter in your boot loader.
And if you root after an official 4.3 update you WILL trip KNOX anyway..
My .02....DO NOT UPDATE....
Stay rooted on the old bootloader and flash a custom 4.3 rom.....g

Wife is getting a new AT&T note 2 on the 24th (it already shipped). I would assume it doesn't have the OTA on it yet. Can you just reject the OTA when it arrives? Or will it try to install automatically on the new phone. Any way to prevent that until I can get my hands on it (have time tio mess with it).

Anyone try flashing a rom After ota update?
Did you thank your Developer today?

Same boat
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!

cordless89 said:
I too have a stock rooted 4.1.2. OTA fails as root present, got that. All I need is a stock 4.3 root. I have read several posts and still unclear as to what to do. I have either missed it or just not found the answer.
Do I need to unroot via SuperSU? then OTA? Odin flash a stock ROM?
Please don't bash as I am only seeking an answer. And any help is greatly appreciated!
Click to expand...
Click to collapse
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: link removed (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.

flymacs said:
I had stock rooted 4.1.2 with cwm as my recovery. I did the ota update. After the update, cwm wanted to fix root but couldn't. Essentially I lost root. Next, I re-rooted with CF-Auto-Root. I then installed SuperSU from play store which disabled Knox. Using GooManager I flashed TWRP. The last issue was wifi wasn't working. I used Odin to flash this file: http://d-h.st/OYC (unzip and use the tar in Odin). Wifi restored. Overall I like this update. It's faster and smoother.
Having said all this, I do not recommend anyone use this method. It's much cleaner to unroot then update. Or better yet, as suggested before, use one of the custom 4.3 roms.
Click to expand...
Click to collapse
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve

Is there a pre-rooted stock 4.3 for the i317 AT&T available?

geeve420 said:
So you had no trouble flashing TWRP? I went back to 4.1.1 from Skynote, OTA'd 4.1.2 and was going to flash another ROM but my wife got my phone the next morning to play slots and she accepted the 4.3 official update before I woke up. I did root with CF Auto and disabled Knox, but was wondering if Goomanager would work.
The next question is can we flash some ROMS with the rooted OTA 4.3?
Geeve
Click to expand...
Click to collapse
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
cordless89 said:
I noticed the OTA did not work on my nine as I got the "unable to update" after the OTA downloaded. I initially rooted via the CF-Auto flash.
Just curious as to next step.
Click to expand...
Click to collapse
Did you debloat or remove any apps from the stock 4.1.2?

flymacs said:
Goomanager worked fine. No problems with twrp either.
As far as flashing on from ota 4.3, I'm not brave enough yet.
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
---------- Post added at 01:24 PM ---------- Previous post was at 01:17 PM ----------
Did you debloat or remove any apps from the stock 4.1.2?
Click to expand...
Click to collapse
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.

cordless89 said:
Nope, pretty much as stock as you can get plus root. OTA failed but I assume reason being the root... but I'm a newbie on this stuff.
Click to expand...
Click to collapse
Then the next question I have is if you are using the stock recovery? I was using cwm on stock rooted 4.1.2. When I did the ota, the phone rebooted into cwm. Cwm asked if I wanted to do the update. I selected yes. When it completed, the Samsung installer gave a failed to install message, but cwm showed that it completed and wanted to fix root. It couldn't fix since I was unrooted at this point. I rebooted into 4.3 non-rooted. Re-rooted...etc.
I want to say again that I don't recommend anyone follow this procedure. I'm just trying to describe how I solved my own mess and hopefully answer any questions.

help needed! Trying to root and install OmniROM 4.4 on my i747

hey guys. lurker turned new poster here at XDA. a friend of mine turned me on to this a while back when he introduced me to the world of rooting. I've recently bought a Galaxy S III (SGH-i747), and I've been trying to root it using mskip's unified toolkit (http://forum.xda-developers.com/showthread.php?t=1979290). I got it rooted once, but eventually bricked it when trying to get 4.4 on it, and had to reinstall the stock 4.1.1 rom on it and lost the root in the process.
I'm completely new to all this, and I'm still trying to figure it out. I've been searching as much as I can and reading a lot, but I'm not sure if there's something I'm missing here. when I try to root it lately using the toolkit, it gets stuck in the process after I exit Odin, and will never progress.
before when the root was actually in place, I tried to install a custom OS after doing a full wipe of the system, and it never would install. I tried it with TWRP and CWM, and there was no success with either of them. the one peculiar thing, however, is that I could never get it to install with the "ALLINONE" option. when I got it to work that once, I had to install it each individually.
is there some sort of guide out there that would make this easier for me to get 4.4 on the phone? or will someone be able to help me through the process?
thank you for your time!

I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?

hachikid said:
I just rebooted my comp, reinstalled the drivers for the phone through the toolkit, and gave it one more shot at rooting it (option 1 in the program), and this is what the process looked like.
*see attached image*
I *always* get stuck at the "pushing superuser.apk and su binary.." part.
any thoughts?
Click to expand...
Click to collapse
I used this when I first rooted my I747. http://galaxys3root.com/galaxy-s3-root/how-to-root-att-galaxy-s3-sgh-i747/
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

My Bell s3 was on 4.1.2. I rooted by installing a rooted rom from here: http://forum.xda-developers.com/showthread.php?t=1739426
Do not flash a 4.1.1 or 4.1.2 rom if you have a bootloader from 4.3.

when I got the phone, it had 4.1.2 on it. when I bricked it, I flashed a stock 4.1.1 ROM on it, and that's what I've been using as my base ROM.
Boomer1605: I'll try that when I get home.
anyone else know what is up with the place I get stuck at during the toolkit way?

My Bell s3 was on 4.1.2 when I got it. SInce I needed to unlock it and didn't want to pay, I installed the stock Bell 4.1.1 firmware from here: http://www.sammobile.com/.
After using the menu option to unlock the phone and confirm that it was unlocked, I flashed the pre-rooted Bell s3 4.1.2 rom.
Everything worked perfectly, no errors or issues at all.

Cool! Can I find a pre-rooted 4.1.1 AT&T rom on that site? I can't really look at that link cause I'm currently at work.

Pre-rooted roms are here: http://forum.xda-developers.com/showthread.php?t=1739426
I was able to install Root Explorer on my pre-rooted ROM and delete a tonne of Samsung apps.

I was able to install a pre-rooted version of 4.1.1, and I did a system/data/cache/dalvik wipe from the TWRP screen, but when I tried to install both Liquid Smooth and Omni Rom, it failed. I even restarted and didn't wipe, and it still failed. not sure where to go from here... :/

tativle coast
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!

hachikid said:
totally got it to work! I skipped using the toolkit to install TWRP, and used GooManager to use the latest TWRP. worked like a charm! currently running on Liquid Smooth 4.4.2!
thanks for the rooted copy of 4.1.1!
Click to expand...
Click to collapse
Awesome! Congratulations. For future reference, TWRP also had tar images for use with Odin.

Unlock bootloader and root new device

I am going to purchase a Nexus 7 2013 and will be wanting to unlock the bootloader and root the device straightaway. I would be grateful if someone could tell me the best way to go about this. Should I carry out these tasks with no ROM updates applied, i.e. on 4.3 or should I update to Lollipop first? Thanks in advance.

With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk

Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.

crazymonkey05 said:
With the nexus 7 its as simple as typing fast boot OEM unlock, but here is a more comprehensive guide on the matter. http://forum.xda-developers.com/showthread.php?t=2381698
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Many thanks. I used the excellent Nexus Root Toolkit.

PrizmaticSmoke said:
Unlock the bootloader before doing anything else, as it will wipe your data in the process.
If you plan on staying with the stock rom, don't bother rooting or installing a custom recovery until you've updated all the way to lollipop, as it can cause the ota updates to fail and you'll just lose root with each update anyways. Beware of taking this route though, the are lots of posts around saying that the latest ota update bricked devices. Might be safer to fastboot flash the latest factory image directly.
If you plan on using custom ROMs, go ahead and root it and install custom recovery then flash away to your heart's content. You may need to update the bootloader to latest version first to successfully flash lollipop ROMs though. I think its version 4.04, and there are flashable zips for doing this somewhere around here that worked great for me.
Click to expand...
Click to collapse
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.

pretty pixel said:
I unlocked the bootloader, updated to Lollipop 5.0.2 by flashing the latest factory image, then rooted and flashed TWRP. I would now like to flash custom ROMS. You mentioned I may need to update the bootloader in order to successfully flash custom Lollipop ROMS? Am I correct in thinking I will have the latest bootloader, now that I have updated to Lollipop 5.0.2? Thanks.
Click to expand...
Click to collapse
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.

PrizmaticSmoke said:
Yep, you're correct. If you flashed the factory image, you should already be on the latest bootloader. :good:
By the way, 5.1 factory image finally was released today for this device.
Click to expand...
Click to collapse
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?

pretty pixel said:
Great, thanks for letting me know. Do you recommend I update to the 5.1 factory image before I flash any custom ROMS, or doesn't it matter?
Click to expand...
Click to collapse
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.

PrizmaticSmoke said:
Doesn't matter, though you may wait for the custom ROMs to update to 5.1 so they will have the latest binaries.
Click to expand...
Click to collapse
Thanks. Do you know if CM12 has moved to 5.1 yet?

Not sure, don't really follow cm, but u can just check their website.

pretty pixel said:
Thanks. Do you know if CM12 has moved to 5.1 yet?
Click to expand...
Click to collapse
as i know only few devices are on 5.1 yet

Just got note 4 still on KITKAT

I got the note 4 I am on kit kat N2K. I want to root but wanted to know the best way to go about it. Root on kitkat, then flash a rom to get on lollipop? Or accept the lollipop update, and then root and flash? Please advise thank you !

You'd have to decide what you want the most.
With Lollipop you get improved Sprint Wi-Fi Calling and latest security and bug fixes. The battery usage is notoriously higher in Lollipop and the fabled material theme is ugly to many.
KitKat has better battery and theme. Until the recent Android 5.1.1 updates, Lollipop bugs had many utilizing fixes to make Lollipop more like KitKat. The thing most important to consider is that if you upgrade to Android 5.1.1, the bootloader will inhibit you from Odin'g back to KitKat unless you use a specific Odin tar for OB7 to OG5 but it doesn't support the most recent OJ6 update. It's said you could just update the modem to OJ6 but I'd think you have to at least Odin the OB7 lollipop tar before doing that.
I wouldn't recommend rooting and then flashing a ROM outside of the base you're running. Use Odin to update to the equivalent base. OJ6 would be the latest but bootloader inhibits downgrade to KitKat.
I'd suggest rooting KitKat and trying it or a custom NK2 ROM. Next you could try OB7 to see if Lollipop is to your liking. Then you could decide if the latest is what you prefer.
Developer support is currently at OG5 and OJ6; Android 5.1.1 Keep in mind that Android 5.1.1 stock requires kernel with root exploit and SuperSU zip flashed in custom recovery to root. The updates prior can be rooted with CF Auto Root or just Odin custom recovery and flashing custom ROM or SuperSU zip to root stock.
What to flash? You'd have to ask a specific question once you have a better idea of what you prefer or direction you're starting at.
Sent from my SM-N910P using Tapatalk

Thank you for taking the time to type all that up for me! I am going to stay stock until the 14 days incase the phone has some problems before rooting but my brother and dad have note 4 also and both on 5.1.1 and phones are way smoother than mine on kit kat so I would want to be on the latest and have root. I also saw there is a note 5 rom which looks great as well. So is it cool if I PM you in a week or so to help me? I know there are threads but I dunno where to begin . Appreciate it!
Thank you,
Indels

Yes, you could PM. Are the other Note 4 phones rooted or plain stock?
Currently, the Note 5 port is one update behind latest. Maybe it will update.
You don't have to stay with KitKat. Updating won't void your return exchange. But I would recommend a factory reset before making the jump to Lollipop. You can take incremental updates over the air; KIES or Odin stock tar OJ6 from general forum would get you updated to latest in one session.
Just don't Odin custom recovery if you're concerned about Knox trip during your return period.
To get started you'll need the Samsung driver for your PC to use with KIES or Odin. You'll find that here:
http://www.samsung.com/us/support/owners/product/SM-N910PZWESPR# Run the .exe file on PC to install.
Here's a link to TWRP for Note 4:
https://dl.twrp.me/trltespr/twrp-2.8.7.0-trltespr.img.tar
Download Odin (below) and make a folder for it and put the TWRP file and stock tar in it. Find the latest tar in general forum and check the md5.
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
You can also download the zip for ROM you wish to install. Typically, you'd flash the tar that corresponds to the ROM you wish to run for maximum compatibility so you could wait on the tar and zip. Any of these could change but preparation wouldn't hurt.
Sent from my SM-N910P using Tapatalk

Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !

Ind3lible said:
Yeah the other 2 notes are on 5.1.1 stock. I am still on kitkat, update notification for lollipop is annoying tho I can't find a way to get rid of it lol. I get good battery on Kitkat is the phone still good on 5.1.1? Is root out for 5.1.1 as well? I would assume so. Thank you for the links! !
Click to expand...
Click to collapse
Battery life for initial Lollipop was not so good until Beastmode kernel came out starting in OG5. I've heard OJ6 is even better but I haven't tried it.
Like I said, KitKat has better battery but worse Wi-Fi Calling feature.
Touchwiz 5.1.1 is rooted with custom kernel and SuperSU zip or any custom ROM is pre-rooted. Just don't use Chainfire auto root for Note 4 on that.
Sent from my SM-N910P using Tapatalk

"But I would recommend a factory reset before making the jump to Lollipop."
So I should factory reset on kit kat and then go to lollipop if I understand this part correctly? I have to notification to go to 5.0 right now. I can odin twrp once I go to lollipop too right? Sorry for so many questions just confused. I have not rooted a phone in quiet some time :fingers-crossed:

Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk

samep said:
Correct. You shouldn't have any problem rooting once you update, even latest update.
You'll have to reapply TWRP after update. OTA updates are incremental but Odin or KIES will allow you to jump to latest update available. Currently, that's OJ6.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!

Ind3lible said:
So it updated on its own to lollipop.. lame so I am on 5.0.1.. the nofication was there since day 1. Now my question is can I go back to Kit kat from here? I searched google and could not find a definite answer. :crying:
I was happy on kitkat everything worked as it should and battery was great!
Click to expand...
Click to collapse
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk

JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx

samep said:
OTA updates are incremental so if you catch it before it updates beyond OB7, you can still Odin back to KitKat. You should go into app manager and disable software update package in all apps and turn off auto update.
You'll need to factory reset before going back to KitKat. If you've updated past OB7, it's too late.
If you're able to jump back check out this post and follow the links:
http://forum.xda-developers.com/showpost.php?p=62620747&postcount=3
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.

Ind3lible said:
Thank you so much ! I was able to ODIN BACK! I am gonna stay on KK for the time being. Just gotta root it, I have TWRP and ODIN Downloaded now. Is there is thread for KK root? I see the 5.1.1.
Click to expand...
Click to collapse
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk

samep said:
If you plan to root stock KitKat, use Chainfire auto root in Odin and then Odin TWRP; custom ROMs are already rooted, just Odin TWRP.
http://forum.xda-developers.com/showpost.php?p=55865427&postcount=1
Download for SM-N910P is in third post.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir! You've been of most help!!

alwright1980 said:
JUST A QUICK WORD OF ADVICE TO THE op @Ind3lible FOR YOUR SAKE DONT UPDATE BOOTLOADER BEYOND THE OB7 UPDATE TARBALL BECAUSE OF ROOT RESTRICTIONS THAT ARE TROUBLESOME TO GET AROUND... yOU CAN STILL TAKE ADVANTAGE OF 5.1.1 LOLLI ROMS WITH THE OG5 BASEBAND MADE AVAILABLE BY @tx_dbs_tx
Click to expand...
Click to collapse
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !

I havent keard of a firmware ending ok1 for the SM-N910P
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
Ind3lible said:
Thank you for this.. Not sure how I missd your post but I did already update to Ok1 and am very happy with it battery is great and it is super smooth !
Click to expand...
Click to collapse
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root Restrictions​All of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents

alwright1980 said:
---------- Post added at 02:37 PM ---------- Previous post was at 02:36 PM ----------
These are the ones I know for Sprint Note 4
N910PVPU...
. . .ANIE . . .ANK2. . .BOB7*. . .BOF5** . . . COG5***...COJ6**
Android
[<==K I T K A T==>][<=======L O L L I P O P=========>] [^^<===4.4.4==>^^][^^<==5.0.1==>^^][^^<==5.1.1==>^^]
*No Locked Bootloader/Mininmal Root Restrictions
**May or May Not have locked Bootloader/minimal root restrictions
***Locked Bootloader/Strict Root Restrictions​All of them have there benefits. I have had people tell me that they will not leave kit kat 4.4.4 because of development is more.... well.... developed! BOB7 was the last bootloader that was a necessary component for loading a lollipop rom, AND didn't have Heavy duty root restrictions and either it or its progeny three months later was the last to not have a locked bootloader. That is where once you have their bootloader you cannot flash back to a previous one. For sure it was off by COG5 and has we all know they instituted some root restrictions that took a long time to get around and even longer time to do so with an "apparent" seandroid enforcing kernel.
All that is to say again, that, whatever you actually are on, if it is still BOB7 or earlier, then when it comes time that you want a 5.1.1 rom custom stock or otherwise, flash the appropriat baseband version of the bootloader that @tx_dbs_tx puts out it will keep you able to do the same things but without locking you into a change you cannot undo. I don't know if this will be an option for marshmallow when the note 4 gets it. If so great if no wait & update late.
My 2cents
Click to expand...
Click to collapse
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:

Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
I don't think it would have been possible to have gon from KK - LP - MM while preserving a KK Bootloader, and if I am correct in that you won't bee able to Odin back to KK unles you can get reliable instructions on how to seperately flash bootloader, which might be a risky venture, I simply don't know there. You also may be able to get a custom rom which is KK based but I would discuss trying to use it on a phone that has been updated to MM with the DEV if they still offer support. Whatever you do be cautious and well informed before proceeding and know your risks, otherwise it can get expensive.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
I would have thought that it would have been impossible to flash 2 a lollipop and then a marshmallow ROM from a KitKat ROM while preserving the KitKat bootloader. If I'm correct in this then you will not be able to Odin Flash from your marshmallow ROM back to stock KitKat firmware. That is unless you know of a way to separately and reliably Flash your bootloader. You may be able to use a custom rom that incorporates KitKat, but I would be careful about deploying around like that after having updated to marshmallow firmware, and I would discuss it with the developer if they're still offering support for it. Whatever you do be cautious and well informed before moving forward otherwise it can get expensive!

Ind3lible said:
SO been a while! I am now on 6.0.1 and I had a question. Is it possible still to go back to 4.4.4? I know the bootloader has changed since as mentioned in your earlier post but I wanna know if it is possible. I wanna test something on kitkat for my tech channel! I know I have to flash the old bootloader and modem as well but not sure if it will actually work!! :highfive:
Click to expand...
Click to collapse
It can be done but not as you would think. The KK bootloader wouldn't flash but read the instructions in this post.
http://forum.xda-developers.com/showpost.php?p=68456368&postcount=149
Edit: if you still have that KK backup, you could restore that instead of the KK ROM but still need the Lollipop custom kernel and Lollipop bootloader.
Sent from my SM-N910P using Tapatalk

Like I said I don't know anything about bootloader switching betweem KK -LP -MM. So I cannot comment effectively on whether or not it would besafe or what you might lose or gain by these methods. Just don't know.