Database Info

OnePlus One - Won't boot RR , boot loop happens

Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment

wahlmat said:
Hi!
A while back I had some issues with the phone, it was when I was supposed to boot it, it always took 2 tries. It always got stuck, then had to long press the lock key to hard reboot it, then it worked fine. This prevented me from doing a factory reset (in hope to fix (what I later found out was) a media rescan etc). Tried to root it, something happened and it wouldn't boot anymore. Yiti yata and the phone wouldn't boot. Finally I got it back to life with some guide on here and I used whatever 4.4.4 I downloaded.
The software wouldn't find any "normal" update phone updates, so I figured I would try Resurrection Remix 7.1.x (.2 I think it was). At first I got just that it failed with some 2.x twrp version. Updated to TWRP 3.1.x.x (3.1.1.0 if I guess). Now I got to know that it was a TZ error (ERROR 7) from TWRP. This happened to my "RR-N-v5.8.3-20170718-bacon-Official.zip" file. I managed to get around it by doing this: https://forum.xda-developers.com/showthread.php?t=2522762. So I could get this installed, sort of I think. The problem now was that it would show the very first oneplus boot screen for around 20 ish seconds, before it would reboot in a boot loop.
So I tried to install some other CM Lineage Os nightly thing (they said install that and then RR), but that didn't work either. This post was the one I donwloaded from (install this first, then RR should work).
I tried doing this both on TWRP 2.8.6.0 and 3.1.1.0 since I saw some post about the modem not being right from versions newer than 2.8.6.0.
Looking around a bit more I saw in some post someone talking about firmware..? Does this matter anything, also how is this different from the recovery or ROM? (new to this stuff)
In short, last working version of Android I had on there was 4.4.4 (think I followed this post). Using a Mac currently and have no problem with flashing, entering fastboot or recovery.
My procedure when I tried to install RR was:
Install the TWRP 3.1.1.0 or 2.8.6.0 (since I did it several times).
Wipe everything (Have nothing of value on the phone) cache, system, internal storage, dalvik and data. Also did a factory reset (from TWRP) before if that matters.
Copied RR and Gapps 7.1 ARM (not arm64) over.
Installed RR, wiped cache/dalvik. (or linear/cm (post above^^) when I tried that)
Installed Gapps, wiped cache/dalvik.
Boot loop.
Also tried with/without emptying cache/dalvik also chose to install both zips at once.
So can anyone clue in how I can proceed to get RR 7.1 onto my OPO? Any help is very much appreciated
I'm sorry if this wasn't the best post. Have an immense headache at the moment
Click to expand...
Click to collapse
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(https://dl.twrp.me/bacon/).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware: https://drive.google.com/file/d/0BxysuRdzsJeWeW9JbTNwaUJKb1E/view?usp=drivesdk
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(opengapps.org)(optional).
Reboot.It should boot fine now.
Good luck!

Mr.Ak said:
Calm down.
You're right about that firmware thing,that is the one causing issue when you're trying to flash RR 5.8.3 over KitKat.
This is because the firmware that kitkat comes with,is old and don't support newer android versions,that's because it is made for KitKat only.
Always use latest Twrp(Can't post links withing 10 posts apparently...).
Make sure you don't edit any zip like what you did with the Rom zip earlier(devs don't post non-working zips),I'm sure you've a backup of your non-edited zip,if not,re-download the zip.
Now boot into latest twrp,wipe everything except internal storage.
Firmware:
Flash the above zip,then without wiping anything flash rom zip(unedited) then flash google apps package(Can't post links withing 10 posts apparently...)(optional).
Reboot.It should boot fine now.
Good luck!
Click to expand...
Click to collapse
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful

wahlmat said:
Thank you so much! Got it working on 1st try with what you provided! Seems like the firmware thing was the bad guy in this scenario. A little interest, what specifically is the firmware in this case? Either way, rocking RR now and I'm really grateful
Click to expand...
Click to collapse
I'm glad you got it up and running.
Here are some FAQs:
What is a Firmware? What is Modem?
- Firmware is the whole package of proprietary partitions of your device, modem itself is a NON-HLOS file responsible for your device's communications over Wi-Fi, Mobile Networks and other such stuff.
So what is the difference between firmware and ROM then?
- Firmware is the responsible partition for IMEIs, the modemst partitions hold your IMEI, persist holds your Mac addresses etc.
ROM is only a combination​ of system.img and boot.img (kernel)
What to restore if I loose my IMEI?
- Both the modemst partitions (IMP: considering you took a backup of them before)
What is the default firmware? (default= firmware which comes with the latest CM/ LineageOS 14.1 weeklies)
- c6-00241

Thanks a lot, once again

Help!
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!

HisMuse said:
I'm not sure of all the specifics on my oneplus one but I accidentally updated the wrong update from my nightly bacon.. it now is stuck in Boot Loop I can get to the fastboot screen (it gets stuck there too) and I can get to the recovery, etc (but it is not the usual screen with all the folders (it was rooted).. it is now just four options in Cyanogenmod recovery.. none work. I do not want to lose my data :crying: .. Sadly my techy is not available to save me! Please help this untechy Cali Girl! I've googled and researched and its still like a foreign language.. Thank you!!
Click to expand...
Click to collapse
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM

wahlmat said:
I am not 100% sure, but I would say, boot into fastboot, flash something like TWRP recovery, then you will be able to access the device files from the recovery. Just reflashing the boot shouldn't mess up anything as far as I am concerned. After that (when you've grabbed all the files you want), flash the newest firmware the guy linked above and install your latest 7.0 ROM
Click to expand...
Click to collapse
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?

HisMuse said:
I can get phone to fastboot but it just stays on the screen that says fastboot.. do I need a computer?
Click to expand...
Click to collapse
Yes you do. You need that + some software. Check out some "install custom recovery oneplus one" guides, you should be able to find something. Are you on Mac or Windows?

Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.

HisMuse said:
Yes I'm on Windows 10.. I tried removing battery overnight as well .. its not boiling hot anymore but still stuck in bootloop.
Click to expand...
Click to collapse
Download the Samsung ADB driver or whatever it was called, then flash a new recovery for it. There are multiple guides for doing that. After that you should be able to transfer your files to your pc while being in recovery mode

[SOLVED] Unable to get Wifi working in LineageOS17.1 with OpenGapps and Magisk

Hi guys,
long time ago i've already been a Member to XDA Community. HTC Wildfire was a brand new phone at that time. In the mean time i've switched to a Oneplus 2 running Lineage OS 17.1 and two years ago i got a Oneplus 6 running stock ROM till yesterday.
Yesterday i got Lineage OS with Wifi up and running fine with the official guide and official lineage recovery but forgot to flash OpenGapps in the first try. Tried flashing it again but got a Qualcomm Crashdump Mode Error after that.
So i went on to reflash the whole phone with clearing storage, system and so on. Flashed again now with OpenGapps and Magisk with reboot to recovery method described in official installation guide, Lineage was booting fine and tried to search for Wifi-Connection but i wasn't able to see any Wifi at all. I finished the setup and tried again in settings but System UI crashes if i try that. Rebooted, cleared Cache and tried again but nothing.
So i went back to full stock 10.3.0 with MSMDownloadTool but it only flashes partition a? Is that correct?
After a lot of trying different things got back to 10.3.5 on a and b partition with mauronofrios stock fastboot roms from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 (Thank you very much for that! :good: ). I can boot both slots if i switch them in booted twrp without any problem.
On stock everything works fine my wifi detects all available networks and i can connect to them without problems.
What did i do wrong?
Any help would be appreciated.
Thank you!
Schwaus
EDIT:
So i did a little bit more testing:
Installed lineage-17.1-20200804-nightly-enchilada-signed.zip with corresponding recovery without anything like Gapps or Magisk both like described in official instruction and with TWRP from mauronofrio. I also tried to flash latest official OTA from Oneplus via TWRP before flashing Lineageos. In neither of the tested ways Wifi is working and i cant see any Wifi-MAC-adress under settings. Also tried to switch back to stock before flashing with flash-all-partitions.bat from mauronofrios stock to get the persist partitions replaced too.
Every version of Stock like the MSMDownloadtool 10.3.0 or Stock 10.3.5 from mauronofrio Wifi works perfectly without problems. I also can update via OTA without issues. I just dont know what is happening with my Wifi firmware when flashing LineageOS.
EDIT 2:
Got the problem fixed:
Don't know if i done it right but maybe it helps someone.
In my case it was a combination of problems:
- First the latest Oneplus 6 Lineage releases (20200804 and the withdrawn 20200811) seem to have a bug when installed fresh on a device to cause a bootloop so i used the one from 30/06/2020 and updated with the app afterwards.
- Secondly the copy-partitions.zip script hasn't copied all of the partitions necessary. In mauronofrio's fastboot image there is a image named fw_4u1ea.img. This one got not copied by the script, so i booted twrp-3.4.0-1-enchilada-Q-mauronofrio.img and flashed all of the images (fastboot, persist and critical) to slot b again manually like described in his thread. The flash-all-partitions.bat has not worked either.
Now LineageOS works like a charm and i can see and connect to every wifi.

Hey mate. I had the same issue and I gave up at this point. Tomorrow I'll try your "EDIT 2:" and gonna leave a feedback

Hey Schwaus, thanks for this post. *EDIT 2* worked for me

can't get anything to boot

All I have access to is twrp 3.4 and the all in one tool. Through flashing I screwed up along the way. Can't say where @ this point but just need to make my phone stock again to start over. I've flashed factory OOS 10.3.3, 10.3.4. each time wiping data and dalvik. Re installed twrp 3.4 and magisk 20.4. I've tried flashing aosp roms as well. Had resurection remix installed and wanted to try and go back to OOS and flash renovate ice magisk mod and never got it to boot into 10.3.3 OOS. All that happens is it goes to bootloader unlocked screen and then black with vibration and reboots into twrp. I even have a rr back up and a stock backup that won't take either. This is all being done using an otg. Not familiar with adb on the laptop. I'm familiar with root, unlocking bootloader, and flashing things but from the nexus era. Things are a bit different now and I've been extensively reading and it seems each rom has its own method of flashing. wish I wouldn't have stopped with modding from years ago. Any help is greatly appreciated as I don't currently have a working phone

Format data. Phone will boot then.

Worked perfect, thanks!! Does that have to be formatted after any ROM install including backups? I've looked through the guides and other threads and there isn't a how to step by step explanation of how to flash new Roms or restore backups

how to know if it's a bootloop?

hello i was upgrading from stock 9.0.7 to 9.0.9, my bootloader is unlocked and twrp is a permanent one, the phone is also rooted. i wiped system then flashed the 9.0.9 then flashed the 4.0.4 twrp, rebooted into twrp, flashed latest magisk, rebooted into twrp and then pressed reboot into system. the phone is encrypted. the booting animation has been on for 20-30 minutes at this point. is it a bootloop? why what did i do wrong? thanks

@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs

flash713 said:
@seth wellington
Try formatting data them reboot system. That should get you booted up.
Never wipe system or vendor on these devices and always when flashing a rom flash TWRP installer zip or you won't have twrp because of where recovery is located which is same place as boot.img and it has to be installed when flashing a rom or update to a rom or it won't be present.
How I flash OOS on my once T-Mobile now converted international/global OnePlus 6t.
Boot TWRP
Flash OOS global 10.3.6
Flash TWRP installer
Flash finalize
Format data
Reboot system
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
Edit
What you could have done is just flash your updated OOS , flash TWRP installer zip, reboot recovery, flash magisk, reboot system. That's what I would have done updating OOS ..
Hope this helps.
Sent from my OnePlus6T using XDA Labs
Click to expand...
Click to collapse
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?

seth wellington said:
Thank you very much for your reply. Unfortunately I couldn't wait for that long and I had to do something right then. After some attempts I also lost my twrp and was left without a functioning recovery, so I had to look for help and some people helped me go through unbricking through the msm tool.
The thing is i just really want to always flash clean so that the phone doesn't lag and works properly, I had no idea you shouldn't wipe system... The guide that I followed said that when updating oxygen manually you have to wipe system so I thought nothing would go wrong. I still don't know what caused a bootloop since that guide was a verified one. Thanks a lot for your help. So if I'm reading it correctly, you have to do the wipes after you've installed the system, not before?
Click to expand...
Click to collapse
Quit a few pretty well known developers here on xda (AOSiP op is one and there are more) say not to wipe system or vendor in their first posts of their custom rom threads. The way I describe how I install works 100% always and is the cleanest possible installation. Formatting data when installing a new rom at the end of install process does all the wiping needed to make sure nothing is left from the past and everything is clean. I used to wipe various partitions but on other devices. The install directions I use are originally from the PiXeN rom developers op. I've been flashing roms since the Nexus S days. Not saying that means anything other than I'm kinda old now. ? But that install process has never failed me once and I've flashed I'm sure hundreds of times on this device.. When I update i just flashing the updated rom over current and don't wipe anything then flashing twrp installer zip, reboot recovery flash magisk reboot system or if gapps are needed when I reboot recovery flash gapps..Unless it's a major OS update that's always worked for me.
Possibly not formatting data caused boot loop.. I know when going from OOS to AOSP rom format data is mandatory or it won't boot system.. I never flash magisk during initial flash. I always boot system first then at some point boot twrp and flash magisk. Try that next round and see if it turns out better. The whole AB partition deal made me feel like I was really old and retarded.
If I was updating OOS I would boot recovery, flash OOS, flash twrp installer zip reboot recovery, flash magisk, reboot system. Check out the finalize script xda thread. There are two here. The original person who made finalize has a thread and another user has another finalize thread. I believe in guides section of OnePlus 6t. With Android there are always more than a few ways to achieve something you know ... But what I post here is what I've been doing and I've flashed 400-500 times at least on this device.
Sent from my OnePlus6T using XDA Labs

@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy

seth wellington said:
@flash713
I totally trust you and respect anything you say and recommend me to do. Thanks a lot for all the instructions and clarification. I've been into android far less time than you — only since oneplus one. I'm extremely bad with tech but even with that phone j somehow managed to get bootloops or half-bricks ten times less than with the oneplus 6. And back then in 2015 I was way more enthusiastic: flashing twice a month loads and loads of roms. Of course it wasn't my personal achievement, I was still simply following detailed and carefully written instructions on forums on how to flash a particular rom in a particular way, but hey, at least I somehow managed it.
Now in this case I'm assuming it's the a/b partitions they've introduced that have completely changed the process and ways of flashing to the point that I stick to the guides and still get bootloops lol. That unbricking process was a huge stress for me, I don't think I'm going to touch anything in my phone for a while now. And I'm on the latest 10.3.6 oxygen so it's alright. Thank you for your help buddy
Click to expand...
Click to collapse
Np. My real first name is Seth. Haha. Cool name btw. I just installed OOS 10.3.7 on my 6t. I was notified of the update yesterday via oxygen updater app from play store. Good handy app to have. I would have never known 10.3.7 was out or at least not so soon if it wasn't for that app. I believe it auto notified me too. I don't remember setting it up. Android has changed soooo much you know.. I love my OnePlus 6t though. Definitely one of my most favorite devices I've ever used. What's new today is gone at some point and replaced with "better.." lol. Not always better imo anyway. Glad I could help. Feel free to message me any time. Good day to you.

[Xiaomi POCO X3 NFC surya] Wi-Fi stuck with "Turning on..."

I have successfully installed LineageOS what feels like a hundred times now. I followed every single piece of advice and best practice. In total frustration I gave up LineageOS and followed every single step for an OctaviOS installation. I even flashed the newest Global stock firmware successfully, just to follow every recommended step.
I boot into OctaviOS, after successful installation and...
Wi-Fi still won't turn on.
I am completely out of ideas and I have no idea what to do about it. Going back to stock and using this in production is not an option.
I have installed TWRP 3.4.0-0 By mahajant99 and every ROM flash and partition wipe, worked as expected and I never encountered a serious error. All flashes went fine and everything was done exactly step by step, as the guides recommended. Still, no Wi-Fi.
What can I do to fix this?
P.S.: Wi-Fi works through stock ROM. So no hardware issue.

Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph

Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
https://telegra.ph/How-to-http://http://
Disregard this...

yan2xme said:
Please, before flashing a custom ROM, make sure you installed the MIUI 12.0.4.0 Firmware Only because it is an essential to make WIFI and Calling Works...
Please be guided here on the tutorial created by @ManoloRey... It works smooth, no problems...
Better use OrangeFox as a recovery image...
How to install Poco x3 ROM
Clean Flash 1. Flash recovery (latest Ofox 11.0 Beta - "Download" ). This is very important. 2. Reboot to recovery. 3. Dont wipe or format anything.. 4. Flash any custom roms you want. e.g. PE+. etc. Wait until complete. 5. Format data -> Yes. 6. Reboot to System. 7. Complete initial setup. 8...
telegra.ph
Click to expand...
Click to collapse
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.

Aki-to said:
To test, I followed the guide and installed this precise FW+Vendor image. Doing this, I cannot boot into a custom ROM (e.g. OctaviOS), at all. I repeated this test several times, to exclude possible installation errors. I did CLEAN flashes and installations. Still, it makes things worse. As already said, I can't even boot into the ROM.
Click to expand...
Click to collapse
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does. Better use EvoX or RR or Pixel Experience ROM... They're more polished and expect to also have great updates... Just wait for more stable Android 11 Custom Roms or just contact the OP of the OctaviOS for surya...
@id.agung17

yan2xme said:
Better just try another rom... They are all still AOSP and uses same kernel as NitrogenOS does.
Click to expand...
Click to collapse
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?

Aki-to said:
Even IF another ROM would work -- why doesn't this ROM work on my phone? What's so special about my phone? I have a plain brandnew POCO X3 NFC, like most others here. So why wouldn't it work? Does the firmware version have anything to do with it?
Every guide I read, explicitly recommends version "12.0.3". However, the newest version is already at version "12.0.4". Maybe this is causing the issue?
Click to expand...
Click to collapse
Maybe, have you also even tried installing fw 12.0.3? Because at the meantime, no developer has compiled the public kernel of poco x3 to their respective roms... They still use the kernel from the first miui rom... Idk whats really the difference on stock kernel vs the released kernel for surya because in my situation, everything works fine on installing roms. My device is surya, 6/64gb... Plain just like you... Idk why devs couldnt even fix this thing...
Sorry bro I can't help you with this, I'm just an ordinary kid being new to this stuff and have a little experience with this (still I'm a fast learner) because I only experienced much more customization on the Poco X3 than even other phones I have owned previously. I did not also learned coding (i was a rookie HTML coder past years but i forgotten it) like Java or scripts on Linux to compile and make compatible custom roms for phones... Peace

I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!

Aki-to said:
I did the following steps:
Flash "surya_global_images_V12.0.3.0.QJGMIXM_20200925.0000.00_10.0_global" with "MiFlash 2020.3.14.0".
Wipe Cache, Dalvik.
Flash "OctaviOS-v1.2-surya-20201109-2033-VANILLA-Official".
Flash "Magisk-v21.1".
Format Data.
Reboot into System.
Wi-Fi is working!!
Now only NikGapps is missing, but that is just booting into Recovery, flashing and booting back into System, so no problem here, anymore.
Thank you, @yan2xme! You say you are noob, but you had the right guess, too! Anyway, thanks for your help, I appreciate it!
P.S.: Boot-up is additionally much faster, smoother and without SystemUI crash on startup. This 12.0.4 firmware really sucks!
Click to expand...
Click to collapse
Ohhh... ok thanks for the appreciation too... Hehe
Resurrection Remix Rom Developer also pointed out that you should flash 12.0.3 even theres the newer version... So maybe.... Haha