[HOW TO] Disable OTA Update (G-Note 3) Notifications!!!!!!!!!!!!! - Verizon Galaxy Note 3 General

The user lordazoroth originally posted this method here in the T-Mobile SGSIII forum. However, I have confirmed that it works with the Note 3 (at least with the Verizon variant) with one small difference. Feel free to give us both a "THANKS" if this helped you out.
You can disable the OTA Update notification by following the steps below. Just be aware that there is a small change in STEP #3.
Solution:
Step 1. Delete the update located in /cache/fota/ (may be /data/fota) and then click the update notification prompt to install it, it will instantly fail and the notification will disappear. (My phone rebooted and tried to install the update - this is the point where my Note 3 gave the update failed notification. I just rebooted the phone and went to STEP #2.)
Step 2. Disable otacerts.zip located in /etc/security by renaming it to otacerts.zip.bak
Step 3. Disable FotaClient.apk and FWUpgrade.apk by renaming with .bak extensions located in /system/app/
Step 4. Reboot
(NOTE: The difference in STEP #3 for the Galaxy Note 3 is that the [FotaClient.apk] is named [LocalFotaClient.apk] instead of just [FotaClient.apk]. All of the other steps are the same.
Continue running JB 4.3 and enjoy your Note 3 without that nagging update notification!

But the kitkat update is awesome... so you might want to reconsider doing this
Sent from my Note 3 using Tapatalk Pro

Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works

lmike6453 said:
Wouldn't just freezing the "SDM" app do the trick? And possibly "FWUpgrade", although i heard that just SDM works
Click to expand...
Click to collapse
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk

Grompy said:
You're right. Freezing just sdm would do the trick lol
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk

TMFGO45 said:
Say I'm not using TiBu. Can I use root explore to change something with sdm or should I just do what was originally posted?
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I personally use ROM Toolbox to do it

I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?

As of this morning...Verizon seems to be trying to "ram the update" onto your note 3
I was rooted and safestrapped on MJE and when I unplugged my phone from the charger this morning...I had a notice that the update failed to install.
I had previously downloaded, but removed the download.
Sent from my Note 3 via Tapatalk

boamuro said:
I got the annoying OTA update today... I DON'T WANT TO UPDATE!!! Why can't they give us an option instead of forcing it down our throats?
Is there any way to disable the update WITHOUT ROOTING? I read everywhere you need ROOT ACCESS to delete the SDM.apk FILE and such. I can't delete it without root.
How can I get rid of the annoying update WITHOUT ROOTING or what is the easiest way to gain root without wiping out everything and starting over?
Click to expand...
Click to collapse
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.

LeftyGR said:
rooting (with jb roms, for us vzw n3 owners) does not wipe anything at all. Kingo is easy. There's how-to threads and vids.
Edit: This is what I recommend. ..
http://forum.xda-developers.com/showthread.php?t=2543386
Edit 2: no way to disable the ota update notification w/o root.
Click to expand...
Click to collapse
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon

boamuro said:
OMG!! I was able too root easily, but the stupid OTA update popped up and I accidentally hit the UPDATE button. Now it rebooted on its own and went into this RECOVERY MODE and it's trying to update... I removed the battery out right away... HOW CAN I CANCEL IT?! OMG! Somone help me please. It was going so well and I can't believe the stupid popup got me...
---------- Post added at 06:23 PM ---------- Previous post was at 06:19 PM ----------
Am I doomed??? OMG I hate you Verizon
Click to expand...
Click to collapse
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>

LeftyGR said:
No way of knowing how far it got. If it was able to get the bootloader nailed in...yes. Screwed. Welcome to kk. If not, whatever you do will wipe at this point.
Safest bet to try and see if you can retain jb is with odin...if it lets you. If it does, great. If it doesn't, you still need odin because you just interrupted a firmware update and probably just soft bricked your phone. So you'll need odin to put kk on your phone.
--
If niether of these things look good, they aren't. So try this first. Try booting to recovery. If you can, it's possible you just saved yourself from learning to use odin. Do a factory reset and reboot. See if it boots to jb. If it does, root asap. If not (it just hangs forever or loops), you're bricked. Try to odin jb. If it keeps failing, you're stuck with kk and you need to odin kk.
If you can't get to recovery and just hangs or loops, odin jb or kk. Whichever it lets you.
If it doesn't let you boot to recovery because it continues to upgrade, at this point let it. This is the ONLY possible scenario that you will keep anything.
Mind you, everything I just covered will never touch any files on external sd memory.
This is a lot to process. So take your time. Good luck!
Odin tutorials are in the general section.
<Note3>
Click to expand...
Click to collapse
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?

boamuro said:
GRRR it installed Kitkat successfully. I'm SO MAD.. I should have set the annoying OTA notification for a different time so that it wouldn't constantly pop up every second... I would have been home free rooted on Jellybean if it weren't for the STUPID UPDATE.
So can I still DOWNGRADE to Jellybean and be rooted? or did Verizon LOCK or restrict stuff with the update? Can I go back to Jellybean keeping all my files?
Click to expand...
Click to collapse
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium

Hulk0069 said:
I heard once you take the verizon ota update for now your locked down.
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!

boamuro said:
I read that too... I can't believe one simple tap mistake ruined my whole first time rooting adventure... Using KINGO was so easy and right when I WAS ABOUT TO DELETE THE STUPID SDM file in the system folder, the update popup came up and accidentally hit the UPDATE And it just rebooted instantly!! I hate how they don't even allow you to cancel or anything... like totally forcing it in your face!!
I still have SuperSU but no longer functions it says "There isn o SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
So there's no way to have root access now?? I can't flash back to Jellybean??? Verizon/Samsung really screwed us here. There must be a way to have root access in Jellybean... I don't care for custom roms... I just want root access!!
Click to expand...
Click to collapse
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium

Hulk0069 said:
It's verizon not Sammy who did this
Sent from my SM-N900V using xda premium
Click to expand...
Click to collapse
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.

boamuro said:
AH EVIL VERIZON... freaking Verizon...
There seriously is no way to flash back to Jellybean and be rooted??? or be rooted in Kitkat?? This is SO RIDICULOUS..
I'm at least glad FoxFi fixed a way to still work with KitKat... if they didn't, I'd be really pissed to have no hotspot and stuck with KitKat... screw you VERIZON.
Click to expand...
Click to collapse
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3

mwshows said:
As it has been warned now many, many, many times.... There is NO GOING BACK if you take the NC4 update. Also, as of now, there also NO root method for it. You're stuck on it.
Sent From The Darkside of My N3
Click to expand...
Click to collapse
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?

boamuro said:
So it would be pointless for me to try to use Odin to flash back to stock Jellybean and then KINGO? It won't even flash back?
I did successfully root before OTA installed Kitkat on mine... does that make any difference?
Click to expand...
Click to collapse
Unfortunately no. Once you have nc4 loaded you cannot go backwards.
<Note3>

bummer

Related

[Q] Rooted T-Bolt downloaded OTA update while sleeping

Ok, so last night my phone downloaded the update (guessing Gingerbread). I'm still running 2.2.1 on my Thunderbolt, as I was out of the country for the past few months. I caught the phone before it completed the installation and thought that if I removed the PG05IMG.zip file from the sd card, that would prevent it from being able to install the update. I turned the phone back on and it began to attempt to install the update again. I would like to flash a new ROM to the phone (as I was simply rooted without a custom ROM before) so that I am running 2.3+ but I don't want to have to re-root the phone. I would like to be able to back everything up before I flash a new ROM. How do I prevent the phone from installing the OTA update that was inadvertently downloaded last night , which will unroot my phone??
Please help! Thank you
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Someone fee free to correct me, but if you flash the CWM recovery it will prevent the update from happening?
Essentially, I just use the phone for wireless tether, so that's mainly why I root. Doubt that changes much of anything...
hallstevenson said:
Not sure if you can stop it at this point and since the phone can still be rooted with the GB update, it may just be easiest to let it go.
Otherwise, if you really want to stop the update, you probably need to boot into Fastboot and find the files that are part of the update. From my Eris days, the OTA update isn't packaged up in the PG05IMG.zip file that you removed. I'm not sure where the files are or what files are the ones you need to delete though...
Click to expand...
Click to collapse
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
tomgillotti said:
So I tried to let the update take, but unfortunately it gets stuck at the screen with Andy and the exclamation point!!
Ughhh.... help! Now I have no workable phone..
Click to expand...
Click to collapse
That's a common problem as I recall from a few weeks back. I saw threads about it but never read them as I wasn't affected. I don't know if it's a dead-end or easily fixed or complicated to fix...
Sent from my ADR6400L using XDA App
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
tomgillotti said:
I stumbled into clockwork recovery earlier... I will see what I can accomplish if I can make it back there!
Side note.. I can get into the phone for a minute or so before it restarts again.
Click to expand...
Click to collapse
johnnyv5 said:
Can you still boot into recovery? I had read that clearing cache and dalvik fixes this...
jv
Click to expand...
Click to collapse
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Thread moved to Q & A
tomgillotti said:
Any thoughts on how to prevent VZW from pushing this update from now on?
Click to expand...
Click to collapse
Install a non-stock ROM. Don't worry, you can get Sense-based ones that won't be anything "new".
It appears that VZW will eventually force the update so there's no way that I'm aware of to stop it while running stock (even rooted stock).
tomgillotti said:
Two thumbs up! So far, so good as for this recommendation. Thank you!!!
Any thoughts on how to prevent VZW from pushing this update from now on?
Also need the best 2.3+ ROM... or is CM9 with 4.0 on the way??
Click to expand...
Click to collapse
Flash a ROM that has the update. There are a few around here that are 2.11.605.5 that you flash in Recovery so that it'll stop bugging you to update. Just pick one that is already rooted. You can do a backup of your currrent rom, flash the 2.11.605.5 then restore your data and your all set....
jv
There are a couple threads on preventing ota updates. A quick search will tell you what file to rename and how to.
Sent from my infected thunderbolt.

Unroot / OTA Update

Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
K-OtiK said:
Very quick question. I have "root only" on my dad's S4 and he's not using root like he thought so if he just takes the update that keeps nagging him, won't mess anything up other than ruining the fact it would patch the root, correct?
Click to expand...
Click to collapse
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
ellisz said:
If all that has been changed is root access, you will probable be ok. Should update and root access will be lost.
Click to expand...
Click to collapse
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
K-OtiK said:
So now I have a problem....I did what you said, it worked just fine. The issue was that it left the "custom/lock" splash screen on. We left it alone and there were no issues. Well now, he has a problem with his phone and has to have it "warrantied"
We have an even bigger problem. I figured out that the right way would have been to just unroot it the proper way from the beginning. Welp unfortunately that is not possible because he took the 4.3 update and now has VRUEMJ7 any ideas how to fix this? Or are we screwed until a new exploit is available?
Please help!?
Click to expand...
Click to collapse
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
kdo23 said:
Your flash counter should be fine, i would think maybe a factory reset and as many as 3 or 4 reboots you should be fine. Basically if you only every rooted before this update you like only get the custom padlock because of the exploit, not from system being changed.
Hard to say for sure since this update is so new, a lot of security has been put in place.
Thing is though if you are warrantying anyways, you might as well try wiping. Backup whatever you can.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
I have the same issue, however I have not tried to wipe yet. I tried the No-Wipe factory restore, however odin fails during the write every time...
Maybe it would work for you:
http://forum.xda-developers.com/showthread.php?t=2301259
K-OtiK said:
Yeah I've wiped it a time or two already and the "custom" splash screen is still there. :-/
Click to expand...
Click to collapse
Full wipe, custom splash gone
Using this link as a guide http://forum.xda-developers.com/showthread.php?t=2301259
and this specific recovery image for the VRUEMJ7 http://forum.xda-developers.com/showthread.php?t=2507253
I was able to completely wipe (and unroot) my dad's verizon galaxy S4. It no longer has the custom splash screen (which was created by Vroot)

For users who soft bricked after MJ7 update!

I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
antisomnic said:
I took the OTA MJ7 4.3 update and then tried doing the M1I root technique and soft bricked my phone. I know some have tried that and others have just had issues where their phone won't boot after taking the OTA. I will share the steps I did that fixed my phone!
1. Place the update.zip from this thread (http://forum.xda-developers.com/showthread.php?t=2502591) on an SD card. You may have to put it in another phone or into an SD card reader.
2. Press and hold volume up + home button for a couple of seconds
3. While still holding those buttons press and hold the power key until the phone vibrates, then release the power key only
4. Your phone should boot into Android System Recovery. Go to Apply update from external sd card.
5. Select update.zip and apply it
6. It will reboot your phone, it will still not boot properly. Remove the battery and follow steps 2-3 again.
7. This time, select Wipe data/factory reset.
8. Once complete reboot your phone, it will boot this time!
I'm so excited my S4 works again!! Hope this helps you guys!
Click to expand...
Click to collapse
Cool! Glad you are up and running.
The MI1 root method flashed a MI1 ROM, so if you are on MJ7, you create a soft brick by trying to root.
Don't do that!!!!
Right. I figured that out the hard way. At least there is a solution
Sent from my SCH-I545 using xda app-developers app
Were you able to boot into android recovery while soft bricked? I experienced the same issue and booted into recovery (volume up, center button, and power button while power is off) and simply did a factory reset. I was able to keep root and fix whatever had gone wrong.
Nevermind, read wrong.
Can be deleted.
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
slackwaresupport said:
tried this.
instead of recovery i get : firmware upgrade encountered an issue. please select recovery mode in kies
Click to expand...
Click to collapse
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
just tried to flash ml1.. failed on system.img.ext4
slackwaresupport said:
just tried to flash ml1.. failed on system.img.ext4
Click to expand...
Click to collapse
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
-Lawless said:
Did you take the MJ7 update and then try to go back to Ml1? I thought that is the error you get if you do try to go back.
Click to expand...
Click to collapse
I was in that boat. Took the OTA and foolishly tried Root de la Vega. Couldn't flash back to MI1 (failed as described) but the new no-wipe MJ7 Odin file saved the day. Good as new (but still unrooted).
http://forum.xda-developers.com/showthread.php?t=2507217
I got root with this post: http://forum.xda-developers.com/showpost.php?p=47187227&postcount=84
As other say, it seems to be bad.
I cleared this post and if you wish, you can check the first line and open the post to see how it goes.
TheJumpingBean said:
You will prolly get banned for this! LOL Either way, it does work. I did it on mine, and all of that is true.
Click to expand...
Click to collapse
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Trak-X said:
Why would i get banned ? Did i do something wrong by sharing the knowledge? I have not taken credit for this and also added the link to the post so it can be verified ;
OK, i removed the link and whoever needs it, can use Google to find it.
Click to expand...
Click to collapse
No there were some xda admins or w/e that said the links 2 this root arent allowed on XDA ne more. Not sure why... I used it and it worked perfectly. oh well. Sowwy
Moderator @Naddict posted this one post prior in that thread. Read up and learn about the risk you are exposing yourself to.
Be aware that as of this moment XDA has deemed the Kingo root method and Vroot method are not allowed on XDA. There are concerns with the information which is collected during the root method by the exploit. It is not about a continuous malware which may affect your device but about important information shared about your device, serial numbers etc during the root process which could be huge securities issues. You have all been warned.
Click to expand...
Click to collapse
This post, courtesy of open1your1eyes, provides some detail from the bright guys that keep us rooted and happy.
We finally have some details on these root methods:
https://twitter.com/TeamAndIRC/status/397767301811802112
TLDR: Uses "Romaster" root method
Click to expand...
Click to collapse
I would take their caution to heart if I was in your position.
--OctOS Powered VZW GS4 Dev Edition
Nice to see the wheels turning here guys. Thumbs up
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
teinwhite said:
I had this happen too. I had to use ODIN to restore to factory MI1 then did OTA to MJ7.
Click to expand...
Click to collapse
Im go the problem where it says Firmware upgrade encountered an issue. how do i fix this? and can u provide a link for the stock firmwares please the mi1 and mj7.
TheJumpingBean said:
I dont know what to think of this. I did the root the first day, and haven't had any problems. I have talked to a few devs and Android engineers who have checked it out and don't think its a threat. I did manage to update mine to SuperSU from the chinese superuser, just in case...
So, I dont know enough to tell you if it is or isnt dangerous, but I can tell u that Im on like day 5 with no issues. I went ahead the first day and installed DroidWall. DroidWall doesnt have any records of su or the chinese superuser trying to access anything, and netstat doesnt show that the su or superuser apps are listening for connections.
I kinda wish we could get some closure on whats happening...
Click to expand...
Click to collapse
How'd you get supersu to work and remove Chinese superuser?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey all, I got a Verizon Galaxy S4 16 gigs. I did the 4.3 OTA, then tried to go back to 4.2.2. I guess that soft bricked it. So do I have to use the MJ7 firmware to make my phone usable again? And if that works, is there any way to go back to 4.2.2? What do I do if it doesn't work?
Update: This worked beautifully, I'm now back to 4.3.

[q] gs4 sch-i545

Need help so lost try to make it as short as possible.
Phone Info:
- Samsung Galaxy S4 Verizon
- Model SCH-I545
- Build JSS15J.I545VRUEMK2
- Android 4.3
Ok, I tried Rooting my Phone and I use the Soft Root that was linked by someone on the forums. Gave me SuperUser Icon and used a app that checks to see if its Rooted and said it was. Now tried using some Root app's like GameCih and it tells me I need Root Admin or Root Privileges, something to that nature, and cant use the app. Iv been trying to remove that Soft Root but cant Figure it out. Used Odin3 and redid that .tar file for my Build. All when good and got everything the same as a fresh phone, but booting up still has the Pad Lock Icon and Custom logo on it and SuperU Icon. So I cant seem to unroot it, Tried to use the I545ALL-IN-ONE-TOOL posted on these forums but cant get it to working.
So what I need so to get this unrooted and back to factory default, and Rooted the right way, with I545ALL-IN-ONE-TOOL??. Please Help
GiZmO-San said:
Need help so lost try to make it as short as possible.
Phone Info:
- Samsung Galaxy S4 Verizon
- Model SCH-I545
- Build JSS15J.I545VRUEMK2
- Android 4.3
Ok, I tried Rooting my Phone and I use the Soft Root that was linked by someone on the forums. Gave me SuperUser Icon and used a app that checks to see if its Rooted and said it was. Now tried using some Root app's like GameCih and it tells me I need Root Admin or Root Privileges, something to that nature, and cant use the app. Iv been trying to remove that Soft Root but cant Figure it out. Used Odin3 and redid that .tar file for my Build. All when good and got everything the same as a fresh phone, but booting up still has the Pad Lock Icon and Custom logo on it and SuperU Icon. So I cant seem to unroot it, Tried to use the I545ALL-IN-ONE-TOOL posted on these forums but cant get it to working.
So what I need so to get this unrooted and back to factory default, and Rooted the right way, with I545ALL-IN-ONE-TOOL??. Please Help
Click to expand...
Click to collapse
Did you flash the no wipe tar?...if so use the full wipe tar file...you will lose your app data but it will restore to 100% full unrooted mdk...the all in one will work after that
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
jamesd1085 said:
Did you flash the no wipe tar?...if so use the full wipe tar file...you will lose your app data but it will restore to 100% full unrooted mdk...the all in one will work after that
Click to expand...
Click to collapse
Sorry...I missed that you are on mk2...flash the full stock Odin tar for that version...the all in one package doesn't work on mk2...before flashing stock in Odin try the saferoot for 4.3...it should get you your full root access
jamesd1085 said:
Did you flash the no wipe tar?...if so use the full wipe tar file...you will lose your app data but it will restore to 100% full unrooted mdk...the all in one will work after that
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Sorry...I missed that you are on mk2...flash the full stock Odin tar for that version...the all in one package doesn't work on mk2...before flashing stock in Odin try the saferoot for 4.3...it should get you your full root access
Click to expand...
Click to collapse
That is what I used is the Saferoot, wasnt sure of the name, but just looked it up and thats what i have on my pc. Also I dont know how to flash it.. do I use the same Odin3 program for that? or is there another method.(Also is the Full wipe a different tar file?)
Edit: Ok I got it Flashed and back to stock now is there anything other then SafeRoot? that did not work the first time I tried it.
GiZmO-San said:
That is what I used is the Saferoot, wasnt sure of the name, but just looked it up and thats what i have on my pc. Also I dont know how to flash it.. do I use the same Odin3 program for that? or is there another method.(Also is the Full wipe a different tar file?)
Edit: Ok I got it Flashed and back to stock now is there anything other then SafeRoot? that did not work the first time I tried it.
Click to expand...
Click to collapse
There are a few other methods...but I don't know them...I do know the other methods safety and security was questionable... Hence saferoot was made by trusted devs here...it should work...all the posts I have seen said they got successful root...did you open the supersu app that was installed and allow it to update binaries?... That is a very important step...if you did then make sure if you try this method again you follow each step it tells you...I don't know exactly how the process goes as I'm on4.2.2 and have to use the all in one tool for root...good luck...if it doesn't work hopefully someone who can help will chime in
jamesd1085 said:
There are a few other methods...but I don't know them...I do know the other methods safety and security was questionable... Hence saferoot was made by trusted devs here...it should work...all the posts I have seen said they got successful root...did you open the supersu app that was installed and allow it to update binaries?... That is a very important step...if you did then make sure if you try this method again you follow each step it tells you...I don't know exactly how the process goes as I'm on4.2.2 and have to use the all in one tool for root...good luck...if it doesn't work hopefully someone who can help will chime in
Click to expand...
Click to collapse
Thank you. You have been very helpful. I'll try it again since i know how to flash it back to stock now
If anyone else knows a way please let me know. I just want a clean install and remove all this Verizon bloatware.
(Did it all again and Game Killer still says "root privilege needed" SuperSU is updated even re-download it and reset phone anyone know whats up with this?)
GiZmO-San said:
Thank you. You have been very helpful. I'll try it again since i know how to flash it back to stock now
If anyone else knows a way please let me know. I just want a clean install and remove all this Verizon bloatware.
(Did it all again and Game Killer still says "root privilege needed" SuperSU is updated even re-download it and reset phone anyone know whats up with this?)
Click to expand...
Click to collapse
Anyone else have any info for me?
I need help UN-Rooting Verizon S4
I have a verizon s4 (SCH_1545) I had it rooted about three months ago. But now I need it unrooted so I can send it back to verizon for warranty issues. Can someone please help me do this? I am told that I need to reset the binary counter as well. SMH....
I'm not a computer guy....can someone walk me through this hard procedure please?
hydrashock40 said:
I have a verizon s4 (SCH_1545) I had it rooted about three months ago. But now I need it unrooted so I can send it back to verizon for warranty issues. Can someone please help me do this? I am told that I need to reset the binary counter as well. SMH....
I'm not a computer guy....can someone walk me through this hard procedure please?
Click to expand...
Click to collapse
several threads pertaining to unrooting
hydrashock40 said:
I have a verizon s4 (SCH_1545) I had it rooted about three months ago. But now I need it unrooted so I can send it back to verizon for warranty issues. Can someone please help me do this? I am told that I need to reset the binary counter as well. SMH....
I'm not a computer guy....can someone walk me through this hard procedure please?
Click to expand...
Click to collapse
hydrashock40 why are you stealing my Post. Im still stuck in the same spot. Is saferoot really the only Option that i have?
GiZmO-San said:
hydrashock40 why are you stealing my Post. Im still stuck in the same spot. Is saferoot really the only Option that i have?
Click to expand...
Click to collapse
If you want to go back to clean stock. ..just odin. .
Sent from my SCH-I545 using XDA Premium 4 mobile app
decaturbob said:
If you want to go back to clean stock. ..just odin. .
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No thats not it, I want to get a working Root that I can use GameCih or Gamekiller. What I get is "Root Privileges Needed" when ever I trying to choose a program.
GiZmO-San said:
No thats not it, I want to get a working Root that I can use GameCih or Gamekiller. What I get is "Root Privileges Needed" when ever I trying to choose a program.
Click to expand...
Click to collapse
I think he was replying to the other guy asking how to unroot
GiZmO-San said:
Anyone else have any info for me?
Click to expand...
Click to collapse
Don't use gamekiller or gamecih - apparently they won't work on a SELinux enforcing-mode phone.
k1mu said:
Don't use gamekiller or gamecih - apparently they won't work on a SELinux enforcing-mode phone.
Click to expand...
Click to collapse
Any other suggestions then? also was reading that you need ...something-strap... in order to be able to install custom Roms, is there one that you can direct me to that is just a clean Rom with just Google stuff on it i.e play store, chrome, gmail app etc. Tired of all this Verizon stuff, it just keeps updating and updating, how to ppl live with this lol
GiZmO-San said:
Any other suggestions then? also was reading that you need ...something-strap... in order to be able to install custom Roms, is there one that you can direct me to that is just a clean Rom with just Google stuff on it i.e play store, chrome, gmail app etc. Tired of all this Verizon stuff, it just keeps updating and updating, how to ppl live with this lol
Click to expand...
Click to collapse
Nope, I have no idea what these applications do, but a quick search on the forums basically leads to the conclusion that they're not ready for 4.3.
Given the build you're running, you're stuck with SELinux Enforcing since you can't replace the kernel. You'll need to find something else to do whatever you're trying to do.
GiZmO-San said:
Any other suggestions then? also was reading that you need ...something-strap... in order to be able to install custom Roms, is there one that you can direct me to that is just a clean Rom with just Google stuff on it i.e play store, chrome, gmail app etc. Tired of all this Verizon stuff, it just keeps updating and updating, how to ppl live with this lol
Click to expand...
Click to collapse
there are plenty of threads...here is one that all S4 owners should look at first....surprise u didn't see it, its a sticky
http://forum.xda-developers.com/showthread.php?t=2606501

G3 Update

I just received a Android update in my notification menu. I am rooted and running a custom recovery (twrp). I know I cannot accept the update but I can't swipe it away. Anyone know how I can get the update removed from my notification menu?
Have you tried long pressing on the notification and disabling notifications?
I froze system update in ti backup I didn't have a pending update but I would try that
Is that file under. Com in tb?
jreink01 said:
Is that file under. Com in tb?
Click to expand...
Click to collapse
Here you go
kennwoodkenn said:
Here you go
Click to expand...
Click to collapse
Thanks for the thumbnail. I did find it in TB and froze it but I'm still getting the update notification in my notification pull down.
Did you restart the phone after
that may work
Don't know if this will work or not, but on the Galaxy S3 the way to stop getting nagged about an OTA was to edit build.prop and replace all references to the old ROM with the new one. So you could try making a backup of build.prop, then edit all references to ZV4 and change them to ZV6. Save the file, make sure permissions are set to rw-, r--, r-- (0644), and reboot.
I would strongly suggest making a nandroid backup first.
Here's how I have been doing it:
1. Download Autorun Manager
2. In settings under advanced enable view services
3. Go to Google Services Framework and disable update...see below.
At your own risk if you decide to try it, of course.
Sent from my LGLS990 using XDA Free mobile app
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
If the update has already downloaded. Disabling the OTA still wont get rid the the notification. Easy way to get rid of it is long press it and go to app info. This will take you to Google Play Services. Simply uncheck show notifications and the system update in the pull down notifications will go away.
Just a temporary fix to get it out of the way. I reccommend just downloading a ZV6 rooted rom.
engine95 said:
This is the recommended way. http://forum.xda-developers.com/showthread.php?p=57182591
Click to expand...
Click to collapse
guys I mistakenly installed this update and now my phone is stuck in twrp where can I go to delete it or am I s.o.l please help
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
im0rtalz said:
You will need to use LG Flash tool if you are stuck in TWRP.
LG Flash Tool How to Thread
A youtube video that might help
https://www.youtube.com/watch?v=1WgXuxDbmbc
Click to expand...
Click to collapse
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Try this first before doing the LG Flash
[Fix] Stuck in Custom Recovery
Thanks to acparker posts
randyrampage609 said:
thanks for this I'll have to wait until I'm near a computer or back home right now I'm vacationing in Florida
Click to expand...
Click to collapse
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
FractalSphere said:
Downside: No Phone.
Upside: Nice weather!
From folks here in Chicago - no sympathy! :silly:
Good luck with the phone!
Click to expand...
Click to collapse
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:15 PM ---------- Previous post was at 11:12 PM ----------
randyrampage609 said:
Alls good now used a two command terminal combo from another thread that I'm trying to find
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2916085
Without having to use a computer and lg flash tool
Sent from my LGLS990 using Tapatalk
Lucky you. Good find. Glad you got it sorted. Now you can relax.
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
jreink01 said:
I have a question that I wanted to ask before I go any further. I bought a G3 last week, rooted it and installed twrp recovery, and have done multiple backups.. Had a hardware defect so I had to exchange my phone for another new one. I received a system update just now so I was going to accept the OTA update since its not rooted, completely stock. My questions are will I be able to root and instally twrp after this update and once I install all my apps, and if rooting and installing twrp is successful, can I restore my backup that I did on my other phone, even though its a different phone? Its from the same carrier and same model phone. Thanks for your feedback.
Click to expand...
Click to collapse
Don't take OTA. Root it and TWRP it. Then flash STOCK ROM ZV6 Deodexed or Odexed, then you'll be up to date and keep root with TWRP.

Categories

Resources