Using
Code:
adb logcat
I was able to grab the url and download each OTA. I have uploaded to my Android File Host account here.
I own the Android One Moto X4 XT1900-1 purchased from Project Fi and these only work on stock via stock recovery adb sideload. This is the same as taking the official OTA from the notification.
Dec - Blur_Version.27.21.2.payton_fi.google_fi.en.US (initial upgrade to Oreo)
Jan - Blur_Version.27.221.3.payton_fi.google_fi.en.US
Feb - Blur_Version.27.231.6.payton_fi.google_fi.en.US
Mar - Blur_Version.27.251.10.payton_fi.google_fi.en.US
Apr - Blur_Version.28.11.15.payton_fi.google_fi.en.US (upgrade to Oreo 8.1)
How can I install these files on my Moto X4, do you know?
Awesome you rock bro
Thanx a lot bro
abrfilho said:
How can I install these files on my Moto X4, do you know?
Click to expand...
Click to collapse
Try to ADB sideload with stock recovery
Neffy27 said:
Try to ADB sideload with stock recovery
Click to expand...
Click to collapse
I tried, and no success. I done this :
"adb sideload nameoftheupdate.zip" and i've had this message : "E: failed to unmount /"
I tried to set "mount /System" and redid the previous command but with no success again... any help ?
My moto X4 is on Project Fi Oreo (previously on Stock Moto, XT1900-7) and the bootloader is unlocked of course.
That is unfortunate. I'm not sure what advice to give next. I uploaded them in hopes to that it may help towards more customizations. Seems Lenovo really doesn't want to be like Google.
I plan to stay stock till development gets further.
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
skmpowdjy said:
THANK YOU for uploading this!! I am on a completely stock, locked, Project Fi moto x4 and was stuck on the 7.1.1 November update. Flashing the Oreo update via adb sideload worked perfectly
Click to expand...
Click to collapse
Glad this worked for you. :good: plan to do the same whenever I get March notification.
On my 5th attempt to sideload the 8.0 update. Tried different downloads, file paths, and PC. Same results.
Step 1/2Error applying update: 20 (ErrorCode: : kDownloadState InitializationError)E: Error in / sideload/package.zip ( Status 1)
Any ideas?
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Glad you got it working ?
jfalls63 said:
Downloaded the full 8.0 firmware file and flashed in fastboot. While setting up the phone, got prompt for Jan security update. Installed it and check for Feb update. Also downloaded and installed. Guess I had some kind of glitch in 7.1.1 that prevented me from receiving OTA's or sideloading with ADB. Figures.
Click to expand...
Click to collapse
I just saw your post in the other thread and was about to direct you here. I was in the same boat. My only guess is that the Oreo update isn't being sent to devices on Verizon's network, but security patches are? There's someone else who posted on these forums a while back with the same issue on Verizon.
I had even tried removing the Sim, rebooting, and checking over WiFi before manual flash. Still don't know what caused ADB sideload to fail.
Official March OTA added!
Official April OTA added!
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Unlocked BL
Slickademo said:
I can't get adb sideload to work. Strange.... Anyone with an unlocked bootloader have success? TWRP won't do it either.
Click to expand...
Click to collapse
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Nick1801 said:
Also can't get sideload to work with unlocked bootloader. TWRP didn't work for me either. Can't tell why exactly it isn't working. My next thought was to try with a MicroSD Card.
Click to expand...
Click to collapse
I tried micro SD card with stock recovery and it did not mount. I just read that the newest update kills USB connectivity (besides charging) so it's probably best not to update until they fix that
So has the OTA files actually helped anybody? I thought I had at least one verified successful adb sideload done on a previous OTA.
Related
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
robert1010 said:
Hi,
I got my Moto G 2015 XT1541 running with Android 5.1.1 official rom and TWRP Osprey 3.0.0 R2. I just got the official message to upgrade to Marshmallow, but when I to upgrade TWRP comes with the following error: Updater process ended with ERROR: 7
I've placed a full log here: recovery.log
I also tried installing an other OTA file - (2GB Retail EU OTA): Download - thanks to @Osid - from here, but got the same error.
Also, the official update is version 24.41.33.en.EU, and the above file 23.41.47 and is already on my phone, according to "About Phone".
Anyway: Can someone please help me to get past this error and update to the official 24.41.33.en.EU? I've read about changing an updater-script file in the zip if you have one, but this is a block.map.
Thanks allot!
Click to expand...
Click to collapse
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Both update methods, as described above, fail. Method 1: using the phone's system updater, method 2: using the official(?) OTA upgrade files provided on this site.
But it looks like the OTA file is of a version I already have. See attachment.
Sorry, I misread your reply. I am looking for the stock recovery now keep you posted.
nobreak1970 said:
Flash the stock recovery and it will work. Official OTAs and custom Recovery's will not work together.
Click to expand...
Click to collapse
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
robert1010 said:
Ok, I took the recovery.img from "XT1541_OSPREY_RETEU_2GB_5.1.1_LPI23.72-33_cid7_subsidy-DEFAULT_CFC.xml", my version was 23.72-47. Hope that doesn't really matter. But is was the only 2GB European ROM I could find here.
So I used fastboot to flash that and tried the system update again. At the beginning it looked hopeful; It was showing the Installing System Update with the progress bar, but then briefly the error icon and rebooted without making any changes.
If I need to re-lock and/or un-root to fix this, can it be don without wiping everything?
Thanks again!
Click to expand...
Click to collapse
Anyone who can help me with this please?
My Pixel is rooted with Magisk so updating through OTA obviously fails.
What would be the best way to update? Would removing Magisk be enough? Or would would I have to flash the stock boot IMG before updating. Or is there another way to update without losing root?
Thanks.
It seems there is no this way.
I flashed the full image after removing -w, then root again.
Well, losing root isn't really a problem. Losing my data would be. So editing the flash all .bat is enough to flash the new system IMG on top of the existing one?
bush911 said:
It seems there is no this way.
I flashed the full image after removing -w, then root again.
Click to expand...
Click to collapse
+1
I did it this way too, can confirm it works. :victory:
Marc199 said:
Well, losing root isn't really a problem. Losing my data would be. So editing the flash all .bat is enough to flash the new system IMG on top of the existing one?
Click to expand...
Click to collapse
Yes I did it this way. Delete the - w in flashall.bat file then save it. Then double click flashall.bat. Then root as you normally would. I use the temporary TWRP.img file to flash latest TWRP, then reboot into recovery and flash your kernel (if you use one) and magisk 15.2. Works fine.
One thing though. If you use substratum disable it all before updating.
I am trying to adb sideload the OTA in TWRP recovery, but it keeps failing, and I can't solve it... or did 8.1 disable OTA sideloading in TWRP?
Dec Security Update
Magisk 15.2
ElementalX Dec kernel
TWRP 3.2.1
Anyone have any insight?
kazemitsui said:
I am trying to adb sideload the OTA in TWRP recovery, but it keeps failing, and I can't solve it... or did 8.1 disable OTA sideloading in TWRP?
Dec Security Update
Magisk 15.2
ElementalX Dec kernel
TWRP 3.2.1
Anyone have any insight?
Click to expand...
Click to collapse
Ota sideload never worked, doesn't work, will never work with twrp.
NoobInToto said:
Ota sideload never worked, doesn't work, will never work with twrp.
Click to expand...
Click to collapse
I have been ota sideloading with twrp since like August but thanks...
kazemitsui said:
I have been ota sideloading with twrp since like August but thanks...
Click to expand...
Click to collapse
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
NoobInToto said:
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
Click to expand...
Click to collapse
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
sliding_billy said:
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
Click to expand...
Click to collapse
I see. I assumed it would be similar to the nexus line. A/B partition only seems to make it complex. I've stopped rooting and flashing sometime after I got my Nexus 6p. Have moved on to pixel now.
NoobInToto said:
I still doubt it. Stock ROM adb sideload updates never worked. To be honest I tried it only in nexus 6p, I haven't with pixel. Flashfire should work smoothly, it supports stock ROM updates.
Click to expand...
Click to collapse
in my case it worked, the correct command to do sideload is simply to prefix ./ to adb (./adb devices, then ./adb reboot recovery, then ./adb sideload ota_file.)...
sliding_billy said:
OTA TWRP sideloads definitely worked for a few months a couple of versions ago (sorry I can't remember which TWRP version) but not since Google 8.0 and since TWRP was updated for that if I remember correctly.
Click to expand...
Click to collapse
Alright thanks that's what I was guessing. It worked for December ota just not January. Thanks!
Vitakocaiman said:
in my case it worked, the correct command to do sideload is simply to prefix ./ to adb (./adb devices, then ./adb reboot recovery, then ./adb sideload ota_file.)...
Click to expand...
Click to collapse
I believe those are the command for executing executables in linux... In windows the ./ is not necessary
Hey here I will share OTA for our NB1 to flash with stock recovery and sdcard method.
If I'm right it will work.
Pls try and report.
Download zip file,
Copy to external sdcard
Reboot to recovery,
Choose update from SD and press power button.
I will start with June security patch.
https://drive.google.com/file/d/1G0qg1b0ZbWjvWi3_WnimY3oy0xexRyXh/view?usp=drivesdk
Powered by View 10
Will work with sideload too, right?
hi
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Unluckily it errors when installing on an unlocked phone....I unrooted it fully, rebooted to recovery and it errors always. Should I relock the bootloader to install OTAs?
No, you do not need to block the boot loader. You need to flash the previous full update 4.88B. And then upgrade to OTA.
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Topogigi said:
I am already on 4.88B (rooted with magisk). No modification has been made on /system partition. I uninstalled magisk and rebooted: in theory that should be enough but in practice it does not work....
Click to expand...
Click to collapse
It won't if this is block-based OTA as Magisk modifies boot partition (with Android kernel and in A/B case recovery too). Quote from Android official documentation: "block OTA handles the entire partition as one file and computes a single binary patch".
Sure, but I uninstalled magisk thus restoring original boot partition before trying to apply OTA...
dark ghost1988 said:
2WildFirE will this update patch can use and support for Nokia 8 TA-1004 Dual sim, i'm from malaysia region...
Click to expand...
Click to collapse
Thanks for reporting [emoji1360]
Powered by View 10
support
does this firmware are support for Nokia 8 TA-1004 dual sim...??
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
Ok, I assume that noone had problems in updating to the june security patches with an unlocked bootloader, so there must be a problem with my device......
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
No news about July security patch?
Topogigi said:
End of the story: I reflashed the full 4.88B OTA update and immediately after the new june patch: it always gives an error. Tried to install the june patch by OTA, and it errors in the same way. I have the doubt that the new patch is allowed to check the bootloader and if it founds it unlocked, an error arises. Anyone confirming that?
Click to expand...
Click to collapse
confirmed ..
thats what happened to me
after i unlocked my bootloader ,rooted mgdisk
after July's OTA
i cant fastboot to june stock firmware
i even tried to sideload the june OTA and it said
that i cant downgrade from July to june
Topogigi said:
Ok I managed to update to june security patches with this file......Had to reflash both slots (A/B) with the full june camera update (4.88B), then I updated through recovery and it worked. Glad to tell that the system is fully tested and working.
Click to expand...
Click to collapse
Thanks Topogigi
How did you do it ?
im kinda stuck here
im considering OST LA ?
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
why666me said:
Any Ideas ??:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
have you tried switching slots? it sure wont solve the issue stated but it may restore the usability of your expensive brick :laugh:
Code:
If you are currently on slot A, type this: fastboot --set-active=_b
Or on slot B type this: fastboot --set-active=_a
No Switch with locked bootloader ?
Nothing work on fastboot with locked bootloader....
issue solved using OST LA 6.0.4
How to Flash Factory Firmware
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Youtube Video :- https://www.youtube.com/watch?v=eCGB-yxC09w
Text Guide
HOW TO INSTALL STOCK ROM IN MOTO X4:
Download Moto X4 Stock Firmware from below (in factory firmwares section).
Extract factory firmware to a folder.
Install Motorola Driver and ADB Fastboot Driver on your PC.
Copy all contents of ADB fastboot folder and paste it in factory firmware folder.
Download flash-all.sh(Mac & Linux) or flash-all.bat (Windows)
Place flash-all.sh/flash-all.bat file in factory firmware folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt/terminal window, navigate to factory firmware folder.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
Make sure device is detected in fastboot mode.
Windows
Code:
flash-all.bat
Mac & Linux
Code:
./flash-all.sh
Once everything is flashed.
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
Motorola Bootloader Unlock - https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Downloads
Motorola drivers for Windows & Mac :- https://support.motorola.com/us/en/drivers
Setup ADB and fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
flash-all.sh (Linux + Mac) - https://mega.nz/#!OYFiRKZC!2CjMLxpoEAqpFyB_q1Q1FncC9a1oNofh9Hjm99PwiGo
flash-all.bat (Windows) - https://mega.nz/#!DF1XwSjC!tkHhb9H9-1piNr1AbKaPJK_yLuv4rpIxw1AWicD1I94
Factory Firmwares
https://mirrors.lolinet.com/firmware/moto/payton/official/
US Retail Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Android One Android 9.0 Pie :- https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Twitter Account to Follow for latest firmware uploads
https://twitter.com/motofirmware123
you da man!
Your tutorials are very helpful .Thanks
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
jpolster2005 said:
When will you have the 28.2 firmware with the May update? Thats what version mine was on before I bricked it.
Click to expand...
Click to collapse
you should be able to flash the latest firmware listed above as long as you can boot into fastboot.
but my locked boot loader says preflash validation failed
jpolster2005 said:
but my locked boot loader says preflash validation failed
Click to expand...
Click to collapse
unlock the bootloader.
I can't, because OEM UNLOCKING is set to off
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
michael28056 said:
Thanks for the simplified guide. Worked great, I was able to relock the bootloader and accept an OTA with no problem. Only issue is the device doesn't pass safety net - signature validation error, and when I boot up I get the device has been modified pop up.
Click to expand...
Click to collapse
rooted?
No -unrooted, stock rom from this thread, locked bootloader.
michael28056 said:
No -unrooted, stock rom from this thread, locked bootloader.
Click to expand...
Click to collapse
well, i never stay on stock long enough to check that ..sorry cant help with that.
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
jpolster2005 said:
guys PLEASE help me I have a $300 paperweight here. Best Buy wouldn't take it back so I NEED to get it fixed. I was already on the newest OTA when I bricked my phone on a locked boot loader, and when I try to flash 28.1 thru Fastboot, it says validation failed. is there anyone out there who has access to the Fastboot flashable 28.2? I need my phone back!
Click to expand...
Click to collapse
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
same peeps thread
aw man... well, I meant to post specifically to the last post in the thread but was on the mobile app.
:good::good: Just wanted to say thank you for this post, the links to the image files and the flash-all BAT file. This really saved my butt with a Project Fi Moto X4, which I had rooted using Magisk before checking on the availability of factory firmware images from Motorola. (of course there are not any available from Motorola ) The phone was continuously prompting for an OTA update, which would fail. I first tried the Magisk uninstaller, which ran successfully in TWRP, but the OTA update was still failing. After some digging on Google I found your post and used the Project Fi image to flash the phone, it worked perfectly! There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully. I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
g3m1n1 said:
I love the Android community, the XDA community, and folks like yourself who take the time to write posts like this. Seriously, thank you!
Click to expand...
Click to collapse
glad to be of help :highfive:
g3m1n1 said:
There was an OTA update available after flashing (The May 2018 security patches, "28.2") and it installed successfully.
Click to expand...
Click to collapse
Hello!
I understand you have Android One version. If that's the case, anyone catching the URL to OTA for the Android One 28.2 update? I've been looking for it for days, and the OTA link generator is not working (at least with the data I'm providing which should be correct).
Neffy27 said:
What have you tried so far? There isn't a full 28.2 image yet that I know of.
Maybe this: https://forum.xda-developers.com/moto-x4/help/20-uploads-official-signed-28-2-t3810215
Click to expand...
Click to collapse
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
Thanks to our friend @hikari_calyx, who provided Internal OTA Update zip package to Android Pie for Nokia 8, we can test it before Nokia release it. The link contains two zips
1) December patch for Oreo for Nokia 8
2) Update to Pie for Nokia 8
Link:
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
Steps you have to do is:
1) Download NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip - this is December Security Patch
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
- Dial
Code:
*#*#874#*#*
and there will be possibility of update (this way you may use this guide https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#ota-installation to keep Magisk)
b)
- Connect your phone to PC
- Go to stock recovery (https://www.youtube.com/watch?v=RmewL1i50c0)
- Choose Apply Update from ADB,
- Type
Code:
adb sideload path_to_zip/NB1-488L-0-00WW-B01-488K-0-00WW-B01-update.zip
where path_to_zip is a path to the location of the file
- Wait and reboot phone, you should have December Security Patch
3) Repeat whole steps froim point 2) for the NB1-5110-0-00WW-B03-488L-0-00WW-B01-update.zip
4) Since @hikari_calyx provided us next internal update, repeat steps for NB1-5110-0-00WW-B05-5110-0-00WW-B03-update.zip and NB1-5110-0-00WW-B07-5110-0-00WW-B05-update.zip.
5) If you want to root your phone, here you may find stock and patched with twrp boot.imgs provided by @THMSP
https://mega.nz/#F!r3RUnaiC!p8FZqNpiPLK8XNwYusJv1Q
Like I wrote at the beginning, it is internal update, so I would strongly recommend to unlock bootloader in case something goes wrong. Additionally it is not known at the moment whether it can be possible to update to official version when it comes, so most likely downgrade will be necessary.
As always, you do all on your own risk and I won't be responsible for any damage you do to your phone.
PS: Here is the proof:
I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?
Gemmik said:
I'm rooted with magisk, can I update uninstalling magisk? or need reinstal firmware with OST?
Click to expand...
Click to collapse
Flash stock or restore stock by magisk, and than give it a try. If it won't work, than OST, downgrade and upgrade again till November, and than zip provided by @hikari_calyx. And than use images provided by @THMSP to root.
If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth
Just_Rise said:
If I move those otas to internal download folder and do as described above any chances to go wrong !?
Bootloader locked unrooted and unmodified attached all
Too good to be truth
Click to expand...
Click to collapse
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader
czupyt said:
There is a chance that you lose possibility for later OTA updates. I would not try to update without unlocking bootloader
Click to expand...
Click to collapse
You're right ,didn't thinked about that
Really divided about what to do now
Thanks anyway !
Confirmed working on TA-1012
Known issue on NB1-5110:
The lock screen can't be reconfigured - it will crash when you try to change.
I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?
rocalino said:
I just tried to install on a Mexico TA-1012 and not working, returns an error "package is for source build 00WW_4_88K but expected 00WW_4_84G, installation aborted"
Did you know what is the problem?
Click to expand...
Click to collapse
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
So updates from 488B to 488K need to be uploaded.
On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.
revanmj said:
On a side note - Pie requiring December security patches means HMD will miss "by end of November" deadline.
Click to expand...
Click to collapse
Seems so
Solved
Toedwarrior said:
Guys i accidentally flashed stock november boot to october system while doing that now my phone got stuck on Nokia screen and hardwarebuttons is not working. I tried adb command device gets listed but it says unauthorized. What should i do?
Click to expand...
Click to collapse
To be clear - You flashed November /boot partition to October /system partition? Switch slots from active to inactive. If you flashed November boot to October boot, flash again October boot. All in all you can use OST LA to downgrade and upgrade again.
czupyt said:
Preconditions:
1) All must be Stock, no root, magisk, xposed, no mods etc.
......
2) Update manually (2 ways)
a)
- Copy the file on internal memory root folder
Click to expand...
Click to collapse
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?
phm83 said:
How does this possible? Without rooting the phone you can`t access root folder, or i am wrong?
Click to expand...
Click to collapse
Internal memory root folder, not /
Thank you! Updating as we speak :fingers-crossed:
Sahilsinghlodhi said:
There are two files, please flash the smaller one first via any of the method mentioned, and then the larger.
Click to expand...
Click to collapse
Yes, I know and thats what I tryied to do but unsuccessfully
---------- Post added at 01:30 PM ---------- Previous post was at 01:24 PM ----------
czupyt said:
Seems the colleague is on SW older than 4.88B (which would be the update from May), therefore he cannot use ADB sideload directly.
Click to expand...
Click to collapse
hikari_calyx said:
So updates from 488B to 488K need to be uploaded.
Click to expand...
Click to collapse
After that error, I donwloaded the updates from June to november which someone else's uploaded to his gdrive but I got the same error when tried to update via sideload