Disclaimer/Requirements:
>> Only run on unlocked bootloader <<
>> TWRP 3.0 patched by st0rm77 as recovery <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Watch the video
Hi,
I wrote a simple Ubuntu-Touch installer for the Meizu Pro 5. Its been tested on OTA-12 and OTA-13
but will probably work for any future version unless they change something.
Make sure you have the TWRP_3.0_m86_patched_st0rm77 recovery installed.
Only this version will backup the bootlogo and device tree.
Steps to install:
1. Make a backup of your device <-- ALWAYS
- select backup from TWRP
2. Install ubuntu-device-flash
# sudo apt-get install ubuntu-device-flash
# ubuntu-device-flash --download-only touch --device=turbo --channel=ubuntu-touch/stable/meizu-pd.en
(For Windows,Mac and lazy people: Ubuntu-Touch OTA-12 & Ubuntu-Touch OTA-13)
3. Open the folder ~/.cache/ubuntuimages and copy the following files onto your internal storage or sdcard:
- version-*.xz, custom-*.xz, device-*.xz and ubuntu-*.xz
- ubuntu-touch-installer*.zip (attached to this post)
4. Start your device in TWRP and wipe your device
- select wipe > advanced wipe
- select Dalvik/Art, Cache, System, Data and >>swipe to wipe<<
5. Install Ubuntu-Touch
- select install
- select ubuntu-touch-installer*.zip.
Wait until the installer finishes and reboot your device
Enjoy
Does OTA work ?
Really nice and wonderful job !!! :good:
Let me ask some details :
* there're some apps to try in ubuntu ?! 'cause if I remember well, one of the big obstacle of ubuntu phone was the lack of apps / programs to install in the system...
* once done this procedure, TWRP Recovery ( your version, in this case ), will remain ?! Or it's been overwritten / disappeared ?! :crying:
* In above case, imaging that TWRP is still present, what's the procedure to go back to an Android system ( Flyme e.g. or RR or whatever ) ?
:highfive:
Benni009 said:
Does OTA work ?
Click to expand...
Click to collapse
Yes, but not until you flash the Ubuntu recovery manually.
Extract /partitions/recovery from the device-*.xz
Flash this to recovery via fastboot.
PYCON said:
Really nice and wonderful job !!! :good:
Let me ask some details :
* there're some apps to try in ubuntu ?! 'cause if I remember well, one of the big obstacle of ubuntu phone was the lack of apps / programs to install in the system...
Click to expand...
Click to collapse
Look in the Ubuntu store, lets say its somewhat limited.
PYCON said:
* once done this procedure, TWRP Recovery ( your version, in this case ), will remain ?! Or it's been overwritten / disappeared ?! :crying:
Click to expand...
Click to collapse
TWRP remains, it does not touch recovery at all.
PYCON said:
* In above case, imaging that TWRP is still present, what's the procedure to go back to an Android system ( Flyme e.g. or RR or whatever ) ?
:highfive:
Click to expand...
Click to collapse
Backup you current state (flyme/aicp/cm/rr).
Install Ubuntu
If you do not like it, reboot into TWRP and restore from backup.
Just follow the instructions in post 1.
st0rm77 said:
* Look in the Ubuntu store, lets say its somewhat limited.
* TWRP remains, it does not touch recovery at all.
* Backup you current state (flyme/aicp/cm/rr). Install Ubuntu. If you do not like it, reboot into TWRP and restore from backup. Just follow the instructions in post 1.
Click to expand...
Click to collapse
* Ok, nice... I'll try to look for some apps like them I'm using
* Nice ! It's the most important thing :silly:
* Ya, I've asked to u this 'cause for example, when I want to delete CM13 ( RR ) and return to Flyme, I cannot simply restore the nandroid of previous Flyme' based rom I've to flash a Flyme rom FIRST and only then I'll be able to restore the nandroid
PYCON said:
* Ya, I've asked to u this 'cause for example, when I want to delete CM13 ( RR ) and return to Flyme, I cannot simply restore the nandroid of previous Flyme' based rom I've to flash a Flyme rom FIRST and only then I'll be able to restore the nandroid
Click to expand...
Click to collapse
...... i wonder if that could be the reason why i patched the recovery ?
I think it is
And you know what the beauty is of this ?
You can now do it too :laugh:
(no more reflashing of flyme, just backup/restore in twrp)
st0rm77 said:
...... i wonder if that could be the reason why i patched the recovery ?
I think it is
And you know what the beauty is of this ?
You can now do it too :laugh:
(no more reflashing of flyme, just backup/restore in twrp)
Click to expand...
Click to collapse
U'r a genius man, thank u very much ! :highfive:
st0rm77 said:
Yes, but not until you flash the Ubuntu recovery manually.
Extract /partitions/recovery from the device-*.xz
Flash this to recovery via fastboot.
Click to expand...
Click to collapse
Done. Thanks man. Nice work =) It's not simple to get from chinese-version with former owner logged in to pro5 ubuntu OTA 13 =) You made it easier.
Lets wait for OTA 14
Benni009 said:
Done. Thanks man. Nice work =) It's not simple to get from chinese-version with former owner logged in to pro5 ubuntu OTA 13 =) You made it easier.
Lets wait for OTA 14
Click to expand...
Click to collapse
So you cant get root ? I have something that might work, but its early stage and you might be the perfect person to test this.
PM me
good job
Sent from my PRO 5 using XDA-Developers mobile app
st0rm77 said:
So you cant get root ? I have something that might work, but its early stage and you might be the perfect person to test this.
PM me
Click to expand...
Click to collapse
Sry for my late answer. Today I tried to upgrade to OTA 14 but the update was not downloaded nor installed. Do you have successfully updated to OTA 14?
BTW: Yes I think I get root with the flyme account
Edit: It seems the OTA-Update to OTA-14 works fine. It only takes a while
i was trying to mess around with this along side with multirom from faust, after some problem i actually thought it was going to work, but after installing the zip i get an error " ! failed, verify error on bootlogo " and even tho the installation conclude it doesn't boot afterward, any clue on how to fix this?
Video??
Flashing bootlogo error. On TWRP 3.0. Tryed on OTA 12 and OTA 13
anyone successful with this guide?
hello, I tried it in ubuntu touch of Canonical and it works, also with the ubuntu 15.04 but it does not work with the 16.04
Any thing new?
I know its been a while but I'm still using my Meizu Pro5. It was an Ubuntu edition. I've been using A custom rom for a couple of yrs now. I'm ready to go back to Ubuntu because there hasn't been any updates from the Rom creators for a couple yrs now and I want to keep the phone updated. so I followed this process but upon install phone says
" could not find 'META-INF/com/google/android/update binary' "
and after reboot wont move past white "Meizu Powered by ubuntu" screen...I did get it back to recovery. So If at all possible is there something that I can do? I'm trying to install the new Ubuntu touch on my phone but it wouldn't proceed with out an older version running on the phone...
TamashiiTora said:
I know its been a while but I'm still using my Meizu Pro5. It was an Ubuntu edition. I've been using A custom rom for a couple of yrs now. I'm ready to go back to Ubuntu because there hasn't been any updates from the Rom creators for a couple yrs now and I want to keep the phone updated. so I followed this process but upon install phone says
" could not find 'META-INF/com/google/android/update binary' "
and after reboot wont move past white "Meizu Powered by ubuntu" screen...I did get it back to recovery. So If at all possible is there something that I can do? I'm trying to install the new Ubuntu touch on my phone but it wouldn't proceed with out an older version running on the phone...
Click to expand...
Click to collapse
Get OTA update with this TWRP BACKUP.
My device updated with OTA-14
Related
Hello All,
NOTE: You should unlock your bootloader.
These are patched TWRP recovery images for the Apollo and Thor devices only. Now Built from the latest .4.5.3 sources.
WARNING:
- Be sure to have a working /system partition before proceeding with installation.
Installation
- Ensure you are running stock firmware .3.2.3.2
- Obtain Root
- Copy the recovery image to the root of your sdcard
- Flash the recovery image by issuing the following commands:
Code:
adb shell
su
dd if=/sdcard/signed-<device>-twrp-2870.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Download
- Apollo Recovery Image
- Thor Recovery Image
Thanks
- @vortox for the exploit
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
r3pwn said:
I see that everyone (well, almost) is using his exploit now. Is there a tool and/or link that I missed?
Click to expand...
Click to collapse
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
vortox said:
I gave @Cpasjuste and @ggow an earlier access to my tool, because I could't write my guide as fast as thought.
Click to expand...
Click to collapse
Ah.
I wrote the recovery on my apollo device which is running 14.3.2.3.2_user_323001720 version and it appears to work flawlessly. I booted into recovery (TWRP) successfully and rebooted the system successfully as well. Awesome!
Thanks for the feedback, glad it's all working
I haven't got a device at the moment to try it out on.
Sent from my Kindle Fire HDX using Tapatalk
Thanks ggow. Could we expect CM roms soon from your new release?
Working on 14.3.1.0
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
Hello tuanda82,
It depends on Amazon, my unlocked Apollo stopped working so they sent me a new one but came pre-installed with 4.5.2.
They have refused to downgrade me back to the old firmware. And after a lot of to and fro they agreed to replace it again .
I hope I have luck with the new device been on the required firmware.
But yes I definitely would like to make such a release.
dangerous
jeryll said:
I just want to confirm, on 14.3.1.0_user_310078820 everything so far is working correctly, I can enter into TWRP, reboot system aswell, successfully tested backup and restore (from Safestrap created backups)
Thanks.
Click to expand...
Click to collapse
I would not be trying interchang eROMs and or backups ppluntil certain things are verified by our developersgosh it only takes a few minutes to understand that one is built for locked bootloader the other one bypasses and they both flash completely different partitions and have different installation scripts.you're just asking to be one of the ignorant whiners on the sidelines while we have fun ..stuck with your brick. be patient guys this is all new stuff if you can't afford to be a developer then I devise you let somebody else take the risk
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
tbm13 said:
Can you tell me where TWRP Recovery is stored and what the boot process is like? Is TWRP called by the boot loader instead of the Linux kernel and it will in turn then start the Linux kernel from your installed system?
What happens when TWRP Recovery is damaged? Is there still a way to recover?
And is there a difference in how TWRP is started as opposed to Safestrap?
Edit: ok, so I see that TWRP Recovery is flashed to the recovery partition, so I guess it's separate from the boot image. And pressing volume up + the power button presumably activates the recovery image rather than the boot image. Did Safestrap work in the fashion I described? Why are we using TWRP for recovery now instead of Safestrap? Are there any advantages?
Click to expand...
Click to collapse
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
r3pwn said:
New recovery system
- Allows for custom kernels (meaning, CyanogenMod, Overclocking, and other things)
- Installed to "recovery" partition
- Bypasses signature verification check with some weird thing about exponents of 3 and the cubed root of something. I don't entirely understand how the exploit works.
- Called from the bootloader
- If you're in a bootloop, hold VOL+ & POWER (I think) to boot into TWRP.
SafeStrap
- No custom kernels (no CM)
- Installed to "system" partition (no key presses can get you to here if you're in a bootloop)
- Designed to provide semi-custom ROMs on devices with locked bootloaders
- Called from the Kernel
Click to expand...
Click to collapse
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Håvi said:
Do you have to be in the stock rom slot to install? Or can you be on a custom rom slot and install?
Click to expand...
Click to collapse
Flash the rollback image to stock slot. This will then enable you to get back to 3.1.0
ggow said:
Flash the rollback image to stock slot. You need to be on stock version < 3.2.4.[/QUOT
Edit, found answer in OP
Click to expand...
Click to collapse
I was able to roll back to 3.1.0 and installed twrp. I was able to make a backup and successfully restored the backup. However after about an hour I came back to my kindle an noticed it updated itself to 4.1.1. I was under the impression with recovery installed any new updates would . Not be able to install. Now when I try to boot into recovery it on l y boots kindle recovery not twrp.
Sent from my KFAPWI using Tapatalk
tuanda82 said:
Thanks ggow. Could we expect CM roms soon from your new release?
Click to expand...
Click to collapse
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Cpasjuste said:
The main problem for cm on appolo seems to be the kernel/bootloader. To run CM kernel (or amazon > 3.2.4) we need (or at least its the only way I found) to modifiy the boot image to manually happen the DT information's to the kernel zImage. Unfortunately this was tested with @ggow and it's not working on appolo. If someone if willing to send me an appolo device I could work on that ...
Click to expand...
Click to collapse
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
GSLEON3 said:
Man, I wish I had more time for XDA. First time I've checked in in months. At any rate, it is awesome to see y'all learning & sticking with it! Since I haven't had much time for anything that isn't work related lately, I passed my rooted 3.2.6 Apollo to my Mom. I don't know if she uses it much, but I'll ask her & unless she did a complete 180 & is now becoming a tablet-phile, I could probably send you mine. I will ask her if I can have it back tonight & let you know.
Click to expand...
Click to collapse
Thanks gsleon but don't rob your mom
---------- Post added at 10:57 AM ---------- Previous post was at 10:53 AM ----------
ggow said:
Amazon are sending me a new Apollo device (again)... hopefully I'll be back in business soon. I think there was something wrong with my device which is why I was having so many problems.
When I get the new device, hopefully it will be on the required firmware for me to try out the new kernel and CM. I'll report back when I have something... Shouldn't take me too long to get something up and running once I have a working device.
Click to expand...
Click to collapse
Crossing fingers
** BRICK WARNING/Disclaimer/Requirements **
>> Only flash with unlocked bootloader <<
>> Scripts are released under GPlv2 license <<
>> Run at own risk <<
Hi,
I patched the TWRP 3.0 recovery from faust93 to include important partitions
that make switching between different versions of Android/Ubuntu very simple.
All partitions are properly added to the fstab, but out of fear that some of
you will brick your device i disabled most of them.
Next version will contain a backup of all unique partitions, but i will have
to test this thoroughly.
Steps to install:
1. Download the zip file from attachments below
2. Unpack the zip file
3. Check checksum with md5sum -c *.md5
4. Put phone into fastboot mode (boot device with [vol-] and [power] button)
5. Flash recovery with:
# fastboot flash recovery TWRP_3.0_m86_patched_st0rm77.img
# fastboot reboot
then boot the device with [vol+] and [power] button, to enter recovery
[Requested by @p82maarj]
Already on an older TWRP version ?
- Flash "update_TWRP_3.0_m86_patched_st0rm77.zip" from TWRP
or
- Unpack the zip and flash the recovery manually in TWRP by selecting "install image"
Enjoy
Warning:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Hi @st0rm77
Thanks for your contrubution!
It will be good if you create a flashable zip of your new recovery. It can be flashed directly from the stock recovery or from the other twrp recovery without entering in fastboot.
Furthermore to have a flashable zip is usefull to flash a new rom update. For updating the new rom version I enter in TWRP, flash rom zip, flash unlocked bootloader zip and flash TWRP zip.
I attach the other flashable TWRP zip you can based on (only replace recovery.img by your recovery.img).
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
PYCON said:
Personally I like android as OS, I don't wish to try Ubuntu, in my case it's useful to update my "old" TWRP by Faust93 with this one ?
Click to expand...
Click to collapse
Yeah, you get some extra abilities:
- Backup of Boot Logo
- Backup of Device Tree
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Thanks for everything you've been releasing, great work!
st0rm77 said:
Hi @p82maarj,
Thanks, as per your request, i added an update_TWRP_3.0_m86_patched_st0rm77.zip . This is directly flashable from an older TWRP.
I added some extra verification so people dont end up with a corrupt recovery.
Enjoy
(in order not to confuse people to much, can you remove your download)
Click to expand...
Click to collapse
Done Thanks!
st0rm77 said:
** If you flash an official update.zip from Flyme, remove bootloader, ldfw & recovery from ZIP**
** Otherwise you'll find yourself with a locked bootloader **
Click to expand...
Click to collapse
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
PYCON said:
Another little question... What's the difference from 2 ZIP files ? Older one and updated ZIP ?
Click to expand...
Click to collapse
I know the answer to this one!
The first zip contains the img file that you can flash using fastboot.
The second (update) zip is the one you need if you already have (an older) TWRP and you wish to update to this version (use it from inside TWRP).
abePdIta said:
Sorry for the stupid question but it's just to be sure. I should remove the file named "bootloader" or the one named "boot.img"? Or both of them?
Thank you very much!
Click to expand...
Click to collapse
boot.img is your boot partition, you need this one :good: (NEEDED)
bootloader is the locked bootloader from meizu, avoid this one as the plague (AVOID)
Dont brick your device, check everything carefully :fingers-crossed:
st0rm77 said:
Dont brick your device, check everything carefully :fingers-crossed:
Click to expand...
Click to collapse
Thank you very much! I will be careful in the future, I promise!
i follow the a to I tutorial
then unlock bootloader
then this
now when i conect meizu to pc i try to pass custom rom to internal memory and the phone restart
what is the problem
---------- Post added at 10:35 PM ---------- Previous post was at 09:56 PM ----------
managed to download the rom in phone browser now i have RR and all it´s ok
I flash stock recovery ( use update 5.1.10.0g) but not success, hÃc hÃc, help me restore stock recovery, many thanks!!!!
st0rm77 said:
Now you can backup/restore in TWRP without manually flashing dtb (device tree) in order to switch between Flyme, AICP, ResurrectionRemix or Ubuntu.
Click to expand...
Click to collapse
Just to be sure I understood :
Going from Flyme to CM :
-Backup Flyme (system+data+dtd)
-Flash CM archive
Going back to Flyme
-(optional) Backup CM (system+data+dtd)
-Restore Flyme (system+data+dtd)
Is there is a quikier way ?
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
help
hi .i change meizu pro 5 from china to national (5.6.1.19 daily )and unlock it and flash recover TWRP 3.0 but not login it the recovery .
i want updated
PYCON said:
TWRP 3.1.0.0 is out... It's possible to port it for our PRO5 ?! :silly:
Click to expand...
Click to collapse
I too vote for a port!
3.1.1 was released
munky-head said:
3.1.1 was released
Click to expand...
Click to collapse
Not for PRO5
Okay, managed to get Nougat and root for my BTV-DL09. Here is a fast forward tutorial how to do that.
I could only root it by using Magisk, Supersu (even the special emui5 ones) did not work for me.
Files:
ROM: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v78425/f1/full/update.zip (BTV-DL09C233B336)
Data: http://update.hicloud.com:8180/TDS/...full/dualcu/cn/update_data_full_dualcu_cn.zip
TWRP, make sure to use twrp_BTV-DL09_5_greatslon.img : https://androidfilehost.com/?fid=817550096634750327 (thanks to greatslon)
Root: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I came from version BTV-DL09C100B006, this is how I did it:
Bootloader must be unlocked, custom recovery installed (Do not install the one for EMUI5 yet, it won't boot).
Enter recovery by adb reboot recovery
Wipe, reboot recovery
Flash ROM + Data
Flash Magisk Root
Flash Recovery again (will be overwritten by the udate)
Reboot, Done.
Download playstore / vending APK from APKmirror: http://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-7-6-08-release/ and transfer it on the device.
There is an app called "Downloads" preinstalled (there is pretty much nothing on the tablet, not even a browser after flashing it), you can use that to open/install the play store APK and get things going.
Please make sure you know what you are doing and you know how to recover from a soft brick. I take no responsibility if anything goes wrong.
The version you should have now is BTV-DL09C233B336 with security update from February included.
Thank you very much, and how to downgrade ?
can someone upload a youtube video showing us the the new EMUI5 on this tablet, and give us an overview about the new features and performance?
Beware that:
1) this is a chinese ROM
2) Nougat version 7.0.0
3) if you don't like the downgrade process is difficult
4) if you want to downgrade have to find another ROM!!!
any idea to downgrade please
drlsd said:
any idea to downgrade please
Click to expand...
Click to collapse
You need another ROM, FULL not OTA.
1) extract from the .APP the recovery (both) and boot images
https://forum.xda-developers.com/showthread.php?t=2433454
2) get a build.prop from the ROM you want to install
3) copy the build.prop in the /system folder, overwriting the original: now the old ROM will unlikely boot!
4) go in fastboot mode and flash recovery, recovery2 and boot images
5) copy the update.app in the dload folder
6) reboot and maintain pressed both volume keys to start recovery
7) if you are lucky the recovery will install the ROM.
Of course you will loose all your data (uhm, not even but... MAKE A BACKUP before!)
If you don't know well how to do ALL this don't even try!
If you have the original european LTE ROM please share it!!!
Nicola
2) get a build.prop from the ROM you want to install
i can t found these file in the new full rom (in my case BTV-DL09C233B035 )
drlsd said:
2) get a build.prop from the ROM you want to install
i can t found these file in the new full rom (in my case BTV-DL09C233B035 )
Click to expand...
Click to collapse
I attached that I extracted from the same ROM.
nicolap8 said:
I attached that I extracted from the same ROM.
Click to expand...
Click to collapse
Please share your oeminfo if you can. Thank you.
thank u very muatch nicolap8 ,is it normal i have NRD90M test-keys like number of software in my medipad m3 european LTE ?
drlsd said:
thank u very muatch nicolap8 ,is it normal i have NRD90M test-keys like number of software in my medipad m3 european LTE ?
Click to expand...
Click to collapse
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...
nicolap8 said:
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...
Click to expand...
Click to collapse
from europien lte to BTV-DL09C233B336 and now my build verson is NDR90M test-key
nicolap8 said:
You need another ROM, FULL not OTA.
1) extract from the .APP the recovery (both) and boot images
https://forum.xda-developers.com/showthread.php?t=2433454
2) get a build.prop from the ROM you want to install
3) copy the build.prop in the /system folder, overwriting the original: now the old ROM will unlikely boot!
4) go in fastboot mode and flash recovery, recovery2 and boot images
5) copy the update.app in the dload folder
6) reboot and maintain pressed both volume keys to start recovery
7) if you are lucky the recovery will install the ROM.
Of course you will loose all your data (uhm, not even but... MAKE A BACKUP before!)
If you don't know well how to do ALL this don't even try!
If you have the original european LTE ROM please share it!!!
Nicola
Click to expand...
Click to collapse
rom-stock-btv-dl09c100b009-european
https://forum.xda-developers.com/mediapad-m3/how-to/rom-stock-btv-dl09c100b009-european-t3588477
nicolap8 said:
What are you saying about???
It depends from which ROM have you installed!
Often the truly incompetent Huawei developers uses the wrong keys...
Click to expand...
Click to collapse
Hi nicolap8 even I followed the same steps as you suggested with the file links you shared and I am also NRD90M test-keys on my Mediapad BTV-DL09
installing Magisk first time gave me a fail message but second time it works like a charm. thanks
could you help, thanks
Switched to eu rom, updated to nougat.. unlocked bootloader and rooted with magisk
But using magisk caused the fingerprint sensor not to work at all and there is no settings for the FP in the settings menu.
Uninstalled magisk and the fingerprint worked again but obviously I lost root.
Flashing SuperSU didn't work gives an error in twrp no matter what version I try.
Any idea on how to root without compromising the fingerprint sensor?? :/
Half Alive said:
Flashing SuperSU didn't work gives an error in twrp no matter what version I try.
Click to expand...
Click to collapse
Error? we do not see errors...
Post recovery.log
question
how to flash firmware for Huawei Mediapad M3 ? I know how to do it for galaxy with odin ?.
where I download firmware for Huawei Mediapad M3 ?
carlo67 said:
question
how to flash firmware for Huawei Mediapad M3 ? I know how to do it for galaxy with odin ?.
where I download firmware for Huawei Mediapad M3 ?
Click to expand...
Click to collapse
You have more than 600 posts and yet have not understod the rules here???
SEARCH and READ!
Fingerprint Button
Hello, velocity.
Worked for me, thx.
The fingerprint button doesn't work anymore.
Is there a way to activate it (without loosing root by uninstalling magisk)?
Kind regards
veloc1ty said:
Okay, managed to get Nougat and root for my BTV-DL09. Here is a fast forward tutorial how to do that.
I could only root it by using Magisk, Supersu (even the special emui5 ones) did not work for me.
Files:
ROM: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1224/g490/v78425/f1/full/update.zip (BTV-DL09C233B336)
Data: http://update.hicloud.com:8180/TDS/...full/dualcu/cn/update_data_full_dualcu_cn.zip
Click to expand...
Click to collapse
Those Links are dead. Anyone save a copy? Willing to share? Thanks.
DisclaimerThis software comes wth no warranty,XDA staff ,myself or TeamWin stuff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_mate9_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** @Tecalote - He was the main tester for this version and also he was the one that convinced me to open this thread in first place
**** @Blackball
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_mate9_0.1.img - initial release
Thank you for such a great project!
I am very happy with this TWRP. Everything is working so far on EMUI, Android 8.
Data wipe is possible, cause OEM Path is excluded.
Vendor.img and System.img and recovery_ramdisk can be flashed by choosing img to the related img.
Backup, restore of all shown Partitions working perfectly.
Decryption of storage if using Fingerprint /PIN is working. Full encryption support for data..
Many thanks to @Pretoriano80 for this awesome and first most complete TWRP for Mate 9 :good::good:
BTW: @Blackball had tested this TWRP for P10 Plus and it is also working on this Device (so it will run also on P10).
Many thanks for testing too :good:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Wirmpolter said:
This is good to know... Going to have to give this TWRP a try. So what, to decrypt data, do I just have to format data in TWRP or?
Click to expand...
Click to collapse
Format data is only necessary if installing AOSP based Roms which require this (in installation guide)
But for Stock Firmware you don't need to decrypt (format) anything because encryption is fully supported
Of course, you can't install older Stock based Custom Rom which mount data in the updater-script without /dev/block/dm-0
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
osk4rin said:
I tried to installed on my Huawei mate using RR remix treble Rom, but It doesn't work, it just boot on the TWTP logo then boot up again.
Click to expand...
Click to collapse
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Tecalote said:
We are aware of this, but this is the initial release.
It's fully working on EMUI for now.
Click to expand...
Click to collapse
Oh right, thanks.
Seems to work perfectly, in my case the rom doesn't even seem to be overwrite twrp upon normal boot
Thanks a lot!
osk4rin said:
Oh right, thanks.
Click to expand...
Click to collapse
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Caguayote said:
i end up with error 255 on huawei mate 9 rooted oreo mha-l29 8.0.0.360(c567)
when i try to backup and at the beginning of twrp boot it ask me for a password
Click to expand...
Click to collapse
If it's ask for password, then insert the same passwords/pin/pattern that you are using in Android, so TWRP can decrypt the internal storage.
That's the whole purpose of having a TWRP with decryption support.
10-4
Thank you for the clarification
Pretoriano80 said:
If you (or anyone else) are still having/testing a custom rom, please send me /system/build.prop and vendor/build.prop.
Click to expand...
Click to collapse
how can I get them?
osk4rin said:
how can I get them?
Click to expand...
Click to collapse
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Work this nougat .. ??
Tecalote said:
If your Phone is rooted, with Root Filemanager like FX Explorer or Mixplorer you can copy from /system/build.prop and /vendor/build.prop
Click to expand...
Click to collapse
I just attached the build.pro files .Using RR remix treble project
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
_Nostromo_ said:
Hi, I really appreciate this recovery, just have one question: is there a way to enter the decryption pwd only once and not with every TWRP start? Would make things easier (even I understand the current way is much safer...). Thanks and respect!
Click to expand...
Click to collapse
No, it's designed to work like this!
Pretoriano80 said:
No, it's designed to work like this!
Click to expand...
Click to collapse
Ok, thought so, it definitely makes sense, just being a bit lazy... Thanks a lot for your prompt response, Pretoriano80! :good:
Code:
[B]NOTE : [/B]PROCEED AT YOUR OWN RISK. Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues.
If already on Stock Rom then visit THIS THREAD for OTA updates.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - TWRP_Stock_v340.zip from this post.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
Users coming from Android Pie reported microphone issues - in case you face it then flash DolbyPlus-Oreo_8.1.zip from THIS post via Magisk which might resolve the issue.
(optional) If you want to boost up by debloating then use this MOD.
(optional) If you want to boost up BATTERY then use this GUIDE.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
NOTE : ROM works independant of RAM i.e. applicable for 3/4/6 GB variants.
Recommended TWRP : https://androidfilehost.com/?fid=3700668719832241089 by @SagarMakhar.
To ROOT the ROM
Flash Magisk from TWRP and you will have root access
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
piku2008 said:
Well I am trying to flash this ROM coming from RR but somehow its taking half an hour to encrypt so is it necessary to encrypt can't we just skip it ???
also it did erased TWRP as when I am trying to get in TWRP using volume up + power button its get back to default bootloader that came with mobile .....
also do I have to flash again TWRP again after this to get back root via magisk......
Click to expand...
Click to collapse
Did you performed factory reset and flashed ROM & decrypt.zip
The TWRP survives the flash and Magisk can be flashed to Root the ROM but after above two files are flashed.
Well I successfully flashed ROM after complete factory reset with internal memory tooo ......
But some how TWRP got replaced with factory default (the one with root checker) with bootloader unlocked screen
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Aftab_khatri said:
Thank you. Just updated to latest version from old stock rom. Please update new versions also whenever available
Click to expand...
Click to collapse
Will do
Thank You bro.. Your Guide has tested successfully from AOSiP build to stock ROM 309.. [emoji16]
Sent from my [device_name] using XDA-Developers Legacy app
AOSP to Stock
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
jroviel18 said:
Good day, Can I use this method to go back in Stock Rom? Currently using AEX but I can't use my mobile data here in the Philippines, your answer would be a great help, Thank you...
[Update]
Good day mate, just flashed this, and I'm back to stock with root, Thanks Mate for this...
Click to expand...
Click to collapse
Great .. Sorry could not reply earlier but you got the resolution of the query.
For subseqeunt update with TWRP intact .. please follow this guide in future .. https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269
Update - WW-15.2016.1805.311
Updated Stock ROM file - TWRP_Stock_v311.zip now avaliable.
For those who are already on stock ROM,
The instructions to flash are in THIS POST.
For those who are on custom ROM,
The instruction to flash are in THIS POST
Do these zips format internal storage or not ??
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
No
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
I believe this is the exact same firmware as the official one. It is just modified to work with TWRP. Nothing more, nothing less.
aadi50 said:
Do these zips format internal storage or not ??
Click to expand...
Click to collapse
You will have to format data (i.e. factory reset) but the Internal Storage will be safe.
aaa
Work For Max Pro M1 ?
This rom XOOT not XOOTD
---------- Post added at 11:26 AM ---------- Previous post was at 11:07 AM ----------
.A.V.i.n.a.S.h. said:
Code:
[B]NOTE : [/B]Guide tested successfully to flash [U]Stock WW-15.2016.1805.309[/U] from AOSP extended (22/06 build) on primary device. Also I will try to help out in case of issues. BUT still proceed at your own risk.
This thread is useful for those who want to return to stock ROM from custom ROM while keeping TWRP & unlocked bootloader.
How to ,
Backup all your important app data.
Do a TWRP backup of current ROM. (precautionary step)
Download modified full recovery stock rom - Stock_X00T_Patch_May_Version_311_TWRP.zip.
Download decrypt.zip from HERE.
Reboot to TWRP.
Go to wipe and select swipe to Factory reset.
Flash the ROM file.
Flash decrypt.zip file.
Reboot & Enjoy.
(optional) If you want to boost up by debloating then use this MOD.
This will update your firmware to WW-15.2016.1805.311 to have updates after this follow THIS THREAD.
Remember that it takes a lot of time to create , test and upload these huge files for everyones use. So please hit Thanks! button on the bottom right of the post to keep me motivated
Click to expand...
Click to collapse
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
arielrizuly said:
My Devices Zenfone Max Pro M1 X00TD
This your Rom Not WORKING X00T
Flash to TWRP error TWRP Has Restarting
sory bad english
Click to expand...
Click to collapse
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
.A.V.i.n.a.S.h. said:
This ROM should work on X00T and X00TD both. Can you please validated checksum again for the downloaded file.
Click to expand...
Click to collapse
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Abby 244 said:
I am on stock build 311 and Rom X00TD , i am unable to root or even unlock bootloader on my device.
Tried all methods , on YouTube and xda but all wasted.
Though , i debloated my phone using one of the methods mention in a thread in xda and even installed xda navbar using adb.
Please help.
Click to expand...
Click to collapse
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
.A.V.i.n.a.S.h. said:
Have you checked the drivers if they are installed.
Do one thing .. see if in fastboot .. if you get any responce for fastboot devices command from pc.
Click to expand...
Click to collapse
No response even in fastboot.