Important notice: This is an outdated modded recovery which only works with nougat. Use the newest one instead. It supports both Oreo and Nougat rom porting.
Modded TWRP 3.1.1-0 Download:
Google Drive
How to install:
- Unlock bootloader
- Enter in Fastboot Mode (Power Button + Vol Down)
- Flash using "fastboot flash recovery twrp.img"
Mod features:
- Automatic A1 Rom Porting
- Included Magisk 14.5 installer
- Included AROMA Filemanager
Where can I find the new features?
Go to Advanced menu and then tap on "Aex12 Toolbox". A new menu will open with the new 3 options (Port A1 Rom, Install Magisk, Aroma FM)
How does A1 automatic ROM porting works?
Install any Nougat A1 ROM directly on your 5X, but make sure you only install system.img and boot.img, if you flash other partitions you will probably face some errors. Then tap on "Port A1 Rom" button. Confirm that you want to make the port using the slider. Wait until it finishes. Reboot and enjoy.
How can I flash an A1 rom into the 5X?
If you downloaded an official rom, extract it somewhere, enter the directory and look for the "images" directory. Enter on it, open terminal on this directory and then execute this commands:
fastboot flash system system.img
fastboot flash boot boot.img
After it finishes, go to TWRP and use the "Port A1 Rom" button
Fingerprint is acting as a button after porting A1 rom
You need to flash A1 firmware to avoid some minor bugs like this.
Will it work with Oreo?
It does not work with Oreo at the moment. I'm working to make it work. As soon as I got it, I will add an automatic Oreo porting button.
Does this works with custom ROMs?
I didn't try, try it yourself and comment results
Where is the changelog?
You can check it here
Donations:
If you like my work and want to contribute, you can donate via paypal.me/aex12
Device Tree: https://github.com/Aex12/android_device_xiaomi_tiffany/tree/nougat
Manifest used: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
XDA:DevDB Information
TWRP Modded 3.1.1, Device Specific App for the Xiaomi Mi 5X
Contributors
Aex12
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Beta
Current Beta Version: 3.1.1-0
Created 2017-12-05
Last Updated 2018-03-08
Good job. Thank you.
Thank you.
Thank you :good::good:
hello thank you, but I have 1 problem, I can not access the micro sd card, by twrp.
Best Regards
Please help to mirror modded versions to mega Drive too, Thank you.
Google is blocked in my country. Even if I use some proxy tools, it still hard to download anything from Google drive.
I have tried everything I can...
I followed the exact procedure word to word on my Mi 5X (It has Nov update before)
downloaded an official rom, extract it somewhere, enter the directory and look for the "images" directory. Enter on it, open terminal on this directory and then execute this commands:
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
After reboot to system the error showed telling "No Command" with no system to boot. Fortunately I had Nov Update so installed it in TWRP and got back to system. Detailed instructions will be appreciated.
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
AncientLord said:
I followed the exact procedure word to word on my Mi 5X (It has Nov update before)
After reboot to system the error showed telling "No Command" with no system to boot. Fortunately I had Nov Update so installed it in TWRP and got back to system. Detailed instructions will be appreciated.
Click to expand...
Click to collapse
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Aex12 said:
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Click to expand...
Click to collapse
Thanks for the tip. I missed that step. I followed the steps to the letter now and flashed system.img and boot.img from December ROM as indicated by the attached photo. But the mobile is still on November Patch level. Done that twice to no effect.
AncientLord said:
Thanks for the tip. I missed that step. I followed the steps to the letter now and flashed system.img and boot.img from December ROM as indicated by the attached photo. But the mobile is still on November Patch level. Done that twice to no effect.
Click to expand...
Click to collapse
Phone is updated, but version displayed on settings is wrong. It's an known bug. Flash fixed recovery and tap on "A1 Rom Porting" again. You don't need to flash system.img and boot.img again.
Aex12 said:
Important notice
Updated modded recovery. Fixed some bugs in the Automatic Rom Porting feature. If you plan to use this feature, please, flash new img.
(New link is on main thread)
As said on the post, after you install it you need to boot into the modded twrp and tap on "A1 Rom Porting". If you dont do it, it wont work.
Click to expand...
Click to collapse
Aex12 said:
Phone is updated, but version displayed on settings is wrong. It's an known bug. Flash fixed recovery and tap on "A1 Rom Porting" again. You don't need to flash system.img and boot.img again.
Click to expand...
Click to collapse
This time it worked. Thanks you for your great effort. Much appreciated.:good:
Can you give me a brush adb file?
I tried to flash the December update system.img and got an error about not enough space. Like the image was too big to flash.
i flash system.img and boot.img but i cannot ota update
Sent from my Mi A1 using XDA Free mobile app
zzzwww said:
Can you give me a brush adb file?
Click to expand...
Click to collapse
You can find it here:
https://developer.android.com/studio/releases/platform-tools.html
---------- Post added at 02:11 PM ---------- Previous post was at 01:23 PM ----------
wailinhtike said:
i flash system.img and boot.img but i cannot ota update
Sent from my Mi A1 using XDA Free mobile app
Click to expand...
Click to collapse
No, you can not update 5x with mi a1 rom via ota.
Getting this when trying to flash system. How do I fix this?
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.219s]
sending sparse 'system' (522959 KB)...
OKAY [ 19.155s]
writing 'system'...
OKAY [ 2.803s]
sending sparse 'system' (502018 KB)...
OKAY [ 18.197s]
writing 'system'...
OKAY [ 2.504s]
sending sparse 'system' (524297 KB)...
FAILED (remote: data too large)
finished. total time: 47.065s
gurex said:
Getting this when trying to flash system. How do I fix this?
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.219s]
sending sparse 'system' (522959 KB)...
OKAY [ 19.155s]
writing 'system'...
OKAY [ 2.803s]
sending sparse 'system' (502018 KB)...
OKAY [ 18.197s]
writing 'system'...
OKAY [ 2.504s]
sending sparse 'system' (524297 KB)...
FAILED (remote: data too large)
finished. total time: 47.065s
Click to expand...
Click to collapse
Are you on a Mi 5X and installing Mi A1 rom? It should flash well as both phones have same system partition size. For me it worked.
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Aex12 said:
Are you on a Mi 5X and installing Mi A1 rom? It should flash well as both phones have same system partition size. For me it worked.
Click to expand...
Click to collapse
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
gurex said:
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
---------- Post added at 01:47 PM ---------- Previous post was at 01:46 PM ----------
Yes. I have a mi5x and downloaded the A1 ROM and tried installing it using the instructions in the first post. I tried downloading newer fastboot version but the same error occurres.
I guess that it is the phone that is the problem as fastboot reports; "target reported max download size of 536870912 bytes"
Can I change this size limit?
Click to expand...
Click to collapse
Max download size is not the problem. Mine is also the same. Fastboot will just divide system.img in chunks of 500mb approximately each of. Try downloading newer fastboot binary.
https://developer.android.com/studio/releases/platform-tools.html
Aex12 said:
Max download size is not the problem. Mine is also the same. Fastboot will just divide system.img in chunks of 500mb approximately each of. Try downloading newer fastboot binary.
https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
Will try it when I come home today and report back!
Related
I followed the directions from this post, but every time I try to install the upgrade, it fails because the partition size is not large enough. I had to flash recovery_MT2L03_mmcblk0p19.img because when I tried to use B321 it also gives me an error that says "failed: remote size too large".
How can I fix this? Thank you!
Also, food for thought, when I look at available internal storage within the stock ROM, it says only ~6gb are free out of 8, and I know this phone is a 16gb device. I don't know if that's related, but it's rather odd.
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
divineBliss said:
Are you following the B322 Huawei upgrade instructions PDF? What does it say the firmware version needs to be initially? Are you paying attention to that ?
Click to expand...
Click to collapse
Yes I've also read those instructions. I successfully got to this screen once, and at about 25% completion, it said the process failed.
Right now I have no installed OS because it fails for all of them, just FYI.
Update: This is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
divineBliss said:
Is your HAM2 a Consumer Cellular by chance? Have you tried starting over by putting B148 recovery and firmware on the phone? That's what I would do.
Click to expand...
Click to collapse
Completely unlocked L03, brand new. I've tried installing the old OS from the JB downgrade pack, still fails.
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
divineBliss said:
You did not answer my questions ....... and what version ROM/recovery is on the phone now?
Click to expand...
Click to collapse
I figured that was a proper response to both questions... Apologies. It is not CC, and yes I have done both of those things. There is no installed ROM or OS. Recovery is variable, I've tried stock and TWRP 2.8.7.
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
divineBliss said:
1. What model # is this phone?
2. What versions of ROMs, recoveries have you had on it?
3. Is the bootloader unlocked? You're going to need in unlocked to put custom ROMs on it.
4. I would try getting it back to stock B148 ROM and recovery if its a non-CC MT2L03. You might have to hunt around the HAM2 forum for threads on how to recover from bricked phones if you're having problems getting to stock B148 or some other stock version that B322 instructions say can be a starting point to upgrade to B322.
Click to expand...
Click to collapse
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Correction: I was able to flash the stock recovery and then the stock B148 ROM. So the only problem I have now is the system partition is only ~1gb in size, not large enough to accommodate for the ~1.6gb for the B322 or B321 update. I'm trying again now tho.
Tried to flash B321, same error. This is what I see.
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
ScoobSTi said:
Just tagging some people more knowledgeable than I who can probably help. @xordos @SHM
Click to expand...
Click to collapse
Any and all help is appreciated, thank you! Btw, the storage size issue has self-remedied since I reflashed the B148. It now says 12.5gb free of 16gb. Apparently the ROM they shipped me with had some issues...
Also: I have tried the repair and resize functions from TWRP 2.8.7 on my system partition to no avail. It remains ~1gb.
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
divineBliss said:
Why are you trying to install B321 vs B322?
Go back to B148 (ROM + recovery), then try using the Huawei provided instructions to install, B322 and post what happens.
I went from B148 out of box to B322 to custom recovery / custom ROMs.
Click to expand...
Click to collapse
Because that's what Nigel's directions say. Both the B321/B322 recovery and ROM fail independently. So regardless which one I try, I still have the partition problem.
chill8888 said:
1. Model is MT2-L03...
2. I have not had any ROMs, just the stock JB out of the box. Stock recovery and TWRP 2.8.7
3. Bootloader is fully and properly unlocked.
4. I said already, I cannot flash ANY ROM, stock or otherwise, because every time it tells me the partition is not large enough...
Again, this is the error message I see on cmd...
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.093s
Click to expand...
Click to collapse
format internal Sd and try again.
Moody66 said:
format internal Sd and try again.
Click to expand...
Click to collapse
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
chill8888 said:
Reformatted to ext4, partition size is still the same. See attached photo.
Tried to do an update from within the B148 ROM update app, same error as the first image I uploaded.
Click to expand...
Click to collapse
Try to do the 309 update first. That should clear up the partitions for L to update.
Moody66 said:
Try to do the 309 update first. That should clear up the partitions for L to update.
Click to expand...
Click to collapse
I may need some help tracking that down. I got the MT2L03_B309_withRoot_Orig.zip from Nigel's Gdrive, but it contains the system and boot.img files, not the update.app file...
Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Thank you for the quick reply.
NightCrayon said:
You have to install TWRP, once installed reboot into TWRP, Wipe then install Lineage OS, su(arm) addon, then open Gapps.
Here is a video on how to install TWRP: https://www.youtube.com/watch?v=sjA4F_TzzwQ
You can find the newest TWRP for the MT2 here (its near the bottom of the page, do not download the version of Lineage OS on that page ONLY TWRP): https://android.cmphys.com/lineageos-mt2/
Then download Open Gapps (click on ARM>7.1> then choose which variant, i use PICO, but other variants have more Google Apps): http://opengapps.org/
Download an official Nightly of Lineage: https://download.lineageos.org/mt2
Download "su (arm)" addon for Root access in Lineage, Flash this a long with Lineage: https://download.lineageos.org/extras
here is another useful video of SuperBass installing a different rom on the MT2 to kind of give you an idea on what to do: https://youtu.be/Tq27VfRYKYQ
Good luck!
Click to expand...
Click to collapse
Hi, I have followed all the above instructions, but i am still getting the same error. Since there is no OS installed, I have performed the following steps:
1 . Downloaded the twrp-3.0.M6-0-mt2.img and renamed it to TWRP.
2 . Rebooted the phone into bootloader mode and flashed the phone with the twrp-3.0.M6-0-mt2.img (twrp).
3. Rebooted the phone into recovery mode.
4. Wiped the phone to factory settings and also wiped the /system, data, cache, except internal storage.
5. Used the adb push command to transfer the rom, extra (su arm), and gapps to the external memory.
6. Upon flashing the rom I get the error below:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
Please let me know if I am missing anything. Thanks again
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
techswy said:
It is a wind Mobile phone that i am trying to flash it to linage 14.1. I don't have stock rom installed because I wiped /system accidentally.. As stated in my first post that I tried to check the bootloader version, but all I get is the following result below:
-----------------------------------------------------------------------------------
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
-----------------------------------------------------------------------------------
I don't know whether ' 001.001.000' means it is an old bootloader or latest. I would also like to mention that I was able to flash the phone to cm13.1 nightly, but the wifi was not working and security under settings was crashing.
I tried to update the bootloader 322 from the link below with B321_stock p19 recovery.zip under B321 folder:
https://drive.google.com/drive/fold...9VZ0ExZmhWS2VSUnNieUc4QTRRUVVZM2dLOHlRTnhNVDg
When I try to flash the phone with B321recovery.img it gives me an error FAILED (remote: size too large). See the result below:
c:\adb>fastboot flash recovery c:\adb\B321recovery.img
< waiting for device >
target reported max download size of 1073741824 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.074s]
writing 'recovery'...
FAILED (remote: size too large)
finished. total time: 2.087s
Please any help appreciated.
Click to expand...
Click to collapse
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
NightCrayon said:
The wind Mobile variant of the MT2 has a little bit of a different process for updating the bootloader, follow this guide to install the last official B322 update, then you will have no problems with installing lineage as your bootloader will be up to date.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Let me know if you have anymore issues. Good luck!
Click to expand...
Click to collapse
Thank you so much for the link. I will definitely let you know if I run into more issues with the upgrade. Thanks again.
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
ScoobSTi said:
Yes, the newer custom ROMs require you to have flashed B322 (Huawei's final Lollipop ROM) first before flashing the custom ROMs. They have these warnings in the posts.
In the future, if you want to switch from one custom ROM to another, like from Lineage to CM, you won't need to flash B322 again as you would have already done this.
Click to expand...
Click to collapse
Thanks for the reply. I really appreciate the response. :good:
Thank you xda forum, NightCrayon and ScoobSTi for helping me fix my phone. Thanks again.
You must be from Wind Mobile from Canada
techswy said:
Hi, I am trying to install the lineage-14.1-20170125-nightly, but I get the following error:
This package supports bootloaders: MSM8226C00B322_Boot; This device has bootloader MSM8226C00B128_Boot. The updated process ended with Error 7. Error installing zip file '/sdcard/lineage-14.1-20170125-nightly-mt2-signed.zip'.
I am not sure if I have the correct bootloader.
c:\adb>fastboot oem get-bootinfo
.
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.016s]
finished. total time: 0.016s[/SIZE]
I have tried to follow the link below, but some of the direct links to the files are not working:
https://forum.xda-developers.com/as...iew-cyanogenmod-mate-2-mt2l03-t3181518/page52
Could anyone help me out with this thanks.
Click to expand...
Click to collapse
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
vivek76 said:
You must from Canada. You have to change your device from MSM8226C00B128 to MSM8226C00B322. Flow the link blow. This link will guide you to change to B322 and upgrade to Android 5.1.
https://forum.xda-developers.com/ascend-mate2/general/guide-step-step-wind-mobile-canada-t3387490
Click to expand...
Click to collapse
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
sevenday4 said:
Hi, I'm having the same issue and I am using firmware B322 Lollipop 5.1. So I think something else is afoot. I'm going to try and update to Marshmallow cm13 first. But, I have to assemble cm13 myself, unless someone can get me a copy I would surely appreciate it.
Click to expand...
Click to collapse
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
I was finally able to install Lineage lineage-14.1 awhile back. I figured out where to get the Rom and modify it in order to flash it on my mtl02. But, it's been acting kinda kinky so for grins I'm going to try Candy that divhandyman suggested. ?
divhandyman said:
Candy is so much better have you tried that yet?
https://www.androidfilehost.com/?w=files&flid=151179
Click to expand...
Click to collapse
I have just flashed Candy ? about two weeks ago. Had some issues with substratum and magisk. I guess it was because you need a certain version of TWRP. Then a few days ago I with the LOD (loop of death). Lineage had the same issue
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
AWFRONT said:
Thank you for your share. I am on my 2nd ZF3U and will look to keep this UNROOTED and BOOTLOADER LOCKED until a decent custom rom becomes available but looks like the developer community does not want to touch this device which is really sad as in my opinipn it is the best large screen phablet currently available,?
Click to expand...
Click to collapse
I was going to do the same but I got tired of the ads and bloatware, so I needed root to install AdAway and Titanium Backup to clean the preinstalled programs
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
doctahjeph said:
Any reason for the v2.80 vs the 2.79? I was rooted before with 2.79 and didn't have any issues that I saw.
Click to expand...
Click to collapse
That is what they recommend on the other site. I do not know why.
once you've done this, does it block OTA updates from Asus?
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
I think so.
speculatrix said:
once you've done this, does it block OTA updates from Asus?
Click to expand...
Click to collapse
Once you unlock the bootloader the OTAs are blocked, even if you aren't rooted. It is okay you can still manually install the firmware easily.
mushufasas said:
[
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Click to expand...
Click to collapse
I updated it & still have root
I have rooted again on latest firmware and used Supersu 2.79. Works as advertised so far.
Gone Looking
mushufasas said:
DISCLAIMER: This is NOT my work. This files I've downloaded from a different site and flashed them to my device with success. I will not take any responsibility for anything wrong happen to your device. Do it at your own risk. Also, I will not update this thread. I just want to share this information.
After searching for hours I found on a site in Taiwan the way to root the ZenFone 3 Ultra on latest update of Android 7.0 (WW_14.1010.1703.42)
Here are the steps I did:
1. Unlock Bootloader with the original program from Asus website.
2. Flash TWRP 3.1.1 recovery with fastboot.
3. Reboot in to Recovery and installed SuperSU-v2.80-201705171619.zip
4. Wipe cache and reboot.
5. Once booted DO NOT UPDATE SuperSU from Play Store, it will break the root.
Both files are in the link below.
Files:
https://drive.google.com/open?id=0B69uFcMh3Eb6QTFSYXF1TzZxX00
Click to expand...
Click to collapse
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
av8or091 said:
Currently at WW_14.1010.1703.36 so off to find xxxxxx42.
This process will not work on my Ultra at rev 36.
cheers,
Click to expand...
Click to collapse
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
av8or091 said:
Have now update to rev 46 and this process still defaults to Android recovery on my Ultra.
I have used your files included in the attached zip and it will not install TWRP.
Thoughts?
Click to expand...
Click to collapse
I do not know why, but I had to reinstall the rom on my phone, used the same files for root and it worked with no problem.
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Suggested Edit
mushufasas said:
I have updated to UL-ASUS_A001-WW-14.1010.1704.46 using the file from ASUS support page and used the same method to root, and it worked without a problem.
Click to expand...
Click to collapse
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
signature verification failed
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
krcma.cz said:
hi i have 14.1010.1705.49-20170602 verison
twpr flash is ok but when i try to flash supersu
i get signature verification failed
any help please
TH
Click to expand...
Click to collapse
i flash downgrade fw WW-14.1010.1703.42
and flashing of supersu still not working
any idea ?
av8or091 said:
As there can be more than one method in which to select 'Recovery Mode' your third line should read as follows;
3. Do not select Recovery Mode from Fastboot Menu, Reboot Phone then select Recovery Mode to install SuperSU-v2.80-201705171619.zip
C:\Users\xxxxxx\>adb reboot bootloader
C:\Users\xxxxxx\>fastboot flash recovery twrp3.1.1.img
target reported max download size of 536870912 bytes
sending 'recovery' (19986 KB)...
OKAY [ 0.772s]
writing 'recovery'...
OKAY [ 0.331s]
finished. total time: 1.109s
C:\Users\xxxxxx\>fastboot reboot
rebooting...
Works like a charm, thanks for the research making this available.
Click to expand...
Click to collapse
seems like all went well for me . . . unlocked / twrp / superuser / even the upgraded kernel & software upgrade ........ but the system hangs on the start screen ... but upon restart - the zenphon still goes into bootloader & twrp if i want to.
I don't suppose anyone made a twrp backup of a fresh / no added programs? Even one w/ bloat removed?
anybody able to show a bit of love?
thx in advance
Bummer . . . . no one's made a twrp backup yet? That's one of the 1st things i do - just in case.
.
Is it possible to update to new version of SuperSU then 2.80 ?
I try to update SuperSU with TWRP to version 2.82-201705271822.zip but installation failed....
Hi,
i tried to update to OpenKirin RR Beta 3, but flashing failed with fastboot (fastboot flash system C:\Daten\rr3.img.xz)
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (460796 KB)...
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 131128796 is not a multiple of the block size 4096
OKAY [ 10.747s]
writing 'system' 1/2...
FAILED (remote: sparse flash write failure)
finished. total time: 14.841s
Click to expand...
Click to collapse
I had installed magisk with OpenKirin beta2 before. After failed flashing the device tries booting a few times but then it boots to eRevovery.
I tried flashing -kernel-recovery-ramdisk 368 from @JBolho Thread (https://forum.xda-developers.com/honor-9/how-to/emui8-kernel-recovery-ramdisk-stock-t3781347), because i thought something went wrong with the patched boot.img from magisk. But no success. Still bootloops and ended in eRecovery.
Can somebody help?
Thank you
P.S.: I posted this question in https://forum.xda-developers.com/honor-9/development/roms-openkirin-aosp-collection-t3828787/page3 too, but i don't know if somebody reads it there.
You tried to flash the compressed file instead of extracting the img file from it...
JBolho said:
You tried to flash the compressed file instead of extracting the img file from it...
Click to expand...
Click to collapse
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Saftpresse99 said:
Thank you. Rookie mistake. Flashing system now works, but boot ends in eRecovery too.
Click to expand...
Click to collapse
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
JBolho said:
OpenKirin website where the rom can be downloaded has full installation instructions.
You flashed recovery, ramdisk and kernel from B368, was that the EMUI version you were before?
I would recommend flashing TWRP and re-install B368 with HuRUpdater tool, reboot to stock recovery (not eRecovery), wipe cache and do a factory reset, turn off the device and boot in fastboot mode, flash RROS and reboot again.
Click to expand...
Click to collapse
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Saftpresse99 said:
I don't know my EMUI version before. Is it important?
I choose B368, because it was the last version available.
Click to expand...
Click to collapse
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
JBolho said:
Of course it's important, the stock kernel, recovery and ramdisk must match the EMUI version installed or it will never boot.
Click to expand...
Click to collapse
What can i do to determine the correct version?
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Saftpresse99 said:
With B360 i can boot and the splash screen from RR3 appears. But after some time the phone restarts into eRecovery. I tried RR2 and phhusson's treble roms , which factory reset and wipe cache. Rom boots but then the device restarts into eRecovery.
Click to expand...
Click to collapse
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
JBolho said:
Please do what I told you earlier, it's the best way. Flash zxz0O0's TWRP and use HuRUpdater tool to flash EMUI again, get the FullOTA from Firmware Finder of B368 or B369 at the most.
Then do a factory reset and see if it boots properly.
After that go to OpenKirin website and follow instructions carefully.
Click to expand...
Click to collapse
Thanks. Installed twrp, but can't get FullOTA from firware finder: http://pro-teammt.ru/projects/hwff/v2/GetLatestVersion.action Site is down. :crying:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Saftpresse99 said:
Installing zxz0O0 works but if i try to boot into recovery it stucks on welcome screen. Nothing happens. Log attached.
I tried this twrp: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442 and this boots.
Click to expand...
Click to collapse
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
JBolho said:
You can also flash roms with HuRUpdater using that twrp. The problem now is getting the rom, try to search on other forums as well, like 4pda and such, since FF is down...
Click to expand...
Click to collapse
Hi,
thank you very much. My device is now working again. Your instructions working very well. I flashed stf-L09c432 B360 with HuRUpdater and device boots. I donwloaded the firware from this site: http://huawei-firmware.com/phone-list/huawei-honor-9
Did some learning, some digging, and found what is so broken on the current TWRP builds that are out there.
We're missing one line in the fstab.qcom
Code:
/dev/block/bootdevice/by-name/oem /oem ext4 ro wait
So I did the simple fix. Took TWRP 3.2.1-R20 (which supports backing up OEM) and added that line to fstab.qcom.
You can now backup & restore the OEM partition using TWRP and it isn't broken for OTAs.
EDIT: backup & Restore might still be broken, but it does not damage the OEM just booting TWRP. Looking into how to backup via image instead of backup via TWRP GUI.
Edit2: I've fixed the OEM backup so it now backs up as an image like /system does. This takes up 768MB of space compared to the previous 141MB, but for working OTAs it's worth it. Enable compression and the extra space isn't wasted. I've uploaded the fix as well and updated the link at the bottom of the post.
To add this fix to TWRP for devs, change the line in \etc\recovery.fstab from
Code:
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
to
Code:
/oem emmc /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
Adding that as an additional line will allow us to pick between a bitwise perfect OEM backup or just a basic "copied files" backup.
In the meantime, you can back up OEM using DD.
You can install Magisk in TWRP without breaking OEM.
I've tested and confirmed this on my XT1806 but it should work with all of them.
I've linked to the file at the bottom of this post. It's able to be directly flashed over your existing TWRP.
To fix your OEM partition for future updates:
Identify what software you're running. If you are running the first Oreo OTA build, just download the full firmware file and fastboot flash the OEM partition again. Then OTA should take
If you are running October patch, you will need to fastboot flash the first Oreo OTA OEM file and then ADB Sideload the October OTA on top of it. Then you're up to date. The October OTA can update just the OEM partition without needing to patch the rest.
If you are running Nougat, same applies, Just fastboot flash whatever OEM you are currently on and then OTAs should work.
To all TWRP devs, please add the OEM RO line to your fstab.qcom so we don't run into this in the future. it's a simple fix.
Edit3: I've added the ability to backup the Persist file as well since that's not included in standard R20. link updated as well.
DOWNLOAD:
https://drive.google.com/open?id=1FRWyndazNcfDugHExAOvSvDdOfy53PYq
That's pretty cool
squirting the #hit out of me!
thx
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Klaus R said:
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Click to expand...
Click to collapse
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
pizzaboy192 said:
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
Click to expand...
Click to collapse
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Klaus R said:
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Click to expand...
Click to collapse
Yup! I believe the file is called twrp-sanders-r20-oemsafe (might also mention persist)
I just did a rebbot in fastboot mode, from there to recovery, TWRP starts. Excellent. But internal storage (Data) is 0MB? Did i forget something?
Tanx a lot for your assistance
Klaus R said:
storage (Data) is 0MB
Click to expand...
Click to collapse
Seems to be encryption problem. https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
Can't fix the problem. First everything's fine, twrp's backup shows some Mb in /data (caused by magisk or su). So decryption is working at that point. Then, after booting into system and doing some settings, root is still there (rootchecker), but back to twrp there will be /data again with 0MB.
Anyone a hint? Main purpose of twrp for me is taking backups (before trying custom roms)
Running stock oreo 8.1.0 Europe with 01.02.19 sec patches
Need the TWRP installer please
Need the TWRP installer please
does this, or any similar twrp increase the chances of getting volte (which works on my xt1806 in stock oreo when i use the lenovo recovery app) up and running on say RR pie builds (which i was using unpatched twrp 3.2.1-r16 to install RR and gapps, then booting, updating OTA, then going back to install the TWRP 3.3 from this forum to flash Magisk)?
---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
Souravskrba said:
Need the TWRP installer please
Click to expand...
Click to collapse
the "installer" is either fastboot from your PC or install from your current TWRP (if you already have another version installed) hit install then >> flash img button)
hi this fixes the error 1 when flashing magisk?
thanks
M4T145 said:
hi this fixes the error 1 when flashing magisk?
thanks
Click to expand...
Click to collapse
Probably no. Search for Treble TWRP Moto G5s Plus on google. You need a trebelized TWRP in order to flash magisk.
link doesn't exist.
Please update the link to the file. Gdrive page results in URL not found.
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
Download the one that's there in the Sanders Telegram group.
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
sBinnala said:
Download the one that's there in the Sanders Telegram group.
Click to expand...
Click to collapse
link?
okayk said:
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
Click to expand...
Click to collapse
no luck, same error that i get with 3.4.0.0:
Code:
> fastboot flash recovery "twrp-sanders-treble-new(ByGeneticEnginer).img"
target reported max download size of 534773760 bytes
sending 'recovery' (14636 KB)...
OKAY [ 0.320s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.179s]
finished. total time: 0.503s