Related
Hi all,
Someone know How can I Root my device?
You can not yet...
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
mudnightoil said:
First stage would be unlocking the bootloader ... which Huawei now deny you the ability to do.
However it appears someone is offering a working unlock service.
People are reporting it's legit for the P20 / Pro.
Be careful though.
https://forum.xda-developers.com/huawei-p20-pro/development/bootloader-unlock-service-t3852447
Click to expand...
Click to collapse
As a fresh owner of Honor Note 10 I was curious if it's possible to have the bootloader unlocked. Just finished chatting to the admin from the website and he claims that YES, they offer this service for 30EUR. But then I asked him if there's an actual way to root the device and he wouldn't know. My point here is: there's not much of a point to have an unlocked bootloader if you can't get the root on the phone. I think we will have to wait a bit longer till someone gets a working root method. I wouldn't mind to pay for having the bootloader unlocked (for reasonable amount of moneyh) as long as it works...
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
mudnightoil said:
You can't have root without the unlocked bootloader.
So of course there isn't a root method yet ... because no-one was previously able to unlock the bootloader.
If that is now possible, then a root method will inevitably come.
Click to expand...
Click to collapse
Given Huawei's recent dull attitude that reads something like "LOCKED BOOTLOADER is for your safety only" (BLAH BLAH BLAH), reasonable doubt of a commonly available ROOT for this magnificent device is more than imminent...
But hope is all there's left, right
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
Hmmm... there seems to be some work in progress alright regarding a custom TRWP for Note 10, if the google translator works fine, that is:
https://translate.google.com/transl...m/thread-17327282-1-1.html&edit-text=&act=url
And the bootloader unlock code might get somewhat cheaper, too:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
Let's wait and see, I guess
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
7gismo said:
Just to keep this thread alive, does anyone happen to have an access to the Chinese Huawei club forum with TWRP recovery? I'm unable to download the img file there as it requires to have a chinese phone number to register on the site. All it takes is to have that file downloaded. I'd like to volunteer to unlock the bootloader, then flash the TWRP through adb interface and try to root the Note 10 with Magisk or SuperSU just to see if it works.
Anyone with Chinese Huwaei ID willing to download that file, as seen here:
https://club.huawei.com/thread-17327282-1-1.html
Any help is much appreciated!
Click to expand...
Click to collapse
i have downloaded but you need to have unlocked bootloader. i had also registered for that xda huawei unlocker thread, but stll waiting for unlock key.
Here : https://1drv.ms/u/s!AizwhfImY2xzgadtepfbKJ1BQqxMvg
---------- Post added at 02:08 PM ---------- Previous post was at 01:57 PM ----------
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
7gismo said:
Thanks for the help, much appreciated?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Ah well, we have to remain patient till someone actually releases a working TWRP for Note 10. Sooner or later, I guess ?.
Cheers!
Click to expand...
Click to collapse
How did you got it unlocked?
i know there are many pid sources but was waiting for someone to confirm they really work for note 10. Can you please share where you got it from?
Sure, I've posted the link already:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
I chose the fast 1-20min option and it was done that way, indeed. You must pay upfront, of course. They generated the unlock code for me and all I did was a few lines in cmd powershell while phone was in fastboot mode.
There's an ugly message coming up everytime I boot saying that my device has an unlocked bootloader?
But we need a custom CWM or TWRP image now?
I wonder if there's a stock boot image of Note 10 floating around online, perhaps in Huawei Chinese forums?
---------- Post added at 04:28 PM ---------- Previous post was at 03:35 PM ----------
bark1234 said:
Can anyone download Official rom 108 from below baidu link. Atleast it will be useful for recovery if something screwsup. baidu is somehow extremely slow to download and connection resets for me after few hours. Please share once you are able to download.
https://pan.baidu.com/s/1-JF43jLbz2WcTMurYHm0Hw
Password : 6c52
Process :
Unzip the compressed file and copy the dload folder to the SD card.
forced upgrade:
1. Simultaneously press and hold the Note10 three physical buttons (volume up and down keys, power button) until you enter the recovery to upgrade
2. If the upgrade is successful, the machine will automatically restart into the system;
Tip: If there is a problem with the upgrade failure, please check whether the SD card upgrade package is copied to the specified directory and the upgrade package is the SD card upgrade package of the product.
Click to expand...
Click to collapse
Just did some digging there and actually, you can find a working firmware file 125 for Note 10 online. Chances are even the latest 132 build is there somewhere on Chinese forums...
I'd recommended you to get the bootloader unlocked from the link above, if you have a good idea how to proceed with root? My skills are way too limited, I'm afraid?.
The good news is I got my bootloader unlocked. The bad news is the apk file requires root, which I was hoping to obtain by flashing a custom TWRP image. I thought that's what it was available in that Huawei club Note10 forum...
Thanks for your reports.
TWRP image file is included in K-RecTools_8e.apk.
Rename apk to zip and decompress it, you can get the twrp.img.
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
mudnightoil said:
If one enterprising individual has found a way, and is charging €30, then others will find a way too, and will provide it for less / nothing eventually.
He's just the first, and good for him.
Click to expand...
Click to collapse
trd_jzx100 said:
i will be a Guinea pig and see if it works. i should have my bootunlock code from the link above soon and looks like we have a twrp (hopefully it works) from a few posts back. i shall try and download fhe 108 firmware just in case i get bricked. when i get home. will keep you guys posted.
TWRP INSTALLED MAGISK 17.1 FLASHED AND SAFETYNET PASSED. ADWAY INSTALLED, SUCCESS
NOTE I AM ON B132 AND IT TRYS TO GET ME TO INSTALL B132 THROUGH SYSTEM UPDATE WHICH IS 3.9GIG
Click to expand...
Click to collapse
OK now. I managed to flash TWRP on the phone successfully. However after i tried to flash Magisk, the phone remains unrooted So it's a no for me. Any idea why?
There's a red error stating coming up twice: failed to unmount '/system' (Device or resource busy). But the Magisk zip get installed anyway. So what am I doing wrong?
EDIT: the bloody TWRP is password protected. My pin password doesn't do the trick...
EDIT 2: OK, just removed my lock screen in phone settings, no errors in TWRP anymore. But after I flashed Magisk (no erros again), phone still remains unrooted? What the hell?
What version magisk are you using
trd_jzx100 said:
What version magisk are you using
Click to expand...
Click to collapse
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway?.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation ?. But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
7gismo said:
Nevermind now. I had to install the Magisk manager app additionally and the root became visible then. First thing installed was adaway.
Thank you for your time and help.
___________________________________________
BIG THANKS goes to tensoba and trd_jzx100 for their tips and participation . But most of all bark1234 is the one who made all of this possible after he kindly provided us with the crucial apk file containing TWRP image.
Ladies and gentlemen, Huawei honor note 10 can be rooted now.
Click to expand...
Click to collapse
bark1234 said:
Awesome mate. Finally we have proper way to root.
Can you please create a thread and mention process to root for others for follow.
Click to expand...
Click to collapse
I'll see what I can do. The least I can do is to create a brief tutorial how to root this beauty of a phone?.
Thanks again for your tremendous help
This guide is for folks who want to turn their stock Mediapad M5 SHT-W09 (C567) in to a rooted, ROM-flashing-friendly device. All credit goes to those listed below, without whom I would have not had a clue how to proceed. The real purpose if this post is to, essentially, get all the steps in to one, comprehensive, guide for all those folks who were unfortunate enough to have purchased their BOOT-LOCKED, ENCRYPTED, FUNKY-AS-HELL Huawei device.
This is my first (and last) Huawei device because of those things. My previous (and any future) devices will not have a locked bootloader, or will at least be easily unlocked. Lesson learned—do your research before spending your money. That being said, let's proceed.
CREDITS
@stinger4321 For link to online bootloader unlock service.
@Apo11on For rooting guide.
@Zackptg5 For DM-Verity, ForceEncrypt, Disk Quota Disabler.
@schwabe93 For TWRP & ROM [LOS 15.1 Unofficial]
@Setialpha and the NanoDroid team for µg (microG) via NanoDroid.
@TiTiB [me] For debloating guide.
In order to keep this guide as brief as possible, I am not going to mention any alternative, nor unsuccessful methods—only those that worked FOR ME. Do some "re/searching" and you may find something that works best FOR YOU.
UNLOCKING BOOTLOADER [GRRRRRR ] Thanks to @stinger4321
AFAIK as of this writing, 18 Dec 18, you will have to pay to unlock the bootloader. I used the online service found here:
https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275/page19
It took about 10 hours for me to get the code, so be patient.
ROOTING Thanks to @Apo11on
https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
It is a Magisk rooting solution, but once rooted you can change to another type, if you wish.
TWRP [3.2.2-1 Unofficial] Thanks to @schwabe93
https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
Not everything is functional, but hey, you'll have TWRP.
ROM [LOS 15.1 Unofficial] Thanks to @schwabe93
https://forum.xda-developers.com/mediapad-m5/development/rom-lineageos-15-1-t3813826
DM-Verity, ForceEncrypt, Disk Quota Disabler @Zackptg5
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Read the instructions, and pay attention to the order of the steps, "This zip should be flashed after anything that modifies your boot img"
Easily the most stable ROM I've ever used! And I've used, probably, 70 or 80 over the years.
µg (microG) via NanoDroid Thanks to @Setialpha and the NanoDroid team
https://forum.xda-developers.com/apps/magisk/module-nanomod-5-0-20170405-microg-t3584928
LOS 15.1 [Unofficial] does not, thankfully, include GAPPS. µg (microG) is "A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries." that allows for most functionality that would otherwise require Google's crap.
GSI PROJECT TREBLE ROMS Thanks to @mishaal Rahman, Editor-in-chief on the XDA-Developers Portal for the "How to flash a Generic System Image (GSI) on Project Treble supported devices" guide.
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
I played around with four different GSI ROMs, but came back to LOS. I highly recommend trying them out tho because in my experience, using the adb method [link and commands below], I never lost any apps/data/settings—everything was still there, just with a new ROM to play with.
ADB COMMANDS [assuming already installed/authorized/plugged in, etc.]
adb fastboot bootloader >>>BE SURE THAT "PHONE" & "FRP" BOTH SHOW "UNLOCKED" BEFORE PROCEEDING<<<
fastboot erase system
fastboot -u flash system [name of system image you downloaded]
fastboot reboot
Disconnect device and play with new ROM.
>> DEBLOAT <<
This device is not a phone. I don't do any phone-like things with it. My debloat list is not for everyone—I'm very aggressive in my approach. Use your favorite search engine to find "bloatware safe to remove", and proceed with your own brain. You now have a rooted device with TWRP so why not do a backup and have fun debloating? That's how I figured out what to, and most importantly, what *not* to delete. BTW, I have used logcat readers to analyze the errors caused by my aggressive deleting of system assets, and am okay with the few errors that are caused—mostly the device trying to do "phone things" and not finding the required assets.
My method is to delete files/FOLDERS of those things I don't want—you have a rooted device, why use a "system app uninstaller" that might not fully do the job? The folders in which I do my deleting are, in order, /data/data, /system/app, /system/priv-app, immediately followed by a reboot, without which all bad things are possible.
I use the awesome MiXplorer (available for free, here on xda) for many functions—including root exploring/deleting, so I get rid of the ROM's included:
html viewer, gallery app, PDF viewer, text viewer/editor, et. al.
Below items are from LOS 15.1 [UNOFFICIAL]
⫸ /DATA/DATA
"Tele" "phone" "call" "cell" anything, blockednumber, dialer, carrier, stk, ctsshim, egg, mms, gallery3d, live wallpaper picker, and live wallpapers (noisefield, music vis, et. al.), dreams
⫸ /SYSTEM/APP
WAPPushManager, Stk, messaging, LiveWallpapersPicker, EasterEgg, CtsShimPrebuilt, CarrierDefaultApp, BasicDreams
⫸ /SYSTEM/PRIV-APP
"Tele" everything, WeatherProvider, MmsService, ManagedProvisioning, Gallery2, EmergencyInfo, Dialer, CtsShimPrivPrebuilt, CellBroadcastReceiver, CallLogBackup, CarrierConfig
I may have missed a few, and every ROM is different, so you may find more things to debloat.
If you found this guide to be useful, please hit the "Thanks" button ?
Unnecessary post deleted by poster
I am going to document my experience with unlocking, rooting and custom rom'ing my device.
I have an SHT-AL09, MediaPad M5 LTE. Country code is C00 (China). I don't know why my experience is quite different from @TiTiB; it could be the fact that mine is LTE device. But the fact is Huawei has MediaPad M5 8.4" (WiFi or LTE), MediaPad M5 10.8" (WiFi or LTE), MediaPad M5 Pro. That's at least 5 variants, and I suspect the ROM'ing procedure won't be the same.
Going back to stock
Firstly, I found myself bricking the device a couple times. But the eRecovery feature saves the day. As soon as you unlock the bootloader, the boot screen would tell you that the device is not safe, and you can run eRecovery to reset it (pressing volume Up for 3 seconds). That feature can connect to WiFi outside of Android, download the ROM specific to your device, and reset the whole thing. I had to do it twice, and I think it took about 45 minutes. It works flawlessly, and everything is reset (except the bootloader still stays unlocked.) So, I would say, don't be concerned about bricking it. Unless you plan to replace the bootloader, then I can't advise you.
Important key combo
As you install TWRP and ROM, you will need these key combination handy.
• Reboot - hold down the power button.
• Fastboot - As soon as it boots, and just before the mediapad screen, hold the volume down button WITH the USB cable connected.
• Recovery - Hold down the power button and volume up WITHOUT the USB cable connected.
Credit to @pyarle on https://forum.xda-developers.com/showpost.php?p=77238982&postcount=31
Choice of TWRP
This is important to know. I found two TWRP's advertised for MediaPad M5.
• From @schwabe93 https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
• From @Pretoriano80 https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
The first one can boot even if the data is encrypted. But it cannot decrypt data, nor can it flash any LineageOS ROM (even the one posted by @schwabe93 here https://forum.xda-developers.com/mediapad-m5/development/rom-lineageos-15-1-t3813826 )
The second one cannot boot if the data is encrypted. But, it can boot just fine if the data is unencrypted, and it could flash the LineageOS image from https://openkirin.net/
You can switch between them; it's a matter of flashing the right image in fastboot. Sadly, not one TWRP can rule it all, but that's the way it is today.
My success story
Here goes how I got LineageOS on my MediaPad M5 LTE
Download ROM and zip file
• This is the ROM I used. https://openkirin.net/builds/openkirin_los_beta5.img.xz
• Unzip it, then copy it to the external SD card.
• For DM-Verity, ForceEncrypt, Disk Quota Disabler @Zackptg5 See https://forum.xda-developers.com/and...crypt-t3817389
• Download the zip file, and copy it to the external SD card as well. You will need to decide whether to disable encryption or not. See the ROM section below. But if you decide to keep the data encrypted, rename the file to Disable_Dm-Verity_12.16.2018.zip before you copy it to the SD card.
Unlock the bootloader
• https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275
• I ended up paying $22 to get an unlock code. https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
• If your device has not been updated to a new Huawei ROM, you might have luck with a $5 solution with dc-unlocker. Otherwise, don't bother with downgrading. I tried for days; I just couldn't get it to work.
Root
• This is straightforward. https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157
TWRP
• Install this first. @schwabe93 https://forum.xda-developers.com/mediapad-m5/development/recovery-twrp-3-2-2-1-t3813825
• Don't forget, after the fastboot flash command and fastboot reboot, you have to boot to recovery right away. Otherwise the stock ROM might remove TWRP. Don't forget your key combo.
• Boot to recovery. Do a normal wipe (aka. Data, Cache, and Dalvik). (It won't be able to wipe /Cache.) Then do a "Format Data".
• Boot to Bootloader, and flash the second TWRP @Pretoriano80 https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917
• With the data partition not encrypted, the second TWRP will boot. It can wipe /Cache.
Install ROM
• Hopefully, you have the LineageOS ROM from openkirin downloaded onto the SD card already.
• Still running @Pretoriano80 TWRP, flash the ROM. It already has google apps.
• You will be flashing the ROM as an IMAGE (to the "system" partition.)
• Here comes an important decision you have to make. Would you like to encrypt your data partition? If so, no TWRP can flash anything onto the device again, so you better figure out all the zip files you'd like to install.
• After you make your decision, rename the Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip file if necessary, and flash it. (TWRP has a file manager for you to rename files).
Should I encrypt or not encrypt?
• This is a personal decision. If you keep it unencrypted, your life would be easier. You can stick with @Pretoriano80 TWRP and boot to it, and flash whatever zip files you'd like down the road.
• If you encrypt it, you will have to flash @schwabe93 TWRP next time you'd like to run TWRP. And all it could do is to format data, so that you can flash @Pretoriano80 TWRP again and flash. You would have to backup data with TitaniumBackup in Android, and restore it after the fact. You see the inconvenience?
• But, you know, if you lose your device, you would hate yourself for not encrypting your device.
Hope this helps anyone who has an SHT-AL09. The LineageOS rom runs really well, and I love the screen and sound.
Thanks @pazzu, especially for:
"Going back to stock
Firstly, I found...I would say, don't be concerned...". This makes me feel even more adventurous.
And the stuff about TWRP. I have decrypted my device since my first attempt at using @Pretoriano80's TWRP, so I'm going to try it out again. Flashing .img files via TWRP is quicker and easier for me than doing it with PC and adb.
Good stuff, mate! Thanks
EDIT: Now running @Pretoriano80's TWRP! No success with Havoc GSI—won't boot. More researching...
Sent from my SHT-W09 using XDA Labs
@TiTiB The fact is you have an SHT-W09 and I have an SHT-A09, I don't know if there are differences when it comes to custom ROMs. I can share a failed story though; I installed Magisk-v18.zip by installing it in TWRP. That was an epic failure that I had to recover using eRecovery. Good luck!
TiTiB said:
UNLOCKING BOOTLOADER [GRRRRRR ] Thanks to @stinger4321
AFAIK as of this writing, 18 Dec 18, you will have to pay to unlock the bootloader. I used the online service found here:
https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275/page19
It took about 10 hours for me to get the code, so be patient.
Click to expand...
Click to collapse
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.
thecdn said:
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.
Click to expand...
Click to collapse
I encourage you to do your best to stop any firmware update from Huawei, and try the dc-unlocker service. It seems that as long as your tablet is not upgraded to a certain build, dc-unlocker service would work. See https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275
pazzu said:
I encourage you to do your best to stop any firmware update from Huawei, and try the dc-unlocker service. It seems that as long as your tablet is not upgraded to a certain build, dc-unlocker service would work. See https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275
Click to expand...
Click to collapse
What @pazzu says is very true—don't do any upgrades! Also, look around here on xda for unlocker services other than dc-unlocker & global-unlocking. I remember anecdotal stories about such-and-such service that "worked when others didn't", so don't give up hope.
Sent from my SHT-W09 using XDA Labs
TiTiB said:
What @pazzu says is very true—don't do any upgrades! Also, look around here on xda for unlocker services other than dc-unlocker & global-unlocking. I remember anecdotal stories about such-and-such service that "worked when others didn't", so don't give up hope.
Click to expand...
Click to collapse
Yeah, the don't upgrade thing lasted about 5 minutes after I opened the box. I'm geeky about devices, upgrading it was as natural as breathing
Tried ministryofsolutions and they said no. Tomorrow I'll give dc-unlocker a go but I'm not optimistic. It's still a beautiful device, I guess I can live with it unlocked/unrooted.
The latest firmware is not DC-unlocker compatible yet, but it's not the end of the world. There are other services who send you a bootloader unlock code although they are simply more pricey ($30-60).
As for TWRP, I recommend TWRP for P10 because it's compatible with MediaPad M5 and capable of handling encrypted data partition and ADB.
thecdn said:
I got my M5 Monday and went to that site yesterday but it had no codes left for the wifi only version. Has that happened before? Does this mean they will never get any more? It will be very depressing if I can't get my shiny new M5 unlocked and rooted.
Click to expand...
Click to collapse
Responding to my own post...
I emailed the service unlock bootloader service in question tonight about ever getting more wifi unlocker codes and they replied, "Yes we will, We are currently testing the service"
So, that sounds hopeful.
Hellow Pazzu. I am a chinese man .I am very interesting in rooting android and install AOSP on my devices. But I am studying in
junior school so I have not a very known for android , Linux and English. The transformer software is not reliable . I have some questions about your article.
Frist why were you install TWRP twice .Whats the problem with the log of TWRP,if I wont do this what will happened?
Second once in a while I was wipeing the data suddenly the power was off .Than I cant reboot my devices.But it can boot into fastboot.
Then I used ADB to write system.img recovery.img boot.img it still cant working .I had write that 3 imgs why cant working?
Having a CMR-W09 with testpoint and Potato NV the bootloader unlocked but for almost one week was trying to get rid of the FRP lock . Ended up getting rid of the lock by flashing CMR-W09_hw_eu with Android 9.0. now I have the TWRP vtr3.2.1.0-v0.4. At least for me this recovery remained even after flashed the Android 9. Dont forget the button combinations.
Put official ROM on SD card in folder dload , turn tablet off keep Volume up and Volume down pressed together with Power botton. When Huawei logo comes up, release Power button and the ROM will be flashed.
Few tips when in TWRP you get failed to mount '/vendor '/cust '/odm etc. Get to Wipe in TWRP >Advanced Wipe >Repair or Change File System and select the partition can not be mounted >Change file system> select EXT2 > after that select EXT4, now that partition can be mounted again. The only you can not repair here ist the '/odm . For that solution is Huawei Update Extractor found here >https://forum.xda-developers.com/t/...updated-v0-9-9-5-open-source-library.2433454/ Extract the ODM.img from original ROM into the ADB folder and flash it on fastboot > fastboot flash odm ODM.img
One tip.... you dont have to use command > fastboot reboot , just keep volume up and power button> release power when Huawei logo comes up, so you will not have the custom recovery replaced with erecovery. That especially when you dont have all workj done in custom recovery and you dont want to lose it.
RobZen77 said:
Having a CMR-W09 with testpoint and Potato NV the bootloader unlocked but for almost one week was trying to get rid of the FRP lock . Ended up getting rid of the lock by flashing CMR-W09_hw_eu with Android 9.0. now I have the TWRP vtr3.2.1.0-v0.4. At least for me this recovery remained even after flashed the Android 9. Dont forget the button combinations.
Put official ROM on SD card in folder dload , turn tablet off keep Volume up and Volume down pressed together with Power botton. When Huawei logo comes up, release Power button and the ROM will be flashed.
Few tips when in TWRP you get failed to mount '/vendor '/cust '/odm etc. Get to Wipe in TWRP >Advanced Wipe >Repair or Change File System and select the partition can not be mounted >Change file system> select EXT2 > after that select EXT4, now that partition can be mounted again. The only you can not repair here ist the '/odm . For that solution is Huawei Update Extractor found here >https://forum.xda-developers.com/t/...updated-v0-9-9-5-open-source-library.2433454/ Extract the ODM.img from original ROM into the ADB folder and flash it on fastboot > fastboot flash odm ODM.img
One tip.... you dont have to use command > fastboot reboot , just keep volume up and power button> release power when Huawei logo comes up, so you will not have the custom recovery replaced with erecovery. That especially when you dont have all workj done in custom recovery and you dont want to lose it.
Click to expand...
Click to collapse
How did you unlock the bootloader? I'm exploring different options, but not sure which route to go. My m5 is on emui 9.1. If I can down it to 9.0 or 8 (maybe using hisuite?) I think I can brute force it at least (there a few promising projects on github). But I just don't know is the honest answer. Grateful if you would elaborate. I'm reading up on testpoint atm. Looks promising.
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
grego34 said:
Hi all
I have just bought a new Oneplus 6 and wanted to install Lineage Os.
I had initially set up the OP6 with my google account and installed some minimum apps over a couple of days. The phone updated a couple of times. I think I started on Android 8, it definitely updated to Android 9 and I think it updated to Android 10. But I am not completely sure of this because I did not take notice at that stage because I didn't realise that this might have significance..
I followed the guide from the lineaoge os wiki here
wiki.lineageos.org/devices/enchilada[
I got as far as using adb to Fastboot boot twrp-3.3.1-2-enchilada.img (which was the latest image in the dl.twrp.me/enchilada/
It then got stuck in the qualcomm crashdump line on screen.
I spent a day checking posts, including here on XDA. There are a lot of posts dealing with this issue and I did try to follow some of them with less or more success but no resolve. I downloaded Android 9.02 and used the following instructions
techtrickz.com/how-to/recover-oneplus-6-and-6t-from-qualcomm-crashdump-mode/
The routine started to run and then posted a series of error messages and exited. ( I have a screenshot of the terminal window but cannot see a way to post it here)
I have tried to research this further and there are plenty of posts and lots of suggestions. But to be honest I have become confused as some of the posts give significantly different solutions to each other.
I wondered whether it would be possible to give me some help or point me in the right direction to a post which is current and has the steps that I am likely to need succeed..
Thanks in advance for any help you can give.
Click to expand...
Click to collapse
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
[email protected] said:
I would recommend using fastboot flashable stock rom from here. People also like to use msmtool, but I feel like it is an overkill.
Please note this warning:
These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie.
So grab the latest oxygen os 10, and follow the instructions to flash it. After that, if you are feeling a bit paranoid maybe download a zip from oneplus and do a local update. You now should have your phone back.
Official TWRP does not support android 10 yet, as far as I understand, so that is probably the issue. If you want lineageos 16, you should downgrade to android 9 using a downgrade package provided by oneplus and then update to Oxygen OS 9.0.9.
There is unofficial twrp by mauronofrio that supports android 10. If you want to go from OOS 10 to some other android 10 rom
Click to expand...
Click to collapse
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
grego34 said:
Thanks very much for your helpful reply. I am now back to a working phone with Oxygen os10. And you have also explained what was wrong when I tried to fix it, I was trying to load an Oxygen Os 9 on a phone that had already been upgraded to 10 and you have explained what went wrong in the first place, I was trying to flash an incompatible TWRP image onto Android 10. So your short post has explained a lot. Thank you.
I am not feeling paranoid unless you advise that I should be and I do want to install lineage os. So I need to revert to Oxygen Os9. I have looked on the Oneplus site and that have found the option to Upgrade to 10.3 but no option to downgrade. In the Oneplus community there is a link to downloadable ROMs, these are divided into a number of folders some of which look not applicable. There are three folders that look of interest
1. Signed flashable zips
2. OTA incremental update zips
3. Stock boot-recovery images
Here is the link /forums.oneplus.com/threads/oneplus-6-rom-ota-oxygen-os-mirrors-for-official-oxygen-os-roms-and-ota-updates.835607/
I can see it is not the OTA Incremental that I need but am unsure if it is signed flashable zips or Stock boot recovery images. or whether it is neither.
Do I flash as normal or would it be a local update?
I would be grateful for any further advice.
Thanks again and for any help provided now.
Click to expand...
Click to collapse
I have had luck with this downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
TexnoViking said:
I have had luck with //oxygenos.oneplus.net/fulldowngrade_wipe_MSM_17819_181025_2315_user_MP1_release.zip" downgrade package. I basically googled it, the package is hosted on a legitimate website, so that's what I used. Just download it, put it on your phone and do a local upgrade through updater app.
Once you have done that I would recommend upgrading to the latest Android 9, which is OOS version 9.0.9 I believe. Then go ahead and follow instructions to install lineageos.
I am actually on LineageOS 16 + MicroG right now, so I ran into the same problems you did Glad I could help!
Click to expand...
Click to collapse
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
grego34 said:
Thanks so much for your reply again.
I used your downgrade link and that all worked well and then let it upgrade to OOS 9.0.9. Again all very positive.
I then tried to flash TWRP to the device using this image "twrp-3.3.1-2-enchilada.img" It appeared to flash okay. Then I issued the command
"fastboot boot twrp-3.3.1-2-enchilada.img" over my adb connection and it returned to the Qualcomm Crashdump error.
I presume I have to start again with the exception that this time I can use a flashable stock rom that is OOS 9.09? Is that correct?
Then do you have any suggestions for getting round the TWRP problem? Did you use a different version?
Thanks in advance for any help.
Click to expand...
Click to collapse
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
TexnoViking said:
Hm. Yes, unfortunately the safest thing to do is to start again. But you can start with 9.0.9 right away.
People have been discussing a similar issue here. It seems like using unofficial twrp by blu_spark helps. Maybe twrp-3.2.3-x_blu_spark_v9.91_op6.img or maybe try the latest one.
Also, make sure you read the instructions on lineageos website. Make sure you have oem unlocked, usb debugging enabled and you clicked "always give access to this" device or something, do the fastboot set_active a. I have also used fastboot flash boot_a <recovery_filename>.img. However, I do recall using fastboot boot <recovery_filename>.img some other time and I think it worked....
Anyway, yeah, maybe try this modified recovery by blu spark and follow the instructions carefully.
Click to expand...
Click to collapse
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
grego34 said:
Thanks very much for your helpful reply and apologies for the delay in my reply to this post, I have been tied up with work the last couple of days.
I did re-install OOS 9 and then followed the instructions on the Team Win site to install TWRP in the Oneplus6. I had success after I used the latest TWRP image and zip from that site . I was then able to install Lineage OS and Microg as I wished.
So thanks for the help all. Really appreciated.
Click to expand...
Click to collapse
Great! I am glad you managed to fix your phone! Enjoy
My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks
zzjea said:
My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks
Click to expand...
Click to collapse
I've tried to sideload OOS 11 using Los recovery, but it doesn't work. And, since OOS recovery doesn't support sideloading I'd say that sideloading isn't an option.
However, using payload dumper and fastbootd may be an option. I would have tried this but I'm on 12 and there's no full install zip. But you're going back to 11 so this is a possibility.
But I wouldn't make these changes in the current working slot - don't break what's working.
I'm also not sure whether to use the OOS recovery for the fastbootd stuff or use one from a custom rom.
As you can gather, I've not done this. So you have to work out the details yourself and be prepared to be a guinea pig for the process.
If you do go down this path I'd be very interested in the outcome.
Of course, you could always use the MSM tool to go back to an older version.
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
I presume that A and B slots are partitions
Code:
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde35
So try using MSM tool to restore them or find a copy of that partition from a working phone and flash on yours.
Maybe this can help you as well.
zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
Here's some information that I found helpful:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
Dynamic Partitions | Android Open Source Project
source.android.com
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Here's a couple of ways to get one partition to look like another one:
1. The Los pre-installation instructions have instructions on how to sync the partitions. Note: it doesn't sync boot, dtbo, or vbmeta.
2. If you're rooted you can copy one partition to the other using
Code:
dd if=/dev/block/by-name/xxxx_(active-slot) of=/dev/block/by-name/xxxx_(inactive-slot)
For example:
Code:
dd if=/dev/block/by-name/boot_b of=/dev/block/by-name/boot_a
Note that you can find out which is the active slot using getprop ro.boot.slot_suffix
I've written a shell script based on the Los zip in 1. (see attachment) that will do all partitions - use at your own risk. Don't run it unless you understand what it's doing.
UPDATE: You can now get root on the Android 10 Umidigi A7 Pro using magisk.zip v25.2 (25200).
See post 10 for more info
----------
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
[reserved]
earlier today i managed to find a link for magisk canary. i dont have the device near me atm, but i believe the manager is v7.5 and magisk itself is v19.X. the output patch file comes out named differently with the older version (newer version appends a unique string behind the name). however, same results as before. boot loop.
one positive note tho: the patched boot file completes with a big green check rather than the runtime error, or whatever it was previously.
i tried pushing the patched boot file over fastboot and via the flash tool. same results regardless.
re-flashed the stock boot image and phone is back up and running. still no root though.
still leaning strongly toward it being a magisk problem, but ive seen mention of disabling some security features dealing with individual partitions, but that was on other umidigi models, so ill have to research further if nothing else pans out
found this tut mentioning vbmeta. otherwise, same process that ive been using with no success. figure its worth a shot. ill post back with results
rooting the umidigi a7 pro (magisk)
rooting the umidigi a7 pro (magisk). GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
This guide is for advince users only! better guide comming soon on XDA (I have test this on my own umidigi a7 pro )In order to root your umidigi a7 pro you need to: 1) download device FW --> https://community.umidigi.com/forum.php?mod=forumdisplay&fid=235 (DO NOT download the EEA verison if you are not in Europe!) 2) download sp flash tool in case you brick you phone. --> https://spflashtool.com/ 3) unlock your bootloader --> https://www.getdroidtips.com/unlock-bootloader-umidigi-a5-pro-2/ 2) flash this vbmeta.img file with fastboot in bootloader mode. --> https://mega.nz/file/dnAS3AhD#g5PnSg-0UKFvyhZSZ8Em6gKO2Do7avaUepPmsH75-Bg cmd: fastboot flash vbmeta vbmeta.img 3) extract the boot.img from fw.7z file and patch it with magisk 4) flash your patched_boot.img in bootloader mode cmd: fastboot flash boot boot.img enjoy your rooted phone!!!
nope, the vbmeta thing didnt help. bootloop. i tried using the patch from the latest magisk, and the patch from the older version of magisk. same across the board.
double b26 said:
to cut to the chase, i have this Umidigi A7 Pro [128gb, global, non-eea rom] that im trying to root. ive hit a snag with Magisk patching.
at this point, and after much tribulation finding correct drivers, i have managed to get the bootloader unlocked [orange state notice at boot] via fastboot commands on the windows 10 box. device successfully boots to stock, un-rooted rom
then...
ive installed the latest Magisk Manager,
copied the original boot image from the stock rom over to the device,
ran the patch operation on magisk
copied patched boot file back over to pc.
load up smart phone flash tool and the stock rom,
selected the patched boot file in the flash tool > boot
pushed to device
ENDS with error notice on flash tool. device goes into bootloop.
resolve by flashing back all of the unmodified stock rom.
multiple attempts, same results
from what ive gathered, there may be an issue with the later versions of Magisk that have a problem patching the file correctly. word is that v20.2 and lower have worked with this device.
so at this point, im trying to install a downgraded version of Magisk. when i install an older version of magisk manager, it want to update the manager, and install magisk newest version. in settings, ive seen a custom update channel option, but i cant find the right input to make that point to an older version. IF thats even the right path to take?
ive been rooting devices for over ten years, but in the past few, i kinda fell out of the game since the newer devices have most of the features i used to have to root/rom to have. but now, im wanting to focus more on secuity and privacy, so im back at it. only to find things have changed substantially. so im well versed in the field, just rusty, and needing a crash course on magisk in general, and specific advice on this umidigi.
for picking it up on sale for $70 brand new from the manufacturer (summer 2021), its a solid device. on par with with same-year samsung A series, but half the cost and twice the storage. the Umi doesnt have an oled screen like the samsungs, but it does have a metal frame and glass back. also came with a decent phone case and preinstalled screen cover. 4g unlocked dual sim slots work with t-mobile over old sprint tower nearby, and their gsm towers in other areas. handles a 128gb sd card without problems. cameras are very similar to a samsung a20, but the umidigi includes an added marco lens, which is nice.
once i get this thing hammered out, ill try to compose a concise how-to and upload the files. looking around online, theres a lot of bad or outdated info for this device. ive had to hodge-podge the bootloader unlock from various guides for this and other umidigi models.
thanks in advance everyone!
Click to expand...
Click to collapse
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
[RESOURCES]
magisk download archive
Download Latest Magisk zip v23.0 and Magisk Manager 8.0.7 and Root your phone
On this page, we will share the full instructions to download and install Magisk zip on your Android Phone. This tutorial is also for the newbies/noobs
www.getdroidtips.com
19deke55 said:
Glad to see I'm not the only one seriously interested in modding this phone. Although, now it belongs to my partner because her Huawei was not playing well with what she was using it for - playing a couple of games and messaging. It had started to slow down. Anyways, to get back to the Umidigi. I had looked at modding it and to be honest it seemed to be more hassle than it was worth and I think I couldn't get the thing rooted. I could connect to my laptop (it's honeslty much easier using Linux and installing ADB and Fastboot there) as Linux does not have the same issues with drivers that Windows has. Everything I do is through Linux...
So, in the end and because I now don't have the phone, whenever I need added peace of mind with a phone I try very hard to not install my Google account on the phone. I can install apks using APKPure for the few additional apps that may not be on the Stock ROM or not initialized through Play Store.
I'm afraid I can't help with Magisk though. The couple of times I've tried to work with it has not worked and I simply do all work through Linux and either push or sideload stuff or use a microSD. Often using TWRP but not always.
Cheers... hope you have some luck with what you are trying to achieve.
Click to expand...
Click to collapse
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
double b26 said:
the driver issue was a bit of a hassle to sort out, but partially due to my sub-standard hughesnet satellite connection being sooo sloooooow. everything takes ridiculously long time.
> thus far, ive managed to get drivers and all that to mesh.
> bootloader unlock was straightforward... a few command lines
> from there, it should be a simple process of sideloading the magisk manager apk. within the manager, select [install] magisk zip, select [patch file] option from popup, point it to the [boot file] u pull from the stock rom image (now on your device storage)
> move the magisk patched boot file to the computer, run the flash tool, flash the patched boot, reboot and verify root <<OR>> push via fastboot
rather than reboot, i get boot loop. LOL
everything goes thru successfully, but just not working out. ive read around and seen talk of there being issues with magisk itself, and the patch file it outputs. something about using an older version, perhaps it has to be a specific one, will allow successful root. i gotta see if i can find that, and go from there.
magisk, from my understanding, serves the same purpose as super user or superSU. but also has some added benefits that are needed with modern system security, and the ability to install 'modules' from the magisk zip. sounds like it may be similar to xposed framework, if you know that. anyway, check the link i posted in previous post if you want to know more. apparently its the new big thing in root.
also, i guess TWRP is only partially functional on the Umidigi A7 Pro. im not sure exactly how or what. i just decided i would try the newer method since it seems like the way things are headed
if i can get this thing sorted out, ill bundle up the files and post up a package for people to grab. the way people talk, the same process can be used for several umidigi devices, and basically the same process for all (most?) mediatek chipped devices. MTK chipsets
also worth mentioning there is a pre rooted rom floating around, here on xda, i believe. cant recall the name of it off hand tho. however its a GSI rom (i think theyre called). my understanding is that GSI is like a one-sized-fits-all build method, where as long as the device meet preset criteria, the rom will run. that doesnt mean it will run well on every device tho, from what ive read. but, worst case scenario, its another avenue to consider.
Click to expand...
Click to collapse
Thanks. The Mediatek side of things is interesting as I have at least one Lenovo tablet that uses them and the Kindle Fire tablet I have also. Such a pain that manufacturers have went down the road of locking bootloaders the way they have. It used to be so easy to install ROMs. Oh well. C'est la vie.
Thanks for the info. I can't see me touching the Umidigi now for a couple of years. It would be more than my life's worth, lol. I'll copy the contents of your post for future reference.
Have a nice day. Hope you have success with your efforts and that your satellite connection improves.
I GOT ROOT !!
Sorry, I forgot to update this thread...
Bottom line is that there was a bug in magisk. It has since been repaired, and root procedure works 'as advertised' using magisk.zip v25.2 (25200)
After having no luck, I gave up. A few months later I tried again after reading about how magisk had a recent bug fix that sounded like it might have been the problem for this Umidigi. So, I grabbed a new build of magisk .zip, followed the tutorial, and it worked as expected. Pretty simple, once you have the resources ready. Not to mention, a windows 10 pc is all you need to get it done.
---------
My Metro by T-Mobile plan is no-cap-LTE, but doesn't have a hotspot allotment. I'm using a 'hotspot unlocker' magisk module to give me access to the hotspot. I believe it stops reporting hotspot activity back to the ISP, but I'm not sure. Regardless, I use a lot of hotspot data every month, but not a peep from the provider.
In conjunction with that, I'm running "VPN Hotspot" to tunnel hotspot traffic thru my phone's VPN connection. Otherwise, tethered data bypasses the VPN. The app is on play store and requires root.
I'm using the phones hotspot to serve data across to an old dd wrt router I have set as a repeater bridge. It runs a virtual wifi network, and other devices sign into that network. From there, behind the router, it operates as a normal home wifi network. Smart TVs, Chromecast, and all your tablet apps work as expected.
----------
I'm also running a few other modules, like viper audio. So far, so good. Really can't complain for a cheap device. It even gets decent battery life when serving data. About 10% per hour, avg running, but can go further if not running a VPN and close background apps .
---------
I'll look on the PC and see if I can compile a list of software, drivers, etc that were needed.