Related
This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
SoCalArm said:
I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
Click to expand...
Click to collapse
I'd also like to know about this. I used CASUAL to root my phone, and while I appreciate the features in the 4.1.2 update, I really don't want to lose root. Any insight into this matter would be appreciated.
Perhaps this is what you are looking for if your just worried about keeping root:
https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
Updating won't 'brick' your phone (not sure if that is even possible with this phone without doing something incredibly drastic). Worst case you can always Odin back to stock - just back everything up first. Excellent guide here on how to do that:
http://forum.xda-developers.com/showthread.php?t=2024207
But since you are unlocked I would look into flashing a custom ROM to get the full advantage of it (Jelly Beans or CleanRom are excellent). Tutorial on that is also in the link above.
Hope this helps.
“System software not authorized by Verizon Wireless has been found on your phone.”
heric1 said:
Updating won't 'brick' your phone (not sure if that is even possible with this phone without doing something incredibly drastic). Worst case you can always Odin back to stock - just back everything up first. Excellent guide here on how to do that:
http://forum.xda-developers.com/showthread.php?t=2024207
Click to expand...
Click to collapse
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Use Root Explorer or equivalent and delete the SDM.apk in system/apps. This is the apk that checks for updates.
Oh and if you want to keep root it is never a good idea to accept an OTA update.
http://forum.xda-developers.com/showthread.php?p=36922297
Sent from my SCH-I605 using Tapatalk 2
markustlaumann said:
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Click to expand...
Click to collapse
Odin can be picky after using casual also (try the rooted odin file if stock fails as well, thats what i had to do). You may need to remove the casual drivers as well for odin to recognize the phone, below is a link on that:
https://www.youtube.com/watch?v=zzghcV8HVVk
Also the new release of casual for the 4.1.2 update is set to be released tonight, does anyone know if he could just re-run and to get root and a custom recovery back?
Hopefully not needed.
heric1 said:
You may need to remove the casual drivers as well for odin to recognize the phone
Click to expand...
Click to collapse
Thankfully I was able to get it to boot into recovery mode eventually. Odin and Kies worked correctly to recognize the phone in download mode and I tried the root66 image with no luck. I'm downloading the VRALJB now to see if that works.
Update: I got my phone back to stock using the guide heric1 posted and the "alternate restore" image here. No bricks in my house.
Use this to update won't loose root...
http://forum.xda-developers.com/showthread.php?t=2269736
TaPpEd from my TwEaKeD N2
SoCalArm said:
I'm on 4.1.1 and used one click root & unlock on this forum.
This morning I woke up to an OTA but declined and asked to post pone till 5/13.
What do I do ? I can't afford a bricked phone, nor do I care to grab an update.
I have a feeling on the post pone date it will automatically update.
Sent from my SCH-i605 on Verizon 4G LTE.
Click to expand...
Click to collapse
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2261478 created by developer beanstown106. Here you will find the latest update modified and placed into a flashable zip file through your custom recovery. If you flash one of those two files that he has, you can have the latest update, keep your root and unlocked bootloader, and be on a stock ROM.
There are two versions of the stock 4.1.2 ROM. The odex version doesn't allow for custom themes to be flash over the stock ROM, while the deodex version does allow for custom themes to be flashed over the stock ROM.
If you don't want 4.1.2 altogether, you can use Titanium Backup or My Backup Pro to freeze the SDM 1.0 file. A slightly more challenging method would be to use Root Explorer or something similar to it to go in and modify the name of the file.
---------- Post added at 10:16 AM ---------- Previous post was at 10:07 AM ----------
For me I use the odex because I have no intention on using themes. My custom ROM and theming days have long passed. All I need is the ability create backups of my stock ROM and the ability to take advantage or root required applications such as Titanium Backup and My Backup Pro.
---------- Post added at 10:26 AM ---------- Previous post was at 10:16 AM ----------
markustlaumann said:
I clicked yes on the update and now I get this message on boot and I can't get to the recovery menu:
“System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help.”
Things I did to my phone prior to this:
- rooted with Framapak
- CWM installed
- Encrypted the internal storage
I'll be praying to Odin tonight...
Click to expand...
Click to collapse
Check out this thread right here http://forum.xda-developers.com/showthread.php?t=2107738 if you are experiencing the "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help" crap. That should get your phone back up and running.
I ended up doing a nandroid back up aswell ass app and data backup and flashing beans. With the help from a admin over at note2forums. So that's my update and I'm digging 4.1.2
I also got something from here that made multi window fantastic and a clear notification bar as well as other goodies.
Sent from my SCH-i605 on Verizon 4G LTE.
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
It is amazing with most of the searching I have done about this update, VS98026A, on how they say that this is the KitKat 4.4.4 update. When it isn't and we are still at 4.4.2.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
Rooted vs98024a and did OTA to vs98026a and still have Root. Pretty neat we didn't lose Root.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
lukester01 said:
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
Click to expand...
Click to collapse
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
wait for new ioroot?
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
RobertVanHagar said:
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
Click to expand...
Click to collapse
lukester01 said:
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
Click to expand...
Click to collapse
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Stump root worked on LG G2 26A
Stump root worked. It auto used the brute forth method like you said. Thanks.
Finally I can program my bluetooth call button back to use google now voice search instead of LG voice command.
snellc001 said:
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Click to expand...
Click to collapse
I used stump root successfully on my 26A as well.
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
Simply remove the modified mobile hotspot from system/app. That should allow you to take the OTA
Sent From The Trail Of Untold Truths
you will not be able to take any OTA if you add a custom recovery
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
If you add a custom recovery you will not be able to take any OTA updates.
lukester01 said:
If you add a custom recovery you will not be able to take any OTA updates.
Click to expand...
Click to collapse
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Correct, you don't need one. Note however you won't be able to do image (nandroid) backups/restores or flash images. So be very careful with your root privileges ?
Sent from my VS980 4G
custom recovery
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Custom recovery allows you to flash roms, make nandroid backups, and do several other things. But it will make the phone so that you cannot get OTA updates. To apply updates when you have a custom recovery you will have to wait for someone to make the OTA update into a file you can flash.
TWRP
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
MFR73 said:
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
Click to expand...
Click to collapse
I'm not familiar with TWRP commands, but sounds to me like the update tried to install by booting to recovery, but since it was not the stock recovery it could not update. Having a custom recovery in my experience has always made it so you can not take OTA updates. You would use the LG Mobile Support Tool to "upgrade recovery", that will basically restore the stock recovery. You will lose root. But you can update to 26A, and then use Stump root to get root again.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
had that happen
nicknjg88 said:
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
Click to expand...
Click to collapse
Look back a page. I had the same problem. You need to use the LG Mobile Support Tool and upgrade your recovery. Then take the over the air update. Then root again using Stump root.
I got the 0x1111004 error, and then the 0x1117008 error when trying to take the 25B and 26A update. I tried removing all of my framework and changes, but it didn't seem to help. Resorted to full KDZ wipe to 24A, then ioroot before taking the 26A update. It updated just fine and now I'm running the latest. Now to remove all the bloatware and restore my backups...
I'm hoping they don't push out any more OTA anytime soon unless it's L.
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Beartooth01 said:
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Click to expand...
Click to collapse
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Thanks - worked for a while - then popup returned
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
I did try that. The popup went away for several days and then came back. There must be at least one root-level app I haven't disabled.
Thanks for the help, but I'm afraid I still need a bit more.
Still having popups...
socal87 said:
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Click to expand...
Click to collapse
When I first got the phone, I disabled OTA, I ran the update - which failed, of course. It got rid of the popup, but I did not wipe the phone as I am a longtime Motorola Droid user and am not totally comfortable using Odin (This is my first Samsung and it's like going from Droid expert to Odin newbie). I have since restored nandroid and Titanium backups from the previous phone (this is a warranty refurb). The backups also included disabled OTA apps from my previous S4. Apparently, I missed one somewhere, as the behavior just recently returned. I'm going fishing on the root level again [sigh].
If anybody would be so kind as to list the exact .apks and their directories involved in OTA, I can make sure they are still disabled and run another failed update. This may be different from my Droids, since it is being referred to as a Samsung build update, and not an Android version update.
If anybody knows where the downloaded update is hiding, I can remove that as well.
Thanks in advance.
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Thanks also.
fxwrangler said:
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Click to expand...
Click to collapse
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
i just made a post about the same problem. I renamed them. so we will see what happens
To delete the OTA zip use a file explorer with root privileges like "ES File Explorer" navigate to /data/fota and delete update.zip
Beartooth01 said:
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
Click to expand...
Click to collapse
That link is dead. Can you please direct me to a good link for that? Thank you
re-rooting after MJ7 kernal pushed by google?
swolh said:
That link is dead. Can you please direct me to a good link for that? Thank you
Click to expand...
Click to collapse
Well - renaming SDM.apk and FWUpgrade.akp stopped the totally annoying push notification for google's new MJ7 build for the S4. But by renaming SDM.apk, my Verizon app visual voice mail stopped working. When I returned the SDM.apk file to it's original name, the visual voice mail works, but I get the annoying notification from google over and over.
I'm trying YouMail app for visual software and am waiting to hear from them about whether their app uses SDM.apk. If YouMail is like Verizon's visual voice mail and uses SDM.apk, then my next thought is to unroot the phone, let Google do their update to MJ7, then re-root. I'm wondering if anyone has done this.
My phone came with NG6. To root, I had to flash the NG5 stock kernal, then root using towelroot. Once rooted, I flashed the NG6 kernal. If I unroot and let google flash their new MJ7 kernal, will I be able to repeat the root process (flash NG5, the root, then flash MJ7)? If that route were possible, would I need to find a separate place to download the MJ7?
Is there any other way to stop google's annoying notificaton and pushing MJ7 at me? All help greatly appreciated.
---------- Post added at 09:58 PM ---------- Previous post was at 09:16 PM ----------
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
My apology. I missed this link first time thru this thread. That link to a thread titled "[HOW TO] Disable OTA Update Notifications!!!!!!!!!!!!!" is pretty helpful. We'll see in a day or two if the notification and push attempt continues, but I'm pretty optimistic following the instructions in that thread will stop it.
Looks like Verizon is pushing 24B update today. Very minor fixes but it's not showing up on my phone yet. Here is Verizon's release for it. http://www.verizonwireless.com/dam/support/pdf/system_update/benefits-lg-g3-7-9-15.pdf?null
Hmm. Do the interruptions mean that they have fixed notifications on wifi? It seems a bit cryptic.
Does anyone know if there will be issues if you try to take this OTA while rooted?
I am still on 23a. The OTA is not showing up and the upgrade assistant is of no help either.
Going to wait and see if we can flash back to a previous version, especially if root and bumping are locked out. Don't want it and currently, LP is running pretty well for me (has been since April when I upgraded to it). I haven't rooted as of yet either. Don't have a need for it right now and want to wait and see when the next big OTA comes out or if this upcoming one does fix the WiFi sync issue completely.
adrianbli said:
Hmm. Do the interruptions mean that they have fixed notifications on wifi? It seems a bit cryptic.
Does anyone know if there will be issues if you try to take this OTA while rooted?
Click to expand...
Click to collapse
As a general rule, with ANY phone, running ANY software, do NOT take ANY OTA's while any modifications have been made to your system (this includes rooting, custom recovery, etc.). Could it go through? Maybe, no one really knows until some bonehead tries and it fails or a trusted member of the community lets people know. If it doesn't, you're in for much more of a headache than the update benefits you, and possibly much worse. Your only options should be either to 1) wait until someone releases an updated rom based on this update (which this update is pretty near worthless anyways - doesn't contain anything major), or 2) tot or kdz back to stock and upgrade without any modifications.
I am still waiting on it to show up on my phone for OTA. I'll upgrade to it and let you know if it fixes the wifi bug.
Installing now
Yeah, I just see added features, no bug fixes listed on the changelog. Does Verizon usually list bug fixes on their updates release notes?
---------- Post added at 12:13 PM ---------- Previous post was at 11:56 AM ----------
Downloading via OTA now! 197.5 MB.
It looks to me like the update might have fixed the wifi bug. I uninstalled DNSet and sent an email to myself and I got the notification right away. I am restarting now to see if that makes any difference.
I'm stock/rooted (no bump) on 23C right now. I have not changed any system files from what I can recall. I'm currently running a titanium backup.
Once that's done, I'll unfreeze my frozen apps and I'll accept the OTA. Hopefully, I'll retain root. Through all of the previous updates with this phone, I have no lost root in taking an OTA.
I'll report back in around a half hour or so.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
matty032 said:
Yeah, I just see added features, no bug fixes listed on the changelog. Does Verizon usually list bug fixes on their updates release notes?
---------- Post added at 12:13 PM ---------- Previous post was at 11:56 AM ----------
Downloading via OTA now! 197.5 MB.
Click to expand...
Click to collapse
Are you currently rooted? If so, let me know if you keep root during OTA.
lexluthor said:
I'm stock/rooted (no bump) on 23C right now. I have not changed any system files from what I can recall. I'm currently running a titanium backup.
Once that's done, I'll unfreeze my frozen apps and I'll accept the OTA. Hopefully, I'll retain root. Through all of the previous updates with this phone, I have no lost root in taking an OTA.
I'll report back in around a half hour or so.
---------- Post added at 12:51 PM ---------- Previous post was at 12:50 PM ----------
Are you currently rooted? If so, let me know if you keep root during OTA.
Click to expand...
Click to collapse
Sorry not rooted. After the first restart, it didn't seem to have fixed the WiFi sync problem. But, after it calmed down awhile, so far it seems to be fixed. God I hope so!
matty032 said:
Sorry not rooted. After the first restart, it didn't seem to have fixed the WiFi sync problem. But, after it calmed down awhile, so far it seems to be fixed. God I hope so!
Click to expand...
Click to collapse
Can someone verify if they can root with the latest one-click root method and if you can revert back to a previous version to bump (KDZ or TOT)? I want to make sure they haven't locked out the ability to bump.
Well that didn't go so well. Upon rebooting to start the install, I quickly got an error message at the 1% mark
Err: 0x1111004
I don't recall any changed system files, but I guess there must be as that's what the error is most likely about?
Guess I'm sitting this out for a bit.
lexluthor said:
Well that didn't go so well. Upon rebooting to start the install, I quickly got an error message at the 1% mark
Err: 0x1111004
I don't recall any changed system files, but I guess there must be as that's what the error is most likely about?
Guess I'm sitting this out for a bit.
Click to expand...
Click to collapse
Are you rooted and/or bumped? If you rooted and then unrooted (but didn't flash back via TOT or KDZ), then the system image is modified, even if you removed root as rooting modifies the system partition. Therefore, no OTAs will be accepted until you flash back to pure stock via TOT or KDZ.
iBolski said:
Are you rooted and/or bumped? If you rooted and then unrooted (but didn't flash back via TOT or KDZ), then the system image is modified, even if you removed root as rooting modifies the system partition. Therefore, no OTAs will be accepted until you flash back to pure stock via TOT or KDZ.
Click to expand...
Click to collapse
I'm just rooted.
I know I've accepted OTAs in the past on my LG G3 while rooted and it worked fine. I didn't even try to unroot (this time or previous times).
Posted a link to the OTA files in @bweN diorD 's thread [REFERENCE] Stock IMG files + Stock Links & Mods.
I do believe if you were rooted going from KK to LP, it definitely didn't work and it could be this time around, if you used the new one-click root, it does the root differently to the point that it won't allow an OTA. I do remember I could update from 10b to 11c to 12b rooted as long as I had preserve root enabled in SuperSU. But, going from 12b to 23c rooted was a no-go and you had to flash back to stock. So, I'm going to chalk this up to the new one-click root method has done something that won't allow even a minor OTA from 23c to 24b to be allowed.
My freshly flashed 23C KDZ is a quarter of the way optimizing, then I'll take the OTA and try the one-click root again. After that, I'll test reflashing the 23C KDZ once more.
Edit: Update...weird. Under JasmineROM 7.0 (no debloat or mods, but rooted), it gave me the OTA, which I then moved from it's folder. Now that I've flashed the 23C KDZ in CSE mode, now it says I have no updates. I'll reboot and try again. If I have to I'll use the Activity Launcher method to run the OTA I already downloaded.
Update 2: Haven't had any luck applying the update with the "Activity Launcher" method. FOTA starts, the phone reboots but just boots the ROM and I have a notification that it failed to update. System Updates still claims I don't have an OTA available even though I did under JasmineROM 7.0 (rooted but not debloated and not modded).
I left my work WiFi, and came back. Google notifications are still working, and calls are still ringing Hangouts. MS Outlook app notifications are also working.
matty032 said:
I left my work WiFi, and came back. Google notifications are still working, and calls are still ringing Hangouts. MS Outlook app notifications are also working.
Click to expand...
Click to collapse
I had to read this 4 times to make sure there weren't any "not" in front of "working."
roirraW "edor" ehT said:
Posted a link to the OTA files in @bweN diorD 's thread [REFERENCE] Stock IMG files + Stock Links & Mods.
Click to expand...
Click to collapse
I can give that a try and see if it behaves any differently than the file I downloaded, but I doubt it. I would put this on my sdcard and then what?
So if the OTA fails on my stock/rooted phone, is there any way to get to 24B without a losing everything? If that's not available today, is that something that typically would be available at some point?