Related
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
cl0g said:
Hi guys,
i tried some Roms for my op3 (sultans 14.1 / OOS OB) and always got WiFi problems, when installed Magisk + some modules. (Google Assistant Enabler and Dolby Atmos Lenovo with audiolib v4)
Running Magisk alone, it did not has problems. Also it seems that the problems came with Android 7, but unsure.
Could only be fixed by clean flashing the rom (dirty flashing and uninstalling Magisk did not help).
Someone can explain, how it is possible?
kmsg was something like wifi couldnt suspend device, and did a random reboot. before it rebooted it could not connect to any WiFi-network.
if needed, i can add some more complete logs
Code:
[ 324.876840] PM: Some devices failed to suspend, or early wake event detected
[ 325.063045] legacy_suspend(): wiphy_suspend+0x0/0x68 returns -11
Click to expand...
Click to collapse
Remove all modules and reboot into recovery.
Wipe caches and reboot.
I have found that I can end up with WiFi, Bluetooth, SIM issue if something happens with the modules.
Before I figured out what it was, I was re-installing the ROM, etc.
Try just deleting the modules and wiping the caches and rebooting.
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
cl0g said:
@tech_head
Thanks for your answer, but this was unnecessary.
I did not ask for a solution to resolve this on my phone, but a explanation, how Magisk(+modules) mess with kernel/firmware or something.
If you read the whole post, then you would have seen, that it was fixed by clean flashing the Rom.
Thanks anyway.
Click to expand...
Click to collapse
Hi,
I actually did read the whole post and was offering a solution that DID NOT require re-installing the ROM.
I'm not 100% sure why the problem persist but I have seen it affect Bluetooth, Wireless and SIM recognition.
Typically it happens after a reboot. Wiping the cache on my phone causes it more than 50% of the time if I don't disable modules first.
I don't know why it happens but you are right, removing Magisk does not solve the problem.
There is something corrupted in the data partition and the only way to clean that up is to remove the modules and wipe the cache or do what you proposed.
Nevermind
I recently had the same problem. I'm currently trying to fix it without reinstalling. I've uninstalled all modules, cleared both caches and still no wifi and I'm getting random crashes. Has anyone found fix a reliable fix?
While posting, I tried resetting my network and everything started working again. If this happens again, I'll try that first.
BTW
Also, it happened after a failed installation of Crossfire and Tethering, both thru Magisk. Tethering actually installed but after the reboot, I've got no wifi.
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
mellus said:
I was able to fix the wifi problem by following this tutorial: https://************/root-razer-phone-fix-wifi-root/
But: JUST UNTIL INSTALLING TWRP INSTALLER. Until this step I got a working wifi (I am on Android Pie Custom rom). After flashing Magisk v18 or v19 same problem as before: No more wifi. Su installer does not work on my Razer Phone 1 ( failure while patching sepolicy, no permission ), so what to do? Any hints?
Best regards and thx in advance
Michael
Click to expand...
Click to collapse
Ugh. I'm having the same issues after upgrading to canary channel Magisk 20.4 on my Razer Phone 2. My WiFi was rock solid on the previous version, but for some reason my WiFi now flashes on and off like a strobe. Weirdly, it doesn't seem to have the issue at my house, but it constantly craps the bed at my work. The work connection is 5Ghz and my home one is 2.4Ghz, so that could be a difference. However, before my attempted upgrade, both worked perfectly.
I tried uninstalling my Magisk modules, flashing the Razer stock boot image, wiped Dalvik cache, flashed Arter/TWRP boot image, Arter kernel zip, Magisk 20.3 stable and reactivating modules. No change at all. WiFi is still garbage.
Are you telling me I'm going to have to flash the entire stock image and wipe my phone to get back full functionality?
im having the same problem, on miui i tried tp downrage magisk, that worked. currebtly searchin best way to downrage cause i forgot what i did. but if anyone stuck at this problem:
Without data wiping (luck method):
Remove modules
Reboot into recovery
wipe caches
reboot
done
Downrage magisk (maybe not fix):
Uninstall ALL modules
Delete Magisk from the app
flash downrage magisk
(eg. uninstall 24.1, install 23.0)
wipe caches
reboot
done
Data wiping (i forgot about should we flash magisk via magisk app with recovery mod on, if this dont work try enabling recovery mode):
Just Re-install Magisk via recovery
Clean everything BUT leave boot not wiped
flash rom WITHOUT boot
let it 10-30 minutes booting
go to recovery
flash rom's stock boot
reboot
finish rom's installation
install MAGISK APP
confirm additional installation
reboot
done
So here are a few things I have been through in the past 48 hours:
I flashed a custom ROM (FreedomOS) for the 3T. Could not get OK Google to work and it is essential to me especially when driving. Other people had mentioned every custom ROM was like this at the moment so I made the switch back to factory. This is where the hell begins. I wanted to try out Magisk so I could play Pokemon GO and use Android Pay, and I thought "oh what a perfect time to do just that". 4 hours of work and the SafetyNet was still tripping, only to find out I needed Magisk 13.0, which is incompatible with the OP3T boot image. Now, that could have been because I installed SuperSU prior and that patches the boot image but I had been through enough to the point of just going stock with SuperSU only. So about 10 dirty flashes later and a few hours of waiting for TWRP to load (F2FS can suck my @#$*), I find out that if you don't want to lost your data partition, there is only one very specific way to install SuperSU.
1) Wipe system and caches
2)Install OOS full rom
3)Boot into OS
4)Reflash TWRP (because OOS removes it)
5)Flash SuperSU
6)Boot into OS again
7)THEN, and only THEN can you install additional things such as ARISE or custom fonts
It appears after you flash the factory ROM through TWRP, TWRP loses all commands. So anything flashed after that doesn't actually do anything. I thought maybe it was because the new recovery is there and so maybe TWRP just needed to be reflashed before the OS was even booted, that however, resulted in a beautiful slew of corrupted fonts, no root access and broken hardware keys (even the power button). So please, learn from this XDA users, as I have the hard way. Now I'm off to go change F2FS to EXT4, fun stuff.
EDIT: On top of everything I just said, it seems none of the SuperSU zips are working now. Does not affect my phone whatsoever. It's almost like it isn't mounting /system...
EDIT 2: Great. Rooting now bootloops me and the logcat is saying AtCmdFwd service errors and BindNDK sensor server unavailable. I'm going back to FreedomOS and will just suffer from never having OK Google again.
EDIT 3: FreedomOS no longer even starts booting. Stuck at bootloader logo. Guess I'm flashing stock OOS unrooted for now. Going to have to deal with ugly default fonts and crappy audio
Try blusparks twrp for OnePlus 3t.. that fixed a lot of my issues with flashing, instead of supersu try magisk instead.
Install twrp - OOS - Magisk - Kernel - what ever else.. but see if it boots. If not, try holding the power button for 12-15 seconds until the screen goes black but the notification led turn red.. plug your phone into the computer and do a unbrick from there with the msm tool.. once it all boots, flash a custom rom over the stock rom and then factory reset from there, I'm just throwing ideas out there.
1. Factory reset.
2. Install official OOS.
3. Reboot to recovery.
4. Install TWRP.
5. Install Magisk, custom kernel, debloater etc.
6. Reboot to OOS.
When upgrading to newer OOS version, skip factory reset. I never wipe caches and everything works. If safety net fails, check that hide is enabled on Magisk settings. If still failing, use Universal SafetyNet Fix.
Forget SuperSu, Magisk does same thing. And with Magisk you can play PoGo. Forget EXT4, it doesn't give you anything, it's going to be history.
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Solved
xKroniK13x said:
Where are you getting that Magisk 13 is incompatible? I'm currently running OB10 with Magisk 13 and ElementalX kernel. Rooted, SafetyNet pass. @heiskanenej instructions above sound like what you need to do. Start fresh.
Click to expand...
Click to collapse
Ok, I will eventually try blu_sparks TWRP (that was the plan anyways), but I am back in working order. So Magisk did not bootloop my device, and v13 works on OOS. It wasn't working on FreedomOS but it even passes SafetyNet on OOS. I have ARISE and Dolby installed and couldn't be more satisfied. Did not have to wipe /data, it's like the whole thing never even happened. I will likely change to EXT4 as soon as I get the chance to backup my data partition, I haven't seen any benefit to F2FS whatsoever. Appreciate the tips, XDA rocks!
EDIT: Still takes forever to boot blu_spark TWRP but eh, I'll keep it. Will update when switch to EXT4, only reason to switch
I do the flashing in a rude way
1. Flash OOS from TWRP.
2. Flash magisk, arise, etc..
3. Reboot
4. Boot into recovery, flash any custom kernel etc..
Changing to ext4 is not required, if you are on OOS. f2fs is way better in performance over ext4 for the stock/freedom.
Sent from my OnePlus 3T using Tapatalk
We already know this phone is arm64,
the GSI rom AOSP v112 has support for this phone.
But how is the rom behave? What works and doesn't?
How are other GSI flavours doing? Like RR, AEX, HAVOC,....
[NOTE: For those who are interested i'll change this post to some GSI guide cepheus,
as soon as i recieve my Mi 9. But until then i'll hope for some of your feedback]
See this: https://github.com/phhusson/treble_experimentations/wiki/Xiaomi-Mi-9
and these two: https://forum.xda-developers.com/showpost.php?p=79284072&postcount=46, https://forum.xda-developers.com/showpost.php?p=79295919&postcount=53
It shoudn't be needed to write a guide
a video guide would be interesting
I usually used twrp to flash the Gsi file but now I didn't understand what steps should be taken
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
update: since Phh was ultra vanilla with literally 2 extra settings, tried RR, same greeting, no fp, and no swipe to apps there, i don't really beg for their modifications as i have Xposed Edge for this. Finally went back to Floko knowing how to fix gapps problem, it's got best navbar solution, although with tons of bugs (contradicting navbar user actions, non responsive gestures, nonresponsive buttons), no tap2wake, AOD sucks, fp sucks too, produces blinking screen.
Looks like trebles are unusable, time to go back to XIAOMI EU... so much for "don't need device specific ROMs".
doggydog2 said:
tried Foloko, RR trebles and it's entertaining as STDs.. couldn't add Gapps for hours and never managed to using 2 very different TWRPs we've got, tons of tricks, or adding stock system/vendor.
I don't understand the assumption "Please don't use third-party custom rom (e.g. Xiaomi.eu roms) as the base rom. Some hacky roms have wrong (unofficial) fingerprint and GSI can't detect what device you are using. ", ok, what should be in the phone then?
After some attempts Phh treble from post 60 installed, greeting me with "There's an internal problem with your device. Contact your manufacturer for details.", some vendor nonsense. After reboot i cannot log in, as fingerprint overrides the letter i need to type the password. omg. So i have to reflash.
Click to expand...
Click to collapse
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
dear mod please close this one, there seems to be already a conversation about this
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
tried to do that, tried to install arm64 Gapps, I'd get an error saying my system is arm, so i install arm gapps, they do get "installed", but when i reboot, there is no gapps at all.
edit: arm64 gapps worked when used LR.Team/wzsx150 twrp.
AndroPlus said:
You have to flash *official* MIUI rom (China or Global depend on your hardware, and it's better to flash developer version to get latest update).
To install GApps, you have to do Wipe -> Advanced wipe -> Select system -> Resize, then Mount -> mount system, then install GApps zip.
Click to expand...
Click to collapse
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
doggydog2 said:
which Global please? this is the link http://en.miui.com/download-361.html claiming to be Full Rom, but the zip is similar to EU version, just a patch.. just tried it, then flashed EU and magisk and getting "can't connect to camera". i was thinking i need to flash some bigger package (.tgz file), but there's none published and going throught the million childish looking forums on eu.miui.com, not sure.. would like TWRP way. perhaps format system?
Click to expand...
Click to collapse
You can find fastboot image here:
https://en.miui.com/a-234.html
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
thanks but both links redirect me to http://www.miui.com/ in chinese where i can browse to quasi-full roms again. strange.
btw i'm a fan of your kernel except it causes "can't connect to camera".. after many combinations of flashing i tried skipping the kernel (v01, or v02 or any kernel), and camera is back. however without Night mode this time...
update: found stable ROM at least https://c.mi.com/thread-1907373-1-0.html
update: somehow i trust this is the legit link to develop ROM http://bigota.d.miui.com/9.3.1/ceph....1_20190301.0000.00_9.0_global_cdb3885bac.tgz
AndroPlus said:
You can find fastboot image here:
https://en.miui.com/a-234.html
Click to expand...
Click to collapse
Hey,
Could you make your magisk patch to not require pressing FP scanner twice for FP to register?
Without the patch, works fine from first try, but with it, two presses at least are needed Everytime.
Thank you!
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
AZ_Miss_Murder said:
Hey everyone - long time lurker/researcher, but generally good at searching for answers without bugging anyone. This one has me stumped.
I have a Mi 9 CN model (6/128) that has been unable to make phone calls with the main mic without having to toggle Speakerphone on/off
I've tried 3 different custom roms (Xiaomi.eu, Pixel Experience, Evolution), and the Global MIUI 11 rom, but nothing seems to help fix it.
I have the newest version of TWRP installed right now (3.3.1-46), I have tried with and without Magisk installed....right now I don't even have TWRP installed at all on the Global rom.
Same happens for my SO's Mi 9 too as well.
Is there something I'm missing? I've tried turning off WiFi Calling/OK Google detection/VoLTE, rebooted, cleared cache/ cleared data inbetween new ROM installs....
Hardware test shows Main and Top as PASS.
Any tips would be appreciated! I feel like I've tried everything possible.
Thanks in advance~
Click to expand...
Click to collapse
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Laptapper said:
Your TWRP is right.
Try to flash syberia with recommended vendor exactly step by step and of course really clean install with formatted data yes.
If this isn't working I'll think you've got to flash via pc the stock and then again a custom ROM.
Click to expand...
Click to collapse
I'm actually going to follow the Evolution instructions (just missed the part about flashing EEA)
So i'm using MiFlash with the MIUI11 EEA boot rom file, then I'll do the normal TWRP -> format data -> install Evolution ROM and test.
Thanks!
So it seems like I'm completely out of luck at this point - I've tried basically everything I can think of, and I think something big must be wrong with the phone's file system.
I've followed Evolution's steps to a T (minus MiFlash having an error at the end of the EEA flashing, but the firmware seeming to load fine) and still run into the no Mic issue.
"Flash MIUI11 eea with miflash
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" (Download here)
Flash TWRP
Wipe (dont wipe system/vendor)
Format data
Reboot recovery
Flash rom
Reboot system"
Wipe (don't wipe system/vendor) I assume means just a normal factory reset wipe via TWRP, which I've tried.
I've tried both fw+vendor files (the newest for Android 10 and newest from Xiaomi.eu)
Any other last suggestions before I assumed the phone is broken?
Try to flash xiaomi.eu_multi_MI9_9.11.7_v11-10.zip
With miflash and after factory reset.
https://sourceforge.net/projects/xi...iaomi.eu_multi_MI9_9.11.7_v11-10.zip/download
SO! Update here
I was able to use Evolution X's Android 9 instructions to get everything working fine....but everytime I try to duplicate that for MIUI 11 it does not work.
Reboot to recovery
- Flash the latest 9.8.1 vendor image or full stock ROM.
- Reboot to twrp and format data
- Wipe cache/dalvik
- Reboot back to recovery and flash
I tested using the newest Xiaomi.EU Vendor for Android 10 and the stock one with no luck....more thoughts?
Did you try turning off the VoLTE?
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Leonvrx said:
Hi guys, I'm here looking for any help
I'm having this weird behavior in any custom rom I flash.
A while after flashing some rom (some 2 or 3 cycles of battery, around 1 to 3 days) suddenly all apps start crashing, falling at that force close popup. I mean every app, when I try to launch some new app it goes to the force close immediately.
I can't take a screenshot because it fails, I can't take a screen record because it crashes.
So I have to reboot, and it boots normally, but already happened that some apps loose their cache/data, because they start from zero and I have to log in again.
Happening on any A13 build, I don't remember about A12.
Can that be a hardware issue? I doesn't happen on MIUI.
Tried PE+, LO, CrDroid, ArrowOS, CherishOS, Voltage, Spark... Well, I'm trying it all.
Tried changing recovery: Kewl TWRP, TWRP, OrangeFox
Tried leaving phone on LTE only.
Tried flash fastboot MIUI before other rom.
Flashing all of them like: wipes, install rom, format data.
Does anybody has any idea?
Thanks and sorry about my english!
Click to expand...
Click to collapse
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Laptapper said:
Did you've formated DATA with yes and reboot recovery
Then flashed fw
and last the ROM?
I mean exactly like this?
Click to expand...
Click to collapse
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Wipe isn't enough, formating with yes is necessary.
Try exactly my procedure (fw isn't necessary for all roms / cherishos don't need, Los need)
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
Sheist! said:
Some ROMs installation instructions do not require an initial format of data before installation of the ROM itself, like EliteRom. Follow your ROM's installation instructions regarding required firmware. (MIUI)
Click to expand...
Click to collapse
Also elite rom need format data if encrypted (normally data is encrypted!)
Leonvrx said:
No i've rebooted to the recovery, wiped, installed firmware, installed rom, formated data.
But would this order change anything even to roms that say that don't need any specific firmware?
Click to expand...
Click to collapse
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Sheist! said:
If installing the EliteROM (for example), your formatting after installing the ROM is the correct procedure, per the declared instructions:
Installation Instructions:
- Install rom zip using TWRP/OFOX
- Format if you are encrypted, otherwise wipe data is enough
- Reboot
- Enjoy the smoothness+performance
Click to expand...
Click to collapse
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Laptapper said:
@Leonvrx
according my experience it's not important if you format before ROM or after Rom installation but very important to restart recovery when you do it before ROM installation in encryption state.
If decrypted then only wiping data
Please feedback your trying and results.
Click to expand...
Click to collapse
I didn't know that; thank you for your help, guidance, and patience.
Tried your steps exactly this morning, so far so good, I'll update in the next days, for better or for worse.
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Leonvrx said:
@Laptapper
Yeah, same results, it crashed the same (using AlphaDroid atm).
I've rebooted it and it even started initial android setup again, after redoing it, i have all my apps like nothing happened, but my sound settings, fingerprint settings (and probably other too) reseted.
I've also already tried to remove the microSD expation slot, same results,
Tried Vanilla + NikGapps, Vanilla + BitGapps and Gapps builds.
I think it's just bad luck with this specific device :/
Click to expand...
Click to collapse
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Laptapper said:
Which recovery?
Take this:
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Try cherishos with exactly my procedure above. Fw isn't needed!
Click to expand...
Click to collapse
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Leonvrx said:
I think that it's exactly this version, but I will reflash to make sure and I'll try again
Click to expand...
Click to collapse
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Laptapper said:
If not working then try this:
In orange fox recovery
format data with manually typing yes
reboot recovery
install cherish gapps rom
format data/yes Again
Start system
Click to expand...
Click to collapse
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Leonvrx said:
Ok, I'll try if happens again. Sometimes it takes 2 or 3 days to happen.
But I have a problem in Cherish that on my bank app (C6 Bank Brazil) my facial recognition doesn't work. It stays on a black screen despite I had given camera permission.
Click to expand...
Click to collapse
Playstore certified?
Rooted?
Cts matching?
Laptapper said:
Playstore certified?
Rooted?
Cts matching?
Click to expand...
Click to collapse
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Leonvrx said:
Non-rooted, CTS profile ok and certified.
It's a thing that just happen in this ROM.
Also this app is really annoying to hide root from, so I never root
Click to expand...
Click to collapse
Try kernelsu root
Then delete caches of playstore and Google play services.
Reboot
I've got non problems with banking and camera in cherish and kernelsu