Database Users

[Q] Help! Think I missed my 4.1.2 update!

I have a rooted Nexus 7.
Got the notification to do an OTA system update, so I did. My recovery is CWM (touch version); when I got into that and it asked if I wanted to install the unsecure package, I accidentally chose no and went into the main recovery menu. I wasn't sure where to look for the update again, so I chose to reboot.
Now when I go to Settings > About tablet, I'm still on 4.1.1. If I select System update, it says my system is up to date
I currently don't have a PC available to flash a downloaded 4.1.2 (and I'm worried I'll lose root - I specially installed the OTA RootKeeper app for the purpose of updating via OTA). Is there any way to get 4.1.2 again?

No worries. I had a failure installing the OTA because I had renamed the browserproviderproxy files so I could side-load the gnex browser that works with flash. After renaming the files back, I was also getting the system up to date message and no update. I checked the /cache folder and found the update. I copied it to the root folder, rebooted into cwm recovery and installed the zip. I responded to a prompt that I wanted to keep my recovery, not flash stock recovery on reboot, and another prompt that I chose to try and keep root. After rebooting, I still had root and I could still reboot into recovery (cwm) from Rom Manager.

Even if you can't find it in your cache, your ota update will come back in time.

Groid said:
No worries. I had a failure installing the OTA because I had renamed the browserproviderproxy files so I could side-load the gnex browser that works with flash. After renaming the files back, I was also getting the system up to date message and no update. I checked the /cache folder and found the update. I copied it to the root folder, rebooted into cwm recovery and installed the zip. I responded to a prompt that I wanted to keep my recovery, not flash stock recovery on reboot, and another prompt that I chose to try and keep root. After rebooting, I still had root and I could still reboot into recovery (cwm) from Rom Manager.
Click to expand...
Click to collapse
Thanks so much! I followed the steps you outlined, which were exactly as you described. And now I have 4.1.2 and kept root!
Looks like updating via CWM recovery would've maintained root. So I needn't have installed OTA RootKeeper after all.

Logic_ said:
Even if you can't find it in your cache, your ota update will come back in time.
Click to expand...
Click to collapse
I was thinking the same, but after reading all the posts in the "4.1.2 is here" thread about the update failing for rooted users, I got quite jumpy and wanted to check mine asap. Just couldn't wait! Lol

[Q] Updated to 4.2.2 and lost my custom recovery

I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.

moose&beer said:
I updated to 4.2.2 the other day, and it appeared that I lost both root and my custom recovery (TWRP), but my bootloader remained unlocked. Root-specific actions wouldn't work (e.g., TB wouldn't work, no access to root in Solid Explorer or Root Explorer, AdAway stopped working, etc.). This was despite having survival mode activated in SuperSu. I also learned I couldn't boot into recovery when I tried to restore a nandroid I made prior to updating.
Somehow though, root reappeared and everything works as normal, except I still cannot boot into recovery.
Any clue why my custom recovery disappeared permanently but root was preserved (albeit, root not preserved at first, but it DID end up coming back)? Also, can I just re-flash TWRP as I normally would?
Thanks.
Click to expand...
Click to collapse
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.

sfobrien said:
Strange first I've heard of that with the N10. I would try to reinstall TWRP with Goomanager.
Click to expand...
Click to collapse
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.

I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.

sfobrien said:
I might have misunderstood, did you guys do the OTA? Got my forums mixed up thought we were talking about flashing CleanROM.
Click to expand...
Click to collapse
No worries. And yeah, I did the OTA, but held off until Google pushed a notification to my N10 for the update. I'll give goomanager a try. Appreciate the replies. Thanks.

This is normal behaviour in a OTA update. Installs a couple of files that, if a custom recovery is installed, reflash stock recovery on reboot. This doesn't happen if you flash a factory image.
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app

three west said:
mine did the same, as mentioned above I just re-installed TWRP with goomanager and everything is back to normal.
Click to expand...
Click to collapse
Thanks - I'll give goomanager a try.

beekay201 said:
A bit off topic but, there was the need to have device at stock condition (everything stock) before running OTA process, but as of now and personal experience, twrp 2.4.1.0 can also run an OTA update straight from Android.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
I assumed the same, but I got the same situation as OP, I'll try reinstalling TWRP using Nexus Root Toolkit, or does goomanager have a special functionality for those conditions?
Update: Used NRT to install TWRP in the advanced settings, worked beautifully.

The latest Google OTA's are not successfully installing unless you restore stock recovery fist and some are failing if you are rooted as well.
Best bet if you are running as rooted or custom recovery is to backup first, un-root, restore stock then sideload the OTA. This will save you lots of frustration and heartburn.
It's easy enough to restore stock and to re-root so just make it part of your ota routine.

[Q] Kitkat 4.4 OTA Update failed to install

Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.

No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
LORD MJ said:
Hello, I'm in a bit of a confusing situation so I hope that someone can shed light on it.
Last night I got a notification that my phone is ready to install the 4.4 update. I didn't have the time or the battery to install it then, so I just left my phone until today. Today, I happily pressed the update button, my phone restarted, it started to update and when the bar was a little more then a third full it stopped and said "Error!" (Thanks for a very informative error message Google! ) I restarted my phone, and now my phone reports that it's up to date?! I tried tapping the Check now, but it keeps saying it's up to date. I checked my cache folder, and there is a .zip file containing the update.
My phone is rooted, I used the Nexus 4 Rootkit, but I DIDN'T install a custom recovery or try to install any custom ROMs. (I'm happy with the stock one) I only installed SuperSU so I can grant root access to some apps and that's it. I didn't install any tweaks.
Now if I'm not mistaken, the OTA update should have worked on my phone, because everything is stock. So why did this happen and why I'm not receiving the update prompt again?
Also as a side note: When I went into the fastboot mode and tried to launch the Recovery mode, it said "No command!" and I had restart my phone.
Click to expand...
Click to collapse

nyepo said:
No, you're wrong. You should've gone to SuperSU app and pressed the "full unroot" button before trying to OTAupdate. This would've replaced the modified bin files for root by the original files, allowing the OTA to be applied successfully.
This happens because the rooting process modifies some system files, so the OTA detects a non-stock scenario and aborts its installation. Also when the OTA fails, a flag marks this update as a "fail update" so your system will continue to show you that it's "updated" as he thinks the only update available isn't suitable for you. He is just waiting for the next OTA update.
Now you have to install the OTA via sideload / adb. I would recommend to make a full nandroid backup before everything else. Then fully unroot your phone and apply the OTA using adb.
This is exactly what happened to me when trying to update from 4.2.2 to 4.3. I was root (obtained with Nexus 4 Toolkit from WugFresh) with stock recovery. Just root, nothing else. Then I tried to install OTA, because with older versions to be root was not a problem. But now it is, and my OTA failed as it failed to you.
Then I managed to manually apply the OTA doing what I told you: first backup, then unroot, and finally using the sideload / adb process button present in the toolkit, following its advices at each pont (very VERY well explained for non-experts). You will need to manually download the OTA update to 4.4. Look for that in these forums.
Hope this helps!
Click to expand...
Click to collapse
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.

LORD MJ said:
Thanks. Unfortunetly the OTA update failed even when I tired ADB sideload, so I had to flash the factory image. Now it works like a charm.
Click to expand...
Click to collapse
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.

I did a "flash stock+unroot" and relocked my device via the Wug app and it still errors

eksasol said:
It failed because you have modified files in your system, such as modified gps.conf or build.prop, custom kernel and non-official radio will give errors too.
Click to expand...
Click to collapse
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.

LORD MJ said:
I really have no idea how did that happen. Maybe some app modified it or I messed some things up. I'm now going to make a full backup of my phone, so I can apply the next OTA with much less pain.
Click to expand...
Click to collapse
The OTA update can fail for many reasons, it could be due to any changes to the /system partition which is what root does, such as changes to gps.conf file, changes in build.prop, different kernel or radio.
If you're going to make a full backup, what you should do is flash a full factory image (link in my signature, and provided you already backup your data.) Then boot into a custom recovery to make a full backup, (not flash the recovery, but: fastboot boot twrp.img) When you do the backup make sure the boot (kernel) and recovery partition are selected. However, you can't backup the radio partition, but that should be fine unless you intend to use the LTE radio.

I have a similar problem. I have ROOTED device with TWRP recovery and stock 4.3 android (obtained OTA before rooting), and I just got notification that my OTA update to 4.4 is ready to be installed.
So I clicked Restart and Install button and the phone restarts(as it should) but after that it went in TWRP recovery and waited for some instruction I suppose. I didn't know what to click exactly, so I clicked Reboot from TWPR menu and it went in fastboot mode. From fastboot I chose Start and phone turns on. Updating didn't even start..
So, were there something that I could do when I was in TWRP recovery that could initiate updating process, or I never had a chance?
What exactly I should do to get that update on my phone? Sorry for my English and if was unclear.

[VK810] Official Kit Kat Update Information

We're all in the process of receiving and installing this update, and there are many questions about recoveries, rooting, etc. This is a thread to gather all the info we know so people don't have to be searching through tons of posts.
(I'm in the process of installing now, so I'll answer as many of these questions as I can. I will also update the OP with info from other users. If anything I state is untrue, please post and let me know.)
Can I take the update while rooted?
Yes! If you are on 4.2 and rooted but on STOCK RECOVERY, you can take the OTA and keep root.
Can I take the update with TWRP installed?
No! You will bootloop into recovery.
Is there an alternative/manual/TWRP method of installing?
Yes, see below post.
How am I supposed to update if I installed TWRP?
See below post, "README if you are currently on JB4.2.2"
Alternative method: "download flashify from the play store, backup twrp, then flash the recovery.img from OP. No pc needed & 100% pain free." Thank you to 86shelby. Then take the OTA.
Can I root the 4.4 version?
As of 8/26, yes! Stumproot works with the Bruteforce method. http://forum.xda-developers.com/show....php?t=2850906
Can I downgrade from 4.4 to 4.2?
Yes
If anyone else has questions they'd like posted, please let me know, and I'll put them in.

NOTE: If you want root/twrp in KK4.4.2, you'll need to pre-root in JB4.2.2 before OTA update(towelroot works in JB4.2.2, but not in KK4.4.2)
Looks like Stumproot works with KK4.4.2
README if you have a non-booting device
If you tried OTA update with TWRP recovery and get stuck in a bootloop for TWRP
Do one of the options below:
A) If you still want 4.4.2 via Verizon OTA, flash stock recovery
Go into TWRP, restore stock recovery via link below
http://forum.xda-developers.com/showpost.php?p=52975059&postcount=65
B) If you want to stop the bootloop, and flash 4.4.2 via TWRP backup from below...
Go into TWRP, wipe OTA partition (which signals the device to keep going into recovery)
http://forum.xda-developers.com/showthread.php?p=51749086#post51749086
Click to expand...
Click to collapse
If I mess everything up and device doesn't boot
Restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)​
README if you are currently on JB4.2.2
If you already have TWRP, you can flash 4.4.2 via the TWRP backup below (probably can just flash over 4.2.2 without factory reset... do factory reset only if something goes wrong)
http://forum.xda-developers.com/showthread.php?p=53043541#post53043541
If you want to apply update via Verizon OTA, READ below first
If you have TWRP installed, you'll need to flash stock recovery. Either (A)
restore stock recovery only, or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
NOTE: some people have problems with OTA even after restoring stock recovery. You'll have to restore using the (B) method, and lose everything
[*]If you want root in 4.4.2, you'll need to apply root BEFORE OTA (via towelroot, ...?). root is allowed during OTA, will be maintained after OTALooks like stumproot works
Apply OTA, hope nothing goes wrong
Yay!
Click to expand...
Click to collapse
README if you are currently on KK4.4.2
Splitwindow/multiwindow on 4.4.2
http://forum.xda-developers.com/lg-...10-splitwindow-multiwindow-stock-4-4-t2837326
Root on 4.4.2: Use Stumproot
TWRP on 4.4.2
Root ? (Towelroot isn't working though)
Flash 4.2.2 aboot.img and TWRP.img
A) Upload aboot.img from 4.2.2 to device, then do
Code:
adb shell
su
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
B) Follow steps in TWRP thread to install TWRP
Click to expand...
Click to collapse
4G LTE does not work on 4.4.2?
Flash modem from 4.2.2 -> http://forum.xda-developers.com/showpost.php?p=54584896&postcount=5
Going from 4.4.2 back to 4.2.2
Install TWRP (see section above)
Get 4.2.2 TWRP backup from here and restore
or restore (B) the entire device back to 4.2.2 using the kdz file(more complicated and you lose all your settings/files/apps)
Click to expand...
Click to collapse
​

Guess I got lucky - never got around to installing the custom recovery. I MEANT to do that....

https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot

So this is what I get when I check for update. I'm stock unrooted I even did a FDR. Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my XT1080 using Tapatalk

Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.

modus81 said:
Towelroot doesn't work yet with the new update. I took the update completely stock and unrooted and I'm not able to root now.
Click to expand...
Click to collapse
have you tried other root methods?
ioroot, or this root below? (
http://forum.xda-developers.com/showthread.php?t=1886460&highlight=4+2+2

paperWastage said:
https://pvzwmdmcdn.vzw.motive.com/firmware/LG_VK810_11A_TO_22B.bin
in case you want to poke around
Verizon LG G2 users say it's okay to be rooted, just need stock recovery for OTA update... let's see what happens..
yeah, 0x136 error when it tries to update. people say 0x136/0x13E errors are because of unlocked bootloaders... i guess we need to flash completely stock via KDZ file, then take ota, then use stuff like towelroot
Click to expand...
Click to collapse
How do I install this?
Sent from my VK810 4G using Tapatalk

gfullwr70 said:
How do I install this?
Sent from my VK810 4G using Tapatalk
Click to expand...
Click to collapse
you don't. go through Settings-> System update

paperWastage said:
you don't. go through Settings-> System update
Click to expand...
Click to collapse
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk

gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Same here

Flashing comletely stock via .kdz file
I'm getting the 0X13E error. Does anyone have the the process for this? I saw a different thread that directed to a droidreviews.com website but one of the files it said to download, my Chrome browser scanned as malicious so I stopped pursuing that route.

ssinn said:
Same here
Click to expand...
Click to collapse
gfullwr70 said:
Ok thanks. Check my above post and pic. I get that everyone I try there check for update.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
Thanks this is what I was looking for. I'll give it till tonight to see if the ota shows up then I'll try this method.
Sent from my XT1080 using Tapatalk

paperWastage said:
you could try forcing the update (manually place the file and the start the apk)
see if the steps below can help you
http://forum.xda-developers.com/showthread.php?t=2699123
Click to expand...
Click to collapse
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?

prana22 said:
So is this only if you can't download the ota update or if you get an error while trying to install it after downloading it?
Click to expand...
Click to collapse
first one.... my tablet wasn't able to find an OTA on 4G LTE (on t-mobile's network), but wifi works fine

Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
That's interesting, and good to know. Can anyone else verify this? I didn't think the update would go through if you were rooted. Now I might downgrade through kdz again and root before I take the OTA.

rjkmadison said:
Mine prompted me yesterday and I was not sure I wanted to yet (wait for other victims...). It would only let me delay it up to 24 hours, so it was going to annoy me. I let it update today and it looks fine. I did not unlock or change my recovery, but had used towelroot to gain root.
After update, it appears that root is still there.
The only glitch I have noticed is that my Mobile Hotspot (wifi name/pass) were reset to defaults.
Click to expand...
Click to collapse
go flash TWRP, make backup of stock and share it please?

How can I revert to stock recovery in OSX? All I see is the LG Mobile tool for windows?

Pokemon GO 0.37 - Custom ROM issue.

Hey folks! I am on a T-Mobile Galaxy Note 3, running a S7 Edge port by Dominion. And of course, Pokemon GO 0.37 is throwing the stupid compatibility error message.
Now, before you suggest it, I am already aware of the Magisk solution for rooted phones. In fact I used that exact method to get the app to work on my wife's rooted Note 4.
However, there seems to be more going on with Pokemon GO this ROM than just the root. I was able to unroot this ROM and get Magisk running. The root was fully toggleable, and when root is off, all apps that require root could not get access. So I know Magisk is working properly. However, Pokemon GO still wouldn't run, and when I ran a check for SafetyNet, my phone failed to pass the last check with the error "CTS Profile Mismatch".
I already checked the system/bin and /xbin for leftover SU files, too, and there's nothing there. Now I do know this ROM comes pre-rooted and it has a permissive kernel that checks for root status (TWRP prompts me to install SuperSU whenever I boot into it). I am guessing that may have something to do with it, but... what can I do about it?

anything modifying the system will prompt the safety net to not work viper4android, xposed, ect. you need to remove them. if you do need xposed there is a systemless 84.5 (cant remember exact verison) google it if that's the case also a update-unSU.zip can be flashed and that in my experience does fully un-root
I'm running it well with phh-su (recommended with magisk) coming from superSU its not that bad/different
and the systemless xposed (flash xposed uninstaller) then system-less xposed and for other system dependent tweaks try to find system-less versions

Dr_DjEnder said:
anything modifying the system will prompt the safety net to not work viper4android, xposed, ect. you need to remove them. if you do need xposed there is a systemless 84.5 (cant remember exact verison) google it if that's the case also a update-unSU.zip can be flashed and that in my experience does fully un-root
I'm running it well with phh-su (recommended with magisk) coming from superSU its not that bad/different
and the systemless xposed (flash xposed uninstaller) then system-less xposed and for other system dependent tweaks try to find system-less versions
Click to expand...
Click to collapse
If I may ask, how did you run Uninstaller for supersu? I followed the instructions and others posts on the Magisk thread. But to no avail. I was able to update to jasmine and unlock the bootloader, coming from biggins. But cannot go further than that. Pokémon worked for me on Biggins with no extra root hide or work up until latest update.

nIkbot said:
If I may ask, how did you run Uninstaller for supersu? I followed the instructions and others posts on the Magisk thread. But to no avail. I was able to update to jasmine and unlock the bootloader, coming from biggins. But cannot go further than that. Pokémon worked for me on Biggins with no extra root hide or work up until latest update.
Click to expand...
Click to collapse
No idea what this biggins is (a rom possibly) but I can help with the uninstall I used a update-unSU.zip just flashed in recovery I'm using the latest twrp 3.?.?.? (idk what it is exactly) but should work on anything worked on both my Oneplus 2 (daily driver) and my note 3 (backup/test phone) so it should work I ran pokemans on both using magisk and systemless root. heres the zip

Dr_DjEnder said:
No idea what this biggins is (a rom possibly) but I can help with the uninstall I used a update-unSU.zip just flashed in recovery I'm using the latest twrp 3.?.?.? (idk what it is exactly) but should work on anything worked on both my Oneplus 2 (daily driver) and my note 3 (backup/test phone) so it should work I ran pokemans on both using magisk and systemless root. heres the zip
Click to expand...
Click to collapse
Thank you for the response!
So the path to try is.
Boot to TWRP (3.0.2-0 installed)
Flash UPDATE-unSU.zip
Flash xposed-uninstaller-20160829-arm64.zip
Flash Magisk-v6.zip
Flash phh-superuser-17-magisk.zip
Boot up. Install Magisk manager v1.2
Reboot
Flash xposed-v86.5-skd23-topjohnwu.zip
This seem like the correct course of action?

nIkbot said:
Thank you for the response!
So the path to try is.
Boot to TWRP (3.0.2-0 installed)
Flash UPDATE-unSU.zip
Flash xposed-uninstaller-20160829-arm64.zip
Flash Magisk-v6.zip
Flash phh-superuser-17-magisk.zip
Boot up. Install Magisk manager v1.2
Reboot
Flash xposed-v86.5-skd23-topjohnwu.zip
This seem like the correct course of action?
Click to expand...
Click to collapse
Yes it seem right however..
I flash the xposed with the Magick and uperuser ect and haven't had any problems.... Yet...? Idk if it can depends on use case may save you a reboot idk

Dr_DjEnder said:
Yes it seem right however..
I flash the xposed with the Magick and uperuser ect and haven't had any problems.... Yet...? Idk if it can depends on use case may save you a reboot idk
Click to expand...
Click to collapse
Don't bother letting it reboot and installing the manager? Just flash the xposed.zip before hand worked for you?

nIkbot said:
Don't bother letting it reboot and installing the manager? Just flash the xposed.zip before hand worked for you?
Click to expand...
Click to collapse
After fresh install of rom, immediate unroot with supersu. It gets uninstalled and reboot automatically.
Flash magisk.zip, phh superuser.zip and xposed.zip.
Then install magisk.apk & xposed.apk.
Install phhsupersu from playstore.
Works for me.
Sent from my SM-G925F

Rosli59564 said:
After fresh install of rom, immediate unroot with supersu. It gets uninstalled and reboot automatically.
Flash magisk.zip, phh superuser.zip and xposed.zip.
Then install magisk.apk & xposed.apk.
Install phhsupersu from playstore.
Works for me.
Click to expand...
Click to collapse
Just tested yes that works fine so yeah save yourself the reboots.

(1)Hmm. Gave this a go. All the zips flash except the last one. The xposed-v86.5-sdk23-topjohnwu.zip fails for version support... Try to reboot and get stuck on logo... Rebooted to TWRP wiped reflashed jas and odin'd partial firm and back to square 1 again.
(2)Tried again with the v86.5 sdk21 and it flashed. Go to reboot and in top left screen says.
> Kernal is not SEANDROID enforcing
> set warranty bit : kernal
Then stuck at boot logo looping.
No clue on what's hanging up on this.
(3) Back to twrp, factoryreset, jas,partial, firmwar, twrp again. Square 1 again.

nIkbot said:
Hmm. Gave this a go. All the zips flash except the last one. The xposed-v86.5-sdk23-topjohnwu.zip fails for version support... Try to reboot and get stuck on logo... Rebooted to TWRP wiped reflashed jas and odin'd partial firm and back to square 1 again.
Click to expand...
Click to collapse
The rom is mm?.
And the first time when you're uninstalling supersu, you would be asked to return to stock boot image or something. Choose no.
Sent from my SM-G925F

Rosli59564 said:
The rom is mm?.
And the first time when you're uninstalling supersu, you would be asked to return to stock boot image or something. Choose no.
Sent from my SM-G925F
Click to expand...
Click to collapse
Running the latest Jasmine rom. http://forum.xda-developers.com/showthread.php?t=2760380
Running the SuperSU app and selecting, "full unroot" only prompts a warning with cancel/ok. The next screen is uninstalling and it has hung up there... Thinking this rom is not playing nice with the process or I have something out of place..
(2) WHoooo boy... :/ After doing it that way through the app and having to start over. I cant flash the TWRP zip i've been using each time to get recovery on... Get "Non official verizon sofware" error screen. have to odin the partial firm to get it to boot again...

nIkbot said:
Running the latest Jasmine rom. http://forum.xda-developers.com/showthread.php?t=2760380
Running the SuperSU app and selecting, "full unroot" only prompts a warning with cancel/ok. The next screen is uninstalling and it has hung up there... Thinking this rom is not playing nice with the process or I have something out of place..
(2) WHoooo boy... :/ After doing it that way through the app and having to start over. I cant flash the TWRP zip i've been using each time to get recovery on... Get "Non official verizon sofware" error screen. have to odin the partial firm to get it to boot again...
Click to expand...
Click to collapse
About the unrooting, probably you could choose ok.
The xposed should be sdk21 as the rom is android 5.0.
Sent from my SM-G925F

Never got prompted for an OK on the unroot. It just said the warning prompt then went to uninstalling animation which didn't end. Now I can't flash twrp.zip. so no custom recovery.

nIkbot said:
Never got prompted for an OK on the unroot. It just said the warning prompt then went to uninstalling animation which didn't end. Now I can't flash twrp.zip. so no custom recovery.
Click to expand...
Click to collapse
Sorry to hear that. I thought verizon has already unlock note 3 bootloader. Why it should prompt unathorized software thing?.
Probably no systemless for the rom you're using. The rom you mentioned is way too outdated. Understandable as it's got locked earlier.
Perhaps you could try with clean install 1 more time. Just make sure the xposed version is correct. But I believe the old rom isn't using systemless supersu either, so perhaps that's 1 of the issue. Just few months ago chainfire came up with systemless root.
I personally don't know the different though.
Sent from my SM-G925F

Rosli59564 said:
Sorry to hear that. I thought verizon has already unlock note 3 bootloader. Why it should prompt unathorized software thing?.
Probably no systemless for the rom you're using. The rom you mentioned is way too outdated. Understandable as it's got locked earlier.
Perhaps you could try with clean install 1 more time. Just make sure the xposed version is correct. But I believe the old rom isn't using systemless supersu either, so perhaps that's 1 of the issue. Just few months ago chainfire came up with systemless root.
I personally don't know the different though.
Sent from my SM-G925F
Click to expand...
Click to collapse
Before trying magisk the first time yesterdat i was able to ollow the unlock thread and on the Odin download screen it says I have it unlocked to dev edition so I'm quite confused on that as well..
Should just boot to normal recovery and try to do the factory reset/reflash jasmine one last time?

nIkbot said:
Before trying magisk the first time yesterdat i was able to ollow the unlock thread and on the Odin download screen it says I have it unlocked to dev edition so I'm quite confused on that as well..
Should just boot to normal recovery and try to do the factory reset/reflash jasmine one last time?
Click to expand...
Click to collapse
Probably you can try again. Have you asked in verizon note 3 section and in the rom thread if anybody successfully run magisk on their phones?.
Sent from my SM-G925F

Rosli59564 said:
Probably you can try again. Have you asked in verizon note 3 section and in the rom thread if anybody successfully run magisk on their phones?.
Sent from my SM-G925F
Click to expand...
Click to collapse
Yeah, I posted to the jasmine thread.
Geeze. Running from stock recovery made things worse for a bit. Odin'd back to partial. Had to Re-run bootloader unlock process to get TWRP installed correctly and working again.
Thats working again and fine, download screen says Developer mode again.
One thing out of place now is the xposed app shows the "custom version 71 build is active" with no clickable options now. Running the uninstallers from TWRP does not clear and posts errors...
Another full stop. Really scratching my head on this one
Wondering at this point if it's less trouble to flash a different rom... I haven't been up to speed in a long time with them and thought that coming from Biggins4.4.2 to Jasmine 5.0 was a massive jump.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

nIkbot said:
Yeah, I posted to the jasmine thread.
Geeze. Running from stock recovery made things worse for a bit. Odin'd back to partial. Had to Re-run bootloader unlock process to get TWRP installed correctly and working again.
Thats working again and fine, download screen says Developer mode again.
One thing out of place now is the xposed app shows the "custom version 71 build is active" with no clickable options now. Running the uninstallers from TWRP does not clear and posts errors...
Another full stop. Really scratching my head on this one
Wondering at this point if it's less trouble to flash a different rom... I haven't been up to speed in a long time with them and thought that coming from Biggins4.4.2 to Jasmine 5.0 was a massive jump.
Click to expand...
Click to collapse
The xposed is normal since 5.0. You can't click anywhere except reboot and doft reboot. But it isn't systemless xposed.
It's ok unless you're trying to get systemless xposed to work.
Sent from my SM-G925F

Rosli59564 said:
The xposed is normal since 5.0. You can't click anywhere except reboot and doft reboot. But it isn't systemless xposed.
It's ok unless you're trying to get systemless xposed to work.
Sent from my SM-G925F
Click to expand...
Click to collapse
Neat. Then I'm back to square one. Everything where it should be again at least.
Have to dig around some more and see if there is a more friendly base rom I can work with to get this accomplished. Thanks for the help Rosli!