Hey, My phone doesn't support OTA update, so I need flash in order to get security update. Where can I get individual update package (a zip that only contain the update's files, not include the complete rom) for lineageOS?
Anyway, my phone is Redmi 4A, I can't find my device on the lineage os download page
horasmichael said:
Hey, My phone doesn't support OTA update, so I need flash in order to get security update. Where can I get individual update package (a zip that only contain the update's files, not include the complete rom) for lineageOS?
Anyway, my phone is Redmi 4A, I can't find my device on the lineage os download page
Click to expand...
Click to collapse
First of all you need to know lineageOS versionen. Ideall with who made it.
Related
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 everyone, these may be of help to you. I'm not a dev so all I was doing here was using a rooted Sirocco to pull OTA files off the phone (data/ota_package). Using logcat/android bug report doesn't catch OTA URL on this device. It's my understanding they will need to be unpacked.
Files are in order of download/installation from A1N-310B-0-00WW-B03-OST604 onwards. That full firmware can be obtained here thanks to Hikari (Under Sirocco) https://hikaricalyx.com/fih-android-firmware/
The boot image for the firmware above can be found in the zip. It's already unpacked (A1N-0-310B-00WW-boot.img).
OTA 1 (Changelog - https://i.imgur.com/EeQeHyR.png)
https://mega.nz/#!SA1U3SzR!WAUtzV5AH2g6jYUYqhrUfMNh_tOe7ziNhNwZ8eZBxew
Boot image - https://mega.nz/#!2J8wBaBR!PbYVY4Ysr4l9idxReLrJe6wWu83KRy5tO29j0H2b3Ew
OTA 2 (Changelog - https://i.imgur.com/AOvs4Ps.png)
https://mega.nz/#!mB0EgCRa!oEKAxCl5iGnR3rHC91te0mgU3JgW3AXAO991kR4nj9g
Boot image - https://mega.nz/#!iU1WlKxT!mz1VrSGS987BbiPj1nvyUQzb4GEBw3686onS6ymctJI
OTA 3 (Changelog - https://i.imgur.com/nEpvMq2.png)
https://mega.nz/#!rNNAhASA!5_CdYQIym6iqc5ycN6wMqG0XvzrsCf70I3VQsy8bjFg
Boot image - https://mega.nz/#!SJt0WSxK!UkG4DbsDmUwIzExcmG1qo2xqhRk4lJlylhWHfMFJxfM
OTA 4 (Changelog - https://i.imgur.com/QH6Dnox.png)
https://mega.nz/#!HF8WlKDS!OpfBdAEUJSe_vzTebdCGg_DN_8Kzj5UZVG29x8aG6Q8
Boot image - https://mega.nz/#!7Usw1aKS!jEoZDlj5mtu5tqVpVG7XFaHLdDleiq3M6GBfy7_IUzc
OTA 5 (Changelog - https://i.imgur.com/bDSCAqX.png)
https://mega.nz/#!XUlWFKiC!_trT2aVmGQVhD-lzeZjWEn2LlmRZ4d6CMrKuAB41kkw
Boot image - https://mega.nz/#!KVl2WKqT!AcDI4YSOSo6vBe4Jb3FrOBsKGzO-KM5a8gowgNQXHog
OTA 6 (Changelog - https://i.imgur.com/ColEcRJ.png)
https://mega.nz/#!DE8QxSDQ!G1xRrjN9do28trYeQT-E9jAYmP7dszuXMKZ8kpmhcMI
Boot image - https://mega.nz/#!XB9EnY4A!UxLAX0hBabbKy09pGQz_BLQW9Hy5Lz0K4y15uVJcY7o
OTA 7 (Changelog - https://i.imgur.com/Tll0QuI.png)
https://mega.nz/#!zUsAzKLZ!TngURPA1pDUFjrmsrWvVglLmkE3GGGE4qX53-Vp38iU
Boot image - https://mega.nz/#!jck0iAjI!nEd890ZxQS1OaXX4ELNtdsIsa3TJZxddC1D7faPOB9U
OTA 8 (Changelog - https://i.imgur.com/HsZLwV4.png)
https://mega.nz/#!3dtEXQwY!CY6J3auoDeMelGSDmQiAJgOBHw3eH-sxrA3x51gXQ-U
Boot image - https://mega.nz/#!SQsUUYSD!iBwTMYd4OEDJJ7Me-zb2SnfPghc2me_ZEYR6SrdOkgU
OTA 9 (Changelog - https://i.imgur.com/eLVqDrM.png)
https://mega.nz/#!CEc1GQ7L!EiZYCubGDf5C97NNQDLZxmjcEaw555FbxHKvMNveZDw
Boot image - https://mega.nz/#!mNFzVCbD!RNTJI1_oPiHSapyykE0szjosBo_QnIoJiGZ0EQtmzqY
OTA 10 - Pie (Changelog - https://us.v-cdn.net/6031042/uploads/editor/je/y2ok3dg0norb.png)
https://mega.nz/#!fYUAgQJY!p6kO-B-IFwz0NhDv4ZlrDCQYKQGakH3fy9GbfG_kmDM
Boot image - https://mega.nz/#!qANy1a7b!ODh8ol97h8qJwZGndUCHqyG3qifnsfT7ILkggDaVoFA
Magisk patched boot - https://mega.nz/#!HYVimArR!m7BHM2iYVZVstTFx0W-zB01cSN-bb4lquKiYUmXoIm4
edit: TWRP removed, buggy
OTA 3 zip was corrupt, it has been replaced.
Also for helping out anyone who gets their Sirocco unlocked, this is a pre-rooted boot image for A1N-310B-0-00WW-B03-OST604
You can use this to do fastboot boot patched_boot.img and then use Magisk to root your device.
https://mega.nz/#!6dMgjCjL!KRkB39ppPp4RA0Wj57yjIjiXaE6B21f-B488yQFc61s
You can, of course, do the above yourself if you have a second phone that is rooted and go into Magisk and patch one of the stock file boot images above.
Now you can do OTAs and keep root
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
Congratulations you can now reboot and will have an updated Android while keeping full root.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nokia-8/how-to/guide-how-to-root-nokia-8-ability-to-t3848390
If anyone is already on the November security update with this device and wants to root without downgrading, here is a magisk patched boot image
https://mega.nz/#!HBcHzYCB!KpqytpNth0Vfu3K9eX0vbP7heJ3MFPm6MX4ozC5L_qk
December security update added as OTA 9.
No Pie yet
Audioboxer said:
December security update added as OTA 9.
No Pie yet
Click to expand...
Click to collapse
Its a shame.
December patched boot for anyone who's had this phone unlocked and has done OTAs up to December without rooting
https://mega.nz/#!6R8RCIoB!ZPR7s-w4LWDXO1UcI7GBuhf7U0U3fujHLQIc6qlqx2g
As always, fastboot boot this image to root your phone with Magisk direct install. Do not flash my boot images, otherwise, you won't be able to do the OTA trick above with Magisk.
Removed: Oreo homebrew packages by Hikari are buggy, avoid.
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
marccoppers said:
So i found this...
https://mega.nz/#F!W50gzawY!nC8Yb9yE6n08gGafFi700A
The A1N-4120 is a Pie build. A guy i met on twitter installed it and said it is a decent build without bugs. I'm a bit hesitant to install it. I'm afraid that if i install it and the offical update comes out i can't update via OTA. Is there a way to revert back to 8.1?
The guy's phone isn't rooted or unlocked.
Still, he says it's the official build from HMD. They are holding it back... If that's true it's kinda sad...
Click to expand...
Click to collapse
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Audioboxer said:
It's the internal OTA and he wasn't sensible installing it without BL unlock
https://forum.xda-developers.com/no...ide-how-to-install-android-pie-build-t3885834
These internal builds don't pass safetynet so Google Pay will not work. It is also unknown how to get back onto retail OTAs without an unlocked bootloader. When HMD did the Nokia 8 beta test they had an official rollback method.
I'd strongly advise staying away from this if you haven't unlocked the BL. The build wasn't all that good either, missing adaptive battery, pro camera, Pie themeing and more. From above two new OTAs exist since the December pie build. I'll try them and see if anything has been added.
Click to expand...
Click to collapse
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
marccoppers said:
Thanx for the reply! Gonna stay away from it then... Usually i try everything, but since the BL is still officially locked there aren't that many people out there that can help when things go wrong. Especially with this being my daily phone, i don't want to mess it up.
Click to expand...
Click to collapse
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Audioboxer said:
Yeah, it's not worth it, Pie should drop this month.
With the Nokia 8, HMD advised if you stayed on the beta you'd get 1 OTA and that would be it. You basically had to rollback.
In order for us to flash firmware packages, we need an unlocked bootloader if HMD isn't providing an official rollback method. As it seems we won't get an official beta test for the Sirocco it's a bad idea anyone with a locked bootloader flashing these internal releases.
Click to expand...
Click to collapse
That was my guess to. Thanx for the info.
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
rajeev.rao87blr said:
You are wrong. And I am the guy he met on twitter. And btw he is referring to Nokia 8 Sirocco and sorry but could you explain how you termed as insensible. I downloaded the internal OTA and then rebooted the phone in safe mode and the update automatically installed. For your information
1. Adaptive battery is there
2. Wellbeing is there
3. Pro camera is there.
So stop being judgemental. Nokia 8 and Nokia 8 Sirocco and two different handsets. Nokia 8 is what you mentioned above . So next time mind Ur tongue while u talk
Click to expand...
Click to collapse
My advice was just following what Nokia devs like Calyx Hikari state. If you do not have an unlocked bootloader its best not to install internal OTAs because there is no way to revert to retail FW. The Nokia 8 had an official beta test so there was a way to rollback off of the beta Pie firmware to Oreo again, to then install the final Pie OTA.
Otherwise you need an unlocked bootloader to flash an Oreo/Pie retail package with LA OST.
I don't mean to offend anyone, I just don't want anyone installing these leaked OTAs on their bootloader locked device and being stuck.
Currently, there's no way to roll back to Android 8.1 for Nokia 8 Sirocco by yourself, so use these packages at your own risk.
It will be better if you're using prototype device or a retail device with unlocked bootloader.
Click to expand...
Click to collapse
https://forum.xda-developers.com/no...stall-android-pie-build-t3885834/post78591840
Nokia 8 Sirocco doesn't need any bootloader to be unlocked.
Nokia 8 Sirocco doesn't need bootloader to be unlocked. Like I got it and others who installed got it without doing the same. You just have to downloaded the A1N 4200 file and reboot the phone to safe mode and the phone automatically detects the update. So I assume that's pretty much official and valid .
Don't know why people end up spreading rumours without knowing the real picture. Just because one device works in a specfic way doesn't mean every device functions the same way.
Plus Nokia 8 Sirrocco gets all the features a full fledged android one device gets including the below
1. Adaptive Battery
2. Gestures
3. Digital Wellbeing
I myself wanted to write a review and a video but never written one for mobile devices, I have done for vehicles.
And most importantly Nokia 8 and Nokia 8 Sirocco are different mobiles . The only common point is The processor.
Pie OTA Rom
Now that the official PIE OTA has been released can anyone capture it and post a link to the file? It can take weeks to reach people over the air sometimes!
Thanks
Let's say they will be captured, can i install them with a locked bootloader?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
I did on the Nokia 8 and the Nokia 7 plus by downloading to the device, renaming the file and using the phone keypad ( *#*#874#*#*) so I assume it will be the same on the Sirocco?
marccoppers said:
Let's say they will be captured, can i install them with a locked bootloader?
Click to expand...
Click to collapse
Sideloading the OTA via ADB can be done on a locked bootloader. The method by EGGMEN should work as well. :good:
Can someone send me.a direct link to all Firmwares for the pixel 6 pro that I can flash stock Firmwares that is. I need the official Firmwares for all countries
Is this what you are looking for
https://developers.google.com/android/ota
Or the full firmwares https://developers.google.com/android/images, and the December ones that they removed from there Alternate links to December full factory images for .017, .016.A1 & A4, and OTAs for .017 & .016.A1 available.
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Vincent_40 said:
I'm december FW without bug. If i want to clean flash the next FW what i must to do.
Can i wipe system in recovery or i must use adb/fastboot command ?
Click to expand...
Click to collapse
You'll be able to use Official Google Android Flash Tool or the full factory image zip which as always would be available at Pixel 6 Pro Factory Images. Either will fully wipe your device. I don't have firsthand experience with Official Google Android Flash Tool so I don't know if it wipes by default but I know it can or has an option to if it's not default. The full factory images at Pixel 6 Pro Factory Images, without modification, always fully wipes the phone. Make sure and update SDK Platform Tools every month (sometimes earlier version Platform Tools doesn't work correctly and update the Google USB Driver if you're using Windows.
Ok thx i'll try to clean flash with next update with flash tool.
Hope Twrp will be released soon.
Vincent_40 said:
Hope Twrp will be released soon.
Click to expand...
Click to collapse
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
roirraW edor ehT said:
I wouldn't hold my breath or take any bets on that. So far without TWRP hasn't held anything back.
Click to expand...
Click to collapse
Yeah, about a month or two ago bigbiff said he was working on TWRP for Android 12 in general, but it would be a while. Honestly, haven't used it since the Nexus days. Really haven't missed it at all and probably wouldn't use it even when/if it does come out.
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Vincent_40 said:
I'm on january security patch and I'd unlock the bL without disable the DM-Verity verification.
Can i root with last Magisk canary directly or do i need to disable DM-Verity ?
Last point, my play protect is uncertified, but it's not important
Click to expand...
Click to collapse
Yes, you can root with Canary Magisk 23016 without disabling verity & verification.
Ok i'll try
Thx for your reply
Hi, im on 12.5.11.0.RJSEUXM and I want to upgrade to miui 13, but after downloading the zip, and trying to install it with the updater app (choosing a zip from menu) its says "unable to verify, you cant install this stable rom"
Is there any way to fix that and install the rom? putting that zip as "update.zip" at the root of my internal storage and booting into recovery does nothing (in previos versions an option called "update.zip to system" was there)
Or I need to do something more to update?
Thanks.
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
_mysiak_ said:
Each recovery ROM seems to be verified at Xiaomi servers during upgrade process and if they block the installation for whatever reason, you're out of luck. The reason might be that the ROM is supposed to be used only by selected testers, in a specific region or maybe the ROM was pulled due to major bugs (I saw some complaints about SIM/network incompatibility in Europe). I can't install this update as well. It is possible to force the installation via fastboot, but I believe that Xiaomi has a good reason why they prevent us installing this version. I'm waiting until it arrives on its own as an OTA update..
Click to expand...
Click to collapse
Oh..ok yes its safer to wait. Thanks
Just to confirm - I never received 13.0.2.0 EU ROM, nor I was able to install it via sideload/ROM updater. I couldn't install 13.0.4.0 manually either, but today I got the update over OTA and installation went through without any issues.
Hi everyone,
for a customer project we have created a custom build of LineageOS 18.1 for SM-P610 and I have an image that is complete with our signage software.
I used to be able to flash these devices following the official installation instructions from the LineageOS page https://web.archive.org/web/20211002124915/https://wiki.lineageos.org/devices/gta4xlwifi/install
Now this doesn't work anymore. On some devices, I can't even unlock the bootloader. This has been discussed elsewhere and I have tried all the tricks from manipulating the datetime to logging on with a google or even a samsung account.
But even on the devices where I could onlock OEM, I can't seem to install the LineageOS recovery. I always get the error message "Only official released binaries are allowed to be flashed (RECOVERY)". FAP LOCK is OFF and OEM LOCK is OFF(U).
It says in the LineageOS install instructions that I must have the latest official Android 11 firmware installed. Previously, I would simply OTA update to this firmware, but nowadays, OTA goes directly to Android 12. So I tried downloading the only available Android 11 firmware from sammobile and flashing it in Heimdall. But unfortunately, I still get the same error message.
Can anybody please tell me which version of the Samsung bootloader I need exactly to install this version of the LineageOS recovery: lineage-18.1-20220112-recovery-gta4xlwifi.img?
Bonus question: Does anybody still have this firmware version mirrored somewhere?
edit: I have downloaded a newer recovery from the internet archives: lineage-18.1-20220504-recovery-gta4xlwifi.img
Now a get a different error message: "Custom binary(RECOVERY) blocked due to remaining installment balance".
Can somebody tell me what this means?
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Pelii said:
Do you really need LineageOS recovery specifically? Perhaps you may have better luck with the TWRP Recovery and then flash the OS through that instead. It was successful on my Galaxy S4 Mini.
Click to expand...
Click to collapse
Tbh I don't know. So how would that work? I Install the TWRP recovery (how?) and then I proceed to install the LineageOS image?
Well, looking at TWRP's website and the forums here, there's actually no build for your model specifically, so it seems you're out of luck on that one.
I suppose what's left is to just keep trying different sources of LineageOS recovery, because neither of the errors you described so far look like anything you can fix from your end.
Update: I have found what seems to be the exact Samsung firmware that was the latest one at the time:
https://samfrew.com/de/download/Galaxy__Tab__S6__Lite__-Wi-Fi-__/0kd5/DBT/P610XXU2DUL9/P610OXM2DUL9/
I'm currently downloading.
Also, I have been able to bring one of the really old devices to exactly this firmware state by OTA by cycling through 3 consecutive incremental updates. I was pretty excited to bring it into download mode, only to see this strange error "Custom binary(RECOVERY) blocked due to remaining installment balance" yet again.