ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
DopeShow said:
ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
Click to expand...
Click to collapse
Open up Wanam and go to security hacks. In there it will have an option for "fake system status"
jagrave said:
Open up Wanam and go to security hacks. In there it will have an option for "fake system status"
Click to expand...
Click to collapse
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
DopeShow said:
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
Click to expand...
Click to collapse
Sorry man. I don't really use xposed a lot or s-health, so idk if there is another fix or not for that.
DopeShow said:
it nt look like im gonna be using wanam exposed cause its not letting my s health work and ive tried the fix and still wont work
Click to expand...
Click to collapse
You could give the xsecurestorage module a shot, you should be able to get shealth to work with xposed. Thr fix i know should be just disable secure storage, clear davlik cache and cache in recovery, then clear data of the s health app and reboot once more and it should work. Otherwise i dont know, there are quite a few threads on both disabling the padlock and getting xposed to play nice with shealth, just search around, supposedly triangleaway will remove the padlock i wouldnt count on it though.
Sent from my SM-G900A using Tapatalk
Rakuu said:
You could give the xsecurestorage module a shot, you should be able to get shealth to work with xposed. Thr fix i know should be just disable secure storage, clear davlik cache and cache in recovery, then clear data of the s health app and reboot once more and it should work. Otherwise i dont know, there are quite a few threads on both disabling the padlock and getting xposed to play nice with shealth, just search around, supposedly triangleaway will remove the padlock i wouldnt count on it though.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
I did the s health fix changing the securewstorage=true to false and reboot then reinstall exposed and nada s health wont even open I get that lil white window that pops up sayin s health has closed, so is there any other ways of getting this damn custom lock off my boot screen?
DopeShow said:
I did the s health fix changing the securewstorage=true to false and reboot then reinstall exposed and nada s health wont even open I get that lil white window that pops up sayin s health has closed, so is there any other ways of getting this damn custom lock off my boot screen?
Click to expand...
Click to collapse
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ive read turning off secure storage is not enough to get it working. Sit tight and i'll edit this post with some clearer instructions.
Edit:
Start by making for sure you have the xposed framework uninstalled, dont just uninstall the xposed installer app, you need to actually go in to the app and uninstall the framework, you should be able to keep the installer app installed though.
Next with a root enabled file explorer and open your build.prop file and just double check you have ro.securestorage.support set to false.
Now go in to the app info for s health, uninstall the updates, and clear the data and repeat for healthservice, then reboot in to stock recovery or safestrap and clear the cache and davlik cache.
Boot up and install xposed then for good measure reboot into recovery again, and clear the cache and davlik cache again, boot up and s health should work.
Past that i cant really help, this is all compiled from suggestions ive read, so im not sure how well all of it works due to the fact i dont even have s health installed, but good luck, hope you get it working.
Sent from my SM-G900A using Tapatalk
Rakuu said:
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ivr read turnin g off secure storage is not wniugh to get it working. Sit tight and i'll edit this post with some clearer instructions.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
no I did that to cleared the data and cach for s health in the all applications, I did everything in order and s health wont work.
Rakuu said:
I thibk you misssed the part where you clear data and cache of shealth and all that, from what ive read turning off secure storage is not enough to get it working. Sit tight and i'll edit this post with some clearer instructions.
Edit:
Start by making for sure you have the xposed framework uninstalled, dont just uninstall the xposed installer app, you need to actually go in to the app and uninstall the framework, you should be able to keep the installer app installed though.
Next with a root enabled file explorer and open your build.prop file and just double check you have ro.securestorage.support set to false.
Now go in to the app info for s health, uninstall the updates, and clear the data and repeat for healthservice, then reboot in to stock recovery or safestrap and clear the cache and davlik cache.
Boot up and install xposed then for good measure reboot into recovery again, and clear the cache and davlik cache again, boot up and s health should work.
Past that i cant really help, this is all compiled from suggestions ive read, so im not sure how well all of it works due to the fact i dont even have s health installed, but good luck, hope you get it working.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Thanks I appreciate you helpin me out, that only part I hadn't done in the past was boot into safestrap and clear cache and delvic cache, I thought it said to just go into the app info and clear cache and data there, but I guess after I get done doing a backup and saving the backup to my pc i'll give it another try with your instructions. thanks for taken the time out to help me bro.
DopeShow said:
Thanks I appreciate you helpin me out, that only part I hadn't done in the past was boot into safestrap and clear cache and delvic cache, I thought it said to just go into the app info and clear cache and data there, but I guess after I get done doing a backup and saving the backup to my pc i'll give it another try with your instructions. thanks for taken the time out to help me bro.
Click to expand...
Click to collapse
Just for refrence, thought id note safestrap recovery is not required to clear the cache and davlik cache, it works fine if done from stock recovery.
Sent from my SM-G900A using Tapatalk
Rakuu said:
Just for refrence, thought id note safestrap recovery is not required to clear the cache and davlik cache, it works fine if done from stock recovery.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
well thank you I just went through the steps you gave me and I finaly have wanam exposed installed and s health is working fine, only problem is I installed wanam so I could make the custom padlock on the boot screen be gone and I did what this other guy told me to do and it didn't work its still there
EDIT
YAYYYYYYYYYYYYYYYYYYY it did work and it took away the custom Unlocked Padlock damn im so happy.
DopeShow said:
well thank you I just went through the steps you gave me and I finaly have wanam exposed installed and s health is working fine, only problem is I installed wanam so I could make the custom padlock on the boot screen be gone and I did what this other guy told me to do and it didn't work its still there
Click to expand...
Click to collapse
You can check a couple things, check the module list and see if theres a check next to wanam indicating its enabled, if its not then enable it and reboot. If you have an sd card then long press on wanam in the module list or in yout launcher and go to its app info and see if its on the sd card, there should be a button that says either "move to sd card" or "move to device storage" if its the latter its on your sd card and that tends to mess things up, so move it to your phone's storage and then reboot, go to the module list and disable then reenable wanam then reboot.
Sent from my SM-G900A using Tapatalk
DopeShow said:
ok ive rooted my gs5 and ive also have wanam exposed on my device and I was told I could remove that custom unlocked padlock on the boot screen with wanam but I have looked through all the options in the wanam app and I don't see this option anywhere so could somebody please help me out and tell me how to make this custom padlock on boot screen to be gone. Thanks in advance
Click to expand...
Click to collapse
triangle away worked for me even though it's not official for it. just hit reset flash counter and reboot the phone
Rakuu said:
You can check a couple things, check the module list and see if theres a check next to wanam indicating its enabled, if its not then enable it and reboot. If you have an sd card then long press on wanam in the module list or in yout launcher and go to its app info and see if its on the sd card, there should be a button that says either "move to sd card" or "move to device storage" if its the latter its on your sd card and that tends to mess things up, so move it to your phone's storage and then reboot, go to the module list and disable then reenable wanam then reboot.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
everything is working 100% perfectly now that s health is working and I got the custom padlock gone from my boot screen using wanam and this phone is just badass right now with al the customized changes ive done with it and its running fast as hell
rnh said:
triangle away worked for me even though it's not official for it. just hit reset flash counter and reboot the phone
Click to expand...
Click to collapse
I didn't wanna brick my phone so I didn't attempt to use triangle away but I was able to remove the custom padlock from my boot screen using wanam
DopeShow said:
everything is working 100% perfectly now that s health is working and I got the custom padlock gone from my boot screen using wanam and this phone is just badass right now with al the customized changes ive done with it and its running fast as hell
Click to expand...
Click to collapse
Glad i could help
Sent from my SM-G900A using Tapatalk
Related
I am running CM 10.2 by Skrilax - http://skrilax.droid-developers.org/cm10.2nightly/razrqcom/index.php?device=xt907 (Might be fine with the DHacker version also, but this is what I used.
Pretty much everything seems to work including GPS. I do not have Bluetooth anything so I can't speak to that. Some (maybe most) people seem to have difficulty getting it installed, but it can be done. There are a few tricks to it. Here's what worked for me:
I highly recommend using TWRP 2.6.0 as that's what I use and I know it works. Not sure whether other recoveries will function the same or not.
What you need:
1. The most recent version of CM 10.2 from the link above.
2. Gapps Core 4.3 - http://goo.im/devs/BaNkS/GApps 4.3
3. Root for 4.3 - http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
1. Erase everything except the external sdcard. Do it three times. (Don't ask, just do it.)
2. Also Format Data - what the heck, do that 3 times too.
3. Install the CM 10.2 ROM, wipe dalvik and cache again and reboot into the system. DO NOT install anything else at this time for best results.
4. Let the OS boot all the way to the desktop.
5. Unlock the developer options by going into Settings\About Phone and tapping 8 times on Build number. (Only needs done one time, updates do not hide it again.)
6. In Developer options, change Root Access to "Apps and ADB". (Go ahead and set up whatever else you want in Settings.Do not install any apps or updates at this time.)
7. Reboot into Recovery. Install Gapps Core 4.3
8. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
9. Once the phone boots all the way, reboot into Recovery again and install Root using Supersu 1.43.
10. Clear dalvik and cache and reboot into System. If it hangs on the Motorola logo, get back into Recovery and format data again. (This is why I said don't install apps or updates yet.)
11. Once System has booted, you can update SuperSu in the Google Play Store. The first time you open it, it will want to update the binary. It's very important that you choose the option to do it from Recovery. Your phone will reboot into Recovery, update the binary and then boot back into System.
12. Once all this is done, so are you. Restore your apps, allow Google Play to do any updates, and customize the layout to your tastes.
Note: Once you get a successfully installed 10.2 setup, you can dirty flash the nightlies. Always clear dalvik and cache. And always backup your apps before flashing anything if you want to make your life easier.
ENJOY!!!
Going to give it a go with CWM I'll let you know how it goes.
Well I got the rom to work but I could not get it to boot after loading gapps. I tried wiping data but no joy!
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Flashed TWRP and I was able to get it up and running having the same issue with root going to try the file above and I'll update again.
edit
*** the supersu 1.51 file worked for me as well. ***
---------- Post added at 04:43 PM ---------- Previous post was at 03:47 PM ----------
I'm still having issues. I got the root to work but everytime I reboot the device I have wipe data or it hangs on the boot logo.
---------- Post added at 05:02 PM ---------- Previous post was at 04:43 PM ----------
Restored back to carbon rom 1.8. I may try again after a few more dailies are out. As this is my primary device I can not have the issues I saw. Admittedly it may be something that I did wrong and not the rom.
Sent from my XT907 using xda premium
Got this up and running last night and no issues so far for me. I'm wondering though if any custom kernels work with 10.2? I was curious about the vanquishpuppiesn12 kernel.
kensdavid said:
Hey, Thanks for the very clear update instructions - I'm now on CM 10.2!
I am not able to successfully root though. SuperSU complains:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!
If you just upgraded to Android 4.3, you need to manualyl re-root - consult the relevant forums for your device!"
I have tried to reflash the SuperSU zip posted here multiple times to no avail...
Thoughts?
EDIT: Solved with http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
Click to expand...
Click to collapse
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Thanks for sharing , make a mark
netizenmt said:
You must not have followed every step exactly. The process I outlined works flawlessly if it is followed exactly. I'm glad you were able to resolve it though. You ended up with the same result and that's what matters!
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
can you confirm if rear mic is working when taking videos? this has been the only hangup for me on the 4.2.2 ROMs...
I doubt it, since that functionality is probably kernel related, but still just curious...
thanks!
Ok I noticed that I had somehow installed the wrong TWRP I installed 2.6.0 today and I have so far had good luck phone is up and running and seems to be stable. At first I had some issues with a few apps throwing errors during the mass install when I sync'ed with Google but a manual download after and they installed just fine. Also the new camera app called focal has some issues for me it opened and took pics but images in gallery are blank. However the stock camera app seems to working fine at least for stills I have not tried video yet.
I've got this all working too, including root. But I've been noticing about a second delay when pressing power to unlock the phone. Sometimes it delays so long that I press power again. So when the phone does wake up, the screen goes off again from my double press of impatience. I'm running the 0907 nighlty
Sent from my XT907 using XDA Premium 4 mobile app
FWIW, never needed to wipe data multiple times and I flashed everything at once. That said, still a good procedure to follow
Also, @georgeascott, that's a known bug. It tends to SOD on occasion... Not much to do to fix except maybe overclocking
Sent from my XT907 using Tapatalk 4
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
zombolt said:
Any plans for safe strap support? My bootloader is apparently permanently locked. Stock isn't terrible.. You can disable and hide bloatware.. But it would be really nice to have pie instead of soft buttons and restart and screen shot on the power menu
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
sloosecannon said:
Probably not, but you can get some of that functionality with root alone if you know how to mod systemui and stuff like that. Probably not the answer you're looking for but that's probably what it is...
Can always hope someone will Dev for it though
Sent from my XT907 using Tapatalk 4
Click to expand...
Click to collapse
I have no clue how to do those things. I got really spoiled on the dinc. So many people spoon feeding contributions to a fabulous device. It sure is a shame it's impossible to unlock my boot loader
Sent from my XT907 using xda app-developers app
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
netizenmt,
Thx a lot for your help. I`m now on cm10.2, too.
But there seemed to be some bugs.
1.I cannot install any apps from Google Play Store, or it hangs on the MOTO logo after reboot.
2.I can take calls, but cannot reach the 3G network.
P.S.When I try to use QPST to configure the phone, the QPST tells Serious error encountered, write to phone aborted.
I've installed CM10.2 two weeks ago and everything is working great! The first time I flashed it I got stuck at the CM boot animation... After ten minutes spent watching it I forced it to reboot: stuck again. At this point I booted back to recovery, followed thoroughly netizenmt instructions (wipe three times, really!!!), installed CM10.2, Installed gapps, installed supersu v1.43 and so on (follow all the steps netizenmt told us!)... Everithing worked fine then. At this point I changed build.props to make the phone works in GSM mode.
fargles said:
everything I've run into *works*
but it all doesn't work so smoothly
Scrolling and everything is kind of choppy, I mean it is definitely livable, but still choppy.
Click to expand...
Click to collapse
If you go to settings/developer options and scroll down to HW overlays. Check the box to disable HW overlays. That should help with the tearing/chopping.
Also, maps FC all over the place as soon as you're using GPS.
Sent from my XT907 using xda app-developers app
Having root now, is it possible to remove/change/delete the verizon boot logo? Its bright and overall annoying. Plus, any less VZW branding on my phone the better.
Or is that something that will require a custom recovery?
Xposed Framework -> Xblast Tools module -> Build.prop Tweaks section
i wouldnt attempt anything until i could make a nandroid
oneandroidnut said:
i wouldnt attempt anything until i could make a nandroid
Click to expand...
Click to collapse
Ya, this is holding me back from removing "custom" in the phone and the unlock screen on startup as well.
I don't really like messing with things that deep without a backup.
jsk23 said:
Ya, this is holding me back from removing "custom" in the phone and the unlock screen on startup as well.
I don't really like messing with things that deep without a backup.
Click to expand...
Click to collapse
i agree i messed with and somehow got all apps in mw using xposed but that was deep enough for me right now!
I changed my custom to official with no issues ....using wanam
Sent from my SM-N900V using xda app-developers app
oneandroidnut said:
i agree i messed with and somehow got all apps in mw using xposed but that was deep enough for me right now!
Click to expand...
Click to collapse
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Lightyear25 said:
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Click to expand...
Click to collapse
I don't want to risk anything lol
Sent from my SM-N900V using Tapatalk now Free
blap017 said:
I changed my custom to official with no issues ....using wanam
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I don't see this anywhere in Wanam.
Lightyear25 said:
I was able to used Xposed Framework to get rid of the Custom Logo just fine. Try it, I dont think you will have any issues (Although it did take me a few tries to get it to work)
:good:
Click to expand...
Click to collapse
Details please.
The officiate status change is under security hacks. .. fake system status.
Sent from my GlaDos Baked Potato
Edit. The lock symbol showed at boot up the first reboot. But never after. Done a few today.
Legato Bluesummers said:
The officiate status change is under security hacks. .. fake system status.
Sent from my GlaDos Baked Potato
Edit. The lock symbol showed at boot up the first reboot. But never after. Done a few today.
Click to expand...
Click to collapse
I was looking for a way to remove the VZW boot animation, thanks though.
Easy guide for getting rid of the CUSTOM logo and symbol at boot.
First, you have to install Xposed Framework, this is just an APK that you download from http://forum.xda-developers.com/showthread.php?t=1574401
Once you install the APK, simply head to the Google Play store and download the Wanam Module at https://play.google.com/store/apps/details?id=ma.wanam.xposed&hl=en
Once Wanam is installed, go into Xposed, and put a check on the module "Wanam" then go into Wanam and then go Security Hacks - Fake System Status.
Note: It took me rebooting a few times and toggling it on and off to get it to work, but was worth it, that logo was U G L Y.
Lightyear25 said:
Easy guide for getting rid of the CUSTOM logo and symbol at boot.
First, you have to install Xposed Framework, this is just an APK that you download from http://forum.xda-developers.com/showthread.php?t=1574401
Once you install the APK, simply head to the Google Play store and download the Wanam Module at https://play.google.com/store/apps/details?id=ma.wanam.xposed&hl=en
Once Wanam is installed, go into Xposed, and put a check on the module "Wanam" then go into Wanam and then go Security Hacks - Fake System Status.
Note: It took me rebooting a few times and toggling it on and off to get it to work, but was worth it, that logo was U G L Y.
Click to expand...
Click to collapse
Not being able to make a backup still bothers me. But this Verizon logo and the unlock boot screen are starting to annoy me. Has anyone who has modified either of these had any issues or complications yet? That may reassure me a bit.
No issues that I've seen. Did it 6 am this morning. Haven't had a problem all day. Done a few more reboots when I tweaked more stuff. Still running great.
Sent from my GlaDos Baked Potato
Guys why don't you just apply the boot animation manually? Here is how:
1. Download your boot animation and extract it if it's 7zipped up, you will have 2 files in .qmg file format
2. Use a root browser on your phone to navigate to /system/media
3. Rename bootsamsung.qmg to .bak and also bootsamsungloop.qmg to .bak(so you can revert rather than just deleting them)
4. Ensure that your custom boot animation is named bootsamsung.qmg and bootsamsungloop.qmg and copy them to /system/media
5. Reboot and it should work!
Very good
Hi all. Tried searching for this for a long time now with no luck. Can you imagine how many posts there are with those words in them? Ugh!!
First of all, random reboots. My s4 will reboot as stated...randomly. No rhyme or reason to it. It can just be laying there idle and out of nowhere...REBOOT. I'm on 4.3 mk2 if that helps.
Now the soft reboot. Or hot boot as I've also seen it called. Specifically related to xposed and associated modules. Or in my case, ALL modules. If I do a soft reboot everything runs perfectly. No problem at all. But a full reboot? Nothing xposed related runs. Not framework or modules. Of course the framework has to run for the modules to work. Is this normal? Does xposed only run after a soft reboot? From my searches on the net I'm inclined to say no. But I don't know for sure.
So there you go. Thanks for any help you can give me.
Soft reboot is no longer an issue. But the randoms are. Any ideas or help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
LWH.31752 said:
Soft reboot is no longer an issue. But the randoms are. Any ideas or help would be appreciated.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Xposed is always running. Are you just rooted or on a custom SafeStrap rom. Has it done this before Xposed, or when did it start? Before/After rooting.
I would:
1. Uninstall/Delete Xposed and all Modules and see what happens. Do reboot clearing all caches if your recovery supports that.
2. Reinstall Xposed fresh thru the apk, and add one Module at a time. Wait and see for a day or two on that one Module.
3. On mk2 you can't change kernels anyway. AFAIK, since new things keep coming out with SafeStrap etc. And I don't keep up.
4. Could always be Hardware--
5. Could Odin back to stock and start over. BackUp Cards first. Or even try reformatting cards.
Just throwing out options--:good:
Hope you get it sorted--
Thanks for the info rugmankc!! A good bunch of suggestions for me to try. To answer your questions, My phone is rooted stock with safestrap. No custom rom. I rooted my phone within days of having it so no way for me to remember if it randomly rebooted before root. Same with xposed. Can't remember when I put it on there to know if it did it before. But my issues with xposed modules and soft booting have been solved. It's just the random reboots giving me a headache. But I'll give your ideas a go and see what happens.
LWH.31752 said:
Thanks for the info rugmankc!! A good bunch of suggestions for me to try. To answer your questions, My phone is rooted stock with safestrap. No custom rom. I rooted my phone within days of having it so no way for me to remember if it randomly rebooted before root. Same with xposed. Can't remember when I put it on there to know if it did it before. But my issues with xposed modules and soft booting have been solved. It's just the random reboots giving me a headache. But I'll give your ideas a go and see what happens.
Click to expand...
Click to collapse
Good Luck--
I have a Verizon Galaxy S5. I've always been afraid to root, but I hate TouchWiz and bloatware so much that I had to try. I'm regretting it.
I just used towelroot and tried to install SuperSU, Titanium Backup, and Wanam Xposed. I tried to research as much as I could, but it's still all new to me.
I first tried to install SuperSU. I wasn't totally sure what to do when it said "Try to disable KNOX? - Cancel or OK".
Someone suggested that I tap OK and disable KNOX. The screen has said "Disabling KNOX..." with a spinning circle thing for at least 5 minutes now. After 10+ minutes of waiting, I closed SuperSU. I downloaded Superuser to try it instead (per someone's suggestion). I tapped it and it immediately opened. It didn't ask about installing or anything. I thought it would need to replace the su binary. It feels like I have a messed up mix of half-installed root software.
Now I just want to undo all this and go back to an unrooted phone. Can anyone help me do that?
Odin back to stock
Sent from my SM-G900V using Tapatalk
ergalthema said:
I have a Verizon Galaxy S5. I've always been afraid to root, but I hate TouchWiz and bloatware so much that I had to try. I'm regretting it.
I just used towelroot and tried to install SuperSU, Titanium Backup, and Wanam Xposed. I tried to research as much as I could, but it's still all new to me.
I first tried to install SuperSU. I wasn't totally sure what to do when it said "Try to disable KNOX? - Cancel or OK".
Someone suggested that I tap OK and disable KNOX. The screen has said "Disabling KNOX..." with a spinning circle thing for at least 5 minutes now. After 10+ minutes of waiting, I closed SuperSU. I downloaded Superuser to try it instead (per someone's suggestion). I tapped it and it immediately opened. It didn't ask about installing or anything. I thought it would need to replace the su binary. It feels like I have a messed up mix of half-installed root software.
Now I just want to undo all this and go back to an unrooted phone. Can anyone help me do that?
Click to expand...
Click to collapse
You can Odin back to stock as mentioned, instructions here http://forum.xda-developers.com/showthread.php?t=2784880 - That is something I ran into also, if you just reboot and reopen the SuperSU app it will ask again to disable KNOX and it takes seconds to complete. I'd try that first, unistall the other SU app you tried. You can also unroot using SuperSU once its installed right.
Before Wanam you did install the Xposed framework I'm sure right?
You just need to reboot. It did the same thing to me. Like Floyd says it takes like a second to complete after that.
PappaFloyd said:
That is something I ran into also, if you just reboot and reopen the SuperSU app it will ask again to disable KNOX and it takes seconds to complete. I'd try that first, unistall the other SU app you tried.
Click to expand...
Click to collapse
I eventually opened SuperSU again and it recognized the other superuser. It asked if I wanted to uninstall the other superuser, so I did. At least I'm down to only SuperSU now, and it seems to be doing what it's supposed to.
I'm still trying to figure out whether I can even use a custom recovery on my Verizon S5 at all. I don't want to do that until it is known to be pretty stable. So, would I even want to disable KNOX?
PappaFloyd said:
Before Wanam you did install the Xposed framework I'm sure right?
Click to expand...
Click to collapse
I haven't opened Wanam Xposed. I'm not sure what the Xposed framework is. Is there a set of step-by-step instructions anywhere? It's really disappointing how difficult it has been for me to find solid info. I'm not trying to do anything crazy, I just want to disable as much TouchWiz and bloat as possible.
ergalthema said:
I eventually opened SuperSU again and it recognized the other superuser. It asked if I wanted to uninstall the other superuser, so I did. At least I'm down to only SuperSU now, and it seems to be doing what it's supposed to.
I'm still trying to figure out whether I can even use a custom recovery on my Verizon S5 at all. I don't want to do that until it is known to be pretty stable. So, would I even want to disable KNOX?
I haven't opened Wanam Xposed. I'm not sure what the Xposed framework is. Is there a set of step-by-step instructions anywhere? It's really disappointing how difficult it has been for me to find solid info. I'm not trying to do anything crazy, I just want to disable as much TouchWiz and bloat as possible.
Click to expand...
Click to collapse
My best advice for you is to watch videos on YouTube on how to use xsposed installer and also how to use the Titanium backup app to freeze apps you don't want. It would take a long time for someone to post a step by step. All info can be watched on YouTube then if you have questions go ahead and ask.
Sent from my SM-G900V using Tapatalk
Savagerun said:
All info can be watched on YouTube then if you have questions go ahead and ask.
Click to expand...
Click to collapse
I watched a few YouTube videos. At this link, the first step is to create a nandroid backup. When I looked up nandroid, it says it needs a custom ROM in order to restore the backup. I thought the point of Xposed was to not need a custom ROM?
ergalthema said:
I watched a few YouTube videos. At this link, the first step is to create a nandroid backup. When I looked up nandroid, it says it needs a custom ROM in order to restore the backup. I thought the point of Xposed was to not need a custom ROM?
Click to expand...
Click to collapse
Have you watched the following video? It explains how to use SS and also how to make a nandroid backup of your rooted stock rom. Watch "Verizon Galaxy S5 Safe Strap Recovery Install and Overview" on YouTube
http://www.youtube.com/watch?v=5d-cPtK-CR8&feature=youtube_gdata_player
Sent from my SM-G900V using Tapatalk
Savagerun said:
Have you watched the following video? It explains how to use SS and also how to make a nandroid backup of your rooted stock rom. Watch "Verizon Galaxy S5 Safe Strap Recovery Install and Overview" on YouTube
http://www.youtube.com/watch?v=5d-cPtK-CR8&feature=youtube_gdata_player
Click to expand...
Click to collapse
That was a good video. I didn't hear him mention "nandroid". I am guessing that by using a new slot and not touching the stock rom slot anymore, that the stock rom slot is considered a nandroid backup, or at least the equivalent.
how can i fix this?
i think the xposed modules messed up my rom and now ive lost my root because i updated my firmware to XXUGNG4,
my counters are still 0x0,
but my device status says its custom even though im on stock odexed rom,
is it possible to fix this w/o odin?
because i dont have a p.c,
and if flash a fresh stock rom will my device status change to official?
and what are the chances of triping my counters?
wipe data/cache in the stock recovery.
wanam xposed also has the option to fake your status to "official", dont know whether it works though.
Lennyz1988 said:
wipe data/cache in the stock recovery.
Click to expand...
Click to collapse
i tried that but sadly it still says custom and eventhough i uninstaled the modules the mods still sticks with the apps,
like the exit button on the browser and the silent shutter sound of the cam,
eprov said:
wanam xposed also has the option to fake your status to "official", dont know whether it works though.
Click to expand...
Click to collapse
yes it does have that option but i lost my root bcoz i updated my os,
switchblade00 said:
i tried that but sadly it still says custom and eventhough i uninstaled the modules the mods still sticks with the apps,
like the exit button on the browser and the silent shutter sound of the cam,
Click to expand...
Click to collapse
Factory reset and anything wont work to make it official. If that would have been the method, why was triangle away introduced. :/
Nothing will hapoen till you get your root access.
Obtain root access, try wanam, because triangle away does not work for i9500.
Can try reflashing the stock rom, it might be of little use though.
Till you get yourself root, nothing good can happen...
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Factory reset and anything wont work to make it official. If that would have been the method, why was triangle away introduced. :/
Nothing will hapoen till you get your root access.
Obtain root access, try wanam, because triangle away does not work for i9500.
Can try reflashing the stock rom, it might be of little use though.
Till you get yourself root, nothing good can happen...
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Finally i found the way to fix it...
Flashed a fresh stock rom using odin...
Cool
Thank me if I helped
Sent from my Samsung Galaxy S4 via XDA app.