I rooted my phone with Kingroot, and ran this script to replace the Kinguser with SuperSU: http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
After launching SuperSU it updates the binary and everything works fine until I reboot my phone. Now when I launch SuperSU it says no su binary installed. Using es file explorer I can see the su is in /system/xbin where it should be but SuperSU can't see it.
After rerooting with Kingroot and doing the same process over SuperSU will once again work fine until I reboot my phone. Anyone know what's going on and how I can get SuperSU to work properly?
Anyone?
I tried flashing the SuperSU.zip, but when I launch the app it fails to update the binary. I've also tried installing ChainsDD Superuser but it also fails to update the binary. I've even tried manually copying, setting permissions, and symlinking the files found in the SuperSU.zip, but it still fails to update.
I don't like using Kingroot because apps like Titanium Backup and Lucky Patcher don't work with it's su binary. Has anyone encountered this before? Why won't SuperSU update? And when it does update why can't it survive past a reboot? This is stressful ha. Any help is very much appreciated.
By the way I'm using a Cricket Galaxy S4 (SGH-I337Z). It's a weird model that few people seem to know about (I337ZTUUBOA1). The only root method that works on it is Kingroot otherwise I would have just rooted it some other way.
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
xstokerx said:
I had an idea wile reading your post could u try flashing TWRP for ur phone then rooting with the built in installer might be worth a try but u might need to Un root or flash back to what ever firmware ur using to remove root so that TWRP sees that ur not rooted
Click to expand...
Click to collapse
I've got twrp flashed. How do I use the built in root installer??
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
xstokerx said:
When u boot into system from TWRP it will ask you if u want to root the system but it only asks if TWRP can't detect root.
Click to expand...
Click to collapse
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Nihilian said:
I unrooted and rerooted with twrp. It installed su binary, but when I install SuperSU and launch it it still gives the no binary installed error
Click to expand...
Click to collapse
Sorry to hear was worth a shot I can't think of any thing else right now :crying:
Klown80 said:
Try rooting with kingroot, then uninstall king user by going into king user and unrooting. Once that is done, download the newest version of SuperSU.zip (update-supersuv2.46.zip I think is newest) then copy to phone storage, reboot to twrp and then flash the SuperSU zip. Reboot and profit!
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Still no luck I think it's an issue with the SuperSU app. Something during a reboot causes it to break for some reason. I really hope it can be fixed :/
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
xstokerx said:
Well only thing I can think of is odin to stock and start over or find a nice custom rom that works with your phone that comes pre rooted if there are any.......
Click to expand...
Click to collapse
Finally found a working custom rom and everything is working. Thanks
Nihilian said:
Finally found a working custom rom and everything is working. Thanks
Click to expand...
Click to collapse
Awsome to hear u found something that works for u and ur welcome ?
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
{
"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"
}
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
jabre said:
I don't wanna open new topic coz I have similar problem.....
I have huawei g630, rooted and unlocked bootloader, but no cwm.... and supersu gives me this messages.....
and when I click on that phone restarts and nothing happens..... when I cancel that this is msg.....
what could be the problem?
Click to expand...
Click to collapse
I'm sorry but I probly can't help I know nothing about your phone this is the att/Canadian s4 forum how did u get your phone rooted? U can try unrooting and rooting with a different method or retry with same method
Related
This morning I was suprised to find a new update for my Nexus 7 2013 LTE; it brings the Android-version to 4.3.1
No changelog found yet...
{
"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"
}
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Jacktheskipper said:
Any news if this breaks root etc.? WIll flashing this from recovery and flashing supersu.zip afterwards work like last time?
Click to expand...
Click to collapse
It's broken my root, though that's probably because I used the OTA update rather than flashing in recovery.
I got it too.
in the update file a some changes at:
keymaster / keystore
camera firmware
framework
services and telephony-common
what exactly has changed I do not know.
root + recovery need to be flashed again. but no problems.
if root and recovery need to be flashed again, did you just do the ota update from the sytem or did you sideload the zip and flash it from recovery?
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
You won't be able to until someone puts out a custom ROM for Flo/Deb.
jmone said:
I'm on JLS36C Rooted, with the ElementalX Kernel and Teamwin Recovery (V2.6.3.0) but the "JLS36I from JLS36C" fails to flash for me from the Teamwin Recovery. Any hints on the process to do this update?
Thanks
Nathan
Click to expand...
Click to collapse
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
jak3z said:
First go back to stock kernel, then remove any custom modified files from stock, then try to do the OTA update.
Click to expand...
Click to collapse
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
jmone said:
FYI - used the SkipSoft Android ToolKit to reflash the stock JLS36C then did the OTA update to JLS36I. Bit of a PITA as I now need to reinstall it all but it works!
Click to expand...
Click to collapse
That was totally unnecessary,
I've updated European nexus in Russia without any problem
Have a trwp recovery and supersu binary. Check ota survivalable mode in supersu and just apply update. Trwp updates all stuff. Root works, recovery didn't check for now
jak3z said:
That was totally unnecessary,
Click to expand...
Click to collapse
Thanks.... Next time!
Update :lost trwp recovery and need to flash it again.
Отправлено с моего...
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
keplenk said:
oh man! i just rooted my N7 last night. i just installed a LOT of apps .
i used wugs toolkit so right now i have twrp + root and nothing more. so im stock rooted.
i have never done this before but should i use wugs tool kit again to unroot and relock bootlader THEN ota?
or can i just update while rooted?
thanks!
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
You can run the OTA perfectly fine, you will lose Root and Recovery after you OTA, but you can get back those 2 anytime you want. Grab the CF-Auto-Root of chainfire (its on the Android Original Dev forum) and you will get root back.
keplenk said:
or can i just update while rooted?
p
Click to expand...
Click to collapse
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Jacktheskipper said:
you totally can, put the zip-file on your device, got to twrp-recovery and flash the zip file. if you wanna make sure you aren`t running into any trouble download the supersu.zip from here: http://download.chainfire.eu/346/SuperSU/ and flash it after flashing the update.
Click to expand...
Click to collapse
http://download.chainfire.eu/supersu
1. Go into SuperSu settings to enable survival mode.
2. Download the OTA directly on your Nexus as you would without root and restart to install.
3. It will be installed by TWRP, root will be kept, but TWRP will be gone.
4. Reflash TWRP in Fastboot.
I've rooted my phone, then followed all the steps in the recovery installing guide, but then I get this message and nothing happens:
{
"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"
}
I don't know what to do. I'm trying to install CWM.
MaorSwan said:
I've rooted my phone, then followed all the steps in the recovery installing guide, but then I get this message and nothing happens:
I don't know what to do. I'm trying to install CWM.
Click to expand...
Click to collapse
Use Flashify
It just makes it so easy.
scottdanpor said:
Use Flashify
It just makes it so easy.
Click to expand...
Click to collapse
Downloaded it, now what?
MaorSwan said:
Downloaded it, now what?
Click to expand...
Click to collapse
I'm not sure which guide you're using, I installed TWRP with it. But all you need is your recovery.zip file. Choose Recovery Image, then "Choose a file" and flash your recovery zip file. You can try "Download CWM" but it might not find one for the LS980 (depends which version you have).
scottdanpor said:
I'm not sure which guide you're using, I installed TWRP with it. But all you need is your recovery.zip file. Choose Recovery Image, then "Choose a file" and flash your recovery zip file. You can try "Download CWM" but it might not find one for the LS980 (depends which version you have).
Click to expand...
Click to collapse
Can you give me a link to the newest TWRP so I'd install it?
MaorSwan said:
Can you give me a link to the newest TWRP so I'd install it?
Click to expand...
Click to collapse
Which version of LG G2 do you have?
scottdanpor said:
Which version of LG G2 do you have?
Click to expand...
Click to collapse
D802
MaorSwan said:
D802
Click to expand...
Click to collapse
Ah ok, I had a look through the thread and it looks like your best bet is to use the auto method, and if that doesn't work, you'll have to go manual. You can use flashify to update after you get the recovery on the first time.
I used this http://forum.xda-developers.com/showthread.php?t=2469995 , also on D802
and after that, i updatet via twrp to the latest verion, but i can't find the link right now.
Does flashify automatically install loki to bypass the locked boot leader? Does it work on the VS980?
Try Freegee from playstore. Very easy to use. I have d802 and used that one.
Sent from my LG-D802 using Tapatalk
mrm43 said:
Try Freegee from playstore. Very easy to use. I have d802 and used that one.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
second that , used Freegee to install twrp
just install the app and choose what kind of recovery you want , it will download and install , then press menu and reboot to recovery to test it
couldn't be easier
[email protected] said:
second that , used Freegee to install twrp
just install the app and choose what kind of recovery you want , it will download and install , then press menu and reboot to recovery to test it
couldn't be easier
Click to expand...
Click to collapse
Does this take care of Loki and the locked boot loader as well, or do you have to do that separately?
mattlach said:
Does this take care of Loki and the locked boot loader as well, or do you have to do that separately?
Click to expand...
Click to collapse
not sure to be honest , i just bought the phone 3 days ago
but it helped me install the recovery and i installed a new rom without a problem
and yes there is an option update zip in loki or something like that , do you know what is it ?
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?
Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!
Lorenzo Benevento said:
Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!
Click to expand...
Click to collapse
https://s31.postimg.org/w6twfqivv/66957ed3_9534_4de8_9804_64a80d21a259.jpg
for me this error comes
I have also same problem in my zuk z1 Indian version. Cyanogen recovery and kingroot. OTA install failed during recovery. I manually download the file then apply update in recovery. It also failed. Please anyone help me
The ota not work on twrp n kingroot n supersu its work only on
Stock recovery only bro
---------- Post added at 07:20 PM ---------- Previous post was at 07:15 PM ----------
The ota not work on twrp n kingroot n supersu its work only on
Stock recovery only bro I m from india
So if I select "Update cyanogen recovery" it should work. I'm right? And I can keep SuperSU
I am having the and problem. I have a rooted phone, I had SuperSu, Root Browser, ROM Toolbox and Busybox. I uninsta]lled then all, I don't know know of my phone is still rooted or not, of it is I have to unroot it, though I don't know how, but till now uninstalling all those apps didn't help, while updating it's still getting failed at Verifying Current System.
Since in new here, I can't post an image here, sorry.
Lorenzo Benevento said:
Hieveryone,
last night i've tried to update my phone using OTA, but it still not work. I have TWRP recovery and supersu installed. I believe this is because of root. My phone restart in recovery mode and says something like "zip file is corrupted". What's the solution?
Thanks in advance and sorry for My bad english!
Click to expand...
Click to collapse
{
"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"
}
anyone help me
Sent from my Z1 using XDA-Developers mobile app
I have twrp and super su also on my phone I tired updating the ota with FLASHFIRE but got stock at boot...I need to flash and download a new stock ROM
U can try FLASHFIRE might work for u?
Sent from my Infinix X510 using Tapatalk
Attention everyone
You'll need latest signed zip to update your device to latest version.
Interested one can read this for reason.
I flashed the zip from recovery skipping the md5 verification. It has worked for me! I have only losed my root permission!
Lorenzo Benevento said:
I flashed the zip from recovery skipping the md5 verification. It has worked for me! I have only losed my root permission!
Click to expand...
Click to collapse
Oh nice, Please tell me how to skip verification
Sent from my Z1 using XDA-Developers mobile app
vishnuchandh said:
Oh nice, Please tell me how to skip verification
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
If you are on stock recovery then just flash signed zip. Zip signature verification is only for custom recovery like TWRP. To disable zip signature verification in TWRP recovery, goto TWRP setting and uncheck 'zip file signature verification' and while flashing don't select 'zip file signature verification'. File will be falshed without checking for any MD5 file checksum.
saurav007 said:
If you are on stock recovery then just flash signed zip. Zip signature verification is only for custom recovery like TWRP. To disable zip signature verification in TWRP recovery, goto TWRP setting and uncheck 'zip file signature verification' and while flashing don't select 'zip file signature verification'. File will be falshed without checking for any MD5 file checksum.
Click to expand...
Click to collapse
Sorry I have not twrp. I'm in stock recovery n rom but rooted with kingroot
Sent from my Z1 using XDA-Developers mobile app
vishnuchandh said:
Sorry I have not twrp. I'm in stock recovery n rom but rooted with kingroot
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Flash signed zip from stock recovery then.
saurav007 said:
Flash signed zip from stock recovery then.
Click to expand...
Click to collapse
Thanks a lot. Problem solved. Updated without erasing data.
Sent from my ZUK Z1 using XDA-Developers mobile app
---------- Post added at 02:12 PM ---------- Previous post was at 02:04 PM ----------
After the above update no root in my phone
Sent from my ZUK Z1 using XDA-Developers mobile app
vishnuchandh said:
After the above update no root in my phone
Sent from my ZUK Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, signed zip revert /system partition to completely stock. Flash latest SuperSU.zip to get back root access.
Thank you very much.
Sent from my ZUK Z1 using XDA-Developers mobile app
I'm in cm recovery so can't flash supersu.(signature problem). Need to change twrp recovery
Sent from my ZUK Z1 using XDA-Developers mobile app
vishnuchandh said:
I'm in cm recovery so can't flash supersu.(signature problem). Need to change twrp recovery
Sent from my ZUK Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Obviously, you'll need a custom recovery. Flash TWRP recovery and afterwards flash SuperSU from TWRP recovery.
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!