Related
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
Yeah, it's odd. Doesn't work for me either. Even after multiple reboots. I'd love for someone to chime in for more details. I know this has been talked about somewhere, but the only answer I remember was selecting fake official status in Wanam and reboot a few times after that. After many reboots, it's still CUSTOM, but Knox and everything is 0x0. Thanks.
war1957 said:
Rooted my AT&T Note 3 with Kingo - great - easy.
Trying to get rid of the *Custom* sign and lock at the boot screen.
Installed XposedInstaller and WANAM to make it show Official Status instead of Custom.
Went into WANAM security hacks tab and checked for taking off Custom.
Rebooted as instructed.
Doesn't work.
Any ideas / workarounds ?
Click to expand...
Click to collapse
That's really weird, because this worked fine for me. I didn't do anything differently though, are you sure you have Wanam enabled in the Xposed Framework? After you download a module you usually have to enable it. I would try unchecking and checking, rebooting in-between.
It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....
When I removed the "Custom" icon from startup screen, it took more than one reboot cycle to go away.
The first reboot after applying the setting, there was still the "Custom" and unlocked lock. I thought nothing of it, since I didn't really care... But at some point after that, with no further action in Wanam, the "Custom" stopped showing on reboot.
I rooted again with the same method and custom miraculously vanished.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
LuckyColdJohnson said:
It's true. You have to enable that module within the Xposed App. Try a total shut down and not just a reboot as well.
Pull your battery. After that, the icon will go away. You also need to go look at your About Phone and see system status. Make sure it shows Official (It should). Good Luck and let us know....
Click to expand...
Click to collapse
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:
war1957 said:
Tahnks a bunch
After the *hard reset* it decided to work.
Happy customer now !! :laugh:
Click to expand...
Click to collapse
Glad to hear that, and thanks for hitting the thanks button. I'm glad we could help. Now, I'm going to give you your first thanks for replying back. Thanks again.
Is there a way to remove the "Custom" padlock message while the phone reboots from an mj5 build? I am unrooted and still continue to receive this, padlock, need to exchange phone at best buy any suggestions?
Fidelio_o said:
Is there a way to remove the "Custom" padlock message while the phone reboots from an mj5 build? I am unrooted and still continue to receive this, padlock, need to exchange phone at best buy any suggestions?
Click to expand...
Click to collapse
Re-root with Kingo then unroot with SuperSU. (Full unroot in the settings menu) After you restart the padlock should be gone. You may need to restart a second time so the system can switch back to Official status. I've done it twice now and it worked both times.
archie87 said:
Re-root with Kingo then unroot with SuperSU. (Full unroot in the settings menu) After you restart the padlock should be gone. You may need to restart a second time so the system can switch back to Official status. I've done it twice now and it worked both times.
Click to expand...
Click to collapse
Going to give it a shot.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Didn't work, try it like 5 times. no go.
Fidelio_o said:
Didn't work, try it like 5 times. no go.
Click to expand...
Click to collapse
Hmm strange. I must have gotten lucky.
you will have to use this and do a full install so it shows its not custom
http://forum.xda-developers.com/showthread.php?t=2559715
Download Wanam Xposed from the market. There's a hack in there to prevent the dreaded padlock
Sent from my SAMSUNG-SM-N900A using xda premium
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Bruce0750 said:
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
What IF they do a factory reset on the phone.....will this not just wipe the wanam exposed settings and BAM!!! the padlock will back and look even more like you messed up your phone?
i got my exchanged and had this same problem, they went through the phone scrupulously trying to find something that pointed to me tampering. they attempted to do a factory reset but with the state that i left my phone they could not even attempt that. but they tried, which will make your solution a Big Hell No once the reset brings that padlock back....they wont even talk to you anymore.
Bruce0750 said:
Yup wanam solves it easily. First get Xposed framework, then install wanam, then in the security hack section in wanam, choose fake system status, reboot.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Didn't work for me. Padlock still there at start up.
edessa said:
Didn't work for me. Padlock still there at start up.
Click to expand...
Click to collapse
how did you reboot your phone? you have to use wanam's reboot option to do so, just so wanam can update things to the system. if you reboot by other means, especially by holding the power bottom and select reboot, it won't get ride of the pad lock.
We'll that explains it. In the mean time stupid AT&T updated my phone when I wasn't looking. I am now put to MJ5. I guess I can try to root with kingo.
Edessa Kingo will root MJ5. Im on MJ5 and rooted with Kingo. You may have to run program 5to6 times but it works
Sent from my SAMSUNG-SM-N900A using xda app-developers app
I got it to work by rooting and deleting busybox from system/bin and system/xbin. Which survives even after a factory reset. Was able to exchange the phone no problem after using full unroot from within SuPro. No padlock.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Hello everyone,
So i have towel rooted the S5, it's great and works fine except for a couple things. Like the title says, neither s-voice or s-health update. They both keep telling me they have updates but, when I try to update the app force closes. Unfortunately "blank" has stopped. I was wondering is this because of towel root or another reason. Any help would be appreciated.
Thanks
Namikaze Minato said:
Hello everyone,
So i have towel rooted the S5, it's great and works fine except for a couple things. Like the title says, neither s-voice or s-health update. They both keep telling me they have updates but, when I try to update the app force closes. Unfortunately "blank" has stopped. I was wondering is this because of towel root or another reason. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
do you have xposed install
have you cleared cache??
If you have xposed do here http://forum.xda-developers.com/showthread.php?t=2784945
Then wipe apps cache and done
Sent from my SAMSUNG-SM-G900A using Tapatalk
carlospr21 said:
do you have xposed install
have you cleared cache??
If you have xposed do here http://forum.xda-developers.com/showthread.php?t=2784945
Then wipe apps cache and done
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I do not have xposed installed. Does this mean I just have to wipe the cache from the settings app?
Yes, thats what he means. Going to app manager and clearing cache
I had updated everything before I used towelroot, so I can only help in saying that a few days ago I updated with no problem.
I might also try a difference between WIFI and Data attempting to update.
Namikaze Minato said:
I do not have xposed installed. Does this mean I just have to wipe the cache from the settings app?
Click to expand...
Click to collapse
yes sir or drag it to the app drawer on top it says App Info you can clear it from there
Sent from my SAMSUNG-SM-G900A using Tapatalk
johns86 said:
Yes, thats what he means. Going to app manager and clearing cache
I had updated everything before I used towelroot, so I can only help in saying that a few days ago I updated with no problem.
I might also try a difference between WIFI and Data attempting to update.
Click to expand...
Click to collapse
I just tried to go through app manager and clear the cache and it still doesn't fix the problem. I'm thinking the only way to get around this would to be uproot and then update and root again. My only complaint about that way is - do I have to do that everytime these apps want to update?
Namikaze Minato said:
I just tried to go through app manager and clear the cache and it still doesn't fix the problem. I'm thinking the only way to get around this would to be uproot and then update and root again. My only complaint about that way is - do I have to do that everytime these apps want to update?
Click to expand...
Click to collapse
I've updated plenty of apps since then. I wouldn't get carried away right off the bat.
There are several factors that could be preventing it from updating that are out of your control. Next thing I'd try, a stupid, yet simple. turn off, pull battery, turn on and try again. If that doesn't work just wait 12 or 24 hours before attempting again.
Like I said before, stuff out of your control, servers, networks, etc.
Namikaze Minato said:
I just tried to go through app manager and clear the cache and it still doesn't fix the problem. I'm thinking the only way to get around this would to be uproot and then update and root again. My only complaint about that way is - do I have to do that everytime these apps want to update?
Click to expand...
Click to collapse
FOUND IT!
I'm sorry for all the trouble guys but I found the problem. What I forgot was that I froze the Samsung appstore app from within titanium backup. Realizing those are Samsung apps and not the playstore apps and defrosting the Samsung appstore is what fixed the problem.
Thank you again for trying to help. Also really sorry for the trouble. Will hit "thanks" to the responders!
Namikaze Minato said:
FOUND IT!
I'm sorry for all the trouble guys but I found the problem. What I forgot was that I froze the Samsung appstore app from within titanium backup. Realizing those are Samsung apps and not the playstore apps and defrosting the Samsung appstore is what fixed the problem.
Thank you again for trying to help. Also really sorry for the trouble. Will hit "thanks" to the responders!
Click to expand...
Click to collapse
lol...yea, that'll do it!
Namikaze Minato said:
FOUND IT!
I'm sorry for all the trouble guys but I found the problem. What I forgot was that I froze the Samsung appstore app from within titanium backup. Realizing those are Samsung apps and not the playstore apps and defrosting the Samsung appstore is what fixed the problem.
Thank you again for trying to help. Also really sorry for the trouble. Will hit "thanks" to the responders!
Click to expand...
Click to collapse
hahahaha stuff like thats happens when your rooted!!! [emoji38]
Sent from my SAMSUNG-SM-G900A using Tapatalk
Since no one has mentioned this, I just wanted to point out that you can use ART runtime on stock KitKat. I have been using this for a long time and have not had any problems. It is faster in my opinion.
zowpow said:
Since no one has mentioned this, I just wanted to point out that you can use ART runtime on stock KitKat. I have been using this for a long time and have not had any problems. It is faster in my opinion.
Click to expand...
Click to collapse
How?
woshiweili said:
How?
Click to expand...
Click to collapse
Go to Settings/About Phone
Go to Software Information
Tap the "Build Number" a bunch of times until it says "you are now a developer"
Now go back to Settings and you should find a new "developer options" category
Press Select Runtime and then select ART
Restart the phone, first restart of the phone will take a long time, around 20 minutes for me
Has anyone else tried this?
I changed the settings and the phone restarted, but it stuck with dalvik
Because is just a beta for developers, some aps are going to run fine, maybe some aps are going to use Dalvik, anothers will just crash.
D1358531 said:
I changed the settings and the phone restarted, but it stuck with dalvik
Click to expand...
Click to collapse
Sorry for the late help but do you have xposed installed? if so you must uninstall xposed then switch to ART
krchi said:
Sorry for the late help but do you have xposed installed? if so you must uninstall xposed then switch to ART
Click to expand...
Click to collapse
Yep, I do have Xposed installed, thanks!
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
kdisn said:
I've tried installing Xposed several times now with no luck. I install in TWRP, reboot, and then my phone sits on a black screen with the blue light for forever until it goes to the Sprint LTE logo and then just stops there. I end up having to shut my phone down (which won't happen unless it's plugged in to charge), go back into TWRP, and then use the Xposed uninstaller. Then when I reboot, everything loads back up perfectly. I don't really know what's causing this? I apologize as I'm kind of a noob to rooting & such.
I have a Galaxy Note 5 SM-N920P on Android 6.0.1. Any advice?
(The only reason I really wanted to get Xposed is so I could install a module to bypass the root status for Snapchat...lol)
Click to expand...
Click to collapse
Which Xposed file did you flash?
Sent from my SCH-R220
mattzeller said:
Which Xposed file did you flash?
Sent from my SCH-R220
Click to expand...
Click to collapse
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
kdisn said:
I think I downloaded from here. Xda website wasn't working last night while I was doing it.
http://android.wonderhowto.com/how-...work-android-6-0-marshmallow-devices-0166278/
Click to expand...
Click to collapse
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
I'm running stock, yes. Thank you for the link. I'll try it and then let you know!!
mattzeller said:
If you running stock 6.0.1 and not a CM ROM you need the specialized one for Samsung. Check this thread:
http://forum.xda-developers.com/showthread.php?p=62377731
Don't forget after flashing it you should wipe caches, and it will take a little while to boot the first time after flashing Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
kdisn said:
The file you sent worked great still can't get into Snapchat though, but that's another issue. RootCloak doesn't do anything for it.
Click to expand...
Click to collapse
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
mattzeller said:
Suhide hides root from snapchat, but Snapchat doesn't want you to have Xposed. There is a work around involving backing up app data on an unrooted, no Xposed phone and restoring that app data on rooted and Xposed phone
Sent from my SCH-R220
Click to expand...
Click to collapse
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
kdisn said:
I have tried several things and have been unable to get Snapchat to login. I have a backup of a logged in Snapchat from an unrooted device and when I install it onto my rooted phone, the app just logs me out.
Click to expand...
Click to collapse
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
I'll try that. I flashed from Odin to wipe everything off and Snapchat works, but I don't have TWRP anymore. Even without Xposed and root, even when I JUST had TWRP, Snapchat wouldn't let me log in. But I'll try what you told me and hope it works
mattzeller said:
Maybe remove Xposed, then unroot, root systemless(at least SR2), root switch, then turn off root and login. Once logged in turn root back on and install Xposed. Should work
Sent from my SCH-R220
Click to expand...
Click to collapse
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
kdisn said:
So after a bunch of trouble with my phone, I'm left with what I can only assume are leftover files of Xposed that I didn't get off my phone when I flashed the uninstall file. I'm not rooted and only have TWRP, but Snapchat still refuses to let me login.
Click to expand...
Click to collapse
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
mattzeller said:
Maybe do a factory reset to clear those out and see if snapchat will work
Sent from my SCH-R220
Click to expand...
Click to collapse
I ran the uninstaller for Xposed again and it seems to have wiped the rest of the files because snapchat now lets me login. Now time to follow the instructions you gave me before w/ systemless rooting my NAND is backed up too just in case I screw up again.