Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.
Brutal-Force said:
Actually, Towelroot may not be related, but oddly enough my phone did a couple of app updates and then Tmobile could tell my phone was rooted. Then it started acting really weird. I got a green LED notification but had none in any apps. The stock keyboard gets really laggy. (1 press per 4 seconds), if you try to long press to move a widget/button or anything, the phone hangs up.
I am almost convinced it is something Tmo is doing. The phone shows in Tmo My Accounts that the phone is rooted.
I tried to unroot (SuperUser is a no-go), I tried downgrading using downgrade methods but I get an error and it shuts down. I don't know where to start now. My phone will be kicked back from Tmo if I try to send it in. I knew one day Root Exploits would catch up with me.
If anyone has a bright idea other than wait till there is a fix, I am all ears.
Click to expand...
Click to collapse
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer
D-FUSE said:
Has nothing to do with rooting your phone. I wasn't rooted for 2 months and it was doing that switch to the g3 keyboard in the g2 thread use the apk installer
Click to expand...
Click to collapse
The new android L keyboard in the playstore is really smooth too. No lag, good feel, has emojis if that matters to you. There's a thread in the apps section for the 5.0 keyboard you can manually install and it'll have more skins but the easiest way is to install from the playstore.
Edit: T-mobile keeps track of rooting somehow? How have I never heard that!? Seems like something a Dev or someone would have figured out how to block or what app they're using to spy. That sucks especially in regards to warranty etcetera being denied.
Its not just the Keyboard. I too switched the thumb keyboard which resolves the lagging key-input, but there is also a blinking green led notification that won't go out and I can't answer the phone because touch input (drags and long presses) are buggered.
I have installed TWRP, gonna Try to install a rom and fix it
Related
Hey guys I was wondering what I can do to unroot my droid 3 and also revert it back to completely stock. I had frozen and removed some apps due to this being my first time using titanium back up and I'm wondering what I can do to do this. The reason I want to do this is so that I can go back to verizon and get a replacement phone because mine has just been messing up too much. I removed or froze all the apps that were safe to remove but it'll keep pressing space or backspace, it will stop with its service and not send calls or receive texts, it will have half a green screen when I push back and it's all just really annoying.
So please if anyone has any suggestions please tell me. I've tried to restore from titanium back up but it ends up just "clocking" when I try to restore sometimes. Also I dunno how to unroot.
here
i did the same thing... lol check out this link
http://rootzwiki.com/showthread.php?5103-SBF-Droid-3-Fastboot-files-(5.5.959-and-5.6.890)
good luck its easy
More power to you but from my experience I bought the d3 when it came out 2 days later I got the same problems green blobs when it redraws screen, space and backspace buttons sticking so I called verizon they sent me a new one, this was about 15 days ago guess what's back to affecting my phone?
I know that there have been reports of the green screen thing from people that use youtube a lot. But out of curiosity, have you flashed any of the ota's? Because I noticed the same thing until I went to 5.6.890
Sent from my STEELdroid3
I haven't done anything more then remove / freeze some apps. I was thinking of trying to use the steel droid and I wasn't sure what the difference was from using 5.6.890. I'm still pretty new to all this so I was worried about what to do. Ill read up on how to do it today and possibly try upgrading to 5.6.890 and changing to steel droid.
I haven't yet installed the ota but my first glitches happened when I was unrooted completely stock and now their back and im rooted with bloat gone.................................................... < just spammed the period button damn phone
First of all running stock Droid 3 Rooted Flashed to cricket
with all the fixin's, Bootstrap, CMW, ... etc....
:edit ... Now with safestrap.
_________________________________________
I noticed after taking my phone out of my pocket while trying to turn it on from normal off screen while on that it wouldn't show up the light still indicated it was working I can even turn off the phone.
Taking the battery out and back in semi fixed this but only to the extent where when the phone is turned on the moto logo doesn't appear but the droid eye does.
whence at the booted screen if I were to let it go black it has a chance to not stay on unless I RIGHT after it boots unlock it and keep it lit,
(but)
the main problem I noticed was it really only did this after lets say I was typing or doing anything with the qwerty board open and perhaps I let the screen turn off after a minute,
when I try to wake it up it stays black. EVERY TIME like most of the time,
it has to do with the keyboard being open when the screen goes to sleep.
WHAT IS WRONG *pulls hair out*
_________________________________
I can't say when but I've looked everywhere
tried uninstalling every app but the essentials,
then restoring to my first restore which was after my first initial root.
Tried factory reset,
Tried flashing back to stock,
yeah I think this counts for as much as I've gone insane looking for an answer for.
I have been told this sounded like a software issue so all I'd need to do is re install like I did when flashing back to stock THIS MORNING.
____________________________________________________
I need help to identify somehow if this IS or IS NOT a software/hardware problem.
and an answer to help me fix this would be nice as well thank you.
I know I am supposed to be brief but putting in all that into google and into every forum I have delved just isn't going to put it the way it needs to be said.
______________________________________________________
______________________________________________________
Edit:
Ok so far since no one has said anything I have also reinstalled my old newest state, still giving me crap.
Then just did the newest update 5.7 blah and still it's happening.
I hypothesize it might be the flex ribbon cable maybe (but it really might not) I read from another phone it might be a capacitor but it might not.
Whatever is wrong the phone still is able to at times now 40/60% of the time work properly and wake normal but then again not.
__________________________________________
Right as of now I have put isc to see if this helps .......... .... to be continued or helped.
I'm back, well ics installed fine after the second time made it boot loop over and over.
-----------------------------------------------------------------------
I can receive calls now
but
no sms, mms, or internet.
(even though the network status settings are blank it's weird I can still receive calls, and send calls.)
since you can't restore the apn's with 3rd party I now have this NEW issue.
the phone goes unresponsive within cdma workshop and ##Program does not work.
I'd like some help in finding out now how to if it is possible yet to properly flash to cricket and or just change my apns and get into cdma as well as QPST.
__________________________________________
PLEASE I NEED HELP thank you
-3nJo1
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Thanks
necromanteion said:
Yeah, it does sound like a hardware problem. If nobody else can help you fix it, you'll need to reflash the latest OTA update (or revert to your safestrap nandroid), unroot it and restore all the system apps that you may have frozen/deleted, and hope that Verizon will replace it.
Click to expand...
Click to collapse
Thanks for your input.
(verizon wouldn't replace it since I baught it from someone else (legit) and I don't have verizon.
UNLESS you think if I had the previous owner take it into the store could they replace it? what steps would they take to see if it was rooted?
_______________________
I never unrooted it when I did allll of this
Do you think rerooting is soumething that I should have done before doing this?
Or most likely is this a flex ribbon cable thing ....
I just tried the diagnostic (leave keyboard open then turn the screen off and on thing)
it came on at least 3 times normal then it didn't either right after the 3rd try or upon closing the qwerty board ...
also do you have an answer at all for the ics portion of my problem?
THANK YOU
___________________________________________________________
EDIT!!!!!!!! Actually realized I did reroot after the sbf ota flash .....
so all things aside yehs I also did that any other solutions inquiries ...
ANYONE ELSE PLEASE HELP!
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
stud beefpile said:
Another path to try down is Motorola - depending on the age of the phone, I believe there's a warranty through them.
Click to expand...
Click to collapse
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
I bought my d3 off craigslist and the power button and n key weren't always working. I took it in to Verizon and had a new one in the mail 3 days later!
Sent from my XT862 using XDA App
Sorry didn't read the part about you being on cricket. Maybe you could make friends with someone that has d3 on verizon have them activate it and take it in for you.
3nJo1 said:
Thanks,
well it is less than a year old I think, could I be able to get motorola to replace it when all I have is the phone no receipt or box ???
MORE HELP FROM ANYONE ELSE PLEASE
Click to expand...
Click to collapse
I believe there is another apn type tool that the Cricket Android tools are using for their specific settings. You may have to search XDA a bit to see if anything shows up for othere phones on Cricket.
Sent from my DROID3 using XDA App
I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
EvilTelephone said:
I can't figure out what's causing it. I don't have very many apps installed that didn't come with the phone, and any I did install were from the Play Store. I haven't done any modifications such as root to the device.
In order to bring it back to life, I have to either hold the power button down for 30 seconds to shut it down (or take out the battery) and power it back on.
Interestingly, if I have notifications waiting and the LED is flashing, that continues to flash even if the phone won't wake up.
I did 'disable' several of the bloatware apps in the app management area in Settings. I'm starting to think that must be what's causing it. Is there a particular bloatware app that should never be disabled? One that would cause this issue?
Other apps I've installed are things like Netflix, eBay, the app for my bank, and a TV-listings app. Pretty basic stuff. I don't think any of those would be the problem, would they?
Remaining battery doesn't appear to have an effect. It's happened with full battery and somewhat low battery.
'Services' that I use are Exchange push email and Gmail. I also have it Bluetooth synched to my car's hands-free thing.
Any help would be appreciated. Taking my phone out of my pocket to use it just to find that it's not responsive is very troublesome.
Thanks.
EDIT: For clarification, this is an AT&T version of the S4A.
Click to expand...
Click to collapse
maybe u can enable back all the apps that u have disabled and see if it happens anymore.
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
cfchong said:
u mentioned "the phone won't wake up" and "not responsive". do u mean that the screen stayed off and u are unable to get the screen to be on?
Click to expand...
Click to collapse
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
The advice you've got is sound - if you think it might be because of disabled apps, re-enable them all and see if it keeps happening. If it doesn't... well then you disable them one at a time until it starts happening again.
Then you come back to the forum again and let everyone know which app never to disable.
If it doesn't stop happening after re-enabling all the apps... well then my guess would be a faulty device. Can't think of any other logical reason for it to behave like that. So try the apps first, if that doesn't help, "return to sender".
EvilTelephone said:
That's right. None of the buttons wake the phone up or turn on the screen. I can tell the phone is still 'on' though. It's not like it got powered off in my pocket.
Click to expand...
Click to collapse
if enabling back all system apps do not resolve the problem, try disabling all user apps to test. one of your downloaded app may be the cause.
Alright, over the past month I've done a bunch of testing. Here are my results.
1. Re-enabling all the system apps didn't help.
2. I uninstalled all my user apps. Didn't help.
3. I completely reset the phone to stock settings and formatted all storage. That didn't help.
4. I figured maybe it was something with bluetooth since it seemed to happen after I used bluetooth devices. I disabled bluetooth completely. It didn't help.
I'm out of ideas for the moment. Could the phone just be bad? I would wonder why the issue only happens occasionally.
Thanks.
Start a chat with Samsung. They have always been good to me.
GT-i9295(i537) running SafeStrap
I have the same problem, is there any solution, thanks
ogbeate said:
I have the same problem, is there any solution, thanks
Click to expand...
Click to collapse
Solved, rom change and ready, do not turn off more
I have the same problem in i9500. I now live in China and have purchased an s2, s3 and now the s4 from China Unicom. I have successfully rooted and flashed new ROMS (latest HK stock firmware) on the S2 and S3. When I bought the s4, it worked fine. I immediately flashed the latest stock HK ROM using Odin 3.07, After flashing, the phone is unresponsive after going into deep sleep meaning that nothing happens when I press the power button. After a long press of the power button, the phone will re-boot. Sometimes I have to pull the battery. Again, this phone is totally stock. I haven't added any applications. I re-flashed the stock China Unicom formware and I took the phone to the Samsung Service facility and they did a new flash. Phone worked great. I take it home, flash the HK ROM with Odin...same results; phone is unresponsive after going into deep sleep. I return to the Samsung service store and they again flash the phone. Phone works fine. What are they doing that I'm not doing? Could the partition table get corrupted during my flash processes. Should I try another version of Odin? Should I try a PIT file and try that? I'm downloading the ROM's from SamMobile. Thanks in advance for any suggestions.
Edit: I fixed this problem by upgrading to 4.3 which brought it's own set of problems.
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
You think the motherboard maybe fried or memory chip
I wouldn't worry about it. Rooting it won't cause a hardware failure.
Woudn't worry to much about it
rexamillion59 said:
Had my note 3 about two months now. Running stock firmware.
I did root it with towel root . with no problems. I stated noticing my phone
rebooting out of nowhere. And pictures sometimes disappearing from camera roll and gallery. Where the pic should be was a blank space. I figured I had a hardware issue.
And was going to exchange it soon. But not soon enough. It went black and i have not got it to boot again. No lights come on when connected to charger or pc.sounds like
sudden death syndrome. I called att and they sent me a new phone.
my question is can I wipe it somehow before I send it back. Or will they even be able to tell it was rooted. I know knox was never triped..
thanks for any advice
Click to expand...
Click to collapse
My ex gf had 2 phones do this to her and she never ran them on anything but stock.
thank you for your replys
att sent me a new phone no problem,coming from note 2 and on my 2nd note 3.iv noticed these phones have issues
wheather its the phone or just kit kat,my new phone also looses photos here and there and the back button dident work
a couple times.and the the other day i tryed to make a call and no sound tryed three calls no sound rebooted and worked perfectly i havent yet rooted this one
So i've been experiencing this issue for months now. I've had the issue since i've gotten the phone but its the past few months that its really gotten bad. So before anyone jumps the gun, i've done quite a bit of research on this and cannot find anything worthwhile, more on that soon.
So as usual, i'll pickup my phone and press the power button or the home button to turn on the screen, but at completely random times the screen will not come on at all. Sometimes the capacitive buttons will light up (maybe 15-20% of the time), but not always.
In my searches I found the following solutions to this problem:
Get a new sim card
Dont use an SD card
Get a new battery
Check the leads on the battery and phone for cleanliness
Factory reset
Remove 1 app at a time and test until it stops happening
Dont freeze any apps
Restore stock firmware
Dont use SetCPU
Turn off animations
Get rid of the lock screen
Remove custom message from lock screen
Clear cache through Recovery
Dont restore data with Titanium Backup when restoring apps
Turn off WiFi and/or Bluetooth and/or GPS
Dont use GreenPower or Greenify
Avoid stock launcher
I have tried all of the above except for removing 1 app at a time (and those that dont apply). I'm deep into that one and only have a few apps left to try. This is something that happens at least once a day, but typically 3-5 times in a day. I used to think i could make it happen by pressing the power button to turn on the screen and immediately hit it again to turn it off. It would sometimes work but that doesnt trigger it anymore.
My phone used to be rooted, but being on AT&T there was no "normal" way to flash a good recovery like CWM or TWRP and install roms, you have to use some other thing which i dont use. So i've always had stock recovery, im fully updated to the newest stock rom that is out, update came OTA which was after i removed root and used odin to flash an older stock rom back. My wife's Note 3 also has the same issue and it has never been rooted, we have gone through all of the above and still it continues to happen.
Also on a side note, my phone was swapped out because of an issue it had 3 months after i purchased the phone. I was able to get a brand new one, not refurbished. The issue had occured once or twice before the swap and an incredibly frustrating amount of times since then.
Reading through most of the other threads, everyone seems to have to remove their battery and re-insert it to get back into their phone. The ones that dont have to do that have found that removing their SD Card, getting a new one, sending the phone in, or one of the other options have worked. However for me, nothing has worked.
Does anyone have any other ideas? Is this common on the Note 3 (I've had it since release)? 70% of the time i can hold the power button for a few seconds to try and bring up the power menu and it works, but not always.. I usually just have to wait up to a minute or two (never actually counted, i use my phone for that stuff...which.. isnt..working...)
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
wudien said:
I've had wake lock lag on a few android phones. Even iPhones.
I would highly recommend rooting it on att and flash a mod that reduces it on the note 3. I talked about it here.
http://forum.xda-developers.com/showthread.php?t=2628716
Rebooting the phone always helps.
Click to expand...
Click to collapse
Unfortunately I cannot root my phone. I have to have my company email on my phone, and for Android devices they use Air Watch. I tried for weeks to get it working while rooted, and even used Root Cloak or something like that (with Wanam Xposed) to hide root from specific apps. Air Watch was specifically tested to work with that app but it still for some reason didn't work (new version of Air Watch perhaps with no update to Root Cloak? Just my guess). I had to remove root, factory reset and re-flash stock from Odin (that was a dual purpose flash) to remove all traces of Root so I could use Air Watch for my company email/calendar/contacts/etc again, even after unrooting and using all the cleanup tools, triangle away, and everything, it still detected my phone as rooted...
However, I don't think that's really a viable solution to the problem, that's more of a band aid. Looking at that thread and looking around, it seems to work well but I still haven't found anyone with my same issue where they used it and it worked. I would like to narrow this down to what the issue is exactly, the root cause. I think its a problem with KitKat, or at least all of 4.4.x (not sure about 4.4.4 yet).