Related
Hi there
Two issues/problems here:
I rebranded my Oreo European MHA-L09 successfully to MHA-L29, everything went perfectly. Then I proceeded to flash RR. SafetyNet however is not helping : CTS mismatch doesn't seem to wanna go away. I tried everything I could find, Magisk does nothing, unrooting : same, can't relock bootloader (root is risk)... kindabummed as it even blocks Spotify from showing up in Play Store. After a week of proding, I'v given up.
So I go back to stock, and whaddayaknow, everything goes fine except... bootloader won't relock : root is risk. I tried reflashing using HWOTA, like, a billion times, couldn't get HiSuite to help either, can't really figure out how to use download mode - most tutorials I found were for P10 - sooooo... yeah.
Any ideas when it come to relocking bootloader (in a stock rom or nah) and passing SafetyNet when a GSI is flashed?
SomeRandomEngi said:
Hi there
Two issues/problems here:
I rebranded my Oreo European MHA-L09 successfully to MHA-L29, everything went perfectly. Then I proceeded to flash RR. SafetyNet however is not helping : CTS mismatch doesn't seem to wanna go away. I tried everything I could find, Magisk does nothing, unrooting : same, can't relock bootloader (root is risk)... kindabummed as it even blocks Spotify from showing up in Play Store. After a week of proding, I'v given up.
So I go back to stock, and whaddayaknow, everything goes fine except... bootloader won't relock : root is risk. I tried reflashing using HWOTA, like, a billion times, couldn't get HiSuite to help either, can't really figure out how to use download mode - most tutorials I found were for P10 - sooooo... yeah.
Any ideas when it come to relocking bootloader (in a stock rom or nah) and passing SafetyNet when a GSI is flashed?
Click to expand...
Click to collapse
So, bootloader relock won't happen if any of the stock images don't match exactly to what the system expects. (If it does, you brick.)
On any ROM, provided it passes the basicIntegrity check, Magisk, possibly with the universal props fix module, will get SN passing. (If it doesn't pass basicIntegrity in the first place, that's another thing, and Magisk can't fix that.)
irony_delerium said:
So, bootloader relock won't happen if any of the stock images don't match exactly to what the system expects. (If it does, you brick.)
On any ROM, provided it passes the basicIntegrity check, Magisk, possibly with the universal props fix module, will get SN passing. (If it doesn't pass basicIntegrity in the first place, that's another thing, and Magisk can't fix that.)
Click to expand...
Click to collapse
Thank you so much for your answer! I already tried installing huawei props fix but it doesn't want to flash - /data/magisk is not configure proprerly even after multiple reinstalls apparently - and when it comes to MagiskHide Props Config, I can't seem to find a fingerprint for the Mate 9. Would using the Mate 10's cause issues?
SomeRandomEngi said:
Thank you so much for your answer! I already tried installing huawei props fix but it doesn't want to flash - /data/magisk is not configure proprerly even after multiple reinstalls apparently - and when it comes to MagiskHide Props Config, I can't seem to find a fingerprint for the Mate 9. Would using the Mate 10's cause issues?
Click to expand...
Click to collapse
Near as I've been able to tell, the fingerprint only makes a difference to things like SafetyNet. You can add the fingerprint for the Mate 9 if you want, obviously, but you could just as easily use one swiped from anywhere else and it would work just the same.
How are you attempting to install Magisk? I've only ever done it, personally, through Magisk Manager, using "Patch boot image" or "Direct install". With the bugs that recently appeared (Magisk Manager 5.8, Magisk 16.6, saw lots of softbricks due to direct install or install via TWRP - it was unconditionally patching something it shouldn't have), I've been telling people to use Patch Boot Image in Magisk Manager always.
irony_delerium said:
Near as I've been able to tell, the fingerprint only makes a difference to things like SafetyNet. You can add the fingerprint for the Mate 9 if you want, obviously, but you could just as easily use one swiped from anywhere else and it would work just the same.
How are you attempting to install Magisk? I've only ever done it, personally, through Magisk Manager, using "Patch boot image" or "Direct install". With the bugs that recently appeared (Magisk Manager 5.8, Magisk 16.6, saw lots of softbricks due to direct install or install via TWRP - it was unconditionally patching something it shouldn't have), I've been telling people to use Patch Boot Image in Magisk Manager always.
Click to expand...
Click to collapse
Okay, thanks! Yeah, I installed it from TWRP. Gonna redo the install then.
Also, I just noticed that Bluetooth does not work - it doesn't even activate for some reason - so I'll probably restart from ,yet another, clean flash. Thank you so much for your help!
So I am running beta 3 of Ressurection Remix from OpenKirin website. Everything is smooth even after heavy tweaks. But I want to root this ROM. Reason is I want to uninstall built-in apps and some of my apps require root access. I already tried rooting the ramdisk.img. it failed. Even though it was rooted root access wasn't available. So can I directly flash latest magisk via elemental ROM TWRP? Or is there any other method?
Like you, I'm on the same build from yesterday, and obviously the minimum that I'd like to do is to root the ROM, since that we already miss a fully working TWRP and a compatible Xposed framework.
I discovered just yesterday topjohnwu's thread about patching the stock boot.img with the custom Magisk Manager apk for Huawei devices, but before doing everything I've decided to make a search on XDA, and I've stumbled upon this. So neither patching the stock ramdisk.img works?? Dammit. Becsuse standing by what i know, flashing latest Magisk on an A only GSI works, but i haven't read successful cases rooting an OpenKirin ROM yet.
I'd like to test this method, but i still have to setup some stuff on this ROM, and so i don't want to try something that could mess up system, trashing all the time that I've spent on configuring the device.
I'll update ya as soon as i can, if something useful should come out. I hope to update you soon!
Dude. I have done it and would like to tell you that it can be flashed normally. Currently enjoying root with all modules working. If you have an honor 6x just flash TWRP from elemental room thread and then latest magisk. So far no issues, no bootloop. However after first installation I recommend you to install via direct patch once again to ensure everything works. i.eif you still wanna know. This is way simpler
Thanks for letting me know mate, yeah i have a 6X. Actually I've installed TWRP and flashed latest stable Magisk, V17.1. Magisk is correctly detected by Magisk Manager.
Now, the file that i should provide to patch on Magisk Manager is stock EMUI 8.0 boot.img, correct?
Nope. If you have magisk installed just direct install once again via magisk manager and you're good to go
Thanks Mannan, I'm enjoying root goodies too now.
I take the chance to ask ya if sound mods like Viper/Dolby Atmos will also work or not as a Magisk module, since that time ago (but even recently) i saw some users that was saying in a couple of threads that flashing one of these would corrupt system files, and so EMUI 8 had to be flashed again.
First of all we aren't on EMUI 8bso no corruption. We are on Android 8.1 so any Sound Mod for this Firmware should work. Now I haven't flashed it yet cause mainly I have to find a working one and of the risk of soft brick. But I will try and let you know if I find a working one. Same goes for exposed framework
Got it. Well it would be great, especially Xposed in systemless version.
EDIT - going off topic a while, even you notice a charging time much slower than on stock? Before, i usually charged something like 60-65% in one hour, now it tooks at least 1 hour and an half to achieve the same percentage of battery. Gotta tweak this someway.
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Mannan Qamar said:
Tried installing Viper4android. Gives IO error while mounting driver. Xposed I havent tried
Click to expand...
Click to collapse
Thanks for the feedback. Sadly i think that Xposed won't work too.
I'm still on 47.1.A.5.51 and was having some issues with my phone frequently restarting itself and I tried updating Magisk from 14.3 to 18.0 and TWRP from 3.1.1.0 to 3.2.X.X (can't remember offhand). It seems to have stopped the rebooting issue but now DRM fix doesn't seem to work anymore. I am using the kernel and fix provided by shoey63.
I did consider updating to Pie but it seems that there's still a bunch of bugs and stuff. Also couldn't find a proper step by step guide of what the flash order is for it to not lose userdata.
Help would be much appreciated. I just need to hold on to this device for another couple of months before XZ4.
EDIT: It's Magisk that is causing the problem, updating it makes the rebooting issue disappear. Can't update because the free version of DRM fix isn't updated for the newer versions of Magisk.
EDIT2: To heck with it, I installed the DRM and kernel from Janjan's thread even though my firmware is an older version and everything seems to work. It's on Magisk 17.1 and not the latest 18.0 but as long as it doesn't reboot it's mission accomplished for now. Bonus points because now it passes SafetyNet too.
I have a question. I want to root my phone (upgraded from oreo to pie, stock), but i'm not sure what should i do. Should i use oreo rooting instructions? I can't find any tutorial for rooting on pie. I don't want to change my rom, i just want to have a root and be able do use the magick and modules that's all. It would be nice to have step by step instruction.
I know i have to unlock my bootloader first at htcdev, then install twrp (not sure which twrp and if the installation is same as on oreo?)
In the past i rooted one phone but it was completely different and i almost bricked my device, because some idiot posted wrong link on the forum... There is so many versions of everything and i'm feeling lost in it.
I hope this helps, but Pie is still very new for the HTC U11. Some even are saying that clean flashes of the Pie RUU have flash, camera, and wifi issues. I am currently running the amazing RR-P rom (which is based on pie), but it runs on the latest Oreo RUU. I have no issues with the ROM and I get insane SoT even without battery savings. I am excited for the future of this phone, since I love the hardware navbar (never liked the on-screen one / though my HTC m8 is still a boss, and even the forums there have a very solid Lineage 17.0 (android 10) working on it).
https://dl.twrp.me/ocn/
Above is the official link to the US HTC u11 TWRP recoveries. I don't think (to be safer than sorry) these are 100% compatible over the PIE firmware though.
I checked HTCdev, and it doesn't seem to have any difference in the instructions in unlocking the bootloader. No mention of Nougat or Oreo, so I would assume there's no difference in doing the same with Pie.
I flashed my U11 after Pie update, working fine, no problems with flash, wifi or anything else (CID: HTC__034)
1. Unlock bootloader via htcdev
2. Flash latest TWRP from the official site. Instructions here for example: https://www.xda-developers.com/how-to-install-twrp/
3. Flash Magisk (also from official Magisk site)… that was a little trickier, since TWRP can't mount the encrypted partitions. The workaround is to copy the Magisk ZIP onto an SD Card and flash it from there while in TWRP.
4. Enjoy.
I decided to root this U11 for the first time, since I don't expect any futur software updates coming form HTC.
Thank you for all your help, i'll try this out today. :good:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Togzyk said:
So i did everything and it's working but i have one problem. After installing magisk i tried to install some modules, and one of them caused bootloop and i was unable to delete it, and also i was unable to install module uninstaller (fail). So i had to do factory reset - any solution to avoid this kind of problems in future?
Also i installed xposed successfully, but none of modules was working..
Click to expand...
Click to collapse
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
hammered58 said:
I have no answers, but as u can see a rooted pie is problematic, hence the many people reverting back to oreo and or nougat, but some people somehow make it work. Not me I could not downgrade quick enough after rooting, unrooted pie worked great, but my many 'need for root apps' did not , so back to oreo for me . Just my 2 cents!! Good luck.
Click to expand...
Click to collapse
I found many working apps. The biggest problem is "substratum", especially when it comes to changing navbar buttons. But gravitybox is working, and I'm happy with it. Thanks for your help
My rooted Pie works fine, but I didn't install Substratum or Xposed.
I'm running, 11.8.0.13 on my 8T (incl. magisk) and trying to update.
The phone claims to detect root and dowwnloads the full image.
When I try to install the OTA file "OnePlus8TOxygen_15.E.26_OTA_0260_all_2106020020_e8382.zip" it simply fails (at 0%, so before even starting to unpack).
I've tried the oneplus installer and twrp.
TWRP 3.5.2._11-0 simply shows Error 7 and install fails as well.
Unrooting didn't fix the problem with the oneplus installler.
Anyone else has this problem? Someone knows the root cause?
Did you remove any bloatware or oneplus apps?
No ... I did only install magisk .. did it work for you ?
Seems to be it detects that file is corrupted and stops installing.