Related
To root or not to root
After my last bad experience and also after reading how some have faced issues after rooting their note 3 I was wondering if rooting has any adverse effects on the phones functionality. What are cons of rooting?
There's bit of lag on note 3 which is really annoying for such a beast.
Any advice would be much appreciated thanks
I own N9005 model from O2 unlocked.
riz157 said:
To root or not to root
After my last bad experience and also after reading how some have faced issues after rooting their note 3 I was wondering if rooting has any adverse effects on the phones functionality. What are cons of rooting?
There's bit of lag on note 3 which is really annoying for such a beast.
Any advice would be much appreciated thanks
I own N9005 model from O2 unlocked.
Click to expand...
Click to collapse
There is an update from Samsung that should fix the lag.
I would wait until a good (really) good rom is out
elias2204 said:
There is an update from Samsung that should fix the lag.
Click to expand...
Click to collapse
No update available for my model unfortunately.
CoolDevelopment said:
I would wait until a good (really) good rom is out
Click to expand...
Click to collapse
Hmmm....are current roms poor or no improvement?
I've rooted my phone and hence sacrificed the ability to get OTA update from Samsung... but still, in my opinion, it really depends on the user own personal preference. I root my phone because there's a lot of apps that I am using requires root access (tasker, xposed, etc)...
There are currently not too many custom roms available for note 3 yet (as far as i know), better wait for a while if you're planning on rooting simply for the sake of flashing new rom. :good:
jigzopuzzle said:
I've rooted my phone and hence sacrificed the ability to get OTA update from Samsung... but still, in my opinion, it really depends on the user own personal preference. I root my phone because there's a lot of apps that I am using requires root access (tasker, xposed, etc)...
There are currently not too many custom roms available for note 3 yet (as far as i know), better wait for a while if you're planning on rooting simply for the sake of flashing new rom. :good:
Click to expand...
Click to collapse
But for a popular device like taht i won't take too long
I'm tossing up the same thing and wondering if anyone can answer this question. If I flash back to stock firmware after rooting will device status revert to official thus allowing me to have ota updates again or does setting the knox flag mean I will be system status modified forever?
I know knox flag can't be reverted but what about system status?
Sent from my SM-N9005 now Free
jigzopuzzle said:
I've rooted my phone and hence sacrificed the ability to get OTA update from Samsung... but still, in my opinion, it really depends on the user own personal preference. I root my phone because there's a lot of apps that I am using requires root access (tasker, xposed, etc)...
There are currently not too many custom roms available for note 3 yet (as far as i know), better wait for a while if you're planning on rooting simply for the sake of flashing new rom. :good:
Click to expand...
Click to collapse
Same here.
Although I'd liked to get a good recovery, too. I just rooted with stock recovery, so I can't make a full nand-backup so far. I tried xposed yesterday, but it didn't work. And as long as there isn't a working recovery option (except for going back to stock and installing my apps again vs. installing the full OS including apps and settings), I probably won't try xposed again. But I do miss the "skip tracks with volume rocker" feature.
Mikegrmn said:
Same here.
Although I'd liked to get a good recovery, too. I just rooted with stock recovery, so I can't make a full nand-backup so far. I tried xposed yesterday, but it didn't work. And as long as there isn't a working recovery option (except for going back to stock and installing my apps again vs. installing the full OS including apps and settings), I probably won't try xposed again. But I do miss the "skip tracks with volume rocker" feature.
Click to expand...
Click to collapse
According to this website xposed should work? Are you using version 2.2?
Sent from my SM-N9005 now Free
Which is the safest way to root please?
My main reason for rooting is to reduce lag and install custom ROMs, at the moment their aren't many ROMs to choose from but I'm sure it won't be too long before that changes.
Also My phone is from o2 and they are one of the carriers who still have their ugly logo bootup at startup, shut down which is very annoying.
Also if things go wrong I can still revert back to stock via Odin?
Sent from my SM-N9005 using Tapatalk 2
Auto root by chainfire is the safest and easiest way ti root.
Sent from my SM-N900 using Tapatalk 4
riz157 said:
Which is the safest way to root please?
My main reason for rooting is to reduce lag and install custom ROMs, at the moment their aren't many ROMs to choose from but I'm sure it won't be too long before that changes.
Also My phone is from o2 and they are one of the carriers who still have their ugly logo bootup at startup, shut down which is very annoying.
Also if things go wrong I can still revert back to stock via Odin?
Sent from my SM-N9005 using Tapatalk 2
Click to expand...
Click to collapse
Rooting or putting a custom rom(based on touchwiz) won't probably change anything.
Sent from my SM-N9005 using xda app-developers app
Yes that's true simply rooting wont get rid of lag however my main questions are which is the safest way to root and would I be able to flash generic rom via Odin? It's been awhile since I used Odin.
Sent from my SM-N9005 using Tapatalk 2
Ever time I consider rooting I come across post were user bricked phone. This is really of putting don't fancy bricking my phone. However can't do with lag which is very annoying.
Which is the simplest and safest method of rooting?
Not worried about knox my Model N9005 on MJ3 FW, unlocked version from the UK. Thanks
Rooting does not brick your phone. Only users who don't read the instructions properly bricks their phones.
I have been rooting andriod phones since Samsung S2 with no bricks.
Rooting gives you 'Admin' rights on your phone and I want / need that to have full control of my device.
Rooting does not stop OTA updates but you will need to re-root for every new update.
Sent from my SM-N9005 using XDA Premium HD app
I had the same dilemma. I rooted my Note 1, flashed mods & ROMs, and it was eventually what I wanted. It was, however, locked in that version. I had no time to play with it any more, so left it.
On buying the Note 3, I flashed a stock ROM for the Note 1, got the updates, and it was much better than what I had customised. I guess I had my customised ROM earlier than any OTA update, so did benefit.
The other aspect is a firewall. You can now block apps from Mobile data access (although it is tedious), but not from WiFi access. You can, however, block the access that apps have to your data (although also tedious), so at least you may be safer.
Finally, we have the bloatware on the device. This generation of Andoid seems a bit better behaved than previous ones, and I can disable a lot of the stock apps, which is good. I am not finding any wakelocks (or at least not a great deal), and battery life is very good overall.
So, for me, I would like to have a firewall, but as for the rest of the system, it is perfectly good for me, and I have no current plans to root this device.
What's the easiest way of disabling stock apps such as trip advisor, flipboard, ant bloatware etc?
Sent from my SM-N9005 using Tapatalk
dholms said:
What's the easiest way of disabling stock apps such as trip advisor, flipboard, ant bloatware etc?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Unfortunately some of the ones you listed cannot be turned off in the app manager. Many other apps, can however be turned off. Once I rooted I deleted most of the third party nonsense and froze most of the extra Samsung apps.
Techweed said:
Unfortunately some of the ones you listed cannot be turned off in the app manager. Many other apps, can however be turned off. Once I rooted I deleted most of the third party nonsense and froze most of the extra Samsung apps.
Click to expand...
Click to collapse
Do you keep Knox counter at 0x0 if you fiddle with deleting stock apps?
Sent from my SM-N9005 using Tapatalk
I have a question, I am experiencing random freeze where my screen will just freeze, will not respond to my touches, I was on mi7 rooted it using Rdlv, then used the mobile odin method to upgrade to upgrade it to mj7 in the hope that, these freezes goes away. Afraid that the issues is still there.
From what i have seen so far these freezes happens when my signal bar is fluctuating.
i have done numerous factory resets and re flashed firmware too, yet the issue doesn't seems to go away.
Can someone please help diagnose the exact cause of this. Seems like some other people are also having the same issues
http://forums.androidcentral.com/sa...te-3-starting-lock-up-freeze-lock-screen.html
swagatsourav said:
I have a question, I am experiencing random freeze where my screen will just freeze, will not respond to my touches, I was on mi7 rooted it using Rdlv, then used the mobile odin method to upgrade to upgrade it to mj7 in the hope that, these freezes goes away. Afraid that the issues is still there.
From what i have seen so far these freezes happens when my signal bar is fluctuating.
i have done numerous factory resets and re flashed firmware too, yet the issue doesn't seems to go away.
Can someone please help diagnose the exact cause of this. Seems like some other people are also having the same issues
http://forums.androidcentral.com/sa...te-3-starting-lock-up-freeze-lock-screen.html
Click to expand...
Click to collapse
If you are still rooted you can flash this it might help https://www.dropbox.com/s/artjwhxli313f7n/V3stockui-1.zip
Hi although I am rooted, I am on stock recovery. I was wondering if I can push this into system apk and set permission. You have given me stock ui or its a new version of stock ui
Sent from my SM-N9005
swagatsourav said:
Hi although I am rooted, I am on stock recovery. I was wondering if I can push this into system apk and set permission. You have given me stock ui or its a new version of stock ui
Sent from my SM-N9005
Click to expand...
Click to collapse
Yeah it's the latest one but don't know if you can push it into system i think it's only for custom recovery so i wouldn't risk it just in case there may be a small chance it will trip knox
Knox will only Get triggered if you had custom recovery of try yo root if the bootloader is Mj7.
Sent from my SM-N9005
Do you think it's the system ui which is the cause.
Sent from my SM-N9005
Is there any way to know who the culprit is
Sent from my SM-N9005
swagatsourav said:
Do you think it's the system ui which is the cause.
Sent from my SM-N9005
Click to expand...
Click to collapse
May well be if not it could be a fault with the phone
I am almost confirmed now the freezes occur when the Phone's signal fluctuates. Not sure what is the dependency of that with the screen. Strange thing is, you can lock and unlock your screen, touch works fine, but it's after that for some time. Can some one please help me. This is driving me nuts
Sent from my SM-N9005
Thanks in advance. I did search
Sent from my SPH-L720 using XDA Premium 4 mobile app
cinnamngrl said:
Thanks in advance. I did search
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CF-Autoroot and Saferoot both appear to work for those that've used it. BUT CF will trigger knox flag. And saferoot 'may not' depending on how you got your update. But Saferoot 'should' work without knox trigger and if the past is any indication if it doesn't it 'should'n't' harm anything. I would try Saferoot 1st.
Why not try on your system and report back. Seems every device is taking the 4.4.2 update(s) differently.
leaderbuilder said:
CF-Autoroot and Saferoot both appear to work for those that've used it. BUT CF will trigger knox flag. And saferoot 'may not' depending on how you got your update. But Saferoot 'should' work without knox trigger and if the past is any indication if it doesn't it 'should'n't' harm anything. I would try Saferoot 1st.
Why not try on your system and report back. Seems every device is taking the 4.4.2 update(s) differently.
Click to expand...
Click to collapse
So I don't need a different program? well we'll see
cinnamngrl said:
So I don't need a different program? well we'll see
Click to expand...
Click to collapse
The Safetoot thread had instructions for its use. For cf auto root that thread too had instructions.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Safe root.
cinnamngrl said:
Thanks in advance. I did search
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Check out this you tube link for rooting your phone safely.
http://www.youtube.com/watch?v=O8DFjI9AEEA
Check out this you tube link for rooting your phone safely.
This is 4.2 .2 and it's not safe root
Sent from my SPH-L720 using XDA Premium 4 mobile app
I'm pretty sure saferoot has not been updated to work on the Sprint 4.4.2 Kit Kat update, but I didn't wait and rooted with cf autoroot instead since I tripped knox back on MJA.
cruise350 said:
I'm pretty sure saferoot has not been updated to work on the Sprint 4.4.2 Kit Kat update, but I didn't wait and rooted with cf autoroot instead since I tripped knox back on MJA.
Click to expand...
Click to collapse
how long does it usually take?
I just did it the other night, and it took a few minutes, mostly just waiting for phone to reboot
Sent from my SPH-L720 using Tapatalk
leaderbuilder said:
CF-Autoroot and Saferoot both appear to work for those that've used it. BUT CF will trigger knox flag. And saferoot 'may not' depending on how you got your update. But Saferoot 'should' work without knox trigger and if the past is any indication if it doesn't it 'should'n't' harm anything. I would try Saferoot 1st.
Why not try on your system and report back. Seems every device is taking the 4.4.2 update(s) differently.
Click to expand...
Click to collapse
So you're saying Saferoot may work on NAE? I'm willing to try it but if it doesn't work, I don't want anything getting messed up so I'm asking upfront.
Also, where is this thread regarding saferoot? I've searched through our forum and can't find it.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Here you go First find and look at the reported successes section.
DJMaj07 said:
So you're saying Saferoot may work on NAE? I'm willing to try it but if it doesn't work, I don't want anything getting messed up so I'm asking upfront.
Also, where is this thread regarding saferoot? I've searched through our forum and can't find it.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Also it's known that if Saferoot doesn't work, it will have no I'll effect on your phone, it just won't work. So it's worth a try. Check with K1mu in that thread you were linked to.
Sent from my SCH-I545 using Tapatalk
I love how you claim "CF-Autoroot and Saferoot both appear to work for those that've used it" when it's clear from the thread that saferoot won't work on 4.4 due to a patched kernel, and since OP's question was if saferoot was available for 4.4.2, your answer made it seem that it will work. Instead of looking it up and saying no or even just pointing to that thread where the answer could be found, you answered based off of how saferoot works with 4.3 and started talking about Knox. I've seen you around the forums so I know you're alright, so don't take this the wrong way, but that sort of vague and general answer (which isn't applicable for the specific question asked) just leads to confusion and frustration.
I got my hopes up for nothing. Sigh. Guess it's my fault for taking the OTA without thinking about possibly wanting root in the future.
DJMaj07 said:
I love how you claim "CF-Autoroot and Saferoot both appear to work for those that've used it" when it's clear from the thread that saferoot won't work on 4.4 due to a patched kernel, and since OP's question was if saferoot was available for 4.4.2, your answer made it seem that it will work. Instead of looking it up and saying no or even just pointing to that thread where the answer could be found, you answered based off of how saferoot works with 4.3 and started talking about Knox. I've seen you around the forums so I know you're alright, so don't take this the wrong way, but that sort of vague and general answer (which isn't applicable for the specific question asked) just leads to confusion and frustration.
I got my hopes up for nothing. Sigh. Guess it's my fault for taking the OTA without thinking about possibly wanting root in the future.
Click to expand...
Click to collapse
My bad ...
I remember seeing a post or two I THOUGHT that stated Saferoot worked for them on KitKat but perhaps that's just my fault. Didn't mean to steer you the wrong way.
I should have read up more before answering to that. Again my fault and thanks for kicking me in a$$.
Back to your issue of CF not working... I'm sure there is something that can be done to get that going for you.
Aside from reinstalling USB drivers, trying maybe a different USB cable altogether, a different version of Odin, maybe a fresh download of the CF tar file. .. I'm at a loss myself.
I've seen others post about leaving Auto Reboot & F Reset Time unchecked and then manually rebooting when finished that has worked better ( no idea why myself , just throwing a possibility out there )
Also some have also said they did a battery pull , then went into download mode and flashed and that helped.
And ive seen others who swear by using Heimdall instead of Odin simply because they couldn't get things to flash the right way through Odin.
Now if I remember correctly, your Odin says reset and then you reboot just to find it wasn't successful... So I'm not certain any of these tips would be your answer but hey what do you have to lose?
If you've tried all of that then sorry, I just am not sure what else you've tried in the way of troubleshooting that's all.
Just trying to help.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My bad ...
I remember seeing a post or two I THOUGHT that stated Saferoot worked for them on KitKat but perhaps that's just my fault. Didn't mean to steer you the wrong way.
I should have read up more before answering to that. Again my fault and thanks for kicking me in a$$.
Back to your issue of CF not working... I'm sure there is something that can be done to get that going for you.
Aside from reinstalling USB drivers, trying maybe a different USB cable altogether, a different version of Odin, maybe a fresh download of the CF tar file. .. I'm at a loss myself.
I've seen others post about leaving Auto Reboot & F Reset Time unchecked and then manually rebooting when finished that has worked better ( no idea why myself , just throwing a possibility out there )
Also some have also said they did a battery pull , then went into download mode and flashed and that helped.
And ive seen others who swear by using Heimdall instead of Odin simply because they couldn't get things to flash the right way through Odin.
Now if I remember correctly, your Odin says reset and then you reboot just to find it wasn't successful... So I'm not certain any of these tips would be your answer but hey what do you have to lose?
If you've tried all of that then sorry, I just am not sure what else you've tried in the way of troubleshooting that's all.
Just trying to help.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Whoa not you man! I was talking about leaderbuilder. You gave me a good answer, to look in the thread. That's where I found the information that unfortunately means bad news for me and others in my situation. I appreciate you helping me out and pointing me in the right direction.
I was specifically looking for saferoot, since I'd rather not trip the Knox warranty flag. I think CF-autoroot has been confirmed to work but since that trips the Knox warranty flag, I was holding off. To be honest, I had given up on root when 4.3 came out and I really wish I had noticed the saferoot option before 4.4.2 came out. Now I kinda want it back haha. I'm just hesitant because of Knox. If I root and get that 0x1 flag, I just don't want anything to stop working, like wifi or whatever (I seem to recall hearing about issues like that when 4.3 and Knox were first introduced).
DJMaj07 said:
Whoa not you man! I was talking about leaderbuilder. You gave me a good answer, to look in the thread. That's where I found the information that unfortunately means bad news for me and others in my situation. I appreciate you helping me out and pointing me in the right direction.
I was specifically looking for saferoot, since I'd rather not trip the Knox warranty flag. I think CF-autoroot has been confirmed to work but since that trips the Knox warranty flag, I was holding off. To be honest, I had given up on root when 4.3 came out and I really wish I had noticed the saferoot option before 4.4.2 came out. Now I kinda want it back haha. I'm just hesitant because of Knox. If I root and get that 0x1 flag, I just don't want anything to stop working, like wifi or whatever (I seem to recall hearing about issues like that when 4.3 and Knox were first introduced).
Click to expand...
Click to collapse
Ohhh alright lol hey no worries either way. Sometimes its tough on here, I read through so many posts and sometimes can confuse things myself.
I just Odin NAE back onto my sprint s4 then used CF and everything worked perfectly. But I understand your hesitation. I DID however lose WiFi when I flashed the MK2 modem to try and save some battery life.
Flashed back the NAE modem and ask was good again so that's my experience.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Ohhh alright lol hey no worries either way. Sometimes its tough on here, I read through so many posts and sometimes can confuse things myself.
I just Odin NAE back onto my sprint s4 then used CF and everything worked perfectly. But I understand your hesitation. I DID however lose WiFi when I flashed the MK2 modem to try and save some battery life.
Flashed back the NAE modem and ask was good again so that's my experience.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Lol so as long as I don't try to mix and match from past stock ROMs, I should be safe? The only thing that will be affected by rooting is my ability to send the phone into Samsung for warranty repairs? I'm already running NAE so I can just head over to the CF-autoroot thread and get started?
DJMaj07 said:
Lol so as long as I don't try to mix and match from past stock ROMs, I should be safe? The only thing that will be affected by rooting is my ability to send the phone into Samsung for warranty repairs? I'm already running NAE so I can just head over to the CF-autoroot thread and get started?
Click to expand...
Click to collapse
Yes you're good to go as far as CF Auto Root .
You can't downgrade your build ( NAE down to MK2 )
However I thought you could still go between Basebands ( modems ) without an issue, however I ran into that no WiFi issue. That was easily fixed by flashing the NAE modem back.
I'm waiting for more answers on the downgrading modems deal.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
As far as your warranty... I've heard most people have not had an issue even with the Knox flag.
I have no experience myself though to weigh in
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Yes you're good to go as far as CF Auto Root .
You can't downgrade your build ( NAE down to MK2 )
However I thought you could still go between Basebands ( modems ) without an issue, however I ran into that no WiFi issue. That was easily fixed by flashing the NAE modem back.
I'm waiting for more answers on the downgrading modems deal.
Sent from my SCH-I545 using Tapatalk
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
As far as your warranty... I've heard most people have not had an issue even with the Knox flag.
I have no experience myself though to weigh in
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Sounds good to me. Looks like I'm breaking that warranty!
Curious, is battery life affected that much on NAE modem compared to MK2?
DJMaj07 said:
Sounds good to me. Looks like I'm breaking that warranty!
Curious, is battery life affected that much on NAE modem compared to MK2?
Click to expand...
Click to collapse
Well unfortunately me and a few others have noticed a considerable amount of battery drain... Im waiting for a more stable stock NAE ROM to flash to see if it helps. I've been debloating it and using Greenify...I think I just have a ways to go that's all. Maybe after removing everything I can it'll be a bit better.
Sent from my SCH-I545 using Tapatalk
Ok I have looked everywhere and tried many fixes including the AT&T fix (put me into a bootloop) and clean flashes... but nothing is working.
Here are all the steps that i have done.
I have a Bell note 3 that was rooted on JB. I sent it into repair after unrooting (it still said custom but i guess they overlooked that). When i got it back it was running KK official.
I rooted with autoroot and flashed X-note with Civz kernel and the wifi/nfc fix.
Now everything is running great and i still have knox 0x0 (which is good)
EXCEPT my GPS is not connecting. I am using GPS status and it will show that there are satellites to connect to and will take a really long time to connect, then it will drop everything and say that there are no sats to connect to...
I need my GPS and am willing to sponsor a beer+ for a working solution...
And is there anyone out there that has seen the same issue?
Thanks in advance
I rooted my note 3 with x-note! I was having trouble with the gps before and after rooting as a taxi driver it really is passing me off!
Sent from my SM-N9005 using XDA Premium 4 mobile app
mypcool said:
Ok I have looked everywhere and tried many fixes including the AT&T fix (put me into a bootloop) and clean flashes... but nothing is working.
Here are all the steps that i have done.
I have a Bell note 3 that was rooted on JB. I sent it into repair after unrooting (it still said custom but i guess they overlooked that). When i got it back it was running KK official.
I rooted with autoroot and flashed X-note with Civz kernel and the wifi/nfc fix.
Now everything is running great and i still have knox 0x0 (which is good)
EXCEPT my GPS is not connecting. I am using GPS status and it will show that there are satellites to connect to and will take a really long time to connect, then it will drop everything and say that there are no sats to connect to...
I need my GPS and am willing to sponsor a beer+ for a working solution...
And is there anyone out there that has seen the same issue?
Thanks in advance
Click to expand...
Click to collapse
Try replacing the GPS config with this app https://play.google.com/store/apps/details?id=by.zatta.agps
It worked for me and I'm also using a Bell N800W8. My GPS behaved perfectly while on stock, stock rooted (with custom recovery) and at a point after flashing several roms it broke. Now it requires this app to work. I've also gone back to stock (knox 0x0) and couldn't get a lock.
Obviously it's a software issue I'm just unsure why flashing the stock firmware didn't fix it and a fix is required.
Good luck!
Sent from my SM-N900T using Tapatalk
I don't mean to be rude but there is a topic of specially made for questions about xnote roms. http://forum.xda-developers.com/showthread.php?t=2666280
Sent from my SM-N9005 beast of a phone.
Sammath said:
I don't mean to be rude but there is a topic of specially made for questions about xnote roms. http://forum.xda-developers.com/showthread.php?t=2666280
Sent from my SM-N9005 beast of a phone.
Click to expand...
Click to collapse
No offence taken
I posted there twice and it got buried within the hour and never got ansered...
Im a volunteer EMT and i rely on my GPS to get to emergencies, i needed a resolution ASAP.
I ended up just flashing vision-x n900w and now the first GPS fix after a reset can take up to a min (but it gets a fix which is an improvement)
But subsequent fixes take only a couple of seconds.... so i guess i have to live with that...
Thanks for the help (and i'm usually good with forums but i had to make an exception this time)
I have the same problem not running xnote or with at&t. I was rooted with xposed. Have tried restoring stock with odin but still doesn't work. I can run a AOSP rom and it works fine so not thinking its a hardware issue. I will start a new thread as this isn't specific to xnote.
Sent from my XT1053 using Tapatalk
Hey guys, I have Note 3 SM-N9005. Android version is 4.3 (Israeli stock Rom, still no update for that).
Current firmware is something that ends with CSC:MJ4. I tried to update to NF4 using Kies 3 but there is some kind of error that prevents me from doing so. The error occurs when download of firmware components gets to about 70%. It happened several times now.
My device is completely stock, and I like to root it. Should I try to solve the firmware update issue before rooting? Is there an easy way to root without voiding KNOX? I tried to search information in the forum but haven't managed to completely understand what should I do.
Any help is greatly appreciated, thank you.
ItayPBM said:
Hey guys, I have Note 3 SM-N9005. Android version is 4.3 (Israeli stock Rom, still no update for that).
Current firmware is something that ends with CSC:MJ4. I tried to update to NF4 using Kies 3 but there is some kind of error that prevents me from doing so. The error occurs when download of firmware components gets to about 70%. It happened several times now.
My device is completely stock, and I like to root it. Should I try to solve the firmware update issue before rooting? Is there an easy way to root without voiding KNOX? I tried to search information in the forum but haven't managed to completely understand what should I do.
Any help is greatly appreciated, thank you.
Click to expand...
Click to collapse
Sorry i cant help you, but i need to do some commenting so i can take part in developing treads, (stupid rule)
That's okay, does anyone know what to do?
Use ODIN to flash Original Samsung Firmware
ItayPBM said:
That's okay, does anyone know what to do?
Click to expand...
Click to collapse
Hi Itay,
Not that I am an expert by any measure, however I have been quite successful (and lucky!) with flashing my Note 3 (so far) and previously with my S2. There is so much good information on XDA, provided by people who really what they are doing and are willing to share their knowledge, work and help us 'users' (as opposed to developers) out.
That said, I hope (expect) that a more experience member will correct me if I'm wrong, it should be possible to flash an original Samsung ROM via ODIN. Browse around on XDA, and you will find the files and instructions you need. There are many good tutorials available, and you need to read up on whether you will lose all your data (very likely!), and whether you will trip KNOX 0x1, which I understand you can avoid using Samsung original files. For me personally, I don't require KNOX to interface at work, so am using a custom ROM, which tripped KNOX to 0x1.
Good luck, and I hope you figure out how to update your device without issues.
That's part of my problem, there is so much information that I kind of get lost in it, and don't manage to understand what exactly I should do.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Try kies in different pc at different place, spl if u r trying at work place avoid using kies as security will be high.
Sent from my SM-N9005 using XDA Free mobile app
ItayPBM said:
That's part of my problem, there is so much information that I kind of get lost in it, and don't manage to understand what exactly I should do.
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read into the Odin method - You can flash software version of your choice, without the risk of voiding KNOX and keeping a completely stock device (if you choose to)