Database Develop

[Q] Get rid of update popup?

Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!

daniel178 said:
Hello,
I am using a rooted (stock) G2. I upgraded (via unrooting then re-rooting) to 4.4.2 a while back when it came out. Then, all of a sudden, yesterday, my phone started downloading MUC 6.4.1.5_E02 (which I thought was old by now). Now, it keeps asking me to install it -- which I cannot because, of course, I am rooted. How do I either: (a) just get rid of/disable this update from installing, or (b) should I install it, which would, again, require un-rooting then re-rooting. Is MUC 6.4.1.5_E02 important/cool/necessary? What is it exactly?
My phone is currently using:
Baseband:
VS98024A-M8974A-AAAANAZM-2.0.20046
Kernel:
3.4.0-perf-gdf89a11
[email protected]
Build:
KOT49l.VS98024A
Software ver:
VS98024A
No custom recovery.
Thank you!
Click to expand...
Click to collapse
http://forum.xda-developers.com/verizon-g2/general/how-stop-ota-pop-rooted-device-t2885667

Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?

daniel178 said:
Thanks!
What is the best way to temp un-root? I see an option in SuperSU, but it says "permanent unroot." I want to just temporarily unroot for updating purposes, then go right back. What's the best way to do this?
Click to expand...
Click to collapse
I did not unroot to update and retained root after the update... If you lose root, I heard stump root will root 26a.
Sent from my Xposed G2

my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2

somnambulator said:
my understanding is that if you're rooted with stock recovery then u can take 26a without unrooting, but if you have a custom recovery then you need to flash the updated rom manually or restore stock recovery before taking the ota.
I'm still on 24a tho with no experience with 26a
Sent from Tapatalk using my xposed VZW G2
Click to expand...
Click to collapse
That is correct.

Help! Accidentally clicked on the update button that popped up and have root
I do have my phone rooted, but as stated above, the update software pop up box kept popping up and I accidentally clicked on the update button. My phone went into the twrp backup screen where I was told the only thing I could do was revert back to a previously saved backup. I tried this and now I can't even get my phone to turn on. If I hold the power and volume down buttons at the same time I just get vibration from the phone but the screen doesn't turn on. When I plug the phone in, it displays the LG start up display and nothing else, it will stay on that display even when I unplug then... So the big question, can I save my phone? I had a buddy do the roots am unaware of how to save it. Thanks for the replies in advance.

[Q] Safestrap 3.75 - Unable to display splash screen

I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.

MorningThunder said:
I'm in the process of trying to upgrade my Dynamic Kat 4.3 ROM to the most recent 4.4 version, and saw that I needed to update my Safestrap from 3.71 to 3.75. I downloaded the Safestrap 3.75 apk (as well as made sure I had the most recent Busybox version already installed), and installed it. Everything appeared to install fine with no issues. I rebooted to try to go into Safestrap, but did not get the splash screen with an option to boot in the Safestrap recovery. I noticed on the 3.75 post that not seeing a splash screen is known issue and the suggestion was just to try re-installing the apk. I have since tried uninstalling/reinstalling the 3.75 apk probably about 6-8 times, then I tried uninstalling 3.75 and back-leveling to 3.71... still no splash screen. Then I tried uninstalling and re-installing 3.75.... again, no splash screen. At this point I've uninstalled/reinstalled over 10 times now, and am at a loss as to where to go next. I've spent about an hour looking around on google and in the forum here for people with the same issue but haven't had any real luck. This seems like such a trivial problem that should be able to fixed that I really don't want to have to revert back to Stock through ODIN mode and re-root, re-flash ROM, etc. if at all possible. Is there anything else that can be done to resolve this?
Any help/suggestions would be greatly appreciated.
Click to expand...
Click to collapse
It sounds to me as if you were on JB and tried to use a KK rom through Safestrap. You can't do that because SS doesn't flash the kernel. You can't run a TouchWiz based KitKat rom on a JellyBean kernel. Your only option is to either Odin back to stock JB and use the setup you had been running, or Odin to stock 4.4.2 KitKat after which you can root, install SS 3.75. Only then will you be able to run the latest DynamiKat rom. All this is assuming you're using an AT&T note 3.
Sent from my AT&T Galaxy Note 3 using Tapatalk®
---------- Post added at 02:40 PM ---------- Previous post was at 02:03 PM ----------
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I misread your post thinking you were no longer able to boot at all. If you want to stay on JB, just reinstall SS 3.71. Make sure you're actually installing the recovery and not just the apk. But if you want the latest DynamiKat Kitkat version, you're going to have to upgrade your phone to 4.4.2 first.
Click to expand...
Click to collapse
Thanks for the reply!!
OK, so maybe I misunderstood what it would take to upgrade to KK... The ROM I'm running now is JB and I had thought that I could just download the APK for Safestrap 3.75, and uninstall the 3.71 version I already had, install 3.75, then go into the 3.75 SafeStrap and install my new KK rom.... it sounds like it isn't that simple.
My phone is booting and working just fine right now on the older Dynamic Kat JB rom I've been running, it just doesn't display the splash screen for Safestrap now when I reboot. You mentioned I need to upgrade my phone to 4.4.2 first in order to use SS 3.75 and install a KK rom, and I thought that just installing the 3.75 Safestrap apk did that. What is the process to upgrade the recovery to 4.4.2 if I can't just install the SS 3.75 APK?

I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

andygev35 said:
I could be wrong but I'm pretty sure SS 3.75 only works if you're on 4.4.2. I think you're misunderstanding though. SS doesn't upgrade your phone. You have to upgrade your phone's firmware yourself to 4.4.2. Then you can use SS 3.75 which is COMPATIBLE with 4.4.2.
Click to expand...
Click to collapse
Ahh ok. I do have an AT&T Note 3, and I know I haven't updated the firmware to 4.4.2 yet. Is there a post stickied somewhere with a link and instructions to install the new firmware?

This should lead you in the right direction
http://forum.xda-developers.com/showthread.php?t=2838117
Sent from my AT&T Galaxy Note 3 using Tapatalk®

Right on. Thank you for help sir!

You're welcome.
Sent from my AT&T Galaxy Note 3 using Tapatalk®

[Q] Enryption fails on rooted S5 mini (G800F)?

Hi there,
Just got a new S5 mini (SM-G800F) today. I've updated to latest Android version (4.4.2). I did not install any custom ROM. Build ID was KOT49H.G800FFXXU1ANJ1.
I've then rooted the phone successfully with CF-Auto-Root (http://autoroot.chainfire.eu/) and Odin. The closest file I found was KOT49H.G800FXXU1ANH2. ANJ1 to ANH2 looks like a "downgrade"... perhaps this is the issue? But read on..
I then started to install corporate access (Exchange account). Our corporation wants to have the device encrypted so I started to do that.
What basically happens is that the encryption droid symbol shows on the screen for about 20 minutes and after that the device reboots.
Yet, no encryption has happened! (is the anywhere a logfile I can look at for more info?)
I have a Samsung Galaxy S3 with 4.1.2, stock ROM as well and rooted with CF-Auto-Root. On that device the encryption process was more verbose and worked fine (although slowed down the phone considerably during normal usage).
So, does rooting the S5 mini with Autoroot break the encryption process? How can I encrypt the phone? Do I have to go back to pure unrooted stock, encrypt first and root later?
Thanks for any insights.
Dan

I still do not know why encryption would not work, but I found a workaround:
I reset the phone to the latest stock firmware with the help of Kies 3. I got G800FFXXU1ANG7. Obviously I lost all data, but that is ok since its a brand new phone.
Started the phone and configured WLAN to accept and install pending OTA upgrade. Just to get to the very latest release at the moment (G800FFXXU1ANJ2).
Encrypted device. I installed the corporate access tools which required the encryption...
Then I installed latest TWRP for my device with ODIN.
Last step was to install SuperSu with TWRP, using the zip file from chainfire.
Some remarks:
- I am not sure why encryption fails while the phone is rooted. Perhaps someone could explain to me?
- If I use CF-Autoroot after encryption of the device, the phone would go into a boot loop, i.e. not asking for the decrypt password and fall back to the boot logo. I thought that encryption would only touch /data. Most likely there is something that initiates decryption during boot, which is replaced by the CF-Autoroot image.
- OTA updates are not possible anymore after installing TWRP recovery (the phone complains that there are changes to the stock ROM). However, if I re-flashed with a stock recovery, OTA was not complaining anymore. If an update would actually work, I have not checked.
- If SuperSu is already installed however, even TWRP re-flashing with stock recovery would not make OTA work again. I would assume that the OTA update routine checks several components to decide if there is stock installed. Temporarily disabling SuperSu did not work, un-rooting through the SuperSu menu left me with SuperSu hanging for an hour until I switched the phone off. I also tried the OTA survival mode (I have SuperSU Pro) and it does not work either (in that try I left out step 2 above).
So for now I have a rooted S5 mini on Android 4.4.2 with encryption and I am happy. I did live without OTA with my S3 (which still is on 4.1.2) since I rooted it and frankly, I did not really miss 4.3...
Regards
Dan

If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!

User_99 said:
If you change some files (like Recoery or rooting) OTA won't work anymore on any Samsung Rom...only pure Stock!
Click to expand...
Click to collapse
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - Do we know what the OTA process is checking to decide if it can go ahead or stall? SuperSu's OTA survival surely knows a bit more on that.. but unfortunately it still won't work..

Mahesh Senghani here please help me. Long time trying but not properly Root Access not properly configured or was not granted. Please sir how to fix this problem deeply request to you please solution easiest explain to me

Mahesh Senghani
Please help me you send Email [email protected]
How to fix this problem

grokit said:
Thanks. That is what I thought.
1 - Encryption fails if the phone (S5 mini, 4.4.2) is rooted. Why? However, encrypting a rooted S3 (4.1.2 stock) did work fine. Was there anything changed with the newer Android versions?
2 - ..
Click to expand...
Click to collapse
Hey, please read about KNOX, hope you may get your answer...

[Q] Easy way to remove Safestrap and root ?

I rooted my phone a while back (Note 3) and have Safestrap on it. I checked with root verify and it says it is rooted.
I want to be able to do OTA updates as I don't really want to be rooted any longer or have safestrap on my phone.
Is there a EASY way to remove both/all of it so I no longer get the safestrap screen when it comes on that has the unlocked symbol at the bottom of it. And no longer have a rooted phone ?
Easy way, preferred as I stated before..

Saw this and giving it a try ! ?
http://forum.xda-developers.com/note-3-att/help/4-4-4-ota-failed-27-t2949069

Well used Super Su, it says I am no longer rooted. But safestrap still shows on start up
And after I did that I checked for a update. It shows v4.2.2 and no available updates ? WTH.... It showed a update before...

Idk either I unrooted and uninstalled safestrap and factory reset my update trys 2times both times says updated failed

is safestrap realy there. i had the same problem and installed traingle away and it removed the safestrap screen.

To Un-root your phone
You'll need to use Odin. After using Odin it will still say custom after the first boot, just re-boot and you'll be good.

I used Super SU, and unrooted. Did check and it says I am not rooted.
But I think the reason it is failing to install 4.4.4 OTA update, is that the safestrap is interfering with the installation..
So if I want to get safestrap completely off of my phone how do I do that > I have been searching the forum, and still searching,,,

Trying to find Stock Recovery Files for the SM-N900A 4.v if possible.
Then I can install via odin ?

Thanks..
Is back to full stock,but I can't update for 14 more hours.
Wish there was a way to push the update..

Spidious said:
Thanks..
Is back to full stock,but I can't update for 14 more hours.
Wish there was a way to push the update..
Click to expand...
Click to collapse
Turn your network time off and switch it to the next day and it shoukd allow you to update again
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
---------- Post added at 03:35 AM ---------- Previous post was at 03:32 AM ----------
Spidious said:
I rooted my phone a while back (Note 3) and have Safestrap on it. I checked with root verify and it says it is rooted.
I want to be able to do OTA updates as I don't really want to be rooted any longer or have safestrap on my phone.
Is there a EASY way to remove both/all of it so I no longer get the safestrap screen when it comes on that has the unlocked symbol at the bottom of it. And no longer have a rooted phone ?
Easy way, preferred as I stated before..
Click to expand...
Click to collapse
Lol you might as well not be on xda if you going to go stock with no root. 4.4.4 OTA official is like a death sentence right now. And you will be hitting your forhead wishing you didnt do that later.
But to answer your question, just uninstall safestrap from the app, and use supersu for full unroot. Or just Odin back with NC2 tar files from the threads. Odin back to NC2 should be no problems with the OTA
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

Well when I had my other Samsung phone I use to install updates all the time, different roms or what ever.
But now I just want to be stock, and knew all the people on this forum do it a lot. So this is where I asked for help...
It is on 4.4.2 and says now that no update is available ? I have already tried the date change trick ! Strange I can't get a update now...Wonder why ?

Now it says I can check again in 735 hours ?

Spidious said:
Now it says I can check again in 735 hours ?
Click to expand...
Click to collapse
That is kinda weird in SuperSU did you disable OTA updates?!? But y you want stock 4.4.4 rom, as AT&T note 3 users there may not b a root or boot rom walk around for long time maybe even tell lollipop 5.0 or maybe never cause note 3 has been dead silence since 4.4.4 released almost like people stop using this device an goin to the note 4... Hopefully there will b a note 3 bootloader exploit for AT&T an verizon but idk again looks like main force is note 4

Well not sure how to fix it.
I have unrooted, removed safestrap.
Checked with root app and it says it is not rooted.
But it still won't update.
Took to AT&T tech center after on-line help from them didn't help. He was not able to update it. So I went to Bestbuys Samsung tech section. They hooked it up to their Smart update software, and it would not allow to be updated either. They said it was either rooted or had a foreign version of software on it. Or one of the software apps I had installed was messing it up.
So I again did a hard reset all the way back to stock ? And after setting up as a new phone I did a check for update 4.4.2 was on it and it said no update available......
SO WHAT IS GOING ON ? Is there a 4.4.4v that I can install with the odin, so that hopefully I can get over this bump..,, ?

Help with Rooting a Note 8

Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?

skatlyup said:
Hi all.
So it's been a while that I've rooted a phone (Note 4 years ago).
Getting a refurbished Note 8 very soon (UK).
I just want to root it and install only what's needed, without applying custom roms etc.
Just need it rooted for Titanium Backup, modded Google Play. Stuff like that.
Hope someone can help me in how I should go about it.
Also should I update the phone to 9.0 as soon as I boot it up?
Thanks.
Edit: Got the phone now. It took me to the home screen when first booted up. Looks like already updated to version 9. Does rooting still trigger KNOX?
Click to expand...
Click to collapse
Yes rooting will trip Knox.
To flash TWRP just follow the steps in this thread - https://forum.xda-developers.com/t/recovery-official-3-3-1-x-twrp-for-galaxy-note8-exynos.3832962/ (just use the latest TWRP which is 3.5 I believe)
If you're just going to root stock filmware you will need to flash RMM/KG bypass or you will get locked out of your phone (only official filmware can be flashed error, then you will have to flash stock to fix it) - https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
If you are going to flash a custom rom they have the RMM state prepatched so this step would not be necessary. To flash a custom rom just follow the steps laid out in the OP of the rom you want to use.