Related
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
FingerBlastJ said:
I get these annoying pop up notifications about nfc not working and other stuff and certain apps freeze for a sec then start up again. I have the screen shots that i will attach. I used the new method on this site after i got the stock JB update from VZ OTA.
Also, im a noob even though i got this done using VM and a cracked version of windows xp.
Please help!!!
Click to expand...
Click to collapse
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
x714x said:
I take it you are running a custom recovery? Boot into it and clear your cache and dalvik cache and then fix permissions. Usually force closes are permission issues. If it doesn't fix it maybe a factory reset? If that don't do anything either then just flash the JB rooted image with odin from here
Click to expand...
Click to collapse
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
FingerBlastJ said:
how long does it normally take to fix permissions? its been doing it for 5 mins and it almost seems frozen and this is my 2nd attempt. i took out the battery and tried again. what should i do now?
Click to expand...
Click to collapse
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
FingerBlastJ said:
ok now i have a bigger problem, "unfortunately, touchwiz hom has stopped" flashes every5 secs and i cant even use my phone. what do i do?
Click to expand...
Click to collapse
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
x714x said:
Download that stock rooted JB image I linked to and flash it with odin. If you don't know how to use odin follow step 5 in this guide. Fixing permissions should only take a couple mins tops on a stock rom so something is probably corrupted and causing issues.
Click to expand...
Click to collapse
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
FingerBlastJ said:
yea i know how to flash with odin, im gonna try it right now with the non wipe version of the latest JB
Click to expand...
Click to collapse
odin isnt allowing me to flash that image, attached is a screen shot
What does the error say? I can't read it that small.
x714x said:
What does the error say? I can't read it that small.
Click to expand...
Click to collapse
it says vmware-host\shared folders\desktop\root files\root66 file ..... then all these special characters that look like boxes
i tried running a different launcher, and they work a lil better but touchwiz is by far superior but i still get the nfc stopped message and everything is much slower
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
x714x said:
Ya i dont know what what that refers too either, you have a windows computer you can run it on then inside a VM?
Click to expand...
Click to collapse
im using a mac so im forced to use windows xp on VM
FingerBlastJ said:
im using a mac so im forced to use windows xp on VM
Click to expand...
Click to collapse
ok i just did a factory reset and i still have the nfc issue along with the com.android.phone issue and i cant get into the mobile networks, any ideas of what i can do?
this thread here says its an nfc fix i just dont know if it will ruin my nfc capabilities
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
please help.
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
x714x said:
Something is corrupt on the system is my guess. Im thinking your only option is to flash the os again.
Click to expand...
Click to collapse
by flashing you mean formatting? why would that do anything when it didnt do much the first time?
About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data
ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks
Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.
esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.
Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.
Freeze software update with titanium backup so your phone doesn't try to install the update agian
wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Im using my att phone on the cricket network and it wont update so What files would i need to download to update my att sm-n950u baseband version N950USQS3BRA8 to latest ota Oreo update? and which odin? thanks for the help
icepick090 said:
Im using my att phone on the cricket network and it wont update so What files would i need to download to update my att sm-n950u baseband version N950USQS3BRA8 to latest ota Oreo update? and which odin? thanks for the help
Click to expand...
Click to collapse
Go HERE download N950USQS5CRK1 and Odin3_v3.13.3b
I'd completely recommend creating a backup and NOT do a dirty flash. Allow the device to do a factory reset.
Don't mess with the Update.zip method, it's not worth the time.
so i downloaded it started odin, put in bl, ap, cp, and CSC_OYN in the fields and put phone into download mode (volume down, bixby, and power) it did its thing was sucessful then phone rebooted saying android update it got to about 32% and said error and brought me to bootloaded screen with some writing at bottom or whatever. i did reboot now after that, and it booted into android and was updated. Only thing is it never formatted my phone and all my stuff is still on there. does it sound right or did i messup somewhere
icepick090 said:
so i downloaded it started odin, put in bl, ap, cp, and CSC_OYN in the fields and put phone into download mode (volume down, bixby, and power) it did its thing was sucessful then phone rebooted saying android update it got to about 32% and said error and brought me to bootloaded screen with some writing at bottom or whatever. i did reboot now after that, and it booted into android and was updated. Only thing is it never formatted my phone and all my stuff is still on there. does it sound right or did i messup somewhere
Click to expand...
Click to collapse
It sounds about right, I have seen it fail at 32% before. I'd double check in your Settings to make sure you're on CRK1, but if it's working ok, no harm no foul. IF your phone starts doing odd stuff, or apps are FC'ing, I'd hop into Recovery and do a Factory reset
kangi26 said:
It sounds about right, I have seen it fail at 32% before. I'd double check in your Settings to make sure you're on CRK1, but if it's working ok, no harm no foul. IF your phone starts doing odd stuff, or apps are FC'ing, I'd hop into Recovery and do a Factory reset
Click to expand...
Click to collapse
Ya it says baseband crk1. Everything seems about the same on phone though except the about phone settings menu is a little diffrent. Now is this the newest Ota update or did they release pie for it yet?
icepick090 said:
Ya it says baseband crk1. Everything seems about the same on phone though except the about phone settings menu is a little diffrent. Now is this the newest Ota update or did they release pie for it yet?
Click to expand...
Click to collapse
Sounds like AT&T did send out an OTA to CRL1, but I haven't been able to get the Odin files for it yet. Pie isn't probably going to hit until March-ish, I've only seen the DRL5, 6 and 7 leaks and even those have stopped. We COULD see AT&T do some beta releases, but we just don't know right now.
After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
DeathCite said:
After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
Click to expand...
Click to collapse
If you only took one A12 update you still have A11 opposite slot. Boot fastboot "fastboot --set-active=other" wipe date and boot into A11. And don't update again.
mattie_49 said:
If you only took one A12 update you still have A11 opposite slot. Boot fastboot "fastboot --set-active=other" wipe date and boot into A11. And don't update again.
Click to expand...
Click to collapse
Oh yeah I forgot I could do that thanks !
DeathCite said:
Oh yeah I forgot I could do that thanks !
Click to expand...
Click to collapse
As long as you only took C36 this will work. Just returns you where you came from. If you updated to C39 C40 you have A12 on both slots. Won't work
mattie_49 said:
As long as you only took C36 this will work. Just returns you where you came from. If you updated to C39 C40 you have A12 on both slots. Won't work
Click to expand...
Click to collapse
Got it working again, but what causes OOS 12 not to work ?
DeathCite said:
Got it working again, but what causes OOS 12 not to work ?
Click to expand...
Click to collapse
I've read a lot about devices reacting like this. Mainly pros. OnePlus rushed the build . It's awful in all ways. Wrecking devices. Glad you got it working. Take full backup through twrp to have one.
I used msm tool oneplus 9 pro indian version for my 9 it works but should use oxygen updater to change model
DeathCite said:
Got it working again, but what causes OOS 12 not to work ?
Click to expand...
Click to collapse
DeathCite said:
After updating my phone to OOS 12 my screen became totally unresponsive. I tried to revert back to a older version by flashing TWRP but after booting into it the phone goes straight to CrashDump Mode. I tried using T-Mobile and Global MSM but they both give a "Unsupported Target IN" error or "Param Preload"
Nothing is working to revive this device, it turns on just fine but again no touchscreen , any help is greatly welcomed
Click to expand...
Click to collapse
Only way I was able to avoid this is MSM back to stock completely. Then update all the way to Android 12 from within the System Update settings. Then I unlocked my bootloader again, for some reason having an unlocked bootloader caused the unresponsive screen issue for me everytime.
Also I was able to get the Global MSM to work but had to uncheck the "SHA256 check" and the "Auto Reboot" options and also select "O2" as the target from the dropdown and its been working ever since.
jshinn1 said:
Only way I was able to avoid this is MSM back to stock completely. Then update all the way to Android 12 from within the System Update settings. Then I unlocked my bootloader again, for some reason having an unlocked bootloader caused the unresponsive screen issue for me everytime.
Also I was able to get the Global MSM to work but had to uncheck the "SHA256 check" and the "Auto Reboot" options and also select "O2" as the target from the dropdown and its been working ever since.
Click to expand...
Click to collapse
Is OOS 12 even worth it for the trouble ?
DeathCite said:
Is OOS 12 even worth it for the trouble ?
Click to expand...
Click to collapse
Gotta try it out to know for sure. Some people say it's much better on battery, and others are saying it still has bugs. I just started using it and so far no issues.
DeathCite said:
Is OOS 12 even worth it for the trouble ?
Click to expand...
Click to collapse
They fixed most issues in the debug builds. Yes I see it being a decent os
TikiThePug said:
Gotta try it out to know for sure. Some people say it's much better on battery, and others are saying it still has bugs. I just started using it and so far no issues.
Click to expand...
Click to collapse
It's actually nice after 39-40 updates/bug fixes.
OK fortunately for you I have already gone through this issue and solved it after a ****load of trying different things.
The issue is that when your flashing you've switched from the slot you were on to the other available slot on your device. If you were on slot_A for the time you've had your phone rooted until now, make sure before you flash that you set your phone back to slot A. I suggest you set it to slot A and if the problem persists without change switch to slot B. I guarantee 100% this will fix the issue.
Commands to cure issue:
fastboot set_active a
Reboot. Voila. If issue persists then:
fastboot set_active b then restart.
Positive vibes brother
71NnX said:
OK fortunately for you I have already gone through this issue and solved it after a ****load of trying different things.
The issue is that when your flashing you've switched from the slot you were on to the other available slot on your device. If you were on slot_A for the time you've had your phone rooted until now, make sure before you flash that you set your phone back to slot A. I suggest you set it to slot A and if the problem persists without change switch to slot B. I guarantee 100% this will fix the issue.
Commands to cure issue:
fastboot set_active a
Reboot. Voila. If issue persists then:
fastboot set_active b then restart.
Positive vibes brother
Click to expand...
Click to collapse
Great response but it's actually fastboot --set-active =other