Related
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work?
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Edit 2: Tried the following without success. Exact same results. A msg on the status screen saying Xposed is installed but not active:
-Unity version of Xposed
-Magisk 14.0 + systemless Xposed framework
-Probably something else I'm forgetting
I created the missing log file and gave it the appropriate permissions but nothing ever got written to it. I suppose I could do a logcat but I can't be bothered. If Xposed doesn't work out of the box for this particular ROM I'm not going any further with it. I posted this question in the ROM thread as well.
Doc Ames said:
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work. $20 to whoever provides me with the solution.
What I did:
-Full wipe (dalvik, system, data, cache)
-Flash latest PureFusion (13NOV2017)
-Flash SuperSu v2.82
-Flash OpenGapps (pico)
-First boot
-Install Xposed installer v3.14
-Reboot to recovery
-Flash Xposed v89
I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.
I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.
Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).
Click to expand...
Click to collapse
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
Choose an username... said:
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works
Edit: I just read the last line, sorry
that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
Click to expand...
Click to collapse
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
Doc Ames said:
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
Click to expand...
Click to collapse
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?
@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!
Choose an username... said:
Nah don't want any price. a thank is enough
Which are the apps that don't work with Magisk?
Click to expand...
Click to collapse
I don't remember. If for some reason I have to use Magisk maybe I can find replacement apps.
AnonVendetta said:
@Doc Ames: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.
My setup:
Vertex Carbide
Hellsgate EAS kernel, with data and cache formatted as F2FS
Phh's Superuser, for root
Busybox 1.27.2 by YashadSaraf
Xposed v89 official
No GApps, except MicroG and Play Store
I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.
Good luck!
Click to expand...
Click to collapse
Thank you for the suggestion. The issue is that there is no other ROM for the A7 (save PureNexus and stock ROMs) that will properly connect to my Bluetooth deck. I was trying to pursue a solution to the Bluetooth issue with custom ROMs for the A7 but it affects such a small number of users that nobody seems to think it's an issue. I tried the ROM you are using and had the above mentioned Bluetooth issue. I've tried a ton of ROMs. I'd rather get a fix to the Bluetooth issue so I can use whatever ROM I want. However, I posted a question about my Bluetooth issue and everybody just gave me the whole, "It's working on my machine. Must be your deck."
@Doc Ames: Well sorry to know that you're essentially forced to used a specific rom just to get your Bluetooth deck working. I don't use Bluetooth for anything but transferring files, that's worked in every ROM I've tried. But I have had issues in the past where a certain device would work on one ROM but not on another. It could be a ROM issue, or maybe an issue with the Bluetooth device you're using. Maybe a combo of both. I'm not a dev so there's nothing I can do except be sympathetic. Maybe you can elevate your issue with A7 devs so they can maybe look into whether there are underlying Bluetooth issues in their ROMs that need to be resolved. If the deck didn't cost too much, you might want to look into selling it and getting a more known, compatible deck that works with most ROMs. I guess it all just depends on how much it's worth to you to be able to run whatever ROM you want without worrying about whether your deck will work.
Good luck!
@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
marcdw said:
@Doc Ames,
If you haven't yet, give the UNITY Xposed package (by @ahrion) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.
Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.
I too stay away from Magisk so I can't speak to any of the systemless installers.
http://forum.xda-developers.com/showthread.php?t=3697756
[12/18/2017] Xposed Framework v88.9 [UNITY]
LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
Click to expand...
Click to collapse
Thank you for the suggestion. I tried the UNITY Xposed. No joy. Same result.
Xposed on 8.1 How-to:
Required: Rooted with Magisk and Xposed installer 3.1.5 is needed for this to work.
I followed how some say to get it installed on here and just couldn't get it to install correctly. The way I got it to work on the first try is:
1) Download and install Xposed 3.15 from the link below,
2) open up the Xposed installer app and accept root,
3) in the Xposed app, click on the cloud next to the first option to install/update to 90 beta 3
4) reboot and profit.
The other methods work after numerously flashing from Magisk or twrp. But doing it once suits me fine.
The pros:
As Oreo becomes more developed by the awesome people here on XDA, more and more modules are available. So the best Pro there is, is that a lot of the modules work, too big of a list to go through, but gravity box, flat status bar, and neo power menu works definitely. Play around there is a lot working.
The cons:.
Okay so the biggest concern there is, it's the lag. I'm talking longer reboots, lag when waking device, switching from app to app, just feels like a sluggish phone after. Even the touch screen seems unresponsive at times. But if you don't care, by all means go for it.
Just thought I'd share this with everyone. Have a nice day.
After booting up for the first time in about a year I'm noticing I'm failing SafetyNet in Magisk. I'm using followmsi's very excellent 7.1.2 AOSP.
Been trying with no success to get RIRU installed both via Magisk and TWRP. Everytime I get invalid zip format if I use the file from github. Attempts to install the module from within Magisk itself lead to it showing up but it not being in the memory when I launch the Riru app.
The universal safetynet patch does not appear to work below Android 8 so I'm not sure what my options are if I want to stick with more stable/older versions of Android and pass safetynet.
I'm in a similar boat, love my CAOSP with all the bells and whistles I've added over the years, but sadly support for this version of Android is becoming scarce, and support of my features (xposed mods etc) for newer android vers is lacking enough to make me stick to it despite more and more apps becoming unavailable for my version of Android might have to look at upgrading I guess
any updates? @lobstapowa @kbekois
hey there,
i was using custom roms back in the day with my oppo find 7, so android 7ish. Back than maintaining custom roms was a major pain in .... because, at least for me, i needed to full flash every time there was an update and most roms were kind of buggy as well.
Since my 9t is being annoying lately (EU 12.0.5) with shutting down apps way to often/fast, forgetting logins, making backups everywhere, switching back to light mode, no idea how to do a proper cleanup without deleting half my app settings etc. I was wondering what the state of the custom rom is nowadays.
I was thinking about getting something smaller, but since the pixel 5 is out of sale, the zenfone 8 missing wireless charge and no real alternative and all of them are more than 600 bucks, so i dont want to get a new phone tbh, prices are out of this world imho. Also iam quit pleased with the device itself, i.e. battery, performance, everyday stuff
so basically here is what i want to know:
How are updates handled in Pixelexperience or lineage?
how hard/easy is installation?
is google pay working?
is there a relyable way to make a full backup of my phone to go back to as is now?
did anybody experience the mentioned issues and maybe has a solution?
bonus qquestions
is there any major improvement in upcomming MIUI Versions(12.1, 12.5) and a roadmap of rollout?
what does SOT mean?
thanks in advance
for updates you may have to re flash the newer rom.
2. installation is easy given you know how to do it.
3. google pay is working fine.
4. twrp is the way, but believe me you won't aspire to go back.
5. I am running pixel experience rom on MI A2 device, the device is working great.
*/learn from youtube properly how to flash recovery, install rom for your device */
best of luck
I'm on Xiaomi.eu Stable (did use Weeklies for 6 months) - daily driver / business phone
If you like MIUI, you have A11, MIUI 12.5, debloated, all stable
You only flash ROM from TWRP (of course, first time, when switching to, Format Data is mandatory).
Later they have like OTA mechanism (Updater downloads ROM in zip, reboots to TWRP and upgrades)
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
suraj123 said:
2. installation is easy given you know how to do it.
Click to expand...
Click to collapse
well i knew it, but it has been ages
Abudinka said:
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
well i knew it, but it has been ages
Click to expand...
Click to collapse
For flashing any other ROM you need to unlock Bootloader - and that breaks Safety Net, not TWRP folder or so
However, Xiaomi.eu has built-in patch to pass SafetyNet with no need for Magisk, any Magisk module, anything
I.e., you switch to Xiaomi.eu (with Bootloader unlocked), no need to install Magisk and any of the modules like USNF, MHPC, etc) and you have SafetyNet, Device Certified in Google Play.
Also Widevine L1 and Netflix really plays in FullHD, HDR-10
And if you need Magisk for something else, you just enable MagiskHide and you still have SafetyNet etc.
No troubles here with SafetyNet
how much free space do i need for a twrp backup? most likely half of the internal space i guess.
so basically for every other rom besides xiami.eu i need to worry about safety net with magisk or similar?
I have TWRP Nandroid backup of 15 GB, but most of that is Data.
You don't need the backup for installing/updating the ROM.
That's only for your comfort
But I put it to PC and delete from the phone (if really needed, TWRP can also connect to PC and you can copy it back to phone before restoring)
I never needed to restore
And one more but very important thing
TWRP (backup) has NOTHING with SafetyNet. SafetyNet DOES NOT look do you have TWRP folder, or do you have Magisk app/mngr (I'm not talking about thevMagisk core/service but apk)
Unfortunately, there are too many unknowledgeable people writing that and similar nonsense elswhere
Problem is (and that's the reason why it might look 'similar' from the end user's point of view) that various banking apps, ganes and so, use VARIOUS methods and in some cases even speculative GUESSES trying to find if your device is SAFE for their apps and businesses (whatever that means for somebody), or is your phone 'rooted' (also in the very loose sense)
Those methods and guesses may include:
- Testing SafetyNet (framework provided by Google, partly in Google Play Services and partly on Google servers).
Fornally, when Bootloader is unlocked and/or with custom ROM (not certified with Google) or rooted (stock) ROM , you *should* fail SafetyNet - but there are methods to trick Google and still to pass SafetyNet.
Actually, to flash any such nod (custom ROM or recovery, or root, you first need to unlock Bootloader - and that's the first thing that SafetyNet looks for, but on some phones and ROMs it is possible to fool even the Google's SafetyNet)
That's the reason why thosre apps combine various other methods trying to find (or just to guess) if your phone is 'safe' or not
Some use sofisticated methods looking for su in the path or modified init.rc, or bypass Magisk Hide acting as isolated processes - that way finding the gllitches in MagiskHide making them possible to detect Magisk
But some use very PRIMITIVE guesses:
- If they find TWRP folder, they 'conclude' you 'must' be having TWRP, hence your Bootloader 'must' have been unlocked and you might have been flashed the root or custom ROM, hence they simply declare your phone as 'unsafe' or "rooted'.
But you could take 100% stock and not-modded phone and just create there a folder named TWRP on Internal memory - and your phone will fail their 'safety' pass (but not the Google's SafetyNet)
- Similarly, some just look if they find that the com.topjohbwu.magisk package installed (being Magisk apk, but that is not Magisk as core/service).
Again, you can take 100% stock, not-modded phone and just install there the Magisk apk (maybe, because you wantef to use its built-in SafetyNet checker), and those apps will declare your phone was 'rooted' - which is again total nonsense
On the other side, that is all about statistics. There will be let's say 0.001% of people who do have TWRP folder but not custom TWRP recovery and similarly 0.005% people who do have Magisk app but no Magisk
On the other side, 90% of people who do have custom Recovery will also have TWRP folder and 60% of people with Magisk service/core will also have Magisk app (formerly mngr) - the rest 40% of Magisk users will have hided/obfuscated/repackaged Magisk app (therefore, it cannot be found under the com.tophohnwu.magisk package name)
Hence those apps (and their developers, or better to say those who paid those developers to implemen that GUESSES) can take them rights to declare the phones with TWRP foldersor Magisk app installed as 'unsafe'
Those 1-5 users out of 100000, who by incidence do have TWRP folder (but no custom recovery) or Magisk app (but no Magisk) - bad luck, who cares about them
On the other side, that guesses (since they didn't come up with anything more sofisticated) will make them possible to catch 500 users with TWRP or Magisk, who tricked the Google's SafetyNet (but didn't even think about that primitive possibilities to 'catch' them)
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Abudinka said:
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Click to expand...
Click to collapse
Please find and read instructions for switching to the (custom) ROM - they can be found elswhere
An important and a MUST step is Formatting Data (that also formats Internal memory). Hence not 'most' but ALL user spps, their settings, your data like photos, contacts, Wifi passwords and everything will be wiped
Read and learn about what and how can be backed up. Good luck
im fully aware, that switching to another rom needs a full wipe and therefore loss of all data if not backup'ed.
I was more hoping one could provid a link and/or recommend something convienent.
And one more point. You must first unlock Bootloader - find where/how, apply for and you will need to wait 7 days
Unlocking bootloader performs Factory reset. However, at that time you are still on MIUI and you can use Xiaomi Cloud to backup and restore upon Factory resetting
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Once you switch to your custom ROM (and potentially root), you can use some apps for backing up and restore - but avoid the old and outdated Titanium
Hence I don't really see a point in TWRP backups, only just-in-case, for restoring the last working point in case of (soft) brick cases
zgfg said:
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Click to expand...
Click to collapse
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Abudinka said:
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Click to expand...
Click to collapse
It usually takes (and not from recently) exactly 168 hours = 7 days, no more or less.
There are also threads here on XDA about
Unless Xiaomi just recently changed the policy, but that could also depend on models
SOT = screen on time
I was bored one evening, so I started poking around on XDA Forums, and found a way to fix the battery issue I had with OnePlus 3T that made me switch to another device years ago! I was surprised how usable 3T is to this day. I thought I would breathe some life into it with LineageOS 18.1 that continues to receive security updates and patches. This way I will have a backup phone ready in case something happens to my OnePlus 6. It is unlikely that 3T will receive LOS 19, so this guide should stay relevant for a long time.
1) Get back to the latest version of Oxygen OS if you are on a custom ROM. Use something like MSM Download tool and then upgrade to 9.0.6 with the built-in updater.
2) Follow the instructions on los website to install LineageOS 18.1 and google apps via MindTheGapps. If you do not need google apps, then you probably do not care about SafetyNet and do not need this guide
Now the main issue is the SafetyNet. If you install YASNAC - Yet Another SafetyNet Attestation Checker you will see that the phone is not passing the SafetyNet verification, meaning that Google Pay will not work and some other apps, like banking apps, might not work either. We are going to fix that with Magisk and MagiskHideProps. Feel free to poke around on your own. I will just present that have worked for me.
3) Go to Magisk's Github, download the latest release and follow the installation instructions. (Notes: 3T has RAM Disk, there is no separate vbmeta, boot.img is inside lineage-18.1-xxxx.zip)
4) Once you have Magisk working, got to MagiskHidePropsConf and get the latest release there. Go to Force Basic Attestation Post and follow the installation instructions under the spoiler.
5) Now, let's get Basic Integrity to pass. Go to Basic Attestation Post and make sure to add both com.google.android.gms.unstable and com.google.android.gms to deny list. Reboot. Go to YASNAC. It should say that Basic Integrity is passing. CTS profile match is not, but that's okay.
6) Install terminal app like Termux. Open it, and run su to get superuser privilages. Then run props. Follow the instructions to Edit device fingerprint (option 1).
Edit Device Fingerprint (1)
Pick a certified fingerprint (f)
Pick vendor (OnePlus is 21 at the time of writing)
Pick device (3T is 5 at the time of writing)
Pick the one with Android 9. (It does not matter that the android versions are mismatched)
Follow the instructions to apply changes and reboot.
7) Check YASNAC, everything should be passing now!
Some other suggestions:
GCam is pretty nice alternative to the original camera. I would recommend this one. (It is recommended to also install Google Photos. It is a google camera after all.)
OpenWeather is a nice weather provider.
I would also recommend going to Google's Keyboard, Messages, Phone, and Calendar Apps. AOSP ones are not great, in my opinion.
Hope somebody finds it useful! Good luck!
Ah nicely done, thanks for the effort and work you put into this. How is your 3T performing?
AndyC76 said:
Ah nicely done, thanks for the effort and work you put into this. How is your 3T?
Click to expand...
Click to collapse
Hi, thanks! I was planning to use it as a development device to pick up android app development, but life got in the way and that never got off the ground
My 3T has developed a battery issue which ultimately led to me retiring it. The battery is extremely unreliable. It can be at 1% but work for 3 hours, sometimes the phone refuses to charge and the battery percentage tends to get stuck at 50% regardless of the actual charge level. I tried replacing the battery but the same behavior persisted. I think it is something either with the motherboard or the battery connector on it :/ Still a pretty snappy phone though!