Related
Alrighty hey y'all! Just wanted to mention that I'm new to the XDA forums! Glad to be here! I have my honor 8 FRD-L04 here, and here is the problem I am facing... In EMUI 4.1 before the nougat update, I was rooted and had TWRP installed as my recovery. Then when I updated to EMUI 5 I downloaded the file via OTA, and then it took me into TWRP and installed it just fine. Now as usually, when I get OTA updates it always undoes my TWRP recovery and supersu root. So expecting this, I plugged my phone in, used the ADB fastboot and installed TWRP like usual, (following the guide on how to root honor 8 on XDA forums). Now, when going into recovery the phone just sits on Your device has been unlocked and can't be trusted.....(Other junk) Your device is now booting... and will never boot to TWRP. Doing alot of research on the internet (10 hours to be exact) I found a file that finally takes me into TWRP but I can not access my /data files, and it says error mounting /data, therefore I can not install super su, and it also says that my internal storage, sd card, etc is at 0mb...that can not be right. So I am a bit stuck, as of now I am going to attempt to rollback to EMUI 4.1, and if I am successful I will see if I can get TWRP to work again, but if it doesn't work I want to know why it's suddenly bugging out, and if it does work in 4.1 again, I'd like to figure out how to get it working in EMUI 5 because I like the new update! Cheers, and thank you all in advance
Bro you have to push the nougat compitable twrp you can find herehttps://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
VenuGopalu said:
Bro you have to push the nougat compitable twrp you can find herehttps://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
Click to expand...
Click to collapse
Thank you for your reply I have actually came across this article when doing my research, but it doesn't work properly for my particular phone and I don't know why. I guess I will stick with EMUI 4.1 and wait til EMUI 5 has official proper support.
Nougat seems to be working hard to block root on phones.
I have the same problem and would very much like to know what file made you able to enter twrp. Thanks
im on emui 5 with twrp 3.0.3-0, it will flash supersu, but will not root, i know its my version of twrp, but when i flash the new 3.1 version it wont boot
VenuGopalu said:
Bro you have to push the nougat compitable twrp you can find herehttps://forum.xda-developers.com/honor-8/how-to/twrp-nougat-edition-t3504140
Click to expand...
Click to collapse
This worked for me. Thanks man!
hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all
one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting
Thx to reply. Like the others i wanna root to have root apps in my phone ,
Thx . Wanna have apps requires root in my phone . That simple
You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
I failed install su however still waiting for any updates
nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?
ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD
ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.
mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
@st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.
mr. ante0 ..... u r the man , thank you so much
thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0
thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0
Hi,
I received today a notification to upgrade to B360 ( i still use the 4.1.3 emui B151), while my phone as Unlocked Bootloader and root!! I was thinking it was impossible to received this notification when the phone was rooted.
I have a few question yet:
1 If I upgrade to B360 should I loose the unlocked bootloader?
2 If i upgrade to B360 should I loose the root? When yes, how can I root my phone?
3 If i upgrade to B360, can I use Xposed Modules as with B151,
Thanks You for your Help!!!
ben75011 said:
Hi,
I received today a notification to upgrade to B360 ( i still use the 4.1.3 emui B151), while my phone as Unlocked Bootloader and root!! I was thinking it was impossible to received this notification when the phone was rooted.
I have a few question yet:
1 If I upgrade to B360 should I loose the unlocked bootloader?
2 If i upgrade to B360 should I loose the root? When yes, how can I root my phone?
3 If i upgrade to B360, can I use Xposed Modules as with B151,
Thanks You for your Help!!!
Click to expand...
Click to collapse
You will only lose root and xpose. Theres a thread in here about the twrp for emui 5. Start from that if you want root again xpose included.
darKz22 said:
You will only lose root and xpose. Theres a thread in here about the twrp for emui 5. Start from that if you want root again xpose included.
Click to expand...
Click to collapse
Thank you!!
But i have a question, the notification I received is the Final rom or the Beta Rom?
ben75011 said:
Thank you!!
But i have a question, the notification I received is the Final rom or the Beta Rom?
Click to expand...
Click to collapse
Final but improvements will be roll out in the next builds
darKz22 said:
Final but improvements will be roll out in the next builds
Click to expand...
Click to collapse
Rhanks You !!!!
A latest question, can I install this update directly from the Software Update, and than flash the modded Recovery?
ben75011 said:
Rhanks You !!!!
A latest question, can I install this update directly from the Software Update, and than flash the modded Recovery?
Click to expand...
Click to collapse
Yes you can.
darKz22 said:
Yes you can.
Click to expand...
Click to collapse
Thanks a Lot!!
I upgrade and root and install TWRP this morning. All work thine, but I am a little disapointed.
1 I can not uptade The latest SU Binary from SuperSU...... How to fix it?
2 How can I found the Dalvik size etc... because in the new Build.prop, there is nothing ...
3 In phone info, my Buil still in Test Key, and I dont have anymore the systeme update...
ben75011 said:
Thanks a Lot!!
I upgrade and root and install TWRP this morning. All work thine, but I am a little disapointed.
1 I can not uptade The latest SU Binary from SuperSU...... How to fix it?
2 How can I found the Dalvik size etc... because in the new Build.prop, there is nothing ...
3 In phone info, my Buil still in Test Key, and I dont have anymore the systeme update...
Click to expand...
Click to collapse
You updated through ota? First time seeing the test key build number error because of update through ota
darKz22 said:
You updated through ota? First time seeing the test key build number error because of update through ota
Click to expand...
Click to collapse
Yess, I updated trough OTA... So yet, what should i do to update my phone to B360 without problem?
ben75011 said:
Yess, I updated trough OTA... So yet, what should i do to update my phone to B360 without problem?
Click to expand...
Click to collapse
In my experience the only solution to this is to backup data, then if possible, use firmware updater (can downloadn in playstore) then download the b360 update with the Full ota-mf-pv tag. Flash it using dload method. About thw dload method search the honor 6x threads cause i dont use it. I did not encounter this problem when updating
darKz22 said:
In my experience the only solution to this is to backup data, then if possible, use firmware updater (can downloadn in playstore) then download the b360 update with the Full ota-mf-pv tag. Flash it using dload method. About thw dload method search the honor 6x threads cause i dont use it. I did not encounter this problem when updating
Click to expand...
Click to collapse
Thanks You @darKz22, I updated with the update data from firmware updater, and all is thine yet.
But I can not update the SU binary, and install Busy Box.... Any Idea??
ben75011 said:
Thanks You @darKz22, I updated with the update data from firmware updater, and all is thine yet.
But I can not update the SU binary, and install Busy Box.... Any Idea??
Click to expand...
Click to collapse
Is the build number and system update present? If it is im glad to know that. If you really want to root your phone the go to this thread:
https://forum.xda-developers.com/honor-6x/development/twrp-t3583413
It will answer all your questions about that
Be advise that emui 5 uses a different twrp version than emui 4.1 just reaf op's post and you will be fine
darKz22 said:
Is the build number and system update present? If it is im glad to know that. If you really want to root your phone the go to this thread:
https://forum.xda-developers.com/honor-6x/development/twrp-t3583413
It will answer all your questions about that
Be advise that emui 5 uses a different twrp version than emui 4.1 just reaf op's post and you will be fine
Click to expand...
Click to collapse
Thanks You!! All work fine yet. I do a fresh install, installed TWRP and SuperSU and all work thine yet!
Thanks you a lot!
ben75011 said:
Thanks You!! All work fine yet. I do a fresh install, installed TWRP and SuperSU and all work thine yet!
Thanks you a lot!
Click to expand...
Click to collapse
Always happy to help
ben75011 said:
Hi,
I received today a notification to upgrade to B360 ( i still use the 4.1.3 emui B151), while my phone as Unlocked Bootloader and root!! I was thinking it was impossible to received this notification when the phone was rooted.
I have a few question yet:
1 If I upgrade to B360 should I loose the unlocked bootloader?
2 If i upgrade to B360 should I loose the root? When yes, how can I root my phone?
3 If i upgrade to B360, can I use Xposed Modules as with B151,
Thanks You for your Help!!!
Click to expand...
Click to collapse
Hello developers:
I also received that update and my device was unlocked & rooted. Unfortunately I installed it, root was gone. I hardly flashed the TWRP 3.1.0.2 recovery, tried for 3 days now to flash the SuperSU but unfortunately i couldn't, when I flash it, it goes under some process but no change & no SuperSU app when booting the divece.
So please help I just want that stupid root.
KhalidZH said:
Hello developers:
I also received that update and my device was unlocked & rooted. Unfortunately I installed it, root was gone. I hardly flashed the TWRP 3.1.0.2 recovery, tried for 3 days now to flash the SuperSU but unfortunately i couldn't, when I flash it, it goes under some process but no change & no SuperSU app when booting the divece.
So please help I just want that stupid root.
Click to expand...
Click to collapse
Hi @KhalidZH, I had no problem to flash the TRWP . Try to flash this SuperSU and tell me if its work
Thanks
ben75011 said:
Hi @KhalidZH, I had no problem to flash the TRWP . Try to flash this SuperSU and tell me if its work
Thanks
Click to expand...
Click to collapse
It worked!
Thank you so much for help, I appreciate it.
KhalidZH said:
It worked!
Thank you so much for help, I appreciate it.
Click to expand...
Click to collapse
Happy to see that its work !!!!
Thanks for your report
So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it
dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.
i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!
Hi,
I'm looking for a solution to root Huawei Mate 20. I couldn't find much on web search about this topic.
I am also not able to find a way to install TWRP or unlock boot loader.
Any ideas?
Sent from my HMA-L29 using Tapatalk
My phone got an update about a week ago. The details didn't mention Anything about boot loader unlocking but when I checked after the update, there was the ability to unlock the bootloader.
I have already opened the developed settings since november but the bootloader unlock option was greyed out and could not be turned on. I read a post from a different thread that his phone recently got an update with the option to turn on the bootloader unlock option. I have been regularly checking for update since I read that post and so last week I finally got it. I am now able to toggle the switch but I did not finish the process because I want to make sure it doesn't cause any warranty issues. I have been a Samsung user and I am very familia with the "warranty void 0x1" issue so I always waited until my warranty was over before rooting my phone. That way everythung has been tried and tested before I take a leap. If you do get the update please post your experience in unlocking the bootloader and eventually rooting your phone.
Sent from my HMA-L29 using Tapatalk
Maybe try kingroot? If it gets the job done on the pro version it might do it here as well.
Found it: https://www.techdroidtips.com/install-custom-rom-huawei-mate-20-cwm-twrp/ https://www.techdroidtips.com/root-huawei-mate-20/
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Hi please create a new thread how to root the phoneee?
Oem unlock is back :cyclops:
Hi, I can't find Twrp for huwaei Mate 20 can you help me?
Wysłane z mojego HMA-L09 przy użyciu Tapatalka
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Mate please help us.
EDIT:
sorry, now found your post: https://forum.xda-developers.com/mate-20/how-to/guide-manual-updating-firmware-t3892686
so only way to get root it's paying for bootloader code?
OldDroid said:
patch recovery_ramdisk.img in latest magisk manager canary build, and flash the patched_boot.img to recovery_ramdisk through fastboot - voila, you are rooted now, you just have to boot to recovery afterwards (will start to system anyway).
I could also upload my patched recovery_ramdisk.img if you want. Would work for you aswell.
Regards
Click to expand...
Click to collapse
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
JazonX said:
Did you test it on EMUI 9.1 Roms?
Seems it doesn't work. I tried patching using the Canary build mentioned above and even used 19.0.
Neither of them worked, The end results is a bootloop.
Any ideas ?
Click to expand...
Click to collapse
nope, my international mate 20 didn't receive 9.1 yet.
Regards
There is info about root EMUI 9.1 for mate 20X on XDA. "[GUIDE] Root AL00 EMUI 9.1"- https://forum.xda-developers.com/mate-20-x/how-to/guide-root-al00-emui-9-1-t3938483. You need Ramdisk for your device and patche it. Also it is possible to extract Ramdisk from full firmware. Now i have a problem to download full firmware for my phone - HMA-L29 9.1.0.310(C10E10R2P1). I tried https://support.halabtech.com/index.php?a=downloads&b=folder&id=35991 but it is impossible to download zip file. Is there another way to get this firmware?
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
ZTNL said:
Look this thread, the firmare was upload in google drive.
https://forum.xda-developers.com/mate-20/how-to/emui-9-1-t3943112/page6
Click to expand...
Click to collapse
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Need Unlocked Bootloader?
vstrglv said:
Thank you! Downloaded from https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=149496 at last.
Now I have root root for HMA-L29, 9.1.0.300(C10E10R2P1) through Magisk 19.4 (Magisk Manager 7.3.3 ). I had root for 9.0.0.245 with the same Magisk. Downloaded firmware HMA-L29 9.1.0.310(C10E10R2P1) from https://support.halabt…e&c=download&id=149496 , extracted RECOVERY_RAMDIS.img, copied to mate 20 9.0.0.245, patched by Magisk. File is magisk_patched9.1.img. It can be downloaded from https://drive.google.c…Jq_6WNOxgdY5nK4VxLHE86. Then flashed RECOVERY_RAMDIS.img from 9.0.0.245 by adb, updated to 9.1.0.300(C10E10R2P1) and flashed magisk_patched9.1.img by adb. That's all.
Click to expand...
Click to collapse
Could you give a short tutorial of how you did that? Did you have to unlock bootloader?
I guess that unlocked bootloader is required to flash boot image, but I hope to be wrong
Yes, I have unlocked bootloader.
vstrglv said:
Yes, I have unlocked bootloader.
Click to expand...
Click to collapse
Where did you get the bootloader unlock codes? HW no longer support to release it...
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Root on EMUI 10
Has anyone rooted the new EMUI 10? Can you give me a how to?
vstrglv said:
I got unlock code on this forum from Crys18 on 30.03.2019 for $6.
Click to expand...
Click to collapse
How can I contact him?