Installing magisk creates bootloop - Nokia 6.1 (2018) Questions & Answers

Hi,
I have an unlocked 6,1, that currently has lineage 18 ( official ) flashed.
I am trying to install magisk with no luck.
If I adb into bootloader, i can then ''fastboot flash boot twrp.img''
If i then reboot , I get twrp.
If I then flash Magisk zip ( latest ), and reboot, it doesn't boot back into lineage.
Sometimes I get a bootloop ( lineage animation ), and sometimes it just sticks on android one.
I have to keep pressing volume and power buttons until eventually, I get back to download mode.
From there, I can either try to factory reset, or worst still, reflash lineage.
Any ideas what I am doing wrong?
As an aside, in case it is relevant ,one thing I have noticed is, after powering off, when I plug power in, I dont get a battery charging sign - never have with lineage - instead I get a blank screen. I also can't get to stock recovery from the battery charging screen using VOL up/POWER.
Srangely, if I flash stock using OST ( offline), I get the battery charging screen ?
Many thanks in advance
Pootler

Related

[Q] T310 Stuck in boot-loop

I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
curiousmike said:
I had installed 'blackhawks next kernel' for dual-booting.
I had CM11 on partition 1 and Stock Samsung on Partition 2.
I decided I want to simply revert to a single partition with the stock Samsung.
I booted into partition 1.
I used Phils to install 'GT3_MH2_STOCK_Kernel_SM-t310_Tab3.zip'
When the machine rebooted, it jumped into the Cyanogen Mod boot sequence, and just loops.
If I try to turn the machine off to boot into recovery, the Tab doesn't shut down - it just reboots.
Trying to 'time' getting into recovery hasn't netted me much luck with about 20 tries of nailing the 10-second 'hold power button then nail volume up.'
Any suggestions?
Click to expand...
Click to collapse
Do a clean install of stock ROM by going into download mode. Power + Volume down + Home button.
curiousmike said:
Well, I got further.
I found that if I plugged the USB cable into the device into my computer, then pressed and held the power, when it would 'auto-reboot' to the battery icon screen.
Once at the battery icon screen, I unplugged the USB cable and the tablet completely turned off.
From there, I was able to get back to Philz.
So, I guess my new question is: How do I correctly install any kernel other than blackhawks, which would allow me to flash back to a stock ROM?
Click to expand...
Click to collapse
The kernel you installed will only work with stock roms. You still had CM installed as primary rom and attempted to use a stock kernel with it. That's why it wouldn't boot.
You have a couple options now for reverting to stock.
1. Odin - Download and flash a full stock firmware; then boot into recovery and do a factory reset. There are many guides for doing this with Odin. Firmware is available at sammobile.com.
2. Recovery - Download a stock-based rom and flash it in recovery. Make sure you do a full wipe in recovery before flashing. The rom will have a kernel also, so there is no need to flash another one.

MM 6.0.1 Xposed Update!

So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
IAmTechFreq said:
So, i recently have tried flashing Xposed on the MM 6.0.1 on G920P a.k.a Sprint S6
( ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar )
I have root and recovery, but Xposed doesnt seem to comply with me.
from multiple sources or builds.
And each Xposed file that i've tried so far that i've been flashing over and over again, rinse and repeat.
( Flash Stock through Odin, Go through setup process on the phone, Reboot Back to Download mode to Flash TWRP, Reboot, Back to TWRP to Flash Xposed, Once flashed i Restart it again, back to the s6 screen to becoming a black screen bootloop, thus having me restart the whole flashing process again )
from android file host website. And Default xda unofficialy build on this website.
xposed-v79-sdk23-arm64-by-romracer-20151218
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - ABDYASAR 7.8MB
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 - SANOC 7.8mb
xposed-v80.0-sdk23-arm64-custom-build-by-wanam-20160211 -WANAM 7.8MB
xposed-v80-sdk23-arm64-by-romracer-20160202
It would go from the Galaxy S6 Boot Menu startup to black screen and bootloop back to the original BootMenu or screen.
NO LED cycles nothing, but i can access Download Mode and Recovery But Updating Nor Uninstalling doesn't do anything to the rom, it just keeps boot looping unless i Flash the Stock back into place.
I'd like to have Xposed working i havent found a version for me that would work for this but i would really appreciate if everyone could help out.
Click to expand...
Click to collapse
Did it work. Ive only noticed a tad bit longer boot up the 1st time but all good.
i've tried most of them and i tried v80.0 or v80 and i got one part success half i didnt which was from it i got to the LTE spectrum screen and it just would go past that before it would just be the led flashing and bglank screen, i waited about and hour and still nothin changed from that screen.
Nevermind i made an update
This is what i've managed so far.... what am i missing here?
So here's what i"d take place in order to attempt a flash of Xposed Framework.
I start with Pre- Downloading the files for the MM 6.0.1 Stock Rom, it's in the forums Somewhere.
TWRP ( New_S6_Spr_TWRP_MM_Bootloader2 ) a.k.a 3.0.1
(This is a special version only for the Sprint SM-G920P and is meant to be flashed with Odin)
SuperSU 2.68 a.k.a ( BETA-SuperSU-v2.68-20160228150503 )
and obviously, Odin ( Odin3 v3.10 )
The steps that are taken place.
1st. I'd Boot my device into download/odin mode.
or
( while the device is powered off, i press and hold the home+power+volume down buttons.
and from there I'd be taken to a light blueish screen saying "Warning", and i follow through by pressing volume up)
2nd.
Once the device is in download/odin mode, and ready to go, i'd take my phone, plug it into my windows PC and open Odinv3 and from there
i'd select in odin, or i'd click the "AP" button and select the, tar file.
After that has been flashed thoroughly, I'd then proceed with the follow on screens, the 1st reboot and it updates or it says
Optimizing app 1 to 30.... the 2nd reboot where the hand free activation commences and
from that 3rd time it reboots and boots up again, i'd follow up with my login information.
3rd. once my device has been fully booted from the 2nd part, i'd then shut it down or restart it into "download mode again" and connect it to my pc again
and from there i'd load odin, and search or i'd find where I downloaded the special "TWRP .tar" or recovery file
and select the "Ap" option again and press start Afterwards.
After it flashes, right when its done i automatically hold the home+power+volume up buttons,
turn the device off and hold home+power+volume up and your should get some red text in the upper left hand corner with recovery not enforcing, that's okay dont be worried,
and from there it should boot into and be brought into TWRP...finally lol.
Now that's where you can flash SuperSU
4th. I'd leave my phone connected to my pc until, it's fully booting into twrp or i'd just connect it once im in the recovery.
I let my pc detect my phone and i'd copy both of these files.
SuperSU 2.68
and
Xposed
4th. After its copied, i'd go back into my phone, i tap install, and i select supersu and let it run, afterwards, i press reboot.
And let it sit for about another 2 minutes to do its own thing. Afterwards. once the phone is fully booted up.
I'd then go back into recovery, and flash Xposed and i'd wait about another 2-3 minutes for it to cycle
from the LTE Spectrum Screen to the, torquise colored screen where it's finally optimizing apps from 0 to 331.
5th. Once done, i'd finally have my advantage to install what i'd like which i'm doing as of right now still testing it out.
P.S if you do what i do for the SnapPrefs Module then i'd take in high note that before you flash the Xposed to download latest Snapchat 9.26
log in, once logged in then proceed with the rest and download XInstaller to downgrade from 9.26 to 9.17.1.0 to take full advantage of Snapprefs coolness.
upon note so far, after installing the modules, i rebooted my phone and it boots until it hits the LTE Spectrum screen and it has a light blueish pusling cycle and im stuck here.
maybe i can try another version. to be continued...
If you need any help feel free, i will try as best as i can, as i am a n00b but i have plenty of free time and have some decent knowledge about this.
After , i went back into recovery, i went to uninstall xposed thru the other flash file and its says optimizing 0 to 36 items and it booted so far, mayber after i flash the cache again and reinstall i should be fine but until further notice...tbc
Alright after a good amount of time i;ve finally concluded that the versions i;ve tired from xposed were the ones from the OFFICIAL thread and id always bootloop with that puling blue led and black screen, BUT with Wanams Xposed Version 80, and 79 they worked EXCEPT i can only get to the LTE SPecturm white boot screen and it does nothing from there BUT when i flash 80.1 it completely pulls through with the boot and completes but i had forgotten to mention that for some people on aanother thread that Xinstaller may leave you with bootloops and as it did for me thats exactly what happened. But i m still confused as to why the officials dont work by wanams does even after wiping cache,and dalvik cache multiple times and uninstall and reinstalling xposed.
Does yours still bootloop or did it finally pull through?

Can't enter Recovery mode. System boots. Automatically enters download mode

LG G3 D855
aoscp 5.1 Funnelcake
3GB/32GB
Android 8.1
No Root
No Custom Kernel
I had TWRP installed for about 2 years
But now when I try to enter it then it says "Boot Verification Failed" and then Blue and Red light flashes constantly until I pull out the battery. I even flashed MR_Bump on every ROM Flash.
Fact is,
The system boots up fine.
In rare cases the system boots up till the Launcher's home screen and then automatically reboots into download mode, but it can be easily fixed by a battery pullout.
My real problem is how to install TWRP once again because I want to install a new ROM because this one's malfunctioning.
Any help would be appreciated

SM-T320 seems to be bricked. Doesn't boot up to OS, only goes to ODIN mode. How to start from scratch?

It's been a while since I've touched the tablet, and I'm hoping to bring it back to life. I can see that it's trying to boot up LineageOS, but the logo never stops loading. I can boot into odin mode, using vol down+ power, but that's about as far as I can go. How can I start over from scratch and get my tablet working again?
@AliMusa no TWRP recovery (Home, Vol-up, pwr)?
That would make it much easier.
Starting from scratch means flashing stock ROM with Odin.
bmwdroid said:
@AliMusa no TWRP recovery (Home, Vol-up, pwr)?
That would make it much easier.
Starting from scratch means flashing stock ROM with Odin.
Click to expand...
Click to collapse
I managed to get TWRP installed, but still can't get LineageOS to install and boot up. It just keeps showing the boot logo and then eventually goes back to recovery mode.
AliMusa said:
I managed to get TWRP installed, but still can't get LineageOS to install and boot up. It just keeps showing the boot logo and then eventually goes back to recovery mode.
Click to expand...
Click to collapse
Wiped everything (not SD) plus "Format Data" ?
Same without Gapps, Magisk aso?
Tell us more what you're doing.
@AliMusa I was able to bring mine back by using a wall to micro-usb charger no USB plugs, I specifically used an old Nokia charger it's output was something small, I believe 700mah but it was the only charger that would get the device to boot to anything besides download.

Unlocked bootloader - boot loop after trying to put stock firmware back on

My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.

Categories

Resources