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
Related
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
Just after some advice on what is the best lean rom for the moto e?
I've swiped my Aunty's old Moto E to use as a music player. But with it only having 4 gb storage it wont even install the latest updated never mind let me add some music players to try.
So I thought I could flash it with a custom rom but there's so many I'm new to android and just getting myself confused. So could somebody point me in the direction of a decent debloated rom for the Moto E.
Thank you
Just use the debloated stock lollipop v5.1 it will be best for your usage.
Link for the lollipop ROM :-
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Ankit_29 said:
Just use the debloated stock lollipop v5.1 it will be best for your usage.
Link for the lollipop ROM :-
https://forum.xda-developers.com/moto-e/development/rom-stock-motorola-lollipop-rom-t3167111
Click to expand...
Click to collapse
Thank you, much appreciated!
Sorry,but how in hell do I install this? I have a bog standard moto e, not rooted or anything. I've flashed custom roms to a samsung using odin and twrp but this is just confusing me now. I've googled but I've no idea what bootloader is or how to unlock it and what andriod sdk is or wht i need it or how to use it.
Jerri1240 said:
Sorry,but how in hell do I install this? I have a bog standard moto e, not rooted or anything. I've flashed custom roms to a samsung using odin and twrp but this is just confusing me now. I've googled but I've no idea what bootloader is or how to unlock it and what andriod sdk is or wht i need it or how to use it.
Click to expand...
Click to collapse
Just check this video. Its too long but this guy not skipped any steps. He has done the job brilliantly.
Download the latest twrp recovery from here https://dl.twrp.me/condor/twrp-3.1.0-0-condor.img.html
Thanks, seem simple enough but I'm already stuck. Bootloader in unlocked, but when i boot into fastboot if I try to flash it says 'error: cannot determine image filename for 'recovery.img'' and if i boot into fastboot and go to recovery it says 'no command'
Jerri1240 said:
Thanks, seem simple enough but I'm already stuck. Bootloader in unlocked, but when i boot into fastboot if I try to flash it says 'error: cannot determine image filename for 'recovery.img'' and if i boot into fastboot and go to recovery it says 'no command'
Click to expand...
Click to collapse
He had one mistake. Just rename the twrp image "recovery" not recovery.img
Ankit_29 said:
He had one mistake. Just rename the twrp image "recovery" not recovery.img
Click to expand...
Click to collapse
Changed the name, now I get this error
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
3zero3 said:
I want to rollback to B190 to B150. Tried with /dload (B150 update.app), no success. Mostly because, there is no root on B190 with Kingroot. I did not tried Magisk, yet. Have to flash TWRP with ADB. Not likely to me.
So, is there any chance for downgrade?
Phone came with B150, upgraded to B170, then B181 and to B190.
Device is SCL-L01C432.
If You need more information, please tell me.
Click to expand...
Click to collapse
With the fastboot method if you have the bootloader unlocked, there are many tutorials on the net. But how did you rate an upgrade to the B170 ??
Androfish said:
With the fastboot method if you have the bootloader unlocked,
Click to expand...
Click to collapse
Unlock bootloader is the very first thing I did.
Androfish said:
there are many tutorials on the net.
Click to expand...
Click to collapse
But I am not really, really sure, which one will work with B190?
You mean flash custom recovery, custom ROM, then try to comeback to stock recovery and stock ROM?
Ok, looking now inside B190 update.zip and there is B190 recovery.img. (12.recovery.img in Huawei Update Extractor)
I see this with magisk:
https://forum.xda-developers.com/showpost.php?p=73838305&postcount=24
Should I try for B190?
Last version of KingRoot (5.3) is not working.
I found (on internet ) for some other Huawei phone, there is some special "middle package" (update.zip) to get the possibility for downgrade. Maybe I need that "special package"?
Androfish said:
But how did you rate an upgrade to the B170 ??
Click to expand...
Click to collapse
With Firmware Finder.
There is update (for me) numbered under #63737.
Update from:
SCL-L01C432B150CUSTC432D008
to:
SCL-L01C432B170CUSTC432D004
Put in /dload and update.
Have not used much B170, but B190 work smoothly.
You just have to download the b150 version and after extracting with Huawei extract the necessary files including the recovery stock, make the flash with fastboot:
fastboot system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust .img
quick reboot
I followed Your instruction for fastboot.
Boot, recovery, system flashed. Cust cannot be flashed. They are from B150.
Code:
target reported max download size of 266338304 bytes
sending 'cust' (194411 KB)...
OKAY [ 6.275s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.283s
Tried to flash whole B150 (UPDATE.APP) with:
Settings -> Updater
EMUI Updater (Volume Up + Volume Down + Power)
Project Menu -> Update (it mean *#*#2846579#*#*)
Nothing work.
Now I have "half" B190 and "half" B150 in my phone.
Is there any way to flash whole B150 (UPDATE.APP)?
Please? Anybody?
Have weird problems, like i cannot remove widgets, launcher crash sometimes, etc...
I do not know is there any downgrade package? Or something?
Maybe I need SCL-L01C432B190CUSTC432D002 firmware? If exist?
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
---------- Post added at 09:20 AM ---------- Previous post was at 09:14 AM ----------
Androfish said:
Given that I still do not understand how you have run the B190 version on this device, try to install this version always with the fastboot method: http: //huawei-firmware.com/rom/huawei-y6/scl-l01/1027
After install any other updated B150 version and it should work.
The cust.img file I do not know why but it does not work with fastboot.
Click to expand...
Click to collapse
Rom: http://huawei-firmware.com/rom/huawei-y6/scl-l01/1027
Since TWRP is still not ported to V10, so i decided to make a prerooted-boot.img.
Download Link
You can flash this boot.img to root your Honor V10 AL20C00 (6GB+128GB China Edition) on stock firmware (B132)
Usage:
0. Unlock bootloader and close find my phone.
1. Power off your phone
2. Plug your phone to computer
3. Hold power and volume down until boot into fastboot mode
4. flash this boot.img by adb ( fastboot flash ramdisk boot-root-b122.img), please download adb by yourself
5. reboot (fastboot reboot)
Your phone may reboot twice, and you'll get root access.
Declaim:
I only test this on my own phone (BKL-AL20C00), Use this on your own risk. I'm not responsible for your phone's damage.
using this tool means you accept this.
Thanks:
HRT-Lin
@mankindtw for his Mate-10 root boot.img
cofface for his bootimg.exe to unpack and repack boot.img
@worstenbrood for his Huawei Update Extractor
Does this root work on stock BKL-AL20 8.0.0.132 update?
Same question. I got BKL-L09 8.0.0.120
No bootloader unlock needed? And i also hope, someone can confirm this on BKL-09 - 120 .
They didn't lock bootloader? Already preorder international unit
Hi,
Can you be a little more specific? Did you unlock your Bootloader first? When you say stock firmware B132, do you mean version 8.0.0.132 ? Thank you in advance for your reply!
Custom Recovery for V10
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
I'm hesitant to try this without more information
harshshah17 said:
Hi ppl. Has a custom recovery been ported for the V10. I have managed to root my phone using the above method, but since there is no custom recovery available, I am unable to flash any mod / roms, etc.
Click to expand...
Click to collapse
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
piphol said:
Hi harshshah17,
Did you unlock your bootloader first? I think there are methods to flash zip files without having a custom REC. Try Flashfire apk. I've read the phone can get even more "restricted" (many features get blocked) once you root your Honor V10. Is it true in your case? Thanks in advance for your reply.
Click to expand...
Click to collapse
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
harshshah17 said:
Ofcourse i have unlocked my bootloader..Its only after that, that you can root. With regard to your question, I have not experienced any sort of "restriction" with my Honor View 10 post rooting. Seems to be working just as normal. The only thing is that i am unable to install the OTA update.
The reason I am asking for a custom recovery is because i need to remove Super SU and install Magisk instead. In order to remove super SU i need to flash an uninstall zip (I know you a can remove it from the Super SU options, but that doesn't seem to be working). I can certainly use flashfire to flash the uninstall zip but then my phone will be unrooted and I wont be able to flash magisk via flashfire.
If anyone has a solution for the above, suggestions will be appreciated. Thanks!
Click to expand...
Click to collapse
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Only thing I've seen that doesn't work with root is face unlock. Also how can I flash magisk since there isn't a recovery yet. Can I use flashify?
Yut kill
dawnc said:
U can remove root by flashing the stock ramdisk.img, which can be extracted from the official full-ota update.app
Click to expand...
Click to collapse
Where can you find the full OTA?
whymista said:
Where can you find the full OTA?
Click to expand...
Click to collapse
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. ?
piphol said:
Download Firmware Finder for Huawei in Play store. They got partial and full OTAs there.
By the way, flashing custom ROMs for V10 is now also thru Fastboot. So I guess TWRP isn't applicable for V10? Maybe Magisk can also be flashed using Fastboot. I will try to research for custom ROM with Magisk. So far, I only see SuperSU pre-installed. [emoji25]
Click to expand...
Click to collapse
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
whymista said:
I did download that and the extractor tool but it says I need the update.app file to extract the boot image an I've yet to find that in either of the three files I tried.
So I know how to use fastboot but will I need the boot image first or can I just flash magisk. The current root method installs su. That's where I'm kind of stuck as far because I've always read that you have to uninstall su first but then wouldn't I lose the ability to flash magisk? I'm currently just rooted on the stock rom.
Didn't even know there was a custom rom hadn't seen it on here yet.
Yut kill
Click to expand...
Click to collapse
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
piphol said:
Do you have BKL-AL20? Here's a non-rooted boot image. I'm not sure if it can be used on other variants / versions. If you have another variant, I can find it for you.
BOOT_BKL-AL20_B132
https://mega.nz/#!Ps4jjIqJ!ssiYej9BAu6kZJZ8RfC8P1JDoyo9Ox36o42i8SMm1Lw
Credits to the custom ROM developer KangVIP for the boot image.
Click to expand...
Click to collapse
I have the bkl-l09. I'd appreciate it if you could. I'll try this version since it can't hurt though.
Sent from my ONEPLUS A5000 using Tapatalk
So I tried to flash it through adb and it didn't work this is what I got.
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
PS C:\> fastboot flash boot C:\Users\charl\OneDrive\BOOT_BKL-AL20_B132\BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.362s]
writing 'boot'...
FAILED (remote: partition length get error)
finished. total time: 0.385s
---------- Post added at 03:45 PM ---------- Previous post was at 03:40 PM ----------
I'm trying to use the recovery tool they have that says I need 5 different files but I've no idea where to find them like the system img etc.
Sent from my ONEPLUS A5000 using Tapatalk
This is what it's saying I need to unbrick
{
"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"
}
Sent from my ONEPLUS A5000 using Tapatalk
whymista said:
This is what it's saying I need to unbrick View attachment 4405892
Sent from my ONEPLUS A5000 using Tapatalk
Click to expand...
Click to collapse
It should be "fastboot flash ramdisk <boot image name>".
Second, if it doesn't help, the next step is to enter e-recovery mode. Press Volume Up + Power for 15 seconds. Follow the prompts and it should download the full OTA for you. I think you need your Huawei ID in the process (and a good Wifi signal).
Lastly, I think this is a sure bet but will cost you, google "funkyhuawei honor v10 rebranding guide". You will find a reddit link. They are the only team who "holds" BKL-L09 Full OTA roms that I know of. You need to buy "credits" to download OTAs and unbrick your phone. Unfortunately, team MT (team behind Firmware Finder) hasn't got a hold of a full OTA of BKL-L09.
From my experience, the first suggested solution should already work. I hope you don't get to the third solution.
Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
tekin96 said:
Hi, After updated my Moto Z (XT1650-03) to oreo from OTA, I unlocked the bootloader in order to root phone. But I couldn't root the phone. And it did not boot. Then I flashed stock 7.1.1 (GRIFFIN_NPL26.118-20-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) and the phone turned on. The phone does not power up after I try to install OTA updates. No reaction. Is it hardbrick ?
Click to expand...
Click to collapse
hi dude, mmm i have a similar problem, so i think you have a hard bricked device. My moto z doesnt power up and doesnt charge it is dead
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Hi I have the same problem, I had Nougat 7.1.1 update to version 8.0 and make a drowngrade to 7.1, then I received an update of the security patch, it was then when it was Hard Bricked (no power up no charge) , I thinkneed a blankFash for the version of Oreo. do you think the flash did you used from the message you mention would?.
Thanks in advance
JohanSjogren said:
I had a similar problem after a failed downgrade from Oreo to Nougat. My phone was bricked over a month but it works now since the factory image of Oreo is out. I had earlier had a working blankflash but due to security limits I wasn't able to flash anything that would downgrade the system (so nothing really).
The blankflash file I found in the unbrick guide a while ago. Erfanoabli posted the Blank flash file but I'm not sure on witch page but it should be the latest version you can find.
The factory image I found in Android Oreo update -chanels- thread on page 37, and should work for every device except RETCN apparently. I unpacked the zip and flashed it in fastboot after I booted up to fastboot with the blank flash file.
Worked like a charm!
It still says RETEU when I go to settings.
Now I can stop using my backup phone!
I can't post any links unfortunately since I'm not a senior member.
PS. If you want to root Oreo you have to be careful! Read the guides. Otherwise you might get a bootloop.
Click to expand...
Click to collapse
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
tekin96 said:
Erfanoabli's blankflash works for me too. Can you please help me about what Im going to do ? I dont want to do someting wrong.
Edit : Now My phone powers up on Stock Oreo!! Firstly I flashed gpt.zip. After I flashed GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Thank you so much.
Click to expand...
Click to collapse
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Scugy said:
Hi ,
Im trying to flash back to stock oreo but using the same GRIFFIN_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml package i cannot flash the boot.img i keep receiving this message :
C:\Temp\Tools\platform-tools>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (32768 KB)...
OKAY [ 0.107s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.834s]
finished. total time: 0.943s
any ideas ?
Click to expand...
Click to collapse
Firstly you should flash gpt.zip which is in 15 page of [GUIDE] Unbrick hard bricked Moto Z topic. After that you can flash the stock oreo.