So updated to the. 8 was fine, Google did restore as I wiped everything(fresh install) twrp and magisk installed. First problem I noticed is I flash install oreo remix boot animation via magisk or twrp but it refuses to change the boot animation of the no limit rom. I thought ok w.e, then I did the battery extend life by adb shell disabling what was listed and I download the jtool to set force 90hz. Now when I try to open these 2 apps this happens https://youtu.be/bCBSCmg2Gb4
So I did clean install back to stock. 7 and on no limit Tom, surprise had same issue again, by installing the June 18th smurf rom. Then I did local upgrade to.8 the issue went away, but came back as soon as I applied the no limit rom. Conclusion bad kernal version on.7 and the rom isn't supported on. 8?
Related
Updated my phone to the April update via flash-all.bat (w/out -w) and phone boots fine with TWRP 3.2.3, Magisk 18.1 & Elemental 2.15 installed.
As soon as I edit the build.prop to allow hotspot and reboot, the phone just sits at the Google logo screen.
Did something change in the April update? I've done this so many times and am really stumped...I've been using the same process of upgrading to a monthly update for like 2+ years, never had this issue.
Is there a section better suited for this question to get some eye balls on it?
I can't even downgrade back to the December release which was working fine for me. I've tried flash-all'ing December, February and March and all of them result in a corrupt system and no boot scenarios. The only image I can successfully flash and boot back into the phone is April, the latest one. I've even gone so far as to not flash a kernel and TWRP and only Magisk, but if I edit build.prop or drop in an already altered build.prop, the phone just sits at the G logo with the scrolling bar for 15+ minutes and I give up.
Someone please assist...
After many hours of trial and error, I resolved the issue. For some reason, when I had edited the build.prop file in FX File Manager (with root), it wasn't properly setting permissions (chmod 644). This is why the phone wasn't booting. I set these permissions via TWRP after making my changes and the phone booted fine.
Hello! I have had my One plus 7 pro international running for months now, rooted, following this guide https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368. I had the OTA update notification for quite some time now, but I ignored it because I was lazy. A few weeks ago my phone must have auto updated however, as I started noticing banner ads again that adaway usually blocked, and I have had a few other minor issues like GPS taking longer to connect or find where I am, wifi disconnects, and google not understanding what it usually does. Phone still works just fine, just minor issues I didn't really experience before.
I would like to completely reset the phone to clean it up, and re root and setup TWRP again, but im not sure how to safely do that since my phone was updated improperly (automatically). I have magisk still installed, but the modules dont seem to be working properly. Rebooting to recovery will reboot me to one plus recovery instead of twrp. When I restart is still says my boot loader is unlocked, and some apps (like chase mobile app) still say my phone is rooted. Oxygen updater says im up to date on OxygenOS 10.0.3.gm21aa.
What would be the best option for me to clean everything up, get my root modules working again, and have the phone fully up to date and stable? Any information would be greatly appreciated.
follow the same steps you followed first time. Boot to TWRP flash magisk, No need to factory reset. Flash twrp again if you want and reboot to system
Android 11 full release upgrade is available OTA now... downloading as I type this, just check for updates in Settings - System.
Anyone able to get chat bubbles working?
Also screenshot from the apps menu does not work unless full gesture or 3 finger btw..
Upgrade went ok in the end, but after an hr or more I had to reboot a couple of times to get it to complete. Was stuck 3/4 of the way up the progress bar. Stock/unroooted.
You need google Android messaging beta app to get bubble chats working. Currently using it now.
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
adm1jtg said:
Anyone get root working? I tried magisk canary and patching the boot.img from the latest update aka Android 11 final but it wouldn't boot
Click to expand...
Click to collapse
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
stompysan said:
Launcher settings are not sticking with gesture navigation again. Lawnchair is my default launcher, but it is still trying to open Pixel Launcher. This issue went away a while back in 10, but seems to be back in 11. This alone is enough to have me switch back.
Click to expand...
Click to collapse
I had this issue too, but I was using the traditional 3 button navigation. Every hour or so when I pressed home button it would want me to choose between Nova and Pixel launcher even though I already set Nova as default. Also after clicking the nav bar buttons, they would stay highlighted which was slightly annoying.
On top of these two minor bugs I just don't like Android 11 overall. I went back to AOSiP lol and I won't even bother updating past 10 custom ROMs until some custom ROMs based on 11 are available.
DriveEuro said:
No problems here. Used latest Canary to patch 11 boot.img. Flashed 11 full image. Let it boot up once. Rebooted to bootloader, flashed magisk patch boot.img. Booted up fine.
Click to expand...
Click to collapse
Would you mind uploading your patched boot image? For some reason it's not working for me. either and also did it the same way you described. Says the boot file is corrupted. Can boot with older patched kmages fine just no root though.
Edit* Nevermind I got it working. Took a few reboots and a couple more trys at patching and the patched boot image no longer was read as corrupted.
Still can't get it to work. Boots to Google screen then just goes back to bootloader screen. So far not liking 11 at all wanted to root it to make backups and maybe load aosip
Can someone link me to the canary build your using maybe i have an older one but it says it's for Android 11
Hello guys, I present the following problems: Bubbles WhatsApp does not work, internal audio in screen recording does not work, notification bar or navigation bar does not hide when opening Applications like fb or cod Mobile.
I cant save photos sent to me inside Facebook messenger & any screengrabs I edit vanish when I try to move them to another folder in Gallery, maybe this is more to do with the apps needing updating by developers? stock unrooted
Dear all,
Hope you are doing great, I was downloading and installing automatic updates just fine and the other week got a notification about a new update of over 1.4 gbs and the automatic installer was not possible to do and requested me to download it and installing it manually. I downloaded the Rar and everything was going smooth and when I enter TWRP I installed at first shoot without doing any wipe or clear cache or data.
All was installed and it told me to restart the phone, I did that and vroom a vibrating sound happen and got me back to the main screen of Poco and then to TWRP and show me 3 workarounds to clear data and cache and the last resort do a clean flash rom.
I had to end with the last option since I was unable to install the update. What could be gone wrong here? I am back at stock now and I am very sad that this fricking update break all the custom firmware and got me bootlooped
I look for your inputs and maybe I can try again.
Thank you!
You must install Android 11 firmware for newer versions of Arrow as it has switched to OSS vendor.
I was on arrow os 11 so Android 11 was on there, the issue was when I was installing the new update from surija I believe si called the developer.
Do you guys have an idea what did I did wrong? Should You recommend staying vainilla stock miui 12 with root privileges or arrow 11?
Thank you!
I was able to flash the latest version update but I am having a System UI is not responding and got WIFI broken so if anyone is installing this update be careful, does anyone installed the last arrow OS update?
I am currently having issues with the last update, I think I will stick with no updates on the firmware
Sorry I am posting multiple updates on my thread, but I tested it and definetly the last update from Surya break the OS when you login you do not have WIFI and is showing the error I mentioned UI system unresponsive. I installed the version from April from Arrow OS and all works like a charm.
So if anyone reads this be careful with latest release from Surya 5/14 version
Yes, i can confirm. The version I used initially was from april 30. The update from may caused bootloop. I'll be turning off updates when I restore it with miflash.
The main reason I went with arrow is that it is selinux enforcing and supports safety net. But this really makes me think..
@SebixWolf The problem may have been that you flashed arrowos from the wrong miui version. I just miflashed back to the original regional version, flashed twrp again and flashed the R firmware. See https://forum.xda-developers.com/t/...ng-flashing-custom-rom.4274891/#post-85002889
Unfortunately, I have a problem. My phone was on the power cord overnight and pulled the latest update (EEA 12.5.5.0 Enhanced). It was then booted into OrangeFox (OrangeFox recovery with OTA support) and waited for my OK. I didn't think anything of it and didn't make a backup either, as I assumed that everything would go smoothly like the last update.
The update then went on, but there was probably an error, because now I have a bootloop (yellow Poco lettering for about 2 seconds). I can't use an old backup because I'm abroad right now and I don't want to lose the apps I've already set up (pandemic, tracking apps, certificates, ...).
Does anyone have a quick trick or the latest full ROM that I can just iron over or any other good quick idea? Change bootloader slot or other options? OrangeRecovery and Fastboot are still accessible. Now I only have ADB/Fastboot on my work laptop, but I still can't list the device with adb devices. I guess I still need to install the Xiaomi driver for it, but that should be the minor issue.
Update: I am currently downloading the different ROM versions (fastboot, recovery and incremental update), just in case they are needed.
OTA for the rom and using ofox? hmm it's not supported unless you will flash stock rom maybe. I don't know much more. Correct me if im wrong.
OTA works very well with orangefox and AICP 16.1...