Develop Bugs

Moto z play (xt1635-03) transformation 64 GB ROM + 3GB RAM

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?

Trouble installing stock firmware on samsung galaxy a5 2017 sm-a520f

I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.

Flash a firmware version that contains S6 or U6 in the middle, it won't work with U5/S5! Not the Samsung phone S5 or S6, but rather, the firmware version.
For cellular, change the modem firmware, or backup and wipe /data/. /data/data/?.
Unless the efs was wiped (probably not if the baseband version isn't there, load a backup then, only if the efs was wiped don't restore it otherwise, and it must not be a backup created with an older twrp, view the recovery log in the backup folder)

julianmunozvaras said:
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Click to expand...
Click to collapse
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs

iloveoreos said:
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
Click to expand...
Click to collapse
I tried installing the latest version available and I had the same error.

julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Well, I don't know what else could be wrong.
Sent from my Samsung SM-A520W using XDA Labs

julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Listen to me, it happened to me 2 days ago, and I came to the conclusion that I was not flash the latest firmware. You need to flash the same firmware with the same bootloader or more recent, the error you receive is because you are flashing an older version of bootloader. Do one thing, type the code *#1234# on the phone keypad
mark the code that gives you on 'AP and look it on Sammobile at https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ITV/ select your language and look for the firmware with your own code . You will see that odin flash it.

Samsung A520F Custom Binary Error
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out

koolblowkid said:
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
Click to expand...
Click to collapse
Obviously you are frp locked. But I didn't think that blocked from flashing official.

Trying to stock my op7t and relock the bootloader

Hello can anybody help me?
everytime i try fastboot stock image it boots fine, but i want to relock the bootloader and be back on stock. can anybody help me
if i lock it , it just says this phone can not be booted or data is currupt
im trying msm but, i cant seem to install the correct driver in device managaer
i tried to install twrp but magisk error 1s. and noting can mount. so i need to go back to stock with locked bootloader. so i can use my banking apps again
cheers.

https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
just follow this, use the flash-all to go back to stock then relock when its all set
unlocking/relocking wipes your data so backup whats necessary

Crystallux said:
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
just follow this, use the flash-all to go back to stock then relock when its all set
unlocking/relocking wipes your data so backup whats necessary
Click to expand...
Click to collapse
Is this true? I'm seeing other posts says that you need to use the MSM tool in this scenario. Unfortunately, I only have a Mac so I can't run MSM.
---------- Post added at 08:34 AM ---------- Previous post was at 08:33 AM ----------
Did you get this to work?

I Have tried this several times on my Tmobile version op7t and every time I get to step 7,8,9 and flash-all (with Indian version 10 or Global version10), I end up with my Tmobile Stock 10.3 version of Android, and the wifi does not work. The only way to get the wifi back is to MSMDownload Tool the original stock version which locks the bootloader back up and I'm back with TMobile version 10.3. I downloaded the Fastboot version they suggested. Any ideas why it's not working and reverting back to my original version of Android 10.3?

ohcello said:
I Have tried this several times on my Tmobile version op7t and every time I get to step 7,8,9 and flash-all (with Indian version 10 or Global version10), I end up with my Tmobile Stock 10.3 version of Android, and the wifi does not work. The only way to get the wifi back is to MSMDownload Tool the original stock version which locks the bootloader back up and I'm back with TMobile version 10.3. I downloaded the Fastboot version they suggested. Any ideas why it's not working and reverting back to my original version of Android 10.3?
Click to expand...
Click to collapse
I was having a similar issue. Either the 10.0.9 version was the problem or I was making the error of manually navigating to the fastboot menu when a recovery type language select screen came up (black background with white logo and text). This screen would appear after flash-all.bat had mostly run through and the "Invalid sparse file format at header magic" was the latest output in command prompt.
What worked for me was to use version 10.0.8 and to not touch the phone until I saw the usual blue setup screen.

ImsumDave said:
I was having a similar issue. Either the 10.0.9 version was the problem or I was making the error of manually navigating to the fastboot menu when a recovery type language select screen came up (black background with white logo and text). This screen would appear after flash-all.bat had mostly run through and the "Invalid sparse file format at header magic" was the latest output in command prompt.
What worked for me was to use version 10.0.8 and to not touch the phone until I saw the usual blue setup screen.
Click to expand...
Click to collapse
Thanks so much. So perhaps I try 10.0.8. Can you confirm the exact 10.0.8 build you used? Global? Indian?

ohcello said:
Thanks so much. So perhaps I try 10.0.8. Can you confirm the exact 10.0.8 build you used? Global? Indian?
Click to expand...
Click to collapse
I used the Global build here. I followed this guide minus steps 1, 2, and rooting. I also downloaded and used the latest platform tools from google and I did not overwrite them at any step in the process.

ImsumDave said:
I was having a similar issue. Either the 10.0.9 version was the problem or I was making the error of manually navigating to the fastboot menu when a recovery type language select screen came up (black background with white logo and text). This screen would appear after flash-all.bat had mostly run through and the "Invalid sparse file format at header magic" was the latest output in command prompt.
What worked for me was to use version 10.0.8 and to not touch the phone until I saw the usual blue setup screen.
Click to expand...
Click to collapse
ImsumDave said:
I used the Global build here. I followed this guide minus steps 1, 2, and rooting. I also downloaded and used the latest platform tools from google and I did not overwrite them at any step in the process.
Click to expand...
Click to collapse
OK thanks so much. Do you think it makes any difference what OS I start from before attempting to move to 10.0.8? Right now I'm on Tmobile 10.0.10.HD63CB, but I see an option for a minor OTA update to 10.0.11.HD63CB

ohcello said:
OK thanks so much. Do you think it makes any difference what OS I start from before attempting to move to 10.0.8? Right now I'm on Tmobile 10.0.10.HD63CB, but I see an option for a minor OTA update to 10.0.11.HD63CB
Click to expand...
Click to collapse
I don't know. I believe that was the same build I was running before flashing.

ImsumDave said:
I don't know. I believe that was the same build I was running before flashing.
Click to expand...
Click to collapse
SUCCESS!... Using 10.0.8 did the trick... and I was able to root with Magisk Canary as well. Now I can update to Global 10.0.12. THANKS SO MUCH.

UPDATE - I forgot that I have to re-root after updating OS to 10.0.12. I was able to do that using the latest boot img from this thread - https://forum.xda-developers.com/on...t-international-magisk-patched-t4053945/page5

If you're on oxygen os ,then just flash a downgradeable oxygen os rom by using the local upgrade feature ,then just use the all in one tool or try the fastboot comand of oem locking it should unroot your phone and relock the boot loader ,relocking doesn't work on latest version of oxygen os..

Redmi Note 9 Pro Global : Trouble installing Lineage Recovery and Lineage OS (miatoll)

I need help installing Lineage Recovery and LOS on my Redmi Note 9 Pro Global version
I managed to unlock the bootloader but Lineage Recovery is messing with me. Once I flash it, I enter it, but can't seem to install LOS because it shows an error when I try to flash it.
Something in the lines of "adb: failed to read command: No status", or something like that. Also bricked the phone but managed to unbrick it.
On the official website it says in the instructions for the device:
Warning: Before following these instructions please ensure that the device is on the latest Android 11 firmware.
This is not necessarily the newest available version! Please up- or downgrade to the required version before proceeding (guides can be found on the internet!).
I thought I just needed to update my device with it's miui updater, but it seems I need to find this specific firmware version and flash it myself.
So if I got this right I first need to flash the firmware, then the recovery and then it should be able to install LOS?
Any idea where I can find this firmware cause there are a lot of files on the xiaomi official pages, not sure which to pick. Also, any good guides on how to flash firmware via adb?
UPDATE: Solved issue - Ignored the "error" and just rebooted to system after installation of LOS, no need for firmware. Just updated MIUI beforehand to newest version. Cheers!

How do I upgrade from rooted Android 8 to latest Android or LineageOS?

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.