Clean flashed OOS 5.0 with magisk 14.5 beta the phone worked fine for 2 days then suddenly it started rebooting continuously.
Dirty flashed the build but faced the same issue after few days.
Downgrade to OOS 4.5.1 or flash custom ROM - this is OOS 5 bug.
I had the same issue but after a wipe cache, it seems to be fixed for some days, repeat the process if you have this issue after
This issue happened to my device too, just a day or two after flashing OOS 5.0. I thought it was due to my custom kernel, but reverted to 4.5.1 after encountering more issues a few days after anyway. I never got to reproduce the reboot bug, but I had more than enough reason to go back to Nougat for now.
Side note: After I had the repeated reboots, I suddenly can't use my home and recents button and thought I had hardware issues. Good thing I found this: https://forum.xda-developers.com/showpost.php?p=73798002&postcount=5
Random reboot Oreo 8.0
I had this issue random reboot 3 to 4 times after clearing cache working properly and all apps were force closing
I'm using beta 14.3 with no issues
Factory reset will probably help.
Magisk 14.3 and 14.5 are perfectly compatible with Oreo.
Sent from my ONEPLUS A3003 using Tapatalk
Related
Everything was working great yesterday after I flashed the new 5.0 OOS through TWRP.
But this morning it was like my device suddenly decided to act funny. First it started FCing different apps all the time.
Then it got into a continuous restart loop.
Finally when it settled, I discovered all these problems:
- Home and recent buttons not working
- Developer options were empty
- Factory reset not working
- When I tried to reboot into recovery, I was asked for a password for decrypting data under a Mount title. I entered my pin and continued with some info for updating partition. I reflashed the stock 5.0 rom and the bluespark v.8.54 recovery, wiped cache, but nothing changed.
Any ideas?
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
thes3usa said:
Are you on the recommended version of Blu_Spark TWRP, which is v50?
Have you tried a complete clean flash of OOS 5.0, and not install any add-ons such as Magisk or another root method?
Did your phone usually request the PIN on boot?
Have you flashed anything else that may cause conflicts, such as V4A or any other mods?
Click to expand...
Click to collapse
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
No other mods, except naptime and AKT profiles that were running since OOS 4.1.5
Anyway, I decided to factory reset my device so I booted to TWRP recovery and wiped data. This didn't work out very well as the device couldn't finalise afterwards the setup wizard, where it's asking about which sim to use for calls/sms/etc.
Then I had 2 wipes of cache and it seems that everything was back in order. Now I flashed back Magisk and still everything looks good.
My TWRP version is the one that I have mentioned at my previous post. I thought that was the recommended version.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Everything looks fine now? Because when you said the device couldn't finalise the setup process, it may have been a corrupt flashable package. But since it's fixed now, that doesn't seem like the issue.
Sorry I was misinformed about the TWRP version, I thought there was only one version of TWRP by blu_spark that can be used. Turns out, there is another. Sorry about that.
Cheers!
Yee I hope the clean install did the trick.
Although 2 days ago everything was also running great before the catastrophic behavior.
And the worst part is that I have no clue what caused this. I didn't mess with root settings or new apps, had stock kernel installed and no new apps were installed recently.
Sent from my ONEPLUS A3003 using Tapatalk
Hi
Updated to latest open beta last day with twrp 3.2.1 and after flashing Magisk 16 am getting bootloops , tried turning Dev off and restarting no luck , tried Magisk 15 version also same bootloops , any idea why is this happening ??
Anything else you flashed with Magisk? Any Modules?
Nothing just Magisk only
Try using Acuicultors black themed TWRP and see if that fixes your issue.
Tried but the password is not getting accepted
Hello All, This is my first post.. Hope I get the help I need .
So the problem I facing was my wifi ic of Oneplus 3t was getting extreme hot (bluetooth never worked , kept searching but in vain ) and due to this it was draining my battery quite soon. I finally decided to get my wifi ic replaced which is pasted on motherboard. After getting it replaced my wifi was gone and bluetooth returned to life but the biggest issue was solved which was the heat issue.
I had installed custom rom before replacing ic to check whether they can help me cool down my phone.
So later when ic was replaced, I flashed the stock rom with MSMDownloadTool and got success, but after that whenever I tried to update to latest 5.0.4 uptill today, it installed fine but when restarted, it came to ONEPLUS round dots splash screen and after few seconds the dots would stop rotating and my phone would restart. After a few restarts it would come to the same stage and then comes to a screen
"encryption unsuccessful "... Now after a zillion tries I tried updating one by one which is in order
3.2.6
3.5.3
3.5.4
till here right now m on success ... All I want to know is what this issue is .. how can i resolve it ???
Here it goes the update.... as soon I updated 4.0.2 , the rom with NOUGAT. it stucks on bootloop
yudi.15 said:
Hello All, This is my first post.. Hope I get the help I need .
So the problem I facing was my wifi ic of Oneplus 3t was getting extreme hot (bluetooth never worked , kept searching but in vain ) and due to this it was draining my battery quite soon. I finally decided to get my wifi ic replaced which is pasted on motherboard. After getting it replaced my wifi was gone and bluetooth returned to life but the biggest issue was solved which was the heat issue.
I had installed custom rom before replacing ic to check whether they can help me cool down my phone.
So later when ic was replaced, I flashed the stock rom with MSMDownloadTool and got success, but after that whenever I tried to update to latest 5.0.4 uptill today, it installed fine but when restarted, it came to ONEPLUS round dots splash screen and after few seconds the dots would stop rotating and my phone would restart. After a few restarts it would come to the same stage and then comes to a screen
"encryption unsuccessful "... Now after a zillion tries I tried updating one by one which is in order
3.2.6
3.5.3
3.5.4
till here right now m on success ... All I want to know is what this issue is .. how can i resolve it ???
Click to expand...
Click to collapse
Try directly clean flashing OOS 5.0.5 from TWRP 3.2.3-0
Sent from my OnePlus3T using XDA Labs
Siddk007 said:
Try directly clean flashing OOS 5.0.5 from TWRP 3.2.3-0
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Ok I am about to start with your mentioned method in this post
https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Will update soon... Fingers crossed
Still on same stage the circle stops spinning and phone restarts
I dont get it , its booting 3.5.3 and 3.5.4 correctly just all of the later updates give this error... is it because my wifi is not in working condition???
Because for some extra information I can flash any 8.1 based rom without any problems... checked Bootleggers, RR and Havoc...
Please guide me
yudi.15 said:
Still on same stage the circle stops spinning and phone restarts
I dont get it , its booting 3.5.3 and 3.5.4 correctly just all of the later updates give this error... is it because my wifi is not in working condition???
Because for some extra information I can flash any 8.1 based rom without any problems... checked Bootleggers, RR and Havoc...
Please guide me
Click to expand...
Click to collapse
It sounds to me that this may be related to encryption of the data partition.
Are you flashing the full OOS ROM from https://downloads.oneplus.com ?
Are you using the latest TWRP from https://dl.twrp.me/oneplus3/ ?
If you aren't, then try using them.
If you still have problems then I would format the data partition in TWRP to avoid any encryption issues, then flash OOS and immediately flash the patched boot image from https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053 to prevent TWRP being replaced by the stock recovery.
Note that formatting the data partition will wipe your internal storage and you'll lose all files on your phone.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
It sounds to me that this may be related to encryption of the data partition.
Are you flashing the full OOS ROM from https://downloads.oneplus.com ?
Are you using the latest TWRP from https://dl.twrp.me/oneplus3/ ?
If you aren't, then try using them.
If you still have problems then I would format the data partition in TWRP to avoid any encryption issues, then flash OOS and immediately flash the patched boot image from https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053 to prevent TWRP being replaced by the stock recovery.
Note that formatting the data partition will wipe your internal storage and you'll lose all files on your phone.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Yes I flashed full rom... But the problem is just two roms go successful on my device. Rest of the roms no matter if I update them or flash fully they will get stuck on oneplus logo and then restart...
BillGoss said:
It sounds to me that this may be related to encryption of the data partition.
Are you flashing the full OOS ROM from https://downloads.oneplus.com ?
Are you using the latest TWRP from https://dl.twrp.me/oneplus3/ ?
If you aren't, then try using them.
If you still have problems then I would format the data partition in TWRP to avoid any encryption issues, then flash OOS and immediately flash the patched boot image from https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053 to prevent TWRP being replaced by the stock recovery.
Note that formatting the data partition will wipe your internal storage and you'll lose all files on your phone.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Tried to format data drive and install os and without any delay flashed the patched boot image as well but stuck on 1+ logo... Not even going to splash screen
yudi.15 said:
Tried to format data drive and install os and without any delay flashed the patched boot image as well but stuck on 1+ logo... Not even going to splash screen
Click to expand...
Click to collapse
Give it a few minutes - it may be re-encrypting the data.
Sent from my OnePlus3T using XDA Labs
Hello friends..(I am a noob )
Actually I was running on Oreo 8.1 lineage os 15.1 but then I wanted to flash oxygen os 5.0.5 stable ROM I searched for the thread on XDA and then followed it..
Here is what happened:-
1---First I clean flashed the ROM (oxygen os) using TWRP 3.2.3-0 successfully..
But then when I tried flashing magisk 17.1 my phone RESTARTED in between of magisk installation process...??
2--Then I tried it using Blu spark recovery
The same issue occured..
3-- then I tried flashing firmware 1st then OOS
Same issue occurred now my phone vibrated vigorously..
4--when I tried to just flash OOS
It again restarted...
5--Now I want to know how can I flash oxygen os with magisk using TWRP recovery ????
I had tried this process using magisk 14.3, 16,17,17.1
But none worked
Plz help me..
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
I always use bluespark recovery, I have flashed all Oxygen updates and magisk and never had such problems.
The restart is happening suddenly,in the middle of the flash or after it has finished?
Click to expand...
Click to collapse
Happening in between..??
Mayank7 said:
Happening in between..??
Click to expand...
Click to collapse
Can u pls elaborate..
How did u flash OOS using Blu spark ??
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
deetailed said:
2 days ago I just did the same (flash firmware, OOS 5.0.5 stable then magisk using TWRP 3.2.3)
At first I flashed magisk v16, then updated to v17, and here's where I encountered a problem, it keeps boot looping at the boot animation
But I solved it by just wiping data and repeat flashing the ROM & everything else
Just make sure none of the files are corrupt I guess, and wipe clean everything including internal storage (after backing up)
Click to expand...
Click to collapse
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
There is no reason to wipe internal files during flashing of new roms and Magisk latest version is 17.1, not 17 which was causing bootloops.
So your post is totally wrong and better next time be careful of what you are writing.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
OP said something about a clean flash, so he probably already cleared his data. So it shouldn't be a big deal if he does it again.
When changing from LOS to OOS you should always clear data anyway.
I think you might not be wiping everything before flashing. If you have a computer, I would follow this steps (assuming that you already backed up all your photos, documents, etc):
1- Download the factory image to your PC
2- Wipe EVERYTHING in twrp (through the advanced option)
3- Reboot to recovery
4- Connect your phone to the PC and send the factory image zip to the phone just like with any other usb drive.
5- Flash the file through twrp and inmeadiately flash latest magisk
6- Reboot to recovery and do a factory reset through twrp.
7- Reboot and be happy.
One or more of those steps might be unnecesary, but I always do it like that and it always works...
Have fun!
Hello,
I just installed the Update 9.0.2 for the Onplus 6
OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip
Usually I shut my mobile off during night and charge it.
The usual bahavior of the mobile is
switching on to charge mode ->
Bootloader unlocked warning ->
afterwards animation of charging the battery.
With the new firmware it stays at the Bootloader unlocked warning screen.
I checked already Magisk Versions 17.1, 17.2, 17.3.
Magisk Uninstall / reverse to stock boot image solved the behavior.
Dalvik Cache were cleaned.
Complete reset / format of all partition didn't solved it.
I think there is a bug with the magisk patched boot image that is causing the not switching inzo charge only mode.
Previous firmwares for Oneplus 6 had no issues with charging while being off.
Update: its an issue of the Stock Rom from oneplus.
9.0.2 freezing at bootloader warning
9.0.3 charge like expected
9.0.4 freezing at bootloader warning
You'll have to test the current Canary build before we can be sure it's still a bug.
Thank you for the hint.
I just did it.
Uninstalled 17.3.
cleaned cache and dalvik
Installed 17.4. canary release - checked charge behavior - same as before _ bootloader unlocked warning - no charging screen
Uninstalled 17.4. canary release
cleaned cache and dalvik
Installed 17.4. canary debug - checked charge behavior - same as before _ bootloader unlocked warning - no charging screen
grabbed attached logs
Strange.. phone is off right ? then all system and applications and Magisk not processing right?
But you said no problem with original bootloader...
Will try this after get home..
Sent from my ONEPLUS A6000 using Tapatalk
---------- Post added at 16:27 ---------- Previous post was at 16:15 ----------
Yes.. its true... No Charging After i had shut down my Op6
Sent from my ONEPLUS A6000 using Tapatalk
#offtopic
Are you able to use google pay with magisk on 9.0.2?
I have the same problem on a OnePlus 6 running the latest open beta 6 with canary release. Open beta 5 was working ok.
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk
I have the same problem. Stuck in bootloader warning while charging.
When you change the current slot in TWRP from Slot B (current) to Slot A and power off the phone and replug to charger, the phone shows the charging animation.
After a reboot and another "power off charging" you'll have the same problem as above.
Strange
I can confirm the same issue, looks like it still is as per the above posts in Canary.
habylab said:
I can confirm the same issue, looks like it still is as per the above posts in Canary.
Click to expand...
Click to collapse
+1
Same here
habylab said:
I can confirm the same issue, looks like it still is as per the above posts in Canary.
Click to expand...
Click to collapse
Inviato dal mio ONEPLUS A6000 utilizzando Tapatalk
Hi! Noticed the same problem already on 9.0.1, made a post about it: https://forum.xda-developers.com/oneplus-6/help/stucked-bootloader-message-charging-t3859775
Same here with 9.0.2, magisk 17.1 (latest stable), I will add that this bug appear installing 9.0, when I updated to 9.0.1 this problem disappear but when updated to 9.0.2 (so partition changed) this bug return so I reflashed (changing the slot another time) but the bug is still there.
For me no problem with oos 9.0. This bug has appeared with the 9.0.2 version
alem972 said:
Same here with 9.0.2, magisk 17.1 (latest stable), I will add that this bug appear installing 9.0, when I updated to 9.0.1 this problem disappear but when updated to 9.0.2 (so partition changed) this bug return so I reflashed (changing the slot another time) but the bug is still there.
Click to expand...
Click to collapse
Inviato dal mio ONEPLUS 6 utilizzando Tapatalk
i can confirm that is magisk related, completely unistalled magisk and charging screen reappared
---------edit---------
aaand magisk 17.4 didn't solve the issue
Any update on this issue?
I tried 17.1 and 17.3 and I have the same problem, please fix it!
Στάλθηκε από το ONEPLUS A6003 μου χρησιμοποιώντας Tapatalk
Testerofroms said:
Thank you for the hint.
I just did it.
Uninstalled 17.3.
cleaned cache and dalvik
Installed 17.4. canary release - checked charge behavior - same as before _ bootloader unlocked warning - no charging screen
Uninstalled 17.4. canary release
cleaned cache and dalvik
Installed 17.4. canary debug - checked charge behavior - same as before _ bootloader unlocked warning - no charging screen
grabbed attached logs
Click to expand...
Click to collapse
Any chance these logs will help development?
No change so far with latest cannary build ,,,
Same issue. Any build 17.1-17.4.xxxx on Canary does not work.
Sent from my OP6 using Tapatalk
Same issue on OP6T with latest 9.0.5.
Sent from my [device_name] using XDA-Developers Legacy app