Hi!
My Oneplus 6 is rooted and since I updated it to Pie I have a problem. When I plug my (off) phone in order to charge it, it will start but get stuck on the "bootloader is unlocked..." message, never moving on. However if not plugged the message will appear for a few seconds and the phone will start normally. Also, if I plug it while on, there won't be any problem, the phone will charge. On other aspects the phone is doing great and the root is working well.
Any thought?
Thanks a lot,
Corto
Hi, how did you root?
CoffeeMachineSwitch said:
Hi, how did you root?
Click to expand...
Click to collapse
Hi! Thanks for your answer. I used the oneplus.gadgethacks's guide to root (unlocked the bootloader, installed TWRP, Magisk Manager App, then booted into TWRP to install Magisk).
When Pie was released, I booted into TWRP to install the official Pie ROM (9.0.1 cause I have a French phone) then installed the last TWRP Installer, changed the slot (A to B) before rebooting, and booted again in TWRP to install Magisk, before wiping the cache.
I did it two days ago and except for the problem I raised everything is working great and the root it still working!
Up!
Its a normal bug since OB4, mostly happening on custom kernels
byReqz said:
Its a normal bug since OB4, mostly happening on custom kernels
Click to expand...
Click to collapse
Thanks for the answer! So I'm just waiting for a new firmware update?
CortoMaItese said:
Thanks for the answer! So I'm just waiting for a new firmware update?
Click to expand...
Click to collapse
Today i updated to last OOS 9.0.2 using twrp, after i flashed twrp and magisk. All works fine, but i have the same issue, stuck at bootloader and no charging. To charge it, i have to power on and after plug the cable.
Inviato dal mio ONEPLUS A6000 utilizzando Tapatalk
Same here
Same. 9.0.2.
Anyone tried a custom Kernel?
Since 9.0.2 same Problem
I tried Blu Spark Kernel r51. No change.
Yes it is kernel related. Because without kernel it charges. I already tried with 3 different kernel and it happens with all of them
I had this issue as well but not anymore..am not sure what's I changed...am on Open beta 6. Try making sure frimware is up-to-date on both slots.in recovery Flash oos then twrp...reboot into twrp then flash oos then twrp again then boot.
Yes. What magisk version are you using.. version 17.3 or 17.1 cause this issue.. try magisk cannary build 17.4 .I am also in pie stable 9.02 and I did fix it with this version
Iwas on Magisk 17.1 and tried your uploaded Magisk Version.
Issue still present.
I'm on 9.0.2 with blu spark Kernel.
Later i will reflash my Rom an try it with the original kernel.
---------- Post added at 05:22 PM ---------- Previous post was at 04:54 PM ----------
I reflashed the Rom with the actual TWRP and used the original kernel from 9.0.2 with Magisk 17.4.
Nothing changed. Issue is still there.
TheMAD1980 said:
Iwas on Magisk 17.1 and tried your uploaded Magisk Version.
Issue still present.
I'm on 9.0.2 with blu spark Kernel.
Later i will reflash my Rom an try it with the original kernel.
---------- Post added at 05:22 PM ---------- Previous post was at 04:54 PM ----------
I reflashed the Rom with the actual TWRP and used the original kernel from 9.0.2 with Magisk 17.4.
Nothing changed. Issue is still there.
Click to expand...
Click to collapse
Strange. I am on 9.02 ROm, stock kernel , and flash This MAgisk version 17.4 and I can charge my phone normally. I know is a magisk issue, because if you go to the Magisk cannary build section , the developer is aware of this issue. Also happens in Pixel Phones
---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------
Rogue8o8 said:
I had this issue as well but not anymore..am not sure what's I changed...am on Open beta 6. Try making sure frimware is up-to-date on both slots.in recovery Flash oos then twrp...reboot into twrp then flash oos then twrp again then boot.
Click to expand...
Click to collapse
Are you root ???.. Or only TWRP..?? MAgisk is causing this issue
Am rooted...magisk 17.3
You are right, it is a Magisk problem. I uninstalled Magisk and now i can charge my phone switched off.
I will try to reinstall 17.4
---------- Post added at 07:10 PM ---------- Previous post was at 06:49 PM ----------
After reinstalling Magisk 17.4 the issue is present again.
Perhaps there is a difference from which slot you are booting.
Just guessing.
TheMAD1980 said:
You are right, it is a Magisk problem. I uninstalled Magisk and now i can charge my phone switched off.
I will try to reinstall 17.4
---------- Post added at 07:10 PM ---------- Previous post was at 06:49 PM ----------
After reinstalling Magisk 17.4 the issue is present again.
Perhaps there is a difference from which slot you are booting.
Just guessing.
Click to expand...
Click to collapse
MAybe i should wipe everything and install Beta 6 and try with 17.4, But the developer of magisk is already aware of this issue and is working on a solution
Related
Hi guys, I just received the OTA update's notification, tried to install but "/system/framework/core.odex has unexpected contents" error appeared. I tried to wipe cache but it still appear.. what can I do?
I have uninstalled xposed and modules, and other apps that modifies system's files
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
here is the zip file? if i delete the zip file, the bootloop disappear?
AndroidHtc101 said:
Same here, I get the 4.4 upgrade uk version, reboots and goes in bootloop so I had to delete the zip file. I have uninstalled exposed all modules too and turned off root no joy
Also guys Will this update fix the famous "touch to retry error"? I heard in this upgrade there is a new radio?
thanks for all your help i know your busy
---------- Post added at 08:29 PM ---------- Previous post was at 08:26 PM ----------
forgot to mention im on CWM recovery not stock and on 4.4.2 with modifications from exposed modules.
Click to expand...
Click to collapse
It has been said already countless times now.
You need to be completely stock to be able to update via the official OTA.
Flash stock recovery, stock /system and then you'll be able to update.
I get an error while updating, it just says ''error''. I have stock kernel, stock recovery, unrooted... Nothing seems to work. I think the problem might be that I have a custom boot animation. Is there any way to flash the 4.4.2 stock UK rom?
Just interested to know many of you have rooted & had any issues. Twice I've been rooted myself & had to use msm recovery program to get me up & running again!
First time it worked well for a few weeks but then I had a charging issue that eventually got me stuck in fastboot. Second time the phone simply gave up after using titanium to remove bloatware
I love my OP7P but never had issues like this on any Samsung device. TWRP backups cause major issues as well!
Had no issues with Root like those. I'm not using TWRP.
No issues with my phone i'm rooted since 1st day and i use twrp
c3drik 67 said:
No issues with my phone i'm rooted since 1st day and i use twrp
Click to expand...
Click to collapse
Whatever you do don't attempt a recovery backup, it won't work
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
mike710_0 said:
Whatever you do don't attempt a recovery backup, it won't work
Click to expand...
Click to collapse
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
No issues, rooted, love it.
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
No I haven't but I'll certain give it a try. Usually when I backup I select everything
Zero issues
Root w/ Magisk 19.3
TWRP unofficial installed
Handful of Magisk Mods
Renovate ROM
Kirisakura custom kernel
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Same. You hit the nail on the head.....backup and restores fine.... But you have to follow these rules....running twrp, magisk, bunch of modules..... everything is kosher
Make sure you're only using stable magisk
The others cause charge issues
vtec303 said:
Rooted, decrypted and twrp from day one, no problems whatsoever, cheers.
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Have you tried backing up selecting boot, system image, vendor image, data and leave the rest. Works for me every time backing up or restoring no problem. On the link scroll down and read "Tips", hope this helps, cheers.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ??
mike710_0 said:
You sir are an absolute legend! Just done this & it worked great.
Thanks very much ?
Click to expand...
Click to collapse
No problem, you are welcome. Enjoy ?
I woke up today to a prompt to upgrade Magisk Manager to 7.3.5, and Magisk to v20. v20 is the one that adds support for Android 10 and complete changes how system_as_root works (which made me nervous).
I was running Magisk v19.3, having never been prompted to install v19.4.
I'm here to report that both install just fine. I have a bunch of modules installed: busybox, debloater, f-droid, magisk manager recovery, riru, edxposed, tzdata. I can't tell if it's using "compat mode" or not. I guess that depends on the specific modules you've got?
I created a new patched_boot for 10.0.14.0 with Magisk v20 (not sure if this is necessary for re-patching now that 19.3 is not current). https://yasmar.net/xda/patched_boot_10.0.14.0_20.img.gz
I'm using it on cr driod works well
on what rom are you running this? i am on 10 gsi rom from here and in v19 riru and edexposed gave me bootloops no mather what i did
Using it on latest stock, no problems so far
loop4444 said:
on what rom are you running this?
Click to expand...
Click to collapse
Stock 10.0.14.0
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.
a1291762 said:
Left the house this morning and mobile won't connect. This does happen to me occasionally, but the timing seems suspicious.
Click to expand...
Click to collapse
And it's back. Stupid mobile network blacklisting me for rebooting
Coincidentally, my TWRP is dead so I'll need to put that back when I get home. Probably affected by the Magisk upgrade.
After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).
a1291762 said:
After upgrading to 10.0.15.0 I noticed that I can't get TWRP and Magisk 20 to be installed at the same time anymore. The normal boot works but TWRP fails to start. I suspect it's Magisk 20 rather than 10.0.15.0, and I just forgot to check that TWRP was still working (since I rarely use it).
Click to expand...
Click to collapse
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'
yashinodon said:
It may be the fault of Magisk V20 because while I was on 10.0.14.0, I installed TWRP then Magisk... Then, rebooted to recovery but states 'System has been destroyed'
Click to expand...
Click to collapse
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Pat750 said:
How did you get it to boot again?
I remember having that message when I got this device back in April and had to flash an old aboot file from an Oreo ROM.
Click to expand...
Click to collapse
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
Right, thanks for the info.
Haven't tried Magisk 20 yet, I still use 18.1. Maybe we need an updated TWRP, but since 33bca aka offain left this device I don't have high hopes...
yashinodon said:
I just pressed the power button so that it would shut down, then booted to system (powered on) again without having any problems.
---------- Post added at 12:34 AM ---------- Previous post was at 12:33 AM ----------
Maybe you flashed something different... I only flash TWRP and Magisk, I think it conflicts with each other that's why booting into TWRP will show 'System has been destroyed' alert.
Click to expand...
Click to collapse
When you see "your system has been destroyed " ,it's most likely conflict between magisk and some module , the easiest fix is to 1.boot to twrp via PC , use magisk manager for recovery. zip and disable all modules.
2. if your recovery says :data is encrypted -flash different kernel , that will disable magisk , reboot to recovery , use magisk manager for recovery , disable all modules and flash magisk again .
In both of the cases you won't need to reflash stock rom every time you see that message , if you want to use twrp again
P. S. BTW , there is an 20.1version of magisk and magisk manager 7.3.6 already
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Stefan-Duisburg said:
Hello everyone.
As mentioned above, my HTC is stuck in a Bootloop (Unlocked warning, white HTC Icon, and again) after I uninstalled a Magisk Module via Magisk Manager. I have no TWRP Recovery installed. Any advise how to get the phone operational again? In case of a full reset of data and storage, i am not afraid to do so. Any help is much appreciated.
Greetings
Stefan
*Edit*
I just noticed that adb doesn't recognizes the Phone via command adb devices. Therefore I'm not able to flash a ruu for my phone. Now I have no idea left what to do
Click to expand...
Click to collapse
you can flash from sd card
---------- Post added at 11:29 AM ---------- Previous post was at 11:26 AM ----------
tolgazorba said:
you can flash from sd card
Click to expand...
Click to collapse
You can find the same software number at the top of the device or the numbered software in the android file host ziand folder
Hello @tolgazorba.
Thank you for your answer. Right now I'm heading to work, but I will try your Advise this evening. Fortunately i downloaded a ruu zip matching with my firmware (2.55.bla bla) and matching with my cid as well. I will report if everything worked, or, hopefully not, not.
Thanks again
Stefan
hello
no problem I would like to explain in detail but my english is very bad
Hi there. That advice was great, everything works now fine again. I guess I let my hands off rooting for now, at least there's an official LOS for this device lol
Thanks again
En joy
You're welcome
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Merhaba
are you serious
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
lulonen said:
I have little similar problem. I bricked phone after updating magisk.
Then I tried to flash original boot.img but didn't know which slot A or B so flashed both. Unfortunately, it doesn't help.
Please help me
Click to expand...
Click to collapse
because I need help with something
---------- Post added at 06:55 PM ---------- Previous post was at 06:49 PM ----------
my problem is that i can't assign custom rom to your device why do you think
I thinked that's because of slots
Hi
buddy what exactly is the problem
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
lulonen said:
completely don't know how to solve it.
bootimg flashed over TWRP, now i have original boot.img and cant start temporary recovery.
Click to expand...
Click to collapse
Maybe just flash actual firmware.zip with sdcard as i have done? With that you are back on full stock and you can root again etc...
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
hi
lulonen said:
Thx. unfortunately, I don't have a backup of one important app which is more important than the whole phone so I want to find every possibility without losing data.
Click to expand...
Click to collapse
You are a very old user, I think you know how to do it
Hi
full rom viper twrp with temporary rom flash without wipe i not temporary to permanent summer device
can't boot TWRP and dont have stock rom without wipe.
Don't you know why I can't boot temporary TWRP? download mode always stuck at booting
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
isn't full wipe?
don't remember but EU version (043). I am on LeeDrOiD U12 V1.3
re-install the same rum without deleting or update it with adb sideload
tolgazorba said:
so find a backup of the auto and load it with adb sideload, whichever version you have is the backup of that version
---------- Post added at 04:09 PM ---------- Previous post was at 04:03 PM ----------
https://androidfilehost.com/?fid=6006931924117931578
Click to expand...
Click to collapse
If I only had a backup different to TWRP.... ;-(
I decided to update my beloved OnePlus 7 Pro from OOS 10.0.3 to OOS 10.0.4 through TWRP after downloading the OOS 10.0.4 full zip from Oxygen OS Updater. After flashing the full zip and TWRP, I flashed latest magisk zip. Then rebooted and suddenly I noticed that baseband was unknown and IMEis were missing. I downloaded & flashed again the full 10.0.4 zip alongside latest TWRP and Magisk but still facing the aforementioned issue. Then I just flashed the full OOS zip so I could receive calls. Tried with flashing patched boot image but the issue persists.
I came across some commands that would fix this issue over Terminal in TWRP but useless...
I do state that I have the GM1913 EU OP7Pro
Has anyone so far encounter this issue and if yes, how did you manage to get past over this issue?
Help will be very appreciated!
You can try the MSM tool.
Have you tried disabling and deleting all magisk modules before flashing a rom.?
---------- Post added at 11:32 AM ---------- Previous post was at 11:26 AM ----------
I happened to experience loosing IMEI after updating to 10.0.2 .. what i just did was simply switch to other bootslot. Disable all magisk modules.. then reflash the full rom.. not by TWRP.. BUT thru local upgrade in system updater..then withoit rebooting.
Install Magisk to inactive slot.. then reboot..
This steps loose my Twrp.. but i just simply reinstall twrp via magisk module.. then install magisk thru direct install, then reboot to recovery... Boom..all.is well..
mholloway said:
You can try the MSM tool.
Click to expand...
Click to collapse
Thanks for your suggestion
santiagoruel13 said:
Have you tried disabling and deleting all magisk modules before flashing a rom.?
---------- Post added at 11:32 AM ---------- Previous post was at 11:26 AM ----------
I happened to experience loosing IMEI after updating to 10.0.2 .. what i just did was simply switch to other bootslot. Disable all magisk modules.. then reflash the full rom.. not by TWRP.. BUT thru local upgrade in system updater..then withoit rebooting.
Install Magisk to inactive slot.. then reboot..
This steps loose my Twrp.. but i just simply reinstall twrp via magisk module.. then install magisk thru direct install, then reboot to recovery... Boom..all.is well..
Click to expand...
Click to collapse
Thanks so much for saving me from a headache (and whatnot)! I don't usually disable Magisk modules while I update OOS(I learned my lesson) but I gave a try after you replied and apparently one of the modules (OOS Native Call Recording Enabler) was causing the whole issue! So I have to live without that module till it gets updated but at least I got my baseband and IMEIs back!
Thanksss so much once again! My issue got resolved!
Nexus4life said:
Thanks so much for saving me from a headache (and whatnot)! I don't usually disable Magisk modules while I update OOS(I learned my lesson) but I gave a try after you replied and apparently one of the modules (OOS Native Call Recording Enabler) was causing the whole issue! So I have to live without that module till it gets updated but at least I got my baseband and IMEIs back!
Thanksss so much once again! My issue got resolved!
Click to expand...
Click to collapse
For OOS Native Call Recording use jonePlus from playstore
zelenko said:
For OOS Native Call Recording use jonePlus from playstore
Click to expand...
Click to collapse
Thanks so much mate, I got OOS Native Call Recording back along with a ton of other customisations!
Really appreciate your suggestion!
Nexus4life said:
Thanks so much mate, I got OOS Native Call Recording back along with a ton of other customisations!
Really appreciate your suggestion!
Click to expand...
Click to collapse
Mine keeps asking for permissions, but all permissions given, but still won't open recordings, how did yours go.
NHNXDA said:
Mine keeps asking for permissions, but all permissions given, but still won't open recordings, how did yours go.
Click to expand...
Click to collapse
Mine worked on the beginning but after I rebooted, call recording isn't be available on my caller id screen unless I run the app first so Magsik can grant permissions.