Database Info

***ota not working! please help!***

hi!
i have honor 6 l02 version on b316 stock rom. i wanted to update to lollipop via local update and 3 button method ,but it doesnt worked for me. lately i've recieved an update to b317, but it also failed at the beginning of flashing. i have root and unlocked bootloader if its important information. anyone faced something like this, or maybe know solution?
thanks in advance

you need stock recovery in order to install OTA Updates

Im not a total dumb i wasnt able to use ota updates while having root and even without.. I dont think that unlocked bootloader would cause something like this too
Sent from my H60-L02 using XDA Free mobile app

but also not the smartest one, you need stock recovery to install otas. That's the point

Grr.. For me that seemed obvious that person who want to update via ota should have stock recovery. So thats all what you can figure out? That all beginned from moving from 4.15.6(or something like that) dev version to stable b316 via adb for honor 6. I always keep to those procedures but still without any effect. Now I dunno what should I do because none of people on this forum can find a way out of that problem.
Sent from my H60-L02 using XDA Free mobile app

Or maybe that was quite different.. I was trying to flash lollipop b532 while having that developer version. As we know it was failing cause flashing stable versions having a dev one doesn't work. Later they told me to downgrade to b316 via adb and then upgrade , so I did it and now I'm in a dead point.
Sent from my H60-L02 using XDA Free mobile app

flash your present ROM again and you can ota successfully. can not ota with root

Uhhh... I already did it like 2 weeks ago. I didn't had root then, only unlocked bootloader. Fine then, I'll do it again.. Do I have to repeat flashing that rom until I succeed?
Sent from my H60-L02 using XDA Free mobile app

007zzz said:
flash your present ROM again and you can ota successfully. can not ota with root
Click to expand...
Click to collapse
I had a rooted B380 with stock recovery and flashed without any problems to Android 5.1.1 (Emui 3.1) via dLoad -folder procedure.

Found out that I have error in recovery.log file in splash2 folder in root. Seems that something's wrong with modem 6085.
[2015-10-31 15:52:02 597] int cust_update_logo(int),line=1429: update logo,the type is 1 ,(1:FORCE,0:LIMIT) [2015-10-31 15:52:02 611] int cust_update_logo(int),line=1445: vendor is unicomelectric/cn,start updating logo [2015-10-31 15:52:02 612] int write_logo_to_oeminfo(const char*),line=1325: write_logo_to_oeminfo[1325]logo file path = /cust/unicomelectric/cn/logo/oemlogo.mbn [2015-10-31 15:52:02 663] int is_update_logo(char*),line=1234: this cust logo is new logo! [2015-10-31 15:52:02 663] int is_update_logo(char*),line=1246: the picture len is 4147280, the offset is 0. [2015-10-31 15:52:02 769] int is_update_logo(char*),line=1275: logo type is 41, the logo is the same. [2015-10-31 15:52:02 770] int write_logo_to_oeminfo(const char*),line=1363: Don't need to update logo! modem_has_6085: 6085 not exit,-1 huawei_nv_bin: no 6085 modem! [2015-10-31 15:52:02 799] void ota_post_update(int, const char*),line=560: erase cach
Any ideas?

Pootch said:
I had a rooted B380 with stock recovery and flashed without any problems to Android 5.1.1 (Emui 3.1) via dLoad -folder procedure.
Click to expand...
Click to collapse
Because you use the complete package. Only ota can not with root. Because ota will check your system completeness. Root will break the system completeness.

Unable to flash Official Lineage OS on my Yu Yunique Plus

when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.

Aditya2512 said:
when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.
Click to expand...
Click to collapse
I'm facing the same problem ... then I tried to remove this META-INF/com/google/android/updater-script/assert(cm.verify_baseband("2.0.2.C1.4-00039") == "1"); line, worked for me... it flashed .. booted .. but at second rebooting (due to data toggle error) its nav bar got inactive ... recent apps were not showing up... so I need to leave it .. at often it was getting into bootloops

Anjan Roy said:
I'm facing the same problem ... then I tried to remove this META-INF/com/google/android/updater-script/assert(cm.verify_baseband("2.0.2.C1.4-00039") == "1"); line, worked for me... it flashed .. booted .. but at second rebooting (due to data toggle error) its nav bar got inactive ... recent apps were not showing up... so I need to leave it .. at often it was getting into bootloops
Click to expand...
Click to collapse
I tried it but not working even not flashing.
BTW thanks.

Try using TWRP 2.8.7.0 for flashing ROM.
Aditya2512 said:
when I flash CM-13 unofficial VoLTE it got soft bricked after 1-2 days and I'm not able to flashed any custom rom and then I'll flashed the experimental cyanogen os firmware and then I flashed the stock firmware but there is no VoLTE option in the stock rom but previously before flashing custom rom there is VoLTE option available in stock rom and then I flashed the cm-13 unofficial VoLTE and now works fine but yesterday Lineage OS released the official lineage-14.1 and when I flashed it it says failed to read current BASEBAND version:2 and it failed to update.Please help and I also uploaded the screeshot.Please help me.
Click to expand...
Click to collapse
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
P.S.
You can also use TWRP 3.0.2.0 for jalebi.It works fine.

SSAURABHH said:
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
Click to expand...
Click to collapse
Edit Updater Script and Delete all its Content & Paste this
assert(getprop("ro.product.device") == "jalebi" || getprop("ro.build.product") == "jalebi" || abort("E3004: This package is for device: jalebi; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);

I have installed lineage all was ok. But suddenly after 1/2 an hour it got off..
When I try to switch on its got bloated

I've got the same issue and thats why I cannot upgrade to 14.1.It shows failed to verify the current baseband version: 2.
please help.

SSAURABHH said:
I have just faced similar issue,I was using TWRP 3.0.3.0,then I downgraded to TWRP 2.8.7.0,and it flashed
Click to expand...
Click to collapse
i'm on 2.8.7.0 but still facing the issue
---------- Post added at 07:10 PM ---------- Previous post was at 06:33 PM ----------
Indrajeet Singh said:
Edit Updater Script and Delete all its Content & Paste this
assert(getprop("ro.product.device") == "jalebi" || getprop("ro.build.product") == "jalebi" || abort("E3004: This package is for device: jalebi; this device is " + getprop("ro.product.device") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "/data", "");
package_extract_file("META-INF/org/lineageos/releasekey", "/tmp/releasekey");
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
set_progress(1.000000);
Click to expand...
Click to collapse
Comparing BASEBAND version 2.0.2.C1.4-00039 to 2.0.2.C1-36914ERROR: It appears you are running an unsupported baseband.
ERROR: It appears you are running an unsupported baseband.script aborted: assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"

NageshGeek said:
i'm on 2.8.7.0 but still facing the issue
---------- Post added at 07:10 PM ---------- Previous post was at 06:33 PM ----------
Comparing BASEBAND version 2.0.2.C1.4-00039 to 2.0.2.C1-36914ERROR: It appears you are running an unsupported baseband.
ERROR: It appears you are running an unsupported baseband.script aborted: assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
assert failed: cm.verify_baseband("2.0.2.C1.4-00039") == "1"
Click to expand...
Click to collapse
Your device's baseband is updated(20151215),and btw the issue is not the same,both errors are diffrent.TWRP 3.0.3.0 for jalebi.img has some issue while reading the baseband(Probably only in LOS),if u want to use 3.x version u can use twrp 3.0.2.0 for jalebi.img,it works fine,but in your case the issue is different,you have to downgrade to the oldest baseband for the device.And please do not edit the script,if the baseband version do not match(like in your case) and u installed the ROM somehow,you may end up with a bricked device.
Btw LOS 14.1 is not booting up,if boots,then in the next reboot it stucks at boot animation.

Do anyone has working solution?

yes i do.
Dush4711 said:
Do anyone has working solution?
Click to expand...
Click to collapse
follow these steps to remove the zip verification codes.
1.) unzip the rom in Pc
2.) go to extracted rom folder\META-INF\com\google\android and open updater-script using note pad (notepad ++ )
3.) delete the first two lines of the script and recompress
4.) Flash and enjoy
if you didn't get what im saying search for this video in youtube named " How to Solve Status 7 Error when installing custom rom ( LG G3 CyanogenMod 14.1 ) " by Techious.
P.S: im not allowed to share links, new to xda.
:good:

solution.
Bro,I had the same problem where twrp said "failed to read current baseband version:2".
So,I flashed my stock rom (you can find the procedure in xda) and flashed twrp 2.8.7.0 and then flashed the lineage os and it worked properly.

I Have Yunique plus n i hv successfully installed Lineage rom.. Jst changed the update script with other unofficial lineage roms script.. Work fine:good: I roll back bcz i need volte waiting fr it

Is any one knows the exact reason that why lineage os is unable to flash in yunique.

kumarakash938 said:
Bro,I had the same problem where twrp said "failed to read current baseband version:2".
So,I flashed my stock rom (you can find the procedure in xda) and flashed twrp 2.8.7.0 and then flashed the lineage os and it worked properly.
Click to expand...
Click to collapse
How did you flashed stock ROM?est tool or flashable zip?

baseband problem wih lineage os
prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
Stock rom have two versions , lineage os rom work on baseband version of the 1st version of stok rom.
so try flashing 1st version of stock rom and then official lineage os.
And official lineage os in non volte rom.

what error you're getting while flashing

prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
I think it's because the firmware is different.
I'm not sure about this, but I think you need to migrate from cm firmware.
---------- Post added at 02:32 PM ---------- Previous post was at 02:32 PM ----------
shikhar adhikari said:
what error you're getting while flashing
Click to expand...
Click to collapse
Error 7

shikhar adhikari said:
what error you're getting while flashing
Click to expand...
Click to collapse
prabhakar53 said:
Is any one knows the exact reason that why lineage os is unable to flash in yunique.
Click to expand...
Click to collapse
iamanurag said:
I Have Yunique plus n i hv successfully installed Lineage rom.. Jst changed the update script with other unofficial lineage roms script.. Work fine:good: I roll back bcz i need volte waiting fr it
Click to expand...
Click to collapse
---#Saransh#--- said:
follow these steps to remove the zip verification codes.
1.) unzip the rom in Pc
2.) go to extracted rom folder\META-INF\com\google\android and open updater-script using note pad (notepad ++ )
3.) delete the first two lines of the script and recompress
4.) Flash and enjoy
if you didn't get what im saying search for this video in youtube named " How to Solve Status 7 Error when installing custom rom ( LG G3 CyanogenMod 14.1 ) " by Techious.
P.S: im not allowed to share links, new to xda.
:good:
Click to expand...
Click to collapse
ashwin.varma4441 said:
I think it's because the firmware is different.
I'm not sure about this, but I think you need to migrate from cm firmware.
---------- Post added at 02:32 PM ---------- Previous post was at 02:32 PM ----------
Error 7
Click to expand...
Click to collapse
So guys here's a solution for successfully installing lineage os on yu yunique ... I'm currently on lineage and that's super awesome and highly fluid... Just flash cm 14.1 zip link : https://drive.google.com/file/d/0ByL...xpQXd5T1U/view
using twrp link : https://drive.google.com/file/d/0ByL...lsMTlCMjA/view
; and this installation will update yunique's splash and boot image both with stock's one ... so now you need to go for installation of latest cos modem , actually due to lack of that we are gettiing the baseband 7 error ... link for cos modem : https://www.androidfilehost.com/?fid=817550096634760193
command : fastboot flash modem NON-HLOS.bin go to fastboot mode by enabling debugging mode on your device and unlocking oem ... and go to terminal / cmd and type >>
adb devices
adb reboot bootloader or adb reboot-bootloader fastboot devices
fastboot oem unlock-go
fastboot flash modem NON-HLOS.bin
fastboot reboot
Now latest cos modem .. you have ... go to recovery (twrp) and grab latest los (lineage) release and flash (clean flash strongly recommended ... do it surely) and no error ... yes no erros ... you'll be booted to most -awaited los within 3mins ... have fun... and the problem was occurring due to lack of stock splash.img , boot.img and latest cos modem(mismatching of baseband ) ... thank you ...
---------- Post added at 06:30 PM ---------- Previous post was at 06:28 PM ----------
Anjan Roy said:
So guys here's a solution for successfully installing lineage os on yu yunique ... I'm currently on lineage and that's super awesome and highly fluid... Just flash cm 14.1 zip link : https://drive.google.com/file/d/0ByL...xpQXd5T1U/view
using twrp link : https://drive.google.com/file/d/0ByL...lsMTlCMjA/view
; and this installation will update yunique's splash and boot image both with stock's one ... so now you need to go for installation of latest cos modem , actually due to lack of that we are gettiing the baseband 7 error ... link for cos modem : https://www.androidfilehost.com/?fid=817550096634760193
command : fastboot flash modem NON-HLOS.bin go to fastboot mode by enabling debugging mode on your device and unlocking oem ... and go to terminal / cmd and type >>
adb devices
adb reboot bootloader or adb reboot-bootloader fastboot devices
fastboot oem unlock-go
fastboot flash modem NON-HLOS.bin
fastboot reboot
Now latest cos modem .. you have ... go to recovery (twrp) and grab latest los (lineage) release and flash (clean flash strongly recommended ... do it surely) and no error ... yes no erros ... you'll be booted to most -awaited los within 3mins ... have fun... and the problem was occurring due to lack of stock splash.img , boot.img and latest cos modem(mismatching of baseband ) ... thank you ...
Click to expand...
Click to collapse
First two links will not work now , I got them a long ago , I can't help u with that

Dush4711 said:
How did you flashed stock ROM?est tool or flashable zip?
Click to expand...
Click to collapse
First try to revert back to TWRP 2.8.7.0 and then install lineageOS firmware + LineageOS ROM.

Nokia 6 Oreo beta zip file DDL

http://download1053.mediafire.com/z...d/Nokia6_Android_8.0_Oreo_Beta_v5.140_OTA.zip
Install it at your own risk.
I'm not responsible if anything goes wrong.
Copy it onto SD card, reboot into recovery mode, then do "Apply update from SD card"

Thanks mate.

whoprasad said:
Thanks mate.
Click to expand...
Click to collapse

Akilesh T said:
Click to expand...
Click to collapse
Can u give such for Nokia 5 too..?

Is it compatible for TA-1033.

Its for TA-1021 ?

Does anyone tried this buid for TA-1021 yet

I wonder if this would work on TA-1000 and TA-1003 which doesn't get Oreo otherwise.

didnt worked on TA-1025, not tested on TA-1021 yet

I will try on my TA-1021 DS EU Variant.

Marius.Petran said:
I will try on my TA-1021 DS EU Variant.
Click to expand...
Click to collapse
tell us when u finish installing.....good luck

Error,then no command....the user who uploaded its from India,i guess he upload OTA for india.....don't know what to do now.

Marius.Petran said:
Error,then no command....the user who uploaded its from India,i guess he upload OTA for india.....don't know what to do now.
Click to expand...
Click to collapse
Reflash it with Mena
Enviado desde mi Moto G⁴ #StayUnbeaten

how to exit no command ? for MENA you need to put your phone in download mode and i cant acces recovery.

This update.zip is for phones having 00WW_3_700_SP02 December update. If your phone does not show 00WW_3_700_SP02 build number in About don't install this update otherwise you'll get a brick.

Marius.Petran said:
how to exit no command ? for MENA you need to put your phone in download mode and i cant acces recovery.
Click to expand...
Click to collapse
Volume - & power button
Enviado desde mi Moto G⁴ #StayUnbeaten

Not a big deal with MENA,im using TA-1025 firmware now...screen brightness are low,no OTA for Security Update,stuck on June 1 2017.

qwertysmerty said:
This update.zip is for phones having 00WW_3_700_SP02 December update. If your phone does not show 00WW_3_700_SP02 build number in About don't install this update otherwise you'll get a brick.
Click to expand...
Click to collapse
Mine showing 00A0_3_700_SP02, and bricked once, idont know when we will get the update

Marius.Petran said:
Not a big deal with MENA,im using TA-1025 firmware now...screen brightness are low,no OTA for Security Update,stuck on June 1 2017.
Click to expand...
Click to collapse
Ignore this,just because i reflashed my TA-1021 with MENA (OST),and i manually update it from 7.1.1 to December update (updates was installed in order),i checked for updates after i was done with December Update,and see what i got xD .

Akilesh T said:
http://download1053.mediafire.com/z...d/Nokia6_Android_8.0_Oreo_Beta_v5.140_OTA.zip
Install it at your own risk.
I'm not responsible if anything goes wrong.
Copy it onto SD card, reboot into recovery mode, then do "Apply update from SD card"
Click to expand...
Click to collapse
Hey, can you share the system.img or system dump of the oreo beta ROM?
Thanks

October 2018 Security Patch

Just checked updates and new October security patch was found.
Captured OTA file:
https://workupload.com/file/jQDkURkS
MD5: 69a58a09918a4735f47de53e478854aa
SHA1: d8a6e5d87a4bb2f5d26bd1b28be829d6b2f3be37
Edit: Couldn't extract the payload.bin inside the archive. :-/

thanks for the info. do you know where i can see the changelogs?

Changelogs are usually never published. This patch looks like a plain security update due to its size of only 82mb.

Doublepost, sorry!

Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB

Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.

thorin0815 said:
Are you sure this is for the A2 LITE? My version says V9.6.9.0.ODLMIFF.
Click to expand...
Click to collapse
Ok, i think maybe is the version of the standard A2 (no lite).

There is indeed a security patch for the month of October. Havent updated yet. Its size is 82MB.

Yes just got updated. Magisk and xposed still intact and working perfectly.

Maximuous said:
Yes just got updated. Magisk and xposed still intact and working perfectly.
Click to expand...
Click to collapse
did you just update without flashing the original boot.img from magisk?

Jordan~Kurniawan said:
did you just update without flashing the original boot.img from magisk?
Click to expand...
Click to collapse
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.

Is there chance to install it from adb?

It's just a security patch, yes. No bugfixes. Some bugs including the shutter lag is still there.

Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
i thought when you say intact you updated without first flashing the stock boot.img

Maximuous said:
Nope. I followed the steps on this guide [GUIDE] Install Magisk with proper support for OTA updates.
Click to expand...
Click to collapse
How could you follow the guide? For me it doesn't work. Magisk says "Stock backup does not exist"
Did you place a file manuelly? If yes where exactly?
The only way let magisk creating is a backup by flashing it with twrp, but i want to wait for official twrp first
update - i resolved my problem:
1. i flashed with fastboot the stock boot image of current running version 9.6.6 to the inactive slot, in my case "slot b" by cmd line:
fastboot flash boot_b boot.img
2. i did run magisk - install to inactive slot -> magisk did backup stock image of inactive slot
3. after reboot i was able to use "uninstall - restore stock image" to do the ota update (like described in the guide)

Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Sent from my Mi A2 Lite using XDA-Developers Legacy app

Ithao said:
Is it possible to do so?
I have magisk in the Oreo version of September. And I want to upgrade to October. And I thought about doing this:
Install official twrp.
Install original boot img. Current
Install OTA via Twrp.
Install boot patched img. Current
Install magisk via twrp.
And then reboot the phone.
Is it right?
Click to expand...
Click to collapse
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.

BubuXP said:
No, because TWRP in A/B devices (like A2 Lite) is located in the boot image too. So doing the second step of your procedure will cancel the TWRP installed in the first step.
Click to expand...
Click to collapse
Ok. Thank you. I understood now how it works.
I did it that way. I had no problems.
https://forum.xda-developers.com/showthread.php?p=77931735
Sent from my Mi A2 Lite using XDA-Developers Legacy app

Txatxiquesi said:
Version: V9.6.14.0.ODIMIFE
Size: 105.8 MB
Click to expand...
Click to collapse
Does second sim slot work?

HTCDevil said:
Does second sim slot work?
Click to expand...
Click to collapse
I personally only use first slot.

Android 10 for nokia 6.1 2018 is out on TA-1043

Update is out .got it on my android beta 10

Is that a beta version?

Nope
malerocks said:
Is that a beta version?
Click to expand...
Click to collapse
Nope i had before not now.now stable version

Android 10 after updating
Have a look after updating

Hello I'm on 6?1 ta-1050 and this is the official android 10 update : https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
My question is, can I install this via recovery if it's on my internal storage? I don't have an SD card or access to a pc right now. I've read conflicting reports online. Please advise, I don't want to brick my phone.
Thanks

Got mine over OTA.

It's official
zuhaibsarwar said:
Nope i had before not now.now stable version
Click to expand...
Click to collapse
https://twitter.com/NokiaMobile/status/1214856358060625922?s=09

Lol see my post again
darweshhamela said:
https://twitter.com/NokiaMobile/status/1214856358060625922?s=09
Click to expand...
Click to collapse
I told i have beta before now yesterday i got global stable version official update

I had beta Android 10 before nor Android 9 pie
darweshhamela said:
https://twitter.com/NokiaMobile/status/1214856358060625922?s=09
Click to expand...
Click to collapse
So i got Android 10 stable official on Android 10 beta :highfive:

junglebungle said:
Hello I'm on 6?1 ta-1050 and this is the official android 10 update : https://android.googleapis.com/pack.../c6260831df0acdfe9828f18bcea7ffb556f4b2e5.zip
....
Click to expand...
Click to collapse
Is the OTA the same for all variants, or is this ta-1050 specific and eg ta-1043 has a different file?

mikem85 said:
Is the OTA the same for all variants, or is this ta-1050 specific and eg ta-1043 has a different file?
Click to expand...
Click to collapse
I didn't received official OTA via "check for updates" option yet so:
I just manually downloaded and installed this OTA file on my TA-1043 and it works fine! I performed the update via recovery using ADB sideload. Restarted the phone and having android 10. It is so simple!

Machi007 said:
I didn't received official OTA via "check for updates" option yet so:
I just manually downloaded and installed this OTA file on my TA-1043 and it works fine! I performed the update via recovery using ADB sideload. Restarted the phone and having android 10. It is so simple!
Click to expand...
Click to collapse
How to install without twrp recovery ? I don't have root

Indashio said:
How to install without twrp recovery ? I don't have root
Click to expand...
Click to collapse
It is no problem with stock recovery. How to enter stock recovery, just do these steps:
https://www.youtube.com/watch?v=8Fv39sTUvbk
Then you can "Apply update from ADB" or "Apply update from SD card". I did it via ADB sideload.

Machi007 said:
I didn't received official OTA via "check for updates" option yet so:
I just manually downloaded and installed this OTA file on my TA-1043 and it works fine! I performed the update via recovery using ADB sideload. Restarted the phone and having android 10. It is so simple!
Click to expand...
Click to collapse
Works. Tested on my Dutch TA-1043.

Zandoz said:
Works. Tested on my Dutch TA-1043.
Click to expand...
Click to collapse
Works on my US/Canada TA-1045 as well.

Hello,
mikem85 said:
Is the OTA the same for all variants, or is this ta-1050 specific and eg ta-1043 has a different file?
Click to expand...
Click to collapse
This is also for Nokia Ta-1054?

andreihincu said:
This is also for Nokia Ta-1054?
Click to expand...
Click to collapse
If that's a Chinese model, no it won't.
From the Android Sage page with update instructions:
Following is the latest OTA update zip or full stock firmware upgrade package. The following OTA update is only for the international variant. Chinese variants will be updated soon. Chinese variants will be updated soon. So stay tuned.
Click to expand...
Click to collapse

Hello
On french modèle no update for moment

Same here, but I have noticed that when major updates roll out in France we have a 15 day delays usually

adjaxio said:
Hello
On french modèle no update for moment
Click to expand...
Click to collapse
Hello,
I just have a update now on a French model.