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.
Related
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?
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
Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!
nitro32 said:
Hi. I'm running Q, rooted with the method described here:
https://forum.xda-developers.com/pixel-3a/how-to/root-3a-t3929053
Brief background is that the phone had been running fine for months, no wifi issues at all, both 2.4 and 5 GHz antennas working, but I stopped getting security updates after January 2020. Didn't like being that far behind on security updates, so I updated using this basic process:
1. Download latest stock factory image
2. Extract boot.img, copy to phone and patch using magisk, copy back to PC
3. Edit flash-all.sh to remove the -w (wipe) option
4. Run flash-all.sh, which flashed an updated bootloader.img, radio.img, and system image
5. Finally, flashed my patched boot.img
The process was successful, but since then I've had major wifi issues. 5 GHz just doesn't connect any more, period. 2.4 GHz will connect, but drops every few minutes. Every time I pick up my phone, I have to prod it a little and wait for wifi to connect, and even while actively using it, watching a youtube video or something, wifi just drops for a couple minutes then eventually reconnects.
Anyone else having this problem by chance? or more importantly, any suggestions on what I can do to fix it? Don't think it's a hardware issue because the phone was working damn near flawlessly before applying the July update.
Would appreciate any suggestions. Worst case I can wipe and re-install the January 2020 image, but would prefer to avoid that if there are any better options.
Thanks!
Click to expand...
Click to collapse
Hey, maybe something go wrong in your update process. To make sure its no issue on the official SW side, i would recommend to do a clean flash:
- backup all your important messaging stuff like whatsapp, telegramm, signal via inbuilt backup function.
- do a backup via the google backup function found in settings / sync photos via the google photos app
- if you have important files on your internal storage, do a backup of it on your pc / flash drive
- then, flash the latest factory image avaiable (use factory image, NOT OTA update) (dont use -w, to preserve data).
- After it setup your phone again. Patch the boot.img (extract it from the factory image you flashed) with magisk and flash it, install root (magisk).
This way you can ensure, that its not a SW error / bug from google.
When you want/need to manually apply a update, follow the instructions in the agisk thread for P3a: https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783
Really, thers is no need to flash the radio, etc files by yourself, just follow the instructions to preserve root and flash the ota.
It may take about 40mins of work, but you can be sure, that if the issue persist its not your fault.
Cheers!
Hi, bejunk. Thanks for taking the time to reply. I'm a little slow to respond because I was hoping someone else might chime in. Not that I don't appreciate your advice, but what you described is pretty much exactly what I did leading up to this point - flashing the latest factory image without -w to preserve my data. I also didn't really seek out to flash the radios myself, that's just part of the flash script provided with the factory image:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-sargo-g670-00042-200421-b-6414611.img
fastboot reboot-bootloader
sleep 5
fastboot update image-sargo-qq3a.200705.002.zip
I guess I'll try wiping my data this time and trying again. Was hoping to avoid that. And failing that, flash back to the January image and see if that gets things working again, unless there are any other ideas.
Will post back the results.
Did a factory install again as mentioned, this time leaving -w enabled, and so far so good. Haven't noticed any wifi drops in the last couple of days, and I'm able to connect with 5 GHz again. No idea what failed previously, but glad things are back to normal now. Aside from that wifi issue, my 3a has been extremely reliable. Hated to see that record ruined.
I use to root everything from phones to tablets for years. But lately I've given it all up. I need reliability and security and you're not going to truly get that with some of these cooked ROMs. No matter how so-called reputable these chefs are. You really don't know anything about them.
Glad you got your situation fixed. I can remember going through the same thing many many times. Frustrating as hell.
Nylo
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
I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.