[Issues] update magisk manager failed and fall into blackscreen - Magisk

HI all expert,
Need your guys advice,my side redmi note 8 pro (unlocked & rooted) fall into black screen after the magisk manager update failed when update using the magisk manager app itself.It happened after the terminal update using the recommend direct install failed,once after click reboot.
Now the phone seem like directly into black screen&i can heard the vibration phone continously after every few seconds,not able go into recovery mode or fastboot mode even i plug out the battery & put it on the phone again.Urgent helps need...

solved

May I suggest that you also post the solution, so that any future visitors to this thread might benefit from the information.

Related

Magisk GT King compatible

Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
PLAY911 said:
Hi all, has any GT King owner tried to root it with Magisk?
Many thx!
Click to expand...
Click to collapse
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
syked said:
Does not work and trying it will remove the current root on the device which will require re-flash of ROM to get it back.
Click to expand...
Click to collapse
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
[email protected] said:
Yes I learned this hard way . Flashed it and lost root . Hoping something can be done soon enough to get Magisk supported on this device . Currently I'm still on without root which is fine for some apps that will not run on root . Unfortunately one of the sports app that detects root which works now keeps bombarding my device with pop-ups ads . Really unusable .
Click to expand...
Click to collapse
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
syked said:
You could just force close the app in question and that way the ads won't appear in the background. Surely the ads won't appear when using the app and watching your sport.
Otherwise you can can flash the stock rom again (this will re-root) but will delete your data.
Alternatively, download blokada which is a ad blocking software. The catch is if you run an actual VPN, you won't be able to run this together as it's also treated as a VPN.
Click to expand...
Click to collapse
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
[email protected] said:
They do trust me . When you watch live or replay games 5-10 min you just get full screen plastered add that won't go away unless you close it yourself sometimes 2 times and game gets paused while that happens . Tried Blokada didn't work some apps won't even start while running even if white listed . Only one that does the job best is AdAway which requires root obviously but then sport app will not run since detects root and so on and on.....very annoying .
Click to expand...
Click to collapse
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
syked said:
Yeah I can imagine that's annoying. There is a way to install magisk but you have to use the recovery partition. Have a read through magisk instructions and how to load it into the recovery partition.
Ive tried it and and it works but you have to boot into recovery every time and will actually start the system but with magisk installed.
You could boot into recovery once and keep the device on.
You do lose the actual recovery partition though...but guessing you could fast boot via ADB to load that or maybe having the recovery on the SD card and depressing the reset pinhole underneath whilst plugging in power.
Btw, what streaming app are you using? I'm also a fellow Aussie.
Click to expand...
Click to collapse
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
[email protected] said:
G'day mate . Optus Sport . Will give that a try I guess . This is by far the best Android Box I ever owned getting Full Magisk working on it would make this amazing . I also own one of X96 Android Box which runs Android 8.0 . Got Magisk installed and managed to hide app . Unfortunately box just doesn't seem to like Magisk at all so I deleted it . Luckily app starts ok . But there 's heaps of issues with this one video lags, freezes sometimes not a daily device at all . That is the reason I got myself Gt-King in the first place .
Click to expand...
Click to collapse
G'day mate.
That's strange. I have never seen Optus sport display pop up ads. I've just watched over 15 mins of an UEFA Champions league game on my un rooted Android tablet using the Optus sport app and there were no ads.
Are you sure there's no other apps running in the background that could be generating the pop up ads but thinking it's Optus sport.
Agreed. It is an awesome box
For me it was just easier to Chromecast from my phone or tablet when using the Optus sport app because I couldn't be bothered continuously loading into recovery to have magisk hide work and I don't see the point to leave my box on just for that reason.
As it stands my box is default rooted and I'm using ALVATECHs rom which I find works great.
I'll post some steps later to help you and others loading magisk though.
Magisk in Recovery mode
Before anything always back up your box. If you use TWRP then create a whole back up which makes it easier to restore and if don't use TWRP then maybe you should.
To get Magisk working on the GT-King follow these steps.
Magisk will be installed into the recovery partition so if you flash the image to recovery, you will loose TWRP or default recovery but you could use an SD card to load into TWRP or default recovery and similarly you can use the patched recovery image from Magisk to and load that from SD card when required. I have not worked out how you can load Magisk recovery partition but also load TWRP when required. Technically this is possible because it's a patched recovery image with TWRP. There might be some sort of key sequence that will allow this but have not played enough with it to work it out. If you leave your box on all the time it should be fine because you can boot into "magisk recovery" once and then leave it on.
1) You need a recovery image.
a)If you have root already (such as default root), you can use this command in a terminal app which will covert the recovery file from the system to recovery.img and we will save it on the internal storage (home level).​
Code:
dd if=/dev/block/revovery of=/mnt/sdcard/recovery.img
b) if you don't have root because you tried flashing Magisk through TWRP or have manually unrooted then or if you can't be bothered using terminal, you can use my recovery.img here recovery image and save this to a location of your choice​2) Download and install Magisk Manager APK from here
3) In Magisk manager main screen click advanced options tick Recovery mode
4) Now next to Magisk Click install then selection the option where you have to select the image
5) Select the image file from either step 1a) or 1b)
6) Give it a few moments and Magisk manager will create a patched recovery img to the same location as the original recovery img
7) Now you need to unroot your device if it's not already by trying to flash Magisk in TWRP. I use impactor universal unroot for this which can be sourced from the play store or other means and follow the instructions in the app. After you restart, the device is no longer rooted but we will need use the magisk patched recovery which will give you root
Now here is where you decide what to do next....
i)Do you boot into existing TWRP recovery via depressing the reset pinhole whilst plugging in the power and then permanently flashing the new patched recovery image or
ii)Do you copy that patched recovery image to a SD Card, renaming it to recovery.img and booting off that temporarily via depressing the reset pinhole whilst plugging in the power
Either way, once you boot into that "magisk recovery" it is now installed and works a treat and have root access but you can hide root per app via Magisk hide
The systemless-host module can be installed via the module manager if you use Hosts file to block ads (I use energized host file for this). I think the path for this after it's installed is /data/adb/modules/hosts
Really appreciate effort and detailed info mate . Will try that later tonight and will let you know. Cheers
Sent from my SM-G950F using Tapatalk
I flashed the magisk_patched/stock-recovery.img with twrp.app and worked!
Many thanks to Syked for this detailed info how to get Magisk working.
Maybe somebody could confirm this is working on the new 2022 GT king ii with the Amlogic a311D2 CPU.
Magisk is a must for me so I'm not buying until this is possible.

Can't install magisk, after adding wrong module

Hi, I wanted to try the debloater module, so i installed it on my Oneplus 7 Pro. After the installisation and reboot, the device always stayed on the bootlocker warning screen really long. After that it always startet to fastboot.
My first try was to flash the module uninstaller: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242.
-> Flash was sucessfull, but it did not work at all.
Second try was to delete the modules via TWRP File explorer, so i deleted the folder of the module.
-> Still same problem, boots from bootloader unlocked warning screen directly to fastboot.
My next try was to flash the magisk uninstaller.
-> Flash sucessful, phone running again.
After that i reflashed magisk.
-> Problem started again.
Next step was flashing the uninstaller and then booting to android, to delete the magisk Manager. After that reflashing magisk.
->Same Problem as in the beginning. But there is no module when i have a look at /data/adb
Right now my device is running, but i have no idea how to reinstall magisk. Is there anybody who could help me?
I'd like to get magisk back and would prefer not to factory reset or wipe any sd data...
If there are no modules installed, there's likely something else going on...
Examples of things to do/try:
Don't install TWRP. Leave the boot image untouched and just boot TWRP to install Magisk (there's been instances where Magisk and TWRP conflict).
Reflash just the system images and leave data untouched.
Ask for advice in your device's forum. That's usually where you'll get the best device specific help.
Thank you for the advice!
So you mean i should flash the stock recovery again? And then sideload TWRP, or simply patch my boot image and flash it via ADB?
But why did i not have any problem with TWRP and magisk all the time before? Everything startet with the reboot after installing a new module?
I will also post my question in the OP 7 Pro forum!
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
GeekMcLeod said:
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
Click to expand...
Click to collapse
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
I just wanted to debloat the oneplus galerie, so i could install an older version from apk mirror, that still has the never settle stamp.
6nchris said:
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
Click to expand...
Click to collapse
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
GeekMcLeod said:
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
Click to expand...
Click to collapse
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
i came from 3T to the essential phone. I Think modding the OP 3T or the OP 7Pro is much easier than the essential PH1...
6nchris said:
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
Click to expand...
Click to collapse
Ahh, sad too say but I can't help with that. I don't take calls often so never noticed anything like that.

How to root the tablet A8 2019 T290

Hello guys, decide to mount this tutorial because I still see a lot of people with doubts, yes we already have how to root our device
I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
A tutorials too complex for some users, teaching you how to create your own Magisk modified Img boot, but I like simplicity, so if you don't want to break your head too much, here's a tip, use a successfully modified img boot , what you need is to install the rom stock that was used to create the modified boot first.
let's go to the tutorial, warning that the files posted here are not my own, and if it doesn't work, check if you're not commenting on any flaws, don't try to memorize the tutorial, follow it step by step. come on!:dedos cruzados:
1 - first follow these steps to unlock the bootloader:
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.
Now let's go to the next step, reinstall an outdated system, I did it on mine and it worked, do it at your own risk, neither I nor anyone else on the forum is responsible for any loss
2 - installing the stock ROM that we will use:
download this rom: https://samfrew.com/ru/download/Gal..._Wi-Fi-__/rue3/KOO/T290KSU3BUE1/T290KOO3BUE2/
OBS: a little detail about this firmware, it is made in arm32, which apparently makes it "lighter", but also has a more acidic use of RAM memory. This was the last software I installed on tab A, and I can say that the use has become better with it, but if you want to stay in the stock rom, even custom gsi didn't get such a good performance. It's worth testing, but be aware of the risks, I'm not responsible for errors.
Updating: use a modified version of Odin, to do the installations, be careful with downgrades, I managed, I was in the most current version of March, and I managed anyway using this modified Odin, but do it at your own risk, download the most current version here:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
And install via Odin, if you need more details just a Google, there are already millions of tutorials for that lol
when you get here you should already be aware that you have lost all your data, but it is necessary that the OEM option is enabled in the options, so in the CSC session use Home CSC, so that you leave the data saved, and do not lose the initial settings : )
once with successful installation, we will now install the file modified by magisk
3 - magisk Installation:
Intall TWRP: https://forum.xda-developers.com/t/...-2-for-2019-galaxy-tab-a-8-0-sm-t290.4185235/
just follow our friend's tutorial, with a little observation, after starting the process in odin, be sure to hold the volume up button + turn on, to be redirected to the TWRP.
follow the standard steps to install magisk, if it doesn't work, you will have to manually modify the system boot.img along with magisk maneger.
if case of problem:
The process of entering recovery on the SM-T290 using buttons is really finicky, unlike the 10.1" version. My best result has been with holding Power + Vol Up on startup, quickly switching to hit Power to dismiss the bootloader unlock warning page, and then immediately holding Power + Vol Up again for 6 seconds. (Holding longer will cause a hard reset.)
If you miss on the first attempt and haven't installed Multidisabler, it will revert your custom recovery to the stock OEM recovery.
I haven't had the tablet in my hands for a few months, so unfortunately I can't help more than that, as I said this was the last system I used, just because GSI are not very functional and are not always light, sometimes they crash more and it has more annoying bugs to fix that discourage daily use. my tip is, stay in stock Koo, excuses for those who can't, the most I can do now is guide them.
As a gift for you, I will teach you how to use Xposed :3
remembering, I did several tests that several times I faced bootlooops but in the end it worked for me, so notice, do it at your own risk.
5 - How to install end use EDexposed with Magisk
these versions were the ones that worked without problems in this rom
Install Riru - (Riru core) V21.0
Install Riru - Edxposed v 0.4.6.1(4510) YAHFA
Reboot, after reboot, install Edxposed Manager
and you can be happy
I thank you all for your help, and remembering that this was just a compilation of tips, to facilitate everyone, take due care to avoid problems, and don't forget to thank: 3 ?
Has anyone attempted this yet?
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
EngineeNerd said:
I am attempting to apply this root and I have run into a minor issue.
The AP Patched file from magisk isn't compressed correctly. Maybe I don't understand, but using 7zip, i can see that all the compressed files inside the AP file are LZ4's, but after patching with magisk, some become .IMG and odin errors our whenever I hit modem.Bin.
Any Ideas?
Click to expand...
Click to collapse
is the topic dead
EngineeNerd said:
is the topic dead
Click to expand...
Click to collapse
Hi friend, sorry but there are more current ways of routing, even already working on a TWRP, but now you can do the following, try using the same Firmware in the same version of the bootloader, otherwise there will always be an error, the file compressed this modified to work with Odin, I tested it myself on my T290, but I cannot guarantee its effectiveness if I try to use it in another version, I do not recommend doing this even.
I had trouble unlocking the bootloader until I did this:
After enabling OEM unlocking and turning the device off, plug in the USB cable. Hold both Vol + and Vol - at the same time, then unplug and replug the USB cable. The bootloader unlock screen should come up.
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
does this work if you're on a11?
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking o
Click to expand...
Click to collapse
themace51 said:
I posted this on twrp thread, but seems no one wants to answer , thought give it a try here?
Anyone know of a fix for the blank screen?
Not sure why they would lock down this tablet but not others?
Whats the point of unblocking the bootloader if you can not do custom roms , root etc?
My firmware is on T290XXU3BUC1
I can successfully installed twrp via Odin.
I reboot, instantly blank screen. I have rebooted into twrp with blank screen.
I was able to install the nexus rom, with adb twrp command line and works but all is blank screen.
I go back to stock and the display is back.
I have tried another twrp on this forum but that gives me security error.
I have also tried to patch ap tar with Magiskt but that flashes but when restart get security error.
Twrp is the only thing that works but complete blank screen with back light.
Tab is unlocked bootloader and oem unlocking on.
Click to expand...
Click to collapse
what are you specifically asking? the TWRP here is very functional, but custom roms are not very stable for this tablet, some GSI behave well, but it's still better to stock debloated
WillisD said:
isso funciona se você estiver em a11?
Click to expand...
Click to collapse
I do not think so
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
MythoAegis said:
Hi, maybe you can help me.
i rooted my SM-T290 MXO with Android 10 but the system always asked me about a new patch update (May 1 Update) and i dont know how to apply updates so i downladed the firmware update via ODIN, long story short after applying the firmware and updating trough Smart Switch (because now my tablet say that the SO has been modified and now i can´t update trought OTA) and now i have Android 11 with One 3.1 so my questions are:
Can install TWRP like before in his version of Android?
In case i need to downgrade to Android 9, do i need to be the exact carrier (XAR = United States) in the file you put or should i use my carrier (MXO = Mexico) and is the same result?
I hope anyone can help me because i dont know much about rooting and is the second time im dealing with rooting a Samsung Device (My first attempt was a Galaxy 4 and was frustrating that KNOX detected my bad root)
Thanks in Advance.
Click to expand...
Click to collapse
yes, you can go back to previous versions, but it gets harder when you upgrade bootloader version.
In order not to crash the downgrade, you need to look for the latest Android version you want, from your region you are in now.
An example:
I'm on the latest version ZTO - Brazil - Android 11
to get back to Android 10 I need to download the latest ZTO version with Android 9, of course you can try between different regions, but it will be a little more complicated.
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
themace51 said:
Hello
I was asking, how do i root this thing lol, it has been a nightmare
I can not root with custom magisk patched rom, as get boot error, and i can install Twrp, which works, but i just get a blank screen.
Was wondering if there was a work around?
Click to expand...
Click to collapse
You mentioned it's on Android 11, didn't you?!
well, I don't have Tab A with me anymore, but the suggestion I give you is to try to go back to Android 10, then install TWRP, and then try to install magisk, I can give you the last firmware I installed,
currently he is with my brother.
The firmware is Koreano, as I said, it is 32bits, and super functional.
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки - 4PDA
Samsung SM-T290/T295 Galaxy Tab A 8.0 (2019) - Прошивки
4pda.to
take a look here, search for the firmware I told you about, very good by the way
Hey
I am on T290XXU3BUC1 and i do not understand the language on the link you post
I tried your tutorial , but i am getting
sw rev check fail [aboot] Fused 3 > binary 3
hello, about that, but lately I don't have much time, but I'll update it today if I can, you probably got this error because this firmware is old.on 4pda there is a newer version with root, remembering that currently you can root through twrp, I'm going to port my last attempts here, but I notice that I don't have the tablet in my hands. use translation tools, the site is in Russian
I updated the guide as I could, any doubts I'm still here, but I can only guide, it's no longer possible to test.
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
themace51 said:
Thanks for the update. The only problem is, is that i have the newer tab and when I flash TWRP, i get a blank screen
I need a way to patch the firmware without failing, as i do not think anyone is trying to fix the blank screen bug with TWRP, unless they are on 4pad.to , but no idea due to the language barrier hehe.
Click to expand...
Click to collapse
have you tried to put the firmware I mentioned? this tutorial probably won't work on android 11 one ui 3.1, i say this because the TWRP is a bit old, so as long as it's on the updated firmware it's really hard to do anything.
if you don't want the specific KOO Firmware, you can get the latest firmware version for your region which is on android 10.

M21 Stuck at bootloader unlocked warning screen

Hi mate... need your help so badly,
my M21 is stuck at the bootloader unlocked screen. Can't do anything more than restarting the phone by pressing Vol down + power. Doesn't detect from PC. Can't get into download mode or anything else. this happened while I'm flashing the TWRP and trying to restart the phone into recovery mode. please help.....
Did you resolve this?
hey did you solved the issue ? and how please. I have managed to flash firmware using odin but still stuck at the bootloader warning. What should I do ?? anyone ?
indike114 said:
Hi mate... need your help so badly,
my M21 is stuck at the bootloader unlocked screen. Can't do anything more than restarting the phone by pressing Vol down + power. Doesn't detect from PC. Can't get into download mode or anything else. this happened while I'm flashing the TWRP and trying to restart the phone into recovery mode. please help.....
Click to expand...
Click to collapse
Hey I have the same issue. I have tried Odin to flash stock firmware also repartitioned the phone using Odin but did not solve the Issue . Please can anyone help us?
Also can you remember what you did before getting stuck cause I did nothing wrong . Opened the maps And gave the permission to use location after that calibrated the compass and phone hung on me from then it is on that warning screen
rajhridoy said:
Hey I have the same issue. I have tried Odin to flash stock firmware also repartitioned the phone using Odin but did not solve the Issue . Please can anyone help us?
Also can you remember what you did before getting stuck cause I did nothing wrong . Opened the maps And gave the permission to use location after that calibrated the compass and phone hung on me from then it is on that warning screen
Click to expand...
Click to collapse
Bro i have also same problem when I was flashing twrp through Odin .
My phone is stucking on twrp twrp is blinking again and again.also when I try to go to the download mode it automatically comes to bootloader and then to twrp please bro help if have fixed it
I was just speaking to a phone retailer and he told me how Shamshung M-series phones are getting locked by OEM manufaturer automatically within 6-7 months of usage (he was ready to show me evidence also so I believed him) , he said there is no solution to this So pls guys just an advice DO NOT CONNECT YOUR PHONE TO INTERNET FOR ANY OEM UPDATES,
1> TRY TO BUY PHONE FROM ONLINE STORE (BECAUSE RETAILER WILL FORCEFULLY UPDATE THE PHONE EVEN IF YOU TELL THEM NOT TO UPDATE)
2> FIRST, DONT PUT IN ANY SIM CARD IN SIM TRAY
3> SECOND, DISABLE WiFi (DONT SAVE ANY WiFi PASSWORDS) & TURN ON AIRPLANE MODE
4> THIRD, TURN ON DEVELOPER OPTIONS- USB DEBUGGING "ON" & DISABLE "KEEP MOBILE DATA ALWAYS ON" UNDER DEVLOPER OPTIONS
5> FOURTH, USE "DEBLOAT LIST" ATTACHED BELOW TO UNINSTALL INSTALLED APPS USING ADB
6> FIFTH, ONLY CONNECT TO WiFi FOR FEW SECONDS SO THAT THE OEM UNLOCK OPTION IN DEVELOPER OPTIONS GETS GREYED OUT.
7> SIXTH, FLASH ODIN-TWRP TAR FILE, WIPE/FORMAT DATA, BOOTLOGO PATCHER ZIP, MAGISK 24.3 ZIP, PRISH KERNEL (OR ANY KERNEL OF CHOICE), THEN FLASH TOTSUKA/PIXIE/CLEAN_OS/CrDroid10 (ONLY 3 STOCK-BASED ONEUI ANDRO 11 ROMS AVAILABLE, NO CUSTOM-BUILT NON-ONEUI ANDRO 11 ROMS AVAILABLE NOT EVEN M30S PORT ROM), VBMETA IMG
8> REBOOT TO TWRP, WIPE DATA
9> AFTER DEVICE BOOTS FIRST THING IS DISABLE WiFi & TURN ON AIRPLANE MODE, INSTALL NETGUARD FIREWALL APK THROUGH PACKAGE INStALLER (ALWAYS KEEP NETGUARD ON THROUGHOUT THE PHONE LIFETIME OTHERWISE SHAMSHUNG OTA MIGHT KILL THE DEVICE),
10> DEBLOAT BUILT-IN GAPPS USING ADB
11> INSTALL MICRO-G FROM TWRP
#NOTE: FOR FACTORY RESET SCENARIO REPEAT STEPS 10 & MAYBE 11 TOO.
AVOID VISITING OR USING OEM WEBSITES AND APPS. REMEMBER, FOR GUGLE EVERYONE IN THE WORLD IS A POTENTIAL TERRORIST.

Question Phone randomly reboot

so i've been experience miui randomly reboot ̶4̶ ̶̶t̶i̶m̶e̶s̶ 5 times on today. i always use my phone for daily like social media, music, reading etc, but i've do little modified system
19.12.2021 rooted phone V12.5.1.0.RKSIDXM using magisk 22.1
11.01.2022 install LSposed + Core Patch
what i experience is my phone randomly reboot, it show POCO logo and Unlocked logo. then phone turn off and reboot again, before it show poco logo there a vibration came from phone. i also tried to force into fastboot mode but it keep turn off in fastboot mode.
so how i can boot to homescreen ? ̶a̶f̶t̶e̶r̶ ̶p̶o̶c̶o̶ ̶l̶o̶g̶o̶,̶ ̶w̶h̶e̶n̶ ̶p̶h̶o̶n̶e̶ ̶t̶u̶r̶n̶ ̶o̶f̶f̶ ̶i̶ ̶h̶o̶l̶d̶ ̶p̶o̶w̶e̶r̶ ̶b̶u̶t̶t̶o̶n̶ ̶t̶i̶l̶l̶ ̶i̶t̶'̶s̶ ̶s̶h̶o̶w̶ ̶m̶i̶u̶i̶ ̶t̶e̶x̶t̶ ̶a̶n̶i̶m̶a̶t̶i̶o̶n̶,̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶i̶s̶ ̶f̶i̶n̶e̶.̶ it's not work, just hope it can boot to home screen
i wonder if everyone who used this phone have this kind experience, i might going to service center if this happend again
U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
wetito said:
U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
Click to expand...
Click to collapse
okay so everything was fine till i write this reply, there no random reboot anymore. in case if random reboot happend again, i will try your advice. anyway thanks
This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?
AnUrbanPenguin said:
This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?
Click to expand...
Click to collapse
vibrate sign on my phone simillar in condition where phone in off and turn on the phone will have vibrate sign before show poco boot up. when it happend i dont see any strange my notification beside download, social media, and games notification

Categories

Resources