So I installed magisk v12 via normal procedure; downloaded then installed from recovery, and the phone didn't boot after. Did not even get past the samsung j5 logo to the bootanimation. I've tried uninstalling SuperSu and then install magisk but didn't help. I "updated" the same rom I was using already and I can use my phone but I would like to install magisk. Anyone?
Phone:J500FN (2015)
Rom: Resurrection remix 5.8.3
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
American_Jesus said:
Weird, never had problems installing Magisk, even on secondary roms (multirom) when all other fail.
Wipe system, and install the ROM then Magisk, in case that doesn't work make a clean install (wipe system, data, dalvik, cache) and install only the ROM and Magisk (no gapps), if everything is working then install gapps the rest (apps, restore backups etc...)
Your Magisk could be corrupted, try download again and install.
Click to expand...
Click to collapse
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
ashyx said:
Wiping system will have no effect. Magisk nor supersu Install anything to system.
Restore the untouched boot.img then install Magisk only.
That should be all that is required.
Click to expand...
Click to collapse
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
American_Jesus said:
I said to wipe system in case of something installed on system before causing the bootloop (BusyBox, viper4android, etc...). Wasn't referring to Magisk or SuperSu.
That's way I said to install Magisk before gapps, to leave system untouched so it can diagnose the problem.
Click to expand...
Click to collapse
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
ashyx said:
Well considering he stated that it wouldn't boot directly after installing Magisk, we can deduce that it was likely Magisk that caused the issue.
Click to expand...
Click to collapse
I can't deduce anything, that's way I recommend to remove any modifications before install.
If you want to debug a problem start removing the variants.
Thanks guys! Problem solved. System wipe didn't do it. It was easier for me to clean install than restore the boot.img at the moment so that fixed it this time. Thank you again. ???
Related
So I completely wiped my Nexus 4 yesterday (everything but internal storage) and clean-installed the 12/29 CM13 nightly + nano Gapps. Everything was working great, installed a bunch of apps from Google Play, etc.
Then this morning I booted to recovery and installed SuperSU 2.46 via recovery zip flash (not via the app), which appeared to flash successfully/with no errors (plus I now see a supersu directory at the root level of my device).
I then rebooted and got stuck at the boot animation. Went back to recovery, wiped dalvik cache and regular cache, rebooted, and I'm still stuck at the boot animation. Reflashed the zip and then wipes dalvik/cache, still stuck.
Any ideas on (a) how to fix without rewiping-reflashing, and (b) how to get root on CM13? Thanks!
EDIT: Forgot to mention my bootloader is unlocked and I have TWRP recovery.
EDIT2: Appears to be solved. I simply deleted the "/supersu" directory in the TWRP file manager and it now boots fine. Unsure if it screwed up hidden stuff, but I didn't have to wipe my system partition, which is a win in my book.
You don't need SuperSU on CM since it has root acces integrated, you just need to enable it under developer options. Format system, cache/dalvik and reflash cm13 and gapps.
Well ****. Looks like I needed to use the newer beta versions of "systemless" SuperSU, like 2.56 or 2.61 for Android 6/CM13.
I wasn't aware that installing 2.46 would cause me to get stuck at bootup, though! That sucks. Still looking for a solution.
Ah I wasn't aware of that. Thanks!
I deleted the /supersu directory, reflashed the 12/29 nightly, wiped caches, and the phone got past the boot animation and booted normally. I'll reboot a few times and see if things are OK.
Saved me from having to format system yet again and redo everything.
Install 2.56b Beta thats working coz it uses systemless ROOT
Do not install 2.56b , because you won't be able to install 2.60+ supersu after that without reflashing system. Install 2.65 beta. It's stable and tested on cm13. I use it myself.
Thank you so much for this - I flashed 2.46 on cm13 on my motog3. I thought I'd lose all my data since I have device encryption and an external sd formatted as internal storage (which is unsupported in twrp for the moto3g, so it isn't accessible for backing up).
I just reflashed the rom and cleared cache and it's back to normal, encryption was fine, all my data is here, and the external sd card functions as well. Saved my ass.
I tried this and it didn't work. I installed supersu while on CM13 and it got stuck at the boot animation of CM. I deleted the /supersu directory reflashed the newest nighlty rom and wiped caches but still stuck at boot animation. I'm on TWRP btw
Doesn't cm13 have an option to enable root under developer settings?
Hi,
I have a problem installing 8.1 oreo roms on my phone. I follow standard procedure: wipe dalvik, cache, system, data -> install rom + gapps -> wipe cache. After my phone restarts, it displays rom logo, but doesn't load (even after 15-20 minutes of waiting). All I can do is load in fastboot and restore my backup. I use twrp 3.2.1-0, unofficial 8.1 pico gapps from 2018/01/30.
So far I tried:
-Installing rom and gapps separately.
-Installing rom, rebooting, installing gapps.
-Installing rom + gapps, then wiping data.
-Installing rom + gapps, then not wiping anything.
-Factory reset, then install rom + gapps.
-Installing rom + different gapps versions.
Additional notes:
-At one point I successfully installed NitrogenOS (about a month ago) and it is my current rom and backup. But I can't clean flash it again.
-When I install rom only (without any gapps) it boots up fine without errors or long loading.
Can anyone help?
Same problem I am also facing. Using Pixel experience ROM but now not able to flash cosmic official rom...remaining on bootanimation
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
Flash
Rom
Gapps
Wipe to factory reset
Reboot
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
devito666 said:
I also have the exact same problem.
Flashing ROM without gapps works perfectly.
adding gapps package, no matter if its pico aroma or mini, it results in stuck on boot animation.
wiping after flashing also did not work.
once made pixel experience boot, using it since...ota update worked without a problem.
any other suggestions?
Click to expand...
Click to collapse
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
sanchez8096 said:
Try this nano package https://androidfilehost.com/?fid=889964283620771808. It's the only one that worked for me.
Click to expand...
Click to collapse
Thanks for the Link!
But unfortunately still Not booting...tried atomic official and teammexs Rom...
metro20 said:
Hi buddy .
TWRP
Wipe Data, Dalvik, Cache , System, Internal Storage
*then tap back, FORMAT DATA and confirm by typing "yes"
Flash
Rom
Gapps
Magisk stable (if preferred if not next >>>)
Magisk beta (always flash after stable)
Busybox flashable zip (if needed)
Mods such as MIUI cam mod
Font package
Wipe to factory reset
Reboot
After 1st boot
Reboot to TWRP
Install Magisk modules ( USN or Viper4android etc)
Reboot system
Done ! That's the only way it worked for me
Click to expand...
Click to collapse
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Suo.Eno said:
ftfy. But before this ensure that:-
1. Non corrupted ZIPs. Avoid if possible from using mobile data. A slower yet stable WiFi yields better success rate.
2. Currently this unofficial opengapps' builds works better and are more current.
Click to expand...
Click to collapse
I didn't need to format data on Oreo nos
As mentioned in other threads on this topic, I just wanted to mention here as well that I am also affected by these Oreo boot loops and haven't found a solution yet. I somehow managed to get PixelExperience to install once, but downgraded now to a Nougat build for other reasons (better battery and GCamMod compatibility).
sanchez8096 said:
Thanks for answer. I tried that method too, but it still didn't work for me. I recently tried clean flash with gapps from https://forum.xda-developers.com/xiaomi-redmi-3s/development/rom-lineageos-15-1-t3718757 and it worked flawlessly. So maybe it's an issue with some gapps packages?
Click to expand...
Click to collapse
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Sunny Za said:
Use twrp 3.2.1-0 bcoz some Oreo ROMs aren't flash able by 3.1.1
Click to expand...
Click to collapse
I am using 3.2.1-0 twrp. Rom itself flashes fine, it's the gapps that create infinite boot.
Exact Same issue Here...
I have same problem too .. can't boot in to any Oreo ROM with Gapps .. really isn't any solution here?
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
sanchez8096 said:
This might not be a proper solution, but here's what I did:
1) Wipe data, cache, dalvik, system
2) Flash rom + gapps(I used NitrogenOS and pico gapps)
3) Wipe data again and restore data from backup(I restored data from previous build of NitrogenOS, so I don't know if restoring from different rom will be ok)
4) Boot into rom, ignore any "stopped working" errors and go to Settings-System-Reset options-Erase all data(Not sure if this will erase internal storage, backup just in case)
After that phone booted up and and did first time installation.
Click to expand...
Click to collapse
Can someone upload me some backup? Pixel Experience would be a best ! Thanks a lot
Anyone have an idea what the problem might be?
I'm facing the same problem. I have a Redmi 3S (international, 3GB version). Doesn't matter what Oreo ROM I try (clean install), they all get stuck in bootloop on boot animation. It doesn't get far enough in the boot process to do a logcat with ADB, so I'm not able to post it.
I'm using TWRP 3.2.1-0 but have tried Red Wolf recovery as well and it yields the same results... I don't think it's a gapps issue since I've tried booting several ROMS without installing gapps.
I have rebooted several times while it's still in the boot process, remounted system in TWRP, wiped everything, ...
If anyone has an idea to get the logs, fire away. Can't boot so can't install liveboot or something like that.
bump
any solution?
The Problem still occurs...
Flashed PE successfully once, but since i went Back to official Nougat lineage os, No Oreo Roms can be booted with gapps
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Ebeninyo said:
Hi. Have you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Let us know about your phone's recovery, which magisk version you used, If you're using TWRP as your recovery let us know your TWRP recovery's version. Also did you dirty flashed your OTA or clean?
Click to expand...
Click to collapse
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
DrCow said:
Im not sure what instructions are you talking about but this isnt the first time i root my device.
Im using TWRP 3.2.1 since the last version giving me a little problems when trying to root. Im using the last magisk version.
About dirty or clean.. I first tried just flashing nornal from the OTA and then after it worked (no wifi or LTE) i tried to do factory reset and root again
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Edit: after flashing magisk reboot your phone once more. (i didn't knew it before. I booted into my os and checked magisk app to see if root was successfull but it didn't show me. I wiped everything down and flashed magisk again. Same thing happened. Rebooted my phone and saw root was on )
Ebeninyo said:
Try flashing this first https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
Download ota again and clean flash it from the recovery.
It might be because your TWRP isn't compatible to Pie. Most people here including me tried codework's TWRP and it solved any of our issues.
Click to expand...
Click to collapse
Will try it on the weekend.. I had some problems restoring my previous backup so i rather be home when i do it
Sent from my ONEPLUS A5000 using Tapatalk
Edit:
Wait the wifi and the LTE problem can be caused by the recovery?
DrCow said:
Hey,
So i wanted to update my android to pie and after updating i did the whole magisk method like i use to
But the thing is that after a restart both my wifi and LTE didnt work.. I kinda like the new android so i was wondering if theres a fix for that.
Click to expand...
Click to collapse
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
i ended up giving up..
im trying to do a clean flash
but the moment i flash the recovery and trying to go into the recovery
boom
black screen
i tried it multiple times both with codework 3.2.3 and blu_spark
Edit: Flash universal codework 3.2.1 does get me into recovery
im gonna restore my backup...for now
Z-Blade said:
I would suggest do a complete clean install (wiping everything but USB OTG) and making sure you got the latest TWRP from blu_spark or codeworkx. Also flash it following these instructions:
[Clean Flash] For Users with an Unlocked Bootloader and TWRP Recovery:
- Download the full ROM zip from the downloads section above
- Transfer the zip to the root of your device's internal storage
- Only needed if you are coming from Oreo or if you use an old TWRP recovery that's not the latest and Pie compatible: Remove the compatibility.zip from the downloaded full ROM zip with either MiXplorer or Total Commander (not with any other tool!) on your device itself
- Reboot to TWRP recovery (make sure you're using siankatabg's TWRP if you're on Oreo or codework's TWRP/blu_spark TWRP if you're on Pie) and take a nandroid backup of your existing ROM
- Flash Magisk Uninstaller (recommended)
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache, cache, system, vendor and data> Swipe to wipe
- From the TWRP menu, Install > Select full ROM zip (modified one with compatibility.zip removed, in case you're on Oreo or unmodified one, in case you're on Pie) > Swipe to flash
- Flash the latest stable Magisk in case you want to root
- From the TWRP menu, Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe
- Optional: If you wish to decrypt, format data via TWRP (please note that wiping the data partition, which we did in the 5th step above, is not the same as formatting it) and after that flash Disable DM-Verity and ForceEncrypt 2.0 (OP5-5T-Treble).zip from here
- Reboot
Full instructions and downloads from -> https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Click to expand...
Click to collapse
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
lorrdvader said:
For the "Clean" Install given that OnePlus5 doesn't have external microSD storage, will ALL data (photos, documents etc) on the phone be erased in Step 6 above?
Click to expand...
Click to collapse
No, it wont because all of that is stored in the Internal Storage. So as long as you don't check that, you will still have your data. However, I personally wipe everything including the internal storage when moving to a new rom. I prefer to start with a complete clean slate but it is optional.
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Dr4In said:
Hello guys, i updated my phone via Oxygen Updater like i always do, i have magisk installed so Oxygen Updater booting into TWRP and flashes the rom.
The thing is when it reboots into the system when screens goes to the lock screen to insert my password the phone shutting down and boots into TWRP. Via TWRP i flashed manually the rom and its boots normally after that but magisk is not installed of course, so when i boot into TWRP flash Magisk and reboot to system the phone shuts down again.
The OTA is 9.0.5 and the twrp-3.3.0-x_blu_spark
Is there a solution for that? I cant live without magisk
Click to expand...
Click to collapse
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
strongst said:
Which magisk version? Decrypted or encrypted storage? Did you flashed magisk uninstaller? Which magisk modules or other mods you're running? Did you tried another twrp or without the compatibility.zip of the rom file?
Click to expand...
Click to collapse
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Dr4In said:
When i boot into TWRP i always have to insert my fingerprint password to Decrypt my data if thats what you mean, i dont really get Encrypted or Decrypted.
Ok i found the problem, i had to use Magisk Uninstaller before flashing the new rom, after i uninstalled magisk i installed the rom and immediately magisk and it booted normally.
Click to expand...
Click to collapse
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
strongst said:
Your encrypted if you have to decrypt your data in twrp.
And your issue is remaining magisk/modules, that's why you should uninstall magisk before updating like described here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 :good:
Click to expand...
Click to collapse
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Dr4In said:
Can i format data to decrypt and flash the Disable DM-Verity and then restore my TWRP backup? Or its necessary to start the device from scratch for this to work?
Click to expand...
Click to collapse
If you mean your encrypted twrp of your internal storage = no.
I would start from scratch with decrypted.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I used this and solved the problem
I was facing to the same problem today, and the problem was the Magisk version! Same problem for Pixel 3/XL users...
The way you can fix it: Install v19.1 BETA (not the stable)! It should boot up!
So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery
Northgical said:
So I was going well, Install TWRP, Take a Nandroid backup, switch from SuperSU to Magisk
But then when I check SafetyNet and click yes on download propeitary code, It wouldn't work. It kept saying "SafetyNet API Error" over and over. I tried:
-Clearing Data and Cache
-Clearing Dalvik Cache.
-Reflash Magisk.
It wouldn't work, Any help?
SM-N900 5.0 Magisk Root with TWRP Recovery
Click to expand...
Click to collapse
If you have xposed installed, remove it. And try again.
Or just clean magisk manager app data, and open it with internet connection.
I never installed Xposed
I tried it. It didn't work