The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a Qualcomm SoC at their core. This includes the S10 and S20 series, the N10 and N20 series, the A10 - A70 series, the Tab A and Tab S series, Z Flip and (Z) Fold devices, and many more.
When flashed onto a compatible device, the multi-disabler will semi-permanently disable a number of device protection features and services that become problematic on a rooted device. Some pose a threat to the rooted state of the device, while others become dysfunctional and generate a flood of log messages. Semi-permanently in this context means that the disablement will persist until re-enabled by the user, for example as a side-effect of flashing new firmware with Odin. You will therefore need to reflash the multi-disabler every time you perform a system-wide firmware update.
The methodology of the multi-disabler is the path of least intervention. This means that for any given device, only those services that must be disabled to ensure the smooth operation of the device will be tackled.
The following is a list of features disabled by the multi-disabler on Samsung devices launched in 2019:
FBE (file-based encryption): Until this is disabled, most versions of TWRP — all for Exynos devices and many for Qualcomm — cannot read files on /data (the userdata partition). You must format /data to actually remove FBE after disabling it. Back up your data first!
Vaultkeeper: Magisk now dynamically disables this during boot, but if you boot outside of Magisk, it will return with a vengeance on some devices.
Process authentication (a.k.a. proca): This service must be disabled on some devices in order to use a custom kernel without problems. Note that all 2019 devices with TWRP utilise a custom kernel for Android, because the same kernel is shared by Magisk to boot the system. This does not apply to devices lauched in 2020 and later.
Stock recovery auto-restoration: In certain circumstances, your device will automatically restore its stock recovery partition, overwriting your custom recovery (TWRP). Magisk now also provides dynamic protection against this, but again, this will not save you if you boot outside of Magisk.
wsm: On Android 10 and 11, this service prevents Samsung smartwatches from connecting to the Galaxy Wearable app.
Extra services are disabled as needed per device.
Furthermore, when the ZIP file is renamed to contain the string _btfix somewhere in the name and the file is then flashed on a supported Android 10 device, the system's libbluetooth.so library will be patched in situ to prevent the loss of Bluetooth pairings across reboots. This is a recurring issue with many rooted Samsung devices manufactured before 2020 and updated to Android 10. Devices launched in 2020 and later do not need this patch.
The multi-disabler's support for this solution is limited to a relatively small number of Samsung devices and is deprecated as of v3.0. It will be removed in a future release.
If you find that patching fails on your device, please refer to Arthur Trouillot's superior libbluetooth patcher, which supports a much wider variety of devices.
The multi-disabler is written in Bourne shell, so you can — and ideally should — audit the code yourself to ensure its safe operation. It's performing open-heart surgery on the software of your device, so you should not simply trust it. Apart from anything else, bugs can creep in from time to time, despite or sometimes even because of my refactoring of the code.
The multi-disabler is idempotent, which means you can safely flash it multiple times without incurring unintended side-effects.
The package is attached to this posting and the code is available on GitHub.
Change log
v3.1 (2020-12-30)
Fix failure to detect a Samsung device on some versions of TWRP.
Make deprecated libbluetooth patching also work on devices originally launched on Android 9 and later updated to Android 11.
v3.0 (2020-12-29)
Add support for Android 11.
All Samsung devices running Android 9 or later are now implicitly supported.
Fix bug that caused disablement of stock recovery auto-reflash to fail on Android 10 devices.
Improve progress and error reporting.
v2.6 (2020-10-05)
Add support for the North American Z Fold2 (F916U/U1).
Add support for the A71 (A715F).
Add support for the Note10 Lite (N770F).
v2.5 (2020-09-14)
Fix issue of 2019 devices upgraded to OneUI 2.5 (DTH firmware) not booting after flashing.
Add failsafe logic for robust mounting of System partition by devices using very recent TWRP builds from the Android 10 branch (e.g. S20, N20, Tab S7 and Z Fold2).
Disable cass service on S10 and N10 series devices (required for OneUI 2.5).
Added an extra path to files searched for Vaultkeeper service disabling.
Added an extra path to files searched for cass service disabling.
Added support for the Z Fold2 (F916B/N and F9160).
v2.4 (2020-09-10)
Added support for many new 2020 devices, such as the S20 and Note20 ranges, as well as the Tab S7 and Tab S7+ ranges.
Fixed mode of patched Bluetooth library to match original.
Other minor bug fixes.
v2.3 (2020-04-11)
Support Snapdragon-based devices that have been upgraded to Android 10, such as the F900[FN] (Fold), F907[BN] (Fold 5G), T860 (Tab S6) and T865 (Tab S6 LTE), as well as Asian S10 and Note10 models.
Improve robustness of libbluetooth patching.
v2.2 (2019-12-13)
Disable wsm service to allow Samsung smartwatches to connect to Galaxy Wearable app (thanks to Andrei Seitan).
Support optional patching of system libbluetooth.so for retention of Bluetooth pairings across reboots (thanks to Arthur Trouillot).
Remove undocumented interactive mode.
v2.1 (2019-12-04)
Fix disabling of Vaultkeeper and proca in the vendor interface manifest.
Add support for N971N (Korean N10 5G).
v2.0 (2019-11-30)
Add support for Exynos-based devices upgraded to Android 10.
Add support for T72[05].
v1.7 (2019-10-20)
Add generic support for Qualcomm devices.
Support the Qualcomm S10 (G9700, G9730 and G9750), Note10 (N9700, N9750 and N9760), Tab S6 (T860 and T865) and Fold (F900F and F907B) ranges.
Add support for more Korean (N type) variants.
v1.6 (2019-09-18)
Add support for more variants of A50: A505([YG]N|G).
Fix A205G detection.
v1.5 (2019-09-13)
Added support for A10 - A50 and Tab A 10.1.
v1.41 (2019-08-28)
Added support for N976B (Note 10+ 5G).
v1.4 (2019-08-28)
Changed regex that caused too much of $ANDROID_ROOT/init.rc to be commented out by some versions of sed(1).
v1.3 (2019-08-18)
Updated to work with TWRP 3.3.1-6_ianmacd and later for the S10 range.
Added support for Note 10 and Note 10+ F and N model devices.
v1.2 (2019-06-17)
Added support for G977B (S10 5G) model devices.
v1.1 (2019-04-22)
Fixed stock recovery auto-reflash prevention.
Added support for N (Korean) model S10 devices.
v1.0 (2019-04-09)
Initial version, supporting F model S10 devices.
Will this in some way remedy the problem that when powering off the S10, it wont listen to they keycombo to boot into TWRP anymore?
If one is in system, and do a reboot all is fine, it will heed the keycombo and let you into TWRP to do what you want and then reboot->recovery to start system with root.
But as soon as the device is turned completely off, it breaks.
Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
cheers
Nextasy said:
Just a question: is this to be flashed after rooting with johnwu magisk root process or which rooting method would u advice?
Click to expand...
Click to collapse
If rooting with Magisk alone and in accordance with John Wu's instructions, this disabler isn't needed. If you're going to use a rooted TWRP image instead of stock recovery, however, then you're probably going to want to flash it.
So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Thanks for ur time to reply and the mod.
cheers
does the disabler in the twrp thread also need to be applied? or does this replace it?
Nextasy said:
So this basically would work for and with the "TWRP for Galaxy S10 Magisk Prepatched by geiti94" and not with John's!?...
After applying this patch and everytime l reboot my devoce it will reboot directly to rooted magisk environment without me going thru' the hassles associated with Johnwu magisk boot procedures?
Click to expand...
Click to collapse
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.
tensux said:
does the disabler in the twrp thread also need to be applied? or does this replace it?
Click to expand...
Click to collapse
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.
ianmacd said:
This one effectively supersedes the one in the TWRP thread, because that one disables only FBE encryption, while this disables several other things.
Click to expand...
Click to collapse
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot
tensux said:
thanks, i am going to try it again. i have been able to get into twrp on the first try, but it always reboots after the Samsung logo comes up and it looks like its going to boot
Click to expand...
Click to collapse
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
ianmacd said:
No, this disabler has no effect on the need to hold down keys to boot the recovery partition.
Click to expand...
Click to collapse
Thanks. But l can flash it after rooting with "TWRP for Galaxy S10 Magisk Prepatched by geiti94"?
dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
seems like only a very small amount of people have been able to get it to work. the procedures are more complicated than with past phones, but i wonder if there could be a very specific version of bootloader we need to have flashed, not just any of the ASCA's
dr4go said:
Same here... twrp+multi disabler+format data+wipe cache+soldier's zip (in that order). Everything was fine until I pressed power off. Needed to go all over again... and am wondering if it really pays off of having twrp......
Click to expand...
Click to collapse
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.
PiCkLeS said:
And, really, I think at this point that ppl saying it working for them actuallly never tried a true power down.
I still think therefore that all have the same problem. If you shutdown your phone manually or run out of battery, you are screwed.
Click to expand...
Click to collapse
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.
drago122 said:
What I didn't understand is what happens once you turn off the phone ?? Brick unrecoverable ??
Or it must be redone all starting from download mode and stock firmware, what interests me to know is only if the phone is easily recoverable or you risk big.
Click to expand...
Click to collapse
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.
PiCkLeS said:
What I mean is that few ppl actually turn off their phones. But if they do they are stuck with no way to boot system at all or able to boot into twrp recovery .
Most just reboot and there the keycombo works fine.
So if you have the twrp solution done, and power down your phone (off, not reboot) yes you probably must start over from the beginning.
Click to expand...
Click to collapse
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?
drago122 said:
Ok but you don't risk a hard brick, you have to start again from the download mode and the stock firmware must be put back and then everything else, correct?
Click to expand...
Click to collapse
Yes.
PiCkLeS said:
Yes.
Click to expand...
Click to collapse
Thank you for the clarifications
drago122 said:
Thsnk you for the clarifications
Click to expand...
Click to collapse
You are welcome
Related
If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.
famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?
famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.
Official updates for our M2 tablet,
although having installed another
recovery and root access, already.
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.
+++ saved +++
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
what android version ?? M2-801L, thanks
Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031
xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.
Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs
thanx
Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!
Problem: Unable to install TWRP via ODIN. I try to flash the device with the twrp-3.1.1-0-picassowifi.img.tar using ODIN, I get the following errors during the boot recovery step Home+VolUP+Power:
Could not do normal boot.
ODIN Mode
Product name: SM-T525
Current binary: Custom
System status: Custom
Knox Kernel Lock: 0x0
Knox warranty VOID: 0x1
Qualcomm Secureboot: Enabled (CSB)
AP SWREV: S1, T1, R1, A1, P1
Write protection: Enable
UDC Start
I am able to reinstall KitKat back to its original state using ODIN each time which helps alot.
The tablet was in the following state prior to the TWRP installation:
I did a factory reset back to original Kitkat version 4.4.2
Samsung account: No
Google account: Yes
Installation Preparation Steps
Downloaded following files:
LineageOS 14.1,
open_gapps-arm-7.1-nano-20201223
ODIN v3.14.4
Samsung USB Drivers v1.7.31.0
Auto-Root-picassolte-picassoltexx-smt525
twrp-3.1.1-0-picassowifi.img.tar
Installation Steps:
Tested if recovery mode is working prior to installing twrp: Done Successful
Installed USB drivers on your PC
USB Debugging was enabled on device by pressing build number 7 times in settings
Developer options: Activated USB Debugging
Disabled bootloader: not done (not sure how to do it and if it is required)
Rooted device via ODIN: Done successfully (Auto Reboot and F. Reset Time flags checked)
Disabled KNOX via SuperSU
Tested if recovery mode is still working after root: Done Successful
Installed TWRP image via ODIN: Status PASS (Auto Reboot flag unchecked, F. Reset Time flag checked)
Booted into TWRP Recovery using HOME+ Vol UP + Power button
The last step is where the error occurs and TWRP recovery mode did not start.
I tried multiple versions of TWRP, but all attempts failed.
I installed TWRP via play store on the tablet and selected the .img file for my device via the TWRP tool. Although the tool was able to flash the device (stated that the flash was successful within the tool), when I try to enter device recovery mode, I get the same error: Could not do normal boot.
Any idea what could be wrong? Am I missing a step, permission issue?
I would appreciate any hint
thx
Sal
Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.
bmwdroid said:
Isn't the T525 the picassolte?
Seems to me you're using the wrong TWRP.
Click to expand...
Click to collapse
There are 2 types of T525, wifi and lte. I have the wifi version.
Sal60 said:
There are 2 types of T525, wifi and lte. I have the wifi version.
Click to expand...
Click to collapse
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?
bmwdroid said:
Well, if you say so.
But I think you're wrong.
wifi=t520 lte=t525
And why did you use Auto-root for lte?
Click to expand...
Click to collapse
Thanks for the help. Before I reached out to you, I tried my best to gather all the info to upgrade to LineageOS. Rooting the device was one of the steps. I got the file for t525. I did not think about wifi or LTE. I see now that it makes a big difference.....thx. I'm rather new to the rooting and upgrading a device approach.
Strange, I doubled checked the package. It doesn't say anywhere about LTE - only wifi. But I checked the imei on imei.info and noticed that it is a LTE model. I bought the tab in 2014 and I guess I bought the lte model. This explains alot.
I will try the lte version of twrp.
thx again
I tried the lte version of twrp and I was able to enter into recovery mode. Thanks for the excellent tip.
I guess I need to do more homework on twrp and the whole process. I also got lucky on using the right root file. Because I almost made a huge mistake with rooting, I think I need to take a step back and do more research. I want to make sure that I have a complete image of my tablet just in case I take a wrong turn. I believe twrp is the right tool to do that. Any suggestions on the steps which I need to do?
Initially when I first started to gather all the info and dowloaded the files, I also downloaded lineage-14.1-20201218-UNOFFICIAL-n2awifi.zip. It appears that this file is also for the wifi model. Is there a difference between wifi and lte for lineageos 14.1?
@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.
bmwdroid said:
@Sal60 so we finally figured out what you really got .
The saving process is very easy in TWRP just use backup option and save EFS, Boot, System and Data.
Although the last three can easily be restored by flashing stock ROM via Odin.
DON'T flash any ROM which is not specifically designed for your model as danger of bricking will be increased by doing so.
Click to expand...
Click to collapse
Awsome, I backed up everything. I will need to do more research on the right ROM. Using the wifi version I downloaded of the Samsung Galaxy Tab Pro 10.1 is probably not the best way to go.
I see that LineageOS.org does not support my tab as of now and CyanogenMod no longer exist. Do you know of any other projects which might support my tablet?
@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.
bmwdroid said:
@Sal60 as I don't own any T52* I've no idea what's going on in ROM development.
Click to expand...
Click to collapse
Thanks anyway
Sal60 said:
Thanks anyway
Click to expand...
Click to collapse
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button
bmwdroid said:
What about this one here:
[ROM][T525][UNOFFICIAL] LineageOS 16.0 | Android 9.0 Pie 20200229
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Btw. I wouldn't mind, if you find and hit the "like" button
Click to expand...
Click to collapse
@bmwdroid: thanks for the link. I will review the url. I completely understand the risk part. I rarely use my very expensive tab anymore because it is so old and more or less useless. Most apps do not work anymore. Samsung stopped updating the tab shortly after it was released.
Sorry about not hitting the like button.
I will update the post with the results after I do some research on the file.
Thanks.
@Sal60 I condemn Samsung for their update strategy as well.
That's why I will never ever again by a new device from them.
All my stuff is older than four years and on custom ROMs either on Nougat or even Q.
I bought them only after searching here for active devolopers.
@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
bmwdroid said:
@Sal60 the brilliant dev @Valera1978 brought out as a Christmas gift :
[ROM][T525][UNOFFICIAL] LineageOS 18.1 | Android 11 | 20210509
I'm not responsible for any damage to your device of any sort. By flashing this you take responsibility of anything that happens. Process at your own risk! If you want to check firmware - please make backup. Better to store all partitions, at...
forum.xda-developers.com
Click to expand...
Click to collapse
@bmwdroid I just seen this newly created ROM as well...thx. I checked both URLs. It seems a little complex. My only concern is understanding the technical side of the installations. I guess I have my work cut out for me.
Hi everyone,
I really need device encryption in order to be able to use my tablet with a work profile.
Has anyone ever done this with this device?
I have tried with LOS 17.1 and 14.1 by @davidmueller13 but unfortunately it reboots, then tells me it is encrypting (with the pending time displayed) and after that reboots again. I am then prompted to put in my pin (which I set before of course) and after that it is just stuck at the bootscreen / LOS logo for hours.
Any help is greatly appreciated.
With the P605 and various other older devices w/o encryption by default and a custom rom, all my attempts ended with bricking the device...
There may also be a significant performance penalty, the older the device.
lecorbusier said:
With the P605 and various other older devices w/o encryption by default and a custom rom, all my attempts ended with bricking the device...
There may also be a significant performance penalty, the older the device.
Click to expand...
Click to collapse
with LOS 16 I got it to work
Thanks a lot!!! I am gonna give it a try.
Alright @Tronje , thanks to your advice I have a working encrypted device.
Unfortunately the system patch level it too old. I cannot set up the working profile due to that.
Any further advice?
I am no software expert, but I do not get why in LOS16 this feature works flawlessly while in the other builds it is not supported.
MaKel89 said:
Alright @Tronje , thanks to your advice I have a working encrypted device.
Unfortunately the system patch level it too old. I cannot set up the working profile due to that.
Any further advice?
I am no software expert, but I do not get why in LOS16 this feature works flawlessly while in the other builds it is not supported.
Click to expand...
Click to collapse
I am also only a user and cannot explain, sorry.
With maas360 In my company everxthing is good for the moment.
I think you have to ask the developer/ maintainer.
Alright, I am one step closer to what I am looking for.
I have managed to encrpyt LOS 14 by reducing my filesystem size via TWRP Terminal in order to gain some space for the crypto footer.
LOS14 has a security patch level sufficient for setting up with Microsoft Intune. Nevertheless, even though my tab is not rooted, Microsoft Intune somehow detects root. Any bright ideas on why that is happening?
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Says "everyone" but then leaves out RM6R
Gunhawk32 said:
Says "everyone" but then leaves out RM6R
Click to expand...
Click to collapse
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
I did a completely clean update. I completely formatted it, deleted all partitions /even the "persist" by accident, but I managed to restore it, but that's another story/.
Then I reset the phone using the Mitool-EDL method and then updated the clean system to EUCommon-V5.10.
The only mistake is that it lists the battery as 3550 mah instead of 5050 mah.
What you write about not receiving calls on Wi-Fi, etc., also occurred to me on the V3.28 system. If I set the mobile network as preferred in the vowifi settings, the error disappeared. Now I haven't experienced this error, vowifi works normally even in wifi preferred mode.
So far, I have not experienced any errors apart from the incorrect listing of the battery, although I cannot test 5G because it is not yet installed at our place...:/
Pisti870923 said:
Sorry, by everyone I meant not only those who are sent OTA. Android 12 has already been released for the 6R in China, so I think it will arrive soon for the 6R as well. :/
Click to expand...
Click to collapse
I doubt it since it took 7-9 months for the android 12 update to release globally for the RM6 & 6 pro after it came out in china.
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
bro i have the same issue
do you solve it
Please i
Pisti870923 said:
Hi guys!
Here's a little trick, if someone might not get the Android 12 OTA update: the update is already on the official website, but for some reason the interface wasn't edited, or I don't know... So, if you rewrite the version number in the download link, the download will start. XD
EU: https://rom.download.nubia.com/Europe/NX669J/V510/NX669J-update.zip
North America & Asia: https://rom.download.nubia.com/Europe&Asia/NX669J/V610/NX669J-update.zip
I completely reset the phone before that, with Mitool, in EDL mode. Everything works, 5Ghz Wifi, Volte, etc., so far I have not experienced any errors. The interface looks smoother, but that might just be because of the clean phone. I like the new Gamespace much better. If you don't like it or if you find errors, you can use the Mitool-EDL method to revert to any previous version.
Click to expand...
Click to collapse
do you have instructions or video .i dont have experience with that
moatazamer83 said:
do you have instructions or video .i dont have experience with that
Click to expand...
Click to collapse
I'll describe how I did it, but I can't promise that everything will work the same way for everyone. I don't know if there are hardware differences between each phone because I could only test it with mine /RM6P/. If someone tries it, do it at your own risk!
Be sure to save the "persist" partition before doing anything!!! Also save Qcn, these two are very important!!!
1. Backup partitions:
2. Backup Qcn:
3. /Optional/ Erase ALL:
After backup, I entered the partition manager in qfil, and after right-clicking, I clicked on "erase entire flash". But it's not absolutely necessary, but I definitely wanted a clean install. When I returned from Chinese Android 12 to EU 11 and didn't do this, the first time I started it, the phone setup got stuck in the wizard and wouldn't let me continue. From this I realized that the Mitool-EDL method alone does not completely clean the phone.
If you have completely reformatted the phone with qfil, you will need to restore the "persist" partition and Qcn with qfil after Mitool is finished. If you haven't formatted it completely, you don't need to restore it, but you should still have a backup of them, you never know when you'll need them, believe me!
4. And here is the description of the much talked about Mitool-EDL method:
RM6/6Pro Unbrick Tool - EDL Flash / Switch from CN to EU
Hello guys, I received the following unbrick tool from my supplier in Shenzhen - China and wanted to share it with you since I noticed that many people are desperate to fix their RM6 and swap it to EU. The process is super easy: 1) Download &...
forum.xda-developers.com
5. Update rom:
If you're done with Mitool, you download the ROM you want, copy it to the internal storage and install it with local update in system update!
I did it this way and still found no errors. (Except that it says the battery is 3550mah). I use the EU510.
After Mitool finished, any rom goes up with local update, I tried EU328, UN428, CN810, UN610 and EU510
This method did not require unlocking the bootloader.
According to my theory, I could root with qfil without opening the bootloader, but I haven't tested it yet. If I try it sometime, I will write about my experience.
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Pisti870923 said:
Two more things:
1: The Firehose file is in the "image" folder of the Mitool pack, it is also needed for Qfil.
2: If someone wants to enter EDL mode from Fastboot after updating to Android 12, the phone will restart immediately. You have to make an Edl cable from a USB data cable, or buy one and use it to enter Edl mode.
It actually seems complicated, but the point is that the black/GND/ and green/data+/ wires have to be touched together while plugging the cable into the phone, and then after a few seconds they have to be separated from each other. The switched-off phone will thus immediately switch to Edl mode.
Click to expand...
Click to collapse
oh my god i can't do it bro
but thx alot for your help should i wait fix from company
moatazamer83 said:
bro i have the same issue
do you solve it
Please i
Click to expand...
Click to collapse
Bro me to i don't have network for calling before it wasn't a probleem but android 12 is smooth tho sad Nubia has to present it like this
An Droid said:
The update was pulled from OTA due to bugs - some users experienced boot loops that required full reset (you did that anyhow).
In my case, I've had cellular network issues where it appears the device disconnects from the network when on WiFi - phone calls are no longer received and legacy SMS/MMS won't send/receive until WiFi is disabled or the SIM is toggled off/on.
An update is apparently on its way, but it's been over 3 weeks now.
Click to expand...
Click to collapse
Bro i got same network problem it's really sad Nubia has to present android 12 like this tho do you know something more
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
thx bro i will wait for your feedback .should i reset before installing
An Droid said:
There's a new update on the Nubia download site for the RM6 - this is Android 12:
USE AT YOUR OWN RISK!!!
North America - v.6.12
https://rom.download.nubia.com/Europe%26Asia/NX669J/V612/NX669J-update.zip
Europe - v.5.12:
https://rom.download.nubia.com/Europe/NX669J/V512/NX669J-update.zip
I've installed v.6.12 on my NA RM6 and all is well so far. Cellular issues seem better if not resolved - need more time to confirm.
Click to expand...
Click to collapse
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
moatazamer83 said:
thx bro i will wait for your feedback .should i reset before installing
Click to expand...
Click to collapse
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
I've installed it too the network problem seems to be fixed but I need time to to confirm if this is solved
Pisti870923 said:
3.28/4.28 is still the last available version on the official website. The only problem with this trick of rewriting the version number in the download link is that we don't know what was fixed in each version...:/
Click to expand...
Click to collapse
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
An Droid said:
Once installed, you can pull up the changelog (if there is one!).
This is from v.6.12:
Click to expand...
Click to collapse
I have EU version the changelog is the same as v.5.10 idk why
I think only if you get it with an OTA update... This is what I see: