Develop Bugs

Need help recovering from failed root

I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?

Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
Click to expand...
Click to collapse
Thanks! I'll give that a shot. But a question before I do something really dumb. Where does this recovery tar file go in odin? PDA?

Yep always PDA
Sent from my SM-P900 using Tapatalk

Worked! I now have rooted KOT49H.T900UEUAND4.

Good stuff
Sent from my SM-P900 using Tapatalk

OK. Here comes the "but". It turns out that I cannot connect over SSL. Wifi works, I have an IP, I can brows non-secure websites. But I cannlt connect to anything https, nor will apps like Google Play connect.
Do we think this is related, or should i start a new thread?
UPDATE: I wiped data and now all is fine. The really interesting thing that I've noticed is that the Device Status is showing as "Official".

JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?

gbr357 said:
JJMT - you are rooted and it says official? Can you go through the exact steps you used please? Is KNOX enabled?
Click to expand...
Click to collapse
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.

Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?

gbr357 said:
Thanks for the instructions. OTA done. I am going to give the rest a shot later tonight. I wonder though if using the B5 recovery for the T900 wouldn't be safer. It was posted later in the same thread referenced above by TweakerL (post #344 pg35). Going to give that a shot vice using the P900 recovery. What do you think?
Click to expand...
Click to collapse
I think I would have done that if I had known there was a B5 recovery image available. The guidance that I was given was to flash the B3 image from the P900. And that *did* work fine. Before there was a root flash for the T900, people were using the P900 root with success. Don't know that there is much difference. In the end, either way, you will end up with a B5 recovery image, as that is what Chainfire included in the T900 root file.

Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.

gbr357 said:
Well I got everything ready and instead of flashing the B5 image, I just flashed the root image from Chainfire. I didn't even think about what I was doing because that's such a normal process. Anyway, everything went off without a hitch. Rooted and rebooted in 10 seconds. Device now says custom however and I can't check for updates. That's fine though because all I wanted was root and I have ND4.
Click to expand...
Click to collapse
Which file from Chainfire did you flash? Was it CF-Auto-Root-v2wifi-v2wifixx-smt900.zip? For me, flashing that after OTAing to ND4 left me unable to boot. Maybe that got fixed in the past couple of day?

Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??

gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Well. technically I wasn't rooted either. I completely removed root with SuperSU.Is your recovery NB5?

JJMT said:
I opened the box on my new Galaxy Tab 12.2 SM-T900 today. I immediately rooted it with CF-Auto-Root-v2wifi-v2wifixx-smt900.zip. That worked fine. But before I rooted it there was a notification of an OTA update, so I unrooted and did the OTA update. That went fine as well. But then I attempted to root using the same file, odin got stuck at writing the cache. I tried it several times, but no go.
Having run out of time, I pulled the battery and set it aside to deal with tomorrow. It would be great if some one could point me to the correct image to flash to bring the device back to life.
As background, my last Samsung device was a Vibrant that I flashed repeatedly. Back then I didn't need to select a ROM, as there was a dev section full of them. Now I need a pointer to the correct firmware, and maybe some words of wisdom. I think the original firmware was NB5, and the OTA was ND2. I'm afraid that I was too excited to b quite organized enough to write this stuff down.
I'm uncertain whether I would prefer to flash back to the original and root, or flash to the newer firmware and wait and hope for the root issue to be resolved by Chainfire. Suggestions?
Click to expand...
Click to collapse
That's the problem I've been writing about for a week. The new OTA update (t900ueuand4) doesn't work with auto-root and crashes exactly where yours did.
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Can you give me the link for the new chainfire file that must have been re-written in the last 2 days
---------- Post added at 11:32 PM ---------- Previous post was at 11:28 PM ----------
gbr357 said:
Yes it was that file off chainfire's site. Either something got fixed or the fact that I wasn't rooted before the OTA??
Click to expand...
Click to collapse
Just re-downloaded the chainfire file and it's identical to the file I got 10 days ago dated May 10th. If you had success flashing it with the firmware t900ueuand4 installed at the time of rooting, then I'll give it a shot too.

JJMT said:
Yes. I am rooted and it says official. What's more, it checks for updates, although who knows what will happen when one shows up.
What I have is the ND4 firmware with the NB5 recovery. To get to this state:
1. OTA to ND4.
2. Boot into download mode. Flash the NB3 recovery. (P900XXUANB3-RecoveryImg.tar) It will reboot automatically.
3. Boot into download mode. Flash the root file. (CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5). It will reboot automatically.
4. Boot into recovery mode. Wipe data/factory reset.
I believe at this point we are done. If you do this and it doesn't come up "official", then there must be something peculiar in the back-story. I am happy to answer questions.
UDATE: Forgot to mention - KNOX was disabled by SuperSU.
Click to expand...
Click to collapse
All I had to do, was stop after 3. Didn't require a factory reset. Everything is great

The same here. Used the Note 12 recovery mod to unbrick the tablet.
Flashed the CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5 and it works. :good:
Now oor Samsung tablet pro 12.2 is rooted.

dodo99x said:
Try flashing the recovery from sm-p900 from this post, the one with the filename ending with "b3", then try to root agajn. Should work after that.
http://forum.xda-developers.com/showthread.php?p=50492301
If not, install Kies 3 and do an emergency restore. It will ask for your serial# and download the correct rom and flash it back to stock
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
I ran into a similar issue except my device came up to an error regarding firmware upgrade failed, use kies to recover. I could not get this to work with kies 3. Searching the threads, I found your post. Worked beautifully. The failed attempt did trip Knox. Not sure I care.
Thanks!

[GUIDE] how to root Sph-L710/L710T S3 4.4.2 (updated as of 8/19/2015)

I'm sorry i had the wrong links and because of this i had miss information. So i formally apologize by updating with the proper links.
this first method doesn't work with the Sph-L710T or the Sph-L710 on NJ2/NJ3
First method: You can root the stock 4.4.2 ND8/NDC:laugh:
1st. Make sure your on 4.4.2 ND8 or NDC
2nd. Download Towel Root
3rd. Place Towel Root in sdcard or internal storage
4th. With any file manager find and install Towel Root
5th. Open Towel Root and well root
6th. Go to play store and download https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en and also https://play.google.com/store/apps/details?id=stericson.busybox&hl=en let super user update the binary
7th. Flash any recovery you want {personally i went with PhilZ Touch (this was before PhilZ had a root Option)}
8th. Enjoy your rooted stock 4.4.2 ND8/NDC
Down below is one more way too root Stock ND8/NDC/NJ2/NJ3 or NF4/OA3 (L710T) and basically any other update
(link to the almighty ODIN)
Second Method: mostly recommended
1st. Odin flash TWRP
2nd. In Odin choose PDA, PA or AP then select the TWRP Tar you just downloaded
3rd. Make sure Auto reboot is unchecked (also at this time your s3 should be in download mode)
4th. Hit start and let Odin let it finish!!
5th. Hold power button to turn off your S3, after it turns off about 10 seconds later it will turn back on to the battery charging screen so before that quickly hold Volume+ and Home, to boot into recovery
6th. now your in TWRP
7th. so to root your stock rom with TWRP flash the following file SuperSU.zip by Chain fire (pro tip. Install any other custom recovery the same way I did for TWRP above if it is in .tar format)
and here is Philz recovery for the D2Lte 6.48.4 ( which you must flash in TWRP)
and here is TWRP that was made specifically for the D2Rephersher/triband/L710T TWRP (which you must flash in a recovery)
Third method Most recent.
Hidyman said:
This is in reference to Samsung Galaxy S3 for Boost Mobile SPH-L710.
Just want to let anyone out there that updated their Boost S3 to L710VPUC0J1 know that you can still root and/or ROM your phone.
Use the instructions to (use Odin to) update the recovery to TWRP first (in the second set of instructions). I had trouble trying to go right to PhilZ Recovery (which I believe is based off of ClockWorkMod). I Had to do the TWRP (twrp-2.8.7.0-d2spr.img.tar) first.
It was the only way to get it to actually accept the recovery, not sure why, maybe because the latest Samsung firmware fixed an exploit or two.
This is an older phone, but it is still a viable one.
I hope this helps someone out there.
It took me a while to figure this quandary out.
As always this WILL flag KNOX, but I'm sure this won't be an issue at this date and time (8/2016).
Click to expand...
Click to collapse

work on ND8 rom? sprint phone?

Tekone said:
work on ND8 rom? sprint phone?
Click to expand...
Click to collapse
i want to say yes but towel root does come with a warning that it might brick your device.....but i want to say yes since most things that can be done to the ND8 can be done to the NDC and also in reverse order.....so try it and report back it will be good to know if it works on both bootloaders

Sprint S3 Android 4.4.2 ND8-It works!
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!

oops
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.

henhun said:
Rooted the phone in one click. Unfortunately, I lost all data (no 3G or 4G connection). Did I goof? I'm looking in the stickies and can't seem to find an answer. I'd appreciate any help I can get.
Click to expand...
Click to collapse
ND8 or NDC? have you tried updating your profile/PRL?

6th_Hokage said:
ND8 or NDC? have you tried updating your profile/PRL?
Click to expand...
Click to collapse
Ya know. People keep talking about ND8 and ND___. I have no idea what that means. I know I should be embarrassed.
UPDATE: FIGURED IT OUT, BASEBAND VERSION. GOTCHA. IT IS NDC.
I was JUST coming back to update my post. I DID update the PRL and restarted my phone. That seems to have done the trick. Thank GOD I got my data connection back!! It worked. Even though I found the info somewhere else, thank you so much for the quick reply. PRL update fixes the problem. You're awesome.

I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app

jbnorton0524 said:
I used it before i had a custom recovery. And on reboot i wouldnt have root. After i ran it root checker told me i was rooted then reboot killed. I installed philz and all was ok
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
many users of basically the same phone report different things with every root method out there. If it worked for you that's great tell other users what you did for it to work and if it didn't work, then ask for help and you will get help; some people don't have success with any method while others do with all of the methods.....my phone falls under every method.....

Successful Towelroot on VM Galaxy S3 4.4.2.NDC
6th_Hokage said:
you can root the stock 4.4.2
first step make sure your on 4.4.2
second step download Towel Root
third step place Towel Root in sdcard or internal storage
fourth step with any file manager find and install Towel Root
fifth step root
sixth step go to play store and download Superuser (Chainfire) and also Busy Box (Stericson) let super user update the binary
seventh step flash any recovery you want personally i went with Philliz Touch
eighth step if you want flash a custom rom now if not enjoy your rooted stock 4.4.2
Click to expand...
Click to collapse
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is usafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave

dave260 said:
Straight forward, fast and easy. I did notice the following:
1) Updating binary reported it did not successfully install. I've seen this before on other devices, but everything worked well. Ext SD and Camera all OK. Everything works fine so far - Titanium, Nandroid, Root Browser, etc.
2) At one point, I was directed to install Busy Box. Having done this on other devices, I said "Yes" and installed it.
3) I see that my device now shows Device Status as Custom ( was Normal before, if I remember correctly). Is this due to Busy Box?
4) Is Device Status the only way to know the KNOX Status? I see no yellow triangle as I did on my Galaxy Reverb.
5) I got a Google warning to uninstall Towelroot since it is unsafe and a security exploit. I understand that.
I would like to verify the KNOX status and if tripped in the Towelroot process, to let potential users know of that possibility.
Thank You! And thanks to everyone who has continued to work on keeping root free!
Dave
Click to expand...
Click to collapse
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the binary (<---completely forgot to fix that) you must hit the option normal not TWRP/CWM

churninern said:
I just used this method to root my Sprint S3 running Android 4.4.2 and ND8, since my USB port is on the fritz, and it worked successfully. I have root, and was able to do a full apps backup with Titanium Backup, and gained root access in ES File Explorer. Next, download and install a custom backup. Thanks, great job, and could not have been made easier to do!
Click to expand...
Click to collapse
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.

Darkangels6sic6 said:
That's great news because same boat here. It worked on 4.3 as well.
I had the phone hacked before and something must not be fully stock so the Ota fails.
I downloaded a package and mobile odin should flash it properly and then I can root it with this again and install a nice modified TouchWiz rom.
Click to expand...
Click to collapse
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all

Knox Counter and "Device Status"
6th_Hokage said:
Knox only notifies Samsung that your device isn't stock anymore not necessarily rooted like with a custom recovery and then flashed mods and what not but if you Odin the stock rom it resets the counters so Samsung will never know....and that i have noticed TowelRoot doesn't trip that counter.....only the recoveries and when you update the recovery you must hit the option normal not TWRP/CWM
Click to expand...
Click to collapse
Thanks for your response. I may be over thinking these indicators. All I did was Towelroot, successfully. On the phone, the "About Device, Status" now says CUSTOM (was "Official"). The Knox counter according to app "Phone Info" shows Knox Counter at 0x0. As you said, since the counter is not tripped, should be no problem on warranty. So then Device Status CUSTOM is not a problem? I'm not really worried about warranty at this point, but I think I'll hold off further mods for another 6 moths.
Thanks again for your help!

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
Thanks. I tried the md8 and mk3 "mk3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all.
I'm guessing maybe I should install twrp. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most md8 Roms want you to odin or flash an md8 base.

Darkangels6sic6 said:
Thanks. I tried the ND8 and MK3 "MK3 is what it's on". Both just restart and get stuck on splash screen :/.
I have to go to download mode and and restart it that way to boot system back up.
Do you have any other suggestion. I'm not sure what part of the system is altered. It seems like a stock recovery and it's stock firmware "now rooted". Maybe the kernel.
I can't use USB at all
I'm guessing maybe I should install TWRP. Then install a stock zip or try out a 4.3 rom that way. I would like to get to md8 one way or another. Most ND8 Roms want you to Odin or flash an md8 base.
Click to expand...
Click to collapse
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be

6th_Hokage said:
just a quick add on Mobile Odin and stock ND8/NDC don't mix at all
Click to expand...
Click to collapse
6th_Hokage said:
cause they need the ND8 base to work as intended...my suggestion would be to get the usb port on your phone fixed but i don't know how expensive that will be
Click to expand...
Click to collapse
I was afraid you would say that.

Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!

strangelady said:
Holy crap. May I say, I am quite impressed. I never planned on rooting my S3 (I like it that much!) but this just looked so damn easy to do and it was!
For the curious! I have a Virgin Mobile S3, and I'm on Kitkat 4.4.2, baseband NDC. Verified root with Root Checker Basic. No problems with mobile data.
Many thank yous, 6th_Hokage!
Click to expand...
Click to collapse
your welcome strangelady and if you want check out the links in my signature area for other cool stuff

added two more t=root methods

[Download]AT&T Kitkat OTA file

Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed

bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!

Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app

bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.

stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app

@bkong
Link is bad, clicking it links to a url with "..." in the middle

CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.

bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?

Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:

Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms

Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.

DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?

bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!

bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.

stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol

Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.

DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.

Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?

So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.

stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.

AT&T Lollipop OTA CFG + Update.zip {{{Get Your Flash On}}}

Get your lollipop here. Below is the full OTA from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
For now this zip is useless until have root. It's here to be available when we are able to use it.
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.

You...are...awesome!!!

Update.zip added.

what is this? I thought we only have a temp root

darkbots said:
Update.zip added.
Click to expand...
Click to collapse
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...

Deleted

darkbots said:
Get your lollipop here. Below is the full ota from 4.4.4/KTU84P/N910AUCU1ANIE to 5.0.1/LRX22C/N910AUCU1COC4.
I have also include an flashable update.zip with the ota. Please read info below.
OTA/cfg only:
https://mega.co.nz/#!mZB3QBZR!tsWqPGQynF_AgWxsO8xZJy5u4pqfb8HKv5jV_SonVI8
Update.zip: Custom recovery only: {{{{WARNING UNTESTED}}}} Although it's most likely perfect it's untested. See update.zip info below.
https://mega.co.nz/#!jQwxkaIb!UBrf26IRhdSgGnk935qE4GejP-wZG7HR4uZOIb5V3cA
OC4 odin Tar newest:
COMING SOON Waiting for Kies to update version
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Update.zip INFO
In the past pre-rooting the zips was causing WiFi in to fork,so the zip is not rooted.
The update.zip and the actual cfg are almost identical with a few exceptions. They update identically using the same method.
Both use a series of update patches to inject new code in existing apk's some do get fully replaced but very few. So for this reason rooting using them needs to be done in a specific manner. You can thank Samsung/KNOX and SELinux for that.
How to upgrade with update.zip and keep root
It's best to be 100%stock before updating.
Remove SU app from system,do not remove the>>>>>>binary<<<<<<
Boot recovery,flash update zip,reboot
Install SU zip after rom fully boots and profit.
Click to expand...
Click to collapse
Now obviously anyone on these forums knows the deal here, if it's flashable it's risky, but this raises some flags that need addressed.
This is for the AT&T yes? If I'm not mistaken, this device has a locked bootloader, so then it goes without saying that your custom recovery flash only is untested. So is the expectation that users here are supposed to test it?

This is only the stock update put in a zip, then I cleaned some of the updater. This way if your on stock kitkat with custom recovery you can take the ota. There's zero risk here other than what Samsung messed up. I assumed it would be obvious we can use them yet because of not having root. I've done this a lot for several devices it's crazy easy to do,and you only need to change its zip and clean the updater.

rondoo said:
Hi bro! I changed the name of .cfg and on recovery stock says failed to verify signature...
Click to expand...
Click to collapse
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.

darkbots said:
You can't change the name extention or open the cfg .Put it on a sd, use stock recovery sd install option.
Click to expand...
Click to collapse
Did it and...
failed to verify whole-file signature
signature verification failed

download again you have a corrupted file

having same problem here.
failed to verify whole-file signature
signature verification failed.

I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.

waqas.ahmad said:
I just bought note 4. This is AT&T model firmware version N910AUCU1BNK3. This is unlocked phone. I am using this phone in Pakistan. Currently it is with Kitkat. Once I am trying to update to lollipop through OTA it shows its is lastest firmware but I know Lollipop already released. Please help me how to update my phone ? I want my phone keep unlock as I am using in Pakistan.
Click to expand...
Click to collapse
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.

annttiigs said:
you can not update at&t version outside of US. I struggled a lot and finally gave up and installed lollipop (5.0.1) manually using files shared by the guys from here.
Click to expand...
Click to collapse
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?

waqas.ahmad said:
If I update manually, will my phone SIM Locked? Currently it is unlocked.
What about Knox? will is break?
Can you share me the firmware link which I exactly download and install in my phone?
Click to expand...
Click to collapse
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.

annttiigs said:
I have used this one and and no issue:
http://forum.xda-developers.com/note-4-att/general/to-stock-files-latestcoc4-build-t3107391
but all is on your own risk.
Click to expand...
Click to collapse
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?

waqas.ahmad said:
I have downloaded the firmware from the link you sent me.
You tried to install it on unlocked phone ? Firmware Version N910AUCU1BNK3?
Do I need to load all files or just AP is ok ?
Click to expand...
Click to collapse
Plase follow the discussion there. Those all were my questions as well. You need to put each file in its location in Odin means you will use all files. My phone was unlocked and I dont remember my fw version. Please read the discussion there.

hi this link for CFG is dead , can you reup link ?>

+1 Please re-upload

New to Note 4 - Boot Loader / Root Confusion

I just picked up my Note 4 and have not even turned it on yet.
I have a few questions after reading various multi-page threads that i am unclear on.
I was looking at the threads and see that ChainFire is what to use to root.
http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
It states that Stock Recovery is installed, does this mean that I can use that recovery to flash TWRP or will i have to use ODIN for that?
What version of ODIN needs to be used?
Is there any version of Root that does not trip KNOX?
I am confused about the different boot loaders / Broadbands (basebands?).
How do I find out what boot loader / Broadband i am on?
I am reading a lot of reports that 5.x is giving very poor battery life. Is that the Case Still?
Thanks for any help Ya'll can give.

You're gonna have to open her up to see what's I under the hood just don't let it update.
Depending on what build you find, CFAutoRoot is fine to root with up until OG5.
If it has OB7 or less, you can Odin back to KitKat NK2. Don't even try if is above OB7.
OG5 would require Beastmode kernel with exploit to root but you still need to flash SuperSU zip for that OG5 to root once the kernel is flashed.
Sent from my SM-N910P using Tapatalk

Android is 4.4.4
Baseband N910PVPU1ANK2
what other information do you need?

Dragonfyr said:
Android is 4.4.4
Baseband N910PVPU1ANK2
what other information do you need?
Click to expand...
Click to collapse
You're options are wide open, so what I tell you depends on you want.
NK2 is KitKat. You can root and install Xposed or flash a custom NK2 ROM and run Xposed. KitKat does better on battery all around. Kernel can be permissive or enforcing. You can run Xposed on either Odex or deodexed ROM. Lollipop requires mods to run enforcing kernel for some apps to work and Xposed only works on deodexed ROMs.
If you prefer lollipop, I'd need more feedback to advise your best options. Xposed is limited to 5.0.1 deodexed only. If you want to retain the capability to return to KitKat, you'd want the OB7 bootloader if going that far.
Most likely, to root, you can use Odin 3.07 or the latest. Use CFAutoRoot for root. For TWRP, you could Odin or use apps like Flashify or TWRP manager to install TWRP. Once you have TWRP, make a nandroid backup and then you can flash a custom NK2 ROM.
Going to lollipop would require Odin to OB7 stock tar (most likely; because you're one of the lucky ones with bootloader and KitKat as well- although OB7 is almost as good and can be reverted to KitKat).
Maybe that answered your questions and can get you started. It's ok to ask again before you start to be in the know before making a mistake.
Edit: if you settle on a lower build, you can avoid the update prompts by deleting /cache/fota folder.
Sent from my SM-N910P using Tapatalk

Thank You so much for the information
I will stick with KK for now.
How can i tell what Boot Loader i have?

Dragonfyr said:
Thank You so much for the information
I will stick with KK for now.
How can i tell what Boot Loader i have?
Click to expand...
Click to collapse
If you using a stock build.prop, it's listed as build in About device.
Galaxy Tools will tell you for sure on a custom build (sometimes build gets replaced by developer name of ROM).
Sent from my SM-N910P using Tapatalk

how do i stop the software updates?
i already have system updates turned off

Dragonfyr said:
how do i stop the software updates?
i already have system updates turned off
Click to expand...
Click to collapse
Root Explorer
System/priv-app/SprintDM.apk
Remount system folder as Read/Write
rename to SprintDM.apk.bak
Remount to Read only
Reboot phone

thank you any ideas as to what its trying to download?

Dragonfyr said:
thank you any ideas as to what its trying to download?
Click to expand...
Click to collapse
Lollipop OTA

xxSTARBUCKSxx said:
Root Explorer
System/priv-app/SprintDM.apk
Remount system folder as Read/Write
rename to SprintDM.apk.bak
Remount to Read only
Reboot phone
Click to expand...
Click to collapse
Renaming that file did not work,
When i go to WiFi it starts a Software update automatically

Dragonfyr said:
Renaming that file did not work,
When i go to WiFi it starts a Software update automatically
Click to expand...
Click to collapse
Did you uncheck the first box in System update, and leave the second one checked?

yes

id also goto Recovery and Wipe Dalvik Cache and cache.
When my phone starts up after a reboot.. that will appear initially after it connects to WiFi.. but the Important thing is that it Goes Away and isnt downloading the OTA and then throwing the Install Screen in your face.
Can you verify that after a restart(or after the one you just did) that after it connects to WiFi... it will appear.. but then goes away and nothing else appears saying that its downloading the Update? If so, thats what you want to happen.

I did wipe both caches
it keeps saying software update downloading, i let it run for about a minute before i killed the WIFI

Dragonfyr said:
I did wipe both caches
it keeps saying software update downloading, i let it run for about a minute before i killed the WIFI
Click to expand...
Click to collapse
If you're rooted, use a root browser and navigate to /cache, open and long-press fota folder; delete. No more update.
Edit: KitKat is /data/fota
Lollipop is /cache/fota
Sent from my SM-N910P using Tapatalk

there is no /cache/fota folder i can locate
there is a /data/data/com.localfota folder
There is also a /data/FOTA folder that contains update.zip

Dragonfyr said:
there is no /cache/fota folder i can locate
there is a /data/data/com.localfota folder
There is also a /data/FOTA folder that contains update.zip
Click to expand...
Click to collapse
delete that

xxSTARBUCKSxx said:
delete that
Click to expand...
Click to collapse
Deleting the update.zip and restarting just caused it to start downloading again.

Dragonfyr said:
Deleting the update.zip and restarting just caused it to start downloading again.
Click to expand...
Click to collapse
I was waiting for that post.. SprintSyncMLSvc.apk .bak that file too, shouldnt have to but in your case, that needs a .bak at the end as well