Related
Dear all
There are so many people looking for exactly samething that iam looking for but unfortunately there is not any proper tutorial available.
Could you confirm if there is anyway to install any other ROM on chinese moto z play ? i don't mind if i have to install each OTA manually.
If so could you please guide step by step guide how to perform this?
If there so no any ROM that can work with chinese variant is there any custom ROM that would and support Moto Mods?
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
freeman_g said:
You can read my thread: https://forum.xda-developers.com/moto-z-play/help/problem-reteu-firmwares-chinese-t3619235
Briefly:
1) If you unlock your bootloader you will be able to flash full image of any firmware throug fastboot (with ordinary instruction)
2) OTA at the moment can't be installed even manually due to different device name (addison_retcn vs addison)
I'm looking through different ways to fix device name with no luck at the moment (but I am sure it is possible)
Click to expand...
Click to collapse
Did you try editing build.prop?
jameelmemon said:
Did you try editing build.prop?
Click to expand...
Click to collapse
I see that you has not even tried to look through my thread (link was provided in previous post). Suggest to do that (espesially the very end) before further questions / discussion
I have gone through almost all threads including your befiore posting or asking you that question
you are referring to
2) target script is probably /device/company_name/device_name/init.device_name.usb.rc
3) there is a string in that script: write /sys/class/android_usb/android0/iProduct ${ro.product.model}
aactualy {ro.product.model} is variable in build.prop so that script (/device/company_name/device_name/init.device_name.usb.rc) from build.prop
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Finally i manage to install 7.1.1
My phone is addison after installing RETAIL version (7.0)
I installed RETAIL version then downloaded ota then installed 7.1.1 OTA from this thread https://forum.xda-developers.com/moto-z-play/how-to/official-android-7-1-1-download-how-to-t3616352
phone should not be locked/encrypted or protected at least i bricked it and it was not booting up.
Now need to change two things those are in bootloader (SKU and ro.carrier) fastboot getvar all
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Just found ro.carrier comes from kernel and will be taken from kernel each time devices boots up. so we need someone to customize the kernel and add retru or retus to kernel as ro.carrier.
sku i can not change as i am getting error of command is not allowed
can anyone help regarding this?
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
freeman_g said:
Actually, not there. I have pushed build.prop with adb and has not found any signs of "addison_retcn" there
Hovewer AIDA64 (as well as adb once you try to sideload OTA) will display "addison_retcn" so it is somewhere else
I do not thing that script take the name from build.prop as, for example, it also obtains serial number with the same way and it is the first recommendation on recovering serial (in case it is lost during the some flashing procedure) to manually set it in that script
Click to expand...
Click to collapse
freeman_g said:
So just install retail version and sideload OTA through ADB?
I see that my phone is encrypted, shall I decrypt it first?
In any case any news on how you managed to boot 7.1.1 are appreciated
Click to expand...
Click to collapse
Just install fresh retail version then sideload first ota via adb then boot your phone do not complete setup.
then install 7.1.1 then do factory restore then you are good to go
and it have so many great features you can view them here specially camera app
freeman_g said:
So what is the result? You have managed to sideload 7.1.1 аnd it is not booting?
Or everything works fine and you tried to change SKU/channel for further updates?
Click to expand...
Click to collapse
Initally it didn't work and stuck on bootloader unlock warning but later it worked perfect and iam using 7.1.1 and now trying to figure out how we can change sku and channel to get official OTA.
Sku (XT1635-03) is in bootloader but i can't write is with Fastboot, channel (retcn) is in kernel.
Lucky you I still have the same problem
Yesterday I tried to start with flashing stock retail 7.0 (the link you have provided earlier) but due to fact I had already flashed image with April security patch I didn't manage to downgrade bootloader and gpt (security downgrade issue)
Despite this fact phone boots but small OTA with April security patch did not agree to flash for the same reason: wrong name "addison_retcn"
So I believe the problem is in bootliader and I will probably manage to fix it only with full 7.1.1 retail image.
Glad to see you guys are making some progress. I'll try flashing the retail version on my Chinese Z Play. I'm currently on Epsilon rom (stock rooted 7.0) with January patch. Can I flash retail and then the ota?
I woulf suggest the following:
1) At your current firmware install Aida64 and check if you have addison or addison_cn product name in System section. If you see only addison - then you may install retail firmware and OTAs
2) If you still have addison_cn here then try to install retail firmware provided above (bootloader can be upgraded) and then check product name in Aida64 again. If it changed to addison - you can sideload OTAs. If still addison_cn - then you can't
Thanks @freeman_g
Here is a screenshot of AIDA64 on my device: https://imgur.com/gallery/Or2JF
I guess I should be good to go, right?
Yes, should work
What I can't understand why I still with addison_retcn. Probably, will have to wait for full 7.1.1 retail image
Sorry for the noobie question, but how did you guys with XT1635-03 flash the XT1635-02 firmware? Did you use this script? Did you flash the full rom, including partition, fsg, and modem, no restrictions? I bought my device at Banggood. I know it will come with a shop rom and I would like to install the stock firmware. I want to be prepared when it arrives. Don't want to take the risk of brick it and would like to leave the custom roms for later.
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
freeman_g said:
Ok, I have finally found why some people (and myself) have problems with 7.1.1 OTA on xt1635-03
As I mentioned before, OTA just refuses to install mentioning wrong device name (addison_retcn vs addison)
The problem is standard instuction for flashing any firmware with fastboot missing these lines:
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
After flashing these files I saw correct "addison" name in Aida64 and managed to install 7.1.1 OTA on my XT1635-03
People who use RSD Lite did not have such problem as this program use xml file contained both commands (oem and dsp)
It is better to have unlocked bootloader as at first attempt OTA was flashed with some mistake and the phone did not boot. After restoring full image (7.0) with fastboot I managed to sucessfully sideload OTA and now have 7.1.1 on my Chineese device.
Hope this helps
Click to expand...
Click to collapse
Awesome, many thanks for sharing. Does this mean you'll receive future OTAs?
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Iam uploading my special Bricked moto Z Loader Stock Oreo TWRP Moto G5+ for those who may need it, ciao!!!
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
SowilM said:
Thank you very much, I just followed your method, very fast and clean, thank you I got Oreo on my phone!
Click to expand...
Click to collapse
Happy to help brother!
So this will work for european users who did not break their persist?
Fabiuz99 said:
So this will work for european users who did not break their persist?
Click to expand...
Click to collapse
As far as i Know only for retail americas but you can try on your own and let us know
Battery performance is for fully happy and satisfied OVERWHELMING
will it work for indian version
will it work for indian version
---------- Post added at 06:48 PM ---------- Previous post was at 06:00 PM ----------
prnv1312 said:
will it work for indian version
Click to expand...
Click to collapse
thnks alot man
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this?
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
can i update my moto g5 plus build number NPNS25.137-93-14 rooted with this? june security update
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
download file from my gdrive: https://drive.google.com/open?id=1XWoaudSHAhQMWi3Au4wmtf2QaCrhugoD
Now to what matters...
Important!!! Only for RETAIL versions AMERICAS with working band base ending in ¨R¨, also for people who DID NOT mess up with persist and EFS...otherwise it is likely to loose IMEI...also....working for previous BRICKED devices that need to use Moto Z bootloader, but only RETAIL AMERICAS versions.
Anything else, please read and follow this post here: https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433
download and unzip file.
extract ROM folder and copy within very same folder the adb fastboot oreo g5+ folder and content extracted in same folder all together.
before going on, make sure you have motorola latest drivers installed, found in ADDONS, adbz folder, motorola device manager.
restart phone in bootloader, connect to laptop.
run file with name OREO G5 PLUS DE CERO.bat (spanish whatever), once done, unplug and restart phone.
should delay a few moments and go into setup.
additionally, you may want to install latest TWRP 3231 found in RECOVERIEZ folder.
additionally, you may want to flash motorola boot logo found in BOOT LOGOZ folder, to prevent the unlocked phone boring screen.
additionally, you may want to flash Magisk 17.1 in ROOTZ folder, only Magisk file, nothing else.
additionally, you may want to flash Kernels like Extended or EX found in KERNELZ folder.
some apps in APPZ folder that I use.
in REVIVALZ you may find files to bring bricked phone to life, but that is another history you may need to find out by reading posts.
in ADBz you can find extra folders for CMD commands.
This tuto is for knowledgeable people.
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
For further updated official releases, just flash as regular in adb-cmd.
Ciao Babies!!!
Click to expand...
Click to collapse
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
I am friom mexico and my phone is working perfect...is your question anserred alwearu...can not go back to nouhat
will it work for indian version XT1686
LLegion said:
Safe STOCK Oreo by Fastboot FULL flash:
I have my device working fine in official stock again, however........BOOTLOADER STAYS FOR MOTOZ, meaning, you cannot take OTAS, reason for which locking Bootloader is unnecesary, recommended that once TWRP3231 is flashed, you may backup averything, all partitions, remember this is the last backup for official STOCK we will have from Motonovo.
Click to expand...
Click to collapse
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
carloandreaguilar said:
will it work on a latin american one? xt1680 currently on npn25.137-92 november patch unlocked bootloader. This is not my daily driver. If the flash of this oreo rom doesnt work, can i just reflash my npn25.137-92 firmware back? or will that not work?
Click to expand...
Click to collapse
nvrpayretail said:
Can you please clarify the above info. I have a U.S. x1687 that is still stock nougat that I'd like to upgrade to Oreo (since Motonovo screwed everyone with the August security update and lots of us are experiencing major battery drain issues!) . I'd like to remain completely stock if at all possible. Any way to update with the Moto G5+ bootloader?
Click to expand...
Click to collapse
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
LLegion said:
You need bootloader open and yess you can flash safely it ks stock and battery is workimg awesome
Click to expand...
Click to collapse
Sorry, I still a bit confused. The text I quoted says "bootloader stays MotoZ". If I install this update, as is, will my bootloader be MotoZ or remain Moto G5+?
Thanks...
I have the US version (retus), bootloader unlocked, nougat 7.0 with August patch (NPNS25. 137-93-18). Can I use this method safely? Thanks
I do not know what else to say...just flash as edpalined if phone breaks then unbrick it reading other tutos sorry pals but seems you are not reading enough
No risk no Win buddies
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
JohnSmith8786 said:
Hi, great write up! I like how your zip is a one stop shop. I used the included Moto G5+ toolkit to flash the stock Oreo zip which worked perfectly. I down graded to stock 7.1 from custom 9.0 however I'm noticing while on official Oreo whenever I reboot the device it will TWRP loop back into recovery and the only way to get back in the system is to go to bootloader and boot to system. Anyone else had this happen and fix it?
XT1867
OC.92 bootloader (unlocked)
TWRP 3.2.3.1
Click to expand...
Click to collapse
Do no flash from twrp but from runnimg the batch file oreo desde cero and it will flash the recobery as well to the oreo stock and thats it.buddie
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
metalik said:
Hi all,
I'm in need of some guidance with regards to a downgrade that I'd like to perform.
About 1 week ago the phone updated itself OTA. I don't remember which version was last before this update .. but what I remember is that the download was quite consistent (over 1G) and then the update took a while. Everything went by without any errors, but at the end I got Android Pie ... and I don't like it.
Reading through the forums I found that flashing a Xperia is doable .. with the right care and tools. So I started to get acquainted with newflasher and Xperifirm - but for now not connecting the phone and / or trying anything and here are the questions for anyone who might guide me a bit:
1. the phone is warranty (about 4-5 months old in fact). I believe the latest firmware that it was running with Oreo was 47.1.A.16.20-R6B. Reference = h**ps://xpericheck.com/cda/1310-4373. I don't see that version in Xperifirm => how can I get access to it for re-flashing?
2. as far as I read, I don't need to root it or unlock the boot loader. Just flashing would be enough to go back one firmware "edition".
3. backing up user data does not interest me so much. I have a list of all apps that are currently installed and within a few hours of tinkering I could get them all re-installed.
4. Would the process of downgrading be visible afterwards? - i.e. warranty would be "bye-bye", right?
.. any other comment / note / reference or observation is highly appreciated.
Best wishes!
Click to expand...
Click to collapse
There is a post in different thread that should answer all of your questions. I couldn't write it better myself, so here you go https://forum.xda-developers.com/xperia-xz1-compact/development/help-t3889845/post78673359
I hope it helps.
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
metalik said:
Hello,
Thanks for the quick reply.
For sure it confirms my understanding of the process.
Would there by any chance to find my Oreo 8 previous firmware (47.1.A.16.20) but for my "Customized DE" version?
It intrigued me that Xperifirm has just the latest one.
Click to expand...
Click to collapse
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Didgesteve said:
I don't think there will be any difference between customised DE and customised UK, there will be VoLTE and fingerprint enabled.
If you have to start asking other xda users for historical firmware then you can't guarantee its validity.
All the firmwares on Xperiafirm are direct from Sony servers.
Click to expand...
Click to collapse
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
the right question would be, how to get the latest security patches but staying with oreo?
vofferz said:
@metalik download the firmware with xperifirm and from settings select to decrypt/decompress (don't remember how it is). Then delete all .ta files from the folder and persist*.sin (to avoid losing android attest keys and flash with newflasher.
Flashtool has some problems with newer phone models so it's not recommended for xz1c.
Click to expand...
Click to collapse
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
metalik said:
I secured the Oreo firmware (customized UK) and the Pie firmware (customized DE) .. using xperifirm. I downloaded Pie just to have the current release that's running on the phone nearby, in case any of my attempts go bad and I'd need to restore it.
By chance, I have for about 2 weeks the possibility to have a non-branded original "Customized UK" XZ1c. As far as I've seen, there 1 app only that's different compared with my original customized DE. I might flash this one to Oreo and back to Pie ... just to learn the process ... and only afterwards to get to work on mine.
I also took my time to look around the web before jumping into flashing.
There are topics which I don't quite grasp yet .. like DRM .. or attest keys.
The thing is that I don't want to break anything in doing this downgrade to Oreo. I don't need to root it, to unlock the boot loader, to break any X-Reality or other functionality. I'm truly amazed by the battery life, btw: I get 3 1/2 days plus with Stamina activated non-stop. The phone is very snappy even with Stamina ... and that's another issue: by downgrading, I wouldn't like to ruin anything of the battery management internal apps / features.
Another thing is this: i don't intend to preserve any data. Whatever I have as apps, currently, will be backed-up and re-installed from scratch + restore of personal data.
I'm now at the point of going through:
1. flashing with flash tool + xperifirm
OR
2. flashing with newflasher.
Basically, I'm trying to understand what the differences (risks) are and what's the safest to use.
Any advice from the XDA community is welcome on this one.
Best wishes,
Click to expand...
Click to collapse
First take a screenshot of your current keystore status by typing this in the dialler *#*#7378423#*#*, then go to Service tests or Service info -> Security
I used newflasher since it's the last updated software for flashing.
Extract your ftf if required, put only the required files to downgrade in newflasher's folder. For me I only used kernel, system, userdata and cache.
Boot to flash mode, flash using newflasher, reboot and done! Make sure your keystore is intact by comparing the status of all keys with your screenshot.
I've used this method to downgrade temporarily, get temp root, backup my TA partition and then go back to current firmware. All keys intact.
metalik said:
gentlemen,
your input is highly appreciated.
aside from the persist*.sin and all .ta files .. should I take care of anything else?
P.S. I followed this tutorial (link) and it clearly indicates that warranty would not be voided if I would attempt such a re-flashing. Is it true?
P.S. the last question in the thread remains valid: how to apply the upcoming patches on top of Oreo? .. can those be obtained and flashed in a similar way? ... I doubt it would be a good approach because Sony is supposed to take the Google patches and make sure they integrate properly in their Android customization ...
Click to expand...
Click to collapse
I would flash everything else but the .ta and persist*.sin to ensure it works as intended with all files from the firmware you're using. Of course that resets all your userdata, but I guess a downgrade would require that anyway.
Warranty should be just fine - you're still just using official Sony firmware without any modifications to the device or system.
I don't think it will be possible to stay in official Oreo fw with locked bootloader and get recent security patches.
Sony will most probably implement the new patches only into the latest fw version - and that's Pie.
And if someone would make a custom rom with the latest patches on Oreo, you won't be able to install it with a locked bootloader.
Hello again,
what's the impact of flashing persist*.sin ... I believe that's connected with the attest keys, right?
Later edit: I downgraded from Customized DE Pie to Customized UK Oreo. I used newflasher, deleted all *.ta from the root & boot folder ... but by mistake I forgot about the one small persist*.sin file.
Long story short: yes, leaving persist*.sin file in the folder and flashing with newflasher destroyed the Attest keys (I get them as NOT provisioned).
The phone seems to work without problems nevertheless. I re-flashed to an older Customized DE Pie and got the last valid OTA update. Going back to Customized UK Oreo did remove everything from the Service Tests > Security (it showed "none"). But on that the Xperia Companion did the trick (software repair). So it's back on the initial Customized UK Oreo - just attest key shows NOT provisioned ... so
Lessons learned: /*.ta + /persist*.sin + /boot/*.ta must be removed before flashing with newflasher.
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
Hey,
sorry for the late reply ...
I kept everything that I (historically) downloaded with Xperifirm ...
I just checked and one folder is this "G8441_Customized UK_1310-6856_47.1.A.16.20_R18B" ... about 2.55 GB in size.
the content of fwinfo.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<fwinfo>
<project>Lilac</project>
<product>Xperia XZ1 Compact</product>
<model>G8441</model>
<market>United Kingdom</market>
<operator>Customized UK</operator>
<swId>1307-7511</swId>
<swVer>47.1.A.16.20</swVer>
<cda>1310-6856</cda>
<cdfVer>R18B</cdfVer>
<fsVar>GENERIC</fsVar>
</fwinfo>
and update.xml is this:
<?xml version="1.0" encoding="utf-8"?>
<UPDATE>
<SYSTEMPARTITIONIMAGE>partition.zip</SYSTEMPARTITIONIMAGE>
<BOOT>boot.zip</BOOT>
<NOERASE>appslog_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>diag_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>ssd_X-FLASH-ALL-C93B.sin</NOERASE>
<NOERASE>Qnovo_X-FLASH-ALL-C93B.sin</NOERASE>
<FACTORY_ONLY>persist_X-FLASH-ALL-C93B.sin</FACTORY_ONLY>
<NOERASE>userdata_X-FLASH-CUST-C93B.sin</NOERASE>
<SIMLOCK>simlock.ta</SIMLOCK>
<NOERASE>cust-reset.ta</NOERASE>
<NOERASE>master-reset.ta</NOERASE>
<RESETNONSECUREADB>reset-non-secure-adb.ta</RESETNONSECUREADB>
<NOERASE>reset-wipe-reason.ta</NOERASE>
</UPDATE>
in a nutshell: I can zip the folder and find a way to send it to you.
Best regards,
Joecalone said:
Hey, sorry to bring up this old thread but I don't suppose you still have a copy of 16.20? I've been looking for a working copy of it everywhere and I'm getting desperate
Click to expand...
Click to collapse
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Xperia XZ1 Compact 47.1.A.16.20 Firmware Search
metalik said:
in a nutshell: I can zip the folder and find a way to send it to you.
Click to expand...
Click to collapse
Shahnewaz said:
I have my copy of 16.20 and related firmware. They are all Generic Latin America versions.
Click to expand...
Click to collapse
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
@cynthi4 Customized NOBA (nordic/baltic) latest Oreo: http://aeitis.org/xz1c/
It's downloaded and decrypted via xperifirm and zipped.
I'll keep it there for a while, but might remove soon.
cynthi4 said:
Great! I have also been searching desperately for a G8441 47.1.A.16.20 firmware. The country doesn't matter.
If either of you are able to send a zip, I would love to host it on my drive for anyone else who comes looking.
Click to expand...
Click to collapse
Here you go:
https://bigboidrive.duckdns.org/nextcloud/s/ZW4FQmqBE8Dfcp2
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
moist_line said:
Hello, I just got a xz1c and I'm on 47.1.a.2.281. I haven't updated because of reported battery drain issues. Should I stick with this? Do you recommend pie at all? If not, what's the most stable build you'd recommend?
Click to expand...
Click to collapse
Unless you have any specific issues with Oreo or see some advantage with upgrading to Pie, I wouldn't. I am not a big fan of Pie and went through this downgrade to 47.1.A.16.20 to avoid it. If you're interested in custom ROMs, I am running LineageOS 15.1 on my xz1c and it's been great!
That's strange. Being still happy with my locked device, I've always regretted switching to pie so today I actually did the whole process to restore Oreo: downloaded the latest Costumized NOBA oreo the user few posts above linked, deleted *persist.sin and every *.ta files in the folder (even the one inside boot folder), run newflasher and then reboot. Too bad I found stock camera broken
I re-checked multiple times searching for those *.ta files to be sure to avoid this issue, but that's it: I got Oreo but now I have lost stock camera and who knows what else.
Does it mean I've lost those functionality forever? Is there any way to restore stock camera? Happy to see this thread still active
My G7 Thinq (G710EM) has been neglected for a while now, ever since I got a new phone. Right now, I want to setup the G7 as a backup phone, and to make it compatible with my current apps, I have to update it either to the latest official firmware (https://lg-firmwares.com/downloads-file/26010/G710EM30h_00_OPEN_EU_OP_0927) or the latest LineageOS (the latter is preferred).
Right now, the phone is still on Android 8 with an unlocked bootloader, and fastboot installed. However, I don't remember exactly how I flashed that firmware, nor how I unlocked the bootloader ¯\_(ツ)_/¯. I just remember flashing a .KDZ file.
I can't get anything to install/flash. What I tried so far to get the stock Android to work is:
- Update OTA: says no updates available; this was the case even before I unlocked the bootloader and installed fastboot
- Flash using LGUP_Cmd from this guide: I get Error!!! [SW_PATH] is null
- Flash using LG Flash Tool 2014 from various sources on the web: flash fails with the message Required info cannot be found (Contact the system administrator)
- Flash using LG FlashTool v2.0.1.6 from this guide: when I press start, a message box appears saying Failed to load
The earliest unofficial LineageOS I could find requires stock Android 9 to be installed, so I haven't tried that at all.
I'd like to know how can I upgrade to latest stock Android 10 or preferably to LineageOS 19.1? Losing all data in the process is perfectly acceptable, since the phone no longer contains anything crucial. However, in the end, I'd like banking apps to work.
Unzip this file and put the .dll file into> LGUP 2.0.1.6 folder > model > common folder.
If there is no common folder, make one yourself. Then try to flash .KDZ again.
I have a WW version of ROG Phone 6. I have had it since mid-July.
Previously, I had ROG 2 but it died on me unexpectedly and I switched to Pixel 6, which was very underwhelming. I pre-ordered ROG 6 as soon as it became available.
I have not seen a concise guide to rooting ROG 6. I think it should be the same as ROG 2 but just in case, I read guide to rooting ROG 5.
Are the steps to rooting ROG 6 the same as ROG 5?
Asus ROG phone 5: unlock bootloader and root guide
Asus rog phone 5 guide note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas. bootloader unlock: ! note that unlocking...
forum.xda-developers.com
Thank you!
I sure hope so. . . I cant find much material online but I'm going to try to just run this tool from asus https://rog.asus.com/phones/rog-phone-6-model/helpdesk_download/ and then flash magisk via recovery.
Sorry extract boot.img move it to phone, patch it with magisk and then run
Code:
fastboot flash boot magisk_patched.img
and that should do it. Although you may want/need to flash the official files first by running the flashall_AFT.cmd file.
Found this all on https://forum.xda-developers.com/t/...e-6-can-be-used-for-cn-ww-converting.4474383/ and https://forum.xda-developers.com/t/...-guide-you-should-read.4474241/#post-87255303
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
leathan said:
It worked for me without even needing to flash the full firmware (you'd have to, to switch versions though) let me know if you need help. the guides I linked might be overkill.
Just
1.) Fully update on phone.
2.) Install apk to unlock bootloader from my first link
3.) reboot to fastboot and run the command I gave above. (after extracting the boot.img from payload.bin and patching it, although the last link includes one prepatched that may work)
Click to expand...
Click to collapse
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
ausaras said:
Thank you for replying.
I read the guide about "flashall_AFT". I think the guy needed to do that because he was converting CN to WW. So, I think you are right in that the guide might be overkill since my phone is WW.
Thank you for taking time to outline the steps. The steps you outlined seems the same as for ROG 5. Glad to know that ASUS is consistent on this.
ROG 6 is the first phone that I ever pre-ordered. Usually, I buy phones when there are already guides on rooting. So, I am a bit nervous on rooting ROG 6 since there is not dedicated and concise guide yet.
Click to expand...
Click to collapse
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
leathan said:
Your good, just proceed as normal, I already got LSPosed, Zygisk+safteynet and all the goodies running. I see why you preordered this thing, its an absolute beast!! I am in love with it.
I wasn't even aware these phones existed but when I saw them and saw ASUS releases bootloader unlock publicly I instantly bought one as in general that's the main thing needed for rooting.
If you need any help It only took me about 15 minutes to root everything without using the guides at all as like you said it was pretty standard process. Like I said I extracted and patched the boot myself but just to potentially save time as I'm almost positive the patched image in the last link will work, and if it does not you can just reflash the one from the OTA.zip.
Good luck! (if you decide to root it will work fine)
Click to expand...
Click to collapse
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
You should be done. I just fully updated and then rooted and set up my phone.
The firmware flash would have been to swap over to CN or WW. If you do that then yes you would re-factory reset + re flash stock boot.img. Then afterwards repeat the boot.img patch to obtain root + repeat setting up your safteynetfix + any other magisk modules.
ausaras said:
I rooted my phone over the weekend. It went well.
Now, I am wondering how to update firmware. I know I need to download the full firmware from ASUS website and then place it in the root directory.
Should I flash back the stock boot.img and then update firmware?
Or, just simply flash the firmware update and then go through the whole extract boot.img from firmware, patch in Magisk, and then flash patched boot.img in fastboot?
Click to expand...
Click to collapse
Hi, I am sorry the last answer I gave you was just wrong. I totally forgot when we root we wont get automatic OTA updates. Which for me is a really good thing anyway. But to get the OTA updates we need to download the firmware files from ASUS website. The same place we downloaded the unlock app but its under firmware. Download every WW firmware and put them one by one in order from oldest to newest on the /sdcard and boot up and it will detect an update. I'm pretty sure we cannot just skip to the latest update like we can with custom rom otas so I am going in order.
I left root, and when done updating will again patch the boot.img and flash it over.
Over the weekend I helped a guy root and set up safteynet and if it helps others I might just write up a tutorial.
Cheers!
Hi! Thank you very much for sharing and helping. I have Tencent edition, from CN to WW, but a couple of things don't work properly:
- Android Auto does not communicate with my car (phone detected and bluetooth connected) bit app stops.
- Gboard voice dictation does not work (google assistant yes)
Country is WW. Safetynet passed. Play certified.
..I followed your guide.
I flashed the posted xda raw throuh fastboot and the the Magisk patched .img
When I tried TO apply latest updates (160) the Same message error appeared.
There is spmething strage (or are least I think It strage):
When I start in "fastboot" (black screen with capital text single line) my device isn'r recognized by PC. Then I switch to "recovery" and then to "fastboot" and a menu (several lines) with title "fastbootd" appears and the phone is recognized by PC (fastboot devices). If I choose bootloader the first screen appears.
I tried to reflash the raw but either the phone isn't recognized or a message appears on the cmd window showing "not rog 6" (more or less) and stops. But the phone is recognized everywhere as rog6...
I miss my broken rog2, it was much easier to root
Do you have any idea what's going on? Or when the twrp boot will be released so that I can brutally flash any zip?
i need fastboot driver for win 64
Anyone know if I root my phone following these instructions, will it factory reset or wipe my data partition? Sorry it's been a while since I rooted any phone, and I am excited about going this route
can anyone provide the patched boot image to have root? Tried looking and asking in other areas but no luck. Or is there a way to patch a bot image that contains root already?