Cannot change from Chinese to European build. Help! - Honor 6, 6 Plus Q&A, Help & Troubleshooting

I have tried many things, HiSuite, MTT (fails to download the entire update file), and both to PE-TL10C432B571 and previous versions of the European build.
Current build is the Chinese build of PE-TL10V100R001CHNC00B260
It won't do OTA obviously, but I can't convince it to change to anything else at all ?
What must I do to get this to the 571 build or better.?
I keep getting the screenshot which I cannot attach when it try the manual update and pointing it to the /dload update.app
Many thanks. After two days of struggling!
" Software install failed " (image cannot upload)
Get online help from www emui com slash emotionaldownload.php?mod=restore
Press Power Key to confirm

Related

Moto X Play (India) Official Marshmallow 6.0 OTA Download Link

Hi All
Today I am releasing Moto X Play (India) Official Marshmallow 6.0 OTA ZIP File. This was released by Motorola for Indian Version of Moto X Play. Get your hands dirty and share your feedback. :laugh:
Mega - https://mega.nz/#!KVB3wSyb!_Wdce9oQOcKGPeXl26GLsgftwnanDTq-QZ9TRhdJprA
Dropbox - https://www.dropbox.com/s/p4ixlrg0naml1c6/Blur_Version.24.11.18.lux_retasia_ds.retasiaall.en.03.zip?dl=0
Google Drive - https://docs.google.com/uc?id=0B8kDOqfxRXEhRjZ0b3o3OHA1bnc&export=download [Credit For Google Drive URL - @amitnvis]
GitHub - https://github.com/motoxplay/stock/releases/download/v6.0.0/file_delta-ota-Blur_Version.23.21.10-24.11.18.lux_retasia_ds.retasiaall.en.03.zip [Credit For GitHub Link - MastahF]
This OTA Update can be applied ONLY on Android 5.1.1 Build LPD23.118-10 and will be updated to Android 6.0 Build MPD24.65-18. Users who have Android 5.1.1 Build LPD23.118-32 have to wait for OTA from Motorola OR get the update from Moto Care Service Centre.
==================================================
Filename : Blur_Version.24.11.18.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 97de580ffa00578e79ef0b1d1cf9ace1
SHA1 : f778fabf0822f943aabc6d7382f1df97bdb25709
CRC32 : 65ab8e6f
SHA-256 : 57fc7c74288eb2e9b01b9e175f32f2cf49c4cbd5311289a77ab7963da2f71ff6
SHA-512 : 786b9fb8398a14b201a4b97c8a4c3e68884137b97eaae653d2ea7512bde01377c32a672b4caae5cf36d7cb351bd011c083c7efe70e4bca72c4da02b6e10b973a
SHA-384 : e460d760ec1a8ffaf50ec6c2a46011c43049aa900cc65194f8f0e73a570dfe66ca39658614a7e8575376bec6021eae56
Modified Time : 12/9/2015 12:58:28 AM
Created Time : 12/9/2015 12:51:13 PM
File Size : 611,237,778
File Version :
Product Version :
Identical :
Extension : zip
File Attributes : A
Model : Indian XT1562 100% [ Unsure if it will be compatible with other regions and variations of handset ]
==================================================
NOTES :
This has to be used on Android 5.1.1 to upgrade to Android 6.0! You will not get any update notification in Android 6.0 for this update BUT will get for any newer builds. This is OFFICIAL FINAL UPDATE. So don't post comments again like "Will i get update notification after applying this update". Why will you be notified by Motorola to apply same update that you have already applied ?
Announcement
New Update Adding VoLTE Support Can Be Found At http://forum.xda-developers.com/moto-x-play/general/moto-x-play-india-official-marshmallow-t3407068
Regards
XDASNR
Steps To Update To Android 6
Save the downloaded file to Root of SD Card and follow instructions :
Method 01 [Reported By Many Users]
Just Save the downloaded file to Root of SD Card [External Memory Card and not Internal Memory] and go to Settings --> About Phone --> System Updates. Update will be auto recognized and user will be prompted to apply update. In case update is not recognized and do not get any update prompt, then try Method 02.
Method 02 :
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down button to highlight "Recovery mode"
Press the Power button to restart into Recovery mode.
You'll see an image of an Android robot with a red exclamation mark.
While holding down the Power button, press the Volume Up button.
Phone will auto reboot to Recovery Mode.
Using Volume Down Button highlight Apply update from SD Card and press Power Button.
From the contents of SD Card Listed, using Volume Up / Down button select dowloaded .zip File and press Power Button.
Updatation Process will start. It will take about 30 Mins to complete updatation.
Already exists 2 threads talking about that.
http://forum.xda-developers.com/moto-x-play/general/android-marshmallow-6-0-soak-otalink-t3265928
http://forum.xda-developers.com/moto-x-play/general/noobs-to-upgrade-moto-x-play-to-t3266264
Hi,
Thanks for youy sharing
Can't download the file now Error on Mega web site.
Dudlei said:
Already exists 2 threads talking about that.
http://forum.xda-developers.com/moto-x-play/general/android-marshmallow-6-0-soak-otalink-t3265928
http://forum.xda-developers.com/moto-x-play/general/noobs-to-upgrade-moto-x-play-to-t3266264
Click to expand...
Click to collapse
This is not the same OTA.
dont work. fake?
DieOrange said:
dont work. fake?
Click to expand...
Click to collapse
@DieOrange - It is Genuine. It is downloaded directly Moto Servers. The ones posted in other threads are for Brazillian Versions. This is Indian Version.
XDASNR said:
@DieOrange - It is Genuine. It is downloaded directly Moto Servers. The ones posted in other threads are for Brazillian Versions. This is Indian Version.
Click to expand...
Click to collapse
your link/mirror dont work. maybe you can upload to other hoster?
006fazer said:
Hi,
Thanks for youy sharing
Can't download the file now Error on Mega web site.
Click to expand...
Click to collapse
May be your ISP has blocked mega.nz. Is anyone else facing this issue ? I will have to upload it to other filesharing site in that case.
Thanks for sharing, I can't download either (Europe).
Thanks, I confirm that is impossible to download the file neither from the browser or from the mega plugin. I'm connencting from Europe.
This can be installed on the moto x play eu version or I need to flash the original India Firmware first? I've an non-rooted moto x play.
I have the same question
It could be. The Filename looks good. But with no Mirror it would be hard to test
Can't download even from mega app
XDASNR said:
May be your ISP has blocked mega.nz. Is anyone else facing this issue ? I will have to upload it to other filesharing site in that case.
Click to expand...
Click to collapse
not downloading error
Upload To New File Sharing Site In Progress
Refer Original Post For Additional Download Links To Dropbox
After many retry download started !!! in progress....
I finally downloaded file from mega. But I dont know what to do.
My build is:
23.21.10.lux_reteu.reteu.en.EU reteu
LPD23.118-10
it seems now Mega works. WTF.
You can add the second Mirror too. more is better
Apply through adb sideload => success
Boot in progress, optimyzing applications....

Moto X Play (India) Official Nougat 7.1.1 OTA Download Link

Hi All
Today I am releasing Moto X Play (India) Official Nougat 7.1.1 OTA ZIP Files :laugh:. These were released by Motorola for Indian Version of Moto X Play during Soak Test and is currently on-going. There are few bugs to be fixed; however stable enough for release and daily usage. Any new updates from Motorola will be updated here as and when released.
After installation of 5th OTA, your phone should be updated to below version :
System Version : 26.31.1
Build Number : NPD26.48-24-1
Android Security Patch Level : 1 September 2017 :laugh:
Below is the sequence in which updates have to be applied. An update can be installed ONLY if existing version matches given after file name below. Note you can directly install a version and skip previous builds if your existing build matches one given below. Example : If your current build is 7.1.1/NPD26.48-8/8, can skip to install 01 and 02; directly install 03-05.
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 6.0.1/MPDS24.107-70-1-5/5" OR "ro.build = 7.1.1/NPD26.42/34"
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.42/34" OR "ro.build = 7.1.1/NPD26.48-8/8"
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-8/8" OR "ro.build = 7.1.1/NPD26.48-16/16"
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-16/16" OR "ro.build = 7.1.1/NPD26.48-24/24"
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-24/24" OR "ro.build = 7.1.1/NPD26.48-24-1/1"
Download Links :
Dailyuploads.net -
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip [760 MB]
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip [78.9 MB]
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip [46.6 MB]
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip [41.6 MB]
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip [15.6 MB]
Mega.nz -
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip [760 MB]
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip [78.9 MB]
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip [46.6 MB]
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip [41.6 MB]
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip [15.6 MB]
Zip Files Checksum
==================================================
Filename : 01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 8d1677c757087ad49af9211ff454945e
SHA1 : a751aadad8662c5a5a6f5a630aeb37426b95be15
CRC32 : 2610d0c7
SHA-256 : 1572a567ef5054a735b794b7e65bffd36a7cfa78fdf5eda24c56f058970d0b37
SHA-512 : 4e76ce5e7519a220d2fb15cec0d9414cebbb0d44b15412026c5bb08fa7d614da06720c8c5b55d534f9c5a5c26bb815c745325acc74b75fda697e1179d72cc6b8
SHA-384 : bc7534a90e72a4e2c1afc00c14106dfa6054ab0a8d824fbcd5e8b095331059703da78316eb421e64e9cc8f46c7d51c0e
File Size : 797,595,918
Extension : zip
==================================================
==================================================
Filename : 02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 4dbfe38e3aace6d148de1557e6ea512e
SHA1 : 1174d4698e9ff4c2408d3dfb09ce48faef55fbc2
CRC32 : 4c56a95b
SHA-256 : c7f4f0fe8a12c9d05c6b5349347037f3072f19895fc78cfeeaa46e11ab6e32b1
SHA-512 : f555918c8c8e784bf30281258d5a89a355d6dd81571373a8d5cdbce4dcdf6f9d2439988d139044213dd78091be20f0a6bb024fdad53ac3448d079fcecf9c10c6
SHA-384 : f993c846fd012ee647a0bb708f1a7e524dd922eee821b54d3dce06be67275aca6f891b300d98d09a2e3f1bd102cb1375
File Size : 82,813,245
Extension : zip
==================================================
==================================================
Filename : 03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 664ecff177e4c14da476ed405c23f289
SHA1 : 0f490c52f176387cb3abd712aa2a02f511621097
CRC32 : 02702ede
SHA-256 : 28d33ed8da0a0da513257d4d32d805546b9157657dbaad9324c59c00715ab4b7
SHA-512 : 7b4fd6881a9bc1ca872ab1e66f46d9001c5d0668708d5855371379df8a62f1125251d79b79f7393916767b0edbdead0569200d39596df6e3d56f9b7d86af3669
SHA-384 : f2343aa4a36d54344819c08c6697386c147b5831968974bf14588d50fb6cc3e4b56963ff4414e913d3caf6815ff67d31
File Size : 48,914,241
Extension : zip
==================================================
==================================================
Filename : 04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip
MD5 : b0225339c14141e5ffb67c83c710f4c9
SHA1 : b62ec2fcd4113cd974a9984e3179d6892296d0f3
CRC32 : 9cc9c5b0
SHA-256 : 10fadca67babd93b621929c0bd16d13e3f01a2c3cd30fc2b7e4fe110b1f867e9
SHA-512 : baa95d79b36060dc24e358f6abbeffb8cc411636e08cc9a1a2fd9e8e24b2d931eae6ef97f9150e7cbd11d7dbfc31ce29ada7bdeab1621ccc9e33e62853e7d72e
SHA-384 : c2a4998e05270eecaa7d873d8683d88b8dd78a7a48308eba690bd473aaa67b85250cfe2e2f1beafe1c755ee56239b6a4
File Size : 43,724,857
Extension : zip
==================================================
==================================================
Filename : 05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip
MD5 : 699ac49664ea5629f437b0477107ac2b
SHA1 : 7c317dbd42f6aa332412bee7784998b4e7d50816
CRC32 : 0a208184
SHA-256 : bc40f8796fda899154105d509fa7ea8e8db32816dce5245892d02186400a1abd
SHA-512 : 07f167d514335396f6c4ea6c540b7d67b2ece55284e57a8f70ec4303393746e64feab46fb185118effab3406c35e7128cec9442f16366e942f6618224de58dee
SHA-384 : 98011bee82a697b256de5f6d1b4c5b267f6429deb5ca8e7684befa612033c074e2007dc78345021da7eded18cb3d66bc
File Size : 16,408,621
Extension : zip
==================================================
FAQs :
01. Why am i releasing these after 2 months of Soak Test ?
Well, first few releases were very buggy, unstable and unusable. I decided to wait until Motorola (Lenovo) fixes them. Now that major issues have been fixed, i am releasing the files so that everyone can start using Android 7.1.1 and before the handset reaches is EOL. Motorola (Lenovo) are very slow to fix the issues and i dont expect the Soak to be completed soon. So why to suffer for their inefficiency ? Now it can be used as daily driver.
02. What are the known issues pending to be fixed ?
Few prominent users reported issues to be fixed are - Random shutdown (minor users facing it), high battery consumption (everyone), network issues (few users facing it, VoLTE issue has been fixed), scaling of graphics on lock screen (minor users facing it), vibration on receipt of notifications during call (everyone, actually Motorola (Lenovo) terms it feature instead of bug though Google has fixed in AOSP).
03. Will i get Official Download and Updates ?
This is an Official Update from an Unofficial Source. Why will you receive the same update twice No modifications have been done to these files. You will get any future OTAs Motorola (Lenovo) releases.
Steps To Update To Android 7.1.1
Save the downloaded files to Root of SD Card and follow instructions :
Method 01
Just Save the downloaded file to Root of SD Card [External Memory Card and not Internal Memory] and go to Settings --> About Phone --> System Updates. Update will be auto recognized and user will be prompted to apply update. In case update is not recognized and do not get any update prompt, then try Method 02.
Method 02 :
With the phone powered off, press and hold the Volume Down button and the Power button at the same time until the device turns on.
Press the Volume Down button to highlight "Recovery mode"
Press the Power button to restart into Recovery mode.
You'll see an image of an Android robot with a red exclamation mark.
While holding down the Power button, press the Volume Up button.
Phone will auto reboot to Recovery Mode.
Using Volume Down Button highlight Apply update from SD Card and press Power Button.
From the contents of SD Card Listed, using Volume Up / Down button select downloaded .zip files in order (01, 02) and press Power Button to apply update.
Updatation Process will start. It will take about 30 Mins to complete updatation.
Caution : You have to apply updates one after another in serial order else update will not be applied. At Worst, you may end up with bricked handset.
Regards
XDASNR
whether i hv to download all d files?
rohitpaul9000 said:
whether i hv to download all d files?
Click to expand...
Click to collapse
Yes.. Motorola (Lenovo) has released 5 updates so far, each fixing bugs and increasing the system version.
XDASNR said:
Yes.. Motorola (Lenovo) has released 5 updates so far, each fixing bugs and increasing the system version.
Click to expand...
Click to collapse
if i put all the files in sd card will it update in sequence automatically or i have to put one file at a time????
---------- Post added at 06:02 PM ---------- Previous post was at 05:38 PM ----------
any bugs? and what about battery backup????
can i root it?
read the op and you will receive answers...
Has anyone tested?
I thought to give it a try.
First I backuped my phone, and flashed stock Indian rom and latest OTA update I had. (Mind that my device is a european XT1562 on which I have flashed Indian firmware in order to enable dual sim functionality).
Then I tried to flash the first .zip file via stock recovery, and all I got was error (status 7). It said that "package expects build fingerprint of ... MPDS24.107-70-1-5 or NPD26.42 and mine was MPDS24.107-52-11.
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
My system version was indeed MPDS24.107-70-1-5 at the time.
So I gave up and restored my perfectly working 6.0.1 setup.
Thanks for sharing the OTAs, but I had no luck installing them.
I guess I have to wait.
does not recognize ota
What version of the system do I need to have installed to be able to install the otas?
download from this thread " https://forum.xda-developers.com/mo...official-7-1-1-nougat-factory-update-t3626387 " and does not recognize them
2017-09-11--02-10-03_npd26.48-24-1_retasia_ds
mark_kou said:
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
Click to expand...
Click to collapse
Not a surprise! You need recovery and modem to be of latest version too.
But I really don't recommend to mess with OTA because you risk to get bricked. It's easy and unforgettable )
Ok folks, I'm pretty familiar with this stuff, here is ready to flash restore TWRP-backup 7.1.1 NPD26.48-24-1 for RETASIA DS model (modem and recovery also supplied). If you got different model, leave your native 6.0.1 modem on place.
I have 1 doubt , Afaik Moto never released soak ota to non soak member ,so what happen if we apply this ota and By chance Moto release 1 more ota to soak members . We will stuck on this version will be fully dependent on someone to leak that also . And aside you I don't see anyone doing this .
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
s5610 said:
Not a surprise! You need recovery and modem to be of latest version too.
But I really don't recommend to mess with OTA because you risk to get bricked. It's easy and unforgettable )
Ok folks, I'm pretty familiar with this stuff, here is ready to flash restore TWRP-backup 7.1.1 NPD26.48-24-1 for RETASIA DS model (modem and recovery also supplied). If you got different model, leave your native 6.0.1 modem on place.
Click to expand...
Click to collapse
After restore your backup, i still have to aply all the OTA updates?!:good:
martt said:
After restore your backup, i still have to aply all the OTA updates?!:good:
Click to expand...
Click to collapse
Of course not. I did all dirty job to rework OTA into ready to use 7.1.1 fresh build (final even, maybe )
Unlock needed, TWRP backup/restore experience, etc. You have to be at medium android-fu level. Please, read a bit about OTA risks
---------- Post added at 03:23 AM ---------- Previous post was at 03:21 AM ----------
debanildas said:
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
Click to expand...
Click to collapse
You mix up leaked development beta build, and public release candidate, that was just dumped and shared.
del post. its old
avi_loveindia said:
We will stuck on this version
Click to expand...
Click to collapse
Until you have locked bootloader, or RSD service ROM 7.1.1 will leak. It should happen, I'm sure.
avi_loveindia said:
I have 1 doubt , Afaik Moto never released soak ota to non soak member ,so what happen if we apply this ota and By chance Moto release 1 more ota to soak members . We will stuck on this version will be fully dependent on someone to leak that also . And aside you I don't see anyone doing this .
Click to expand...
Click to collapse
debanildas said:
After installing all 5 of the updates , will the moto dev apps like Moto Survey , Perf Monitor , PM Test etc will be there or not..?
Click to expand...
Click to collapse
The updates remain same for all and are ready to install on Moto Servers. However they limit the people who can access these updates by EMEI number which they collect during Soak Test. Once the test is over, the EMEI limit is removed and same updates are delivered to everyone. Once the Soak Test is over, i believe, everyone will get to install all these one after another OR one build with all these updates packed in one file. However the final build number or version will be same for everyone. So nothing to be afraid of.
Having said these, you will just have to wait until Soak is over for any updates to come from Moto; Until then, i will release them here for benefit
Zip Files Not Visible
I went into the recovery mode and selected the update from SD card option But the zip files i copied into the root directory are not visible to select there. What should i do?
mark_kou said:
I thought to give it a try.
First I backuped my phone, and flashed stock Indian rom and latest OTA update I had. (Mind that my device is a european XT1562 on which I have flashed Indian firmware in order to enable dual sim functionality).
Then I tried to flash the first .zip file via stock recovery, and all I got was error (status 7). It said that "package expects build fingerprint of ... MPDS24.107-70-1-5 or NPD26.42 and mine was MPDS24.107-52-11.
After searching the forum, I found a twrp backup of that exact version I needed(MPDS24.107-70-1-5)
So I just booted twrp recovery without flashing it on the phone, and restored the backup I downloaded.
Afterwards I rebooted to stock recovery and tried to flash the first zip, which again failed and I got the same message.
My system version was indeed MPDS24.107-70-1-5 at the time.
So I gave up and restored my perfectly working 6.0.1 setup.
Thanks for sharing the OTAs, but I had no luck installing them.
I guess I have to wait.
Click to expand...
Click to collapse
I have updated main post with below, however posting it for you as it is apt. Note if you dont have below builds, you can get one of Stock ROM from other threads in the forum and continue with installation.
Below is the sequence in which updates have to be applied. An update can be installed ONLY if existing version matches given after file name below. Note you can directly install a version and skip previous builds if your existing build matches one given below. Example : If your current build is 7.1.1/NPD26.48-8/8, can skip to install 01 and 02; directly install 03-05.
01. Blur_Version.26.1.42.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 6.0.1/MPDS24.107-70-1-5/5" OR "ro.build = 7.1.1/NPD26.42/34"
02. Blur_Version.26.21.8.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.42/34" OR "ro.build = 7.1.1/NPD26.48-8/8"
03. Blur_Version.26.21.16.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-8/8" OR "ro.build = 7.1.1/NPD26.48-16/16"
04. Blur_Version.26.21.24.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-16/16" OR "ro.build = 7.1.1/NPD26.48-24/24"
05. Blur_Version.26.31.1.lux_retasia_ds.retasiaall.en.03.zip if build is "ro.build = 7.1.1/NPD26.48-24/24" OR "ro.build = 7.1.1/NPD26.48-24-1/1"
s5610 said:
Until you have locked bootloader, or RSD service ROM 7.1.1 will leak. It should happen, I'm sure.
Click to expand...
Click to collapse
There are other threads in this forum where in full Stock ROM is released after integrating OTAs. One of the developers will do this and until then, just wait. Same has happened when i had released OTAs for previous version.
murugunm said:
I went into the recovery mode and selected the update from SD card option But the zip files i copied into the root directory are not visible to select there. What should i do?
Click to expand...
Click to collapse
If you have copied files to Internal Memory, then you will have to choose Internal Memory instead of SD Card Option. I recommend you to move all files from Internal Memory to SD Card and apply update. In case you dont have SD Card, place one at a time in Internal Memory and apply updates.

Firmware files

Sometimes we see that some firmware contains 3 files, whereas some contains 2 files.
1. What's the difference between them?
2. Some firmwares can be flashed through TWRP, but some fails. Why?
3. What's the difference between FullOTA-MF and FullOTA-MF-PV?
If you do just a tiny bit of research whether it's here on XDA or Google you'll have your answers. You're breaking the literal first rule of XDA. SEARCH FIRST.
SirDarknight said:
Sometimes we see that some firmware contains 3 files, whereas some contains 2 files.
1. What's the difference between them?
2. Some firmwares can be flashed through TWRP, but some fails. Why?
3. What's the difference between FullOTA-MF and FullOTA-MF-PV?
Click to expand...
Click to collapse
1. The only firmwares with two files are PV firmwares. For example, B394 for FRD-L09 is PV and has two files. The Firmware itself is not different. It has the same files as those firmwares which have their data split into two separate files, a public data zip (which as the name suggests is a generic data zip applicable for all models) and a region data zip (like hw_usa or hw_eu) which is intended only for a specific model / region.
3. FullOTA-MF are complete firmware files. It contains all patches released for a specific Android version and is thus also called as the firmware which contains all service packs. The OTA firmwares are one specific service pack only. So let's say you are on B360, you can use a FullOTA-MF package to straight upgrade to B504 but if you take the OTA route, you have to take all updates released after B360 one by one until you reach B504.
The PV packages, known as Point Version are used to upgrade from an older Android version to a newer one, say from 6.0 to 7.0. That's the reason why changelogs for PV contain the line 'your device will be upgraded to Android 7.0, bla bla bla'. Other than that they are same as MF packages and can be used to jump straight to a newer firmware.
2. Why you can PV through TWRP, I suspect that's because PV allow you to upgrade to newer Android versions and this is for the sake of compability. EMUI 4 doesn't has the same authentication algorithm as EMUI 5.
Apart from PV all other firmware cannot be flashed through TWRP since they were not intented to be flashed using TWRP the first place. They fail authentication which TWRP doesn't supports. That's why we have HuRupdater which has its own update binary that allows you to flash those packages by bypassing the authentication checks.
hackslash said:
1. The only firmwares with two files are PV firmwares. For example, B394 for FRD-L09 is PV and has two files. The Firmware itself is not different. It has the same files as those firmwares which have their data split into two separate files, a public data zip (which as the name suggests is a generic data zip applicable for all models) and a region data zip (like hw_usa or hw_eu) which is intended only for a specific model / region.
3. FullOTA-MF are complete firmware files. It contains all patches released for a specific Android version and is thus also called as the firmware which contains all service packs. The OTA firmwares are one specific service pack only. So let's say you are on B360, you can use a FullOTA-MF package to straight upgrade to B504 but if you take the OTA route, you have to take all updates released after B360 one by one until you reach B504.
The PV packages, known as Point Version are used to upgrade from an older Android version to a newer one, say from 6.0 to 7.0. That's the reason why changelogs for PV contain the line 'your device will be upgraded to Android 7.0, bla bla bla'. Other than that they are same as MF packages and can be used to jump straight to a newer firmware.
2. Why you can PV through TWRP, I suspect that's because PV allow you to upgrade to newer Android versions and this is for the sake of compability. EMUI 4 doesn't has the same authentication algorithm as EMUI 5.
Apart from PV all other firmware cannot be flashed through TWRP since they were not intented to be flashed using TWRP the first place. They fail authentication which TWRP doesn't supports. That's why we have HuRupdater which has its own update binary that allows you to flash those packages by bypassing the authentication checks.
Click to expand...
Click to collapse
Huge Thanks, brother!! You're truly helpful.

Looking for June-updated boot image

I want to avoid configuring the system from scratch and thus need to recover the official boot image for PPIS29.65-51-5 for the European version (reteu), which has been available since few days ago.
Does anyone know where to find it?
Stockrom[1] only has the Brazilian version (retbr) and lolinet[2] only has versions up to PPIS29.65-51-3. The Telegram Moto Updates Tracker[3] shows the update, but the download does not work and the older MotoOTA script[4] does not work neither (or I am entering incorrect information) and the newer MotoOTA script[5] needs the build guid, which I do not seem to be able to get from fastboot or TWRP.
If you have a matching model and version, could you please get the boot image[6] and put it somewhere?
[1]: stockrom.net/2020/06/xt2019-2-retbr-9pie-ppis29-65-51-5.html
[2]: mirrors.lolinet.com/firmware/moto/doha/official/RETEU/
[3]: t.me/s/motoupdatestracker?q=%23doha+Retail+Euro+PPIS29.65-51-5
[4]: motoota.lolinet.com
[5]: motoota.lolinet.com/guid.php
[6]: android.stackexchange.com/a/190102
Update
I learned that the former most recent version [7] can be used to find out the guid inside of oem.img inside of that zip file:
ro.mot.build.guid=7d7b4268f01b080
Using that information [5] can be used to download Motorola's OTA zip file. However, that zip file seems to be some kind of patch format (only 72 MB instead of the typical 1.9 GB) not including a (complete) boot.img. As I do not know the file format, I can't patch the new boot.img myself.
[7]: mirrors.lolinet.com/firmware/moto/doha/official/RETEU/XT2019-1_DOHA_RETEU_9.0_PPIS29.65-51-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Question P11 PLUS, TB-J607F --> TB-J607Z: How-To

Update: This did not delete my serial. It's hidden in "settings, about, model"
Hi, thanks for anyone who was helping me the last few days!
Today i succeded in converting my International "Xiaoxin Pad Plus" to international "P11 5g" !
This it what i did:
A) Boot Tablet to FFBM:​
Power off
Press Up, Down, Power + insert USB
Release Power few seconds after the Lenovo screen appears
Select boot to bootloader
Select boot to FFBM
Wait until FFBM is displayed on screen
B) Change NV-RAM:​
Install NV_Ram_Reader
Install Qualcomm USB Driver
Open NV-RAM Reader and Set right Port, press connect
Put Range 6858-6858, then press read, save file
Open new file, change 01 to 02 and save
Check file again for value 02
Back to NV-RAM Reader, press write, select file with "02" in it.
Chill
Put Range 2497-2497, then press read, save file
Open new file, change "43 4E 58 58" to "4B 52 58 58" and save
Check file again for "4B 52 58 58"
Back to NV-RAM Reader, press write, select file with "4B 52 58 58" in it.
Reboot tablet - now maybe bootloop with "software incompatible" appears and tablet shuts itself down.
This is fine =)
C) Change Software: (This works fine on latest W11)​
Install Lenvo LSMA from here: (only latest version works, needs Lenovo-ID)
Rescue and Smart Assistant (RSA) - Lenovo Support DE
support.lenovo.com
Login to LSMA and select "recover"
Put a valid serial of TB-J607Z
Follow steps
D) Enjoy:​
Get yourself a drink or a good cigar =)
Set up tablet as you wish.
Note:
Part of this tutorial is inspired by
Check Region Unlock!! P11 [TB-J606F/L/N]
This method was shared by Koreans at the Ppomppu Forum. When Check Region Unlock is performed, firmware downgrade and update are free. Chinese ROM ZUI(12.6) check region introduce Global ROM 210805 check region introduce How To Guide (Check...
forum.xda-developers.com
안드로이드11 미개봉 중국롬 P11 글로벌롬 5월 이후 업데이트 방법
추가로 확인을 해보니 중국롬의 경우 ANDROID 11부터, 글로벌롬의 경우 8월롬(안드10)부터 해당 버전을 체
www.ppomppu.co.kr
Whoever made them: Thank you very very much for providing those helpful guidelines!
It didn't work before with QFIL - since i tried to flash TB-J606* Firmwares since those are linked somewhere else in this devices topics, to be used with TB-J607F. This doesnt work. save your bandwith
try to restart your pc
here firmware :
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
TEK023 said:
try to restart your pc
here firmware :
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Click to expand...
Click to collapse
Thanks,
any hints on why it is giving me the same config file error with any lolinet roms from this folder? (Some file is not found even tho it is right in the folder), is the path to long?
Or do I have to flash those roms with something else then qfil?
Can't post a screenshot since I'm out of home until Thursday. (See 2nd picture for the "missed" file's name)
I tried various files from this folder yesterday on w10
// lenovo android rescue assistant (or how it is called) asks for a serial before doing the selection now, this might cause the fail of flashing in that tool.
Anyone knowing a version that doesn't do that - I found some version. 6.1 instead of 6.2 it still asks.
it's something to do with your driver try install it again with no driver signature mode via advance startup
myself use to fail but after few try it work
I finaly did it. without qfil =) see above
is there a way to do the oposite? install zui rom over P11 5g rom in my j607f?

Categories

Resources