Hello all
I've been reading about the software updates on this forum
I have been rooting and using custom firmwares on my android phones for years but
I don't know what you mean by RAW firmware and why people wait to uptade unless there is one
Can someone explain to me what is the difference between RAW and regular firmware
And why I should or shouldnt use it?
All the help is appreciated
It is not better, raw is for some phone that converted but didn't root to change the country version. For example, mine is CN unit, but I installed WW. So I can no longer receive update OTA, unless I root and change the properties to WW. But I do not want to go through the process.
So the only way for us to update, is to wait RAW version to flash it for new update.
With the update zips, there are some checks being done to make sure you are using a variant that's acceptable (i.e. if you have the CN fingerprint, you won't be allowed to flash an update made for the WW version). The RAW version has the full images for all partitions and the script you run erases the current partitions and flashes the new images without any checks, so it just works even if you have the CN fingerprint.
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?
Please anyone upload motorola update services apk from oreo rom
It is named ota in system partition
Search it with xplore and upload it
It is the easiest way to get oreo
#help
Tried it and not working
Anyone tried this idea?
ahmedAZ said:
Please anyone upload motorola update services apk from oreo rom
It is named ota in system partition
Search it with xplore and upload it
It is the easiest way to get oreo
#help
Click to expand...
Click to collapse
Updating the app won't get you oreo
Updates are pushed out in regions - they are geo restricted & also based on your current firmware
If you really want oreo the firmware from india/Brazil has been posted - just flash it via fastboot or just wait until they push it to your country & firmware version
Hey I was wondering, my wife just got her OTA notification for oreo and we have identical g5's cedric. I wanted to try to capture it on my phone so I restored to 137-93-14 and checked for updates.. It doesn't detect the ota.. Is it possible that having an unlocked bootloader and root prevents me from receiving it? I think I read somewhere that unlocked phones have it last. My wife's phone is totally stock untouched.
The reason I wanted to capture it even though the ota is everywhere on XDA is that I tried the twrp flashable oreo on my device and it didn't work. Which made me wonder if our update has something different than other phones (probably not) cause it seems that I'm the only one on the twrp oreo thread that hasn't been able to flash that update.
Btw I know I can't install official ota with my modified system I wasn't going to try it
Hi guys i recently bought a refurb phone and i want to unlock it and put some custom rom but i cant identify the real model of this device. i also tried opening the back and see if it has some model print on the motherboard but its not there i think. so ill put the pics of relevant info on my phone to help to identify it so thanks a lot for those who can help i would appreciate it
You must take out the motherboard. It is written on the backside
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
kukel21 said:
thanks its there turns out i have an 810 variant. Any tips for me to install marshmallow on my phone and usu it? because on my version of the device i cant update thru system updates its still on LP. should i flash stock 810 rom and update to marshmallow that way?
Click to expand...
Click to collapse
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2 - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
sdembiske said:
First thing is check your kdz version that you have installed - use steadfasterX's SALT program to do this. It will also establish your ARB version (must be less than or equal to 2) - if not, i.e., if greater than 2, UsU is a no-go in your case). It will also let you know your GPT compatibility to show you what custom roms versions you can install.
Once that is ascertained, if you are rooted, re-install your stock LP kdz first (important), then proceed to upgrade to Marshmallow (MM) using LG Bridge first (download from LG site, it will sometimes work when OTA doesn't). If that doesn't work, you'll have to download an MM kdz for your model and carrier and upgrade it with LGUP-NEW. Then, once you have stock MM installed, do at least a partial backup with SALT before proceeding to unlock with steadfasterX's UsU method. Make sure you read and understand the OP completely there.
Click to expand...
Click to collapse
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
dharakv said:
Is the ARB value stored as a variable? I'm guessing its just a variable that gets checked during a KDZ flash. If so, where is the ARB value stored, and why can't we just overwrite it with 0? Has anyone tried this already?
If it's not possible, can't we alter the ARB values of specific KDZ's? For example if your phone has ARB value 3 and you want you want to flash a KDZ with ARB value 1, can you change the ARB value of the KDZ from 1 to 3, so it won't brick?
Click to expand...
Click to collapse
Suggest you read the OP in the UsU thread and pay particular attention to REQUIREMENTS #2.
If you really want to hard-brick your device then go ahead -- i.e., you cannot alter the arb value !!!
I found my answers after posting this thread, sorry for the clutter. Please ignore, can't find a way to delete. Thanks! (If a mod sees this, please delete thread)
So I am about to order a chinese RoG II Phone, my goal is to ask to leave the chinese rom as I don't want to lose OTA and I would like to see for myself if I can make do with the chinese fonts here and there... but my question is, if I happen to dislike it and flash the WW rom, I understand I lose OTAs, how about if I flash back the CN rom, will the OTA function return to the phone or is it essentially a one-time deal type of thing? As soon as you flash, OTAs on the device are essentially gone forever??
(Edit: I have read in a different thread that the bootloader can be "re-locked" I assume that is bringing back the phone to it's original state and therefore reinstating OTA as the device will appear to have "never" been flashed a different rom? If possible, please confirm)
While I am at it, any Google Play Services APK will do for sideloading? Can I just grab the latest version? Wait... Is sideloading as simple as just grabbing an .apk and installing it like any other app directly from the phone?? Lulz
Thanks!
WhyKlwd said:
I found my answers after posting this thread, sorry for the clutter. Please ignore, can't find a way to delete. Thanks! (If a mod sees this, please delete thread)
So I am about to order a chinese RoG II Phone, my goal is to ask to leave the chinese rom as I don't want to lose OTA and I would like to see for myself if I can make do with the chinese fonts here and there... but my question is, if I happen to dislike it and flash the WW rom, I understand I lose OTAs, how about if I flash back the CN rom, will the OTA function return to the phone or is it essentially a one-time deal type of thing? As soon as you flash, OTAs on the device are essentially gone forever??
(Edit: I have read in a different thread that the bootloader can be "re-locked" I assume that is bringing back the phone to it's original state and therefore reinstating OTA as the device will appear to have "never" been flashed a different rom? If possible, please confirm)
While I am at it, any Google Play Services APK will do for sideloading? Can I just grab the latest version? Wait... Is sideloading as simple as just grabbing an .apk and installing it like any other app directly from the phone?? Lulz
Thanks!
Click to expand...
Click to collapse
Hi, once you flash any raw firmware whether it's WW or CN. You lose OTA and the consequences for now aren't reversible. So if OTA updates are important to you, you better not flash any raw firmware, it's even better to get the global version instead. Regarding locking and unlocking the bootloader, yes you can do it but it doesn't mean you will not lose warranty for now users who have flashed the same raw firmware of the device "CN rom" haven't been able to go back to the default system state, meaning if you took the device to the service center for what ever reason they would be able to detect that you have altered the system and consequently refuse to service the device for free.
Regarding the play store, you only need to get the latest apk file of the play store and simply installing it. That's it after that you can install/update any app you like.
Rashad83 said:
Hi, once you flash any raw firmware whether it's WW or CN. You lose OTA and the consequences for now aren't reversible. So if OTA updates are important to you, you better not flash any raw firmware, it's even better to get the global version instead. Regarding locking and unlocking the bootloader, yes you can do it but it doesn't mean you will not lose warranty for now users who have flashed the same raw firmware of the device "CN rom" haven't been able to go back to the default system state, meaning if you took the device to the service center for what ever reason they would be able to detect that you have altered the system and consequently refuse to service the device for free.
Regarding the play store, you only need to get the latest apk file of the play store and simply installing it. That's it after that you can install/update any app you like.
Click to expand...
Click to collapse
Hi , I had buy a rog phone 2 Tencent game and I have got an WW rom from the buyer so now I will never get an OTA even if I return to CN rom
masl100 said:
Hi , I had buy a rog phone 2 Tencent game and I have got an WW rom from the buyer so now I will never get an OTA even if I return to CN rom
Click to expand...
Click to collapse
https://forum.xda-developers.com/rog-phone-2/how-to/flashing-ww-rom-changing-cn-fingerprint-t3969765
Follow the link and check the vendor file and see if the country is WW instead of CN. Try to change it to WW if it's still CN. If this doesn't work go back to Chinese Raw firmware flash it and change the vendor to CN and see if that works for OTA updates.
WhyKlwd said:
... (If a mod sees this, please delete thread)
...
Click to expand...
Click to collapse
THREAD CLOSED! Please be aware that XDA currently has more than 3.5 million threads i.e. we just see such a message by accident.
The best is to alert the moderators' team via the Report Functionality.
Hi,
I can't manage to find Full OTA package for the Chinese variant. Firmware finder is not very helpful, as it only finds OTA updates, that weight ≈ 300mb.
Actually all i want to do is get gapps working and i thought it might be easier on a custom OS, but i won't proceed without a backup plan to get it into working state if i ****ed things up.
Does anyone know where i can find Full OTA of EMUI 9.1 (Android Pie)?
By the way, do the rooting/unlock/recovery guides work for all variants or do i have to find the one for BND-AL00?
One more question, what would happen if i flashed international firmware onto Chinese variant?