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
Related
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!!!
Hello
I was on B180 (PRA-LX1C432) rooted with magisk
No updates available in settings/update firmware, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
Thanks !
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota, maybe I can use fastboot to flash only system and boot, and the reflash magisk to patch new boot img ?
anyone ?
Nobody updated after root ??
Ok, this is what I did and happened:
- In TWRP, flash magisk uninstaller script: ERROR 1. After reboot magisk was still here. That was a bad start...
- So I opened magisk app, click Uninstall and then Complete Uninstall. After that I made a reboot as asked, and device rebooted twice.
- Then, went to download mode and flashed stock recovery. And reboot.
- Then went to settings/updates/download latest full ota. It downloaded but refused to start the install process claiming to free up more than 900MB... Nothing on my internal sdcard so I had to uninstall some apps... cool !
- Then it reboot and installed the update
- First boot took a while, I still have "this device cannot be trusted" on start, and OEM unlock in settings is grayed and ON, so I think the bootloader is still unlocked
- Theme and wallpapers were reset with the update
For now I don't have flashed back twrp neither magisk .
In the meantime have you flashed TRWP and Migistik ? And again: do you have still to update your signature or something went wrong in installing fw B194.
Lastly: what do you mean by "went to download mode and flashed"...
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
First- I am NOT Responsible if you brick your Device! You do everything at your own Risk!
As I cannot find successfull thread here guiding to root this tablet I am posting the success with rooting with Magisk, all is seen on Russian forum 4pda,but the firmware I am on is not here ,it was little hard to find it(paid) but at the end it works, I have full root:
1 .You must have UNLOCKED BOOTLOADER!!! You can do it here are 2 threads guiding to it,mine was with DC_unlocker-4USD;
2. You must download Magisk from its original thread :Link
3.You must Look at which firmware you are,download the patched ones :С170B003
С170B253
C100B270
Or you can download you full Rom, extract it using Huawei Firmware Extractor extract the BOOT.img from UPDATE.APP file transfer it to your tablet and using Magisk--> install choose boot.img and patch it, then copy the patched_boot.img from folder "Downloads" in the internal memory back to PC,rename to boot.img.
4.You must have installed ADB and fastboot.
5.Using fastboot command on PC install the patched boot.img to tablet:
-First on your tablet enable Developer Options, thick Enable OEM Unlock,thick USB Debugging on,when connected to PC must ask for Fingerprint Security Rsa key,thick Always Trust to this PC"
-Second Tunoff Tablet, then hold volume Down button and connect to PC with USB Cable,Fastboot menu must appear: With green at bottom must be written that it is not FRP locked! If so -dont do proceed disable remove Huawei Account if you have one!
-Third-copy patched boot.img to folder where is located ADB and fastboot, then hold shift and right click mouse button and click Open Command Prompt here.
Now on fastboot menu enter following:
fastboot.exe flash boot boot.img
At the end everything must be OK!
Reboot with power button and check in Magisk !
Regards
I just wanted to confirm that this method works for my tablet. My Huawei Mediapad M3 10.1" BAH-L09 had bootloader unlocked. Emui5.1.2 and OS 7.0. Following these instructions, I extracted the BOOT.img from the stock ROM, then used Magisk Manager app (6.0.1) to create the patched-boot.img. Flashing this patched-boot.img using fastboot mode with command:
fastboot flash boot patched_boot.img
My tablet now is ROOTED without any problems (camera works normally). In short, just follow exactly these instructions and your tablet will be ROOTED
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Sorry but how did you unlock the bootloader?
DragonautMk said:
Sorry but how did you unlock the bootloader?
Click to expand...
Click to collapse
I used dc-unlocker (you can google for). Its easy but it costs ca. 4 €.
Does this method still works on latest ota ?
The4anoni said:
Does this method still works on latest ota ?
Click to expand...
Click to collapse
My M3 10 lite was on latest frmware C100B270 as i used dc-unlocker. Unlock worked well for me.
Does rooting enable you to install Google Services on the tablet? Is so, how?
Is there an international ROM that can be used (with Google tools)
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
---------- Post added at 08:40 PM ---------- Previous post was at 07:51 PM ----------
ossizwei said:
This works for me on BAH-L09 with Build Number BAH-L09C100B270. My Tab ist now rooted with Magisk 17.1 installed. Next i do flash special version of TWRP from the TWRP Builder site. I took the version for the BAH-W09 (WIFI version of the tab) on my own risk. I KNOW thats not the correct version, so please dont criticize.
Installation via fastboot worked. I can boot into Huawei recovery (Power+Vol-up) and TWRP (Power + Vol-Up and Vol-down same time). System boots without problem too. Also i can flash back the original huawei rcovery.img in fastboot mode.
But there is an issue in this TWRP recovery version 3.2.1-0. It does not decrypt data. I tried to format data and flash "no-verity-opt-encrypt". But there is still an Huawei secure mechanism, that wants me to format data in Huawei recovery again. Without format data my tab do not boot into system.
Next step i tried to get TWRP for my device on TWRP-builder app. but no succes because the build queue ist full. So i have to wait...
Click to expand...
Click to collapse
The same for me. Have you got the appropiatte twrp recovery?
wanlus said:
Thanks! Worked for my Mediapad M3 lite 10 (BAH-L09), but now... How can I update Magisk? The Magisk manager doesn't support the version installed.
Can't install twrp either
The same for me. Have you got the appropiatte twrp recovery?
Click to expand...
Click to collapse
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
ossizwei said:
This is an old post. Development has going forward. Look here:
For a LineageOS rom
https://forum.xda-developers.com/mediapad-m3/development/rom-t3945684
For TWRP
https://forum.xda-developers.com/mediapad-m3/development/twrp-t3914531
For the first step use the 3.2.0 version of TWRP if you are in Huawei's stock Rom.
For me its the best for this moment. Only issue is, that camera dont work in this early lineage rom. But developer is working on it.
Click to expand...
Click to collapse
Ok, thank you so much. I've got installed Twrp properly, and it boots ok... but no more. Now it stays on the recovery home screen. I'll try again
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?