Related
this has been going on for a few months now, when i try to shut the phone down completely it just reboots itself. the only way to get it to turn completely off is by pulling the battery and leaving it out. as soon as i put the battery back in the phone it autoboots up. at first i thought this was a CM7 issue but in the past 2 days ive tested leedroids rom, honeysenceHD, and a few others and the phone still acts the same. its never been an issue but i would love to be able to turn the phone completely off if i ever needed to. someone suggested that its possible my bootloader is corrupted. is there any way to fix this issue?
This is a problem with the Advanced Power Manger, search for the fix.
Sent from my Inspire 4G
ok well can someone point me in the direction to fix this problem.....search finds NOTHING for a fix
what apps do you have installed can you list them? They can sometimes cause problems...
Make sure "Fast boot" is UNchecked under Settings, Power.
i dont see a POWER sub menu in settings nor can i find Fast Boot.
apps are as follows
everything that comes stock with CM7
Battery Calibrator
Beautiful Widgets
COveroid
Dev Tools
DSPManager
FasterFix
Linpack
Quickboot- just to see if it would turn the phone off and it doesnt
setCPU but not using it currently
Spare Parts
thats about it a few of those apps i think are part of CM7 but im not sure
Look for fastboot in settings, applications.
Sent from my Desire HD using XDA Premium App
theres nothing in applications that allows me to turn on or off FASTBOOT
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Projectdwnshft said:
ok so i was told theres no FASTBOOT option in CM7 so anyone else out there have any clue as to why my phone will not turn off and stay turned off when i power it down?
Click to expand...
Click to collapse
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
It's a clockworkmod issue with daylight savings time. Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off.
"Change your date from automatic to a date before the time change (I just go to Jan) and your phone will shut off and stay off. "
i dont really understand what you mean by change it to a date/time before the time change. i turned off the auto time but dont see where your talking about with setting the date change
I wasn't going to try to help cause I didn't like yer tone. You could say please and thank you for peeps time..
http://forum.xda-developers.com/archive/index.php/t-1104835-p-2.html
Not sure if anyone has run into this yet, if so please share the fix. When selecting "power off" my Inspire 4G just reboots. I can no longer turn off my device. Thanks in advance for the help.
Download quick reboot from the market for now
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
I stopped reading. But a search is easy on the thread. Google is your friend....
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Projectdwnshft said:
big ups for the useless reply but thanks anyways....CHEERS
oh and there was no tone, but whatever mr internet coolguy THUMBSUP to you. i wouldnt have made this thread if i didnt already search to see if anyone else has had this problem, and it seems noone else has. when the phone was flashed back to stock the problem stopped and as soon as i re-rooted it the problem started again
Click to expand...
Click to collapse
I just linked a guy with the same issue .. Yes its on another rom, but its the same issue....
Download the app....does it work? Problem solved if it does? Or don't.. i could not care less, my phone works normally......
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Scott_S said:
Well at this point, if you think that continuing to try other roms other than what you've already flashed won't help, you might just try flashing a completely stock image, with the stock hboot/recovery, etc., and see if indeed something went haywire with your bootloader, as you mentioned someone had suggested to you.
Try the RUU in the stickied thread, for example. The recent OTA ROM by Attn1 has the hboot removed from it so I don't think that would be a good choice for this attempt, because you want to get the stock bootloader back.
Now, I can't speak to the validity of that suggestion about the possible corrupt bootloader... I don't know either way whether or not that could be the cause, but if you wanted to at least try it, then my suggestion above would be the way to do it, I would think.
There would be no reason for it to continue to behave like this on a completely stock ROM, other than there being something defective with the phone itself.
Click to expand...
Click to collapse
so yeah you had a good point scott. i went ahead and got the phone all back to stock and problem solved, but its not what i want sadly. so i re-rooted the phone and immediately after the re-root i went to turn it off and there it goes again turning itself back on =(
Projectdwnshft said:
it was a rom issue but guess u didnt read the thread to see that, that app is just another way to reboot your phone, i appreciate the effort but ive tried it many times and it boots/reboots the phone in the same manor the phone boots itself
Click to expand...
Click to collapse
So you have re-flashed to stock and the issue went away.
What rom are you flashing after root?
Did you check the MD5sum of the rom?
Have you tried a second rom?
Try just flashing to a stock rom like TCP;
http://forum.xda-developers.com/showthread.php?t=982963
Edit, just read yer above post... None this is going to help. Lol
i havent tried flashing anything, i flashed it back to stock, rebooted worked fine. So i decided to just reroot it. its stil STOCK atm just rooted. its obvious that its a software issue id just love to know what and how to fix it.
When you're flashing to a new rom are you clearing all of your data every time? If not you might want to give it a shot when you try to flash to another rom.
Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
J94w said:
Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
Click to expand...
Click to collapse
Are you rooted? If so what modifications have you done?
Have you uninstalled any of the stock bloatware, even if it was uninstallable without root? The update requires all bloatware to be installed.
J94w said:
Don't know what went wrong, but every time I try to update to 2.3.6 I get an error image and then it reboots. Done this 5 times and its driving me crazy
Click to expand...
Click to collapse
Seriously people, search before you post!! We have covered this at least 10 times!Anyways, If you have deleted any of the AT&T bloatware the update will fail. It is STRONGLY recommend that you flash the fkz's to get back to stock before you apply the update, especially if you have rooted and performed any mods. Just be sure to re-root and apply the 4ever root mod to keep root over the OTA.
Or just wait for lfaber to make something awesome with it!
Thanks, I just now stumbled on the other thread's also saying the same thing my bad. And also another question why is the bloatware so important?
J94w said:
Thanks, I just now stumbled on the other thread's also saying the same thing my bad. And also another question why is the bloatware so important?
Click to expand...
Click to collapse
It's not that it's important... it's that the update file is filled with a bunch of patches, some of which are for the bloatware, and so if the bloatware isn't there the patches don't install and the update won't begin (it checks everything at first.)
Oh ok thanks
It's not working for me too . I removed alot of the bloatware yes any solution beside restoring fxz ?
Sent from my MB865 using XDA App
alcatel444 said:
It's not working for me too . I removed alot of the bloatware yes any solution beside restoring fxz ?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
Sadly not...
you can just wait for custom ROMs to be based off of 2.3.6 and flash them... this update really isn't very major.
How can I tell if it's even trying to update. I manually started the update about 4 hours ago, but it doesn't look like anything is downloading. When I click on system update again, it says an update is currently being downloaded, but according to 3G watchdog, my wi-fi usage isn't changing. If I turn off wi-fi, it says the download will resume when wi-fi is back on, but the percentage is at 0%, and when I turn wi-fi back on, it stays at 0%.
If it's going to error out, does it not say something? I'm not getting any indication that it failed. Is there not a progress bar in notifications or anything? At first, I figured the server was just busy, but after 4 hours, something should have downloaded by now, right?
stedean said:
How can I tell if it's even trying to update. I manually started the update about 4 hours ago, but it doesn't look like anything is downloading. When I click on system update again, it says an update is currently being downloaded, but according to 3G watchdog, my wi-fi usage isn't changing. If I turn off wi-fi, it says the download will resume when wi-fi is back on, but the percentage is at 0%, and when I turn wi-fi back on, it stays at 0%.
If it's going to error out, does it not say something? I'm not getting any indication that it failed. Is there not a progress bar in notifications or anything? At first, I figured the server was just busy, but after 4 hours, something should have downloaded by now, right?
Click to expand...
Click to collapse
A reboot can't hurt.
Ok i had issues upgrading to 2.3.6 tonight.. I realized i had stupidly uninstalled YahooContacts.apk and FMRadioService.apk... As we know Titanium can't restore these. However what I did do was this:
open /cache/recover/last_log in a text viewer
scroll to the bottom, it will tell you what is causing the installer to fail.
Mine i could clearly see it couldn't find FMRadioService.apk I took the .gz file from the titanium backup directory, un-gzipped it, renamed the .apk to FMRadioService.apk and placed it in /system/app I then re-tried the update, it failed again, repeated with YahooContacts.apk
and viola... all was well..
-t
I tried that. The progress bar that was stuck at 0% went away after reboot, but it's still not downloading anything, as far as I can tell. That's why I was wondering if there is any kind of progress bar normally.
I'm thinking that, since I'm at work, our wi-fi is blocking it. I can't get it to download over 3G, so I guess I'll wait until the morning, when I'm home.
BTW, if your phone dies ("Battery Low - Cannot program" message) while trying a rollback to 2.3.5 try the following procedure. It's risky but I was able to bring my Atrix 2 to live:
http://forum.xda-developers.com/showthread.php?t=892026
Per this poster over on S4GRU.com, the new version is 77.8.10.XT897.Sprint.en.US:
http://s4gru.com/index.php?/topic/2507-photon-q-software-update/
Yeah, I had seen someone on the Sprint forums say he got the update last night. He said IM didn't work aterwards, but I wasn't sure if he meant Gtalk, or what.
I am rooted and debloated as well, but from my experience, that shouldn't prevent the device from saying an update is available.... but the update could fail if we try and apply it like this... I always go back to stock unrooted if I wanna install an update.
I think at least one thing they were supposed to address was that VSNCP registratiom error that pops up sometimes, I've seen it pretty much every day, and I've even done the fix of editing my data profile username.
Sent from my XT897 using Xparent ICS Tapatalk 2
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
yogi2010 said:
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
any idea is it JB or stil ICS?
Pretty sure its still ICS, I'm sure the guy would have said if it were JB, plus something that significant would have hit the various sites beforehand most likely.
yeah, if it were JB we most probably would have heard about it beforehand. i haven't seen many people with the update yet, today i keep getting 'check for update not available at this time'.
Probably to fix the vsncp error message problem.
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
yogi2010 said:
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
Click to expand...
Click to collapse
The tech was an idiot, I just got the popup notification and was able to click on the link for the release notes.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/90757
Yeah, I just got the update notice myself. Thanks!
Gonna install and check it out. Can always revert if it's no good.
Sent from my XT897 using Xparent ICS Tapatalk 2
---------- Post added at 08:11 AM ---------- Previous post was at 08:03 AM ----------
dpwhitty11 said:
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
I'm gonna try restoring the bone-stock backup file, reflashing stock recovery, and then installing the update. From past experience, unlocked bootloader has been ok, it just won't work if your system is rooted/modded.
Sent from my XT897 using Xparent ICS Tapatalk 2
I got the OTA message this morning.
Coming from the shift forum we have learned to never to install OTA updates. However this one looks harmless.
Who knows.. maybe my LTE will start actually working?
Sent from my XT897 using xda app-developers app
anyone do the update with a rooted phone>?
Got the update pushed down around 10:30 am est today.
From the release notes:
Multimedia Texting - Improved MMS texting functionality when the Data Username/NAI has changed to a shorter length
Click to expand...
Click to collapse
This is most likely the data profile extra ".com" fix. I like their wording.
Hey a quick question to everyone. Never really had to deal with Sprint for my epic since XDA had everything I needed but I have gotten very concerned with the information around this and the "VSNCP" stuff. Are the tech's normally this clueless? Is there a quick way to talk to someone that actually knows what they are talking about? They told me I had to get a new phone the other day due to these issues. How could they tell me that if a software update to fix it is going to be release a week later?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
swintec said:
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
Click to expand...
Click to collapse
I am also rooted (and unlocked, of course you have to be unlocked to be rooted ), but my phone went through a different scenario.
I downloaded the update (was 56MB I believe, somewhere around there. The update is 77.8.10.en.US). Downloaded it via Wi-Fi, then the phone asked if I wanted to install. I pressed Install Now, and it rebooted.
My phone rebooted and went into recovery. I dont remember everything, but it asked if I wanted to install "Unknown.zip", and it had:
No
No
No
No
Yes - Install Unknown.zip
No
No
No
Etc... I clicked No, then it went to the recovery menu (where you have the option to restart the phone, and the other options.. sorry, I've only ever rooted my evo shift so my termoinology is limited). I rebooted the phone via the first option, the phone went through its process, came back up fully, and rebooted by itself! Everything happened again (asking to install the unknown.zip, etc..). Basically, it was in an endless look when I would restart the phone.
First thing I tried was to wipe the Delvik Cache. Did that, rebooted, phone came back up and rebooted by itself again.
Second thing I tried (and I had a feeling I would probably regret this cause it would either brick my phone or unroot it), was to install that Unknown.zip. But that didnt even go through. The install failed (A message appeared at the bottom of the phone along with the other message logs, so I really dont remember exactly what it said. It was just an error message basically).
At this point I didnt know what to do... so I got to the recovery menu (where it said Reboot phone, Advanced, and the other options), and I selected the one that said to Wipe Cache. Not the Delvik cache but the phone cache (I dont think the option said Wipe Cache, but something similar?). Did that, rebooted, and my phone stayed on! The update popped up again, and this time I pressed "Later". Learned my lesson.
I guess the update may be hit or miss for rooted users?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
Yes, clockwork recovery booted up and the update failed.. probably going to flash the stock image..
But my phone says I'm up to date?
Kenneth196 said:
I guess the update may be hit or miss for rooted users?
Click to expand...
Click to collapse
Possibly..I dunno. I used the 2nd method posted only a few weeks ago and a few clicks of the mouse to root...not the first method initially posted when the phone first came out. When I clicked update now it simply rebooted and the android guy came up and did its thing...about 5 minutes later everything was back to normal.
I wiped my phone completely and am not getting a notification about the OTA now.
I'm flashing TWRP and hoping I get notified again.
Is there a way to flash the stock recovery?
I installed this update, all I can confirm is that it's still Android version 4.0.4. Otherwise I've really not noticed anything different or new yet, but I haven't had much of a chance to use it.
Hello there! i'm making my forum debut while extremely confused as to how to proceed with fixing my Verizon Galaxy S3, running the stock android JB 4.3. So there is no custom ROM.
I realize that this may or may not be similar to a plethora of posts about apps crashing around the time android 4.3 was released but i've upgraded to 4.3 less than a month ago. After diving through countless forums, i couldn't find one that addressed the same problems that my device had. They were all similar, but the solutions posed in those threads did not work with my device. Plus the problems i have are not isolated to one app.
I had just recently upgraded to android 4.3 which had unrooted my previously rooted device. After using Chainfire's method of rooting the SCH-I535, utilizing saferoot, i then installed the Xsposed Framework and that was really where my troubles began. A few days had passed while i was tinkering with a few modules like XBlast tools, XHaloFloatingWindow, Xposed Torch, and Wanam Xposed, and i had a good sense of what mods interfered with other mods and it was only last night when the problem first arose.
Without warning, a game that i play all the time stopped working. Literally in the time span of 6 hours (i was sleeping) something happened and the beginning of my problems started. Every time i would open the app, the app itself would close and i would get a message saying, "Unfortunately, Valkyrie Crusade has stopped." It was only a few hours later did i realize that Pandora, an app i use every day, suddenly stopped working and provided me with the same message. There was no error ID, and clearing the cache/data, reinstalling the apps, did not work. Once it became 4-5 apps that i normally use to get the message, i tried uninstalling the mods as well as the xposed framework but that also did not work. I also tried restoring the game as well as the other apps to a backup i'd made just the week prior with Titanium Backup but i still had the message coming up and the apps still did not work.
As a last resort i did a factory wipe/reset. During the initial set up, i opted to allow google to restore my apps (which i'm not sure i should have done) and after everything was restored, i tried using the apps, and i was met with the familiar message "Unfortunately, (app) has stopped.". I have run out of ideas. While i'm more tech savvy than most, i'm really just a novice when it comes to Android. How should i approach my next step? If anyone needs logs or anything like that, if you would be so kind as to walk me through the steps to get them.
Thank you, thank you, thank you in advance.
EDIT - 2/10/14
I have successfully resolved the issue (or at least, removed it) from happening. I bricked my phone but thankfully i was able to get into download mode.
Follow this guide! http://forum.xda-developers.com/showthread.php?t=2586319 - just be aware, this will delete all of your apps. backup all your propers and jump in.
This is the only method that i had success with. Other methods i tried are explained above and in the comments. Good luck and i hope everything works out!
If you had the Xposed frameware installed and you also installed Wanam xposed, this will help if you are experiencing apps crashing. I'm no expert, but i'm really glad to have resolved this as quickly as possible. I couldn't have done it without everyone! You guys literally kept my sanity healthy during this whole ordeal.
*NOTE* - The link to the guide above will lead you to a stock rom of android 4.3 for the SCH-I535. I'm not sure about other samsung devices but one user had success with a SCH-I605 (galaxy note 2) in the comments.
*ANOTHER NOTE*- i'm not in any way explicitly saying that the xposed framework and wanam xposed module are the cause of this glitch. Frankly i have no idea. But they seem to have been problems for a few people, myself included. If you want to explore this further, i'd suggest going to each of the respective forums. For me, i'm going to make sure i have a proper Nandroid before i do anything crazy. Lesson learned.
Again, Thank you!
PS- since i'm newer to this forum, i have no idea how to edit the title of this Q....haha if someone could let me know....that would be great.
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
daoist said:
I am having a similar issue.
Can you check your logcat to see what's going on?
I'm getting a segfault in webview code. I believe my issue is only in apps which provide a webview (e.g. mostly apps which display ads).
There were a flurry of updates to the google stuff (google search, google play services) as well as to a bunch of xposed modules over the past couple days. Sometime after this I noticed my problems starting.
Click to expand...
Click to collapse
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
awstuder said:
This is actually my first time checking a logcat. What should i be looking for? I'm a little overwhelmed with all the colors and all the text in the one log that i made trying to open the app.
I filtered the log with the name of the app and also "seg" to see what i would get. CrashAnrDetector w/ the letter D inside a blue square that has (SEGV_ACCERR), fault addr #######.
was that what you were talking about? From what i could see there were crash reports with webview code when the app was opening up a website.
:fingers-crossed:
Click to expand...
Click to collapse
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
BadUsername said:
Sometimes xposed breaks apps or system ui. Disable it, reboot, and see if your problems persist, it's hard to read a logcat.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
ATGkompressor said:
I had a similar problem, tried everything u guys have. Ultimately...Nandroid...never go wrong with a Nan handy. I haven't touched Wanam since I flashed wicked. My problems started with either the 2.7.3 Wanam update, the torch update or both.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I think i'll try that next. I used to have TWRP but had to flash the stock recovery just to upgrade to 4.3. I'll try to get a clean copy of stock OS, flash and just start over from scratch. I'll be sure to let you guys know if i got it to work.
ran into a bump in the road. flashing a stock copy of android 4.0.4 did not work. Browsing through a few forums informed me that i'm unable to downgrade after i've taken the 4.3 upgrade. so next i tried to flash TWRP to boot into recovery mode and flash a rom from there. That didn't work either. I kept getting an authentification error.
As of now i can't get into download mode anymore. I get the yellow triangle saying Verizon detects unauthorized software. I'm able to get into recovery mode but i'm not sure what i can do with stock android recovery....
what can i do from here?
EDIT: I am able to get into download mode. I'm not sure why i wasn't before and now i am...
EDIT2: I have tried flashing the "official" stock android 4.3 but it fails everytime. I have also tried flashing twrp and cwm but i get a red Secure Check Fail: recovery. I suspect the bootloader has been locked. I'll look into ways of getting it unlocked again...
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
awstuder said:
unfortunately i've tried disabling xsposed, uninstalling all the modules, reinstalling everything and rebooting everytime and the problem does persist.
Click to expand...
Click to collapse
Same here. Disabling all xposed modules didn't work. Disabling xposed entirely didn't work. Doing both and then uninstalling didn't work. My guess is that along the way either xposed or wanam xposed made some sort of change that it can't roll-back when it's disabled/uninstalled.
I resorted to taking a TiBu update of everything and reflashing.
Once I get my battlestation fully armed and operational I plan on taking frequent nandroids and seeing if I can replicate the issue. Once I do that, (if I do) I can compare the last known good nandroid to see what messed up.
BadUsername said:
http://forum.xda-developers.com/showthread.php?t=2586319
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I wasn't able to do this right away since had class in the morning but as soon as i got home, i did this and it fixed my soft-bricked phone.
thank you thank you!
Now back to the problem at hand......let's see if the problem still persists.
It's completely fixed! No apps (so far :fingers-crossed have crashed and i'm able to happily play my games again! sigh. that was refreshing.
Thank you to everyone! i will edit my first post to outline what i did and how i fixed it, finally....
during saferoot process your suppose to update SU then continue with finishing up the root process..took me several hours to figure this out..no errors now since I figured this out
Sent from my SCH-I535 using XDA Premium 4 mobile app
That... Actually makes sense. When I used safe root I didn't check for any other updates because I assumed the program took care of that for me. That and because when I opened su there were no notifications to update. So maybe that could be a solution as well.
Sent from my SCH-I535 using xda app-developers app
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.
Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.
I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.
I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.
Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.
aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.