Develop Bugs

Rooting the phone breaks cellular network

Hello.
I'm experiencing some issues with rooting. My objective: stay stock, but gain root to flash franco kernel in order to get the best out of my device
All this is happening on OOS Open Beta 12 (Android 7.1.1). I was originally on OOS 4.1.1 and done everything I listed below, and then sideloaded OOS Open Beta 12 in hopes that it would resolve the issue.
What I've done: unlock bl > reboot into android> reboot to fastboot> flash twrp> reboot to twrp> reboot to system> reboot to recovery> i notice that the twrp recovery got overriden by the stock one
i then reboot to fastboot> flash twrp again> reboot to twrp> flash supersu> reboot to system
i have root and it works perfectly, but i lose cellular network.
Flashing franco kernel didn't bring the cellular network back. My device is not encrypted as far as I can see, even though the "Encrypt phone" tooltip in settings says "Encrypted". I'm not required to enter a PIN to start booting android nor did I not need to enter it to decrpyt the phone in TWRP.
Root zip I used is: BETA-SuperSU-v2.74-2-20160519174328-forced-systemless.zip
TWRP used: official 3.1.0-0 from official TWRP site, not the one from this guide
TL;DR: As soon as I get root, I lose cellular network. Right now I can't regain cellular network unless I reflash stock OOS.
Any clues on why this is happening and how can I resolve the issue?

Nevermind, resolved the issue using these steps:
Unroot > reflash twrp > flash SuperSU-v2.79-201612051815 > reboot. Also reflashed FrancoKernel and everything seems to be working fine now.

Although everything seems to be working fine, I can't seem to get LTE. 3G is max I can get. My G3 can pick up LTE with no problems. I was able to pick up LTE with OnePlus 3 yesterday, but nothing today. I'm not sure if this is due to root + kernel change.
Is this a known issue?
Edit: I just randomly got back LTE. It was probably just a temporary issue on my side.

I know you have to allow system modifications in order for twrp to stick or flash something besides an ota.
Glad your problem was fixed!

wifi not working after root

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.

sim card not working oreo/noughat

hi i have had the pleasure of using the developer oreo img and enjoyed it,but decided to reflash stock noughat img
until the official oreo comes out.heres where my issue started,after a successful flash and start up,my sim no
longer shows as inserted,i even tried a restore of my noughat back up.the only way my sim will work nowis with the
oreo stock img reflashed..anyone else have this isssue

Are you sure you flashed all the files included in the Nougat fastboot package zip? There must be an image called 'modem' and anoter 'dsp' which should take care of that.
Try reflashing the Nougat image once again.

I will try again

Having the same exact issue
Flashing the MR3 factory image results in no SIM card, same with fkashing MR1 @TheCrazyLex
EDIT: reflashed again the next day and it's now working....ugh annoying

Had exactly the same issue. Although on initial boot back to Nougat, everything worked fine.
It was only after a restart or two the SIM was then undetected.
I'm flashing stock Nougat again just now, hopefully that resolves it for me too.
EDIT. Ok I've now tried flashing multiple images, they all flash successfully and boot successfully, but none of them are detecting a SIM card.... any ideas anyone?
EDITS AGAIN: It would appear now working after flashing Oreo again, then back to Nougat. Very odd....
I want to lock the bootloader again, which is how I ended up in this mess, so I'm now flashing latest Global ROM again, rebooting and then attempting to lock the bootloader again.
I shall update with results.

any update in the same boat

I'm still having same issues,I'm just using Oreo which is working really well.only downfall I noticed is tethering doesn't seem to be working on it

Are you running the right image as Razer and Three have their own build so wanted to point this out as ThreeUK may not work right with the Razer build. i Remeber them saying something about making sure you use the right build

UPDATE - if anyone is having this issue.
--Take the Oreo preview and flash_all.bat via bootloader
--Let it boot and get in to Android just so you can enable debugging via dev options
--reboot to bootloader and flash_all.bat with the latest Three or Global image
--Again let it boot and enable debugging again
--Now reboot to bootloader, and do BOTH the following in fastboot:
---- fastboot flashing lock_critical
---- let it reboot and go back to bootloader again and perform the next lock
---- fastboot flashing lock
Once finally back in, only then did I have a locked bootloader + working SIM card.
Hope this helps someone.

Locking the bootloader doesn't fix things lol. I was on Oreo yesterday and flashed back to nougat and had signal and relocked the bootloader then 10 minutes later .y phone rebooted and lost sim. Only was to get it back was flashing Oreo then booting then flashing nougat mr1 and got my sim back. Then I locked bootloader and took the ota and now I'm back to normal and can take otas again

This is such a weird issue. like for instance I went back to MR1 from Oreo and had signal but when I picked the bootloader and ota to MR3 it was gone.then just unlocked bootloader flashed MR3 still nothing. So went back to Oreo and it worked and then flashed MR1 again and randomly worked even after the ota to MR3
So absolutely random.

hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too

SIM card issue
Hey @parky169, @Roxas598, @linuxct, @kickassdave, @joemossjr
Thanks for posting about this issue that you saw about the SIM not being detected. Our engineers would like to learn more about this and EXACTLY what happened. Can you please PM me with the details:
What carrier you guys are on?
What was the previous build you were on before you flashed the Oreo developer build?
Can you please walk me through EXACTLY what happened that caused the SIM to go undetected
Were any APNs changed prior/after?
Were any changes made to the files or phone (rooted, custom ROM, etc.) prior to flashing the O build?
How did you resolve this situation? Is this repeatable?
Thanks again for testing the developer build! Please PM me if you run into any more issues!
Best,
Khanger

parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Same issue as the rest. I wonder if this will work with the Oreo OTA modem img, I'm gonna give it a shot. I will report back
EDIT: Well there is probably no reason it shouldn't have worked I would assume the modem images are identical in 8.1 Dev and 8.1 OTA, but it does work by putting the 8.1 MR0 OTA modem img in the 7.1 MR3 and flashing. Honestly i ws too lazy and didn't want to wait for the Dev image to download and I already had a copy of the 8.1 OTA ON MY pc.

Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!

​
Jonlines94 said:
Hi
I had the same issue, I updated the APN settings from the carrier's website (three) and everything went back to normal!
Click to expand...
Click to collapse
I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?

NoXXX said:
​I can't edit or add any APN setup - nothing happens after saving new or edited APN items.
How did you do that?
Click to expand...
Click to collapse
Any update on this? I am in the same boat after standard OTA update. Can not save apns either. (at&t)

Thanks!!!
parky169 said:
hi i found a simple way to solve this issue.all i did is use the global 7.1.1 nougat factory img.but before flashing via the flash all bat.swap out the modem img from the nougat folder with the one from the oreo developer one.worked first time and after several reboots.hope this helps....
just an update i just installed recovery,magisk without issues too
Click to expand...
Click to collapse
Thanks for finding a fix. I was worried my phone was jacked up. I was having the same issue. I wanted to downgrade from Oreo since there is an issue with HDMI not having audio. I got signal now whoooo

WiFi and Bluetooth don't work after following the unbrick guide

Got my OP3 hard-bricked recently. I followed Naman Bhalla's unbrick guide and flashed down to OOS 3.x. Everything works fine except the WiFi, Bluetooth, and GPS.
The GPS toggle activates when I click on the icon, but it never calibrates my actual position.
The WiFi toggle doesn't activate, no matter how much I try.
The same goes for the Bluetooth option as well.
You can see the problem for yourself here
If I try to flash a new version of OOS, the phone freezes mid-boot and keeps restarting.
Any suggestions?

rahulkulhalli said:
Got my OP3 hard-bricked recently. I followed Naman Bhalla's unbrick guide and flashed down to OOS 3.x. Everything works fine except the WiFi, Bluetooth, and GPS.
The GPS toggle activates when I click on the icon, but it never calibrates my actual position.
The WiFi toggle doesn't activate, no matter how much I try.
The same goes for the Bluetooth option as well.
You can see the problem for yourself here
If I try to flash a new version of OOS, the phone freezes mid-boot and keeps restarting.
Any suggestions?
Click to expand...
Click to collapse
What happens when you try to activate these from Settings?
Flashing OOS later versions may solve the issues. What method did you use for flashing the later versions, adb or TWRP? Try adb.
I didn't face any such issues when I used the Unbrick Guide.

@rahulkulhalli
Do you have op3 or op3t ? This is for op3 .
If you have op3t use this guide
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

mar.ur said:
@rahulkulhalli
Do you have op3 or op3t ? This is for op3 .
If you have op3t use this guide
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
OP3

tnsmani said:
What happens when you try to activate these from Settings?
Flashing OOS later versions may solve the issues. What method did you use for flashing the later versions, adb or TWRP? Try adb.
I didn't face any such issues when I used the Unbrick Guide.
Click to expand...
Click to collapse
I tried, but I run into the same bootloop.
I used TWRP touch.
Could you tell me what steps you took after flashing to OOS 3.x?

rahulkulhalli said:
I tried, but I run into the same bootloop.
I used TWRP touch.
Could you tell me what steps you took after flashing to OOS 3.x?
Click to expand...
Click to collapse
I simply flashed the then latest version of TWRP and then clean flashed the later version of OOS and then clean flashed custom ROM coupled with flashing of proper firmware after a couple of days, all using TWRP.
Which version of TWRP do you use? After the OOS 3.x boots up, flash TWRP 3.2.3 official and then try using that for the further ROM installations. If this also fails, use adb to install the ROM. Don't go straight to a custom ROM since you seem to have firmware issues.
You haven't said what happens if you try to enable wifi, BT etc from Settings instead of from Quick Setting tiles.

What I think is you need flash the latest wifi and bluetooth drivers. Just download them from this link and flash using twrp
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628/amp/
You may need to reflash the OS after installing the firmware. Don't directly try to install custom roms after flashing the firmware. First flash latest stable build from official oneplus site, boot into OS and then you can do whatever you want with your device.

Question Random reboot +- corrupted boot image?

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.