Perhaps this guide will help fellow YU's users who want to downgrade their YU from Lollipop to KitKat (OR FROM OTHER ROMs UNDER THE SAME PARTITION TABLE):
Download KitKat fastboot images from HERE.
Download fastboot.zip from HERE.
Extact all zips in ONE EMPTY FOLDER.
Open "Terminal Window" from the folder where you extracted all the zip files (right click your mouse and choose "Open command window here"):
{
"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"
}
Put your phone into fastboot mode (disconnect the phone from PC, turn off the phone, and connect the phone to PC WHILE PRESSING VOLUME UP BUTTON).
After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback:
Code:
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf erase modem
fastboot -i 0x1ebf erase boot
fastboot -i 0x1ebf erase recovery
fastboot -i 0x1ebf erase aboot
fastboot -i 0x1ebf erase abootbak
fastboot -i 0x1ebf erase hyp
fastboot -i 0x1ebf erase hypbak
fastboot -i 0x1ebf erase rpm
fastboot -i 0x1ebf erase rpmbak
fastboot -i 0x1ebf erase sbl1
fastboot -i 0x1ebf erase sbl1bak
fastboot -i 0x1ebf erase tz
fastboot -i 0x1ebf erase tzbak
fastboot -i 0x1ebf format system
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf flash modem NON-HLOS.bin
fastboot -i 0x1ebf flash sbl1 sbl1.mbn
fastboot -i 0x1ebf flash sbl1bak sbl1.mbn
fastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
fastboot -i 0x1ebf flash abootbak emmc_appsboot.mbn
fastboot -i 0x1ebf flash rpm rpm.mbn
fastboot -i 0x1ebf flash rpmbak rpm.mbn
fastboot -i 0x1ebf flash tz tz.mbn
fastboot -i 0x1ebf flash tzbak tz.mbn
fastboot -i 0x1ebf flash hyp hyp.mbn
fastboot -i 0x1ebf flash hypbak hyp.mbn
fastboot -i 0x1ebf flash boot boot.img
fastboot -i 0x1ebf flash recovery recovery.img
fastboot -i 0x1ebf flash system system.img
fastboot -i 0x1ebf reboot-bootloader
fastboot -i 0x1ebf oem unlock
fastboot -i 0x1ebf format userdata
fastboot -i 0x1ebf format cache
fastboot -i 0x1ebf reboot
Welcome back to KitKat, easy wasn't it.
Hi Quakze, could you post this procedure at YU's official forum website, as I don't have access there. I'm hopping that more YU's owner will help our mission in forcing official from YU Televentures to release all source code, include all Qualcomm signed mbn files.
------------------- Edit ----------------------
Since a lot YU's users in this thread have been insisting for a simple FLASH_ALL.bat file, so here is it. Extract it to the same folder you extracted fastboot.zip and KitKat fastboot images. However, please keep in mind that I don't recommend to use the bat file, and I am not responsible for bricked devices.
Does this really work?
rahulsingh616 said:
Does this really work?
Click to expand...
Click to collapse
Yes, of course, but please do the guide in order.
is bootloader unlock is mandatory??
Anybody tried that?!
will it hard brick the device??
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
jogson said:
i heard that infact i myself hard bricked before while downgrading from lollipop to kitakt..
Click to expand...
Click to collapse
Just tried it works perfect thanks bro @tirta.agung
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Sent from tomato using Tapatalk
baggu1984 said:
is bootloader unlock is mandatory??
Click to expand...
Click to collapse
Yes, you can't flash anything with a lock bootloader.
3andala said:
Just tried it works perfect thanks bro @tirta.agung
Click to expand...
Click to collapse
Thanks 3andala, I'm happy to help.
roy92 said:
Uh a few screenshots of this working would be better since most official mods of yuforums advise against using fastboot when upgrading from KitKat to lollipop and downgrading from lollipop to KitKat. If this works then it is really great work. Thank you. I can now try lollipop and go back to KitKat if not happy with it.
Click to expand...
Click to collapse
What kind of screenshota that you need? I'll be happy if I could help you.
tirta.agung said:
Thanks 3andala, I'm happy to help.
What kind of screenshota that you need? I'll be happy if I could help you.
Click to expand...
Click to collapse
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
roy92 said:
It works for 3andala. I guess that is proof enough. Thank you for finding a clean way to revert to KitKat.
I guess you could upload desktop screenshot of the cmd window with executed commands. A photo of device first running on Lollipop and then on KitKat would be great.
Also did you try flashing cm 12 ota again after going back to KitKat?? Does it work??
Sent from tomato using Tapatalk
Click to expand...
Click to collapse
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
tirta.agung said:
Hahahahahah, you won't believe this, but I'll post the screenshots tomorrow.
Click to expand...
Click to collapse
Thank you[emoji5]
It's just that many bricked devices are floating around and not being able to properly revert back and forth to 32 bit builds and 64 bit builds is the only reason I haven't upgraded to lollipop yet.
KitKat is still the best with full xposed support and arm v7 is better supported by media players.
Sent from tomato using Tapatalk
Request
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
It's very easy to do so. But not recommended. Read OP's post again. You need to get OK confirmation after every step before moving on to next. So suppose a command to erase system fails but the script proceeds to flash system image it might brick your device.
The chances of this happening are very very low. But it is important that you follow the step of commands exactly and also get OK confirmation that every command is successfully executed.
Edit: To quote the OP:
tirta.agung said:
[*]After the phone is connected go to the "Terminal Window" you have opened previously, type all the command below (ONE LINE AT A TIME) and make sure you get an "OKAY" feedback
Click to expand...
Click to collapse
Sent from tomato using Tapatalk
Points to remember?
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Awesome!
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
onlyoneaamir said:
Can you make a file like flash-all.bat to do everything automatically other than typing the commands?
Help appreciated
Click to expand...
Click to collapse
Nope, i don't think so. But, if you want to try it for yourself, just copy all commands to a text editor, for instance notepad or notepad++, and save it as flash-all.bat.
technowizard99 said:
I'm running official cm12 updated via ota with xposed . I have a nandroid backup . If something goes wrong can i restore using the backup. What are the chances of HARD bricking?
Click to expand...
Click to collapse
No, you can't use your CM12 (Lollipop) nand backup on CM 11 (kitkat), it will brick your YU.
technowizard99 said:
Many people have hard bricked the phone by downgrading ( the whole 64 bit, 34 bit confusion)
Click to expand...
Click to collapse
Just use my guide to downgrade your Lollipop back to Kitkat, but be sure to read carefully the guide and do the steps orderly. It works for me, and many others have also confirmed my method. By the way, I'm the OP of this THREAD, so I know what I'm doing.
kane111 said:
@tirta.agung
thanks man, works like a charm!! i dont think i'll be switching back until CM12 gets bug-ridden officially!
Click to expand...
Click to collapse
Thank you, glad that I could help.
Can I copy paste the commands?
I'm just being paranoid. But can i copy paste the commands?
technowizard99 said:
I'm just being paranoid. But can i copy paste the commands?
Click to expand...
Click to collapse
yes you can, i did the same!
Related
Hey Guyz,
Guess what? YU finally released factory images for our beloved Yureka.
Check this out.
Download Links:
FastbootZip
boot.img
flash procedure:
1. Boot into fastboot.
2. fastboot -i 0x1ebf erase boot
3.fastboot -i 0x1ebf erase cache
4. fastboot -i 0x1ebf erase recovery
5. fastboot -i 0x1ebf erase system
6. fastboot -i 0x1ebf erase userdata
7.fastboot -i 0x1ebf flash boot boot.img
8.fastboot -i 0x1ebf reboot-bootloader
9. fastboot -i 0x1ebf -w update imageZip.zip
Gotta use latest fastboot or file size too large error.
Someone from official YUTeam will create a thread for this, btw this belongs in general!
Thanks. Good find. Hope they will release an update soon, as so many bugs in the current OS.
Now I can re-lock my YU's boot-loader.
But they have not mention the steps to flash. Btw thanks to you for mentioning the steps in detail.
link is dead
Dead link for Fastboot image!
BB23482 said:
Dead link for Fastboot image!
Click to expand...
Click to collapse
https://forum.xda-developers.com/yureka/general/yu-yureka-mirrors-official-cyanogen-t3107684
Thanks!
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
mfastboot is necessary for flashing Motorola firmwares; standard fastboot is sufficient for Yureka.
Thank you man!!! Great Help
you are a life saver.
Did all you mentioned and my device returned to normal stage
prince.d.emperor said:
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
Click to expand...
Click to collapse
So by this restore we will go to kitkat 4.4.4??
kenil89 said:
So by this restore we will go to kitkat 4.4.4??
Click to expand...
Click to collapse
No, you will go to official CM12 !
prince.d.emperor said:
No, you will go to official CM12 !
Click to expand...
Click to collapse
Okie...
Does the following step will unbrick my soft brick yureka device??
Bob Parihar said:
Does the following step will unbrick my soft brick yureka device??
Click to expand...
Click to collapse
Only if you have officially or manually upgraded to CM12.
Please help sir
Will this method work if I have installed CM12 64BIT CUSTOM ROM? AND WILL WE GET OTA UPDATES AS NORMAL?
AND lastly can u say me why i always get "Android is starting" after every boot, when I was in CM 12 CUSTOM ROM WITH 64BIT MINIMAL GAPPS?
jogson said:
Will this method work if I have installed CM12 64BIT CUSTOM ROM? AND WILL WE GET OTA UPDATES AS NORMAL?
AND lastly can u say me why i always get "Android is starting" after every boot, when I was in CM 12 CUSTOM ROM WITH 64BIT MINIMAL GAPPS?
Click to expand...
Click to collapse
Follow this method only if you have officially/manually upgraded to CM12. This method requires updated bootloader. Flashing these on old bootloader may brick your device !
I'm on cm12.1 by varun chitre how can i get back to cm12.
not able to find system.imf file
prince.d.emperor said:
IMP : You need to be on 5.x.x Rom
Download official CM12 firmware image files.
Link : http://builds.cyngn.com/cyanogen-os/tomato/12.0-YNG1TAS0W0-tomato/56deeca328/cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
Download and install yureka drivers so that your pc can detect your phone.
Link : http://forum.xda-developers.com/yureka/help/fix-yureka-fastboot-detection-issues-t3014794
credits to @[email protected]
Download adb and mfastboot files.
Link : https://drive.google.com/folderview?id=0B05Crz57q4zgZE1aVW5FT1RsUUU&usp=sharing
Extract mfastboot files and factory images to a folder.
Open command prompt there.
Reboot your yureka into fastboot mode.
Now, its the time to enter commands. Execute these lines of command one by one checking that each command you executed returned ok !
commands :
mfastboot -i 0x1ebf oem unlock
mfastboot -i 0x1ebf flash boot boot.img
mfastboot -i 0x1ebf flash system system.img
mfastboot -i 0x1ebf flash userdata userdata.img
mfastboot -i 0x1ebf flash recovery recovery.img
mfastboot -i 0x1ebf flash modem NON-HLOS.bin
mfastboot -i 0x1ebf flash rpm rpm.mbn
mfastboot -i 0x1ebf flash sbl1 sbl1.mbn
mfastboot -i 0x1ebf flash tz tz.mbn
mfastboot -i 0x1ebf flash aboot emmc_appsboot.mbn
After successful execution, disconnect yureka from pc and reboot.
If every command you entered was successfully executed, your phone will reboot into stock CM12 firmware !
Please don't do this if your are on 4.4.x Rom. It will hard brick your device.
Hit thanks, if helped ! :good:
Click to expand...
Click to collapse
not able to find system.img file
seshadri.1995 said:
I'm on cm12.1 by varun chitre how can i get back to cm12.
Click to expand...
Click to collapse
I was also on custom rom and I wanted to revert back to stock cm 12.........this method helped me and I have successfully reverted back.....thanks to prince.d.emperor
I've already done this method when my yureka was in bootloop after updating official cm12 by OTA. Prince.d.emperor suggested this method to me and it worked. Now I've flashed custom cm12.1 and i want to revert back. Somebody saying that we want to flash "stock recovery" then only we need to flash official cm12. Is it necessary to flash stock recovery ???
seshadri.1995 said:
I've already done this method when my yureka was in bootloop after updating official cm12 by OTA. Prince.d.emperor suggested this method to me and it worked. Now I've flashed custom cm12.1 and i want to revert back. Somebody saying that we want to flash "stock recovery" then only we need to flash official cm12. Is it necessary to flash stock recovery ???
Click to expand...
Click to collapse
Nope !
Just flash the stock firmware. It's enough.
prince.d.emperor said:
Nope !
Just flash the stock firmware. It's enough.
Click to expand...
Click to collapse
Thanks bro... It worked...:thumbup:
:fingers-crossed::fingers-crossed::fingers-crossed:Awesome...
all is done very well
Thank you...
EiiiiiiiYUUUUUUU...:good::good::good:
I reverted back to official firmware but unable install any custom recovery. If I flash cwm or twrp, the existing stock recovery also gets removed and none of the other gets installed. Plz help I need root so bad...
Sent from my AO5510 using XDA Free mobile app
I've done this method from cm11 . And my device was hard bricked. What can I do now...!!!! Please help me....
s333hacker said:
I've done this method from cm11 . And my device was hard bricked. What can I do now...!!!! Please help me....
Click to expand...
Click to collapse
Can't help u.
In the post, it is written that u need to be on 5.x.x ROM before doing those steps.
[GUIDE][Perry(Qualcomm)][Windows, macOS & Linux] Flash Stock Firmware and Recovery
*This has only been personally done and tested using a Sprint Qualcomm variant of the Moto E4. I will be working on expanding this guide to cover all specific models of the Perry to avoid potential confusion as there are minor differences, so if anyone wants to pass along their firmware's flashfile.xml into my inbox it would be greatly appreciated.*
Links:
ADB and Fastboot mini .zip for macOS/Windows (Linux users make sure to have android-sdk installed, no need for this download)
All Stock Firmwares (sperry is Sprint firmware, perry is the rest of the Qualcomm models (Thanks to proudlytm) https://mirrors.lolinet.com/firmware/moto//
What you need:
A Windows/macOS/Linux computer
A USB cable
ADB and Fastboot files
Stock Firmware
Your phone
*Disclaimer* Your warranty is now void if you modify your phone. I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Let's get started! First, backup to your computer/Dropbox/etc. all the files you wish to save. This will wipe all data off your phone including root (Not data saved on any cloud services, such as Google, OneDrive, Dropbox, etc.)
Second, boot your phone into the bootloader. This can be done in certain ROM power menus, or with the ADB command "adb reboot bootloader" in Command Prompt/Terminal, or also by turning off your phone and then holding the power and volume down buttons at the same time. After booting into the bootloader, plug your phone into your computer.
The firmware file will look similar to This when extracted
Make sure to look in the firmware folder to see if you need to change a few lines during flashing. If you are unsure, check the flashfile.xml
Next open up Command Prompt if on Windows, Terminal if on macOS/Linux.
Navigate in CMD Prompt/Terminal to the directory you downloaded and extracted the stock firmware. Copy the Fastboot and ADB files into the same directory as the stock firmware files.
For Windows and Linux users, enter the following commands in Command Prompt/Terminal (use sudo before each command in Linux, or use sudo -s beforehand):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
For macOS, enter the following in Terminal:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash modem NON-HLOS.bin
./fastboot flash fsg fsg.mbn
./fastboot erase modemst1
./fastboot erase modemst2
./fastboot flash dsp adspso.bin
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
./fastboot flash recovery recovery.img
./fastboot flash system system.img_sparsechunk.0
./fastboot flash system system.img_sparsechunk.1
./fastboot flash system system.img_sparsechunk.2
./fastboot flash system system.img_sparsechunk.3
./fastboot flash system system.img_sparsechunk.4
./fastboot flash oem oem.img_sparsechunk.0
./fastboot flash oem oem.img_sparsechunk.1
./fastboot erase cache
./fastboot erase userdata
./fastboot erase DDR
./fastboot oem fb_mode_clear
./fastboot reboot
Click to expand...
Click to collapse
Hope it helps!
*Reserved*
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
</poorly_coded> said:
This is good for the XT1766, but the other variants firmwares have differences. Some have an extra system sparsechunk and an oem.img rather than 2 oem sparsechunks.
Click to expand...
Click to collapse
Thanks for letting me know, I'll add a note
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
Because your bootloader is unlocked.
codyalan said:
Hello, I have followed all of the directions and when I reboot the device, it says "bad key" then it goes to a screen where it says "erasing" and just keeps on doing this. Any help would be appreciated. Thanks
Click to expand...
Click to collapse
I have restored stock on my E4's (I have two, one with a cracked screen) a whole bunch of times, from soft-bricked stock and also from custom ROM's. The key for me was to NOT flash gpt.bin. Leave that step out.
First thing I'd try is re-flashing just the stock boot.img, then see if you can get boot normally... if not...
Try re-flashing stock bootloader and stock recovery, reboot to stock recovery and factory reset. Reboot to bootloader and start stock flashing again (thanks @acejavelin), but don't flash the gpt.bin.
If that fails, one thing that worked for me when I was bootlooped was to completely install a custom ROM and Recovery (I used LineageOS and TWRP), get it up and running, then go ahead and restore the whole business back to stock.
The bad key thing.... it will say that for a few seconds (up to 30 seconds, maybe?) on boot when you restore stock but should get past it. I think it keeps echoing that every time you restart until you've replaced your recovery with a custom one, then the message turns into 'N/A'.
HTH
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Vicpdx18 said:
Ok so I wanted to update this thread. I have the XT1768 and the instructions are a bit different. For the XT1768 there is a Sparsechunk.5 and also for the XT1768 there is only a oem.img. By changing those steps I was able to get unstuck and back in business.
Click to expand...
Click to collapse
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
fireball0093 said:
Do you happen to have a copy of the flashfile.xml for your model number you could send to me? I've been wanting to further expand this guide to encompass each individual QComm model
Click to expand...
Click to collapse
For the Xt1768??
codyalan said:
For the Xt1768??
Click to expand...
Click to collapse
Yes, if you have one for it that'd be awesome
fireball0093 said:
Yes, if you have one for it that'd be awesome
Click to expand...
Click to collapse
No Problem,
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
madbat99 said:
https://forum.xda-developers.com/ap...perr-s-kitchen-v3-0-0-0-t3601702/post72168885
How to start building
Click to expand...
Click to collapse
Thanks heaps, it'd be nice to create stock rom before root just incase the phone bricks.
McTRASH692 said:
Would you by chance have a stock rom for the XT1769? Anything I would need to know about restoring it to stock?
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
And not sure if there is a thread for this, if there is could you point me in that direction?Is there a way to create a ROM from a stock phone?
Click to expand...
Click to collapse
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Articul8Madness said:
I built the XT1765 Flashable rom in Assaayd's Kitchen. Followed the instructions to a T, and had no problems. Try him out too.
Click to expand...
Click to collapse
Cheers mate,
I have since found a stock rom for my phone and fixed it completely,
Thank you for helping though,
Hi guys,
Could someone please post the contents of their stock build.prop file? I have corrupted mine and can't find one anywhere,
Device is moto e4 xt1769
WARNING: if the gpt.bin flash did not work, please stop and do not continue with the rest of the commands. It has been brought to my attention that software upgrades to the phone has changed the gpt and may not allow you to go back to the original stock firmware.
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Outstanding. Thank you for the post. I'm sure this will get used quite a bit. I did do a backup but it's always nice to have contingencies at the ready.
Sent from my Nexus 10 using XDA Premium HD app
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
glockman4519 said:
I know this may sound like a stupid question, but which firmware package should I download and use for the Device purchased straight from Motorola? There are quite a few there and I don't want to flash the wrong one. This device was supposed too work on any US carrier and I would like to keep it that way, but my carrier is Verizon. All I had to do, when I got the device was install my Verizon Sim out of my Nexus 6 and it worked great. I do test for Cricket network too and that is a GSM radio so as I said, I would like it to have the firmware that would have come right from Motorola for this specific device. Thank you in advance.
Click to expand...
Click to collapse
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
aj2333 said:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you very much. You sir are an awesome person.
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
glockman4519 said:
I have another question and forgive me for being a pain but all steps went ok but at the end where the re-boot takes place it just keeps flashing back and forth from a black screen with "Bad Key" in the upper left corner and then to a screen with a colorful circle that says "erasing". I figured it was just doing a factory reset but it just keeps flashing back and forth between the 2 screens. Any idea what to try ? I tryed to boot to recovery and get the same thing. Thank you for any help.
Click to expand...
Click to collapse
Did you remember to do an fastboot OEM fb_mode_clear?
no I didn't do that. I will go back over your instructions and re-do it. Thank you again for your assistance. I usually don't bug people for help and try to fix things on my own so I really appreciate you help.
Sent from my G3223 using XDA Premium HD app
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
glockman4519 said:
Actually that is the command input right before the reboot command so I guess I did do that command. I will research this more and thank you for your help once again.
Click to expand...
Click to collapse
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
doodalydoo said:
The cmd commands above aren't written correctly for carrier unlocked E4 Plus's. Hlos.bin isn't in the unlocked stock ROM, NON-HLOS.bin is. Also, "flasty" should be flash. Here is the correct commands. This worked on my unlocked phone.
Click to expand...
Click to collapse
You Sir are the man. I can't thank you enough for your help.
Update: Awesome.... It worked like a charm. I have everything copied now in case I hit the wall again. Thank you once again.
So I have used this and it worked great. However does anyone know when the firmware in that download will be updated to the latest version?
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Cool miner malware that pops up on firmware.center.
mattleft said:
Cool miner malware that pops up on firmware.center.
Click to expand...
Click to collapse
I haven't had that problem. Have you scanned your PC for virus/malware?
I would like to relock my bootloader but on this firmware it says the boot is not signed. Can I relock it after I do the ota as they should be signed then right?
bcrichster said:
Not Stock ROM, no. Custom ROMs should work fine tho
---------- Post added at 11:41 AM ---------- Previous post was at 11:32 AM ----------
For OP @zerogun & those of you wondering which stock ROM Firmware to grab for Boost Mobile's XT1776 (owens), I used this one and it worked 100%. The Fastboot cmd list in the 10th post or so i nears perfect, (all the rest is Golden) except that for the Boost Mobile FW's:
fastboot flash oem.img
..needs to actually be:
fastboot flash oem.img_sparsechunk.0
fastboot flash oem.img_sparsechunk.1
Click to expand...
Click to collapse
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
mindstream98 said:
Did this allow you to use a non Boost/Sprint sim card?
Thanks,
Victor
Click to expand...
Click to collapse
I read in another thread that it was possible by using a Custom ROM but haven't tried it myself..
Although the Custom ROMs should work on several Carriers, this is a "Completely Back to Stock" thread..
Running an Xp3r!meπt with my XT1776
zerogun said:
For all of you who DID NOT do a System image backup in TWRP and then found out your backup doesn't work.
First get your stock firmware here, the only place to get Moto stock firmware!
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Then get fastboot. Google fastboot or grab the one from here: This one still works:
https://forum.xda-developers.com/showthread.php?t=2317790
If your fastboot directory isn't in your $PATH or you don't know how to do that, then copy fastboot into the same folder where you unzipped your stock firmware.
Got to the folder where you put everythig, open up a command or powershell prompt. Hold down shift, right click, "open command window here".
Now for the fun. You veterans can just look at the flashfile.xml to see the order. Those of you who are new, here are the commands you need to do. You could probably copy the entire thing and past it in your command window at one time. But I like to type it out.... line by line. You know, old school.
Commands:
Code:
fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem hlos.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash oem oem.img
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
the command to erase ddr will probably fail, but that shouldn't affect anything. I have tested by bringing my Moto E4 Plus that was running Lineage OS back to 100% stock. Of course, then I went right back to Lineage
Click to expand...
Click to collapse
I used this to go back to stock, now my phone wont even turn on, at all.
Hi everyone I have some questions if here in the forum we can solve them together
Without offending or underestimating the work of forum members and the people I have quoted, I only try to find solutions
I have the Chinese version of the Motorola Z2 Play Model XT1710-11, so I wanted to remove the default firmware with ZUI!. by 7.1.1_NZS26.71-36
First try Unlocking the bootloader to work clean following the steps of many sites who recommend working with the unlocked bootloader But unfortunately when I tried to unlock it, it told me a message "BAD KEY", Look for this type of problems in the forum and other sites, according to the problem is because the supplier who I buy it in China, should give me the key, since it is likely that the seller has changed it. Unfortunately the seller does not answer me and I do not think he does.
1. So the first question is: Is it possible to do the flash even if you have this kind of problem?
First I use this command as the flash comes, blocked from the factory by the supplier:
fastboot flashing unlock
Click to expand...
Click to collapse
First of all make a backup of the firmware, and all the elements with the TWRP here: https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Thanks to @Junior Passos , for his post, who helped me to do it, and in case someone has this phone model with the same "BAD KEY" problem. and be afraid of damaging it, it was tested and it worked normally.
The first problem in my head was that I did not like the operating system that brought by default my Z2-XT1710-11, because even if it was in Spanish or English there were places in the Chinese system
So, what I wanted was a clean and operable nougat.
I started looking for this exact model on the Internet and in the forum, I did not find a specific topic of this model, but in the comments of someone who had it, its name is: @LunaTheLuminous Who had a problem with their modems, https://forum.xda-developers.com/z2-play/help/fastboot-xt1710-11-china-mobile-modem-t3801969.
I did not have a modem problem because I had done backup, but I wanted to try to get to a clean rom and try to flash with comments from @KirMit from here: https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3. Unfortunately there were not the exact commands that he use, for avoid some kind of brick in my device.
Then I continued looking for the same model, and I found something similar that I decided to try : https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668. The original idea is to try to get a clean Nougat, According to @KirMit he managed to get a Clean nougat by using Two ROM, which I do not know From Here: https://forum.xda-developers.com/showpost.php?p=74833568&postcount=17.
I tried to find a clearer solution, because I had doubts about the exact commands that I use and roms, below in the comments, KirMit explains: that "the best manual is in the post" . I decided to use the @lexie90 tutorial https://forum.xda-developers.com/z2-play/development/moto-z2-play-stock-retail-xt710-07-t3669668 Thanks with this ROM: "ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
and These commands:
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
Click to expand...
Click to collapse
NOTE: The commands that are In red do not use them, I put them to see, the commands that I use and the ones that you do not have to use
Here I found a problem, because the bootloader has "BAD KEY" I can not close the OEM LOCK, and in the stage of flash recovery and flash boot it showed this message:
"Image signed with key bad key"
Click to expand...
Click to collapse
The flash of the firmware was made, I could go to the Nougat, Stock Running the modem, fingerprint reader, but when I turned on the phone I got a "bad key error message", looking for this type of problem is that the "logo.bin" file was necessary flash it, Unfortunately I could not find the original, but in the forum there are several people who have made their own logo.bin as: https://forum.xda-developers.com/moto-z/themes/logo-bin-to-remove-unlocked-warning-n-t3757030, and https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153 Thanks to @TobiPeter and @flashallthetime .
But when trying to flash it, and since they were from z play, the screen did not look good, therefore after several tests to eliminate this message:
{
"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"
}
To delete the message, from the motorola z2 play MODEL: XT1710-11, I did a flash with the logo that I made in the backup of the twrp.
https://drive.google.com/open?id=1OjPxy5k02MrH73SXZoXjI1sZCp83uFAr
With this command:
fastboot flash logo logo.emmc.win
Click to expand...
Click to collapse
2. My question is is there any way to make a flash clean and to install normal without any error with this type of BAD KEY problem?
But I did not just try that Rom, try several Stock Roms which I present to you in this list:
ALBUS_NPSS26.118-19-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_RETAIL_7.1.1_NPSS26.118-19-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
ALBUS_NPSS26.118-19-1-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
CHINESE VERSION XT1710-08
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-36_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
XT1710-08_ALBUS_RETCN_7.1.1_NZS26.71-97-41-9_cid11_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
Also try to change the command to try to see if there was the error, and use these: https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479, Thanks to @Kacike27 , Always avoiding:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
In the ROM of China I decided to make a full flash using all the commands, as @KirMit said in one of his comments.
https://forum.xda-developers.com/showpost.php?p=76813587&postcount=3
Hi. Use this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
I flashed all using standard set of fastboot commands including modem flashing and erasing. You will boot in Chinese version, but still able to change a language to English in preferences menu (try to find a right menu by logos). It is still Android Nougat 7.1.1 with CH/EN only languages.
After that I flashed this https://mirrors.lolinet.com/firmware...LT_CFC.xml.zip
But skip modem flashing and erasing. You will have multi language Android Oreo.
Enjoy.
Click to expand...
Click to collapse
Unfortunately I did not succeed the result was the same "bad key" errors and commands ("Image signed with key bad key", FAILED) Etc.
But as you will understand, I was not satisfied with the fact of all these mistakes, which were presented to me along the way, so I decided to do an update to OREO of both version ZUI!!!, and Stock of rom 7.1.1 ALBUS_NPSS26.118-19-4.
Then I followed the instructions in this post by @HTCDevil https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 Thanks!!!
I followed the following commands:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin I DID NOT USE IT
fastboot flash fsg fsg.mbn I DID NOT USE IT
fastboot erase modemst1 I DID NOT USE IT
fastboot erase modemst2 I DID NOT USE IT
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase DDR
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
Following the advice of KirMit, I do not use the commands that are in red
By @KirMit
I confirm, that all is working after update on XT1710-11 (China Mobile), BUT! do not flash all - skip:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
If you want your modems and fingerprint sensor are still working!
Click to expand...
Click to collapse
The process that I did for fastboot, it did not work for me, unfortunately the same mistakes appeared in the previous roms, I have to add that when updating to Oreo, in both versions, ZUI and 7.1.1 (Stock ALBUS_NPSS26.118-19-4.), the fingerprint reader stopped working.
The device, started to "encrypt", when I wanted to downgrade to 7.1.1 ALBUS_NPSS26.118-19-4 or ZUI!!. In the command stage:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
The commands were throwing error, (failed), now the question is:
3.It is possible that I can not flash the Bootloader, nor do the gpt partition, because the device is encrypted or has the oreo bootloader
?
To finish I try to flash with RSD Lite, without any result, due to the error when it goes in :"fastboot flash partition gpt.bin", it can not execute the flash in the gpt, it stays stuck in that stage.
The testing of RSD lite was with the help of the following post:
https://forum.xda-developers.com/showpost.php?p=76454434&postcount=29 by @St.Nogiel
https://forum.xda-developers.com/moto-z-play/how-to/mini-guide-bricked-special-case-attempt-t3812530 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/addison-factory-stock-images-t3736767/post75236696#post75236696 by @KrisM22
https://forum.xda-developers.com/moto-z-play/how-to/guide-rsd-lite-mini-guide-t3740641#post75334194 by @KrisM22
Click to expand...
Click to collapse
end of the tests,
sorry for my English. greetings friends
I got a z2 play in secondhand.
This phone is from china mobile and the previous owner has flashed 7.1.1 .
Now the phone is stuck in 7.1.1 and it does not get get updated to 9.0.
Is there any way this can be done.
I contacted Lenovo and they say that the build number is not in the database .