I have TA-1046 with Pie and unlocked bootloader...
After install (via TWRP) Magisk (official zip release (tested 17.1 and 17.2)), then is missed:
From Settings/System/Gestures:
- Swipe fingerprint for notification
- Swipe up on Home button
- Lift to check phone
From Settings/Display:
- Double tap to wake
After uninstall Magisk, then all this gestures is available again, this is not (direct) related to unlocked bootloader, still have unlocked and without Magisk installed is all Gestures here...
I try following:
- enabled Magisk hide
- activated MagiskManager
- installed Magisk module "MagiskHide Props Config" (but not manualy changed anynthing in prop files)
Anyone have any tips for fixing this?
btw: screenshots is from DP4.1, but in Stable Pie is same problem...
UPDATE: thanks to Doktaphex, workaround found, confirmed with screenshot here
UPDATE2: actual version (1.7.4) not working, i not have installed other version before than 1.4.3, reinstalled this older version manualy from Download folder working
Where did you get TWRP for pie? Please guide me to the correct place
Broadcasted from Zeta Reticuli
I had the same issue! I'm on Official Android 9 (version 00WW_3_22C) TA1046, and i root it with magisk by following this method:
https://forum.xda-developers.com/nokia-7-plus/how-to/guide-how-to-root-ab-partition-scheme-t3792509
When i remove Magisk Module, Gesture navigation, Lift to check and Double tap to wake are available again!
Gravemind2015 said:
Where did you get TWRP for pie? Please guide me to the correct place
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I think he didn't flash TWRP, he booted into it and flashed Magisk. That's what I did too.
---------- Post added at 12:07 ---------- Previous post was at 11:35 ----------
I am on Oreo September and I keep getting a blank screen on Smart Lock. every time I enable it somehow (Settings>Lockscreen>Trust Agents>Disable Smart Lock>Reboot>Enable Smart Lock), it gets blank again after some time.
k3dar7 said:
I have TA-1046 with Pie and unlocked bootloader...
After install (via TWRP) Magisk (official zip release (tested 17.1 and 17.2)), then is missed:
From Settings/System/Gestures:
- Swipe fingerprint for notification
- Swipe up on Home button
- Lift to check phone
From Settings/Display:
- Double tap to wake
After uninstall Magisk, then all this gestures is available again, this is not (direct) related to unlocked bootloader, still have unlocked and without Magisk installed is all Gestures here...
I try following:
- enabled Magisk hide
- activated MagiskManager
- installed Magisk module "MagiskHide Props Config" (but not manualy changed anynthing in prop files)
Anyone have any tips for fixing this?
btw: screenshots is from DP4.1, but in Stable Pie is same problem...
Click to expand...
Click to collapse
I just got the OTA today and had the exact same problem. Initially i thought it was just a bug from the update and did a factory reset, and it worked and had the gestures back until I installed Magisk again. Did you find how to fix it?
Gravemind2015 said:
Where did you get TWRP for pie? Please guide me to the correct place
Click to expand...
Click to collapse
i not flash TWRP, install Magisk via ONLY BOOTed TWRP(Oreo version)
@siberflyers, @TheWing still no have sollution
Same problem here on TA1062.
Do we suspect it's the phone or magisk to blame?
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of
cat /proc/mounts
Click to expand...
Click to collapse
on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
braveheartleo said:
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
Click to expand...
Click to collapse
info added: https://github.com/topjohnwu/Magisk/issues/668#issuecomment-433522871
braveheartleo said:
@k3dar7 Need your help guys. I have switched back to Oreo after my brief stay on Pie. I have made a Github issue regarding this here https://github.com/topjohnwu/Magisk/issues/668
The dev has replied and is asking for the value of on an UNROOTED (Magisk uninstalled) Pie. Could someone perhaps provide this info to the ticket contained above, to get a resolution to this issue?
Click to expand...
Click to collapse
Here is the output in a text file. Had one of my friend pull it out from his TA-1046 Global ROM Pie Stable, September patch.
I hope it helps (◕‿◕)
Edit: Commented on github with pastebin link. There already was one but I saw more lines on mine who decided to post it anyway
@k3dar7 @Gravemind2015 Many thanks Hopefully, this will lead to a fix so that Magisk properly supports our device on Pie sans the glitches.
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Doktaphex said:
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Click to expand...
Click to collapse
I install and active this module.... And nothing happens.... Gesture Navigation is still missing...
siberflyers said:
I install and active this module.... And nothing happens.... Gesture Navigation is still missing...
Click to expand...
Click to collapse
Strange. It worked for me, not that I was searching for a solution, so I thought that I would share my experience
Doktaphex said:
If you use the PIX3LIFY mod, it will re-enable all missing gestures.
Click to expand...
Click to collapse
You are a WIN, thx Work for me, missed gestures is back with Magisk/MagiskManager installed...
edit: add screenshot of Magisk/Modules
braveheartleo said:
@k3dar7 @Gravemind2015 Many thanks Hopefully, this will lead to a fix so that Magisk properly supports our device on Pie sans the glitches.
Click to expand...
Click to collapse
your issue be closed, but if i try magisk canary build 9592a69 then see problem not fixed, can you please try?
and if too have still problem with missed gesture (without forkaround with PIX3LIFY), then please reopen issue?
k3dar7 said:
your issue be closed, but if i try magisk canary build 9592a69 then see problem not fixed, can you please try?
and if too have still problem with missed gesture (without forkaround with PIX3LIFY), then please reopen issue?
Click to expand...
Click to collapse
Unfortunately, I can't do that atm. I'm on Oreo right now and I'm not moving up to Pie. I'm afraid you'll have to ask the others to try it out, and if they too concur with your experience, then I'd gladly reopen the issue. ?
braveheartleo said:
Unfortunately, I can't do that atm. I'm on Oreo right now and I'm not moving up to Pie. I'm afraid you'll have to ask the others to try it out, and if they too concur with your experience, then I'd gladly reopen the issue. ?
Click to expand...
Click to collapse
i think if you not have now Pie, then i wait if someone confirm/disprove and i reopen own issue
btw: actual (1.7.4) version Pix3lify stop working (=not enable missed gesture), i not have installed other version before than 1.4.3, reinstalled this (1.4.3) manualy from Download(if have installed this version before) folder working
With Pie Nobember update is now NOT need workaround using Pix3lify 1.4.3 mod...
now gestures is simply not blocked with installed Magisk (17.3 which is version BEFORE (not working for me) patch on Magisk side)
Related
Dunno where else to put this but so far none of the unofficial xposed solutions support the pixel phones because no one seems to want to work with the A/B file layout so if anyone here wants to pick up a project id greatly appreciate that one and i know ive seen a number of others asking for it in different magisk and unofficial xposed threads. Thanks for reading my post and potentially contributing to a fairly noble cause.
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
alladinscastle said:
Unknown if this is a pixel success. Anyone who knows please do reply.
https://www.xda-developers.com/official-xposed-framework-android-nougat/
Click to expand...
Click to collapse
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
KittyRgnarok said:
Doesn't support A/B partition layout yet. No version of xposed except magisk systemless will even flash and even then the magisk systemless xposed also doesn't seem to work right for pixel phones yet
Click to expand...
Click to collapse
The couple of xposed modules I tried seemed OK (Greenify, youtube adaway...). I just didnt like it because it seemed to break Facebook and Facebook Messenger Apps (caused constant crashes for some reason) and also broke SafetyNet too, which defeats the purpose of even using Magisk. But overall you're most likely correct the modules still need to be updated for Nougat.
Damn...and I was so thrilled when the Nougat version came out.
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
cgrimm9 said:
Guess I stick with rooted Oreo was thinking about reinstall nougat cause of framework but sounds like it's not that great for pixel
Click to expand...
Click to collapse
Yeah xposed was my main reason for rolling back but for me none of the modules were being read as properly activated. Its fine though because I have my custom ROM back since there aren't any for Oreo yet.
A thread at pixel xl is saying yes and no with various install methods
UPDATE: added pie controls from xposed to my pixel running RR ; )
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
If you haven't already replaced SuperSU with Magisk, do that.
ItWasAllIntended said:
If you haven't already replaced SuperSU with Magisk, do that.
Click to expand...
Click to collapse
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Sent from my Pixel using XDA-Developers Legacy app
piperx said:
Well, choice is good, choice is what it should be, glad I have a choice to use what I want.
SR5-SuperSU-v2.82-SR5-20171001224502
Click to expand...
Click to collapse
I highly recommend switching to magisk at least until we get a proper non magisk Xposed and this is coming from someone who has used SuperSU their whole life
KittyRgnarok said:
Resolved: Systemless Xposed (SDK25) module in magisk now flashes and sticks without fail. Installing the modded Xposed provided in the module description allows the framework/app/modules to interface properly. With both the Systemless framework and the modded app all modules updated as of this month will work
Click to expand...
Click to collapse
Works on Oreo?
xneuromancer said:
Works on Oreo?
Click to expand...
Click to collapse
No nougat only, Xposed is not supported on Android Oreo at all yet
Q: I haven't received the lastest security update, how can I get it?
A: Just wait. Updates may take up to two weeks to reach your smartphone.
Edit: there's now an official way to force install updates:
Download and install the latest version of Google Play Services - it's an official signed version, 12.2.17 (448-186052348) (12217448).
Check for updates - you'll receive an update immidiately.
Q: What's the current build number?
A: As of March 1, 2018, the current build is OPR1.170623.026.V9.5.4.0.ODHMIFA Security patch level: February 1, 2018. Kernel version: 3.18.66-perf-g90e3040 [email protected] #1 Mon Feb 26 11:58:45 WIB 2018
Q: Does Picture in picture mode work?
A: It does but only a few apps currently support it: e.g. VLC (it must(!) be enabled first in VLC settings), Google Chrome (for desktop mode), YouTube (YouTube red subscription is required), Google Maps (only in navigation mode) and WhatsApp (during a video call).
Q: What are the known bugs?
A: Check this topic.
Q: Where can I get a firmware image to flash offline (fastboot ROM)?
A: Check this page for updates.
Q: Are there EIS or Camera2API? Has low light camera performance been improved?
A: Sadly, both are still missing and low light camera performance is still horrible.
Q: How can I improve low light camera performance?
A: Root your phone, enable EIS/Camera2API, install Google Camera with HDR+.
Q: Can I use/install Google Camera with HDR+?
A: No. (Yes, if you're willing to root your phone and enable EIS/Camera2API).
Q: I've heard about Quick Charge in Oreo, is it indeed present?
A: No, this has been verified by many people, some of whom used multimeters.
Q: What about the Google Phone (dialer) and Google Messages apps?
A: They are now both stock straight from Google.
Update: The latest version of Google Phone is incompatible with the MI A1 for unknown reasons but it's Google who made this decision.
Q: How can I hide the X mark for mobile networks?
A: You can disable WiFi or you can install a substratum theme, "Hide X".
Q: My favourite app or game crashes under Oreo.
A: Factory reset your phone, install just this game/app - check if it crashes. If it does, contact its developer. If it doesn't then some other app or your settings have broken the app/game.
Q: How can I disable/hide/remove App is running in background notification?
It's a "feature" of Android 8. There are three methods to get rid of this nuisance.
Source: http://en.miui.com/thread-1316545-1-1.html
Please share you tips in this topic.
How to root Oreo,?
mhdsanto85 said:
How to root Oreo,?
Click to expand...
Click to collapse
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.
birdie said:
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.
Click to expand...
Click to collapse
Does It wipe?
And how to go back to stock again to receive otas?
mhdsanto85 said:
Does It wipe?
And how to go back to stock again to receive otas?
Click to expand...
Click to collapse
No. If you install Magisk you will be able to receive and install OTA updates. You'll just have to reinstall Magisk after each update.
birdie said:
Unlock bootloader, flash/boot using TWRP, install Magisk or any other sudo solution.
Click to expand...
Click to collapse
There is not fully working TWRP for Oreo as of now.
Magisk can be used by flashing patched boot.img, which already contains Magisk or follow a bit complicated TWRP guide.
birdie said:
No. If you install Magisk you will be able to receive and install OTA updates. You'll just have to reinstall Magisk after each update.
Click to expand...
Click to collapse
Are you sure about this?
I got this Decryption Unsuccessful on side B (updated to Oreo on side A), while the side A is working just fine. Can anyone assist me with this?
varben said:
Are you sure about this?
Click to expand...
Click to collapse
You have to restore stock boot before OTA installation, currently that's possible probably only manually.
tensaigandy said:
I got this Decryption Unsuccessful on side B (updated to Oreo on side A), while the side A is working just fine. Can anyone assist me with this?
Click to expand...
Click to collapse
Oreo changed the encryption scheme, only the latest TWRP version or Oreo system supports it. Nougat system and older TWRP versions will have problems with decryption.
_mysiak_ said:
Oreo changed the encryption scheme, only the latest TWRP version or Oreo system supports it. Nougat system and older TWRP versions will have problems with decryption.
Click to expand...
Click to collapse
I tried flashing my phone with latest Nougat, both locked and unlocked bootloader. All fine and good, then I updated to Oreo on my partition B. Worked just fine but I cant boot into partition A as the encryption failed.
Not sure what I have to do on my phone.
Has anyone noticed this thing where if we open a slightly darker or dark image, the display boosts up the brightness in the dark areas ? Sort of like the sunlight display on some phones. I tried to record an instance but it doesn't show it clearly.
https://gfycat.com/MemorablePotableKarakul
Is it just me or Has anyone else noticed it ? Is it something that's built-in or can I disable it ?
Ok so my A1 is rooted bootloader unlocked but for some reason the google camera is not working on this and it used to work on 7.1.2 i enabled HAL3 but still no result can anyone help me
tensaigandy said:
I tried flashing my phone with latest Nougat, both locked and unlocked bootloader. All fine and good, then I updated to Oreo on my partition B. Worked just fine but I cant boot into partition A as the encryption failed.
Not sure what I have to do on my phone.
Click to expand...
Click to collapse
What are you trying to do? Once you upgrade to Oreo, you can't safely boot Nougat system. Even if data wouldn't be encrypted, many apps would force close due to changes between these systems. If you want to downgrade, factory reset is probably inevitable.
_mysiak_ said:
What are you trying to do? Once you upgrade to Oreo, you can't safely boot Nougat system. Even if data wouldn't be encrypted, many apps would force close due to changes between these systems. If you want to downgrade, factory reset is probably inevitable.
Click to expand...
Click to collapse
I dont know LOL
So A/B partition thingy is not a thing anymore on Oreo ?
tensaigandy said:
I dont know LOL
So A/B partition thingy is not a thing anymore on Oreo ?
Click to expand...
Click to collapse
There are still A/B partitions. Could you describe what are you trying to achieve? I simply don't understand why do you try to boot into Nougat once you have successfully upgraded to Oreo.
can future security updates fix these issues as well? monthly updates are provided by google or xiaomi? please answer and add this info to original post
sarfaraz1989 said:
can future security updates fix these issues as well? monthly updates are provided by google or xiaomi? please answer and add this info to original post
Click to expand...
Click to collapse
I could have added the answer but I don't have it.
It is somehow possible to hide/disable update to Oreo? My phone is not rooted.
What about this?
Hey I installed the RROS ROM and everything works fine except one thing.I cant find the fingerprint option on setting menu to set up the fingerprint scanner.
Any ideas how to fix it?
Did you remove fingerprints before you flashed rros
Hi, did you install additional magisk?
makiscfu said:
Hey I installed the RROS ROM and everything works fine except one thing.I cant find the fingerprint option on setting menu to set up the fingerprint scanner.
Any ideas how to fix it?
Click to expand...
Click to collapse
The Latest Magisk Does Not Work Good With RROS Or Other Roms, Magisk 14.0 Wil Work On Fingerprint,
The latest magisk will not allow you to use Fingerprint or add password.
But magisk 14.0 allows that
SuperSwordSmasher said:
The Latest Magisk Does Not Work Good With RROS Or Other Roms, Magisk 14.0 Wil Work On Fingerprint,
The latest magisk will not allow you to use Fingerprint or add password.
But magisk 14.0 allows that
Click to expand...
Click to collapse
16.7 works PERFECTLY on mine. You really need to stop assuming things don't work for everyone just because you have an issue
agraceful said:
16.7 works PERFECTLY on mine. You really need to stop assuming things don't work for everyone just because you have an issue
Click to expand...
Click to collapse
I Mean Like Putting A Password or fingerprint with like the latest magisk
When i downgraded to magisk 14.0, fingerprint and passcode started working
agraceful said:
16.7 works PERFECTLY on mine. You really need to stop assuming things don't work for everyone just because you have an issue
Click to expand...
Click to collapse
Nice to see. Will try this version. I have same problem. For me no version higher than 14 worked. Tried nearly every version and I already asked in Magisk and RROS threads but ... anyway.
Thanks for the info.
Sent from my FRD-L09 using XDA Labs
EDIT: As I expected, it didn't work. Also with 16.7 beta no fingerprint sensor - and I don't know why. Only Magisk14 is working. Already tried clean flash.
Any help with this is very appreciated and I can provide logs and more information, of course.
Here is a bunch of some older logs: https://drive.google.com/folderview?id=1nTIPHsn7QazdVCVYmX_zxwrSLrz8Z4IV
And here are some newer: https://drive.google.com/folderview?id=1lXAj5-61qVz9T50i5bsnDQvXUnunYaCd
I found out that there is no proper thread on Honor 9 Forum talking 'bout Treble ROMs,
from XDA forum and Openkirin team.
I wish this thread working as place for discussing about Issues and Fixes.
To start, Here's my personal result and infoes from replies.
It's not based on most recent version so plz report with your flash date or version No.
Waiting for report from Lineage, AOSIP, Omni, or others.
or issues about system, Xposed, SU, anything.
I'll edit OP with your reports.
RROS By mracar 07.28
Working
System
Magisk 16.7
Fingerprint
Issues
none.
Havoc OS By EnesSastim 07.25
Working
System
Magisk 16.7
Fingerprint
Issues
Huawei Quick-charge not working.
Havoc OS for HI3660 By Wirmpolter 08.09
Working
System
fingerprint
Issues
not working home button
on-screen nav bar is laggy
AOSP Phh-Treble By phhusson 07.03
Working
System
phh's SU
Fingerprint
Issues
none.
Pixel Experience By jhenrique09
Working
System
Magisk 16.6 16.7
Xposed
Issues
Volte
Fingerprint (maybe not)
AEX 5.5 By TingyiChen
Issues
Not working.
dotOS By mohancm
Issues
Not working.
ArrowOS By bauuuuu
Working
System
Issues
Can't mount external SD card with MTP
Omni ROM by Openkirin 07.22
Working
System
Issues
.
UPDATE : OP moved to Honor View 10. No more update will come.
Still, most of tips can be used to other Honor devices, so I will let this and other posts be.
It was nice to discuss about treble ROMs with you guys
I'll use here as TIP posting, mostly the basic ones.
1. Here's simple guide for magisk and stock camera.
UPDATE: add some tips about 9.0 GSI
https://forum.xda-developers.com/honor-9/how-to/guides-magisk-root-8-1-stock-camera-t3816078
2. TWRP for 8.1 GSI - Magisk, Gapps and re-stock tool. (mostly it's fine with just flashing stock system.img)
https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
no proper TWRP fro 9.0 GSI so far.
3. Use Huawei Update Extractor to extract SYSTEM, RAMDISK, RECOVERY_RAMDISK, KERNEL. don't forget to uncheck 'verify header checksum' at settings.
4. AudioFX app will break your earphon jack, so disable/unintall/delete it.
5. qemu.hw.mainkeys=1 to remove nav bar
6. /vender/usr/keylayout/fingerprint.kl to change fingerprint gesture.
TASON42 said:
I found out that there is proper thread on Honor 9 Forum talking 'bout Treble ROMs.
I wish this thread working as place for discussing about Issues and Fixes.
To start, Here's my personal result and infoes from replies.
It's not based on most recent version so plz report with your flash date or version No.
Waiting for report from Lineage, AOSIP, Omni, or others.
or issues about system, Xposed, SU, anything.
I'll edit OP with your reports.
RROS By mracar
Working
System
Magisk.
Issues
1. Sound awkward with earphone. fine with bluetooth or speaker.
2. Play Store not working properly. Need to manually restart everytime to start downloading apps.
Pixel Experience By jhenrique09
AEXBy TingyiChen
Issues
Not working.
AOSP Phh-Treble By phhusson
Working
System
phh's SU
Issues
None.
Click to expand...
Click to collapse
:good:
received report that Pixel Experience is working.
Need re-confirm, more information about magisk, xposed, issues, etc.
TASON42 said:
received report that Pixel Experience is working.
Need re-confirm, more information about magisk, xposed, issues, etc.
Click to expand...
Click to collapse
Magisk 16.7 work
Xposed work
Volte don't work
Fingerprint unlock don't work
phh's AOSP issue; Sound from Speaker no matter you plug earphone or not.
Not sure this is real issue or not since it's first time. I'll update after while.
UPDATE: Found out earphone is not working on phh's AOSP,
My earphone hardware is fine with stock one, so I guess it's sotfware issue.
Anyone have same problem? Anyone had and solved?
UPDATE: I did factory reset several times and dying earphone jack problem happens randomly.
You can't fix it without full wipe and re-install via fastboot and I don't know what's the trigger...
TASON42 said:
received report that Pixel Experience is working.
Need re-confirm, more information about magisk, xposed, issues, etc.
Click to expand...
Click to collapse
Boots only with magisk 16.6 (maybe 16.7 as well)
For me I wasnt able to access internal storage,not knowing why.
My fingerprint works well tho.
Previously on STFAL10 8.0.0.350,it is a AL00 but the OEMINFO got wrong before.
Sent from my Honor 9 using XDA Labs
Is there an 100% working TWRP? I know fastboot works, but twrp makes live easier.
Thanks
hujialun2002 said:
Boots only with magisk 16.6 (maybe 16.7 as well)
For me I wasnt able to access internal storage,not knowing why.
My fingerprint works well tho.
Previously on STFAL10 8.0.0.350,it is a AL00 but the OEMINFO got wrong before.
Sent from my Honor 9 using XDA Labs
Click to expand...
Click to collapse
Thx for the report.
accessing internal storage, means?
you mean MTP with usb connection to PC,
or TWRP backup, or typical file manager?
not working TWRP is normal, broken MTP happens, but never heard about not working file manager..
Saftpresse99 said:
Is there an 100% working TWRP? I know fastboot works, but twrp makes live easier.
Thanks
Click to expand...
Click to collapse
Since encryption one internal storage is not open yet, so there is no internal-storage-backup-capable TWRP right now.
But you can back up or flash things with and at external SD card, So it's working tho.
TASON42 said:
Thx for the report.
accessing internal storage, means?
you mean MTP with usb connection to PC,
or TWRP backup, or typical file manager?
not working TWRP is normal, broken MTP happens, but never heard about not working file manager..
Click to expand...
Click to collapse
The third one
It seems data partition is inaccessable on phone.In file manager it said content is inavailable the moment (or something like that).In browser when trying to download something it said selected location is inaccessible.Didnt try MTP but TWRP got stuck at splash screen.
It appears that AL varients is crappy when it comes to Treble...or it is something wrong with my device perhaps:crying:
Sent from my Honor 9 using XDA Labs
TASON42 said:
Since encryption one internal storage is not open yet, so there is no internal-storage-backup-capable TWRP right now.
But you can back up or flash things with and at external SD card, So it's working tho.
Click to expand...
Click to collapse
Thank you.
If i understand you correct, only backup/restore isn't working? Flashing (rom, gapps, magisk) and wipe (cache, data, system) works? Which TWRP should i flash?
Have you guys tried the overlays posted by dilemma in our forums? Do they fix issues like sound issues you mentioned earlier?
hujialun2002 said:
The third one
It seems data partition is inaccessable on phone.In file manager it said content is inavailable the moment (or something like that).In browser when trying to download something it said selected location is inaccessible.Didnt try MTP but TWRP got stuck at splash screen.
It appears that AL varients is crappy when it comes to Treble...or it is something wrong with my device perhaps:crying:
Sent from my Honor 9 using XDA Labs
Click to expand...
Click to collapse
You can try rebrand again, maybe...
Saftpresse99 said:
Thank you.
If i understand you correct, only backup/restore isn't working? Flashing (rom, gapps, magisk) and wipe (cache, data, system) works? Which TWRP should i flash?
Click to expand...
Click to collapse
I used TWRP from this forum, made by swiss flag man (I can't remember his name, but thread name is something like TWRP + capative fix)
you can't directly flash TWRP from 8.1 treble GSI (which will malfunction), but you can use TWRP by flash from 8.0 stock (maybe custom ROMs too) and flash GSI.
Double Chin Bigot said:
Have you guys tried the overlays posted by dilemma in our forums? Do they fix issues like sound issues you mentioned earlier?
Click to expand...
Click to collapse
specific URL, if you can....?'
UPDATE: I was too lazy to find what thread you were talking about back then, now I found the thread you talking about, but I think this overlay has nothing to do with sound issues.
It will be really thxful if you try and report tho.
TASON42 said:
You can try rebrand again, maybe...
Click to expand...
Click to collapse
Is there any chance that you sent the OEMINFO for STFAL00C00 to me?The one in HWOTA Is for AL10 and I didn't find the proper one
hujialun2002 said:
Is there any chance that you sent the OEMINFO for STFAL00C00 to me?The one in HWOTA Is for AL10 and I didn't find the proper one
Click to expand...
Click to collapse
Sorry man I don't have one, but I think you might be able to backup one by yourself with TWRP or Root file explorer, those things are working fine whatever legion code is, isn't it?
TASON42 said:
Sorry man I don't have one, but I think you might be able to backup one by yourself with TWRP or Root file explorer, those things are working fine whatever legion code is, isn't it?
Click to expand...
Click to collapse
I didn't backup and now it Is corrupted and it displays AL10
Sent from my Honor 9 using XDA Labs
hujialun2002 said:
I didn't backup and now it Is corrupted and it displays AL10
Sent from my Honor 9 using XDA Labs
Click to expand...
Click to collapse
There are some discussions about rebranding AL00 to AL100 to Cxxx at the thread, if I remember correctly.
If your OEMinfo is totally pooked up, you won't see AL10 either so I think you successfully rebranded your phone to AL10, at least...
I'm using L09 not AL variants, so I can't help you much but wish you good luck.
Testing ArrowOS, only rom without earphone problem, for now, to me, at least.
It has no Gapps, so I'm currently using my phone as ArrowOS + dirty flash phh's AOSP.
Also I would love to have some report about AEX 5.7 By AryanPatidar,
And my honor 9 don't boot up with Pixel Experience, which is not matching with report...
TASON42 said:
Testing ArrowOS, only rom without earphone problem, for now, to me, at least.
It has no Gapps, so I'm currently using my phone as ArrowOS + dirty flash phh's AOSP.
Also I would love to have some report about AEX 5.7 By AryanPatidar,
And my honor 9 don't boot up with Pixel Experience, which is not matching with report...
Click to expand...
Click to collapse
Flash Magisk 16.6 and PE will boot!
Sent from my Honor 9 using XDA Labs
Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Edit: Thanks for all the responses..using canary magisk instead has worked.
chinbags said:
Hi guys,
Sorry if I'm missing something very obvious but I can't install the latest update on my rooted oneplus 9
I have a LE2110 model, currently on 11.2.10.10..LE25BA. I'm rooted with magisk, confirmed with root checker.
I've downloaded the C44 update, went to updater, install from storage, then to magisk where I disable all my modules and select install to inactive slot, 'lets go' and 'reboot'.
The phone reboots and displays a message saying that the update did not install try again or try reapir.
Anyone know if I'm missing anything in the process? Any help would be appreciated.
Cheers everyone
Click to expand...
Click to collapse
You have to fastboot flash the stock untouched boot.img back. Magisk patched the boot partition to root. Therefore the partition is modified. Ota fails. Try uninstall Magisk and see if it restores stock boot image. Or get full build run payload him through payload extractor and nab boot.img there.
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
Wrong magisk was used. You must use canary magisk.
MrSteelX said:
Wrong magisk was used. You must use canary magisk.
Click to expand...
Click to collapse
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
in order for magisk to work on A12 and booting to an inactive slot it has to be the alpha build ill post it but its also in the root guide for oos on 12 the table shows the only one that works on 12 is this build, same thing happened to me
chinbags said:
Thanks, so I basically need to unroot, restore to stock, update to C44, then reroot from scratch again?
Click to expand...
Click to collapse
no need for any of that
mattie_49 said:
Wrong . I'm on stock A12 and it's rooted with 23.0. passing safety net,modules,Magisk hide all working
Click to expand...
Click to collapse
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
MrSteelX said:
yes it is true but you did the manual way. every one else wants the automatic way which requires canary or alpha.
Click to expand...
Click to collapse
Everyone does want bleeding edge.
Thanks for all the info guys, sounds like a bit more reading needed on my end but all of the above should steer me in the right direction.
I was able to jump from rooted 11.10.10 to c44 using canary magisk.
Downloaded the 4gb c44 from oxygen updater, then local udpate and DONT reboot then install magisk in inactive slot.
Ok, this has worked, original posted uodated, thanks everyone.
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
chinbags said:
One last question...and slightly unrelated. I can't find my list of hidden apps in magisk. I've hidden the app in settings and have the magisk hideprops config module enabled. My banking app is telling me I'm rooted...I'm pretty sure I added it to a list in the past. None of the options at the bottom bring me to it either..anyone have the same issue?
Click to expand...
Click to collapse
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
jruizdesign said:
the alpha build doesnt have magisk hide built in. and he literally just posted the updated v24 stable build an hour ago and is supposed to fully support android 12. but he also announced that he removed Magisk hide all together and is no longer going to support it.
so its still early, not sure how to fix your problem , those are the only two builds i see for 12
Click to expand...
Click to collapse
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
chinbags said:
Ok, thanks. Could a rollback to v23 APK work? Happy to give it a whirl unless you think it could bork my phone
Click to expand...
Click to collapse
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
jruizdesign said:
i would try and delete the version you have and install stable 23, dont repack the boot.img or anything only replace the app, that wont hurt you
Click to expand...
Click to collapse
No dice, v23 will install and the option is available in settings, I just still can't find where I add an app to the hidden list. Bank apps not loading.
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com
Have you tried using USNF? https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/
I'm also having troubles updating to c44 with magisk v23, but don't wanna lose the magisk hide option. While looking for alternatives, I came across this the USNF solution in here :
How to pass SafetyNet on Android after rooting or installing a custom ROM
It is possible to pass SafetyNet, even after extensive modding like rooting or installing a custom ROM. Check out how to do that here!
www.xda-developers.com
Didn't try it myself yet...
I can confirm USNF works for me, and I have some very strict apps detecting root access, DenyList hides the root from the apps, but it doesn't try to fix safetynet, with USNF I have no more problems even in apps that didn't work with DenyList only (remember to turn on Zygisk and Enforced DenyList).
If you are using permissive mode on SELinux you will also need SELinux switch to get back to enforcing mode for some apps, but that is an edge case
EDIT: It seems if you are on custom ROM MagiskHidePropsConf might help, not sure if USNF is enough but I can't test it