[Q] New Note N9005, can I root? - Galaxy Note 3 Q&A, Help & Troubleshooting

So today I got my new Note 3. I've been doing some reading but am not sure about the Knox issue.
It's Android 4.3, Baseband - N9005XXUBMI5, Build - JSS15J.N9005ZHUBMI7, and I am being offered an update.
I'm thinking from the threads I am already above the version that let's De La Vega rooting work without tripping Knox? Can I downgrade using Odin, root the phone and then get updates?
Also, what is SELinux status - says it's 'enforcing' - I'll do some searching tomorrow.
Once I worked out how to shut the 'Talkback' voice up it's been enjoyable - nothing quite like having a screen non-responsive because every time you try to do something she yabbers at you in a foreign language. As soon as that turned off the phone behaved properly - very quick too.
More tomorrow - end of a long day here.

need help with this myself
Trying to root this same phone as well.
AP: N9005ZHUBMI7
CP: N9005XXUBMI5
CSC: N9005ZZHBMI7
Can't seem to find any working links for those though.

Rdlv works for pre mj1 firmwares. After mj1 kingo is supposed to work. But didnt for me. Just come to the dark side and trip knox

Journyman16 said:
So today I got my new Note 3. I've been doing some reading but am not sure about the Knox issue.
It's Android 4.3, Baseband - N9005XXUBMI5, Build - JSS15J.N9005ZHUBMI7, and I am being offered an update.
...
Click to expand...
Click to collapse
makaveli72 said:
Trying to root this same phone as well.
AP: N9005ZHUBMI7
CP: N9005XXUBMI5
CSC: N9005ZZHBMI7
Can't seem to find any working links for those though.
Click to expand...
Click to collapse
DO NOT take any update (and also disable the separate SECURITY update).
Read the UNIVERSAL ROOT DE LA VEGA thread.

Found the security update one but it's been on for a day... crossing fingers. I have read a lot of the RDLV thread - one thing I'm not sure of - if I root successfully does an OTA official update trip Knox?
I guess there's a question behind that - if I root and remain on stock ROM, will I get an update at all?
Not particularly worried about it. I figure I'll remain stock for a bit in case the phone plays up but will shortly be rooting and custom ROM'ing like I did with my S3.
Pretty good battery so far - all the setup stuff and configuring and only down to 48% after 16 hours.

double post

Journyman16 said:
Found the security update one but it's been on for a day... crossing fingers. I have read a lot of the RDLV thread - one thing I'm not sure of - if I root successfully does an OTA official update trip Knox?
I guess there's a question behind that - if I root and remain on stock ROM, will I get an update at all?
Not particularly worried about it. I figure I'll remain stock for a bit in case the phone plays up but will shortly be rooting and custom ROM'ing like I did with my S3.
Pretty good battery so far - all the setup stuff and configuring and only down to 48% after 16 hours.
Click to expand...
Click to collapse
No updating via OTA won't trip KNOX, you'll lose root though.
Rooting means your device (depending on the method used) will show custom status and cannot receive OTA updates, but they work via KIES still. URDLV shows Official iirc, so you may be able to update OTA with no issues, but as I said you'll lose root. There are methods of using Mobile ODIN to update and re-root and keep KNOX preserved as well.. But I tripped mine instantly, so not sure how you'd go about it all.
Battery on the Note 3 is a blinder, you think Stock is good, wait til you decide to trip KNOX and install a custom ROM, then you'll see how powerful the battery actually is haha

Well, I will keep reading. If I find a way to do it I will post back here about it. I guess my 1st port of call is the RDLV thread - I need to know if I will trip Knox anyway - if so I'll give it maybe a month to be sure phone isn't faulty then root and custom it. I do miss Greenify...
I'm used to good battery - I was using Purelook 8 on my S3 and getting more than 4 days on med to light use.
And now there's a whole new world to explore...
Another answer I am looking for - is there a way to do a Nandroid backup without root? I want to try some things but don't want to lose all i have done so far.

Journyman16 said:
Another answer I am looking for - is there a way to do a Nandroid backup without root? I want to try some things but don't want to lose all i have done so far.
Click to expand...
Click to collapse
Helium is a good non-root backup tool, although I think you need the premium version for all the features.

Finally Rooted! N9005
Much thanks to @brangalm for his step by step breakdown in the RDLV 0.5 thread; I was able to find my way and got my first Android device (the Note 3 SM-N9005 32GB hdd, 3GB mem, Snapdragon cpu Behemoth of a phone) rooted. His POST really made the process much more approachable.
Only thing, at step 9 and 10 in my case I had to use forward slashes / instead of \ backslashes.
For ex.
[email protected] /cygdrive/c/Users/MaKaveli/Desktop/Note3
$ cd C:/Users/MaKaveli/Desktop/Note3
And
[email protected] /cygdrive/c/Users/MaKaveli/Desktop/Note3
$ ./URDLV.sh full C:/Users/MaKaveli/Desktop/Note3/N9005ZHUBMI7_N9005ZZHBMI7_N9005XXUBMI5_HOME.tar.md5
And at step 22 I would recommend leaving the phone alone for at least 10 mins while it does its thing (rebooting etc.) After seeing 'Pass' in Odin the screen was blacked out for some time..so I say just leave it for a while.
Besides that the root process was straight. Both Knox statuses are 0x0 with Custom status. Woot!
I would thank @brangalm directly in the RDLV 0.5 thread but the xda-dev forum has me as a newb (rightfully so) and has restricted me posting in the developers section for now.
My phone info. for whom it may concern.
Model: SM-N9005
Country: Hong Kong
Version: Android 4.3
Changelist: 1626679
Build date: Wed, 11 Sep 2013 10:54:57 +0000
Product Code: TGY
PDA/AP: N9005ZHUBMI7
CSC: N9005ZZHBMI7
MODEM/CP: N9005XXUBMI5
PS: downloading my stock fw from terafile.co via sammobile.com was a P.I.T.A. Took multiple tries and lots of patience before getting a decent copy.

Congratulations and happy flashing.

Related

[Q] OTA no longer working with Triangle Away??

Hi all,
Well for fear of the classic 'try google' or 'why not search these forums you lazy git' here goes with my post.
I have searched for hours and hours on end and havent found anything presise, but just wanted others experience and if I'm pissing upwind with this.
I installed stock Rom on my note 3 version:
AP: N9005XXUEND3
CP: N9005XXUENC2
CSC: N9005OXAEND1
I used CF root method then Triangle away to reset counter and ticked 'run tracker' to enable OTA updates.
Now after a reboot it worked perfect and my device status was 'Official' allowing OTA updates.
Well I'm assuming an update occurred of somethings happened as my device is now back to 'custom' and therefore I cant check for OTA updates.
So question is; is there something else I should be doing or another workaround or has a latest update pooped Triangle Away. I cant use Kies to check for latest firmwares as it just doesnt connect to my device, so have to check for latest firmware via sammobile.
Any advice/help appreciated bigly
I am fairly new to Android, and love it but its a huge learning curve, one I am enjoying but still shady in areas.
cheers

New to Flashing, Want to install Eclipse [Note 3]

Hello everyone.
Is there a one true guide to installing a ROM on my Note 3? I'm running a T-Mobile N-900T. It seems that after browsing the web, I've seen so many different ways to install a ROM that I'm extremely hesitant to try one on the off-chance that it is no longer supported and may brick my device. This is a non-warrantied phone (bought it on Swappa) so I only get once chance if I end up Hard Bricking it, so my fear level is at the absolute highest.
I wanted to run Eclipse Note 3 TW Rom (found here: http://forum.xda-developers.com/showthread.php?t=2620723) because it's a nice simple ROM that retains S-Pen function and removes all the bloat and stuff. However, I noticed that it says "This is based off of 4.4.2 NC2 for Verizon Wireless." Does this mean it won't work with a T-Mobile Note 3?
This is as far as I got in towards the process before I stopped due to something unexpected:
1) TowelRoot. Rooted it and confirmed with the Root app that it was indeed rooted.
2) Downloaded SuperSU. I installed the binary using the Normal mode since I didn't have CWM or TWRM at the time. It asked me to disable KNOX and it looks like it was fine. I restarted it.
This is where I stopped. After I installed it, it asked me to confirm if I want to confirm allowing Freedom and SetCPU. I did and it continuously started spamming the notification that it was allowed for 20 minutes.
I went into the SuperSU program to see what's wrong and it then told me that the Binary could NOT be found and that I may have to flash my rom back to get it back to normal. It then gave me the error that something was wrong on my phone and that I might have to install something called Samsung Kies to make it better.
I pretty much freaked out at this point and de-installed SuperSU out of fear that I might screw up my phone. Now I'm extremely fearful to do anything without seeing some sort of de facto guide on what to do next.
If it helps, here's the phone information I have. I know that different ROM flashing methods are used for various kernels.
Model: SM-N900T
Android Version: 4.4.2
Baseband: N900TUVUCNB4
Kernel: 3.4.0-660648 | [email protected] #1 | Wed Feb 12 21:31:27 KST 2014
Build Number: KOT49H.N900TUVUCNB4
SE for Android Status: Enforcing | SEPF_SM-900T_4.4.2_0005 | WED FEB 12 21:31:01 2014
Security Software Version: MDF v1.0 Release 2
I have a 128GB Samsung SDXS MicroSD. The phone recognizes 119 GB of it which I know is normal.
Any help or direction would be most appreciated. The world of Flashing has so many roads that my head is spinning and my fear is that I will turn this phone into a $500 brick because I followed the wrong guide.
Thank you.
Best way of flashing a new rom is using "Odin".
dodoqq said:
Best way of flashing a new rom is using "Odin".
Click to expand...
Click to collapse
Thanks.
I do understand that and I have the program, but I can't find any SOLID documentation. I see all these different guides out there and I'm scared that I'm going to pick the wrong one. The ages vary as well, so I don't know if they are still relevant or not.
Not only that, I don't believe that just Odin is enough. There are also prerequisites that are required before I can just up and use Odin. That'st he part that I would hope a decent guide out there would provide me.
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Nanaya Shiki said:
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Click to expand...
Click to collapse
Contact me on Google+, I can help you with this and calm you down about it.
It's +NicholasPhilipChum

[Q] Towelroot no longer works... ideas?

I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks
CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky
CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?
CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse
No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app

[Q] Note 3 (SM-N9005) firmware update in Australia...

Hi There!
The company where I am working provided me with a Samsung Galaxy Note 3 (I have a Note2 on my own, so it was pretty straight forward getting used to it!).
The current mobile status is at it follows:
Bootloader : N9005XXUBMI7
Baseband : N9005XXUBMI6
CSC: N9005XSABMI1
Basically, I'm running under an old version of Android 4.3 . Is there any real reason to update it to a newer firmware (Samsung official, I do not want to mess up with a rooted mobile..it is not my mobile after all) ? Is there any *real* improvement in using the device with KitKat (battery life, smoother, etc) ?
I'm asking that because I am still regretting the moment when I decided to update my N7100 from 4.1.2 to 4.3 (and then to 4.4.2)... so I don't really want to update the Note 3 and regretting the update afterwards... (..and then finding out that no, it is not possible to go back to the previous version).
Last firmware available in Australia is N9005XXUENE3_N9005XSAENE1_XSA : with the official XSA I have some apps for free in the App Store (which comes pretty handy). Perhaps, I may try the New Zealand one too (N9005XXUGNG1_N9005NZCGNH1_NZC) that looks more recent.
Or, perhaps, is there any 100% stable leaked firmware made by one of you, based on an official Samsung rom, lighter, cleaned of most of the bloatwares AND a safe way to root the mobile without tripping the Knox?
Thank you all
Starflex said:
Hi There!
The company where I am working provided me with a Samsung Galaxy Note 3 (I have a Note2 on my own, so it was pretty straight forward getting used to it!).
The current mobile status is at it follows:
Bootloader : N9005XXUBMI7
Baseband : N9005XXUBMI6
CSC: N9005XSABMI1
Basically, I'm running under an old version of Android 4.3 . Is there any real reason to update it to a newer firmware (Samsung official, I do not want to mess up with a rooted mobile..it is not my mobile after all) ? Is there any *real* improvement in using the device with KitKat (battery life, smoother, etc) ?
I'm asking that because I am still regretting the moment when I decided to update my N7100 from 4.1.2 to 4.3 (and then to 4.4.2)... so I don't really want to update the Note 3 and regretting the update afterwards... (..and then finding out that no, it is not possible to go back to the previous version).
Last firmware available in Australia is N9005XXUENE3_N9005XSAENE1_XSA : with the official XSA I have some apps for free in the App Store (which comes pretty handy). Perhaps, I may try the New Zealand one too (N9005XXUGNG1_N9005NZCGNH1_NZC) that looks more recent.
Click to expand...
Click to collapse
This is a really a big question and a long story. No one can tell you exactly which version is better in term of battery life, smoothness... Also there is no official changelog from the Samsung. And there are also many threads discussed about these updates. You have to read and decide yourself.
Or, perhaps, is there any 100% stable leaked firmware made by one of you, based on an official Samsung rom, lighter, cleaned of most of the bloatwares AND a safe way to root the mobile without tripping the Knox?
Thank you all
Click to expand...
Click to collapse
Regarding a safe way to root without tripping the Knox, as your firmware is still MI7, you can use URDLV to root. That will not trip your Knox. You can google for URDLV or start from here: http://forum.xda-developers.com/showthread.php?t=2522858
vndnguyen said:
This is a really a big question and a long story. ... /cut/
Click to expand...
Click to collapse
Mmmh.... make sense your answer, and it's good already that it is not like "stay away from XYZ version". I guess for the Note2 it was more clear that JB 4.3 was not such a step ahead...fro your answer I can guess that no versions are really "flawly" or defective in this way...
vndnguyen said:
Regarding a safe way to root without tripping the Knox, ... /cut/
Click to expand...
Click to collapse
Thanks, I will!

[Q] Rooting Note III Question

Yes, this has probably been gone over ad nauseum throughout the site. Due to time constraints I cannot dig through the forums as much as I'd like, so I'm simply going to ask.
Phone: Samsung Note III (SM-N900V)
Carrier: Verizon Wireless
OS Version: 4.4.2
Baseband Version: N900VVRUCNC4
Kernal Version: 3.4.0
Build Number: KOT49H.N900VVRUCNC4
Hardware Version: N900V.07
It was purchased November 2013 with OS 4.3. Over the summer I accepted the OTA update to 4.4.2. My phone went to hell. Battery gets chewed through like a woodchipper, phone is horribly laggy, antenna connection is always 1-2 bars under where it was prior to update (and doesn't get reception in areas it did before), changes to the UI are less than desirable, etc.
The phone was never rooted, as this was the first phone I've ever had that worked well enough on stock software that I skipped it.
After giving it a few months on the update and trying changes/tweaks within the updated stock software to fix the issues the update caused, I'm at the end of my patience. Contacting support at both Verizon and Samsung was pointless, with one blaming the other for the problems.
What I'd love is to take the OS back to 4.3 and leave it, but in lieu of that I want to root the hell out of it and put a build on without these issues and a better antenna software. I'd prefer not to void the KNOX, but at this point I'd microwave it if it'd help.
I have no backups or root access from before the update to base a root on. I tried towelroot; install button doesn't work and I understand the maker Geohot works for Google now. I started to play with Odin, however the install seems to have an oddly high amount of other software it wants to install, and even after declining those it doesn't want to install (tried 3.09 and 3.10, I'm using Windows 7 w/latest SP and updates). Also, it drives my AV software crazy, so even turning that off and working with it didn't get me very far.
So, at this point, I'm open to most anything to get this crap off my phone, and my only requirement is that I don't brick it.
Options?
Thanks in advance for any help.
HarlockTaliesin said:
Yes, this has probably been gone over ad nauseum throughout the site. Due to time constraints I cannot dig through the forums as much as I'd like, so I'm simply going to ask.
Phone: Samsung Note III (SM-N900V)
Carrier: Verizon Wireless
OS Version: 4.4.2
Baseband Version: N900VVRUCNC4
Kernal Version: 3.4.0
Build Number: KOT49H.N900VVRUCNC4
Hardware Version: N900V.07
It was purchased November 2013 with OS 4.3. Over the summer I accepted the OTA update to 4.4.2. My phone went to hell. Battery gets chewed through like a woodchipper, phone is horribly laggy, antenna connection is always 1-2 bars under where it was prior to update (and doesn't get reception in areas it did before), changes to the UI are less than desirable, etc.
The phone was never rooted, as this was the first phone I've ever had that worked well enough on stock software that I skipped it.
After giving it a few months on the update and trying changes/tweaks within the updated stock software to fix the issues the update caused, I'm at the end of my patience. Contacting support at both Verizon and Samsung was pointless, with one blaming the other for the problems.
What I'd love is to take the OS back to 4.3 and leave it, but in lieu of that I want to root the hell out of it and put a build on without these issues and a better antenna software. I'd prefer not to void the KNOX, but at this point I'd microwave it if it'd help.
I have no backups or root access from before the update to base a root on. I tried towelroot; install button doesn't work and I understand the maker Geohot works for Google now. I started to play with Odin, however the install seems to have an oddly high amount of other software it wants to install, and even after declining those it doesn't want to install (tried 3.09 and 3.10, I'm using Windows 7 w/latest SP and updates). Also, it drives my AV software crazy, so even turning that off and working with it didn't get me very far.
So, at this point, I'm open to most anything to get this crap off my phone, and my only requirement is that I don't brick it.
Options?
Thanks in advance for any help.
Click to expand...
Click to collapse
This is the best breakdown of what you need to do. Click here, scroll till you see the blue outline for NC4 OTA.
Be sure to hit "thanks" on @az_biker link for this tutorial!
Unfortunately this won't work, I've already tried. When running the towelroot installer the Install button is not clickable. The other buttons function normally.
Op did you ever hey the note rooted....did you get the towel root to work
chefb said:
Op did you ever hey the note rooted....did you get the towel root to work
Click to expand...
Click to collapse
No to both, unfortunately.
I've had no issues with towelroot. But for giggles make sure you have install from unknown source checked, and then unlock your developer options and make sure USB debug is enabled, then give it another shot.
Sent from my Baja'd 4.4.2 Note 3
cjamison08 said:
I've had no issues with towelroot. But for giggles make sure you have install from unknown source checked, and then unlock your developer options and make sure USB debug is enabled, then give it another shot.
Sent from my Baja'd 4.4.2 Note 3
Click to expand...
Click to collapse
did you take a ota
I have not, since the leaked NC2 firmware was leaked out. However on my s4 I just used towelroot with the latest NC5 firmware, and it worked flawlessly.
Sent from my Alliance 4.4.2 Note 3

Categories

Resources