[REQ] Boot.img EVA-L19C185B361 - to remove phh superuser - Huawei P9 Questions & Answers

Hi all,
I initially rooted my nougat and i'd like to remove the root.
My understanding was with the root (17 me.phh supersu cm-su subind suinit) in order to remove it, I need to reflash the original boot image.
Like a numpty I didn't make a backup of it.
Is there anyway that anyone might have it somewhere and can share?
I installed the newest TWRP (decryption support) but would like a clean boot.img so when magisk and xposed are working I can do everything systemless.
Thanks in advance!!!

streetsurfer said:
Hi all,
I initially rooted my nougat and i'd like to remove the root.
My understanding was with the root (17 me.phh supersu cm-su subind suinit) in order to remove it, I need to reflash the original boot image.
Like a numpty I didn't make a backup of it.
Is there anyway that anyone might have it somewhere and can share?
I installed the newest TWRP (decryption support) but would like a clean boot.img so when magisk and xposed are working I can do everything systemless.
Thanks in advance!!!
Click to expand...
Click to collapse
I have same build number. How I can help you

Download Nougat firmware and extract the boot from it

Ooh. Right! Hah. I'm an idiot.
I presume I can just flash via TWRP as well too.

Related

Flashable OTA?

When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
idbl_fanatic said:
When I had my Nexus 5 people would make flashable OTA files to be used in TWRP, is no one doing this any longer? All I can find is how to sideload the OTA.
Thanks
Click to expand...
Click to collapse
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
WOW thank you, I didn't know that TWRP did this.
simms22 said:
just flash the boot.img and system.img in twrp. if you had root, youll need to reroot. yes, twrp flashes system.img and boot.img files now as well.
Click to expand...
Click to collapse
Ok, I am a little confused, I am trying to apply the MRA58K from LMY48T OTA found here: http://forum.xda-developers.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 in the ZIP file, I am not finding system.img, or boot.img
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
holeindalip said:
Download the factory images and extract the system and boot.imgs,put them on your SD card(phone storage) enter twrp,select install,then select images in bottom right, select the partition you want to flash to, select the correct.img file
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
idbl_fanatic said:
Just want to double check, this will be ok to do giong from 5.1.1 to 6.0.1?
Click to expand...
Click to collapse
yup
simms22 said:
yup
Click to expand...
Click to collapse
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
idbl_fanatic said:
Ok, so, I got my phone updates, however, I had systemless xposed working on it, MM 6.0.1 (MOB30M) however when I went in to try and enable the modules, it gave an error (a long one) so I thought that maybe I didn't have the correct version installed, or wasn't rooted right, so I went back into recovery, re-rooted, and installed 85.3, now it says that xposed isn't installed at all. So for now, I went back to my 5.1.1 restore. Any ideas?
Click to expand...
Click to collapse
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
zelendel said:
You have to reflash xposed. It is in the system partition so you will have to redo it after making room as google now fills up the system partition almost completely.
Click to expand...
Click to collapse
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
idbl_fanatic said:
I thought that was the whole reason behind the System Less Xposed, so it doesn't install to your system partition.
Click to expand...
Click to collapse
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
zelendel said:
was the systemless updated to work with the new security measures built into the update? You have to remember that with each update google is making things like xposed harder to get working. It is well known that sooner or later xposed all together will no longer be an option.
So I would check all the changes that the update did to see what it changed. I nor most the people I know have not used xposed in a long time so I really cant say for sure
Click to expand...
Click to collapse
That makes sense, maybe I'll go to MMB29K instead.
Systemless root or systemless exposed?
Sent from my Nexus 6 using XDA-Developers mobile app
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
putridfoetus said:
I have systemless xposed working on mob30m. currently have v85.2 installed, all modules working. Only hiccup i ran into was the installer apk. you have to use the one linked in the systemless xposed thread, or it won't recognize the framework is installed.
Click to expand...
Click to collapse
Thank you, I just reinstalled 6.0.1 MOB30M and it works!
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
cL0uD` said:
I'm on 6.0 right now with TW recovery, root with SuperSU and Xposed v85, I want to go to 6.0.1 latest version, what would be the best was to do it?
Shall I uninstall xposed, unroot and get stock recovery and then just try to install OTA or is there another way?
Click to expand...
Click to collapse
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
idbl_fanatic said:
Check out Flashfire in the appstore, it let's you update with OTA, and re-root
Click to expand...
Click to collapse
Yes, used, Great job, Mr Chainfire

[SOLVED] Can I really switch from SuperSU ?

Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.

CF Auto Root : Root Access Disappeared

I used CF Auto Root a while back to root my Nexus 6 (months ago). It did the trick getting the bootloader unlocked and rooting the phone. I then proceeded to install TWRP and then installed Pure Nexus. From then to know the phone has been a joy to use. This ROM is fantastic.
Recently I decided to look into custom Kernels, Elementalx is the one I have been reading up on. I installed the kernel, and then purchase the EX Kernel Manager. Using the app I realized that the phone wasn't rooted, or so it told me. I test this with the Root Checker Basic App and it confirmed that the phone was not rooted.
I am not sure what happened but what I wanted to do was run the SuperSU zip via TWRP again, but wanted to ask you guys if this would be an issue. I can't see why it would but it Rooth had already been achived and then it was gone so..... I just wanted to ask in case.
Sorry that this was a little long winded. Thanks in advance.
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Strephon Alkhalikoi said:
Magisk and SuperSU achieve root without modifying the system partition through patching of the kernel's ramdisk (?). When you installed the new kernel it installed an unpatched copy. This is why you lost root.
Download SuperSU from the XDA thread and flash it in TWRP to restore root.
Click to expand...
Click to collapse
Thanks for the quick reply. That makes sense. I will run SuperSU again. Take care.

Rooting with Magisk more risky than other methods?

Hi there,
I'm in the process of deciding whether to root my next phone with Magisk or SuperSU. The point I want to discuss here is the risk of bricking the phone. I found rather little information on how Magisk actually links into the system, but it seem that it modifies the /boot image. Now my concern is that if anything goes wrong with this, the phone may be bricked with no return. If I compare this to installing SuperSU to /system, if something goes wrong with that, I still have a working boot loader to boot into recovery and install a working system image. But if /boot is damaged, there should be no return.
So my question: is my understanding of how Magisk works correct, and does this mean higher risk of bricking the device?
Thanks
Tom
I use Magisk for 1 month and I have no problems. Even that Magisk is much better than SuperSU because you can hide the root for your applications.
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). Reflashing your stock boot.img and wiping data would likely reverse anything magisk does. So risky? Not if you backup your stock boot first in twrp. But we backup everything before we flash anything right? Magisk is doesn't modify system at all, everything it does is in /data (besides patching boot.img)
So the question becomes, do you need to pass safetynet for any reason? And would you like to be able to take ota updates?
madbat99 said:
The boot.img is not your bootloader, it's basically the kernel (part of it anyways). (...)
Click to expand...
Click to collapse
Thanks for the clarification. That basically answers my question!
You can use magisk it safe
The best feature of magisk you can hide root from other app like pokemon go, banking app etc
And also you can modify the the system make some app system app or uninstall system without modification of system
And lots more for more details check the magisk official thread
And ya don't download magisk from magisk.com or other site it not offical
I am using magisk in miui rom, Samsung note 4
Moto G5 plus without any problems
can i use magisk on rokit io pro 3d?

Guide for rooting

Hello,
I have a second hand p20 pro (C432) with emui 12 on it. I succesfully downgrade to emui 9.1, fw on 9.1.0.387, and got my bootloader unlocked.
Twrp by pretorian installed but can't do anything with it. Data is encrypted, i just need to flash magisk. What's the way to go?
Thx for those who could help,guide me.
aIecxs said:
read Huawei section (deleted)
https://web.archive.org/web/2020092...ithub.io/Magisk/install.html#emui-9-or-higher
Click to expand...
Click to collapse
Thank you sir, i'm now rooted.
But now, contacts, messages and phone dialer keep crashing....uninstalled magisk and everything is fine. Reflashed magisk and same problems
try older Magisk. install the apk and set this file as custom channel. then patch the kernel ramdisk.
https://raw.githubusercontent.com/topjohnwu/magisk_files/b0694fad86/stable.json
i patch kernel.img not recovery_ramdis.img? or the 2?
i'm now with 21.4 and manager 8.0.7 but dialer still crashing (just recovery patched)
then it is probably not caused by magisk itself. maybe factory reset will help.
Maybe i messed to much when debloating fw, went with fresh install before flashing magisk and all working! thx for your help and advices

Categories

Resources