hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here , when Im rooting doesnt show anything , and the smartphone turns on without showing the red android that suppose to show
jgfernog said:
hello guys,
I rooted my Note 4 SM-N910C yesterday, and everything was fine until now. I saw that reactivation Lock(can't flash via odin when it's on) was off, so I tried to turn it on, but it was not working. I tried everything, but without sucess. I tried to flash a stock firmware from sammobile, and after that, it was working, so I rooted again and It's not working anymore.
So, someone knows a way to root and get it working? Did you have this problem too?
help me :/
Click to expand...
Click to collapse
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)
UnboundDemon said:
Same here, maybe installing xposed and putting a request for a module? although s health and private mode don't work on my note 4 either (xposed running)
Click to expand...
Click to collapse
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.
jgfernog said:
this is a kernel related, I think. Everybody says that it still working on Snapdragon's Note 4, but here at Exynos, you can't activate it.
Click to expand...
Click to collapse
I dont think it is that, I have a friend with the same model that us, and the activation works on his phone :s
So, guys, have anyone solved this problem?
I also have rooted Note 4 and neither "Remote controls" nor "reactivation lock" can I activate...
reactivetion lock not working
I also encountered a similar case but only used through l launch , give me one new idea when it dies in it :good:
Guys, has anybody solved this problem?
Here I am, rooted GS5 with MM fw, before root it worked, as it did with lollipop and kitkat.
After root it doesn't turn on anymore, I reflashed stock recovery too. I guess it's related to knox 0x1, with rooted knox 0x0 kitkat and lollipop I could enable it.
Or maybe it's kernel related, so systemless root with stock kernel could be the solution
Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root
Joker87 said:
Good news, after reflashing a stock firmware I could enable RL back. So it's not knox related but root related. Tomorrow I'll try with systemless root
Click to expand...
Click to collapse
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)
chaundb said:
I think what is needed it to copy your stock recovery from an official touchwiz rom and flash it. You will need a tar.gz converter to flash it via odin. Sometime ago I tried it where your root remains but you have a stock recovery. I believe all those Samsung security features like Reactivation Lock relies on a stock recovery and not a custom like ( TWRP/CWM)
Click to expand...
Click to collapse
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked
Joker87 said:
I reflashed stock recovery but still no luck. It's root related, or better kernel related, as someone posted above. I'm on systemless root and it shows "warranty bit kernel" message at boot. With rooted lollipop and stock kernel/recovery it worked
Click to expand...
Click to collapse
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???
chaundb said:
Really, so how can I do the same on Marshmallow. Where can I obtain a systemless root method for my SM-N910H Note 4 ???
Click to expand...
Click to collapse
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications
Joker87 said:
Just flash supersu beta via twrp
You must have stock boot.img, I suggest reflashing the entire stock firmware if you did some modifications
Click to expand...
Click to collapse
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???
chaundb said:
Look...i am currently rooted. I have twrp 3.0 and i flashed super su beta. I dont have any modified or special kernels of that sort...just root. So are you telling me all i need to do is flash the original touchwiz boot.img from the marshmallow rom file ( i will have to go convert it to a Tar file) ???.... And that will give me the ability to stay rooted and be able to use reactivation lock again ???
Click to expand...
Click to collapse
Nope... rl doesn't work with any root method
Joker87 said:
Nope... rl doesn't work with any root method
Click to expand...
Click to collapse
Ok..thats what i thought.......its best we stay without it then. Or go back completely stock and unrooted to use the feature.
Hello, seen there is no new news about this.. Has anyone got around this?
Can we root and activate the reactivation lock now?
Thanks
Related
Hi, I have an Samsung Galaxy S3 updated to Jelly Bean 4.1.1 and rooted with cf-root 6.4 and I would like I have readed that chainfire think that is "better" cf-auto-root so now I would like way mobile odin pro change cf-root to cf-auto-root if this is possible.
Can you help me? I don´t have post for post in the chainfire post and I don´t know if with mobile odin I can put cf-auto-root and how I can do.
Regards
Back up your data using Titanium Backup or any other backup tools.
Then flash stock JB firmware, root it using cf-auto root.
Restore data.
astrall said:
Back up your data using Titanium Backup or any other backup tools.
Then flash stock JB firmware, root it using cf-auto root.
Restore data.
Click to expand...
Click to collapse
Ok, but one question, why don´t work flash cf-auto-root directly?
regards
jjaviercs said:
Ok, but one question, why don´t work flash cf-auto-root directly?
regards
Click to expand...
Click to collapse
You need to ask Chainfire he developed it .
jje
JJEgan said:
You need to ask Chainfire he developed it .
jje
Click to expand...
Click to collapse
Ok, thanks
Lolz just leave the **** alone. You are already on firmware you want to be and you're rooted....? Leave it alone. No point going through all that work for nothing.
**** delete custom, that is reflash custom recovery with regular one and you got yourself auto root lol. Then when you get to the point that you'll need custom recovery, do it all over again.
Highly suggest you go read again what auto root is and does without blindly thinking it's better and automatically thinking you gotta redo it. You don't!
Sent from my GT-I9300
Loving c.f.-auto_root. for now till I decide to flash again hahaha
Sent from my GT-I9300 using xda premium
What's the problems with 6.4 usage on jellybean?
At moment I am having major problems I first thought as nothing, but basically I am seeing increased battery drainage since I updated. I also am having some "wifi suffocation" - Wifi media would just cut and you need to disable and enable wifi to get it working again. I updated a rooted phone via kies and rooted it with 6.4 so I am trying to know if these problems are just my old settings being incompatible, CF root 6.4 and/or BusyBox or just a general NEE Jellybean error...
Thanks to all for your answers. For now I don´t will change until new firmware
regards
Sumea said:
What's the problems with 6.4 usage on jellybean?
At moment I am having major problems I first thought as nothing, but basically I am seeing increased battery drainage since I updated. I also am having some "wifi suffocation" - Wifi media would just cut and you need to disable and enable wifi to get it working again. I updated a rooted phone via kies and rooted it with 6.4 so I am trying to know if these problems are just my old settings being incompatible, CF root 6.4 and/or BusyBox or just a general NEE Jellybean error...
Click to expand...
Click to collapse
No problem whatsoever with cf root. Chainfire simply decided not to make and use custom recovery anymore. So he took it out. Which is his right anyways.
Your counter will still increase with auto root as with original for initial flashing via Odin. After which you can perpetually flash with 'mobile odin', preserving root. Which is probably what he wants and it makes sense for those of us that own it.
Those that want custom recovery for flashing zips will have to flash it separately. Which unless flashing with mobile odin will make the counter show 2 (auto root + recovery) instead of one with original cf root.
For those that care about warranty and Chainfire already hinted he might stop playing cat and mouse with samsung and samsung changes something so that current triangle away stops working...
Testing JKay alpha on GT-I9300
Idan73 said:
No problem whatsoever with cf root. Chainfire simply decided not to make and use custom recovery anymore. So he took it out. Which is his right anyways.
Your counter will still increase with auto root as with original for initial flashing via Odin. After which you can perpetually flash with 'mobile odin', preserving root. Which is probably what he wants and it makes sense for those of us that own it.
Those that want custom recovery for flashing zips will have to flash it separately. Which unless flashing with mobile odin will make the counter show 2 (auto root + recovery) instead of one with original cf root.
For those that care about warranty and Chainfire already hinted he might stop playing cat and mouse with samsung and samsung changes something so that current triangle away stops working...
Testing JKay alpha on GT-I9300
Click to expand...
Click to collapse
Sounds good really - and seems like it at least is not CF root that is causing my problems, something is what is making me go through complete wipe and firmware reinstall probably from sammobile source. I hope I get it fixed and it is not something in the firmware itself because the Jellybean IS nice.
jjaviercs said:
Hi, I have an Samsung Galaxy S3 updated to Jelly Bean 4.1.1 and rooted with cf-root 6.4 and I would like I have readed that chainfire think that is "better" cf-auto-root so now I would like way mobile odin pro change cf-root to cf-auto-root if this is possible.
Can you help me? I don´t have post for post in the chainfire post and I don´t know if with mobile odin I can put cf-auto-root and how I can do.
Regards
Click to expand...
Click to collapse
i flash directly the cf-auto root from my custom JB by using mobile odin and revert back to cwm due to the fonts too small.
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
banerbocken said:
I just tested Towelroot on my GT-I9506 running latest NEE 4.3 and it worked like a charm and did not trigger Knox.
Thread found here:
http://forum.xda-developers.com/showthread.php?t=2783157
Happy rooting
Click to expand...
Click to collapse
Works perfectly!
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Alestilohomer said:
Please, can you help me?
I've downloaded the towelroot apk and installed it. Then, once the phone was rebooted, I've installed supersu from playstore, but it ask me to update de SU binaries, I select the normal option but it gives me a message about samsung knox and if I want to try to disable it, I select no because I don't know if it will affect to the knox counter.... What are the steps please?
And if I download the suggested SuperSU from the towelroot thread, I can't install it because it's a flashable zip that I can't install because I have stock recovery...
Click to expand...
Click to collapse
Towelroot installs needed files for root. I didnt install SuperSU at all from play store cause its not latest version.
ChainFire is updating SuperSU soon and when latest version (1.99) is online you can install it from play store.
After Towelroot I just installed Titanium Backup (and pro key) and freezed all crap including knox.
After using towelroot on a KNOX-enabled stock 4.3 device, is is possible to revert back to the 4.2.2 bootloader without burning the e-fuse?
Ok, tried to delete system apps, including the knox ones, with root explorer and was successfull!
And about the downgrade, it will change the knox status for sure, because knox is in the bootloader too, not only the apps and libraries, and here, root doesn't made any chance...
Enviado desde mi GT-I9506 mediante Tapatalk
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
tlund said:
The KNOX e-fuse should be burned only by the bootloader in ODIN mode when it flashes an unsigned file to the device. Getting local root on the device and writing a new bootloader directly to the flash should not be able to affect the e-fuse?
Click to expand...
Click to collapse
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Now I have my GT-I9506 Singapore version with KNOX warranty void 0x0 in this configuration:
System and NON-HLOS from Finladian version: I9506XXUBNE1
The others from original Sigapore version: I9506XXUBND2
towelroot.com installed and working!
Thanks to towelroot
tomogo said:
It is slightly wrong. You shoud burned KNOX when you flash different version of kernel, recovery, bootloader.
You can flash system, modem, NON-HLOS and maybe others. I've tested only system and NON-HLOS.
Click to expand...
Click to collapse
Yes, but you are talking about flashing this via download/odin mode, right?
My point is that with root, you should be able to modify the flash directly, overwriting the bootloader.
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Probably not
topimax said:
Would it be possible to receive original updates OTA with this root?
Sendt fra min GT-I9506 med Tapatalk
Click to expand...
Click to collapse
As we have root I would think (so don't quote me on this) that OTA is blocked. But as I see it it does not really matter as the next update for this devise is probably going to be 4.4.2 and flashing that probably also means loosing root.
Now that was a lot of probably but as I see it..
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
mar10o said:
You need "Official" status under Phone Info to receive OTA updates. ROOT will be overwritten by the updates.
After root it's very common to have "Custom" status, but you can cheat it with Traingle away app (not tested by me) or sometimes you can be "Official"after Wipe ( it depends what changes has been done to the system)
Click to expand...
Click to collapse
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond of rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
windstrings said:
I would think getting the OS" 4.4.2 is only part of the package (BTW 4.2.2 vrzn w/gs4 rooted with ease) but you also get other surprises...
Not exactly like a box if lucky charms either.
Samsung or vrzn either one are not fond if rooting.
Triangle away didn't help me unless i did something wrong.. I still have the unlock icon when booting and phone info says "custom" but knox is 0x0
Sent from my GS4 Zombie Communicator
Click to expand...
Click to collapse
Was told that xposed could chance the status from custom to official.
Sendt fra min GT-I9506 med Tapatalk
For those who failed check last version !
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
bertrand13 said:
For me
V1 Towel root didn't work
V2 towel root didn't work
V2.1 (downloaded today) = SUCESS
I9505XXUFNC4
Click to expand...
Click to collapse
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Don't know why he doesn't label his site or the filename better but it should be the latest version when you download from his site.
When you open the app to install it, it should say the version at the top.
Sent from my GS4 Zombie Communicator
mohammedkhairy said:
Will it work in gt-I9505 4.4.2 XXUFNBA without tripping knox
Click to expand...
Click to collapse
It should work. It does not trip Knox
kerko said:
I do not seem to be able to find V 2.1 Can you guide me please? Thanks
Click to expand...
Click to collapse
Well I downloaded it from the towelroot web :laugh::laugh:
I saw on XDA tnat somebody mentionned a new version so I tried
If you need more PM me...
The why
A lot of this has been said in other threads, however I decided to gather all the up-to-date (as of Jun 17, 2014) instructions and info in this thread to alleviate fears of the infamous 'KNOX WARRANTY VOID 0x1' and help people with the process. People with tripped KNOX can of course use this as well, however it won't untrip their devices, duh.
The cheers
First of all big cheers for Pinkie Pie (person who discovered the Linux kernel vulnerability that makes rooting without tripping KNOX possible), geohot (person that used the vulnerability to make a rooting app), chainfire (developer of SuperSU), rovo89 and Tungstwenty (developers of Xposed). Go and donate to these guys if you can!
The what
This post will tell you how to upgrade your P605 to 4.4.2, if you haven't already. And how to install SuperSU and Xposed all the while keeping your KNOX counter at 0x0, CURRENT BINARY: Samsung Official and SYSTEM STATUS: Official!
Note: The versions in this text are just for reference - telling you what versions already worked. New ones will surely also work, so you should usually download the newest available.
The how
Firmware
4.4.2 NEE P605XXUCNE2 (any of the current 4.4.2 firmwares should be fine, although Samsung might use an updated kernel for the future versions, disabling towelroot)
From http://forum.xda-developers.com/showpost.php?p=53092676&postcount=1
Simple instructions available here http://www.sammobile.com/firmwares/3/?download=30325 (you can also download the firmware from here, but download is slow for free accounts)
Root
From http://towelroot.com
No special instructions (it's a 1-click root)
SuperSU
Version 1.99.rc5 from http://download.chainfire.eu/448/SuperSU/
Extract Superuser.apk (in 'common') from the zip, install and run
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
Xposed
From http://repo.xposed.info/module/de.robv.android.xposed.installer (version 2.6.1)
No special instructions
The victory
Congrats! Now you should be on a rooted, SuperSUed, Xposed KitKat with warranty left intact! However before sending it to Samsung, e.g., for repairs, you should flash your original firmware, of course.
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
no.0ne said:
SuperSU
Version 1.94 from Google Play (Jun 17, 2014)
Answer yes to the Disable KNOX prompt (don't worry, KNOX will not be tripped)
At the end it will say it failed, however it will be working!
If you are annoyed by the 'failed' message for some reason, download an updated version from http://download.chainfire.eu/448/SuperSU/ (you'll have to flash it manually though) which supposedly fixes it.
Click to expand...
Click to collapse
Just Download specified zip and extract superuser.apk from common folder and install as normal program, don't download play version
İ am gonna try and write my appreciate ) thanks in advance
It did work . Thanks to you and that steps i have rooted kitkat knox is 0*0 what i was waiting for last 5 months. Thank you so much now i can use my tablet in full capacity
iPhone 'den Tapatalk aracılığı ile gönderildi
Eudeferrer said:
Can this be made to work with the SM-P600 on Android 4.3 unrooted? Any help will be appreciated. This would be a dream.
Click to expand...
Click to collapse
It seems that so far people have had no success using towelroot on P600. Wait and hope it will change...
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
yararli said:
Hello, i want to do this on clean tablet, so i want to do clean install , how can i clean it all had before, from odin? And is nee nordic kitkat rom suitable for all p605 , i am frightened about boatloader problem and soft brick before i done i wanted to ask. Thanks in advance.
Click to expand...
Click to collapse
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
no.0ne said:
You can wipe the tablet from recovery:
Turn tablet off
Turn it on holding Volume Up + Power Button until you see something on the screen
Wipe data/factory reset
Reboot
NEE will be fine for all P605, however I don't know if it works with something like P605V (US Verizon).
Click to expand...
Click to collapse
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
yararli said:
Should i do this before or after kitkat installation ? And where can i find usb installation of p605 when it is taken into download mode for pc to recognize the tablet.
I have no windows pc now im gonna do that on thursday ı was waiting this topic for 4 months thank you so much
iPhone 'den Tapatalk aracılığı ile gönderildi
Click to expand...
Click to collapse
First you wipe then you flash
You can download the driver from the Samsung website, e.g., http://www.samsung.com/us/support/owners/product/SM-P605VZKEVZW (don't worry that it is on the US page, the driver is the same for all Samsung devices)
Glad I can help. I waited for root quite long myself :victory:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Matthias.ja said:
In the thread discussing towelroot on P605, people claimed installing xposed would change your binary to custom. That's holding me back for now, can you confirm that it stays official?
Click to expand...
Click to collapse
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
alright, thanks!
so if i have some warranty issues, wiping everything from recovery or re-flashing the unrooted stock ROM would make everything official again, right? I know I sound like a scared little girl, but I just really don't want to risk my warranty on this rather expensive device
Heyy its wonderful i did it but there is a problem about kitkat rom i saw a little lags and the biggest problem is whatsapp says it is not compatible with this device also twitter in playstore what should i do thnx for your all help
iPhone 'den Tapatalk aracılığı ile gönderildi
valexi said:
It only makes it custom inside of the ROM. In download mode it shows Official. You can also use the Wanam xposed module to change it back to Official in the ROM.
Click to expand...
Click to collapse
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Hello i should restore system defaults how should i do directly by using recovery mode can i clean systam cache and ... Or before it should i unroot from su?
iPhone 'den Tapatalk aracılığı ile gönderildi
To make sure; unroot and then factory reset
Matthias.ja said:
So i just tried and installed xposed, and funnily enough, my system status stayed official, even inside the ROM. I won't complain though..
Click to expand...
Click to collapse
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
dt33 said:
As long using stock recovery and it will stay Official. Just custom recovery will give custom.
Click to expand...
Click to collapse
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
valexi said:
No it doesn't. You dont seem to understand difference between "system status" in Download mode or inside of the ROM.
Here is couple of pictures to make you understand.
In the picture below you can see system status official. This will change, if you install CUSTOM ROM or CUSTOM RECOVERY. Towelroot does not change any of these data here:
In the picture below you can see Device status "custom". This can change to custom if you ROOT the device and/or install SuperSU or Xposed framework. This has NOTHING to do with the status in the Download mode as seen in the first picture.
I hope that people wouldn't mix these things, because they are rather easy to understand. Talking about things that you dont really understand will cause confusion and makes people asking more stupid questions.
Thank you!
Click to expand...
Click to collapse
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
dt33 said:
Pls, explain how come it stays Official after rooted with towelroot, installed SuperSu and Xposed?
http://forum.xda-developers.com/showpost.php?p=53452193&postcount=33
Click to expand...
Click to collapse
I'm not quite sure, but it seems that in some cases the ROM can detect if it's rooted.
For me it changed to "Custom" after rooting with towelroot and SuperSU installation. I changed it back to Official with Wanam xposed.
Hi everyone,
Just spent the best part of 2 hours wondering how I go about installing some kind of custom recovery on my wife's Note 3 (SN9005) so I can run SlimKat on it.
It's currently running MJ7 firmware.
Question: Can this phone have a custom recovery installed so I can flash a different ROM?
I understand that the bootloader is "locked", but it seems that I can still go on my merry way and install a custom recovery and ROM, but Knox will flag that I've changed it.
Can someone please explain to me my options if that's ok?
Thanks very much
No one? :/
Any info would be great
Install ROM Toolbox Pro from the Google play store. You can get recovery installation within that.
CaptChaos1969 said:
Install ROM Toolbox Pro from the Google play store. You can get recovery installation within that.
Click to expand...
Click to collapse
How do you manage to think that?
Doesn't that just install a ROM? I didn't think it'd somehow install a different Recovery partition or anything. You'd need Root before installing Rom Toolbox Pro first though, so I'd need to find the best/easiest way to gain Root Access on this handset first.
Thanks
Whip Cracker said:
Hi everyone,
Just spent the best part of 2 hours wondering how I go about installing some kind of custom recovery on my wife's Note 3 (SN9005) so I can run SlimKat on it.
It's currently running MJ7 firmware.
Question: Can this phone have a custom recovery installed so I can flash a different ROM?
I understand that the bootloader is "locked", but it seems that I can still go on my merry way and install a custom recovery and ROM, but Knox will flag that I've changed it.
Can someone please explain to me my options if that's ok?
Thanks very much
Click to expand...
Click to collapse
Bootloader is not locked. Just install CWM/TWRP using Odin, then boot into recovery and flash your ROM.
Knox will be broken, but otherwise you should be fine.
jisoo said:
Knox will be broken,
Click to expand...
Click to collapse
My Knox was broken first day I had the phone. Was a wonderful thing I did.
Thanks for the answers everyone
Hi,
I'm using AT&T S4 running 4.4.4 have nj4 bootloader and currently rooted. My Question is if I downgrade to stock i.e. MDB will I be able to install Custom ROM like Cynagenmod ? Please reply
I'm going back to stock using this Guide
Thanks
I assume you want to downgrade from a locked bootloader to an unlocked bootloader. Based on everything I have read, this cannot be done.
http://forum.xda-developers.com/showthread.php?t=2257620
taqi110 said:
Hi,
I'm using AT&T S4 running 4.4.4 have nj4 bootloader and currently rooted. My Question is if I downgrade to stock i.e. MDB will I be able to install Custom ROM like Cynagenmod ? Please reply
I'm going back to stock using this Guide
Thanks
Click to expand...
Click to collapse
If you could downgrade to stock unlocked bootloader, you could be able to install Custom rom like cyanogenmod (CM). So far, we do not have solution to downgrade to unlocked bootloader from the locked bootloader. The lowest you can go without tripping the knox counter is NB1.
If you want to install the CM, there is a safestrap version availible on xda. You can find it here.
sway8966 said:
If you could downgrade to stock unlocked bootloader, you could be able to install Custom rom like cyanogenmod (CM). So far, we do not have solution to downgrade to unlocked bootloader from the locked bootloader. The lowest you can go without tripping the knox counter is NB1.
If you want to install the CM, there is a safestrap version availible on xda. You can find it here.
Click to expand...
Click to collapse
Thanks for the link will check it. I have another problem with nj4 kernel
I wanted to change android mode from enforcing to permissive so I downloaded an app called se mod changer but the problem is that when I select permissive it just revert back to enforcing without any error. I also tried to change mod using terminal but that also revert back to enforcing.
I tried this app on moto x and s3 and it worked fine.
If I downgrade to nb1 will I be ablw.to change mod ?
Thanks
taqi110 said:
Thanks for the link will check it. I have another problem with nj4 kernel
I wanted to change android mode from enforcing to permissive so I downloaded an app called se mod changer but the problem is that when I select permissive it just revert back to enforcing without any error. I also tried to change mod using terminal but that also revert back to enforcing.
I tried this app on moto x and s3 and it worked fine.
If I downgrade to nb1 will I be ablw.to change mod ?
Thanks
Click to expand...
Click to collapse
What I understand about SELinux Mode changer is it depends on the kernel that you are using. The kernel has to be complied such a way that SELinux mode can be changeable.. When I was on kit-kat, I was using GE roms. The cooker included a safestrap flashable modified AT&T kernel so we could change the SElinux mode and to be able to use the xPose module.