Related
So, here is the problem i am facing with my moto E
I followed the tutorials from this site and had flashed my MOTO E to stock ROM 3-4 times due to different reasons, i was successfully able to do that using the STOCK ROM that i had for android kitkat 4.4.4. Last month i updated my moto E to android lollipop. After that it kept asking me to install a 12MB update which i tried installing quite some times but was not able to install. It showed some error while installing the same. So, i started ignoring that. A couple of days ago i once again tried to install that update and after installing the update when the phone turned on, it logged on into FASTBOOT MENU saying:
hab check failed for boot
failed to validate boot image
Fastboot reason: Fall-through from normal boot mode
So, i thought Flashing it once again might solve the issue. When i tried flashing it, on the command screen it gives ERROR for 4 files i.e. boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 saying::
<bootloader> invalid signed image
<bootloader> preflash validation failed
And on my phone screen it says "Invalid PIV signed image"
For all other instructions it says OKAY
Now it is again and again turning ON into this fastboot mode only...
Since i already had flashed my moto using the same custom rom , i think the files must be okay...
PLEASE HELP :'(
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
-z3r0- said:
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
Click to expand...
Click to collapse
sorry, i didn't knew that i shouldn't update my phone after installing the stock rom. No i haven't tried flashing my phone with android 5.1 stock file, i thought maybe flashing my phone with android 4.4.4 will downgrade my phone back to kitkat. Will try it now...will be helpful to me if you could get me a link for android 5.1 stock file as well, i tried finding the same, but it says for moto e2 which comes originally with lollipop but mine comes with android 4.4, its so confusing for me which stock file to download....
thanks for the help
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
-z3r0- said:
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
Click to expand...
Click to collapse
tried it, still giving the same error, preflash validation error :'(
Please kindly respect others work and Remember to say THANKSNEW as of 16th October 2016Background:
After much trial and error I finally found a method that allows us to have a fully functioning MM (6.0) which is rooted and has a working custom recovery.
Be sure to Follow the instructions very carefully. I do not write these tut's so you can skip parts of it or ignore what is being said. If you fail or do not understand a certain step then simply ASK!! All steps are critical for success.
Choose the download (at the bottom of this post) which is for your device ONLY do not flash others!! thinking it will work.
If you do not see your C4/C5 device listed then please upload the MM boot.sin only for your device stating the model and device number (C5 Dual E5xxx)
Please use a quality upload site with no spam like Mega, OneDrive, GoogleDrive, etc etc
First you need to get back to a full clean factory 5.1 this is called "Rolling Back" and to achieve this we will first need to use FashTool
You must of already done an official Sony bootloader unlock before on LP or MM and used the exact same FlashTool with the unlocked bootloader at least once.
To explain FlashTool takes a copy of your Unlock codes and TA by default and saves it then the next time you use FlashTool You simply hit BLU to lock or unlock the bootloader.
Tools:
FlashTool: FlashTool-0-9-19-8-windows.rar
Download Here
flashtool-0.9.19.8-linux.tar.7z
Download Here
Fastboot
1. Using Flashtool lock your bootloader and then flash as much as possible of the old 5.0 firmware.
For those who's devices never had 5.0 then see this post here http://forum.xda-developers.com/showpost.php?p=69201203&postcount=33 which explains that you need to flash the earliest version of 5.1 possible!
2. After this you can use the “Update” function to receive the OTA update which will put you on 5.1
Thanks to @Kenzi BNH for this tip.
2a. If you have followed THIS small tut and used Xperia Companion tool to achieve the same state then that’s also fine. (Note: It has been reported that the latest version of Xperia Companion Tool no longer does incremental updates and will now put you on the Latest Android version for your device but the above way via OTA's still works)
Note: The above methods are the ONLY ways to achieve this. Thinking you can skip or miss the above will lead to a failed root You have been warned!
3. Now using FlashTool Flash only the MM boot.sin, oem.sin, userdata.sin and system.sin which is made for your device.
Do not flash any other parts for now as more testing needs to be done with other partitions.
4. You should now reboot back to system and check all is working as it should.
(Note: I had to manually download/set my carrier's apn as the MM apn.config is in the oem partition which I did not want to flash until I had got root)
5. When you're happy all is working go to your Internal and external Sdcard and rename any “TWRP” folders to oriTWRP
6. Now copy the Exxxx-boot.img and SuperSU in the .zip (files attached below) to the root of your Internal Sdcard.
7. Using only FlashTool UNLOCK your bootloader.
(NOTE: It is very important that you only use FlashTool for this procedure as unlocking the bootloader via Fastboot seems to put a FLAG in one of the partitions (I suspect secro or sec-cfg) thus causing the issues with LockScreen & Security FC's in MM.
8. Now you need to re-flash TWRP recovery via Fastboot “fastboot flash fotakernel fotakernel.img”
The recovery's are in this post http://forum.xda-developers.com/showpost.php?p=64633893&postcount=3 under the heading “DOWNLOADS HERE:”
9. IMPORTANT: After you have flashed the recovery manually reboot to the recovery using the buttons.
“Press and keep held the Volume Down key (-)
Now Press and hold Power Key until you see the Sony Boot Logo then release the Power Key only.” When the recovery boots It will Ask if you want to keep the the system Read Only YOU MUST SAY YES
10. Now from the TWRP menu select install and select “image” find your custom Exxxx-boot.img and flash it to “boot” Then go back to the Reboot menu and select “recovery” Make sure to choose Read Only option again on reboot.
11. Now select install and flash the SuperSU after it has done and hopefully without any errors reboot to system.
12. If everything has worked you are now rooted and can carry on as before. :victory:
13. Rename your "oriTWRP" folders back to “TWRP” note That you can now mount the system read write again by using the swipe button if TWRP asks you.
14. Give THANKS, feedback and any suggestions.
IMPORTANT UPDATE NOTE: Firmware versions dated 2018 need the boot.sin repacking due to changes Sony made so if you are using a 2018 firmware you will need to upload the boot.sin giving full details of the device Model, firmware version and date. Without this info I will do nothing and ignore your requests also use a NO spam upload site like google drive, mega, etc etc
Downloads:
C5-single-E5506-MM.zip https://mega.nz/#!zEByjIyK!KmiG1i72nHD7_vFfwlVjg6__Kw2c4KESLxbKi32E0YY
C4-single-E5303-MM.zip https://mega.nz/#!mJx2zBZS!CNV21CB39HiqERxg5XRej2nHNu4ssX4MO4ovFt1zygg
C4-dual-E5333-MM.zip https://mega.nz/#!TUZUhQRB!zjOr6xK4JkexN8GSyn2tdw-Fbw5Urt0sk23OVDirQr4
C4-dual-E5363-MM.zip https://mega.nz/#!eFx2UBLb!0WkR4uOGuD0opyMTzRBELmKkXCtalTuKKat6G7pgyU4
C5-single-E5553-MM.zip https://mega.nz/#!WAwyFRqa!cF_Q01UlWCAFGRajMYje7Yo3ddzdu08AAi1b9u81w40
C5-dual-E5563-MM.zip https://mega.nz/#!XQoAybTS!xMMHqml7fd0xEo7WoH7ryabixyDAZGeLIiRvXIqb9oY
C5-dual-E5533-MM.zip https://mega.nz/#!qJA2EL5I!NAppeYx61Ev_71RLu7GCtSk8Dx-dxeA8mY6t_uJ0jT8
C4-?-E5353-MM.zip https://mega.nz/#!zIBlwbqC!GZ0jjihinEDgR1hT9jvh3N6l0hdBzcqizoBA9LemkCE
Be sure to check the download name as I have had to update all the links.
Credits/Thanks:
For testing the method.
@Kenzi BNH
WARNING Some people are recommending using a later FlashTool version than what I recommended. So just to be clear I DO NOT RECOMMEND USING ANY OTHER VERSION than the one I have linked above.
The FlashTool Website also says not to use it so you have been warned.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can't seem to edit my OP
Link Clean up
reserved
Thanks but what I had in mind
Does not work as it make's you reformat data after flashing the userdata partition via fastboot it says "un-encrypt failed your password is correct your userdata is corrupt please factory reset" although I have not set any passwords :crying:
SuperSU did the mod to the boot.img so dm verity and forceencrypt should be disabled.
Man Sony screwed this down tight as they seem to have all the angles covered.
I have one more thing to try then that's it for me as I have spent far too much time on this already :silly:
bigrammy said:
Does not work as it make's you reformat data after flashing the userdata partition via fastboot it says "un-encrypt failed your password is correct your userdata is corrupt please factory reset" although I have not set any passwords :crying:
SuperSU did the mod to the boot.img so dm verity and forceencrypt should be disabled.
Man Sony screwed this down tight as they seem to have all the angles covered.
I have one more thing to try then that's it for me as I have spent far too much time on this already :silly:
Click to expand...
Click to collapse
What about this systemless root method?
gsser said:
What about this systemless root method?
Click to expand...
Click to collapse
:laugh:
Ok to put it simply since there seems to be a lack of dev's for this device.
1. If you flash MM by FlashTool it will only flash certain areas of the device it does not flash secro preloader lk etc etc.
Which is fine and you can still have a working MM and keep your custom recovery :good:
The downside is that certain things will not work such as anything in Settings/Lock Screen & Security as this just crashes when you try open it.
I am sure as time goes on more things will become apparent so it's not an ideal situation.
2 If you flash MM by Xperia Companion it will flash all areas of the device.
After this your are left with a locked bootloader which will not FULLY unlock again so stops you from booting a custom recovery (Note we have no oem unlock option in the setting menu like the XA has)
The reason I say FULLY is because it allows the booting of a modded boot.img to work unhindered
I am unsure if a prerooted system.img would be allowed to boot or not has I have not tried that yet but it would cause problems with many apps such as banking and pay per view stuff like Sky etc etc so not an ideal solution even if it worked.
Trying to do a systemless root without any real access and no custom recovery is pretty hard trust me I have been trying for a few days now
Access via userdata failed
Access via oem failed
so I have a couple more things to try and then I will give up for now.
MM is good but we definitely need rood and recovery... I miss dolby atmos and pdesire
Im gonna use MM for 2 3 weeks then flash back to lp
Try to install the recovery and SuperSu on 5333 MM.
Unlock the bootloader with Flashtool v0.9.22.3
insatll the recovery, the phone boot into recovery then i flashed SuperSu.
Android can't boot !
BOOTLOOP
Hi Nothing news...
Repair with xperia companion put me on MM
After unlocking the bootloader with flashtool.
install the recovery.
But the phone doesn't want boot into the recovery... (Sony Xperia screen)
After 10 sec, the phone reboot into Android. :crying:
---------- Post added at 09:02 PM ---------- Previous post was at 08:43 PM ----------
Code:
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
(bootloader) secure: no
(bootloader) version-baseband: 1292-1559_27.3.B.0.122
(bootloader) version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_208
(bootloader) serialno: NONEEDTOKNOW
(bootloader) product: E5333
Kenzi BNH said:
Hi Nothing news...
Repair with xperia companion put me on MM
After unlocking the bootloader with flashtool.
install the recovery.
But the phone doesn't want boot into the recovery... (Sony Xperia screen)
After 10 sec, the phone reboot into Android. :crying:
---------- Post added at 09:02 PM ---------- Previous post was at 08:43 PM ----------
Code:
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
(bootloader) secure: no
(bootloader) version-baseband: 1292-1559_27.3.B.0.122
(bootloader) version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_208
(bootloader) serialno: NONEEDTOKNOW
(bootloader) product: E5333
Click to expand...
Click to collapse
You can get back to 5.1 by following this http://forum.xda-developers.com/showpost.php?p=68922853&postcount=146
So MM has this Bootloader version : version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_208
I was able to build an MM ftf file using the files from the Boot folder of an LP download.
Flashed it with no problems, and MM ran fine.
(bootloader) secure: no
(bootloader) version-baseband: 1292-1552_27.3.A.0.122
(bootloader) version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_106
But I couldn't install TWRP using fastboot.
I kept getting an error "flash write failure"
fastboot flash fotakernel fotakernel.img
target reported max download size of 134217728 bytes
sending 'fotakernel' (13126 KB)...
OKAY [ 0.464s]
writing 'fotakernel'...
FAILED (remote: flash write failure)
finished. total time: 0.481s
Is this of any use in getting Recovery and full root?
eoink said:
So MM has this Bootloader version : version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_208
I was able to build an MM ftf file using the files from the Boot folder of an LP download.
Flashed it with no problems, and MM ran fine.
(bootloader) secure: no
(bootloader) version-baseband: 1292-1552_27.3.A.0.122
(bootloader) version-bootloader: 1292-1556 S1_Boot_MT6752_TC9SP_106
But I couldn't install TWRP using fastboot.
I kept getting an error "flash write failure"
fastboot flash fotakernel fotakernel.img
target reported max download size of 134217728 bytes
sending 'fotakernel' (13126 KB)...
OKAY [ 0.464s]
writing 'fotakernel'...
FAILED (remote: flash write failure)
finished. total time: 0.481s
Is this of any use in getting Recovery and full root?
Click to expand...
Click to collapse
In MM
When we go into the Service Menu
( *#*#7378423#*#* )
We can see a new information only in MM
Remote Lock State: Locked
(See Screenshot)
Don't know what is it ! :silly:
alright,, im ready to help and back at lp 5.1 . now @bigrammy what do i need to do ?
C5 ultra E5553
gsser said:
alright,, im ready to help and back at lp 5.1 . now @bigrammy what do i need to do ?
C5 ultra E5553
Click to expand...
Click to collapse
Hi @gsser
See this http://forum.xda-developers.com/showpost.php?p=69118369&postcount=170
If we don't care about TWRP/custom bootloader is there still a way to achieve #root access on 6.0 MM for C5 Ultra? Or are we stuck on 5.X LP until/if someone can figure this out? Thanks for reading.
[Like will third party foreign rooting tools such as kingroot fail / SuperSuMe etc, not worth the update to MM for me if I'll lose root... thanks again XDA]
Darkshades said:
If we don't care about TWRP/custom bootloader is there still a way to achieve #root access on 6.0 MM for C5 Ultra? Or are we stuck on 5.X LP until/if someone can figure this out? Thanks for reading.
[Like will third party foreign rooting tools such as kingroot fail / SuperSuMe etc, not worth the update to MM for me if I'll lose root... thanks again XDA]
Click to expand...
Click to collapse
Please wait a TUT
Be patient :angel:
M nt getting 5.0 firmware for India generic... What can I do? Can I flash different region 5.0 like other than India???? will it work?? PLZ rly
sauaditi said:
M nt getting 5.0 firmware for India generic... What can I do? Can I flash different region 5.0 like other than India???? will it work?? PLZ rly
Click to expand...
Click to collapse
I don't see why not
You could just try it and see what happens. :fingers-crossed:
You can always reflash flash your own device .tft but if it does not work or you could always use Xperia Companion Tool to repair the phone firmware.
PS: I cannot guarantee anything and everything you do is at your own risk also to lower any risk make sure you use the flashtool version in the op.
Hi bigrammy.. I searched on google..Sony c5 ultra E5563 in India doesn't come with 5.0...it was come with 5.1 lollipop.. Version 29.1.B.0.87, and then got update 5.1 version 29.1.B.0.101
So no 5.0 firmware for E5563
Now NO 5.0 so what can we do? For root on MM need 5.0? Is it compulsory? Can't I flash 5.1 instead of 5.0 and follow root procedure for MM?
PLZ rly
sauaditi said:
Hi bigrammy.. I searched on google..Sony c5 ultra E5563 in India doesn't come with 5.0...it was come with 5.1 lollipop.. Version 29.1.B.0.87, and then got update 5.1 version 29.1.B.0.101
So no 5.0 firmware for E5563
Now NO 5.0 so what can we do? For root on MM need 5.0? Is it compulsory? Can't I flash 5.1 instead of 5.0 and follow root procedure for MM?
PLZ rly
Click to expand...
Click to collapse
Just flash the Version 29.1.B.0.87 then update via OTA which should put you on 5.1 version 29.1.B.0.101 which is fine for the tut. (They do not normally skip any OTA updates so you will get them incrementally)
Just make sure not to accept the 3rd update which would put you on 6.0
Make sure your bootloader is relocked with FlashTool
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
TWRP for the Moto E4 Plus (Qualcomm)
Based heavily on squid2's TWRP device tree for the Moto E4 (Qualcomm) - See here for more information.
Seems to work fine, but use at your own risk, std_disclaimer.h, etc.
Use fastboot to test or boot this recovery.
To test:
Code:
fastboot boot recovery.img
To flash:
Code:
fastboot flash recovery recovery.img
XDA:DevDB Information
TWRP for Moto E4 Plus Qualcomm (owens), Tool/Utility for the Moto E4 Plus
Contributors
ReimuHakurei, squid2
Source Code: https://github.com/ReimuHakurei/twrp_device_motorola_owens
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-10-30
Created 2017-10-30
Last Updated 2017-10-30
Has any one tried this? Does that mean it can be rooted as well? I thought the bootloader had to be unlocked which is not available with qualcomm e4 plus?
shezzy83 said:
Has any one tried this? Does that mean it can be rooted as well? I thought the bootloader had to be unlocked which is not available with qualcomm e4 plus?
Click to expand...
Click to collapse
I have a model from Sprint, and it's unlockable, just not on the official list -- I successfully unlocked mine.
Rooting is also possible -- use phh's; SuperSU doesn't seem to work: https://superuser.phh.me/superuser-r259.zip
https://play.google.com/store/apps/details?id=me.phh.superuser&hl=en
Got Root on Qualcomm E4 plus! ( BOOST MOBILE )
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
So what will it take to make this TWRP official and available on the TWRP website?
I am willing to help make it go official on their website.
shezzy83 said:
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
Click to expand...
Click to collapse
I just followed this guide on my XT1775 and apart from having some minor issues unlocking (had to run fastboot flashing unlock in addition to the fastboot oem unlock) I'm now unlocked, have twrp installed and rooted.
Thanks all! Can't wait to see what comes next
do anyone know where I can get stock boost mobile firmware for this phone
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
shezzy83 said:
Just tried this on my Boost Mobile E4 plus and it worked. I also used the the no-verify zip and Magisk 14.0 to root.
Can use this guide and just swap out the twrp.img with the recovery.img from this thread:
https://forum.xda-developers.com/moto-e4/how-to/moto-e-guide-to-rooting-t3652982
Click to expand...
Click to collapse
thinking about buying this phone at it seems to be boosts easiest rootable phone. did network access persist? and do you still have 4g access and such? or any issues in general.
Has anyone had trouble flashing this? I have the owens XT1775 16GB P3A and can test boot into twrp fine but when I try to flash it comes up with the following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10258 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.387s]
finished. total time: 0.762s
I know it says Image not signed or corrupt but the md5 is correct even after DLing it twice.
mdgiest231 said:
thinking about buying this phone at it seems to be boosts easiest rootable phone. did network access persist? and do you still have 4g access and such? or any issues in general.
Click to expand...
Click to collapse
No issues at this point on boost mobile after I rooted. Only issue I had was I made a backup in TWRP but had to put it on a sdcard since the phone stock doesn't have enough room to store it. The problem came with that the backup I made wasn't visible on the card when connecting to my PC unless I was in recovery mode. This may just be a TWRP issue but I don't know. Haven't tried xposed yet. Busy box wouldn't install.
ReimuHakurei said:
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
Click to expand...
Click to collapse
I for got how to flash with fastboot can you please help me out thanks I usually use a tool kit when have to do this so I don't mess it up but now that my phone is basically a brick it don't matter
Chad The Pathfinder said:
Has anyone had trouble flashing this? I have the owens XT1775 16GB P3A and can test boot into twrp fine but when I try to flash it comes up with the following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10258 KB)...
OKAY [ 0.375s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.387s]
finished. total time: 0.762s
I know it says Image not signed or corrupt but the md5 is correct even after DLing it twice.
Click to expand...
Click to collapse
That message is normal -- as long as your bootloader is unlocked, it should work fine.
Has anyone here tried Xposed on this device? I am interested in gravitybox and maybe xprivacy modules.
just a heads up, unlocking the bootloader, installing TWRP, and then Magisk 14.0(14.3 beta will pass safety net) is enough to root the xt1775
ReimuHakurei said:
You probably want the Sprint firmware: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The Retail firmware will also work: https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Retail firmware has none of the Sprint bloatware. Flash with fastboot.
Click to expand...
Click to collapse
Is there any good guide for flashing the stock ROM? I can't seem to find any.
Edit - I found a version of RSD Lite that works on windows 10 and flashed the Retail ROM that way. I've been out of the android world for a while so I'm refreshing myself on stuff.
Bobboman said:
just a heads up, unlocking the bootloader, installing TWRP, and then Magisk 14.0(14.3 beta will pass safety net) is enough to root the xt1775
Click to expand...
Click to collapse
Thanks for the heads up on Magisk 14.3 beta passing safetynet! I love being able to dl things like netflix from the playstore now.
soaringowl2145 said:
Has anyone here tried Xposed on this device? I am interested in gravitybox and maybe xprivacy modules.
Click to expand...
Click to collapse
I just tried and got a soft brick. Have Twrp, magisk and substratum running well. Just no busybox or xposed yet. Perhaps personal error
xhan145 said:
I just tried and got a soft brick. Have Twrp, magisk and substratum running well. Just no busybox or xposed yet. Perhaps personal error
Click to expand...
Click to collapse
How did you get substratum to run?
shezzy83 said:
How did you get substratum to run?
Click to expand...
Click to collapse
With permission I want to post like a compete guide for root, BusyBox etc so it's all in one place. I'm doing a bit of cleaning but I can either pm or make a subject and the compendium! I don't want credit just want it to be easier for us e4+ peeps
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