i rooted my note 3 after the mj7 update and used the kingo root method, i never tred the de la vega method, but both methods mention at the start up a padlock with a customize under it, does anyone know how to remove this?
un4givn1 said:
i rooted my note 3 after the mj7 update and used the kingo root method, i never tred the de la vega method, but both methods mention at the start up a padlock with a customize under it, does anyone know how to remove this?
Click to expand...
Click to collapse
Install exposed framework module then download Wanam xposed from the market and enable it in exposed framework. Then in Wanam under security check the fake official status. Then reboot. Twice. Should be gone.
Sent from my GlaDos Baked Potato
Legato Bluesummers said:
Install exposed framework module then download Wanam xposed from the market and enable it in exposed framework. Then in Wanam under security check the fake official status. Then reboot. Twice. Should be gone.
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
That has not worked for most people (including me) since the mj7 update
jmorton10 said:
That has not worked for most people (including me) since the mj7 update
Click to expand...
Click to collapse
Worked fine for me. *shrug* someone else suggested using Triangle away from the market. Used to be a free link to us xda members in the forum. Just don't know where it is anymore
Sent from my GlaDos Baked Potato
Legato Bluesummers said:
Worked fine for me. *shrug*
Click to expand...
Click to collapse
Yea, it's weird. It worked fine for me until I flashed the mj7 firmware and it hasn't worked since (I've checked & rechecked the setting and rebooted it 20 times.
The sys module that is supposed to remove that doesn't work either. I've decided to just ignore it, I hardly ever reboot anyway
Xposed framework
un4givn1 said:
i rooted my note 3 after the mj7 update and used the kingo root method, i never tred the de la vega method, but both methods mention at the start up a padlock with a customize under it, does anyone know how to remove this?
Click to expand...
Click to collapse
Refer to xda thread on xposed framework..after thats installed go ahead and install the module called Wanam Xposed. This actually has an option under Security Hacks to remove custom logo. Its the option called Fake System Status.
Legato Bluesummers said:
Install exposed framework module then download Wanam xposed from the market and enable it in exposed framework. Then in Wanam under security check the fake official status. Then reboot. Twice. Should be gone.
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
I was one of the people that exposed didn't work for. However I just went into the exposed app and it prompted me to install the frame work and then after it still had the logo. I ended up doing a hard restart shortly after and the custom logo is gone.
Sent from my SM-N900V
jspencer89 said:
Its the option called Fake System Status.
Click to expand...
Click to collapse
Correct, it just doesn't work for me or a lot of other posters after flashing to the new firmware (it worked fine for me with the older firmware).
Legato Bluesummers said:
Worked fine for me. *shrug* someone else suggested using Triangle away from the market. Used to be a free link to us xda members in the forum. Just don't know where it is anymore
Sent from my GlaDos Baked Potato
Click to expand...
Click to collapse
My understanding is that you need to have an unlocked bootloader before using Triangle Away. Otherwise, you'll get a soft brick.
AlpineMan said:
My understanding is that you need to have an unlocked bootloader before using Triangle Away. Otherwise, you'll get a soft brick.
Click to expand...
Click to collapse
Did not know that. Only time I've ever used TA was on my unlocked galaxy S3. *shrug* I shall not be recommending this then.
Sent from my GlaDos Baked Potato
jmorton10 said:
That has not worked for most people (including me) since the mj7 update
Click to expand...
Click to collapse
I had it enabled before the update, then I had to disable the fake status, reboot, enable the fake status again, and after a reboot the lock was gone.
billinaz said:
I had it enabled before the update, then I had to disable the fake status, reboot, enable the fake status again, and after a reboot the lock was gone.
Click to expand...
Click to collapse
yea, that didn't work for me but since everything else in my system is working perfectly it's not something I'm losing any sleep over........
Here is the other thread with this issue:
http://forum.xda-developers.com/showthread.php?t=2517996
It wouldn't work for me either but eventually after a bunch of uninstall/reinstalls of everything (framework, wanam) toggling, rebooting (hard and soft) it decided to stick.. I know exactly what youre talking about though cause it was a pita for me too
NeoMagus said:
There was a few of us in the main update thread this happened to.. wasn't because of safestrap for me but it seemed after reinstalling Adaway and doing some other /system stuff the icon and custom status came back and would not go away.. only thing I can suggest after uninstalling framework/wanam, reboot, reinstalling the framework, reboot, reinstall/toggle wanam, reboot, multiple times toggling the options in the app and rebooting (regular/ and soft reboot) it finally stuck for me dont know what it was that finally got it, but I feel your pain cause it pissed me off the past two days
Click to expand...
Click to collapse
jmorton10 said:
Yea, it's weird. It worked fine for me until I flashed the mj7 firmware and it hasn't worked since (I've checked & rechecked the setting and rebooted it 20 times.
The sys module that is supposed to remove that doesn't work either. I've decided to just ignore it, I hardly ever reboot anyway
Click to expand...
Click to collapse
You have to reset flash counter.
Sent from my SM-N900V using Tapatalk
On beans build 2 I ran it and it set status to official, but reboot still shows the custom unlock screen.
Sent from my SM-N900V using xda app-developers app
Triangle away app http://forum.xda-developers.com/showthread.php?t=1494114
It worked for me and I'm on the map build
Sent from my SM-N900V using xda app-developers app
---------- Post added at 10:48 PM ---------- Previous post was at 10:47 PM ----------
Darn auto text. What I meant to say is that.....it worked for me and I'm on the MJ7 build
Sent from my SM-N900V using xda app-developers app
anyone figure out a fix for this yet? I didnt want to start my own thread on it
b00sted said:
anyone figure out a fix for this yet? I didnt want to start my own thread on it
Click to expand...
Click to collapse
Works for most people still with Wanam. Otherwise the "triangle away" app from the play store works as well.
njfoses said:
Works for most people still with Wanam. Otherwise the "triangle away" app from the play store works as well.
Click to expand...
Click to collapse
Worked for me until I updated roms and now it won't go away. Both were on current update.
Just my. 02
Tap'n & Talk'n on my Note 3
Related
Okay so I am brand new to the Android OS. I have been an iPhone user for about 5 years and jailbreaking was such a simple task and I fully understood how that worked. I'm glad I made the switch to android because it does everything a jailbroken iPhone does. I just found out about this rooting stuff. How does it work and how can I do it with Note 3 on AT&T SM-N900A? I downloaded some new OTA update but I don't know what it means.
I am an Android noob
kyco16 said:
Okay so I am brand new to the Android OS. I have been an iPhone user for about 5 years and jailbreaking was such a simple task and I fully understood how that worked. I'm glad I made the switch to android because it does everything a jailbroken iPhone does. I just found out about this rooting stuff. How does it work and how can I do it with Note 3 on AT&T SM-N900A? I downloaded some new OTA update but I don't know what it means.
I am an Android noob
Click to expand...
Click to collapse
Kingo Root is the only current method to root MJ5, its really simple and fast if you chose to do so. Its just a program on you pC that you run and it will give you root and reboot your phone and your done.
the2rrell said:
Kingo Root is the only current method to root MJ5, its really simple and fast if you chose to do so. Its just a program on you pC that you run and it will give you root and reboot your phone and your done.
Click to expand...
Click to collapse
Are you kidding? Is it really that easy? I've been reading about all this Root De La Vega thing. Your way seems to be a lot easier. Why doesn't everyone use this Kingo Root program?
kyco16 said:
Are you kidding? Is it really that easy? I've been reading about all this Root De La Vega thing. Your way seems to be a lot easier. Why doesn't everyone use this Kingo Root program?
Click to expand...
Click to collapse
RdlV is for versions prior to your MJ5. Don't even think about using it!
Kingo Root works well but is suspected to be malware (search for details) and all links to it have been banned from xda until kingo devs prove it is safe. That doesn't seem to be happening very quickly.
kraz
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
krazman325 said:
RdlV is for versions prior to your MJ5. Don't even think about using it!
Kingo Root works well but is suspected to be malware (search for details) and all links to it have been banned from xda until kingo devs prove it is safe. That doesn't seem to be happening very quickly.
kraz
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I too just upgraded from my note 2 to the 3 last night.. i have MI9 on mine and i was sble to do the Rdlv method and mine is rooted and running ok. Is there a problem with doing this? I am going to freeze the updater so that no OTA runs and i dont lose root.. any issues?
RdlV was created for MI1 and MI9 only. You're okay! kraz
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Zugshad said:
I too just upgraded from my note 2 to the 3 last night.. i have MI9 on mine and i was sble to do the Rdlv method and mine is rooted and running ok. Is there a problem with doing this? I am going to freeze the updater so that no OTA runs and i dont lose root.. any issues?
Click to expand...
Click to collapse
Just so you know, you can take the ota and keep root as long as you follow the proper steps, I uploaded to mj5 and kept root, no issues.
Sent from my SAMSUNG-SM-N900A using Tapatalk
clothednblack1 said:
Just so you know, you can take the ota and keep root as long as you follow the proper steps, I uploaded to mj5 and kept root, no issues.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Thanks.. i found the ATT update thread in here and followed the steps .. i was rooted with mi9 and upgraded to SU pro and then did the survival mode with disabling SU and then did the update. it updated to MJ5 and then i turned off survival mode and re-enabeled SU and i am still rooted and my apps so far are working fine...
so,, for the OP.. just back out of this and go into the ATT update thread and folllow the instructions there (i basically posted it above, but a cleaner "how to" is in there)
Zug
I am on MJ5, can I still use the 'Root De La Vega' method or is the only option this Kingo Root?
ZishanMalik said:
I am on MJ5, can I still use the 'Root De La Vega' method or is the only option this Kingo Root?
Click to expand...
Click to collapse
You will brick your device if you use RDLV.
As far as I know, Kingo will work. However, due to it sending our IMEI number to China, I don't wanna do it yet.
econan1214 said:
You will brick your device if you use RDLV.
As far as I know, Kingo will work. However, due to it sending our IMEI number to China, I don't wanna do it yet.
Click to expand...
Click to collapse
They said the newest Kingo update removed those calls back home and that they won't be doing that anymore. I don't know anything about them sending IMEI info to China, but supposedly the connections to their servers in China was to download the updates as the program rooted the phone.
I was skeptical about kingo root but after doing some research I went ahead and did it and everything seems to be fine. Yes, it takes your imei but no one really knows what they do with it if anything. All rooting is, is finding exploits and utilizing them to gain root access. In all actuality, you never truly know the intentions of any new developers that come on the scene.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
jtmj06 said:
I was skeptical about kingo root but after doing some research I went ahead and did it and everything seems to be fine. Yes, it takes your imei but no one really knows what they do with it if anything. All rooting is, is finding exploits and utilizing them to gain root access. In all actuality, you never truly know the intentions of any new developers that come on the scene.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agree 100% its simple and i doubt they take the IMEI .... It works 100%
I'm MJ5. If I use Kingo is there anything I need to turn off (OTA/Security updates)?
MI9 to MJ5 while rooted
Hi Zug
I tried the method with survival mode and disabling superuser and the official mode in Wanam to try to go from MI9 to MJ5 ......everything is fine until it reboots but always fails at 27% point of installation. ... trotted it 7 or so times. .... Same result. After the fail it reboots and I get the message "update interrupted".
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Replay
ZishanMalik said:
I am on MJ5, can I still use the 'Root De La Vega' method or is the only option this Kingo Root?
Click to expand...
Click to collapse
You will brick your device if you use RDLV.
As far as I know, Kingo will work. However, due to it sending our IMEI number to China, I don't wanna do it yet.
wayne8821212 said:
Hi Zug
I tried the method with survival mode and disabling superuser and the official mode in Wanam to try to go from MI9 to MJ5 ......everything is fine until it reboots but always fails at 27% point of installation. ... trotted it 7 or so times. .... Same result. After the fail it reboots and I get the message "update interrupted".
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I remember reading about users having the same issue with the instalation stalling at the same percentage every time. It has something to do with you changing something (can be a number of things) in the system folder. Think about it, did you change the boot animation? There is a thread talking about it, I'll see if I can't find it for ya.
Cant root MJ5 with kingroot or vroot?
hoangps said:
Cant root MJ5 with kingroot or vroot?
Click to expand...
Click to collapse
I rooted with kingo on mj5 with no issue.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Updating to from MI9 to MJ5 problems
DustinKimble said:
I remember reading about users having the same issue with the instalation stalling at the same percentage every time. It has something to do with you changing something (can be a number of things) in the system folder. Think about it, did you change the boot animation? There is a thread talking about it, I'll see if I can't find it for ya.
Click to expand...
Click to collapse
Thanks Dustin!
I finally solved 2 problems (the installation problem and the sudden failure of Kies3 to see my phone) by going to recovery, doing a wipe data and cache and factory reset. I then re-rooted using the De La Vega method, disabled root and checked "survival mode in SuperSU Pro and then accepted the update to MJ5. This time it made it past the 27% installation point and completed. The I re-enabled root in SuperSU Pro launched titanium backup and batch restored apps and all is well. So I am finally rooted and on MJ5 without having to use Kingo. Thanks for your help.
well I flashed the firmware just fine...no problems...but when I tried to root it, it got stuck in bootloop...if I pull the battery and restart its just fine, but no root....help?....lol thanks in advance...I have found a few cf-root files on the web, but every time I flash any of them I get stuck in bootloop...also...no custom recovery....yet....So confused...
Which phone do you have and os?
Sent from my SM-N900W8 using xda app-developers app
hey_joe said:
Which phone do you have and os?
Sent from my SM-N900W8 using xda app-developers app
Click to expand...
Click to collapse
sorry...tmobile SM-N900T , RUNNING LATEST STOCK KIT KAT 4.4.2
You found a few cf root files on the web... well ain't that cute. Isn't there just one cf root file for your model ? Flash the right one and your good.
Sent from my N9005
Dirtylarry11 said:
sorry...tmobile SM-N900T , RUNNING LATEST STOCK KIT KAT 4.4.2
Click to expand...
Click to collapse
Link below is suppose to be the one for your phone but I'm not sure if cf updated it already for 4.4.
http://download.chainfire.eu/354/CF-Root/CF-Auto-Root/CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
Sent from my SM-N900W8 using xda app-developers app
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Make sure reactivation lock is off or you won't be able to root.
Sent from my SM-N900W8 using xda app-developers app
hey_joe said:
Link below is suppose to be the one for your phone but I'm not sure if cf updated it already for 4.4.
http://download.chainfire.eu/354/CF-Root/CF-Auto-Root/CF-Auto-Root-hltetmo-hltetmo-smn900t.zip
Sent from my SM-N900W8 using xda app-developers app
---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------
Make sure reactivation lock is off or you won't be able to root.
Sent from my SM-N900W8 using xda app-developers app
Click to expand...
Click to collapse
ok, I got the right file...always did have the correct one after double checking....what is this reactivation lock?...I read the pdf file, but I don't see any downloads etc?...
Download is at the bottom of the link and it's a zip file. You can check in download mode whether reactivation lock is off or on.
Sent from my SM-N900W8 using xda app-developers app
Dirtylarry11 said:
ok, I got the right file...always did have the correct one after double checking....what is this reactivation lock?...I read the pdf file, but I don't see any downloads etc?...
Click to expand...
Click to collapse
Settings > security > reactivation lock > uncheck it. (for future reference)
Reactivation Lock is a security feature implemented that if you have on and you lose/have your phone stolen it is tied to your Samsung account. If someone tries to flash a new ROM/Reset it, they cannot as it will require your Samsung account info to get past the setup screen.
radicalisto said:
Settings > security > reactivation lock > uncheck it. (for future reference)
Reactivation Lock is a security feature implemented that if you have on and you lose/have your phone stolen it is tied to your Samsung account. If someone tries to flash a new ROM/Reset it, they cannot as it will require your Samsung account info to get past the setup screen.
Click to expand...
Click to collapse
ok, thank you, but I don't have this listed under securitymine says encrypt device, then encrypt external sd card, and then it sasy sim card lock...no reactivation lock anywhere
Dirtylarry11 said:
ok, thank you, but I don't have this listed under securitymine says encrypt device, then encrypt external sd card, and then it sasy sim card lock...no reactivation lock anywhere
Click to expand...
Click to collapse
Off the top of my head it should be in there or around security - (not currently using my N3 as it's got a broken screen so using my N5). -
radicalisto said:
Off the top of my head it should be in there or around security - (not currently using my N3 as it's got a broken screen so using my N5). -
Click to expand...
Click to collapse
I just looked at all the setting screens and when into each sub screen..I don't have it there on any of them...hmmm
Dirtylarry11 said:
ok, thank you, but I don't have this listed under securitymine says encrypt device, then encrypt external sd card, and then it sasy sim card lock...no reactivation lock anywhere
Click to expand...
Click to collapse
That's weird. When i go to security settings, top one is encrypt, below that is find my mobile section and reactivation lock is at the bottom of that section.
Sent from my SM-N900W8 using xda app-developers app
Do T-Mobile offer a different method of locating a device? Like Lookout or something? I know one of the US carriers do - it's possible the firmware has been adjusted to reflect this due to any deal the carrier may have.
radicalisto said:
Do T-Mobile offer a different method of locating a device? Like Lookout or something? I know one of the US carriers do - it's possible the firmware has been adjusted to reflect this due to any deal the carrier may have.
Click to expand...
Click to collapse
next to RP SWREV in download mode I see this: S2_T2_R2_A3_P2...but according to a leaked PDF file, it should show this:S2_T2_R2_A2_P2 for tmobile...I think Tmobile does use lookout, but what the heck do I do at this point?..I am sooo confused on all this stuff!!!!....lol.....Thanks a million
Here's how it looks on mine.
Sent from my SM-N900W8 using xda app-developers app
Dirtylarry11 said:
next to RP SWREV in download mode I see this: S2_T2_R2_A3_P2...but according to a leaked PDF file, it should show this:S2_T2_R2_A2_P2 for tmobile...I think Tmobile does use lookout, but what the heck do I do at this point?..I am sooo confused on all this stuff!!!!....lol.....Thanks a million
Click to expand...
Click to collapse
EDIT: Post a pic of your device in download mode if you can also!
I wouldn't worry too much about the S T R A P number versions currently, I think best thing to do is wipe the device, reflash your stock and start again with the CF-AutoRoot that was posted in the thread. It's possible something just may have corupted on you somewhere along the line.
radicalisto said:
EDIT: Post a pic of your device in download mode if you can also!
I wouldn't worry too much about the S T R A P number versions currently, I think best thing to do is wipe the device, reflash your stock and start again with the CF-AutoRoot that was posted in the thread. It's possible something just may have corupted on you somewhere along the line.
Click to expand...
Click to collapse
ok, here is what I did:
1: install firmware. it reboots...then shows the android ..( he turns blue), then restarts ....phone works fine.
2: install the cf-root from above link and it installs fine, but then on reboot it gets stuck in "Seanandroid enforcing (something like that) and just keeps rebooting like it wants to go into recovery, but it never does...just bootloops.
3: I read in CF forum to turn off..pull battery and try again...same thing.
Do I need to load a recovery file?..am I missing a step or doing it out of order perhaps?
It's possible that the cf file you are using isn't compatible with the N900T - to be 100% certain you'd have to go over to the T-Mobile Note 3 forum on here and have a look through their cf auto root thread to be sure one way or another. It's puzzled me especially since the method you're using seems correct.
Sent from my Nexus 5 using XDA Premium 4 mobile app
radicalisto said:
It's possible that the cf file you are using isn't compatible with the N900T - to be 100% certain you'd have to go over to the T-Mobile Note 3 forum on here and have a look through their cf auto root thread to be sure one way or another. It's puzzled me especially since the method you're using seems correct.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will do that, thank you...I just saw this online in another forum with others having the same problem:
"I upgraded to kitkat 4.4.2 Note 3 SM-900T and even after odin says pass, it is stuck in Boot loop (which I know how to get out of) and I get this message like everyone else;
Recovery Booting...
Recovery is not seandroid enforcing
Set warranty bit: recovery"
uh -oh....lol...interesting find.
Uh oh indeed. Chainfire may have fixed it since though, he's pretty quick as updating and fixing things as soon as he's made aware of changes.
Sent from my Nexus 5 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2696537
Link below ~
its ready
http://download.chainfire.eu/408/CF-Root/CF-Auto-Root/CF-Auto-Root-kltespr-kltespr-smg900p.zip
it now says our model is supported.... who will be first to test it out, lol
evilbeef54 said:
it now says our model is supported.... who will be first to test it out, lol
Click to expand...
Click to collapse
Here goes nothing..
camdz said:
Here goes nothing..
Click to expand...
Click to collapse
fingers crossed, good luck
evilbeef54 said:
fingers crossed, good luck
Click to expand...
Click to collapse
The hardest part was waiting for the Samsung drivers to install onto my laptop!
It worked..and Im rooted!
There was a warning that popped up when I opened SuperSU that says KNOXX is enabled, and asked if I wanted to try to disable. I chose "yes" and it prompted me that it is now disabled. Im not sure what that means though? I was under the impression KNOXX was here to stay?
camdz said:
The hardest part was waiting for the Samsung drivers to install onto my laptop!
It worked..and Im rooted!
Click to expand...
Click to collapse
awesome, me too, rooted now, de-bloating commences
I love coming home from the Sprint store and being able to root immediately. Here we go!
EDIT: 30 seconds later, I'm rooted.
it doesnt seem to like it when you delete system apps through TiBu, lol, TiBu crashed upon deleteing the lumina tool bar and one of the other apps, they went away though so we win, lol
So glad to have the root (it worked just like it said). Time to clean up the bloatware now. Thanks!
Works!
Yes, it did only take 30 seconds. No drivers needed on Win 8 update 1 update 1.
Im rooted. That was easy. Thx to Chainfire. Amazing
SPRINT :C
Won't let my download the zip, just tells my its corrupt on both my laptop and PC, any ideas?
So this is use with Odin, correct?
Sent from my SPH-L710 using XDA Premium 4 mobile app
camdz said:
The hardest part was waiting for the Samsung drivers to install onto my laptop!
It worked..and Im rooted!
There was a warning that popped up when I opened SuperSU that says KNOXX is enabled, and asked if I wanted to try to disable. I chose "yes" and it prompted me that it is now disabled. Im not sure what that means though? I was under the impression KNOXX was here to stay?
Click to expand...
Click to collapse
That disables the software side of KNOX. The part in the bootloader is still there
eloko said:
So this is use with Odin, correct?
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yup
Tether? what is everyone using to tether once rooted?
evilbeef54 said:
awesome, me too, rooted now, de-bloating commences
Click to expand...
Click to collapse
Pretty sure it does but did it trip the KNOX counter?
Did anyone else loss their wifi with rooting their phone?
---------- Post added at 05:19 AM ---------- Previous post was at 05:13 AM ----------
ernicoats said:
Did anyone else loss their wifi with rooting their phone?
Click to expand...
Click to collapse
Fixed seems I had to put in airplane mode then back out.
"Failed to enable Private Mode. Try Again." Private Mode not supported with ART
I was trying out all the various features of my new S5 today and discovered when enabling Private Mode it flashes the following "Failed to enable Private Mode. Try Again." and obviously fails to enable Private Mode.
The only things I've done to my phone are enabling Developer Options and switching runtime to ART. I noticed that on reboot, having ART enabled displays the Custom unlock icon on the bootscreen. Does using ART prevent the usage of Private Mode?
EDIT: Switched back to Dalvik and verified Private Mode now works as expected.
I've had the same problem and I also have ART enabled
Sent from my SM-G900V using Tapatalk
Mjs830 said:
I've had the same problem and I also have ART enabled
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
One person @mexiken give me this suggestion for solving about Private mode. You can try it..
mexiken said:
Turn on Private Mode
Set the password option to use with it
Mark your photos, videos, music, etc that you want to set private via options
Turn off Private Mode
Turn back on when you want to see them.
Click to expand...
Click to collapse
Failed to enable private mode...... not fixed
Hi,
I have checked in my settings and I am running Dalvik not ART according to my phone. I have also included a screenshot.
But it still does not work?
I have attached a screenshot of the error "Failed to enable private mode..Please try again"
Can anyone shed any light on this please ?
Cheers
Paul
dpamdesign said:
Hi,
I have checked in my settings and I am running Dalvik not ART according to my phone. I have also included a screenshot.
But it still does not work?
I have attached a screenshot of the error "Failed to enable private mode..Please try again"
Can anyone shed any light on this please ?
Cheers
Paul
Click to expand...
Click to collapse
Paul weird, I am having the same issue as you. The only difference I installed The Governaa' - v0.2 kernel and now I'm running into that issue.Anyone has any idea? I forgot to mention I am on Sprint variant.
Thanks!
rsaavedra said:
Paul weird, I am having the same issue as you. The only difference I installed The Governaa' - v0.2 kernel and now I'm running into that issue.Anyone has any idea? I forgot to mention I am on Sprint variant.
Thanks!
Click to expand...
Click to collapse
Hiya,
Very strange, surely we cant be the only ones?......... lol
Same issue.
spuniun said:
I was trying out all the various features of my new S5 today and discovered when enabling Private Mode it flashes the following "Failed to enable Private Mode. Try Again." and obviously fails to enable Private Mode.
The only things I've done to my phone are enabling Developer Options and switching runtime to ART. I noticed that on reboot, having ART enabled displays the Custom unlock icon on the bootscreen. Does using ART prevent the usage of Private Mode?
EDIT: Switched back to Dalvik and verified Private Mode now works as expected.
Click to expand...
Click to collapse
I to have this problem, however Dalvik is enabled and if I try to switch it reboots but does not go to ART.
nerdnation said:
I to have this problem, however Dalvik is enabled and if I try to switch it reboots but does not go to ART.
Click to expand...
Click to collapse
I have the exact same issue. Can't go into art mode and private mode was working before I rooted the phone. Does anyone know how to fix this?
Sent from my SM-G900T using XDA Free mobile app
Same issue with me. I'm on Davlik, rooted with Xposed, I'll try see if any of the modules may have broken it.
Im an omega fan. Just recently I did a search of his post and read that with knox triggered private mode won't enable. Can anyone confirm this?
http://forum.xda-developers.com/showthread.php?p=51957897&highlight=private+mode#post51957897
Sent from my SM-G900W8 using XDA Free mobile app
nerdnation said:
Im an omega fan. Just recently I did a search of his post and read that with knox triggered private mode won't enable. Can anyone confirm this?
http://forum.xda-developers.com/showthread.php?p=51957897&highlight=private+mode#post51957897
Sent from my SM-G900W8 using XDA Free mobile app
Click to expand...
Click to collapse
Since this is the Verizon SM-G900V forum, no we cannot confirm this as we have no root or unlocked bootloader. I would defer to chainfire's response on the matter.
nerdnation said:
Im an omega fan. Just recently I did a search of his post and read that with knox triggered private mode won't enable. Can anyone confirm this?
http://forum.xda-developers.com/showthread.php?p=51957897&highlight=private+mode#post51957897
Sent from my SM-G900W8 using XDA Free mobile app
Click to expand...
Click to collapse
This is really confusing - why are some people saying they've got it working after rooting (which trips knox) and others aren't able to get it working. If it was because of Knox, then it shouldn't work for anyone who rooted their device, let alone installed Xposed.
i fixed the problem
DroidsConcept said:
Same issue with me. I'm on Davlik, rooted with Xposed, I'll try see if any of the modules may have broken it.
Click to expand...
Click to collapse
i had recently used that Xposed and after that my private mode stopped working but i fixed the problem by uninstalling it and it was working again.. u may wanna rot it another method with superSU..
EP2008 said:
This is really confusing - why are some people saying they've got it working after rooting (which trips knox) and others aren't able to get it working. If it was because of Knox, then it shouldn't work for anyone who rooted their device, let alone installed Xposed.
Click to expand...
Click to collapse
maybe because rooting your phone DOES NOT trip knox lol
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
maybe because rooting your phone DOES NOT trip knox lol
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
It does according to Chainfire (and users who root). Triggered it on my Note 2 and Note 4.
Is it different for the S5?
EP2008 said:
It does according to Chainfire (and users who root). Triggered it on my Note 2 and Note 4.
Is it different for the S5?
Click to expand...
Click to collapse
Yes, on the VZW S5 it dosen't trip Knox. I'm pretty sure Chainfire is refering to CF Autoroot witch dosen't work on our locked bootloaders. We have to use towelroot.
Misterxtc said:
Yes, on the VZW S5 it dosen't trip Knox.
Click to expand...
Click to collapse
You're lucky! :laugh::laugh:
EP2008 said:
It does according to Chainfire (and users who root). Triggered it on my Note 2 and Note 4.
Is it different for the S5?
Click to expand...
Click to collapse
yea.. knox is tripped when you mess with the bootloader but on the g900v n some others theyre locked so itd be pretty hard to trip knox
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 06:42 PM ---------- Previous post was at 06:41 PM ----------
EP2008 said:
You're lucky! :laugh::laugh:
Click to expand...
Click to collapse
not really lmao.. id much rather trip knox and have an unlocked bootloader than being locked down and no custom kernel/cwm etc
Sent from my SM-G900V using XDA Free mobile app
My note 4 is 0x1, exposed installed and i have private mode working
Sent from my SM-N910P using XDA Free mobile app
Well, I had Xposed installed, wanam xposed too. Uninstalled wanam, and uninstalled xposed's updates (or w.e. called) and it worked well.
P.S: Tested on G900F running Davlik
Hope that helps.
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
russ18uk said:
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
dladz said:
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
Click to expand...
Click to collapse
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
juDGEY2k10 said:
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
Click to expand...
Click to collapse
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
dladz said:
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
Click to expand...
Click to collapse
Not sure larr, i dont care myself best ask about before you jump in
Try this...
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
solution..
dladz said:
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Click to expand...
Click to collapse
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
juDGEY2k10 said:
Not sure larr, i dont care myself best ask about before you jump in
Click to expand...
Click to collapse
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
fffft said:
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
Click to expand...
Click to collapse
Dude are you going to post on every thread i make? Just to tell me to search? You're offering nothing in the way of a solution, more to the point, both the threads i've created were for unique questions, not all my questions are answered in other threads.
Please stop just commenting to say search.
yash kariya said:
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
Click to expand...
Click to collapse
My Galaxy app's application hasn't been deactivated m8, it's always been on, the second i turn on S-Health it crashes, it's because my system says custom when in download mode i believe, problem is i've now updated my OS so i'd need to reflash a stock rom via odin and then re-root if i wanted to have access to the location that the user before you mentioned. Been away from home for a few days so not had the chance, might do it tomorrow.
Thanks for the suggestion, but if I turn on S-Health now i know it'll begin crashing again.
aguarello said:
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
Click to expand...
Click to collapse
Will need root access for that, need to downgrade the OS back to a prior version. Will do it tomorrow.
Thanks for your help and to anyone else who offered something constructive.
dladz said:
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
Click to expand...
Click to collapse
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
juDGEY2k10 said:
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
Click to expand...
Click to collapse
Cheers fella, an I moved to London about 7 years ago, met a girl in London, was in Liverpool last saturday for my Stag night, dressed up like a bee gee with an afro and silver stacks, had a boss night m8, well until i fell on some stairs an near ripped my leg out of my hip joint, just spent 4 hours in the hospital getting X-rays. Worth it though
An yea Liverpool is a gorgeous City, night life is amazing we smashed it the other night