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....
I accidentally flashed a Retail US version on my Moto Z Retail EU, and now I am having a "bad key" at the Warning on boot up. Can someone provide me with a 7.1.1 or 7.0 link for Retail EU for the XT1650-03? It's for the normal Moto Z, not Play or Force. I NEED an Retail EU Boot as I flashed a wrong one and I cannot go back to 6.0.1 to fix it, so my Boot is broken until someone gives me a proper EU one for 7.0 or 7.1.
Thanks in advance!
Note: I am getting this when trying to flash the "XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" files:
D:\MAIN FOLDER\Android\Moto Z\XT1650-03_GRIFFIN_7.0_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml\GRIFFIN_NPLS25.86-17-3-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.078s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.805s]
finished. total time: 0.885s
So yeah, I need a boot image that isn't signed with a bad key for RETEU.
Fixed. Flashed a Retail US 7.0 STOCK ROM even though it said "bad key", and then I flashed erfanoabdi's "Stock" 7.1.1 ROM which flashed a working boot.img that doesn't cause this problem.
Thread closed.
i have same problem bro but i didn't understand your solved please help me
i have same problem bro but i didn't understand your solved please help me
anatete404 said:
i have same problem bro but i didn't understand your solved please help me
Click to expand...
Click to collapse
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
yanniclord said:
Flash this: https://forum.xda-developers.com/moto-z/development/rom-erfanrom-flashable-zip-t3646962
Click to expand...
Click to collapse
ok i will try flash it tomorrow but my phone still say bad key and didn't star i flash 7.0 with erorr and 6.0 with erorr
i see erorr bootloader not found when i flash with fastboot i mean my phone didn't boot in recovery or normal just fastboot
I am not understanding most of what you are saying, but I can prepare a little .zip with everything you need for you. I make a .bat file that you need to run which should do all the work for you.
anatete404 said:
...
Click to expand...
Click to collapse
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
i flash your rom bro when i flash i cant get recovery only fastboot please help me
try another Kernel flashing by TWRP https://forum.xda-developers.com/devdb/project/?id=17677#downloads
anatete404 said:
i flash your rom bro when i flash i cant get recovery only fastboot please help me
Click to expand...
Click to collapse
Would you please try to at least speak a little proper English and use punctuations, it's really hard to read.
i need flash for my phone i upload problem and info i am sorry about english but please help me
anatete404 said:
i need flash for my phone i upload problem and info i am sorry about english but please help me
Click to expand...
Click to collapse
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
thx bro but this https://androidfilehost.com/?fid=889964283620761640
working to my info phone i uploaded photo
Benoe said:
Here is the latest official full firmware with october patch:
https://androidfilehost.com/?fid=889964283620761640
Click to expand...
Click to collapse
Hey your link doesn't work anymore. Is it for 7.0+ and RETEU? If so, please send it to me !
yanniclord said:
Alright, here. Make sure that you have ADB installed System-Wide on your PC, you can use ADB-AIO for that if you don't have ADB and Fastboot Tools installed yet.
Anyways, once you have that, download my .rar file (Yes, .rar, install WinRAR if you don't have it, I won't use .zip in order to compress much more and save space and download time for you), and then run the "Moto Z Automated Flash.bat" file, it should do everything for you, but make sure to READ what I wrote in it, when it asks you to "Press Enter", please READ everything carefully, I will NOT explain further here, everything that you need to know is described and explained to you while you use the "Moto Z Automated Flash.bat" file as a form of guide.
In case you wonder, it is 3.5GB large because it contains the STOCK 7.0 ROM for the Moto Z (that you will flash first), and then the 7.1.1 ROM from erfanoabdi that you will flash through TWRP. It also contains TWRP (which will be flashed during the guide/bat file) and a logo.bin that covers over the stupid "N/A" at bootup.
RAR file download:
https://mega.nz/#!M9kCDQRQ!184HVnma8xGi1m0llqWcSSTdcYjLb9hToRSx0BkqwfI
Click to expand...
Click to collapse
Hi,
I tried to unlock bootloader following instruction on Motorola website then my moto z play has "BAD KEY" and keep restarting with that message on the screen. I found and used your file but it didn't help my device out of the "BAD KEY". Please help. Thank you
I can add your Moto e6 on here if you send me a copy of your recovery.img so o can port it it only takes me a few minutes now to port to new device I will be uploading more this weekend if you want one for your device send me your recovery.img and I will port it to you real fast
Thanks to A-Team Digital for all there help
This certainly works with usb mouse plugged into usb port. No touch otherwise.
I need 2 files from your device to get touch working
Let me know which ones and I will send them to you. Thanks.
Pick the 2 you need from these files
What carrier do you have what is the model number o have all the files I just need to know the model number and carrier please
I'm repacking a universal one with all the files for all models and carriers right now give me a little bit and I should have it uploaded
I have it built but can't upload it here too big of files in total it is just over 3gb but it adds something's to the system so you don't have to boot into recovery to get root and you have rw access in twrp and Android if you have a telegram let me know and I can send you the files on there if you like
If not I'm uploading them to google drive right now
I got the download size down to 1.6gb zipped and 3.3gb unziped that have to be flashed please read readme.txt
Here is the link to google drive it has 2 zip files download both and it has all the files you need to flash to device
Moto e6 - Google Drive
drive.google.com
Sorry for delay in getting back to you. First, I downloaded the zip files and the readme. Thank you. Second I have the latest version of the T-Mobile Rom, which, I believe, is very similar, if not identical to, the MetroPCS version you have. I will check out the readme file and let you know how it goes. Thanks again.
Okay. I reviewed your zip files and they are the ones from AIO. I looked at all of these files before and decided not to install them since it prohibited upgrading the firmware in the future. If these are required to have a touch-friendly TWRP recovery, then I will pass. I like my Moto E6 security updates too much. By the way, I admire the A-Team work.
They are not the same as there's I added the ability to update you just have to use magisk and go to update in settings and keep magisk after update you can get security updates for a while but moto is stoping updates on that phone next month
I just added a few lines to allow security updates because I started with there base and needed updates for my work phone
I change a few files in the recovery file but twrp will have touch but can not mount as rw or anything no back ups or nothing unless you go my route right now at least you get security updates
Thanks for the explanation. I think I will give it a try.
I tried it and I am now running my T-Mobile version fully rooted with a fully operating TWRP touch working recovery!
The system.img would not install, and that was a very good thing. It was not needed. Everything works. I have done full backups, including non-encrypted data, using the Batik-TWRP. I did update to Magisk 23 and that worked just fine as well. Thank you so much for finally giving us a way to fully root and backup this phone!
You are welcome sir Al software updates will work just remember to go in magisk manger and keep magisk after update
I have two moto e6:
1. XT2005-5 RETCA (bootloader unlocked & rooted with Magisk, but via recovery only)
2. XT2005-1PP Verizon version (Brand new state. Not even activated. But fastboot is available).
Both are with the newest stock rom for their channel (rescued by LMSA).
I followed the readme, but fastboot could not flash any image.
I got error like this:
Sending 'boot' (32768 KB) OKAY [ 1.279s]
Writing 'boot' (bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Can you make images if I upload boot, dbt, recovery?
Or can you show instruction to patch/modify images?
Also, I have tried to flash the stock ROM from RECTA onto Verizon version but failed (went into fastboot loop).
Then I tried to falsh back stock Verizon ROM, and failed, as well.
Yet, LMSA could flash the stock Verizon ROM.
Maybe we can copy patched images into LMSA Download folder (C:\ProgramData\LMSA\Download\RomFiles), over the stock ROM, and let it flash for us (probably depending on the "Preflash validation").