When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire
Related
Hi,
I seem to have managed to bootloop my Nexus 5. Yesterday I updated my Nexus to Android Lollipop (through the system update), I rooted it with CF-Root. All working well after.
However, I noticed that xposed was not activated. So I pressed on uninstall with the intention to install again. As soon as it rebooted, the device got a bootloop.
What should I do?
I tried the xposed-disabler fix but to no avail.
Thanks,
Immortali
Flash stock firmware again. I'm sure stock images are available in the N5 section.
Also, Xposed is not compatible with Lollipop so don't try to install it again unless you want to recover from another bootloop.
Sent from my C6603
Dies that mean that I will lose all data and need to reinstall all apps again?
immortali said:
Dies that mean that I will lose all data and need to reinstall all apps again?
Click to expand...
Click to collapse
I don't have an N5, but you should be able to just flash /system leaving your data intact.
If you ask in the N5 section I'm sure someone there will help you.
Sent from my C6603
You can save your data!
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
I'll try that
I did something else:
I did a Nandroid backup, Flash Stocked and then restored the data part only. It is still in the bootloop, therefore I am presuming that the data is actually corrupted.
Can I edit a nandroid backup that is saved on my pc and remove xposed from it?
I think teh lesson here is when moving from one version of Android to another you should do a clean install, either that or just dirty flash over the after a system wipe. Either way I struggle to see how this is an Xposed issue..
OmerElbaz said:
If you know how to flash the stock image (If not, let me know), you can just look at the "flash-all" file and search for: "fastboot -w update image-hammerhead-<VersionCode>.zip".
Then, just delete the "-w" (W stands for Wipe).
After that you can just flash with no fear, all of your data will be kept.
If you don't know how to flash a stock image or you know another way to do so that is not giving you the option to not wipe everything form your device, let me know and I'll send you a guide (well, actually, I will translate you a guide from another language ).
Hope I helped and sorry for my English
Click to expand...
Click to collapse
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
cmstlist said:
Please note that even without the -w flag, if it flashes over userdata.img then that's a wipe.
Click to expand...
Click to collapse
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
OmerElbaz said:
I didn't knew that actually, what exactly does it wipes?
And still it's pretty much the best you can do... I think
Click to expand...
Click to collapse
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
Inferi0r said:
Argh, did exactly the same with the same result. So it's an XPosed issue.
Installed Lollipop OTA on my Nexus 7 WiFi 2013 with XPosed installed. Everything fine and running for a few days.
A few hours ago I decided to remove the XPosed framework from inside the XPosed installer and rebooted -> bootloop.
Strange that this happens after removing XPosed.
Click to expand...
Click to collapse
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
Userdata.img covers the entire data partition including internal SD, installed apps and app data. Flashing Userdata.img is equivalent to a full data and storage wipe.
Sent from my Nexus 5 using Tapatalk
---------- Post added at 08:11 AM ---------- Previous post was at 08:07 AM ----------
All the modifications that Xposed originally made to your system were reverted by the OTA. I'm sure what happened was the Xposed installer held onto backups of the system files it had modified. When you "uninstalled" Xposed it replaced some proper Lollipop system files with backups that came from KitKat. No wonder it bootlooped.
Since it corrupted system files, what you really need to do is reflash the system.img of Lollipop in fastboot. Then it should boot fine without data loss. Then reroot if you want to.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Are you sure about the wipe?
Cuz I think I already used this method once "without wiping" (For sure used it WITH wiping b4 but I'm not sure I also used without..) and if I really used it this way then I'm pretty sure it didn't wiped any of my data (I may be wrong, though, let me know if it's 100% wipes).
Thanks for all the suggestions, I managed to reboot my Nexus 7 without any loss of userdata.
With help of the Nexus Root Toolkit v1.9.8 I flashed the system.img from the razor-lrx21p-factory-ba55c6ab.zip onto my device in bootloader mode. Within 3 minutes I was up and running again.
That's all it takes to fix the bootloop.
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
db77 said:
Ok, but the question is "What to do to uninstall Xposed after Lollipop Update ?"
Click to expand...
Click to collapse
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
You don't do anything. If the update succeeded and your device boots successfully, then the update already removed Xposed.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
db77 said:
Some people who try to uninstal Xposed, have bootloop.
I haven't uninstall Xposed and I wait for an update for Lollipop... because my Nexus 5 works fine without uninstall Xposed. But it don't work...
Click to expand...
Click to collapse
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
cmstlist said:
What doesn't work? The OTA? Lollipop? Xposed?
If you did the OTA and the OS works, then just remove the Xposed Installer app and your Xposed modules. Xposed itself is no longer installed so don't take any further steps.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
db77 said:
Xposed don't work under Lollipop.
On my Nexus 5, Xposed is always present but don't work, because ART et not Dalvik.
It has not been uninstalled...
Click to expand...
Click to collapse
What makes you say Xposed is still there? The files that were patched when you installed Xposed under KitKat have been replaced by the Lollipop upgrade. Hence it's gone.
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
KWKSLVR said:
So this morning I got this maintenance update and now I'm being told that an update is available and that this install is differed. When I click on "select to continue update" I'm told my system is up to date. I've already wiped cache, which did not help. Anyone else experiencing this?
Click to expand...
Click to collapse
Are you unlocked and rooted?
Nope, totally stock Verizon 4.4.4. I'm so far out of the loop, I didn't even know I could unlock and root in the first place.
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
T-Keith said:
Anyone have a fxz for this update? I have it too, but I am rooted with twrp.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
KidJoe said:
There does not appear to be an FXZ for this.
You can try flashing stock Recovery.img onto your phone and take it. Unlike other OTA's that failed due to Xposed, this one did not give me any issues installing with Xposed still enabled.
NOTE: I'm unlocked bootloader, rooted, running TWRP, with Xposed instaled (MotoXNetActivity module installed). I haven't made any other modifications. I only run apps that require root like AdFree, wifi tether for root, Root Explorer, etc.
Click to expand...
Click to collapse
Thanks, I think this answered my questions in the other thread.
Is there a risk to try running the update with stock recovery and other Xposed modules like Gravity Box? Would they fail similarly to a failed system check like I've had in the past for removing/renaming system apps and such?
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.
Here's the download link for the factory image at the usual place: https://dl.google.com/dl/android/aosp/hammerhead-mmb29s-factory-6bfcdfa4.tgz
Amazed to see that no one created a thread for this (I guess). I know that this is only a month security bug fixing, but still, sometimes they fix other things beyond that.
If anyone notice more bug fixes (or more bugs!!!) beside the security ones, glad to report.
does anyone manage to root it with superSU 2.66?
onesolo said:
Amazed to see that no one created a thread for this
Click to expand...
Click to collapse
Probably because other threads have the link already...
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. It works without problems.
Sent from my Nexus 5 using XDA Free mobile app
damijanp said:
Yes. It works without problems.
Click to expand...
Click to collapse
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
EddyOS said:
Probably because other threads have the link already...
Click to expand...
Click to collapse
It's not about the link!!! It's about a thread to discuss this new factory image!!
onesolo said:
So, one only needs to have TWRP and flash latest systemless SuperSu, right?!
Click to expand...
Click to collapse
Yes.
aslam_ said:
does anyone manage to root it with superSU 2.66?
Click to expand...
Click to collapse
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
What the difference with mmb29k?
faighter said:
What the difference with mmb29k?
Click to expand...
Click to collapse
Monthly security update.
tuncan said:
Yes. I now have Android 6.0.1 (MMB29S), SuperSU 2.66 and ElementalX 6.0.7.
Click to expand...
Click to collapse
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Yes, it worked for me. After update, I flashed elementsX 6.07, then SuperSU 2.66.
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
ezio84 said:
I tried today with xposed and the new factory, NFC service started crashing (i flashed the new system img without deleting data).
So i rebooted again in twrp, flashed the xposed uninstaller zip, then wiped dalvik/cache, flashed xposed installer, wiped dalvik/cache again. Now it's working fine.
Click to expand...
Click to collapse
Did you wipe cache and dalvik the first time?
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
PhilipTD said:
Did you wipe cache and dalvik the first time?
Click to expand...
Click to collapse
Yes i did (i also did a fastboot erase for cache, system and boot partitions).
pgptheoriginal said:
I have problems with the update :crying:
Before updating, I had the phone in "alarms only" mode; I flashed the new factory image, and now I can't disable it anymore! I tried both using the notification pane, and the volume rocker, but the setting doesn't switch off...
Any ideas?
Click to expand...
Click to collapse
Weird issue. I'd try a factory reset.
I figured out how to disable it: I added a rule to enable Do Not Disturb for calendar events, then created an event lasting one minute. At the end of the event, the phone was back to "All notifications"; the toggle works fine now.
Sent from my Nexus 5 using Tapatalk
Does it fix the syncing/notification issues ?
PhilipTD said:
I'm now on 6.0.1 MMB29K, SuperSU 2.65, and ElementalX 6.07 and intend to update to MMB29S, SuperSU 2.66, same ElementalX. Were/are you running Xposed? I'm wondering if I should uninstall it first and then reinstall afterwards. Thanks
Click to expand...
Click to collapse
No, I don't have Xposed at the moment.
Another minor issue is that WiFi seems to be always on, looking at the battery usage graph, even when it's set to be off (WiFi scanning is disabled), and even when the phone is in airplane mode!
I don't know how to check if it's actually always on, but I noticed this both before and after the latest security update.
Sent from my Nexus 5 using Tapatalk
I set the Xposed app to install via manual flash because the other two methods kept freezing my phone. But I can't find the zips! Can someone please tell me where they are supposed to be and where they might be if they're not there? My device is a Samsung Galaxy S2 HD LTE (SM-i757M) on 4.0.4.
superluig164 said:
I set the Xposed app to install via manual flash because the other two methods kept freezing my phone. But I can't find the zips! Can someone please tell me where they are supposed to be and where they might be if they're not there? My device is a Samsung Galaxy S2 HD LTE (SM-i757M) on 4.0.4.
Click to expand...
Click to collapse
When you say "on 4.0.4" do you mean that is your android version? If so, you don't flash Xposed, you have to use the older apk version of Xposed
Sent from my SCH-R220
mattzeller said:
When you say "on 4.0.4" do you mean that is your android version? If so, you don't flash Xposed, you have to use the older apk version of Xposed
Sent from my SCH-R220
Click to expand...
Click to collapse
I have to flash it, the "Classical - Write to /system" and "Auto-flash" modes don't work. I know you have to flash it on Lollipop and above - I've already done that with another phone. but on this one I need to flash it using the apk. I just can't find where the app put the zip for me to flash manually.
superluig164 said:
I have to flash it, the "Classical - Write to /system" and "Auto-flash" modes don't work. I know you have to flash it on Lollipop and above - I've already done that with another phone. but on this one I need to flash it using the apk. I just can't find where the app put the zip for me to flash manually.
Click to expand...
Click to collapse
You are on ICS, you do not flash Xposed, you install via the apk from here:http://repo.xposed.info/module/de.robv.android.xposed.installer
Sent from my SCH-R220
mattzeller said:
You are on ICS, you do not flash Xposed, you install via the apk from here:http://repo.xposed.info/module/de.robv.android.xposed.installer
Sent from my SCH-R220
Click to expand...
Click to collapse
Omg m8. I INSTALLED THE APK. The "Classical" install method and the "Recovery (Automatic)" install methods DO NOT WORK. There is also a "Recovery (Manual)" method. The app WRITES A ZIP TO THE INTERNAL STORAGE. Then you FLASH THAT ZIP. I cannot FIND that zip. That's what I asked for help with. As I said, I know you don't normally flash Xposed with a zip unless you're on Lollipop or above. I've been doing this for a long time, dude. I just can't find the zip the app wrote to the internal storage, and the app doesn't have a way to find out. Jeezus.
superluig164 said:
Omg m8. I INSTALLED THE APK. The "Classical" install method and the "Recovery (Automatic)" install methods DO NOT WORK. There is also a "Recovery (Manual)" method. The app WRITES A ZIP TO THE INTERNAL STORAGE. Then you FLASH THAT ZIP. I cannot FIND that zip. That's what I asked for help with. As I said, I know you don't normally flash Xposed with a zip unless you're on Lollipop or above. I've been doing this for a long time, dude. I just can't find the zip the app wrote to the internal storage, and the app doesn't have a way to find out. Jeezus.
Click to expand...
Click to collapse
The Jeezus quick is completely unnecessary and uncalled for when somebody's trying to help you.
What version of the APK did you install and trying to use?
Sent from my SCH-R220
mattzeller said:
The Jeezus quick is completely unnecessary and uncalled for when somebody's trying to help you.
What version of the APK did you install and trying to use?
Sent from my SCH-R220
Click to expand...
Click to collapse
I am using version 2.7 experimental1 of the app.
superluig164 said:
I am using version 2.7 experimental1 of the app.
Click to expand...
Click to collapse
When installing via the apk, does it freeze during the install, or after it reboots?
Sent from my SCH-R220
mattzeller said:
When installing via the apk, does it freeze during the install, or after it reboots?
Sent from my SCH-R220
Click to expand...
Click to collapse
It freezes during the install, but if you leave it for long enough it complains that it couldn't mount /system as rw even though it has root permissions and other apps can mount it as rw (I used ES File Explorer to delete some sounds and it worked fine.) As for the automatic flash method, it just never reboots. I guess calling the reboot action is just incompatible with my phone and/or ICS. Or maybe Philz Touch doesn't support it? I can't be sure.