Bootloader Unlock Developments Full XDA Huawei Magisk Magisk Manager News Tech XDA Android XDA Feature

Huawei rolled out an update which broke Magisk, but it can be easily fixed

Huawei rolled out an update which broke Magisk, but it can be easily fixed

Regardless of current troubles in the USA and Australia, Huawei continues to develop their enterprise around the globe. The corporate, which quickly grew to dominate the Chinese language market, now challenges the likes of Apple and Samsung. Their Huawei P20 flagship lineup is a testomony to their success, with reviewers largely praising it for its digital camera, construct high quality, and options, they usually’re sure to make waves once more with the Huawei Mate 20. The corporate’s sub-brand, Honor, gives units just like the Honor Play and the Honor 10 to compete within the mid-range market. It’s due to smartphones like these that many on XDA have been followers of Huawei and Honor units, but as lots of you’re conscious, Huawei determined to cease offering bootloader unlock codes in a shocking anti-consumer transfer, successfully blocking most improvement and modding for his or her telephones.

We’ve beforehand addressed this concern on the Portal, and we’re nonetheless closely dissatisfied by this choice. Getting an enormous like Huawei to reverse their determination or at the least provide you with a compromise isn’t straightforward, and whereas there was some progress on that entrance, the state of affairs continues to be grim for lovers. A current update made individuals lose much more religion within the firm because the update triggered telephones that have been rooted with Magisk to not boot until the inventory ramdisk picture was re-flashed. So not solely are Huawei and Honor system house owners unable to unlock their bootloaders, but people who have already completed so turned unable to root their units. Many bashed the corporate for what appeared like (yet one more) anti-enthusiast transfer, but an investigation into the update reveals that the mushy brick is a side-effect of an update and never deliberately achieved to dam Magisk/root. Right here’s all the things we find out about this update.


Huawei’s “Patch01” Update Stopping Magisk-rooted Telephones from Booting

This difficulty was first delivered to mild, after which additional detailed, by XDA Senior Member Tecalote on the official Magisk Beta XDA discussion board thread. The member stumbled upon this situation on his Huawei P9 after rebranding his gadget so he might set up the official Android Oreo update after which putting in a small “bug-fixing” OTA update. The update itself, which is known as “patch01”, consists of fixes for MMS and gaming, but it additionally features a kernel patch which mushy bricks Magisk-rooted units.

In line with him, he flashed the unique boot picture, the unique restoration, and uninstalled Magisk Supervisor earlier than taking the update, at which level the telephone managed as well simply wonderful. Nevertheless, reflashing Magisk after the update resulted within the telephone getting caught within the “Your device cannot be trusted” splash display. The up to date firmware solely booted up with the unique b528 ramdisk picture. This conduct continued no matter whether or not dm-verity, pressured encryption, or Android Verified Boot have been disabled, and each Magisk v16.zero and v16.7 have been examined. (Simply flashing TWRP was not an problem because the restoration is flashed to its personal partition referred to as recovery_ramdisk, but trying to root the telephone afterward would set off a bootloop.)

Thus far, there have been a number of customers confirming this conduct up to now. It additionally seems that it just isn’t restricted to the Huawei P9, as a consumer on the Huawei Mate 10 boards can also be confirming the identical conduct after putting in the “patch01” OTA update, which leads us to assume that this patch will roll out to all presently supported Huawei/Honor telephones. Given Huawei’s current actions relating to bootloader unlocking, it’s not exhausting to see why individuals consider this update was rolled out to deliberately block rooting. XDA Acknowledged Developer / Acknowledged Contributor topjohnwu, the primary developer behind Magisk, initially acknowledged the difficulty on his Twitter account.

I’m knowledgeable that a new Huawei OTA will make putting in Magisk unable in addition in any respect. At this level I’d simply merely ignore this model even exists.

— John Wu (@topjohnwu) August 23, 2018

Tecalote himself, in addition to a number of Huawei customers and builders, took on the duty to research the difficulty completely through the previous few days and managed to determine out an answer.

Right here is a few additional information relating to the Huawei OTA blocking Magisk challenge. TL;DR, choose “Preserve AVB 2.0/dm-verity” is required on some Huawei units.https://t.co/gNzY5AX4wG

— John Wu (@topjohnwu) September eight, 2018

Why is that this being carried out?

Preliminary proof (and extremely rushed hypothesis, rumors, and articles/dialogue) led customers to consider that this update was pushed out with the only function of locking out rooted customers from the system. In any case, Huawei has just lately taken a hostile strategy to bootloader unlocking. This wouldn’t be the primary time that a telephone producer went after rooted telephones, both: Final yr, we reported that LG included a root checker software that may go haywire when it detected root. And naturally, we even have the various instances of producers and carriers blocking bootloader unlocking to stop customers from messing with their telephones, the place we’re additionally together with Huawei since just lately.

Nevertheless, additional analysis by XDA Senior Member Tecalote and different customers has revealed that this isn’t essentially a case of Huawei cracking down on rooted customers. Moderately, it’s extra possible that we’re coping with an unintended aspect impact of a kernel patch which prompted the Magisk-patched ramdisk picture to be incompatible and stopping telephones from booting. Moreover, customers can easily work across the situation to get Magisk working simply superb on patched telephones.

So it looks like the entire “Huawei is preventing rooted devices from booting” controversy is just an unintentional aspect impact of a patch relatively than an intentional factor. Can be easily labored round when you’ve already up to date, too: https://t.co/DMugh8f0vm

— Arol Wright (@ArolWright) September eight, 2018

On the finish of the day, we can’t inform for positive whether or not this was intentional or not, as Huawei’s actual intentions will not be recognized. We don’t see a justifiable purpose why this update, if certainly deliberately finished to dam rooted customers, exists in any respect as a result of the affected customers have already jumped via hoops to get their bootloaders unlocked. But given current analysis and context across the topic, and the truth that you can nonetheless set up Magisk after the update, we don’t consider this was intentional in any respect.

How can I repair this?

In case you’ve already up to date your system and need to set up Magisk on it, you’ll have to allow the “Preserve AVB 2.0/dm-verity” flag earlier than putting in, as Tecalote revealed on our boards. You can’t merely flash the newest Magisk zip on TWRP, as stated flag is just not set routinely on set up, but you can manually patch the boot picture with Magisk Supervisor:

  1. Obtain the newest Magisk Supervisor APK from the official thread, set up it in your system and open the app.
  2. Be sure that the “Preserve AVB 2.0/dm-verity” checkbox is enabled, and allow it if it’s disabled. In case your system is encrypted, additionally make it possible for “Preserve force encryption” is enabled.
  3. Faucet on the Set up button and choose the “Patch Boot Image File” choice. This can create a Magisk-patched boot picture contained in the app.
  4. Flash the ensuing boot picture to your gadget. You can both set up it on fastboot mode by shifting the file to your pc’s fastboot listing, rebooting your telephone to fastboot mode and utilizing the “fastboot flash boot boot.img” command, or just flashing it with TWRP by going to Set up, tapping the “Install image” button and flashing the newly patched boot.img.
  5. Reboot to system and open the Magisk Supervisor app once more. For those who get a popup asking you if you wish to proceed with Magisk’s further setup, faucet Sure.
  6. Take pleasure in!

When you’re already rooted and don’t really feel like taking the update, you can nonetheless go the old-school method of disabling the OTA supervisor:

  1. Obtain Strong Explorer, MiXplorer, FX File Explorer, or some other root-enabled file browser from the Google Play Retailer or XDA Labs.
  2. Open the app, settle for the phrases and circumstances, give it permissions, and grant it root entry.
  3. Go to the basis of your storage, after which transfer to /system/app/HwOUC.
  4. Rename HwOUC.apk to HwOUC.bak.
  5. Reboot, and you need to be good to go.
Solid Explorer File Manager
Solid Explorer File Manager
FX File Explorer: No ads, No tracking, No nonsense
FX File Explorer: No ads, No tracking, No nonsense
MiXplorer
MiXplorer

Developer: Hootan ParsaMega.co.nzMail.ruYandex.ruMyDrive.ch

Worth: Free

Should you’re operating a customized ROM because of Challenge Treble help, then you need to be protected from this, as this function ought to solely have an effect on Huawei’s personal EMUI software program.

In the event you had in thoughts rolling again from the “Patch01” update for those who’ve already up to date, we extremely discourage doing so: Some updates might have a special XLoader (akin to some updates on the Huawei Mate 10), and also you run the danger of completely bricking your gadget in the event you flash an incompatible XLoader. Moreover, a workaround for Magisk was already discovered. Downgrading isn’t for the faint of coronary heart, so in case you actually need to do it and acknowledge the danger, we advise you to look our boards for a working downgrade technique in your gadget.


The Backside Line

Blocking bootloader unlocking and having insurance policies towards root entry is one thing we can stay with, even when we don’t agree with these insurance policies. But actively blocking rooted customers who’ve already unlocked their bootloaders, and deliberately bricking their telephones with an update? There’s no good purpose for that, and it’s, no less than in our opinion, too pointless of a stretch, particularly provided that rooted customers make up a negligible variety of Huawei’s large international consumer base. We do perceive why customers would assume that Huawei is obstructing root, although, but we actually don’t assume it’s the case right here.

Rooting shouldn’t be seen as akin to piracy, hacking, or any cybercrime. A rooted Android smartphone is just about corresponding to a Home windows pc with admin permissions… or a Linux PC with superuser entry. Those that select to root their units are absolutely conscious of the safety dangers concerned with rooting and are simply in search of methods to get further capabilities on the units they spent some huge cash to personal.

Whereas we don’t assume that is an intentional change, we did attain out to Huawei for clarification and can update this text accordingly if we hear again. It’s nonetheless not the wisest selection to purchase a Huawei/Honor gadget when you’re actually all for rooting/utilizing ROMs: as we talked about earlier than, they’re nonetheless not offering bootloader unlock codes. But within the meantime, in case you’ve already up to date, merely comply with the steps above to get root again.

Need extra posts like this delivered to your inbox? Enter your e-mail to be subscribed to our publication.

!perform(f,b,e,v,n,t,s)if(f.fbq)return;n=f.fbq=perform()n.callMethod?
n.callMethod.apply(n,arguments):n.queue.push(arguments);if(!f._fbq)f._fbq=n;
n.push=n;n.loaded=!zero;n.model=’2.zero’;n.queue=[];t=b.createElement(e);t.async=!zero;
t.src=v;s=b.getElementsByTagName(e)[0];s.parentNode.insertBefore(t,s)(window,
doc,’script’,’https://connect.facebook.net/en_US/fbevents.js’);
fbq(‘init’, ‘403489180002579’); // Insert your pixel ID right here.
fbq(‘monitor’, ‘PageView_XDA’);