Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
The usual way can mean a lot, but most important, did you use Magisk 25.1?
Cheers
Tom
ne0ns4l4m4nder said:
Just did the 13.2 update, rooted the usual way. And Bluetooth is crashing when I boot or reboot. And won't turn on at all. Any ideas or solutions besides a clean install
Click to expand...
Click to collapse
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Lughnasadh said:
No problem here with Bluetooth crashing when booting or rebooting using Canary Magisk 25101 (same as Stable 25.1) on A13B3.2.
I clean flashed A13B2 and dirty flashed the updates to A13B3+
Click to expand...
Click to collapse
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
AlkaDragos said:
Hey, do you know if keeping the root with OTA updates works? Or for each update I need to sideload it? Thanks
Click to expand...
Click to collapse
In the past it has worked for some but not others. The key is to make sure you haven't made any modifications to any of the partitions. For example, if you are using a custom kernel it won't work unless you flash all the modified images back to stock beforehand.
Also make sure you patch your own boot image so there is a stock boot image backup Magisk can restore.
Related
Hi everyone,
Anyone able to help out here trying to installer SuperSU but just end up with a boot loop of the CyanogenMod logo when installing SuperSU from app store or flashing via TWRP.
Yes I do know that CyanogenMod already has the root option that can be enable under developer options which I have tired but one of the apps I am trying to use needs SuperSU to work correctly.
So is there anyway to get CM13 working with SuperSU?
Flash SuperSU.zip
AFAIK, supersu does not work on CM13.
Really don't tell me that
jecatch said:
Really don't tell me that
Click to expand...
Click to collapse
If it's root you want, you can enable Developers option and in that you will find an option for root.
How did you manage to get out of the loop I have the same problem
gh_pics said:
How did you manage to get out of the loop I have the same problem
Click to expand...
Click to collapse
You need to reflash the ROM. Clean wipe is recommended.
gsstudios
Has anyone had any luck getting Magisk installed and working on a custom rom yet? I tried it on the CM13 Rom but root would just turn back on within a second. link for Magisk install http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Thank you
Wait until Magisk V7 is released.
Its states under known issues "HTC One M9 (yes, this particular device): sepolicy issues, should be fixed in v7" .
If you have a twrp backup of a rom that has the last build in it go to the app store and download an apk backup app and backup the pokemon go.apk and reinstall it in a newer rom build and don't do the update. Older version is still working until they finish rolling out the update.
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
I've gotten magisk to boot up once with phh superuser. However as soon as I tried to flash the systemless xposed from twrp. I would get stuck in a boot loop. I was unable to get it to boot up anytime I flash magisk now. I am S on but I don't think that should do anything with the rom.
Magisk works great on my Nexus 7
tws101 said:
Just to give an update on this....
I used BadBoys rom and I went into SuperSU and did UNINSTALL UNROOT... Which is the first step you need to do for Magisk.... This allowed me to PASS the Safetynet TEST... I can reverse this in moments since I am S-OFF by reinstalling SuperSU and reflash the binary from TWRP
*****So I am under the impression that when Magisk v7 comes out and works for this phone. It "Should" work with BadBoys. Until then I am just reinstalling SuperSU when I need it
Click to expand...
Click to collapse
This is what Ive ended up doing. Thank you
Another update
http://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
As you can see above today we still only have Magisk v6 and not v7 which we need to work with this phone model.... I will update again as soon as I can test v7 which they are still working on.
I installed CM13 via TWRP onto my KFHDX 7" (thor). However, 4G LTE isn't working. It isn't detecting my SIM Card.
(the zip I flashed is cm-13.0-20161001-NIGHTLY-thor.zip )
GameExpertNetwork said:
I installed CM13 via TWRP onto my KFHDX 7" (thor). However, 4G LTE isn't working. It isn't detecting my SIM Card.
(the zip I flashed is cm-13.0-20161001-NIGHTLY-thor.zip )
Click to expand...
Click to collapse
Known issue - shown as 'not working' in CM 13 OP (here). CM11 and FireOS are the only two roms that fully support LTE on this device.
*sigh* Ok.
After successfully unlocking the bootloader on my Fire HDX 8.9 Apollo I flashed the newest nightly build of CM13 (cm-13.0-20161006-NIGHTLY-apollo) and tested it. Everything was ok (I was able to set up the system with wifi etc.) , then I continued with flashing Gapps and SU and after the reboot I was stucked at the CM boot screen. Switched Kindle off - only boot screen again. Tried everything again (factory reset, flashing CM-Build&Gapps&SU, this time without a test and still stucked with the boot screen logo. TWRP is working fine.
Any suggestions? Thanx!
Alle9ne said:
After successfully unlocking the bootloader on my Fire HDX 8.9 Apollo I flashed the newest nightly build of CM13 (cm-13.0-20161006-NIGHTLY-apollo) and tested it. Everything was ok (I was able to set up the system with wifi etc.) , then I continued with flashing Gapps and SU and after the reboot I was stucked at the CM boot screen. Switched Kindle off - only boot screen again. Tried everything again (factory reset, flashing CM-Build&Gapps&SU, this time without a test and still stucked with the boot screen logo. TWRP is working fine.
Any suggestions? Thanx!
Click to expand...
Click to collapse
TWRP -> Wipe -> Advanced -> System/Data/Cache/Dalvik. Then reflash everything in one operation before rebooting.
Davey126 said:
TWRP -> Wipe -> Advanced -> System/Data/Cache/Dalvik. Then reflash everything in one operation before rebooting.
Click to expand...
Click to collapse
Thank you! I think I found a source of my problem: I flashed an (outdated) version of SU (2.46). Which version is recommended (or just try the latest?)
Alle9ne said:
Thank you! I think I found a source of my problem: I flashed an (outdated) version of SU (2.46). Which version is recommended (or just try the latest?)
Click to expand...
Click to collapse
You don't need SuperSU with CM13. Just use the native root manager found under developer options. Some have reported WiFi issues with recent SuperSU builds. That said, if you opt to keep it the latest stable build is your best bet.
Davey126 said:
You don't need SuperSU with CM13. Just use the native root manager found under developer options. Some have reported WiFi issues with recent SuperSU builds. That said, if you opt to keep it the latest stable build is your best bet.
Click to expand...
Click to collapse
Ok, I think I am one of this persons with Wifi problems after installing the latest SU. What is the best way to remove SU?
Alle9ne said:
Ok, I think I am one of this persons with Wifi problems after installing the latest SU. What is the best way to remove SU?
Click to expand...
Click to collapse
SuperSU (not SU...) has its own uninstaller under settings (within app); works well. If you want 100% assurance wipe system/data in twrp and reflash rom+gaaps.
My SM-G900T is running Lollipop 5.1.1 rooted by installed twrp-3.0.2-2-klte + SuperSU using odin.
I am planning to update it to Marshmallow 6.0.1 (G900TUVS1GPK3) using odin. After the update, I believe the phone will be unrooted. Should I install twrp-3.0.2-2-klte + SuperSU again in order to bring back the root?
Yes, is the short answer. It's a pretty simple process, just flash the update, boot back to Download, flash TWRP, boot to recovery, then flash SU. However, after some experimentation, I'd recommend an extra step, especially if you're planning to run Xposed. After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
I'm not sure if you'll also need to wipe or not, all the updates I've done have been MM->MM. You can flash those without any wiping or restoring because they don't touch /data. I've found that switching between stock & modified MM roms without wiping appears to work but later causes severe performance problems. Between stock updates, I've had no problems even without wiping.
invisiblewave said:
Yes, is the short answer.
Click to expand...
Click to collapse
Thank you Invisiblewave. I understand that I need to reflash twrp, but since I installed SuperSU already and I think the update would not delete/uninstall it, if I flash SuperSu again, will there be a problem?
The update will remove your previous SuperSU install, so yes, you have to flash it again if you want root.
invisiblewave said:
After flashing the update, boot into the stock recovery and let the phone boot normally after the stock recovery does its thing. Without this step, Xposed breaks Wifi Calling, and my guess is there are other things which also break, since I get force-closed messages for a couple of T-Mobile processes if I don't let the stock recovery run. Once the phone has booted, just boot back to Download & then flash TWRP & install SU, and Xposed if you want it.
Click to expand...
Click to collapse
Thanks for the tips! I just did the same upgrade and wanted to make sure everything worked afterwards.
use this guide
https://forum.xda-developers.com/tm...l/root-how-to-root-sm-g900t-firmware-t3358190
That guide is incomplete. It needs an additional step after flashing the update to let the phone boot once normally, otherwise WiFi calling doesn't work. Flash update, reboot (stock recovery runs and does stuff), reboot to Download, then flash TWRP, SU, Xposed, etc.
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
I you have backup of efs partation of just restore that via twrp
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try?
characterdivide said:
Unfortunately I don't think so. I made a backup but without EFS partition. Is there anything else I could try
Click to expand...
Click to collapse
Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: DN2103_11_A.07 DN2103_11_A.10 *deleted DN2103_11_A.11 *deleted...
forum.xda-developers.com
Try to flash this
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
characterdivide said:
Thanks, I will try that! Should I flash the complete rom? Or only one of the update parts (for example V10 to V11 update)?
Click to expand...
Click to collapse
Yes
characterdivide said:
Hello! I tried to install the newest official OTA update while being on v10 (rooted with Magisk). It rebooted to TWRP and I tried to install the OTA manually in TWRP. Schouldn't have done this... this is where all the problems started. I was afraid I bricked my phone for a few hours, but finally I managed to get it back up. I'm now running the newest official OTA update.
Unfortunately, wifi and bluetooth isn't working. Mobile data (LTE) is working fine. Everything else works just fine. Does anyone here have any idea what the problem can be? If I remember correctly, wifi and bluetooth problems are often due to modem or firmware problems? Or maybe a problem with boot.img or vbmeta.img? I've messed with vbmeta.img and because I have full root with Magisk my boot.img is also modified. Thanks a lot for your help!
Edit: some additional info:
Build number: DN2103_11_A.11
Smallbandversion: M_V3_P10,M_V3_P10
Kernel-version: 4.14.186+
If I go to about phone -> status it shows no bluetooth address and no mac-address for wifi.
Click to expand...
Click to collapse
Can you tell me what happened actually while updating? Did you successfully flashed new update in twrp or some else
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
So
characterdivide said:
Okay, I try to write everything down that I still remember. Frist, I tried to install latest official OTA on my rooted phone. It tried to restart into recovery, where I manually installed the official OTA package. After that, my phone didn't boot. It was stuck on the oneplus boot animation. I tried to restore a backup I made of the stock rom V10. After that, I don't remember exactly what I did, but I think I flashed the vmbeta.img from the 'how to root oneplus nord 2' guide. I also tried wiping cache, data, etc. multiple times. After another time of trying to restore an old backup + formatting the whole phone it booted and seemed to work fine. Until I discovered that bluetooth and wifi weren't working...
Click to expand...
Click to collapse
Someone told me that after downloading incremental update package ROM Boots to twrp but failed to flash update and nothing happened he booted to old OS
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
characterdivide said:
Yes, that's right, after auto reboot nothing happened in TWRP, but I manually navigated to the .zip file of the OTA update and installed it in TWRP. For me this worked and the OTA succesfully installed. But I think this didn't work as it should because my phone was rooted using Magisk. Maybe it has something to do with the fact that my boot.img was patched by Magisk? And installing the OTA over that would cause problems?
Click to expand...
Click to collapse
So you have to flash old roms boot.img it will. Help to back everything
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Give me V10 stock image FOR DN 2101
And after flashing this will our TWRP avilable or Not agian?
Done
characterdivide said:
Thanks a lot! It worked, I'm so relieved!
For anyone else who broke their phone this way: flash V10 stock image -> flash V10 to V11 update .zip -> flash vbmeta.img. Boot phone and it's fixed.
Click to expand...
Click to collapse
Im having same issues as you could help me out what image did you use and how. Thanks in advance.