Related
For some reason my sprint note 4 all of a sudden stopped being able to install xposed framework through twrp. I'm running cm 12.1 rom and using the latest sdk but no matter what i do i still get .zip file is corrupt and twrp instantly reatarts. Can anyone shed some light on this for me?
friendofganja said:
For some reason my sprint note 4 all of a sudden stopped being able to install xposed framework through twrp. I'm running cm 12.1 rom and using the latest sdk but no matter what i do i still get .zip file is corrupt and twrp instantly reatarts. Can anyone shed some light on this for me?
Click to expand...
Click to collapse
Seems to be an issue with the .zip file. Download it again and check whether the problem still persists.
Yea i did. That's why i am a bit confused. I even tried an older version which i have installed countless times before after every nightly update but even that says corrupt zip now.
friendofganja said:
Yea i did. That's why i am a bit confused. I even tried an older version which i have installed countless times before after every nightly update but even that says corrupt zip now.
Click to expand...
Click to collapse
Did you flash a new nightly built of a custom ROM or a newer version of TWRP, maybe a bootstack? Such kind of things don't occur "all out of sudden".
I had flashed a new build of cm12.1. twrp is the same version. But i don't see what difference that would really make unless all nightlies since sept. 30th stopped support for xposed. Like i said before i had been reinstalling xposed each time i would update cm and never had an issue until recently.
No one has any ideas??
Go read the last few pages of the main thread. On Oct 5 they added a security fix to AOSP that broke xposed compatibility.
friendofganja said:
No one has any ideas??
Click to expand...
Click to collapse
A new version of Xposed (v75) is available. Download the correct version for your device and report back.
same issue
hello fellas i had same issue when i tried to install,
corrupt zip file.
i was using twrp 2.8.4
android 5.0.1
with sdk21 arm 32bits v80 (same of my phone)
we have in comom is that our phone carrier is the same, Sprint Glaxy s4 sph720
I also came across the issue with the xposed installer saying it's corrupt. Here is the entire process I went through and got around this:
(Device is LG G3 D855 running CM13)
1) Made certain all previous xposed apps were uninstalled (mostly the installer itself)
2) Also made certain any previous xposed framework was uninstalled
3) Booted back into TWRP and created a new backup (just in case)
4) Installed xposed-v83-sdk23-arm.zip via TWRP (did not reboot in between steps 3 and 4)
5) Rebooted back into system, takes a while since it optimizes all apps
6) Tried to install the XposedInstaller_3.0_alpha4.apk and ran into the corruption issue
7) Also tried XposedInstaller_3.0-alpha2.apk to see if it had the same issues (it did)
8) Installed de.robv.android.xposed.installer_v33_36570c.apk just to see if it would run, it did
9) Once de.robv.android.xposed.installer_v33_36570c.apk was installed I reran XposedInstaller_3.0_alpha4.apk and it installed successfully
10) Rebooted again
11) I was then able to download and install xposed modules
I went through all of this initially because I wanted the SU (#) indicator to be hidden. I had xposed installed on CM12 and it worked well for me. I have missed a lot of the features available with xposed.
I apologize if I have left out any pertinent info. If anyone needs more info, please reply here and let me know. If I see any questions, I will try to respond.
Please write your experience with SuperSU 2.60 / 2.61 / 2.62-3...2.66 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Systemless 2.62-3 with works as a charm with my 6.0.1.
I dirty flashed 6.0.1 system.img and boot.img, then I flashed SuperSU 2.62-3 (in TWRP). I stayed unencrypted.
Xposed, ES File Explorer, Double tap 2 wake, Greenify, BetterBatteryStats ... work perfectly.
Edit:
2.62-3 works for some with 6.0.1. and with Android Pay
2.52 has been working fine for me since mm has been out, running on MRA58R now. Have not tried 2.6 but 2.49 was also working perfectly. If you need android pay to work then 2.6 or there are other options like custom ROMs that have it successfully working
Sent from my Nexus 6 using Tapatalk
Running it here without issue. Also had it running on mra58r.
The only casualty I suppose was/is es file explorer. It could not gain root access for some reason.
I am rooted, unencrypted and have the latest Elite kernel.
Sent from my Nexus 6 using Tapatalk
Using 2.6.1 and brand new 6.0.1 fresh install and Android pay is working flawlessly!
Does anybody have a downloadlink for 2.61, can`t find it anywhere
Nevermind, found it.
gee2012 said:
Nevermind, found it.
Click to expand...
Click to collapse
Adding the link to the post would have been useful!
f2 said:
Adding the link to the post would have been useful!
Click to expand...
Click to collapse
Thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344. Link http://forum.xda-developers.com/attachment.php?attachmentid=3568267&d=1449521348.
belek1979 said:
Please write your experience with SuperSU 2.60/2.61 on Shamu.
2.56 didn't work on my unlocked, unencrypted 6.0.0 (MRA58R)
Maybe 2.60/2.61 will work with 6.0.1?
Click to expand...
Click to collapse
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root
NLBeev said:
Although 2.61 is installed
TWRP says: no root
Root Explorer says: you are not rooted
Quick reboot says: no root
Click to expand...
Click to collapse
Root Checker Pro, BusyBox Pro said i was rooted and the Franco FKU app has root too. Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.
gee2012 said:
... Maybe its a problem with apps not adapted/compatible with systemless root (2.61) yet.
Click to expand...
Click to collapse
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.
NLBeev said:
I am using the lite Rom 6.0.1 of @Danvdh. Works, but with Franco's kernel (r35) installed, problems with the sim-card. (Not recognized).
Going back to 6.0...... Too many issues.
Click to expand...
Click to collapse
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:
gee2012 said:
Well i`am on stock 6.0.1/TWRP/2.61/Franco r35 and so far no issues, everything working well :fingers-crossed:
Click to expand...
Click to collapse
Now back on 6.0. Will retry with a full wipe.
NLBeev said:
Now back on 6.0. Will retry with a full wipe.
Click to expand...
Click to collapse
Good luck, from what i understand systemless root works best on stock.
gee2012 said:
Good luck, from what i understand systemless root works best on stock.
Click to expand...
Click to collapse
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.
NLBeev said:
Did a full wipe and flashed again the lite Rom 6.0.1 of Danvdh. This rom is stock based.
After reboot I restored the 6.0-data from a nandroid backup with TWRP. Root checker says 'no root'.
Now last try with full wipe and restore from Google.
At this moment my N6 is restoring the apps from Google take a long time, but root checker says there is root access.
So this update needs a complete wipe and factory reset.
Click to expand...
Click to collapse
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.
gee2012 said:
Maybe thats it, i didn`t mention i actualy did a full wipe prior to rooting.
Click to expand...
Click to collapse
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.
NLBeev said:
I did some reading and trial with the lite rom of Danvdh. What seems important is that SuperSU 2.6x is flashed as the last file after flashing system stuff, like mods, kernel.
Click to expand...
Click to collapse
Yup, that what i did too. Thought you knew that
gee2012 said:
Yup, that what i did too. Thought you knew that
Click to expand...
Click to collapse
It is logical, but I was too busy with trying to flash without wiping the data partition.
gee2012 said:
...about wiping data...
Click to expand...
Click to collapse
I managed to update from M6.0 to M6.0.1 with data kept.
Important is that the system partition does not contain su-stuff of previous versions.
In TWRP I wiped the M 6.0 system and caches, but not the data.
Flashed the lite 6.0.1 rom of Danvdh;
Flashed Franco's kernel r35;
Flashed SuperSU 2.61;
Reboot - TWRP button 'do not install SU'.
Needed to restore settings (dpi), layers and the black themed apps of the TBO team.
I dirty flashed from stock rooted 6.0.0 to 6.0.1 today and rooted using Systemless 2.62-3. Everything is working great so far.
Source: https://forums.oneplus.net/threads/...s-starting-on-oneplus-3.454469/#post-15056543
Usual 48h to hit devices thing is probably in effect here swell but i'm sure the VPN trick will work for most if you're impatient or waiting for this fix for your SIM issue.
The changelog seems to have added just the SIM fix but for some reason the changelog on the phone says there's more Notification fixes but have to wait and see on that
Here are some of the highlights:
Fixed some notification issues
Addressed SIM recognition issue
Enabled sRGB mode in developer options
Improved RAM management
Improved GPS performance
Enhanced audio playback quality
Updated custom icon packs
Improved camera quality/functionality
Fixed some issues in Gallery
Implemented latest Google security patches
Fixed bugs in Clock/Music apps
Thanks to @Patschi_ for the links
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip[/QUOTE]
Full ROM Mirror (Soon)
deleted.
The direct link, if anyone is interested in:
OTA file
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Edit2:
Full ROM
http://otafs.coloros.com/patch/amaz...6_OTA_011_all_1607052050_0e5983ace5314161.zip
Edit3:
Mirrors for all updates and ROMs are available here:
http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
no notification issues?
Patschi_ said:
The direct link, if anyone is interested in: (OTA file)
http://otafs1.coloros.com/patch/ama...010-011_patch_1607052050_0e5983ace5314161.zip
Edit: MIrror:
http://www43.zippyshare.com/v/9NUHWPJ3/file.html
Click to expand...
Click to collapse
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
JumboMan said:
already installed 3.2.0. and its working very well
should i need to update again for 3.2.1
Click to expand...
Click to collapse
Might swell the Changelog states there's Notification issue fixes as well but still waiting to see if that's true.
Roxas598 said:
Thanks for this do you mind if I add them to the OP? not that people shouldn't see your post just might be easier i'll give credits swell.
Click to expand...
Click to collapse
Feel free to add it to the OP
Downloading the Full ROM right now to provide a mirror... could take a while as the download servers are quite slow right now.
mirrors will be provided here aswell I think: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Are you using the System Update option on the phone to install or the Zip file? either way normally any changes to the system will make OTA fail (like root and xposed)
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
Actually no. You don't have to unroot but you need to flash stock boot.img . Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed. Or wait for Full ROM mirror. Will take me some 20 minutes more. I am downloading it at the moment.
Yes, I tried to install the downloaded ota file via TWRP. Guess I have to download the whole 1.2 GB to get the 15MB update.
---------- Post added at 02:37 PM ---------- Previous post was at 02:33 PM ----------
Naman Bhalla said:
Better option always is to flash Full 3.2.0 ROM twice (sometimes first flash doesn't succeed) and then 3.2.0 -> 3.2.1 OTA immediately and then SuperSU and Xposed.
Click to expand...
Click to collapse
Thank's for the hint! Had the 3.2.0 file on my phone and did it this way.
Sledge2013 said:
no notification issues?
Click to expand...
Click to collapse
can you explained it in detail.which notification issues?
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Spotted this and just VPNd it my self.
Fingers crossed i get less drain over night
Der-Knuffi said:
Sorry for the question, just to be clear:
I install the full ROM in twrp, install it again without rebooting and after that immediately SuperSU?
Do I have to wipe Cache/Dalvik?
After that I reboot and all the apps are still there?
Click to expand...
Click to collapse
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
eikaramba said:
If you install the full 3.2.1 rom just install it once, then supersu and THEN wipe cache/dalvik. Your apps will be still there he just needs to optimize them at the start(might take 10 minutes).
If you want to use this "trick" to install 3.2.1 OTA over a 3.2.0 full rom, i have no clue. But i would rather install the full rom. I tried it with the OTA last time and it didn't worked.
Click to expand...
Click to collapse
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Der-Knuffi said:
Ok, thanks. That's the way I used to do it since years, but I'm new to OnePlus 3, so ...
Click to expand...
Click to collapse
me too. coming from nexus 5 some things definitely changed for us flashoholics
flashed over 3.2.0, no issues so far. supersu, xposed, adaway all is working fine.
daClaus said:
When I'm trying to install the ota update I'm getting an error 7 in TWRP. TWRP, root and xposed are systemless. Do I have to unroot to install the OTA?
Click to expand...
Click to collapse
daclaus, you have to install the complete rom via twrp, after that you have to install root and xposed again. ota will not work with twrp.
Hi,
I flashed the CM15 for Nook HD, Image name: cm_hummingbird-ota-NMF26Q.161222 and open Gapps(
open_gapps-arm-7.1-pico-20170329). But I can't install SuperSU on this version Android 7.1.1, either from Android or TWRP. Please help me out. Thanks.
The rom should already be rooted.
That's what I thought. But I can't use lucky patcher on this ROM. Lucky patcher asks for root privilege. That is the reason I tried to install SuperSU.
yindingmin said:
Hi,
I flashed the CM15 for Nook HD, Image name: cm_hummingbird-ota-NMF26Q.161222 and open Gapps(
open_gapps-arm-7.1-pico-20170329). But I can't install SuperSU on this version Android 7.1.1, either from Android or TWRP. Please help me out. Thanks.
Click to expand...
Click to collapse
The ROM should already support "Root", look for "Manage root access" under Settings->"Developer options", and see https://forum.xda-developers.com/showpost.php?p=71514132&postcount=9.
digixmax said:
The ROM should already support "Root", look for "Manage root access" under Settings->"Developer options", and see https://forum.xda-developers.com/showpost.php?p=71514132&postcount=9.
Click to expand...
Click to collapse
Setting shows "CM14.1-20161223". Tape builder number 7 times to enable developer option. Thank a lot for digixmax. But SuperSu still can't be install on this ROM. Appreciate for the help.
yindingmin said:
Setting shows "CM14.1-20161223". Tape builder number 7 times to enable developer option. Thank a lot for digixmax. But SuperSu still can't be install on this ROM. Appreciate for the help.
Click to expand...
Click to collapse
Problem solved.
In the setting, open the developer option:
Root Access->Apps only
Manage root access->view and control the root access
After I did these settings, Lucky patcher obtains the root access.
Thanks Digixmax!
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Blastyrant said:
Today I was having Chromecast issues with Netflix, so I factory reset my Chromecast and then had some issues getting it set back up. I had to point the Fire 7's WIFI towards the Chromecast because it couldn't find it otherwise.
After this strange series of events, I rebooted and decided maybe I would remove Netflix and install the last good version I used. I opened Titanium Backup and was told that it could not acquire root. Then a notification for SuperSU popped-up saying "The SU binary needs to be updated!". When I click on it, SuperSU opens and says "SU Binary occupied". When I click "how to solve", I'm taken to a blank WIKI page.
I rebooted. Turned on "Root access" (for apps) in "Developer options". I then rebooted again. I am still unable to achieve Root access!
My tablet was originally running Fire OS v5.1.3 and I downgraded it to v5.1.2. I Rooted v5.1.2 using Root Junkie's tools and then installed CM 12.1 using the guide from the developer's thread.
Firstly, why did this happen or how did this happen?
Secondly, what can I do to gain Root again?
Click to expand...
Click to collapse
Lol. Unlock bootloader and flash latest lineage:
UNLOCK: https://forum.xda-developers.com/amazon-fire/development/unlock-fire-t3899860
LINEAGE: https://forum.xda-developers.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
If you have lost root your only practical options are: 1) restore FireOS and start from scratch; or 2) follow the links suggested by @Rortiz2 (here).
MontysEvilTwin said:
From the error message I am guessing that you are on SuperSU 2.82. I would try uninstalling the SuperSU apk (just the apk, don't unroot) and install version 2.79 of the apk. Sometimes I have seen that error message (on 2.82) when the su binary has somehow been deleted. It tries to replace the binary but fails. If 'daemonsu' is still present in xbin it may be possible for SuperSU to fix the installation but this works better on 2.79 than it does on 2.82.
Click to expand...
Click to collapse
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Blastyrant said:
Hello thank you. I like this idea, it will be pretty easy give it a try! Is there a safe source for old SuperSU .apks that you can recommend to me?
Click to expand...
Click to collapse
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Blastyrant said:
Hello. Thank you for that reply. Both threads were very interesting! I would like Lineage on here... Unfortunately, I do not have access to Linux and fear that a lot of those steps to unlock the bootloader are beyond my current understanding.
I'll have to keep reading.
Beyond this.... is my only alternative to flash back the stock ROM, downgrade again, root, and install CM 12.1?
Click to expand...
Click to collapse
No need to install linux. Just use VirtualBox or bootable USB!
Rortiz2 said:
No need to install linux. Just use VirtualBox or bootable USB!
Click to expand...
Click to collapse
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
MontysEvilTwin said:
The best place is Chainfire's blog. A link to the page with 2.79 SR3 (bug fix update) is here: https://chainfire.eu/articles/970/SuperSU_v2.79_SR3
Download the zip file: the superuser apk is in the 'common' folder. Click on the apk file from a file browser to install. You will have to enable the option to 'install apps from unknown sources' but you will be prompted to do this if you have not already done so.
Click to expand...
Click to collapse
Thank you! I bookmarked it and grabbed the file. I've just reinstalled it and am being told "no root detected". =(
Still, it was worth a try!
Blastyrant said:
Hi. Thank you for those suggestions. I Googled quickly but am still afraid using both options is not something I'll be able to dive right into. I'm also a little confused that the guide for unlocking the bootloader mentions "Install python3, PySerial, adb and fastboot." I'm unsure how to do this for a virtual install or a bootable USB. My Linux usage dates back to a 1 month course in the mid 2000's. =P
Am I making this out to be more difficult than it actually will be?
Click to expand...
Click to collapse
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Enviado desde mi Mi A2 mediante Tapatalk
Rortiz2 said:
Yes. It's very easy. The difficult part is short the pins but since you have 5th gen you don't need to do that.
Click to expand...
Click to collapse
That said, you have to decide if the benefit is worth the effort/hassle. In the US $64 scores a very serviceable 8" tablet at Walmart running the latest version of Android that runs circles around all Amazon offerings except the HD10.