How to survive the OTA - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

Here's what worked for me:
Go into SuperSU
Disable SuperSU
Enable Survival Mode (pro version) (dunno if disabling SuperSU has any effect on this)
Uninstall Xposed Framework (if you have it installed)
Reboot (if you've uninstalled Xposed)
Download the OTA
Install the OTA
Upon reboot, re-enable SuperSU and disable survival mode
Reinstall Xposed
Profit
I even had some KitKat apps installed and the new Play Store. In reading others' accounts where it didn't work, something that seems to be missing is disabling SuperSU altogether. Good luck to everyone.

jimbosi said:
Here's what worked for me:
Go into SuperSU
Disable SuperSU
Enable Survival Mode (pro version) (dunno if disabling SuperSU has any effect on this)
Uninstall Xposed Framework (if you have it installed)
Reboot (if you've uninstalled Xposed)
Download the OTA
Install the OTA
Upon reboot, re-enable SuperSU and disable survival mode
Reinstall Xposed
Profit
I even had some KitKat apps installed and the new Play Store. In reading others' accounts where it didn't work, something that seems to be missing is disabling SuperSU altogether. Good luck to everyone.
Click to expand...
Click to collapse
I thought I remembered how to do this from the last update, but I forgot the frigging survival mode.
So now I am trying to figure out how to get re-rooted.

Have they fixed the transition animation scale bug yet? That's literally the only reason why I would even bother updating from stock.
Also, OP, when you uninstall xposed, I'm assuming it obv reverses all installed mods. What I'm wondering is, are all the modules and settings and everything set up within xposed retained when you reinstall it, or did you have to start fresh?

I've read using Kingo can work. Never used it, even from beginning with root de la vega. I guess give Kingo a shot. Good luck.

I'm thinking I would still have some issues since I've used lucky patcher to disable all ads directly, on the app level. Maybe I'd have to reverse that first then uninstall lucky patcher. Ugh.

siciliano777 said:
I'm thinking I would still have some issues since I've used lucky patcher to disable all ads directly, on the app level. Maybe I'd have to reverse that first then uninstall lucky patcher. Ugh.
Click to expand...
Click to collapse
Just used Kingo and everything worked fine. Uninstalling it from my PC now though..

jimbosi said:
Here's what worked for me:
Go into SuperSU
Disable SuperSU
Enable Survival Mode (pro version) (dunno if disabling SuperSU has any effect on this)
Uninstall Xposed Framework (if you have it installed)
Reboot (if you've uninstalled Xposed)
Download the OTA
Install the OTA
Upon reboot, re-enable SuperSU and disable survival mode
Reinstall Xposed
Profit
I even had some KitKat apps installed and the new Play Store. In reading others' accounts where it didn't work, something that seems to be missing is disabling SuperSU altogether. Good luck to everyone.
Click to expand...
Click to collapse
Did the same on mine a few days ago and working great. I didn't uninstall XF though, just disabled all of the modules prior to downloading the OTA. I also disabled SuperSU in SuperSU Pro when enabling survival mode. Don't think survival mode is available in regular SuperSU, but correct me if I'm wrong.

I followed your steps and it still errored. I have no processes running in Wanam framework, su is disabled and survival is on. Not sure why it errors. I see it try to boot into recovery for the update then it shows the android guy installing updates and then the android guy is on his back and says error. Then it restarts the phone. I wonder if safestrap is my issue. Any ideas?
MJC

Chillout2010 said:
I followed your steps and it still errored. I have no processes running in Wanam framework, su is disabled and survival is on. Not sure why it errors. I see it try to boot into recovery for the update then it shows the android guy installing updates and then the android guy is on his back and says error. Then it restarts the phone. I wonder if safestrap is my issue. Any ideas?
MJC
Click to expand...
Click to collapse
I was having this exact same problem. I downloaded the original MJ7 file again. Disable supersu and put my phone into BOOT MODE. ODIN in the MJ7 again and then took OTA update. After that was all done I used kingo to reroot. Everything went fine and kept all my settings. Didn't have to reinstall a single app.
Sent from my SM-N900V using Tapatalk

Lol. I did all this. Then I used kies to update. Worked but lost root... Survival mode didn't stick. Lesson learned. I'll try kingo again.
Edit: kingo worked, backed to rooted on mje. Anybody have a link to the newest su as kingo installed su. Then su asked to update which I did. The play store says my su pro 1.80 is up to date.
MJC

Stock mj7 firmware
Hi there,
The update's failing, so I guess I need to install the stock rom from ODIN. Where can I download the stock rom without giving my credit card number? I've only found one link, and they want a credit card. I won't give out my CC.
Thanks
... Nevermind, Apparently it did start downloading. I don't remember clicking ok for the download. I must be getting in a hurry...

Related

[Q] SuperSU hidden/half enabled

I am running Nexus 7 with 4.2.1 build JOP40D.
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
[edit]
When installing busybox it checks and says you should see the reply
system/xbin/busybox
but the reply I get is
system/bin/busybox
Is this a problem?
DazFromTaz said:
I am running Nexus 7 with 4.2.1 build JOP40D
After I got the 4.2.1 OTA update I noticed root was no longer working.
I went into Settings and Apps and disabled it and tried using SuperUser but discovered that it didn't work with 4.2.1
I used the Google Nexus_7_ToolKit_v4.0.0 and ran the root command choosing SuperSU which was the correct one for 4.2.1.
It did a cleanup of any other root stuff and successfully pushed root to the device.
It did not show up in the App Drawer, but does show up in Settings, Apps, All.
I tried again by sideloading via CWM recovery but there was no difference.
I then ran the toolkit to remove root, busybox, etc, then attempted to reinstall them both again.
I am still stuck with the same problem.
When running a root app such as Titanium Backup, it gets stuck at "asking for root rights" and not the 'you need to root your device' message.
Any help?
Click to expand...
Click to collapse
1. you need to flash the su binaries in your recovery, latest su binaries http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
2. or you need to install busybox if you already flashed the binaries. you can find free busybox installer apps in the play store. best one is by stericson.
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
DazFromTaz said:
That's what confuses me. I have flashed the su binaries via recovery and also installed busybox.
Downloaded the busybox from Play Store now though. It can't install with root though.
Remember, SuperSU is showing up in Settings, Apps, All, it just doesn't seem to be usable or showing up in app drawer.
Click to expand...
Click to collapse
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
simms22 said:
delete supersu from either /data/app/ or /system app/, wherever you have it installed. then reboot into recovery and wipe cache and dalvik. after, reboot and reinstall supersu app.
are you sure that you flashed the latest su binaries? if not sure, flash the one that i linked while youre in your recovery.
Click to expand...
Click to collapse
Thankyou again for your response.
I deleted superuser.apk using adb, then cleared the caches. I then rebooted recovery, sideloaded the latest superuser (from the link provided) and then booted into Android.
Same as before. Superuser is not in the app drawer, but can be seen in settings.
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
DazFromTaz said:
Remember when I said I disabled it in Settings, Apps?
Well it turns out that Google remembers this, even when the app is removed and reinstalled. It will not show that it is disabled when you check it in Settings though.
To fix, I disabled again, then enabled it. Boom fixed.
Feel rather sheepish now.
Although you pushed me to learn quite a bit more about adb so thanks for that!
Click to expand...
Click to collapse
no matter how it was "fixed", its still a :victory: congrats
WooooooW!!!!!! Banging my head with this one until I found this thread. Crazy but it worked, after I did all that the OP said he did.. Thanks..

This shouldn't be frustrating - binary update.

I tried a couple of root apps, they didn't work. F***. Adaway and Music2SD. Both tell me that my rooted S4 isn't rooted. I have prerooted MF9, flashed via TWRP. It included SuperSU, with 1.1.3 binary (I think). Okay, after no search results I decided to do something on my own.
First, I opened SuperSU and told it to install itself as a system app. Then, I installed ChainsDD Superuser. That's when I found out my binary was out of date. I chose to update it via Superuser. For some reason or another, it said it didn't update. I went to app manager, cleared data and uninstalled updates for SuperSU. I updated it in the play store and opened it. Then, it told me my binary was out of date - woo! Wait.. normal method didn't work - "Installation Failed!" Okay, try TWRP/CWM method. It rebooted into recovery, flashed some stuff before I could read it, and restarted. Booted right back up. I opened Superuser and it said I was on v0. Went to ChainsDD's site and downloaded the 3.1.3 ARM to flash in recovery. I did that, still nothing. Now SuperSU and Superuser are permanently installed apps (I now have no root to delete them). Whatever. I ran CF-Auto-Root in Odin. After that, both SuperSU and Superuser were removed. I have nothing now.
My question is, what's the best way to get the latest binary on MF9? If i restore from Nandroid, how should I update? If I start from scratch, what binary will I get from CF-Auto-Root?
UPDATE: I'm back to rooted, with SuperSU. I got the update binary notice and chose the normal method. It updated just fine, but I still can't use Adaway or Music2SD. Superuser by ChainsDD still shows v0.. all of my normal apps have root access just fine.
FIX!: My ignorance is to blame here - XPrivacy blocks root access by default on Adaway and Music2SD... I didn't realize it did that!

Update keeps failing?

I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
shizumie said:
I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
Click to expand...
Click to collapse
Any modifications to system will usually cause the update to fail. Xposed and wanam can cause the update to not work. You can download and odin the update and then re-root with kingo. This thread might help http://forum.xda-developers.com/showthread.php?t=2483380
shizumie said:
I looked and didnt see this, so hear goes.
I picked up a note 3 today, it did not have the update installed. I rooted with de le vega, installed safe strap, made backup.
installed xposed installer / then wanem xposed. Then went to security hacks / fake system status to official. Uninstalled Safe Strap. Went into SuperSu and unchecked enable SU / then clicked survival mode.
Go to install update and it fails time after time.
What gives?
Click to expand...
Click to collapse
This is what I did. Rooted phone with Dela Vega. Left stock rom clean no mods, no safe strap , no rooted applications except SuperSu. Disabled SuperSu , enabled survivor mode. Took OTA. Disabled survivor mode enabled SuperSu.
Sent from my SM-N900V using Tapatalk
Thanks guy's.
I had read that after root ota would fail because system showed not stock, and that you had to use Xposed and wanam to change the system to look stock.
I will oden back to mi9 and try again, without doing anything but rooting, and using su to save root.
Thanks again, and ill post back tomorrow my findings.
Ok, So i Odin'd back to mi9, re did (de la vega), after root, updated SU hid and protected it. Took the ota. After OTA re-enabled SU, installed safestrap. and all is well.
Thanks for the help, and direction guys.

[HowTo] Pokemon Go on Rooted Phones (CM13/PaulPizz/Jasmine/Stock)

I know this is all over the place, but I thought I would bring it here just in case anyone hadn't found the answer. I have seen a few posts about this on Reddit and some other forums. This will obviously hinge on having the unlocked bootloader. You will also need a file explorer that lets you view root folders just in case you want to make sure the binaries have been delete.
What worked for CM13:
Install SuperSU and use it's unroot method which should delete all SU binaries in /system/bin and /system/xbin.
Install phh SU and Magisk manager.
Reboot to recovery
Install the Magisk v6 and PHH SU files.
Reboot system after clearing cache
Access Magisk Manager and toggle root, it should prompt PHH SU to ask about permissions.
I have read that this same method works for PaulPizz and Jasmine Rom as well. PaulPizz has Xposed preinstalled, so you have to run the Xposed uninstaller and remove the Xposed app. Follow instructions from the Xposed for Magisk thread to reinstall xposed if you require it.
If you want this with the Stock Verizon image, there is a link in the Stock Image thread on page 41 with the bootloader removed for safe upgrade. I will update the post with links to the appropriate threads later today.
Credit to all the devs involved with the Note 4 and Android in general.
The method you've described worked for me on 0.35 PoGo. Then 0.37 update I already had to rollback.
I'm using HTC One M8, rooted, pph and Magisk on stock Rom, systemless xposed.
Now the forced 0.39 version does not run, leaving me with me 'Failed to log in' text. Please guys, work on some help I put my trust in you
I'm on Paul pizz and when i follow the instructions I can get full unroot, everything flashed, but when I go into Magisk manager I am not prompted for anything and if I hit the toggle for root it just toggles itself back. It appears that even after removing the super.su from system in twrp that I still can't get it to install.
I have also removed Xposed with the uninstaller and tibu to remove the APk. I can get systemless Xposed to install and work but not systemless root.
Any ideas?
NickyNicky44 said:
The method you've described worked for me on 0.35 PoGo. Then 0.37 update I already had to rollback.
I'm using HTC One M8, rooted, pph and Magisk on stock Rom, systemless xposed.
Now the forced 0.39 version does not run, leaving me with me 'Failed to log in' text. Please guys, work on some help I put my trust in you
Click to expand...
Click to collapse
I'd it's still detecting root, the su binaries haven't been removed completely. Also check that magisk toggles off root.
Cauterized said:
I'm on Paul pizz and when i follow the instructions I can get full unroot, everything flashed, but when I go into Magisk manager I am not prompted for anything and if I hit the toggle for root it just toggles itself back. It appears that even after removing the super.su from system in twrp that I still can't get it to install.
I have also removed Xposed with the uninstaller and tibu to remove the APk. I can get systemless Xposed to install and work but not systemless root.
Any ideas?
Click to expand...
Click to collapse
If you have xposed active, it may not allow you to toggle root off. You have to go to system less and deactivate and then reboot. Then turn off root in magisk. It's the only way I found to get it to work.
Anyone figure out how to install magisk on emotion 7.1 I tried and just boots to download mode and says it couldn't boot normal.
aaronmj863 said:
Anyone figure out how to install magisk on emotion 7.1 I tried and just boots to download mode and says it couldn't boot normal.
Click to expand...
Click to collapse
I'm also running emotion 7.1.1 die you ever find a work around of PoGo. I've been trying lit of things but of us it sounds like this magiaksu option is our only option but I can't get it to work either.
chugs said:
I'm also running emotion 7.1.1 die you ever find a work around of PoGo. I've been trying lit of things but of us it sounds like this magiaksu option is our only option but I can't get it to work either.
Click to expand...
Click to collapse
iSu [v3.5] Simple app to deactivate activate
https://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348
I've seen a few posts on people getting iSu to work to get PoGo on our phones. I've tried a few times but no matter what version of Su I have installed o get this respongse.
Does anyone have a verison that is compatible with iSu. Or could provide me some guidance that would be great.

Magisk v11.6 compatible with Droid Turbo Stock ROM

I can confirm that Magisk v11.6 installs and appears to function perfectly on my stock, unrooted, bootloader unlocked MCG24.251-5-5 device. Also, MagiskHide is not enabled by default, so keep this in mind if you're using a work device or any other situation where you might get in trouble for failing safetynet. That's all I know so far.
Go forth and Magisk!!!
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Pics or it didn't happen
And last, but certainly not least...
So I can root without unlocking the bootloader using sunshine?
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
No. Sunshine unlocks your bootloader, so you can then root.
Sparksys said:
So I can root without unlocking the bootloader using sunshine?
Click to expand...
Click to collapse
There will never be a free root for this device unless you develop it, so you can save yourself the time asking in so many different threads.
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Tokogon said:
Can anyone tell me where you get the "magiskSU" app from I can't find it in that thread.
Click to expand...
Click to collapse
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
TheSt33v said:
MagicSU is included with the Magisk package. You can enable or disable it using the Magisk Manager app once it is installed.
Click to expand...
Click to collapse
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Tokogon said:
Do you have a screenshot of where I can find it in settings? I've been searching for an hour and I've reset my phone twice and installed it but can't see it lol.
I want to play Pokemon Go so bad again.
Click to expand...
Click to collapse
Sorry, I was wrong about being able to disable it. There doesn't seem to be an option for that. But as long as Magisk Hide is enabled, Pokémon Go works fine for me.
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
y8s said:
More complicated question:
If I'm rooted via Computerfreek's debloated stock ROM, is there any point to running Magisk--and if so, how would I switch from SuperSU to MagicSU
Click to expand...
Click to collapse
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
TheSt33v said:
The only advantage gained would be the ability to pass safetynet/use Android Pay/play pokemon go while rooted. To switch, uninstall SuperSU by selecting the full unroot option in the SuperSU app, then flash Magisk.
Click to expand...
Click to collapse
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
y8s said:
It's mostly for intellectual curiosity and maybe android pay.
But it didn't work--at least how I went about it.
I went into SuperSU and did a full unroot but did not restore the boot image (should I have?)
Then downloaded and flashed the latest 11.6 magisk
When the phone came back up, SU was gone but Magisk didn't re-root it. There were no options to do so.
Tried a second time and wiped caches but no change.
I'm going to go out on a limb and guess that Magisk needs the OG boot image to work properly?
Click to expand...
Click to collapse
I installed it on stock MCG24.251-5-5 and Superuser is an option that appears in Magisk Manager. Yes, you should probably have the stock boot image before installing Magisk. I think the Magisk installer is designed to detect existing installations of SuperSU and not install its own superuser if it's detected, so if the full unroot didn't clean itself up properly for whatever reason, that might be why it didn't install with superuser.
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Is that correct or should I use another kernel version? I don't want another bootloop or damaged wifi^^
Einheit-101 said:
It says:
...
-(Recommended) Restore your boot image back to stock
-Download the latest Magisk zip file
-If you choose to use SuperSU (only support Android 6.0+), first flash SuperSU in systemless mode
...
Which zip of super su should I flash therefore before flashing magisk zip?
I am currently, after restoring a backup, running your MGC stock with stock kernel, but I try installing bhb27s kernel now.
Ultimately I simply want to hide root+xPosed against my banking app...
€DIT: Wait, so SuperSUB may not be necessary, but is it safe to install magisk over bhb27s kernel?
I would do the following:
-Install newest v44 kernel from March, 12
-Reboot and look if Wi-Fi still works ...
-install Magisk 11.6
-Check if phone still works
-then install a working xposed
-Check if everything works
Click to expand...
Click to collapse
I don't see any problems with that plan, but you should know that xposed will insta-fail safetynet. If you want to hide modifications from anything that uses safetynet, xposed in any form is not an option. The only thing that works for me is Magisk 11.6's built in root, no xposed, no other modifications. With that, I can use Android Pay, Pokemon Go and my banking apps just fine as long as Magisk Hide is turned on. Android Pay and PoGo are blocked by default, but you need to make sure to go in and manually check the box next to every other app that you want to hide stuff from.
Also, if you insist on using SuperSU instead of the built in Magisk root (why???), you will also have to install the latest version of suhide (and I'm not positive that works anymore).
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
I just haven't had time to dig up another boot.img and flash it. I might revert back to SuperSU and come back to this later.
Einheit-101 said:
.I did not exactly know Super SU is just an option so I will not install it. Wish me luck
Also I hope there will be a way to hide xPosed however my banking app does not use SafetyNet, there is still hope, I don't care about Pokemon Go.
€DIT::: Everything working perfect - however safetynet fails when checking with Magisks own test. I guess it detects the Bootloader?
€DIT2::: Now after another reboot safetynet is successfully bypassed. My banking app still doesn't work - looks like they found a way that is even better than safetynet.
Click to expand...
Click to collapse
Try clearing the data for your banking app. Maybe it's set up so that once it fails, it never checks again. Also, clear cache/dalvik cache in TWRP if you haven't already. Also also, did you remember to block the banking app in magisk hide?

Categories

Resources