Hey you people!
Clean flashed Android 9 yesterday, rooted with magisk. No more stuff applied. Wifi stopps working on the phone after some time, restart solves it, but not for long. Mobile data doesnt work at all. Wtf is this?
Thanks
xflowy said:
Hey you people!
Clean flashed Android 9 yesterday, rooted with magisk. No more stuff applied. Wifi stopps working on the phone after some time, restart solves it, but not for long. Mobile data doesnt work at all. Wtf is this?
Thanks
Click to expand...
Click to collapse
Sounds like a Charlie Foxtrot to me! Who's your provider? And have you tried removing/replacing your sim card?
Is Mobile data enabled?
Badger50 said:
Sounds like a Charlie Foxtrot to me! Who's your provider? And have you tried removing/replacing your sim card?
Is Mobile data enabled?
Click to expand...
Click to collapse
yea it is enabled, there is "LTE" shown in the status bar, too. switched to 3g mode, same thing with H.
But wifi doesnt work either after some time, has an x shown besides the icon then. how about that?
no problems with 8.1 before.
xflowy said:
yea it is enabled, there is "LTE" shown in the status bar, too. switched to 3g mode, same thing with H.
But wifi doesnt work either after some time, has an x shown besides the icon then. how about that?
no problems with 8.1 before.
Click to expand...
Click to collapse
Have you tried resetting your APN's?
Did you fastboot, side load, or OTA to 9.0?
Idk what caused the problem, but go to Settings > System > Advanced > Reset options > Reset WiFi, mobile & BT.
If no improvement, then get a new SIM card.
If still no improvement, then flash the factory image and don't make any system changes like installing a custom recovery/kernel. Make sure data is back to normal before doing any mods. Good luck!
i think i got it.
after flashing the magisk uninstaller zip, everything works.
so its either just root, or (and that i previousl missed) the adguard module (with root proxy mode).
I updated as usual without doing anything... and everything works. Could it be the extra stuff you do to your phone?
I think it's best that people run this without magisk until they sort out the bugs. Seems to be working fine for me after going straight stock without twrp or magisk. Had major problems before when I was rooted.
xflowy said:
i think i got it.
after flashing the magisk uninstaller zip, everything works.
so its either just root, or (and that i previousl missed) the adguard module (with root proxy mode).
Click to expand...
Click to collapse
wcouri said:
I think it's best that people run this without magisk until they sort out the bugs. Seems to be working fine for me after going straight stock without twrp or magisk. Had major problems before when I was rooted.
Click to expand...
Click to collapse
Right after Android 9.0 was released, I flashed the factory image without "-w" in flash-all.bat, installed TWRP and used Magisk 16.7 to root. Weird stuff started happening: the camera app force closed once, and I couldn't multitask back into Google Keep because the system thought Keep was not available (even though I could open it from the app drawer and it worked fine). So I started from ground zero and reflashed the factory image without editing flash-all.bat, I did *not* flash TWRP or Magisk, and everything worked as it should and no FCs. Today, I flashed TWRP and Magisk 16.7, and everything is still working properly. I am also using Adguard in standard mode (not root proxy), and it has been working flawlessly, and no mobile data or WiFi hiccups so far.
I have been flashing for years, and I am convinced that some stuff doesn't get completely wiped even when you flash a factory image. But usually another clean flash resolves any issues.
sublimaze said:
Right after Android 9.0 was released, I flashed the factory image without "-w" in flash-all.bat, installed TWRP and used Magisk 16.7 to root. Weird stuff started happening: the camera app force closed once, and I couldn't multitask back into Google Keep because the system thought Keep was not available (even though I could open it from the app drawer and it worked fine). So I started from ground zero and reflashed the factory image without editing flash-all.bat, I did *not* flash TWRP or Magisk, and everything worked as it should and no FCs. Today, I flashed TWRP and Magisk 16.7, and everything is still working properly. I am also using Adguard in standard mode (not root proxy), and it has been working flawlessly, and no mobile data or WiFi hiccups so far.
I have been flashing for years, and I am convinced that some stuff doesn't get completely wiped even when you flash a factory image. But usually another clean flash resolves any issues.
Click to expand...
Click to collapse
Good info my friend! As the saying goes...No wipes, no gripes!! :good:
Related
Hello all!
At the request of Santod, here is a separate thread to discuss the SMS issue some of us are experiencing with his 5.0.1 GPE ROM.
The original ROM thread can be found here:
http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
For some of us, flashing this ROM makes sending SMS messages work intermittently. Some experience that only the first message successfully sends, then all subsequent messages fail. Personally, I've tried flashing v. 1.02 three times to no avail. My most recent attempt was after re-flashing updated firmware and radios.
Let's figure this out!
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
steveg545 said:
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
Click to expand...
Click to collapse
because that stops the phone from sending them all together?
synisterwolf said:
because that stops the phone from sending them all together?
Click to expand...
Click to collapse
1x allows me to send SMS and make calls. Just tested both.
steveg545 said:
1x allows me to send SMS and make calls. Just tested both.
Click to expand...
Click to collapse
good to know. i wonder why some are having the sms bug. I use textra and havent ran into the problem yet..
*knocks on wood*
steveg545 said:
As an update, it would seem that disabling both cellular data (In Settings -> Data Usage) and setting the preferred network to 1x (In Settings -> Wireless & Networks -> More -> Cellular Networks) seems to stop SMS from failing.
I've attached screenshots of my current settings.
Perhaps this helps!!!
Click to expand...
Click to collapse
Damn. I'm glad there's SOME way around it, but hopefully a more convenient and more permanent solution comes along soon. This is the only ROM on any phone that I've been 100% satisfied with. Well I mean, it was perfect until I started having the SMS issue.
OP.
Can you pull a log cat after you sent 2 messages before the work around. i wonder if i can see something that i can help with. lmk
synisterwolf said:
OP.
Can you pull a log cat after you sent 2 messages before the work around. i wonder if i can see something that i can help with. lmk
Click to expand...
Click to collapse
Sorry if the log is a bit of a mess (never pulled one before).
Two messages were sent on a fresh boot, one succeeded. One failed.
Let me know if I can be of any more help!
Setting to 1x and disabling data allows SMS for me too. So weird.
Sent from my HTC One using XDA Free mobile app
Headed home now. Will take a look at it.
Problem Flashing Stock recovery
I'm having the SMS problem. I tried the method of flashing stock recovery and then factory resetting. I flashed the stock recovery and it seemed to flash ok, but when I go into bootloader and select recovery, the screen goes blank and then after a bit, an image of the phone appears with an red triangle and exclamation point on it. So I can't get into recovery. I reflashed TWRP recovery and I can get into that fine, but when I flash stock recovery, it still doesn't work. The stock recovery I'm using is https://www.androidfilehost.com/?fid=23622183712472879
Any ideas?
greiland said:
I'm having the SMS problem. I tried the method of flashing stock recovery and then factory resetting. I flashed the stock recovery and it seemed to flash ok, but when I go into bootloader and select recovery, the screen goes blank and then after a bit, an image of the phone appears with an red triangle and exclamation point on it. So I can't get into recovery. I reflashed TWRP recovery and I can get into that fine, but when I flash stock recovery, it still doesn't work. The stock recovery I'm using is https://www.androidfilehost.com/?fid=23622183712472879
Any ideas?
Click to expand...
Click to collapse
You don't need to do anything else with the stock recovery. You have to have it in order to do the stock factory reset. After you do the factory reset go back to twrp and flash the ROM again.
Well add me to the list of people having this problem. Setting it to 1x network only also allows me to send texts temporarily until I turn it back on LTE. Has a reset with the stock recovery been working for many people or was it a new idea that you decided to try greiland? Has anybody else restored their text history with titanium backup? I did and am wondering if it is a problem. I went from a fresh flash from 4.4.3 stock with all of the OTA firmware so I'd be surprised if it is something that requires a factory reset.
Also what recovery did you guys use? I flashed it with 2.8.1.0 and I had to do it twice before it would let me boot.
BranC85 said:
Well add me to the list of people having this problem. Setting it to 1x network only also allows me to send texts temporarily until I turn it back on LTE. Has a reset with the stock recovery been working for many people or was it a new idea that you decided to try greiland? Has anybody else restored their text history with titanium backup? I did and am wondering if it is a problem. I went from a fresh flash from 4.4.3 stock with all of the OTA firmware so I'd be surprised if it is something that requires a factory reset.
Also what recovery did you guys use? I flashed it with 2.8.1.0 and I had to do it twice before it would let me boot.
Click to expand...
Click to collapse
Try again with 2712 and don't restore your messages.
disconnecktie said:
You don't need to do anything else with the stock recovery. You have to have it in order to do the stock factory reset. After you do the factory reset go back to twrp and flash the ROM again.
Click to expand...
Click to collapse
Stock recovery factory reset did not fix it for me.
---------- Post added at 11:26 AM ---------- Previous post was at 11:13 AM ----------
I'm doing the stock recovery reset based on Santod's advice (http://forum.xda-developers.com/showpost.php?p=55930057&postcount=1553). There's a lot of discussion about it towards the end of his Lollipop thread and his GPE 4.4.4 thread.
It just started happening to me within the last few days. Only thing I've done to my phone right before it started happening was I upgraded to Santod's GPE Lollipop V1.02 edition (dirty flash from 1.00) and installed the NuK3rn3l V2.00 kernel. The other thing I did was I restored an old Titanium backup of my SMS messages from a 4.4.4 backup. Maybe that hosed things up? But I've done full wipes, stock factory resets since that and it won't fix it. Only thing that fixes it is restoring my nandroid backup of the [ROM][4.4.4] NuSenseSIX-ART Edition that I had before upgrading to Lollipop.
This may have already been suggested but using an alternative texting app like Textra doesn't work. This is getting so freaking frustrating.
For me, coming from a fresh flash on mdmower's TWRP 2.7.1.2 and not restoring any messages (I don't use Titanium or any app backups) still presents the issue. App doesn't matter (I've tried stock messaging, Google Messenger, and Textra).
There is a logcat a few posts back that I pulled when the issue occurred as well.
Just an FYI from my experience thus far!
steveg545 said:
For me, coming from a fresh flash on mdmower's TWRP 2.7.1.2 and not restoring any messages (I don't use Titanium or any app backups) still presents the issue. App doesn't matter (I've tried stock messaging, Google Messenger, and Textra).
There is a logcat a few posts back that I pulled when the issue occurred as well.
Just an FYI from my experience thus far!
Click to expand...
Click to collapse
Have you tried the factory reset with the stock recovery too? I've thought about it but its a lot of work to do if it isn't doing the trick for anybody else here.
BranC85 said:
Have you tried the factory reset with the stock recovery too? I've thought about it but its a lot of work to do if it isn't doing the trick for anybody else here.
Click to expand...
Click to collapse
I'm in the same boat. If the stock recovery fix hasn't worked for others, I wonder if it's worth the work.
I think I'll give it a try as a last ditch effort if the logcat I uploaded doesn't yield any insight into the issue.
Not saying Tibu is or isn't the cause of the problem.
But my gut always tells me folks with this issue did just that.
Restored messages with tibu.
Are there residual side effects that continue to booger you up once that's been done, even after a full wipe?
I don't know, but restoring messages with Tibu is about the worst thing ever and has always, always, always created issues.
I won't even touch Tibu personally.
Haven't since a bad experience years ago, and never will again.
It causes more grief then it saves me.
That's my opinion on Tibu...
Hi, I have the latest CM12 installed in my tablet, but I have a lot of issues, especially when installing multiple apps or if I try to change the Launcher. It gets into boot loop and there is nothing one can do but re-flash the rom, which is pretty annoying. It has happened to me already 3 times in a short while and I am thinking of flashing LineageOS. However, I hear it is still very buggy, especially the issues with wifi. So I would like to ask which is the least buggy Rom for 7.0 v410 or if there is a way to avoid CM12 from getting the problem with boot loop.
Boot loop has been caused when trying to change Launcher (because trebuchet regularly crashes), when installing x-plore file manager and in a clean flash when I attempted to install multiple apps at the same time. In all cases it got stack in boot loop, or would start only to restart after a while, endlessly.
Finally, I opted for LineageOS 14.1.
I had the 11-11 Nightly for some time and seemed fine. Today I updated to 25-11 Nightly. It feels maybe slightly laggy, but still checking it.
I have also installed "Best WiFi Keeper" app from play store and it generally keeps me connected. However, if connection is lost (e.g at restart or if I get out of range), I have to reconnect manually. I tried few apps for reconnecting but nothing worked. It appears that although the WiFi network is seen, the tablet cannot really re-establish the connection automatically.
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Tesla works great for me. I'm running a lollipop version that's still on androidfilehost; I'm not sure if GZR ever got updated beyond 5.1 for V410.
I've had CM 14.1 (long enough ago it was still CM and not LOS) on the tablet, and it felt like it would get laggy. That could just be from junk my kid installs though, but I don't seem to have that problem with Tesla.
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
kingzones said:
I installed Tesla (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip from https://androidfilehost.com/?fid=24052804347807214) with open G apps but getting errors while installing apps from Play store(Some error code 963 - tried cleaning cache of playstore, play services download manager, removing google account and adding again - Nothing works). Same situation with tipsy. Any help?
Click to expand...
Click to collapse
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
jason2678 said:
That is probably what I'm running, I don't have my tablet right now. I think I flashed it with opengapps nano. I didn't have to do anything unusual to get play store to work.
Tipsy uses the same base as Tesla and Validus. Since it is persisting across multiple flashes and roms, consider formatting the internal storage if it isn't too much hassle, the TWRP wipe where you have to type "yes" to confirm. Sometimes some remnants in userdata that aren't touched by the normal system/data/cache/dalvik wipe cause problems like this and can persist the way you're describing.
Just make sure you have rom and gapps on an external SD or you have confirmed you can push files to the tablet in TWRP over usb via mtp or adb before you blank the internal storage.
Click to expand...
Click to collapse
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
xdause said:
can you tell me if hotspot and usb tethering is working on tipsy? Thanks.
Click to expand...
Click to collapse
I'm on Tesla, but it has the same base as Tipsy. I don't have data on the tablet so it isn't a 100% conclusive test, but it doesn't seem to work. The switch for USB tethering never turns on. Wifi turns on but never connects properly. My laptop does briefly show connection then disconnects with both USB and wifi tethering. It could be because there is no data connection on my tablet, but looking through dmesg on the laptop gives me the impression that something on the tablet isn't working right.
kingzones said:
I found Nothing stable yet.. In last few days, I have installed CM 12.1, same trouble.. I installed Tipsy and Tesle, unable to install apps from playstore. Tried CM 13 and Lineage OS latest build as you, Wifi Teathering and USB teathering not working and same problem with wifi connectivity. Keed posted if you find something better.. I shall too...
Click to expand...
Click to collapse
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
nicospanas said:
I'm on lineageOs 14.1 which is alright though the wifi issue is still there. However, someone may have found a solution, but I don't know how to implement it. Check posts 207, 210 and 215 in this thread: https://forum.xda-developers.com/g-...eageos-14-1-v400-lg-g-pad-7-0-t3583952/page22
Click to expand...
Click to collapse
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
KLit75 said:
Would you (or anyone who sees this) please tell me is it possible to flash TWRP if I'm on 5.0.2? Or must I downgrade first?
I'm rooted already. TBH stock is pretty solid and if the custom roms have too many bugs I might pass. But I would like to flash Viper4Android and don't think I've ever installed it without a custom recovery. Many thanks in advance.
Click to expand...
Click to collapse
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
nicospanas said:
I made the same question more or less, over a year ago here: https://forum.xda-developers.com/android/development/help-installing-cm-t3483074
You cannot flash another rom over lollipop and I've never seen twrp for android 5.0.2 for v410. I am not 100% sure because my question was a bit different, but I assume from the replies, that probably not.
Click to expand...
Click to collapse
Thanks. That's more or less what I thought. From what I'm hearing there are some bugs in the roms that no doubt aren't being maintained at this late stage so I think I'll stick with stock (would be nice to have a custom recovery though.)
Not that it matters (a year later) but lots of people root with Kingroot when there isn't another option and there's several ways to remove all the bits left behind and switch it to supersu.
Thanks again!
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
kingzones said:
Well, I have a work around to stop wifi from disconnecting in lineage os. After that I did not know when wifi got disconnected and reconnected.
Just download E-Robot from playstore.
https://play.google.com/store/apps/details?id=com.bartat.android.robot
And set it to settings as per screen shot.
Click to expand...
Click to collapse
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
nicospanas said:
It works! Thank you so much! It seems the LOS developers have stopped trying to fix the wifi issue but it is important. The workaround even works at restart, with some delay, but it works!
Just to clarify to newbies like me, where ssid you have to put the name of the network you want to connect. I wonder if one can add more networks, so it can connect to any saved network according to where you are. You think that's possible?
Click to expand...
Click to collapse
That would be great.. I shall try.. if successful, I shall post results.
I have a uk410, the US Cellular variant of the v410. I tried the CM12.1 "stable" release cm-12.1-20151117-SNAPSHOT-YOG7DAO1K5-v410.zip found here (archive.org/download/cmarchive_snapshots), along with Open GApps nano for 5.1 (opengapps.org/?api=5.1), and quickly got the infinite rebooting issue.
I then switched to the Telsa ROM mentioned earlier in this thread (Tesla-v410-5.1.1.High_Voltage.2.2.1-Release-20150902.zip) found at androidfilehost.com/?fid=24052804347807214, again with Open GApps nano for 5.1 (build open_gapps-arm-5.1-nano-20180922.zip), and have been running it with no issues for two days. My wifi is connected, and stays connected (tested two different routers), Play Store and apps have been working fine, and no crashes so far.
I'm using TWRP 3.1 (twrp-3.1.0-0-v410.img).
Thanks for mentioning Tesla, @jason2678 !
So like all of you I was looking for a rom to install on this v410 7" tablet, and it looks like I should just give up or stick with 4.4.2 stock if I want to go through the rooting process.
Basically all the development roms end with the same problems, wifi dropping, hostspot not working, no ir blaster, volume problems, bluetooth errors, and several hundred posts about lolipop memory leaks crippling the tablet because of only 1gb mem.
So, I am asking all of you, is there any real reason to root it, besides going back to stock 4.4.2?
And lastly, is the stock 4.4.2 kdz image that is floating around a test version, and if so is there an actual official kdz image somewhere that isn't a test image?
Thanks...
CrDroid by far in my opinion. Lineage based, 7.1.2.
Also, e/ os has been unofficially released. No Google anything...an entirely new Google list operating system by lineage. It's lightning fast and runs magisk perfectly. It's basically like nothing you've ever seen before and if you look under LG g pad 7.0 on Android file host, go to the second page and click on the last user who goes by the name anonymous and you'll find the ROM there. I had no idea what it was until my g pad boot it up and I saw the e logo. I pretty much **** myself in excitement
Straight away after rooting 4.7.5. my wifi doesn't work. Like the toggle won't turn on etc and won't find networks. But after a reboot it's fixed until the next reboot which it starts again.
Any idea how to fix it for good or wait for updates?
known problem, Have to wait on update
Lol! It's not a rooting issue at all. Only after flashing a custom kernel you CAN end up with non functioning WiFi but that's only because the kernel-thread hasn't been read properly.
Rooting + WiFi = zero problems :good:
Likely a custom kernel was installed which installed it's own wifi (and other) modules. Then the kernel was changed or reverted back to stock, but system partition is still changed with custom modules for connectivity. If you revert back from a custom kernel, a "dirty" flash of the system partition usually solves the issue.
Maybe it was after magisk. After magisk patches the boot.img it's "sort of" custom kernel Right. I had magisk 14.5 beta and wifi wasn't working and I flash 14.0 and it's seemed to fix it i think.
wifi working- but...
Hi, my wifi works (picks up all networks nearby- including mine)
but-
it won't connect to my network when using passcode.
Any ideas?
Running Lineage current and used magisk to root initially...
HELP!
It's driving me nuts.
Having same issue as above.
Can search for but cannot connect to my WiFi.
First issue I had after rooting was Facebook messenger force closing only while I was writing a message, installed a custom rom and hasn't happened since. I cleared cache and data, tried a full format, reinstalled magisk and tinkered with settings with no luck still.
I believe I've deeply messed up here. I was trying to update to 8.1 while keeping Magisk root and ElementalX, but now I've got various UI problems including the home and app switch buttons not doing anything, the cell signal indicator never shows whether I'm on any data network, and notifications never show up. I also get a pop up right after boot that says my device has an internal problem, when I open up the phone app it says that my device isn't supported but I can still make and receive phone calls, and the USB OTG is not functioning at all. Almost if not everything else is working.
I followed the instructions to the T (I'll post a link to instructions a little later) then installed EX but, I didn't have root. At one point I also forced the phone off when it was presumably setting up final things after the ROM switching reboot. After booting up again, several apps were crashing and the problems above came up, so I followed different instructions specifically for installing EX and Magisk, which only fixed app crashes and Magisk.
I'm thinking where I messed up is that I didn't make a Magisk patched boot image for 8.1 before installing it, but at this point I'm not sure if that's the problem. I don't want to wipe the user data partition, but I'd do it if I have to. I have backups of everything anyways.
I just figured out that I was having the same issue as Cristiano Matos, though my OTG cable seems defective. The type-C connection is not working in one orientation, so I'll just have to use it in the other. This thread can be closed. Sorry for my stupidity
Hello, recently I got the poco f3 (256-8gB) and I have experienced a really weird behavior (I know about random reboots other peooke expperience, but please read what happened to me)
I rooted it with magisk (patching boot image using latest stable apk from official github).
I added smali oatchee module to it.
At some point miui auto-updated to 12.5.1.0 RKHEUXM, I had to get boot image from the update, extract from payload and reparch to get magisk back.
After this I noticed the phone rebooted randomly, it happened like once in 2-3 days, son nothing really anoying, I didn't pay much atention to it since the phone worked flawlessy for everything else. Then I tried to connect to a router wifi (router setup with openwrt) and I noticed EVERY TIME I tried to connect to that specific wifi the phone rebooted. I tried to reconfigure the wifi network but it still happened. No problem with other devices.
Then the next day, I openwd an app which had embedded adds (an app I have been using for a long time, the very same version). 1 second into the add the phone rebooted...and it became stuck in a bootloop in MIUI logo. I couldn't even power off the phone, I could enter recovery/fastboot though.
I used twrp to wipe it without erasing my data, but problem still persisted. Only reflashing boot image (I used stock version) revived my device. I tried to boot it without flashing, phone seemes to boot but with no display.
So I decided to make a full wipe, then reinstall magisk. Phone has been working fine since then, but the occasional random reboot still happens and I'm afraid eqch time my poco f3 will be stuck in bootloop again.
My conclusion is somehow boot image got coreupted, but I can't think of anything I could have done for that to happen, as I only had magisk set up, I didn't even use any app with root permisions yet. Any ideas why that my have happened?
I'm thinking of flashing twrp to recovery so I can reflash boot image from it in case this hapens again...
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Robert314 said:
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
Click to expand...
Click to collapse
How may I get those logs?
Alin45 said:
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Click to expand...
Click to collapse
My phone is already rooted via magisk patching the roms's boot.img, then flashing via fastboot. That's the recommended method for this device afaik.
Try clean flash. Backup all your stuff that you want to keep. Format data in TWRP before booting into system.
OTA auto-update from time to time causes issues.
I tried again and the revoot when connecting to that certain wifi network persists.
Is there anyway I can reflash my current firmware without having to wipe? Can I jast flash my current update with twrp with no data loss? (Basically what happens when a system update is out...)
Just posting to note that update 12.5.3.0.RKHEUXM solved all those random reboots for me.
They were also happenning when trying to share image/links/anything via bluetooth, telegram....only thing that worked without reboot was "copy link" in the share button.