Hello,
my Pixel XL came from T-Mobile Germany.
I am in TWRP alpha2 and SR4-SuperSU-v2.78-SR4.
My Pixel XL is on NDE63H.
I logged the OTA download process used the link in there and got now the 68MB small OTA.zip.
Can I use TWRP and this small update OTA to update to NDE63U,
or do I need to use the large 850MB OTA file from the google develope site to do so -> marlin-ota-nde63u-56d5b07a.zip?
I think I will loose root by using the large one, but will I loose TWRP as well?
My preference would be to use the small one, but will it work via TWRP and will I loose root as well or will this only update the necessary files?
Any help is highly appreciated.
mancman
I haven't tried it on the pixel, but on my previous Nexus device (N6), the small OTA would fail if the devices was rooted or had any changes to the system partition - that's because the small OTA was an incremental update, and was checking to see if the system partition was modified in any way before applying the OTA.
The full OTA would work - but you would lose the root/TWRP. Reinstalling TWRP is just a fastboot command away, so why is that a big deal?
Hello jj14,
I tried it.
First within TWRP and then by sideload and both failed with the same error.
I first needed to get a newer version of adb, but it failed as said above as well via sideload.
See error message here in the attached picture.
Any hint?
As far as that error, it means the binary update files are missing. That could be because the structure of OTA's changed. Without seeing the OTA I cannot say for sure. I would post that screenshot in the twrp thread and ask @Dees_Troy what he thinks.
Hello Scott,
thanks for your answer.
I wrote Dess a message.
Attached 2 screenshots which show what is in the zip from the OTA file and one for the comparison to a Nexus 10 zip,
you see that the update-binary is missing, so Goggle has changed things here as you postulated.
Thanks,
mancman
I assume you are trying to sideload the full OTA file. If so, what error did you get using the ADB sideload? (yes, you will need the newest version of ADB - download from the Google developers site). TWRP is still very new, so there may still be some bugs to address - Dees is pretty good about quick updates/fixes though.
I may be wrong here but shouldn't you flash back stock recovery before applying stock ota ??
Related
I purchased the tablet online in China about two months ago, so I got a tablet running CN system. (A5CN51C as I got it.)
So I followed a manual and immediately flashed a A5FM51C system.img to my tablet.
When the OTA A5FM91E came, I checked up this forum, only found high risk of updating.
While today, while I consulted a Chinese forum, there is a method to safely update the tablet to a newer version of system without converting back to CN systems ( meanwhile the boot is still lost after updating ! )
Basically, for all who initially has a CN system installed and successfully converted to TW version, there is a way to update your system while keeping all google frameworks.
Method is listed below.
1. Enable developper mode and USB debugging, and connect to PC using adb.
2. Flash the corresponding boot.img and recovery.img to the tablet. (By saying corresponding, it's the boot.img and recovery.img must match the version you're using. For eg, I'm updating from a A5FM51C version, so I should at least have a boot.img and recovery.img of A5FM51C.)
Below you can find the boot.img and recovery.img of A5FM51C.
HTML:
http://pan.baidu.com/s/1gdwKN7P
Password 2jwi
or https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
command on adb shell should be like :
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/pci/pci0000:00/0000:00:01.0/by-name/boot
3. After rebooting once and rebooting into recovery mode, check if the recovery is converted to the targeted version.
As I am updating to a system with Google applications, I should check if the version is marked FM.
4. In the recovery mode, side load the updating zip files, after a patient waiting, the system should be successfully updated.
ATTENTION ! [/SIZE]the zip file should be a full updating file, NOT A PATCH zip. So the file you are side loading is at least 300+ M.
If you are updating from A5FM51C, you can directly download from the links below two files.
HTML:
A5FM91E 848.38M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FM91E_update.zip
A5FMB19 816.04M
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FMB19_update.zip
5. The first time booting the updated system could be time consuming, so take a cup of coffee and be patient.
All credits should be given to the Baidu Tieba user "遇上咨询", and if you happened to be capable to read Chinese, you can visit http://tieba.baidu.com/p/4174802149 for further consult.
PS.
I updated from A5FM51C firstly to A5FM91E, after once rebooting normally into the system, I then updated again to A5FMB19, just being careful not to cause any damage.
And after updating there could be several applications crash unconditionally, since I've been using the system for less than 24 hours, I am not sure if this situation can be optimised after a period of time.
So the update only brought the Android version to 5.1.1, and Nokia added a "Close all app" button in the overview. Consider again if you are willing to spend one hour to update the tablet into a very similar system !
Wish you luck.
Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again
Neegola said:
Update
As soon as I finished updating the "System Webview" app to newest version at Play, all those apps started running again
Click to expand...
Click to collapse
i'm update to A5CNB19 today. How can move Chinese to Taiwan?
thanks for your post, is there any chance to make it rooted in A5FMB19 ??
thanks
p233 said:
i'm update to A5CNB19 today. How can move Chinese to Taiwan?
Click to expand...
Click to collapse
Originally, I converted my tablet at A5CN51C, with root. Following this manual.
http://forum.xda-developers.com/nokia-n1/general/n1-taiwan-release-t3083115/post62313790
So using this method to convert, you should guarantee a valid root state executing DD command on adb shell.
So I personally think that at least you should wait for a root method, then there would be a chance for converting system.
I directly updated from A5FM51C to A5FMB19 (not went through A5FM91E . confirmed it's okie with this method
Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.
Xiware said:
Thanks a lot. I confirm that we can directly update from A5FM51C to A5FMB19. I just have a question, if an update release can i do the update by the ota ? Sorry for my bad english.
Click to expand...
Click to collapse
After converting the recovery and boot partitions to FM version, there should not be a problem in updating directly by OTA.
Before, when I execute OTA, it will pop up a message read "Could not download the update, please check the storage". And after, I could successfully start the download. It was because the limited network speed, I've chosen to side load the update package.
But it's merely my guess. Since the tablet has at least 20 partitions, and I don't know if there's any other which could influence this process. Maybe we could invite a real expert to join in this discussion.
Are you update with OTA?
gazziandrea said:
Are you update with OTA?
Click to expand...
Click to collapse
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.
Neegola said:
No.
But technically I did use the ota package to update. Given it was a whole system compressed file.
Click to expand...
Click to collapse
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?
gazziandrea said:
I did rootare the devise to other people ( chinese guys) and i dnot have many experience in modding, only with TWRP in Xiaomi Redmi Note 2, so I can update via OTA diretly ?
Click to expand...
Click to collapse
Hi, I'm afraid I don't understand what you are asking.
Do you speak any other languages like Chinese or French, or your native language so I can do a google translate ?
Thanks for these updated information.
Hi, guys, thank you for help with moving from CN to TW. I've done this from rooted A5CN51C to A5FMB19.
But, now I've got system reboot every 15 min. Uptime no more than 30-35 min. It's very unstable during watching video (e.g. youtube app). Do you have the same? Model: n1s.
Hard reset doesn't solve this problem.
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?
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
ast00 said:
First of all this phone belongs to my dad. This means I haven't used it and I'm not familiar with many things about it.
The phone is running a stock ROM. It is not rooted, but it does have TWRP.
A software update prompt popped up trying to install "v20p-apr-03-2018" (why is an update for the G4 called v20 lol).
Telling it NOT to download it and NOT check for updates ever doesn't work. The update prompt comes back in 2 days tops. So **** you LG.
Since it's not rooted the easiest option seems to be to flash the update, however it just launches TWRP and does nothing. I found no way to actually download the update and keep it on the device so that I can manually tell TWRP to flash it.
So: Is there a way to download said update and flash it through TWRP? Or should I root it and delete the stupid update tool? I really don't want to flash a stock recovery.
Click to expand...
Click to collapse
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
sdembiske said:
Freeze or uninstall Software Update (LG proprietary, i.e., closed source, app) - may require root. That should stop the annoying requests. If you are able to upgrade you will lose TWRP and will have to re-flash TWRP again. You may want to consider that you do not have the latest Google security patches by not doing the update, putting your Dad's phone more at risk.
Click to expand...
Click to collapse
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
ast00 said:
It's not like LG updates security patches that often so it's not that big of a deal if I can't update it.
It's also fine if I lose TWRP during the process, I just want to avoid flashing stock recovery just for the sake of updating it.
And I still can't download the update and keep it. I don't know where it puts the update after downloading it. I couldn't find it in TWRP.
Click to expand...
Click to collapse
It helps if you include your phone model when looking for specific firmware updates.
If you're Dad's phone is an H815, there are some v20p downloads available here: https://lg-firmwares.com/lg-h815-firmwares/firmwares/
In order to flash in TWRP without losing TWRP, you would have to remove the stock recovery and create a flashable zip ...
Easiest is to simply freeze or remove the lg Software Update app as I indicated - the annoying update notification should then disappear ...
Note: XDA courtesy is to hit the Thanks button (bottom right of post), when members are trying to help and solve your issues. As a Senior Member you know this.
This update does not contain any security fixes it's just for the new European data protection law..
First thing you should try is:
Upgrade TWRP.
Do a full TWRP backup!
Test android update again.
Second thing:
Have you tried the LG bridge windows software to update?
If so and it fails there too you can find the update when you try to Flash it within the LG folder of your Windows PC afterwards use this KDZ file and lgup to flash it.
There is a chance that when using the internal updater that you can find the update file when in TWRP in /cache in a folder fota but it will likely be in a LG specific format so may don't help you much.
Third thing :
Disable the LG updater within TWRP (search for a howto)
Sent from my LG-H815 using XDA Labs
Sorry if this has been discussed elsewhere. I couldn't find anything about it specific to the pixel 3xl.
Has anyone tried Flashfire to install an OTA update?
I have it installed. It recognizes is an A/B partition device. I've seen that there are people that have done it on the pixel 2.
Just curious if anyone has given it a shot. If it was successful, what steps did they take?
Just looking to see if it's possible to take an OTA and maintain root with magisk using Flashfire.
I wouldnt mess with flashfire, it hasnt been updated in ages
I haven't had a chance to try it because my device doesn't get the OTA notifications right away and I get tired of waiting so I download and flash the factory image, but you could try topjonwu's OTA update instructions here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Greetings.
Let's say I accidentally DL'd the OTA from the OEM update screen. Where in my file system might I find the file? I read that it may expire and vanish. It's that true? Kind of afraid to reboot right now. Thanks in advance.
Pixel 2xl, rooted, Magisk, OEM 10, Aug. rev.
Even if the OTA did expire and vanish, and I have never heard that happening, Google makes full OTA images available at https://developers.google.com/android/ota in the Taimen section. As to where they are located, likely in the /data partition, but I have absolutely no clue where exactly they are.
I would simply reboot, as the system has most likely already applied the OTA and simply needs to finish completing the update.
So I had to reboot, now I lost root. Is there an easy way to get it back or do I have to wipe?? Thanks.
Boot - NOT install - TWRP using fastboot on the bootloader screen and flash a copy of Magisk you should have stored on your unit.
If you need detailed instructions we have a rooting guide on the forum that should help. Just make sure not to install TWRP or the unit will end up bootlooping, requiring you to flash the full firmware to fix it.