Database Info

bootloops and wifi doesn't turn on

i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?

matanp said:
i had the latest COS12 stock rom (rooted)
few days ago my battery ran out and after charging, the device got into bootloop.
i tried the onplus fix (https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/) which indeed fixed my bootloop and flashed KTU84Q (4.4.4), however, my wifi doesn't turn on now:
https://youtu.be/xchjcNl3pPk
i've tried clean flash again (with lolipop i get bootloop again)
i've also tried flashing color os (kitkat) and also no wifi
so far my problem seems to be:
on lolipop - bootloop
on kitkat - no wifi
any one has any idea?
Click to expand...
Click to collapse
A few questions:
What method are you using to switch between KK and LP? Fastboot (flashing stock images) or recovery?
If it's recovery, are you flashing the correct firmware/modem?
Are you still able to see your baseband and IMEI in About Phone?
IF you haven't flashed the stock images with fastboot that's the first thing you should try. I have detailed instructions in my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471

first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem

matanp said:
first, thanks for your reply
second:
at first i did a clean flash from fastboot like this: https://forums.oneplus.net/threads/tutorial-flashing-a-factory-image-from-scratch.142870/
i also tried the oneplus one fix for bootloops that also use fastboot from here: https://forums.oneplus.net/threads/fix-stuck-at-boot-logo-boot-loop-random-reboot.160199/
later, i tried flashing from recovery, also the colorOS rom
the common for all is LP = bootloop \ KK = no wifi
when i'm on KK the phone works got, getting calls in and out
when i've flashed from recovery i've flashed only one zip file. didn't flash firmware nor modem
Click to expand...
Click to collapse
Have you flashed the latest Lollipop build with fastboot as outlined in my guide?

not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had

matanp said:
not with your guide but with the guide in the link in my last post
also i don't remember seeing a userdata 64GB file in the lolipop image i had
Click to expand...
Click to collapse
That's because the LP images don't usually contain it, but the ones I link to do.

i'll try and report
thanks

i just got a message from oneplus support:
Hi Matan,
Thank you for reaching out. Sorry for the inconvenience that has caused to you. Rest assured that we will be providing you solutions in solving the issue.
You can also try to flash the device to the latest Oxygen OS, it is designed to fix common bugs that causes the issue.
To install OxygenOS on your OnePlus One, you need to flash the device. You may follow the guidance here:
https://forums.oneplus.net/threads/oxygenos-is-here-installation-guide.289398/
Please also note that since OxygenOS is a product from OnePlus therefore it is currently only available for OnePlus One.
Please don't hesitate to contact us for any update and feedback.
Thank you and have a good day.
Regards,
Jefflee
Click to expand...
Click to collapse
can i flash oxyOS (to check if it solve the problem) and after that flash your COS12 img with the fastboot commands or is there anything else i should know about?

flashed the latest COS12 version with your guide and i still have bootloops

Having this exact problem.... No wifi in CM11 and when updating tot CM12 getting boot looped.
Found a solution to your problem?

It's because of the modem files.. When u downgrade or upgrade from/to lollipop/kitkat u must flash the appropriate files!! Pm me if u want more info
Sent from my A0001 using Tapatalk

yes, i've open a ticket with oneplus one and their tech guy installed oxygenOS and it works well

From OOS 10.0.1 trying to install LOS 16.0 as a beginner and failing completely

I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?

It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.

TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.

remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?

I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well

In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.

I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?

[Solved] Sensors not working when using a Custom ROM with a custom vendor image

I have a weird problem:
When using Custom ROM's that use a custom vendor image, all sensors stop working. But when using Custom ROM's that use the stock OOS vendor image, Omni ROM and Paranoid Android, they work. On OOS they obviously work too.
Thing I've tried so far:
MSM Download Tool (Upgrade and SMT Download Mode)
Flash ROM's with fastboot
Flash ROM's with TWRP
Firmwares I've tried so far: 10.3.0 (global), 20.0.3 (eu), 10.0.2 (eu)
I don't know why only I have this bug apparently. I would appreciate everyone's help into investigating into this.
btw here's a log of crdroid (this rom uses a custom vendor image) for those who want to check it out: https://www.dropbox.com/s/3myddc1rzijqbcm/log.txt

What is your method to flash crdroid rom?

c3drik 67 said:
What is your method to flash crdroid rom?
Click to expand...
Click to collapse
I have tried both fastboot and twrp (for twrp i followed the official instructions)

I finally fixed it (somehow): Used msm download mode one more time and now it works!

hellcat50 said:
I finally fixed it (somehow): Used msm download mode one more time and now it works!
Click to expand...
Click to collapse
Am also facing few problems from few days bro,
Camera is crashing
Torch is disabled
Sensors are not working.
I also tried:-
-Flashing Custom Roms
-Flashing Stock Roms (A9 , A9(beta), A10)
-Used MSM Tools also no use was there:'(
Device:- OP5{CHEESEBURGER}

Xiaomi Poco F1 touch not working after installing TWRP!

Hey guys i have an issue,
i was running Pixel Experience 10 but on MIUI 10, i couldn't update the last one so i thought to get back to stock rom, update to miui 11 and then get back to my Pixel rom. I DID A F*CKING MISTAKE. I installed the Miui 11 Update through TWRP without restoring the stock miui 10 rom. It worked but i had lost my Pixel rom ( i have a backup), ok then i installed TWRP at the MIUI 11 because recovery mode got me at Xiaomi Recovery for some reason. Inside the TWRP i flashed Disabled forc Encryption, but it didnt flash the Magisk, i reboot to system and after 100 bootloops i tried to go back to recovery mode, it boot at TWRP but since then, the TOUCHSCREEN DOESN'T WORK.. I used xiaomi mi flash tool to return to stock rom, it did, locked the bootloader etc...the touchscreen still doesn't work though... I can connect a mouse with OTG Type-C and i can do anything you tell me in order to fix it.. i have already update to MIUI 11, unlock the bootloader, installed TWRP and have Root. Has anyone any idea or a solution to try?
Thanks everyone in advance.

diamoc said:
Hey guys i have an issue,
i was running Pixel Experience 10 but on MIUI 10, i couldn't update the last one so i thought to get back to stock rom, update to miui 11 and then get back to my Pixel rom. I DID A F*CKING MISTAKE. I installed the Miui 11 Update through TWRP without restoring the stock miui 10 rom. It worked but i had lost my Pixel rom ( i have a backup), ok then i installed TWRP at the MIUI 11 because recovery mode got me at Xiaomi Recovery for some reason. Inside the TWRP i flashed Disabled forc Encryption, but it didnt flash the Magisk, i reboot to system and after 100 bootloops i tried to go back to recovery mode, it boot at TWRP but since then, the TOUCHSCREEN DOESN'T WORK.. I used xiaomi mi flash tool to return to stock rom, it did, locked the bootloader etc...the touchscreen still doesn't work though... I can connect a mouse with OTG Type-C and i can do anything you tell me in order to fix it.. i have already update to MIUI 11, unlock the bootloader, installed TWRP and have Root. Has anyone any idea or a solution to try?
Thanks everyone in advance.
Click to expand...
Click to collapse
did you find a solution, I have the same problem. Thanks

Question GLtools crash 😭

Hello, my problem is that after I installed Nusantara 12 without upgrading to A12 firmware, cause a major crash in my vayu, previously it can run google assistant and gltools, but after the update it kept on crashing again and again, I've tried flashing stock firmware but nothing works, does anybody knows any other options to revert to factory?

flash fastboot rom to solve the problem

Ramesh006 said:
flash fastboot rom to solve the problem
Click to expand...
Click to collapse
nvm the problem was I keep using the backup packages made from the A12, use the A11 backup and everything went back to normal