I remember the day when towelroot came out, there were a few threads claiming the Ultra Power Saving mode causes your phone to never boot up or never getting past the samsung logo..... I rooted my AT&T version the same day towelroot came out, is it safe to use this mode or did those people do something wrong?
All I have installed is greenify and xposed wanam, the rest is just regular apps
And last question, I don't have titanium back up premium but I do have app freezer, I froze S health but it still keeps giving me a pop up that it crashed
How do I get rid of S health? maybe just add .bak to it?
I tried ultra power save just to see if it worked, it did just fine. I'm rooted with towel root
Sent from my SM-G900T using Tapatalk
I remember that thread, the person rooted and froze the Touchwiz launcher which broke Ultra Power Saving Mode and hung the phone, causing the phone to not boot to the home screen if restarted.
Sent from my SM-G900F using Tapatalk
Related
Any ideas to make Wanam work again?
Sent from my SM-N900V using XDA Premium 4 mobile app
Are you running Wanam to dissable staus on "stock" rom? (Not on the rom within the ss rom slot)
Sent from my SM-N900V using Tapatalk
Yes I am running Wanam to disable the status on a stock rom.
Sent from my SM-N900V using XDA Premium 4 mobile app
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
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
Did everything you said must have rebooted my phone 20 times and I still have the custom icon driving me crazy.
Sent from my SM-N900V using XDA Premium 4 mobile app
What sucks is you know wanam is working because at least for me the notification mods were working like NFC icon removed and clock and stuff.. just the status wasnt sticking... took me forever but it did take eventually
I've done it like 30 times no luck. I think I'm just going to let it be.
sent from my ROOT powerd Note3
This is not a troll question...
I've seen lots of folks worried about the "open lock" icon on boot. Why does this matter, unless you are requesting service/replacement of your device?
Is this a separate indicator from the Knox "0x0" that shows in download mode?
Galaxy Note 3 (VZW) / Nexus 7
SoCalNewb said:
This is not a troll question...
I've seen lots of folks worried about the "open lock" icon on boot. Why does this matter, unless you are requesting service/replacement of your device?
Is this a separate indicator from the Knox "0x0" that shows in download mode?
Galaxy Note 3 (VZW) / Nexus 7
Click to expand...
Click to collapse
Exactly what you said, for warranty and also just OCD for some of us yes its seperate it shows in the Settings>Status screen as well as the boot screen instead of Official it will say "Custom" (Wanam removes the icon and sets the status to Official)
You don't have to uninstall.... just re-install the framework and it should be back up.
Sent from my SM-N900V using Tapatalk
I got my new S5 (SM-G900W8, Telus) and I rooted using Towel Root. I installed a bunch of root apps, including Titanium Backup. I then proceeded to remove apps (backing them up first). I removed TouchWiz (backing it up) and used Nova. A few days later, I decided to activate UPSM (Ultra Power Saving Mode), and found that my entire screen went black, I could only drop down the notification bar, I had no apps, no ability to deactivate it.
I googled and found no way to force UPSM to turn off. I tried charging to full, no. I eventually restarted, and my phone got stuck on the "Samsung" logo, in black and white. I everything I could think, and then just decided to factory reset. I re-installed all my apps, and stuff, and just remembered that I didn't backup Titanium Backup, so I couldn't re-install TouchWiz.
What do I do now? I'd like to use UPSM, but I would prefer to not soft-brick it, and have to factory reset it after everytime I use it. I know I'm n00b, and it was my first rooted phone, and I should have researched first, but oh well.
Is there anything I can do to get TouchWiz back without tripping the KNOX counter (i.e. reflashing my phone to get it back)?
Once rooted I don't think you can use UPSM. You could install a TouchWiz based ROM with safestrap and probably get similar functionality, but I don't believe ultra power saving mode is available after rooting.
Find a rom for your device and either flash that, take the apk out and put it in your system/priv-app, or find someone here to post it for you. It's called TouchWizHome.apk. Seeing as how you don't want to trip Knox you will need to put it back yourself using something like root explorer.
Actually. Look at this thread here http://forum.xda-developers.com/showthread.php?t=2732110. The second post has all the bloatware that was removed that I think you can add back.
I have the Note 4 (SM-N910H), I've had mine rooted for 2 weeks and it kept randomly rebooting twice or so every 1-2 days, now I've removed the root and everything seems to be working fine with no reboots for 1 week. Most (I even think all of them) of the random reboots happened while the phone was idle (screen off).
I've rooted using the CF-Auto-Root via odin.
Anyone knows why the root was causing random reboots for me? I've tried with knox disabled and enabled and with both options I get the same reboots while the phone is idle, also I would like to mention that I don't have an SD card in my phone. I tried everything, Tried a recovery reset, tried a soft reset... It only happens when I root it.
Thanks.
Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium
It keeps rebooting mine so if i unroot it will solve the issue?
dr.ketan said:
Sometimes xposed module can be a culprit.
Sent from my SM-N910G using xda premium
Click to expand...
Click to collapse
Xposed sucks on a stock odex roms. I suggest you flash a new rom or deodex your stock rom.
the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!
TML1504 said:
the note4 i have atm was never rooted (efuse intact), but it also reboots randomly every few days, sometimes every few hours!
so i would say root is NOT the general cause!!
maybe, or perhaps root makes it worse, but it cant be the only reason!!
Click to expand...
Click to collapse
In my case it's the issue, I've had mine un-rooted for 3 weeks now with no any random reboot, I rooted it yesterday using CF auto root just to test and it rebooted today while it was idle. I've never used any Xposed modules. It's also on stock rom and stock recovery.
menko2 said:
It keeps rebooting mine so if i unroot it will solve the issue?
Click to expand...
Click to collapse
I think it's worth a try to unroot and see if the problem is solved for you.
Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..
menko2 said:
Thank you.
Do you know how to unroot?
The biggest problem is how to pass my apps and data without Titanium that needs root access..
Click to expand...
Click to collapse
Just flash the latest stock ROM from sam mobile (http://www.sammobile.com/firmwares/) for your exact model number and CSC using odin, no data or apps will be lost and root will be automatically removed after the process.
You can install "Phone INFO ★Samsung★" from play store to know what your exact model number and CSC, you can also type all the fields you get after you open it (except for your IMEI) and write them down here to me so I can give you a link of the stock ROM from sam mobile so you just download and flash via odin.
After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.
Planet X said:
After rooting open SuperSu and choose never for the question to also disable Knox. Until now I didn't have any unexpected reboot.
Click to expand...
Click to collapse
I mentioned in my original post that I tried with both, knox disabled and enabled but with both options I had the same random reboots, no matter what I do, the same problem for me as long as I am rooted. Did you have random reboots before while you are rooted and now you fixed it somehow?
Tmobile Note 4, rooted but with the stock ROM on it. Functions perfectly until a couple of days ago I get this odd stutter, the entire phone just freezes for a couple of seconds and I can't do anything, it does this every couple of minutes. I suspect an xposed module but I'm not sure. After freezing and uninstalling apps and even uninstalling xposed it still does it so I back everything up and do a factory reset from the settings menu.
Doing a factory reset from settings it just sits there saying it's powering down, it stays there forever and I cannot go back or close it, I can't even force power down with the power button. Only alternative is to pull the battery. The phone powers on normally, and all info is still there, so I can't factory reset this way.
Powering back up with vol up/power/home I can see the little android guy but this just flashes on and off forever so I cannot get into recovery to do a hard reset.
My last option is to reflash the stock ROM via Odin, but I'm at work now and was hoping to have a functional phone today. I'm not sure what went wrong, it's odd that I can't reset yet the phone functions perfectly apart from the stutter. I wonder if it's some kind of virus.
Crap I just realized if I can't get to download mode I can't flash via Odin. Anyone have any suggestions?
spinedoc said:
Crap I just realized if I can't get to download mode I can't flash via Odin. Anyone have any suggestions?
Click to expand...
Click to collapse
You need someone's help to insert battery, while inserting battery hold vol down plus home plus power, try.....
It is not a virus, xposed is the cause. I restored my nand I created when I first rooted, problem solved.
That odd stutter will eventually lead to a complete crash.
Sent from my SM-N910F
JagDave said:
It is not a virus, xposed is the cause. I restored my nand I created when I first rooted, problem solved.
That odd stutter will eventually lead to a complete crash.
Sent from my SM-N910F
Click to expand...
Click to collapse
Wow, do you know if it's a specific module or xposed itself? I did uninstall it but still got the stutter.
I was able to get into download mode, while keeping the buttons pressed I plugged in the usb cable and for some reason download mode worked. I flashed stock NK4 then rooted, dirty flash though. I reinstalled xposed and everything ran perfectly smooth for a couple of hours, then it started stuttering again. I think my next move is a full wipe and reinstall stock NK4.
So did you stop using xposed altogether?
Hmm, going to try this: http://gs5.wonderhowto.com/how-to/f...hes-when-using-xposed-your-galaxy-s5-0157344/
I also read here and there that Xblast was the culprit. Uninstalled and haven't seen the freezing yet this morning.
spinedoc said:
Wow, do you know if it's a specific module or xposed itself? I did uninstall it but still got the stutter.
I was able to get into download mode, while keeping the buttons pressed I plugged in the usb cable and for some reason download mode worked. I flashed stock NK4 then rooted, dirty flash though. I reinstalled xposed and everything ran perfectly smooth for a couple of hours, then it started stuttering again. I think my next move is a full wipe and reinstall stock NK4.
So did you stop using xposed altogether?
Click to expand...
Click to collapse
No more xposed for me. I tried evening suggest in other threads, but the lack of s-health or privacy mode along with the freezing problems far outweighed the benefits.
Sent from my SM-N910F
JagDave said:
No more xposed for me. I tried evening suggest in other threads, but the lack of s-health or privacy mode along with the freezing problems far outweighed the benefits.
Sent from my SM-N910F
Click to expand...
Click to collapse
Was the issue that Shealth wouldn't open? After reading your post I tried opening it, it won't open. No error message or anything, just nothing happens when I press the icon.
spinedoc said:
Hmm, going to try this: http://gs5.wonderhowto.com/how-to/f...hes-when-using-xposed-your-galaxy-s5-0157344/
I also read here and there that Xblast was the culprit. Uninstalled and haven't seen the freezing yet this morning.
Click to expand...
Click to collapse
That link seems to have done the trick. Running smoothly now with xposed installed and S-health opens up just fine.
The stutter for me tied in with s-health and health service, it can be blocked, but unless you do this first it'll cause issues, pull the battery, begin holding home and volume, then pop the battery in and then hold power, get into download mode and flash it
---------- Post added at 10:43 PM ---------- Previous post was at 10:41 PM ----------
I moved around a bunch of roms and none of them worked, the issue just wouldn't go away, so I downgraded, rooted, installed a rom, then xposed and then the module to allow s-health
I've had my Note 4 for a while and after a few Lollipop update incidents I finally after a lot of hesitation decided to root my phone (with the TWRP bootloader) and disable the update notifier. Since then, I've always stuck to the latest stock version of KitKat 4.4.4.
Since I've rooted my phone, I made the following modifications that require root priviliges: I installed XPrivacy mod, YouTube AdAway mod, NoSafeVolumeWarning mod, PlayPermissionsExposed mod, and CrappaLinks mod for the Xposed framework. I also installed Titanium backup to freeze/uninstall the updater and AdAway. After XPosed was installed I had to change a line in /system/build.prop to 'ro.securestorage.support=false' to make 'S Health' work again. I did that with the 'FX' app.
That's it, I had made no more modifications and the phone seemed to work quite well for a month or so.
Two days ago I decided to try out Instagram, I've been quite wary with social apps but figured Instagram shouldn't hurt and everything was fine. Then I installed a bunch of dating apps, I started with Match.com and Tinder. Tinder didn't work because it required FB and Match didn't work because it refused to, probably because of denied permissions with XPrivacy so I gave up on them and uninstalled them.
But I also installed OkCupid and Motesplatsen and enjoyed playing around with these apps. They didn't seem to interfere with XPrivacy and worked rather fine. Motesplatsen was rather intense with sending me notifications of girls who watched my profile and sent me (rather strange) messages whereas OkCupid was rather calm.
Then something strange happened.
Yesterday I started noticing that the battery was draining considerably faster than normal during normal day. It was almost empty whereas it usually is half full after a full day, I also noticed that the phone was unusually warm. I forgot to put it on the charger and woke up today with a dead phone. I put it on charge and after about an hour the battery was full again.
When I tried to turn on the phone it was stuck on boot loop. I first tried disabling XPosed by "touch /data/data/de.robv.android.xposed.installer/conf/disabled" using the 'terminal' tool in the TWRP bootloader. It didn't help. I tried flushing the cache/dalvik cache but it didn't work either. Then I did a total factory reset, but that didn't work. I noticed that during boot, the phone froze so hard that it doesn't even respond to button pushes. I had to take out the battery to reboot (that's one reason why I never will buy S6).
So then I decided to flash the phone with stock KitKat once again using Odin and that finally restored the phone.
Now, here's one of my questions, how can things go so bad with a phone that not even a factory reset will fix it? We're talking stock firmware here, albeit it is rooted.
What boot logs could be worth looking into when such a thing occurs and what is the easiest way to extract them? The terminal tool in the bootloader seems promising, plus I saw a 'copy log to SD' option which I neglected this time.
I'm puzzled, does anyone know what happened? I made no root modifications in the process of installing these apps and they don't advertise themselves as needing root privileges. How can a seemingly inconspicuous app directly from Google play **** a phone up like that?