Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
pandabamboo said:
Helppp!
Hi, I have a samsung galaxy note 8 LTE, which i just updated to 4.4.2.
How do I get this rooted?
-Do i follow this thread? http://forum.xda-developers.com/showthread.php?t=2291839
Seems like that's only confirmed for 4.2.2..
What else should I take note of? I've read things about 'Recovery' and unlocking bootloader.
-Should I do a recovery? How do I do that?
-Do I have to worry about the bootloader?
-Will I be able to get further ota updates after rooting?
Should I wait for 4.4.4 before rooting?
Thank you in advance. I've done alot of reading but I'm still paranoid and confused...
Click to expand...
Click to collapse
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
You will want to install a custom recovery to flash roms (PhilZ or TWRP). However, changing the recovery, bootloader, etc. will prevent you from taking OTA updates. This is not such a bad thing because you never know if a new OTA will destroy root and lock the device. It is better to let the devs modify it first and then flash it safely. Usually only takes a day or so for devs to do this.
As for changing the bootloader, it depends on the rom you flash. Some will be fine running from older bootloader and some require the KK bootloader. Just check the first post of the rom and it should give you the requirements.
---------- Post added at 09:07 AM ---------- Previous post was at 08:53 AM ----------
jwdink said:
I have all of these questions!
There's so much information in these forums, and it's very confusing.
I simply can't find a guide for how to get from Kit-kat on the Note 8 to rooted and with civato's ROM (would love some increased pen accuracy).
Any help would really be appreciated!
Click to expand...
Click to collapse
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
7014
As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Thanks CCallahan. Do you know of any method that will not trip Knox?
You can use CF Autoroot to obtain root and then install custom recovery via Odin as well. Then you can flash whatever rom you want.
Click to expand...
Click to collapse
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel (edit: and ROM). I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
jwdink said:
Thanks CCallahan. Do you know of any method that will not trip Knox?
I just wasn't sure on the details of these steps, and wasn't sure where to find more detail. I think I've figured it out now.
First I'd follow these steps: http://www.theandroidsoul.com/samsu...n5100-wifi-philz-touch-advanced-cwm-recovery/
Then, I'd use philz to install the custom kernel. I haven't been able to find any step-by-step instructions, however. But these seem close enough: https://www.youtube.com/watch?v=aDOY3Oi1VX8
Does this all sound correct?
Click to expand...
Click to collapse
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
CCallahan said:
I do not know of any root method compatible with the N8 that will not trip Knox. Towelroot is not compatible otherwise it would be an obvious choice.
Yes...looks like that walkthrough will work fine for installing PhilZ.
Why are you installing a custom kernel? Are you sticking with the stock rom or flashing a custom one? A lot of roms already come with the kernel packaged.
Click to expand...
Click to collapse
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
jwdink said:
I'm installing a custom ROM & Kernel because the accuracy of the pen is not very good on my device, and I primarily brought it for note taking. My understanding is that civato's ROM/kernel will fix this (hopefully!).
But I didn't mean to imply that I'm only installing a custom kernel but keeping the stock ROM. I was planning on doing both, as described in civato's kernel+ROM release thread.
Click to expand...
Click to collapse
Ah ok....after you get PhilZ on there just flash civato's rom and you will be good to go.
1928
CCallahan said:
I don't have a 5120 but everything I have read confirms that CF Autoroot works without issue on that device. Just make sure after boot up you install SuperSU, update binary, and set it to apply upon system boot. If it doesn't work the first time keep trying. As a warning....this root method will trip Knox and void your warranty. Can follow the steps HERE to root.
Click to expand...
Click to collapse
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
beniboy86 said:
Hi CCallahan,
Would you please confirm whether the method described in the link you mentioned to root Galaxy note 8.0 GT-N5120 running android 4.4.2 would work on note 8.0 i467m (LTE canadian version) running on 4.4.2?
Click to expand...
Click to collapse
The procedure is the same but you want to go and download the CF AutoRoot for your device here: http://autoroot.chainfire.eu/
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
CCallahan said:
The procedure is the same but you want to go and download the CF AutoRoot for your device here:
Your device is on the list so is compatible. There are also some basic instructions listed for how to root.
Click to expand...
Click to collapse
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
It's just a warning pal I rooted fine from 4.4.2 with chainfire autorotate it's just a precaution before proceeding as with any flashing procedure it contains a risk of bricking
Sent from my GT-I9505
beniboy86 said:
Thanks for your response. I have only one corcern left. In the link you posted, on top of the table of CF-Auto-root, it mentions that if the bootloader is locked this might brick the device! How can I make sure that my bootloader is unlocked prior to start rooting.
Previuosly, I had my note 8 rooted with CF auto root via odine when it was on jelly bean 4.1.2. Does this mean that it is safe to root it again with new CF auto root for 4.4.2?
Click to expand...
Click to collapse
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
CCallahan said:
How did you update to 4.4.2? Rom flash or OTA? Did you manually update the bootloader?
As far as I know Samsung doesn't usually lock bootloaders unless it is carrier dictated. It is usually common on HTC and Moto devices.
Better to be safe than sorry though.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
beniboy86 said:
I updated to 4.4.2 via Kies with samsung's released firmware. I havent done any other flashing apart from this. So, I suppose rooting must be fine, right?
Click to expand...
Click to collapse
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
CCallahan said:
Sorry but I can't/won't confirm whether or not that particular model is safe to root after 4.4.2 upgrade. Maybe someone with more knowledge on that version can chime in. I wouldn't think it would be an issue but don't want to steer you wrong. The bootloader could be locked.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
thanks, I will dig in more on this and will post here if I find something useful.
Related
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
What version do you have?
P600 (wifi only)
P601 (3g)
P605 (lte)
?
They have different chipsets and different root methods.
[e] I see you have found the correct version if you want to get OTA updates you need to flash stock recovery so your device status is not custom. But it basically doesn't matter since you can always flash updates through odin. You may choose a custom recovery that offers you a lot of cool features instead.
stamina11 said:
Hey guys,
I was wondering if someone could help me a little. I just bought this tablet (2014 version) and it has MK1.
I am trying to read information on how to root it but can't figure it out. I tried to flash autoroot with odin but it errored. I didn't find mk1 autoroot anywhere so i used autorootp600.mj4.tar.md5. Is there autoroot for MK1 and i can use? Also i guess i will need to have custom recovery file for my stock OS, where do i get that?
Thank you in advance for all the help.
Edit: I finally located autoroot for mk1 and it worked. But i do have a question: why do we need to flash it with Stock Recovery after? btw i am using this tutorial : http://theunlockr.com/2013/12/17/root-samsung-galaxy-note-10-1-2014-edition/
Click to expand...
Click to collapse
I believe...... so you can still get OTA updates and some functions like All Share Cast may not work if you don't.
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Thank you guys for responding so quickly.
It's starting to make sense.
My device is Wifi only so SM-P600 (mk1). I rooted it but haven't flashed with stock recovery. Would you guys recommend i do a custom recovery or keep it stock? Where do i get stock recovery from? i can't seem to find it.
clouds5 said:
The thing is, even if you have stock recovery but modify your system in other ways like uninstall alot of bloatware or use busybox your status will be custom anyway so I recommend a custom recovery for the safety of using backups etc.
Click to expand...
Click to collapse
Yea i definitely plan on de-bloating it. So where do you get custom recovery?
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
clouds5 said:
http://forum.xda-developers.com/showthread.php?t=2515656
Check this thread
Click to expand...
Click to collapse
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
So as far as Roms go, i see that in Development section there are few ROMs available but some say they are for MJ9 or ML1, i cannot use those on my MK1 right? Do ROMs from note 10.1 (2013) work on this device? Is there a list of ROMs that would work on my device.
Sorry, guys i know these are newb questions but i just could never figure out some of this stuff.
stamina11 said:
Ok, that makes sense i went though it. So i see that there is ClockMod and TWRP and GooManager, do they do pretty much the same thing?
Click to expand...
Click to collapse
I got the same question here. Any help?
legender said:
I got the same question here. Any help?
Click to expand...
Click to collapse
Goomanager is an app use it to flash twrp recovery.
TWRP and clockmod (CWM) they are 2 different tools but have the exact same functions, just a user choice. Sometimes custom rom preferred one over the other. I like TWRP a bit better (easier).
is there a way to check if it is rooted or not?
legender said:
is there a way to check if it is rooted or not?
Click to expand...
Click to collapse
Download rootchecker in the play store
Sent from my Nexus 5 using Tapatalk
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Interesting. Going to have to look into the original No-Knox Trip thread too.
SUCCESS! 4.4.2 KitKat Rooted with Knox 0x0!
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Awesome stuff haha. I wonder how this roots without voiding knox
I wonder if there were more successes?
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
Could you post us a picture of your phone with the proof....seeing is believing.
joetzzz said:
Success! Followed the German guide in the link and now I have 4.4.2 KitKat Rooted with Knox 0x0! Below is the bootloader file that I created and used.
Click to expand...
Click to collapse
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?
My words are my proof, my friend. It's too much trouble for me right now to have to take picture of the Download mode screen. Sorry.
Muffycheeks said:
Could you post us a picture
of your phone with the proof....seeing is believing.
Click to expand...
Click to collapse
Dreamgun said:
Found this German page just off of Google with what appears to have a guide on rooting kitkat without voiding knox...
http://www.mobtivity.com/de/news/galaxy-note-3-update-auf-android-kitkat-mit-root-und-knox-0x0.html
I posted the link in another thread as well, but figure a new thread will give it some more attention.
Not sure if this would even work on the T-Mobile note 3.
I've never personally rooted before, but planning to once a knox friendly method has been confirmed for KitKat!
Click to expand...
Click to collapse
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...
Yes. Just follow the steps. The trickiest part is the extracting bootloader. I had to open the command prompt, go to the folder, and run the batch file, instead of running it directly from Windows explorer. That's why I posted the file here for others to benefit.
droidkevlar said:
So you followed every step and just used the bootloader file you uploaded instead of theirs and you are now rooted with KNOX 0x0? Not that I dont believe you, but can you show a screen shot of this please?
Click to expand...
Click to collapse
---------- Post added at 03:48 PM ---------- Previous post was at 03:37 PM ----------
I confirm that it works on my T-Mobile Note 3 SM-N900T.
belozeroff said:
THIS IS T-Mobile Note 3 Forum, why are saying: "Not sure if this would even work on the T-Mobile note 3" ???
wrong forum...
Click to expand...
Click to collapse
Just to clarify
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.
effortless said:
This method has been used for some time here... http://forum.xda-developers.com/showthread.php?t=2522729&page=69
Also, this is not a 4.4 root method, rather it takes advantage of root while on 4.3 (ex. Root de la vega). So if you already installed the 4.4 bootloader, you have to wait for something else to come along.
You use mobile odin pro (which requires you already have root) to flash the 4.4 ROM while injecting root into it, however mobile odin pro never touches the bootloader and so if you stop there, you can't boot back into your phone. It's a soft brick. You need to update to the 4.4 bootloader using Odin on the desktop after using MOP to flash the ROM.
I tried this the day the update came out and got stuck on the booting recovery screen after I flashed my own 4.4 extracted bootloader. I was forced to Odin to the complete 4.4 and I am stuck with no root unless I auto-cf and lose knox.
Click to expand...
Click to collapse
So what your saying is, this doesnt work like the person before you said, correct?
I think my bootloader file wasn't created right. This should technically work if the bootloader is correct. It's for preserving a rooted 4.3 to 4.4, not rooting 4.4.
Sent from my SM-N900T using Tapatalk
What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk
The tool in the German guide is supposed to be able to create a bootloader from any rom, given you have the md5 file from Sammobile. Use Google translate if you can't read German.
droidhead36 said:
What's the best and easiest way to to create a bootloader file? I need one for different version of note 3. Any issues since using this method? Like spen or force closes or anything?
Sent from my SM-N900R4 using Tapatalk
Click to expand...
Click to collapse
Ok it works. Pretty easy instruction. Knox still 0x0. But I had to spend $4.99 to buy Mobile Odin Pro.
Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q
Dreamgun said:
Things are getting a little confusing... I think this needs an english guide with requirements that people can follow and understand. Q_Q
Click to expand...
Click to collapse
Agreed. Someone that has done this, can you make a quick guide on how to do this exactly coming from 4.3?
I followed the guide and got to 4.4 with root access and KNOX is still on 0x0.
1. I got the initial root on 4.3 with root_de_la_vega and used regionaway to unlock the device as I am currently using my N900T with ATT.
2. Followed all the steps to create the bootloader file after getting the stock firmware for 4.4.
3. Followed the instructions as described on the page using google translater via chrome.
4. After applying the firmware using mobile odin pro...the device gets stuck at recovery booting.
5. Took off the battery for a few and then finally made it to download mode.
6. Tried to use the BL option, but the version of ODIN I had didn't provide an option to choose the BL.
7. Download the ODIN from the instruction page and that provided the option to load the BL i created using the method.
8. Finally the device booted, and I still have root access with KNOW 0x0 and running on 4.4 as well.
Let me know if you need the bootloader file I created and I shall upload the same.
Hope this helps.
Confirmed working; did this yesterday following the instructions, step by step like on the website mentioned; started from 4.3 rooted with Root de la Vega 0x0 Knox flag, unpacked tar.md5 file, created bootloader with the script provided, flashed firmware from Mobile Odin (need to be careful to select after flash option to download mode before you click flash now), then flashed the bootloader I've created using the Odin version provided in the link; everything went smooth, no softbricks, got to keep all my apps and settings, now my phone is running 4.4.2 and is rooted with the Knox flag untouched, 0x0. Only issue I've seen so far is that my default email application keeps FC-ing, can't use it.
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Currently I'm at v4.3 (touchwiz) and haven't done the latest OTA yet (presumably it's v4.4.2). It'd be best to do the OTA update and then root, right? Reading the earlier post, it
appears this method works for v4.4...
While posting, also is it possible to downgrade back to v4.3 from v4.4? Not that I'm planning on it, but have read both yes and no on doing it and just wondered.
Thanks in advance and do advise if there's anything I should watch out for while doing this!!
Click to expand...
Click to collapse
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
wha2do said:
Planning on rooting my P600 and after reading Hahahalalala's earlier post, will follow BeansTown106's instructions (http://forum.xda-developers.com/showthread.php?t=2490805).
It appears I need to flash from p600Autoroot.7z for v4.3 and CF-Auto-Root-lt03wifi-lt03wifixx-smp600.zip for v4.4? Please correct me if I'm wrong?!
On step 4, it says to "...flash the stock mj4 recovery provided". Planning on installing TWRP v2.7.1.0 - can I just do it here? Or do I need to do this step and afterwards install
TWRP (and flash Super SU)? I'm curious about the reason for flashing the stock recover and whether it's version specific...
Click to expand...
Click to collapse
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
buhohitr said:
1) If you flash twrp then you can't do OTA any more
2) The root instruction would work but will trip the Knox and void warranty.
3) Not possible to downgrade back to 4.3
4) if you not use twrp but reflash stock recovery image then OTA would work but will wipe out root if you take the OTA upgrade what ever that maybe 4.4.3?
Click to expand...
Click to collapse
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
deV14nt said:
I used these full instructions for Kit-Kat: http://forum.xda-developers.com/showthread.php?t=2719750
One step in that is the CF-autoroot, but there are other steps as well. I just ignored the "To Flash New Update" part, but maybe you need it. I was already on the latest OTA before I started. Trips knox but I'm sure you knew that.
Click to expand...
Click to collapse
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
wha2do said:
Thanks! Yep, not concerned about warranty at this point... And figure will do the OTA and then root...
Actually latest posts appear to show some issues with SU when using CF-autoroot (maybe due to them being on kitkat?). Appears flashing CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5 does the trick. Sounding like it's part
of the flash, and can then just flash twrp (figuring be safe with v2.6.x for now).
If not reading this right, anyone feel free to correct me before I "jump", lol!
Click to expand...
Click to collapse
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
wha2do said:
1) That's why I figured best to do the OTA first - just had other devices that didn't have root methods for the newest update & wanted to thought best to ask first!
2) I'm out of warranty (due to drop and repaired screen) so warranty is of no issue...but thanks for the warning
3) Thought that to be the case, but again hearing it may be possible and also can't. Don't foresee doing it, but was curious...
4) Plan on flashing the latest (CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5) via odin, reboot, flash twrp v2.6.x as I hear 2.7.x may have a few issues. Only problems I've read are potential with Super SU - not sure if it's part of the root flash, needs to be flashed
separately, or just dl'd from Google Play Store? Guess will just flash root, see if app is there, if not try Play Store. If not, then go back and find the flashable SU dl.
Thanks!
Click to expand...
Click to collapse
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
22sl22 said:
Su is fine with me after cf root.
In my signature is a guide to rooting with kitkat (second post)
Follow that and you'll be good : good:
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks - that was the post had been reading through - appears after the kitkat OTA, latest posts mentioned problems with SU when running the original CF-AUTO Root method (flashing autorootp600mj4.tar.md5). Wondering if flashing the "newer" CF-Auto-Root-lt03wifi-lt03wifixx-smp600.tar.md5
would be best. At this point feel confident either way!
deV14nt said:
Yeah you want TWRP 2.6.3.3. It won't work right with 2.7.x. Might as well flash the SuperSU. Most of the root apps worked fine but Viper4Androod did not find Busybox even after using the installer. Need to go back a version of V4A too due to bugs but it still didn't work. Tried freezing Knox apps that might be interfering but eventually just installed that MagazineUX ROM and now it works. Everything else should work easier.
Click to expand...
Click to collapse
Yep, will be downloading TWRP v2.6.3.3 and flash it and SuperSU after rooting. After rooting, will be curious to see where I sit with superuser (sorry, reading the latest posts kind of muddy whether a SU app is already installed or not, lol)...
Thanks everyone for all the great input & help!!
In the ever changing market of roots and exploits I believe it would be nice to have a device specific rooting "poll". the other reason I'm starting this thread is because I can't seem to root my phone tried towelroot but it says my device is not supported. Im running stock 4.2.2 and I want to root mainly so I can back everything up before I custom install stock 4.4.2
Towelroot works for 4.4
Being on 4.2.2 you could try the Safe-Root method depending on your actual Firmware. Otherwise you have to stick to rooting through CWM.
All methods have their threads here. Please read them.
You could also backup your data with adb without root and after update restore this adb backup to your device. So there's no need to root before installing custom 4.4.2
CWM all day! so fast and easy to do plus it's easy to unroot.
feckinfinch said:
CWM all day! so fast and easy to do plus it's easy to unroot.
Click to expand...
Click to collapse
how exactly? I know I need to flash smth but I dont know which file it is and such. could I have a link to the proper page please?
kostas90 said:
how exactly? I know I need to flash smth but I dont know which file it is and such. could I have a link to the proper page please?
Click to expand...
Click to collapse
http://www.s4miniarchive.com/search/label/Root Find your model version and read the instructions, you won't regret it.
4.2.2 can be rooted using Kingo. Doesn't trip knox.
Tap tap tapatalked from my I9192
i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
eric303 said:
i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
Click to expand...
Click to collapse
No, the partitions are completely different. KK is gone for good after your on lolly.
Kit-Kat+Lollipop
http://http://forum.xda-developers.com/note-4/orig-development/tw-kernel-emotroid-team-t2990557
eric303 said:
i got a note 4 and i know i cant downgrade from lollipop to kitkat without bricking it, but what if i were to root it and do a custom recovery, can i load a kitkat custom rom onto it?
Click to expand...
Click to collapse
*delete
hmm... since i got 2 different answers i'm not sure which to do. my purpose is to do the domestic sim unlock on this phone, any other advice?
?
eric303 said:
hmm... since i got 2 different answers i'm not sure which to do. my purpose is to do the domestic sim unlock on this phone, any other advice?
Click to expand...
Click to collapse
*delete
Iceburn1 said:
I told you my steps and that I have done it my self, doesnt matter if the partitions are different, it works, trick is to flash the rooted kernel after. As far as a domestic unlock sure fire way and only way on lollipop is paying...idoneapps...http://idoneapps.com/.
Click to expand...
Click to collapse
really??? r u sure???
// anyone comfirm this work??? running KK rom on L Kernel????
Iceburn1 said:
I told you my steps and that I have done it my self, doesnt matter if the partitions are different, it works, trick is to flash the rooted kernel after. As far as a domestic unlock sure fire way and only way on lollipop is paying...idoneapps...http://idoneapps.com/.
Click to expand...
Click to collapse
fantasylovevn said:
really??? r u sure???
// anyone comfirm this work??? running KK rom on L Kernel????
Click to expand...
Click to collapse
No I can't. But I see no reason to doubt what he says he's done himself. I do know the method he mentions was verified for several lollipop ROMs by multiple users.
OTH. Until I read the post above, IIRC, that's the first I've heard of it working on KitKat. TBH, I've not attempted this- "works on any ROM" concept but stayed close or with my bootloader. OB7 bootloader running OG5 being the biggest exception. But I've also made exceptions for kernels and modems but stayed close to revision of bootloader. I feel max compatibility is where they all match. When possible, that's what I run with.
KitKat may boot with your lollipop bootloader and lollipop 5.1.1 custom rooted kernel but how stable and compatible is it? For me, KitKat WiFi Calling was never stable. Not saying it's a total waste of time; use at your own risk.
I can't affirm with absolute certainty that Odin won't allow you to downgrade once your bootloader is greater than OB7 (because I never tried it, myself) but I can say MANY reported and posted failed Odin logs to confirm that. (That is confirmation). AND some had to use Philz CWM touch recovery for Note 4 to factory reset and flash in recovery after TWRP failed to flash afterwards and for a time; there were a few to confirm this. Don't try to "downgrade to KitKat with Odin" unless your bootloader is OB7 or less. If bootloader is greater than OB7, use recovery only plus the kernel mentioned for downgrade. It's a risk vs reward to consider yourself.
Sent from my SM-N910P using Tapatalk