Related
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
EuEra said:
yup i had the same thing, used the brick recovery tool and was fine but when i re unlocked the bootloader i forgot it wipes internal data and lost all my pics music and titanium backups. Very annoyed to say the least.
Click to expand...
Click to collapse
That solved my issue, didn't realize that I really bricked my device. Sadly it wiped my data also!
Thanks for your advice!
I've experienced this about 3 times over the last 4 months, and had to restore a full backup each time. Basically afraid to do anything with Magisk at this point. This really needs to be fixed.
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
I did that when i switched from official to open beta, and everything went fine, then i installed a module, rebooted and got blackscreen again
Anova's Origin said:
It's probably because the Magisk updater is interfering with the kernel.
Every time Magisk is updated, I always dirty flash my current ROM and flash the new version of Magisk over it. I can then flash a custom kernel and everything still works flawlessly.
Click to expand...
Click to collapse
It's not the kernel, the black screen has occurred twice when just installing a module with no modifications to /boot.
dre-z said:
Hello,
I have a problem with my 3T. I updated magisk yesterday via magisk manager from 11.2 to 11.5. After the update my screen was completely black, the funny thing is if I press my power button long enough the reboot menu pops up. I can boot into recovery, the bootanimation is working but the ROM itself isn't visible.
I tried reflashing magisk via recovery, ROM+magisk via recovery, ROM via recovery and uninstalled magisk via recovery. Nothing works, the last thing I can try is a complete factory reset.
Does anyone has maybe an idea what else I can do?
I would appreciate any form of hint
Click to expand...
Click to collapse
Fix for me was to boot twrp, manually wipe system, data, caches etc (NOT internal storage box), then clean install the OS in twrp. Keeps your data and encryption then.
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Didgeridoohan said:
I've not experienced anything like this on my OP3T. I did see something similar on my Nexus 6 a couple of times, but could never quite get a grip on what caused it (I had a lot of other issues with that device ).
Is there any particular module that has been known to cause the issue (for testing)?
Click to expand...
Click to collapse
Nope, I've had this happen with multiple modules, including App Systemizer, ad-free YouTube, and OP3/T channel bonding enabler. Based on the file size changes in magisk.img, I legitimately think that the linked GitHub issue is the root cause. I think the only consistent repro is to flash different versions of modules while rebooting repeatedly.
Problem might be corrupted magisk.img during resize.
vemacs said:
Just happened again. Ugh. Anybody manage to recover their existing data partition from this?
---------- Post added at 01:21 PM ---------- Previous post was at 01:15 PM ----------
I think this is the fundamental issue: https://github.com/topjohnwu/Magisk/issues/185
Click to expand...
Click to collapse
I had the same issue when trying to install xposed 87.1 through MagiskManager (black screen and repeated vibration).
On my J5 I just removed the battery and booted into twrp, then I uninstalled magisk with the uninstall-zip, wiped dalvik an cache, rebooted once and everything works.
I reinstalled magisk in twrp and installed xposed 87.0 through the material xposed-installer and everything works.
No data loss.
The issue on GitHub was closed with a comment saying that it's likely fixed in latest Magisk (13.1). FWIW I haven't seen it occur after running 13 beta for a while.
My op3 was bricked again today after the update. Funny thing is, this time I had not installed any module. So the problem doesn't seem to be fixed.
pls someone should help me i tried to root my android v10 infinix note8i with magisk patch boot img file using adb fastboot when i tranfer the file and reboot the phone is not booting and not gettig into recovery mode, just blank screen when a turn on pls help me out with solution
same but my problem is kind of stupid because someone rooted my phone in another way and magisk says it is installed and needs updating but it is actually not and the biggest problem is when i unroot my phone the stupid rmm locks gets enabled and boom i can't open twrp recovery because it is not an offical binary so i got stuck there i flashed a stock rom got it fixed but i still can't do it
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone, and then it was stuck at the pulsating SAMSUNG logo.
So, next step would be obvious: get into TWRP and install Magisk 14.0.
And so I did, and so it failed. This time I got a bootloop. The "Galaxy S7 powered by Android" thing appears for a few seconds, and then vibrates and starts over. And over, and over, and over.
So then, I "installed" the Magisk Uninstaller. Thinking to get rid of all traces of Magisk that introduced this problem in the first place.
So I did, and now I'm back at the first problem: stuck at booting.
Then installing Magisk 14 AND wiping cache&dalvik: boot loop
Then I installed the uninstaller again, then Magisk 15, and wipe the cache&dalvik. And it's back at being stuck while booting again.
Brilliant. What do I do to fix this?
Are you using a custom ROM, or a port ROM, or a custom kernel?
It's all stock, except for it being rooted.
I'm having the same issue. Canadian S7 W8, Stock ROM with root, Magisk 14, upgraded to 15 using direct install through magisk manager.
Yes, exactly that. No offense, but that's helping neither yourself nor me nor anyone else. Have you been able to figure anything out?
Maybe how to produce some kind of log output?...
Same thing happened to me just now. Never would have thought that upgrading through the Magisk app would cause this. I've tried all of the above and have also tried installing v 12.0 but still no dice.
I even tried a factory reset and still no dice. This is seriously infuriating.
Guess I will have to reflash everything and start fresh. If anyone else has any other ideas I'm all ears.
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
thany2 said:
I've let the MagiskManager upgrade Magisk from 14.x to 1.50. Then I rebooted the phone
...
What do I do to fix this?
Click to expand...
Click to collapse
Mate 8 running 7.0 stock except rooted, running Magisk 14, did the same thing and I'm in the same boat. Have also tried removing magisk, reinstalling 14 no dice. Have not factory reset yet (trying everything else before that step) but it looks like it won't help.
thany2 said:
I'd like to know what the phone is actually *doing* when it's stuck. How can we get to know this?
`fastboot logcat` and `adb logcat` both keep waiting for a device that will not connect. Something does connect, christ knows what, but certainly no adb or fastboot device.
@fattyspecial
"reflash everything and start fresh" can you explain what exactly this comprises? What should I do?
Click to expand...
Click to collapse
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Ok, I'm still not in that loop... yet.
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
I'm still not in that loop... yet.
ct1aic said:
Ok, I'm still not in that loop... yet.
I selected installing the 15.0 Magisk zip file (from 14.0) using direct install, then did the reboot and I'm stuck at the pulsating SAMSUNG logo.
Can I do the same fix of fattyspecial without loosing anything on the S7?
I did the exact Magisk 15.0 zip update on my LG Nexus 5, with no problem, in less than a minute.
Click to expand...
Click to collapse
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
If you can' t solve download Magisk Uninstaller https://forum.xda-developers.com/attachment.php?attachmentid=4370032&d=1514240372
and Magisk 14.0 https://forum.xda-developers.com/attachment.php?attachmentid=4264532&d=1504713887
Then reboot in Twrp (hope you have it) and flash
1 uninstaller
2 14.0
I had the magisk 14.5 and I installed the 15 via twrp on top, and it updated normal. Is there a problem updating this way?
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Same here, updated from v14 to v15 and got a nice bootloop.
Huawei Mate 8 with Nougat (stock) and TWRP.
EDIT:
Solved!
Flashed my stock boot.img backup through TWRP, then booted my phone and downloaded v14, flashed v14 through TWRP, booted my phone again and downloaded v15 with Magisk Manager app and checked "Preserve AVB 2.0/dm-verity" and then tapped "Install" using "Direct Install (recommended)"
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Because a custom kernel disables dm-verity. There's an issue, mainly on Samsung devices, with the dm-verity detection in Magisk v15.0. It's under investigation...
Meanwhile, flash a dm-verity disabler together with Magisk v15.0 and you should be good to go.
I'm fairly certain you need a custom kernel. I'm also on the S7 and without one I've always boot looped, I think it has to do with dm-verity.
EDIT: I didn't notice there was a second page so I guess I didn't really say anything new, oh well, sorry!
ct1aic said:
Ok, I tried that soluction and it worked. I didn't loose anything and I have now Magisk 15.0 installed and still rooted/SafetyNet OK
Thanks, fattyspecial .
Happy New Year.
Rui
Click to expand...
Click to collapse
Awesome! Glad it worked. Happy new year.
---------- Post added at 04:22 AM ---------- Previous post was at 04:15 AM ----------
thany2 said:
@fattyspecial
I don't see why installing a custom kernel is a viable fix. Or a good idea. It seems random.
Maybe you can explain why this is a fix, and how the stock kernel makes the phone bootloop?
@Tribal123
I think you will find I've already tried it. I appreciate your contribution, but please do read my topic start.
Click to expand...
Click to collapse
Hey man. I'm just telling you what worked for me. If you don't want to try it then don't.
fattyspecial said:
Completely reflash the entire stock rom with ODIN and then re-root and reconfigure my entire phone. About the biggest bother imaginable.
I'm trying to re-flash only a new boot.img (or new kernel) through twrp right now. If I can get that to work I'll let you know right away.
---------- Post added at 03:10 AM ---------- Previous post was at 02:29 AM ----------
FIXED IT!
Ok here's what I did. Maybe not a perfect solution but I am out of bootloop and phone is working and root is working too.
I had to install a custom kernel. I'm guessing this replaces the corrupted boot.img file. So you will need to be rooted and have a custom recovery like TWRP.
Go to https://forum.xda-developers.com/galaxy-s7/development/kernel-tgpkernel-t3462897 and scroll down to the part that says: DOWNLOAD VIA ANDROIDFILEHOST for N version and download the zip file.
Transfer the TGPKernel zip to your external SD card (either with android file transfer if on mac like me or with an SD card reader).
Flash the zip in TWRP.
It will take a LONG time to reboot. Don't worry.
I chose to install root with Magisk and it ended up updating it to v15.0 and so far everything seems to be working well.
Hope this helps. That took a long time to figure out. Time for bed.
Click to expand...
Click to collapse
Hello,
Here is the problem I personnaly had (solved now !) :
Initially, my wife had a G930F (samsung galaxy S7) and a Custom 7.0 rom (i think it was the "AlexNDR.G930FXXU2DRAG" rom...but I'm not sure at all because it was installed several months ago or even years) with TWRP as recovery and Magisk as root.
I saw that Magisk not working (since when ? I don't know because it was not my phone). So, I tried to update it via the Magisk application (the initial goal was to use then Titanium Backup).
Logically, the phone then rebooted to install the Magisk update... except that a Boot Loop appeared.
I then tried many things :
1° Downgrade or Upgrade the TWRP recovery to 3.0.0.0; to 3.2.2.0 and to 3.5.2.9.0 (thes recovery .img files are here: https://eu.dl.twrp.me/herolte/)
=> It didn't work, and the bootloop continued (but, at the end, i keep the TWRP v.3.5.2.9.0)
2° I tried to uninstall and reinstall Magisk
(cf. the "Custom Recovery" tuto here : https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
=> Failure. Still the BootLoop... (either with the .zip v19.1 or the .zip v23)
nb: I even tried to donwload other magisk files but still the same bootloop (cf.https://forum.xda-developers.com/t/collection-of-magisk-modules-v2.3575758/page-13#post-72542167)
4° I tried to change the kernel by using TGPKernel (https://forum.xda-developers.com/t/...2-30-tgpkernel-v6-15-5-3-18-140-esd2.3462897/)
=> Failure, the bootloop remained...
5° Finally, I found a solution :
a° I downloaded the rom "G930FXXU2DRAG_DevBase_v4.6.zip" (via the following tutorial here : https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/)
, more exactly at the following location : https://androidfilehost.com/?fid=818070582850489124
b° Then, as indicated in the tuto (https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-jul-10.3592914/), I renamed the .zip downloaded on my PC to "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" (ps: so, i add "..._rescue.zip)
c° After that, I copied the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" on my micro SD.
d° In the recovery I finally installed the file "G930FXXU2DRAG_DevBase_v4.6_rescue.zip" and the phone restarted after a long time (or maybe 5 minutes, I didn't watch).
=> End of the bootloop and all data was preserved!!!
Scroll down over this post to see anwer!
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
gulp79 said:
have you tried to use Magisk 16.4,
if not, try to follow this guide:
https://www.theandroidsoul.com/xiaomi-mi-8-root/
Click to expand...
Click to collapse
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Padlite said:
Thank you for the fast reply!
I followed that guide and tried these steps:
fastboot boot mi8-twrp-3.2.2.img
Unencrypted via Pattern
Flashed Magisk v16.4 + DM verity disabler file
Reboot
But I'm still stuck at "powered by Android" bootlogo.
Normally it boots within 5 seconds but now it's taking forever. I'll wait a few minutes to see what happens.
I'm attaching some screenshots of the install process.
Click to expand...
Click to collapse
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
gulp79 said:
Ok,
but if you install Magisk 16.4, don't install also DM verity disabler.
DM verity disabler is needed if you don't want to root (see poin 14 in the linked guide).
Hope it works...
Click to expand...
Click to collapse
If I only flash Magisk 16.4, then phone shows "Powered by Android" and instantly reboots into stock recovery.
Only way to get it back booting, is performing fastboot flash boot boot.img from stock dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global image
I read somewhere about official and unofficial bootloader unlock. I didn't unlock the bootloader myself. Maybe it has something to do with it?
PS: Anyone had any luck using Magisk with MIUI 9.5.13?
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
punk84z said:
Did you try with a newer magisk version ? ... 16.7 was released 15 day ago
https://github.com/topjohnwu/Magisk/releases
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip
It´s a good practice to use magisk_uninstaller before flash new one if you had problems.
Direct link: https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-uninstaller-20180719.zip
Please tell us if it´s works
Click to expand...
Click to collapse
I just tried that. Uninstalling and re-installing v16.7. Although it seems now it's doing a few more steps, I'm still getting the recovery bootloop.
Install log screenshot attached.
gulp79 said:
Seems that also others users have this problem
https://forum.xda-developers.com/showpost.php?p=77234924&postcount=6312
Click to expand...
Click to collapse
Exactly that. Maybe we'll need to wait for a supported Magisk version. I'm still wondering what's the difference between our Mi8's that some can get Magisk working and some not. ?
I am running Magisk stable and tmiui 10 from Xiaomi. Eu without any problems.
I have a Mi 8 se and i install the eu rom boot the phone , reboot to twrp wipe and factory reset and installed magisk 16.4 .this is how works for me
i have the same problem too..when using china stable rom 16.7 magisk can be installed successfully tried many times...
flashing global version seems to have this issue...
tried all this steps too but no luck in global rom...
Padlite said:
Hey there! I just got my Xiaomi Mi8 from HK Goldway at Aliexpress. It came with its bootloader already unlocked and a Global ROM flashed.
I wanted to install Magisk but failed horribly . I've already done that to several phones (my last one was a Moto X Play, and it worked without major complications). But with this one, it seems I can't get past the bootlogo.
Stock Fastboot image used:
dipper_global_images_V9.5.13.0.OEAMIFA_20180714.0000.00_8.1_global
This is what I've tried so far:
First try
Flashed TWRP for Mi8 version 0711.
Flashed Magisk.
Got a bootloop.
Reflashed stock image via Fastboot.
Second try
Booted (not flashed) TWRP.
Tried to install latest global weekly from this thread.
Also got a bootloop.
Reflashed stock image via Fastboot.
Third try
I thought that those flashable ZIP firmwares were too small for them to be a full-fledged OS. So I went and downloaded this other one. Global version.
I read somewhere that I needed to format data before flashing a new image, so I did.
Booted TWRP.
Formated data (not Wipe)
Installed that ZIP from TWRP and booted correctly.
Booted TWRP again and flashed Magisk.
Got bootloop.
Back to stock image via fastboot.
Last try
Booted TWRP.
Formatted data.
Installed MIUI via TWRP.
Without rebooting, flashed Magisk and no-verity-opt-encrypt-6.0.zip.
This got past bootlogo ("Unlocked" message changed to "powered by Android") but got stuck there. Not booting at all.
Right now I'm back to the last try, booting MIUI successfully but without Magisk nor no-verity-opt-encrypt.
I kinda have no more ideas left. I understand this is a new device but I can't understand why people claim the have been able to install Magisk and I can't! Other thoughts were, maybe they were running MIUI 10 Beta and it only works with that version? I'm unsure about that.
Can someone lend me a hand? What am I missing?
Thank you!!
Click to expand...
Click to collapse
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
-fluffy- said:
i allso hade that problem
wen i got my phone it was with global rom
then i flashed twrp
didt like they said
wipe dalvik cache an cache an factory reset
flashed miui eu rom
then flashed twrp again rebooted into recovery
flashed magisk 16.4
ended up in staying on android logo
then i try format data an didt it all again
still android logo an nothing more
well then i didt what i allways didt on my other devices
i wiped dalvik cache
cache
data
system
then i flashed eu rom
an twrp again rebooted into recovery again
then flashed magisk 16.4
rebooted system an now it booted up
REMEMBER to manke a backup before flashing all off thise things otherwice u wont have the option to go back if something goes wrong
Click to expand...
Click to collapse
Well maybe the critical step is to wipe everything, including System.
Did you Format anything instead of Wipe this last try?
Also, could you please share a link from that working MIUI rom?
Thank you!
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
Is Google Assistant ("OK Google") working for you now as well?
I just flashed magisk v16.0 over the Miui 8.7.26 build and it booted without issues.
japancakes said:
Is Google Assistant ("OK Google") working for you now as well?
Click to expand...
Click to collapse
I just checked and no. If I go to Google Settings -> Voice, Voice Match is disabled because "This feature is currently unavailable for this language". Even though it's set to English UK. Maybe there is some Magisk Module to enable it?
Thanks, followed these steps and it got magisk going on the recent global release. Only difference was i had to use fastboot erase userdata.
Padlite said:
Scroll down over this post to see anwer!
EDIT: FIX!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7.
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata.
Rebooted.
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Hope this works out for everyone having this problem!
Click to expand...
Click to collapse
Hey guys im a toal newbie to this whole flash theme but Ive purchased a mi8 and i would like to use GooglePay and so on, could someone give me a step by step tutorial , how to install all this stuff on my device ?
Padlite said:
Sorry for double-posting, but I wanted to notify you I GOT IT!
Over here, user @richardyusan helped me out with an extra step.
What I did:
Installed Magisk V16.7
Installed DM-VERITY AND FORCED ENCRYPTION DISABLER.
Performed fastboot format userdata
Rebooted
And I got my phone booting with Magisk Installed!
Even though I couldn't install any module, (every install claimed I needed Magisk v15+). I read some threads and with a Magisk Direct re-install (from its app) I got Magisk downgraded to v16 and everything worked perfectly!
Here are some screenshots!
Click to expand...
Click to collapse
well i didt not flash dm-verity an mine pass saftynet
Hi all,
So went over to 9.1.0 (device and firmware / variant is at the foot of this question
I downloaded a ROM from halab in the hope to upgrade from 9.0.0.190 to some kind of EMUI 9.1
Used EMUI flasher, half worked then failed.
So on boot i went to bootloader and flashed TWRP to get ROOT back, now as soon as TWRP opened, it flashed the update_sd.zip and the actual ROM booted.
It didn't delete anything, it works perfect and I have no problem with the actual OS i now have, in fact it's actually rapid with good USEFUL features
MODEL: C432 L29 (Single sim, rebranded from 783 L09, no funky huawei crap)
FIRMWARE: 9.1.0.311 from 9.0.0.190 apparently it was a service ROM? No idea.
But it' on there now.
My question though? How can i root??
Flashing TWRP (any of them)
fastboot flash recovery_ramdisk NAME OF TWRP.ZIP
It will flash, but you cannot boot to TWRP
Patched a Magisk img, same method of flash in the same location recovery_ramdisk
Nothing, it will actually boot to eRecovery, so it's either protected or it's moved.
My bootloader remained unlocked, FRP was untouched.
Perhaps i should upgrade to 320.
Anyone know how to root?? Conventional means don't seem to work anymore.
Any help would be nice, thanks.
Not sure whether it'll work for You, but that's what some of us did:
1) flash patched ramdisk
2) reboot to erecovery
3)wipe data and cache - since stock recovery is gone you won't be able to accoomplish this step. The device reboots in rooted state instead.
"adb reboot recovery" seems to trigger root too.
However I must warn you. Root broke sms app for me.
BTW. What happened to your 1+7 Pro?
I was also considering getting it within couple of months.
forever_lol said:
Not sure whether it'll work for You, but that's what some of us did:
1) flash patched ramdisk
2) reboot to erecovery
3)wipe data and cache - since stock recovery is gone you won't be able to accoomplish this step. The device reboots in rooted state instead.
"adb reboot recovery" seems to trigger root too.
However I must warn you. Root broke sms app for me.
BTW. What happened to your 1+7 Pro?
I was also considering getting it within couple of months.
Click to expand...
Click to collapse
Getting it on the 6th. I've relocked the bootloader on this turd of a phone. I'm done with it.
What you said above worked fine on 9.0 but not 9.1.0 I tried everything, nothing worked..
Totally lost interest in it now. Cheers for the response all the same.
I went back to stock via otg method, as in other post, then factory reset from stock, then boot straight into bootloader after wipe and flashed a patched magisk. So now on 9.1, rooted and no issues with phone or messages apps.
Sent from my CLT-L29 using Tapatalk
So guys!! I am actually rooted, TWRP, Magisk fully installed, bootloader still unlocked and everything is all good! stoked.
I used things from around the P20 lite forums, messed about with some files and voila!
---------- Post added at 07:19 PM ---------- Previous post was at 06:58 PM ----------
I need to write this down before I forget.
FW - 9.1.0.311(C432E5R1P9)
EMUI 9.1
I used a patched magisk TWRP image for the P20 lite -https://drive.google.com/file/d/15NoARNVcbraCZiHLLpppq1kERvCKPSU2/view
Flashed it 3 times in a row via bootloader and powershell
Rebooted into TWRP recovery and then from there I rebooted back into bootloader and flashed a modded P20lite TWRP - https://drive.google.com/file/d/1-4kW_ly2fxTTLu9ZW6UgSQGwjkn2rFR2/view
Rebooted into system and noticed Magisk manager shortcut on homescreen, install it, create a patched image from within the app and save it to desktop
Reboot into bootloader and flash the patched image
Reboot and you should be fully MAGISKed up with root...get a rootchecker and then smile
https://imgur.com/gallery/GIfB0UA
EDIT - EDIT - EDIT
DO NOT USE ABOVE - Restarted the phone and it's lost root bummer. Will work on this.
-ANOTHER EDIT-
I can get temporary root and use ROOT only apps by following some guidelines and I seem to be able to get there everytime but with a couple of flashes after every reset. I'm trying to beat this encryption crap.
I just flashed https://gofile.io/?c=uFbiPK, noticed MAGISK shorcut, installed it, then DIRECT INSTALL magisk update, reboot, ROOTED!! but it's only temporary until a reset of the phone.
Xsjados said:
So guys!! I am actually rooted, TWRP, Magisk fully installed, bootloader still unlocked and everything is all good! stoked.
I used things from around the P20 lite forums, messed about with some files and voila!
---------- Post added at 07:19 PM ---------- Previous post was at 06:58 PM ----------
I need to write this down before I forget.
FW - 9.1.0.311(C432E5R1P9)
EMUI 9.1
I used a patched magisk TWRP image for the P20 lite -https://drive.google.com/file/d/15NoARNVcbraCZiHLLpppq1kERvCKPSU2/view
Flashed it 3 times in a row via bootloader and powershell
Rebooted into TWRP recovery and then from there I rebooted back into bootloader and flashed a modded P20lite TWRP - https://drive.google.com/file/d/1-4kW_ly2fxTTLu9ZW6UgSQGwjkn2rFR2/view
Rebooted into system and noticed Magisk manager shortcut on homescreen, install it, create a patched image from within the app and save it to desktop
Reboot into bootloader and flash the patched image
Reboot and you should be fully MAGISKed up with root...get a rootchecker and then smile
https://imgur.com/gallery/GIfB0UA
EDIT - EDIT - EDIT
DO NOT USE ABOVE - Restarted the phone and it's lost root bummer. Will work on this.
-ANOTHER EDIT-
I can get temporary root and use ROOT only apps by following some guidelines and I seem to be able to get there everytime but with a couple of flashes after every reset. I'm trying to beat this encryption crap.
I just flashed https://gofile.io/?c=uFbiPK, noticed MAGISK shorcut, installed it, then DIRECT INSTALL magisk update, reboot, ROOTED!! but it's only temporary until a reset of the phone.
Click to expand...
Click to collapse
What if you hold the volume up when you restart?
Xsjados said:
So guys!! I am actually rooted, TWRP, Magisk fully installed, bootloader still unlocked and everything is all good! stoked.
I used things from around the P20 lite forums, messed about with some files and voila!
---------- Post added at 07:19 PM ---------- Previous post was at 06:58 PM ----------
I need to write this down before I forget.
FW - 9.1.0.311(C432E5R1P9)
EMUI 9.1
I used a patched magisk TWRP image for the P20 lite -https://drive.google.com/file/d/15NoARNVcbraCZiHLLpppq1kERvCKPSU2/view
Flashed it 3 times in a row via bootloader and powershell
Rebooted into TWRP recovery and then from there I rebooted back into bootloader and flashed a modded P20lite TWRP - https://drive.google.com/file/d/1-4kW_ly2fxTTLu9ZW6UgSQGwjkn2rFR2/view
Rebooted into system and noticed Magisk manager shortcut on homescreen, install it, create a patched image from within the app and save it to desktop
Reboot into bootloader and flash the patched image
Reboot and you should be fully MAGISKed up with root...get a rootchecker and then smile
https://imgur.com/gallery/GIfB0UA
EDIT - EDIT - EDIT
DO NOT USE ABOVE - Restarted the phone and it's lost root bummer. Will work on this.
-ANOTHER EDIT-
I can get temporary root and use ROOT only apps by following some guidelines and I seem to be able to get there everytime but with a couple of flashes after every reset. I'm trying to beat this encryption crap.
I just flashed https://gofile.io/?c=uFbiPK, noticed MAGISK shorcut, installed it, then DIRECT INSTALL magisk update, reboot, ROOTED!! but it's only temporary until a reset of the phone.
Click to expand...
Click to collapse
Doesn't have to be so complicated. Download canary magisk manager. get yourself stock or twrp recovery_ramdisk. open magisk manager and patch the recovery image. copy patched image to computer then fastboot flash the patched image. done.
fyi to boot into recovery in 9.1 is the combo power button+volume up.
Cheers.
Sent from my CLT-L04 using Tapatalk
nikifeto said:
What if you hold the power up when you restart?
Click to expand...
Click to collapse
I'll try that tomorrow! Cheers
Dene_Bluesman said:
Doesn't have to be so complicated. Download canary magisk manager. get yourself stock or twrp recovery_ramdisk. open magisk manager and patch the recovery image. copy patched image to computer then fastboot flash the patched image. done.
fyi to boot into recovery in 9.1 is the combo power button+volume up.
Cheers.
Sent from my CLT-L04 using Tapatalk
Click to expand...
Click to collapse
Hey Dene, what version of TWRP did you install? I can't seem to get it to stick, just keeps booting to Erecovery instead of TWRP
6- https://otafsg1.h2os.com/patch/amaz...22_OTA_061_all_1911200429_a3efe64891d2c42.zip
6T- https://otafsg1.h2os.com/patch/amaz..._41_OTA_061_all_1911200419_f2e12518eef8ae.zip
Found this today. File has a date of 11/20/19. I put in root and do manual update thru settings/update.
Magisk patched boot.img for the above 6T ROM.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
I had a boatload of bugs with the OB1. I have a 6T converted. Couldnt answer or make calls, reboots, freezes, crashes, WIFI didnt work, no pic messages, etc. I just tested for a second and I could make calls and wifi works. Do not try to install the Magisk patched boot.img. It will give the problems I had with OB1. I tried.
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
g4seb said:
@shatty, thanks.
What did you do to upgrade ? Actually i'm in OB1 Android 10 and Root with patched boot. So you upgrade with OTA or local upgrade ? You loose Root, and you put the new patched in adb? IS it ok?
Thanks
Click to expand...
Click to collapse
If you're rooted use the same method as always, use local update ( you don't have access to incremental update anyway as you are rooted) and BEFORE rebooting go in Magisk manager and install Magisk again but on other slot. You don't need to play with adb or fastboot.
@Striatum_bdr :
Thanks, so download the update, do local update and after juste install magisk on the other slot.
shatty said:
Here's a bonus: Magisk patched boot.img for this OB2. Tested and verified root and no problems. Patched myself. For 6T. Extracted the boot.img from the payload.bin and patched.
https://drive.google.com/open?id=1DIoNvGG81IC6FdWiOgSRawG0-eAKUqBF
Click to expand...
Click to collapse
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
ariyan rana said:
wiped my device and flashed A10 beta 2, but every time flash this patched img file from fastboot my not booting. is there any other way to flash this patched img ?
Click to expand...
Click to collapse
It worked on my 6t converted from tmo. Anyone else try this patched boot.img? Why wipe? Upgrade works fine.
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
shatty said:
So after hours of using the ob2 I didn't have any freezes or reboots. 1000000x better than my experience on ob1
Click to expand...
Click to collapse
Same here bud. Thanks.
shatty said:
Def works a lot better. No freezes or reboots. My phone was useless on OB1 and I didn't want to flash back to 9 and lose my data. I had to forward my calls to another phone and wait for an updated ROM. But this def fixed a lot of the problems I encountered.
Edit: Still cant flashboot boot twrp.img.(3.3.1-1) Same error as before (failed remote unknown command)
Click to expand...
Click to collapse
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
[EDIT3]
I've fix it! I've talked with mauronofrio and he said that it's due to flashing the twrp in the boot partition, so he suggested me two ways:
1. Root your device and flash the twrp installer using magisk manager
2. After the command fastboot flash boot twrp.img reboot in recovery, flash the stock boot.img flash twrp installer.zip and finally flash magisk.
I choosen the second way and it worked! Now I've OB_2, twrp, magisk and wifi connection.
Thx a lot for the links and Infos.
I have flashed it and it feels definitely smoother and I hope the random reboots are fixed.
From the changelog they should be.
Here is a small how to, how the upgrade from 10 to 10 ob2 went smooth. Also using this on every update.
1. Just use normal systen ota & let it install or Flash full OOS 10 zip via local update . (DO NOT REBOOT)
2a. Flash newest TWRP: fajita twrp 3.3.1-28.zip (or newer) by @mauronofrio via Magisk Manager (DO NOT REBOOT)
or 2b. go into magisk manager, search for a module called "twrp a/b retention script" Install it (DO NOT REBOOT)
3. Flash magisk to 2nd slot via MAgisk Manager (Magisk Manager → Tap on Install → Then select Install to Inactive Slot)
4. Reboot, wait and enjoy
pOpY
Gesendet von meinem ONEPLUS A6013 mit Tapatalk
Be very careful with the patched boot image. It hard-bricked my OP6T! Full details here:
https://forum.xda-developers.com/oneplus-6t/help/spent-6-hours-trying-to-rooted-android-t4012909
It looks like they took FactoryMode away using *#808# when using the dialer... anyone noticed?
Did they fix the extra blank space under navigation keyboard when type? Thanks
nicche said:
For now the right command is fastboot flash boot twrp mauronofrio.img version and then flash the installer zip through recovery.
It's a Oneplus's problem.
[EDIT 1]
After a few tries it worked! Now I try to install twrp (mauronofio version) and root the phone.
P.s. I'm trying to update (come form OB-1) I removed all magisk's modules, flashed magiks unistaller but the update with update manager keep failing...any idea?
[EDIT2]
ok, now I'm rooted and I've twrp but wifi doesn't work it's turn off automatically!
Click to expand...
Click to collapse
same thing happened to me. Have you found the fix sir?
OK just reflash the rom and dont forget to flash twrp and magisk again
anddd boom i got wifi working again
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
I upgraded from OOS 10 Stable to OOS Beta 2 and all went on okay. No data lost.
Rickydwi said:
Anyone else having issues like the systems is getting slower animation is choppy and it just lag. I noticed it as well when playing games when that happens and it feels like i dont get as much framerates but a reboot of system fixed it for me. I thought by updating to ob2 it would fix this choppy feeling but its still there
Click to expand...
Click to collapse
I don't have this issue, but I do have the Bluetooth not working bug