Database Develop

Android System Update *root* 24.6 MB........

I was hoping someone could help me out with this......
I've been getting this irritating "Android System Update" (screenshot attached) week after week.
I'm rooted (unlocked bootloader), running stock 5.1.1
This update keeps showing up and when I go to install it, the phone reboots, then it goes it TWRP. I'm assuming this hasn't installed correctly because it keeps coming back.
Does anyone know how to get rid of this or install it correctly. It's becoming quite annoying when it pops up time after time.
Thank you-

Install the update manually or block OTAs.

nhizzat said:
Install the update manually or block OTAs.
Click to expand...
Click to collapse
How do I install manually?
That's what I'm trying to find out

http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.

jj14 said:
http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919
You can't take OTA if you are rooted.
Click to expand...
Click to collapse
Thank you.
So I just need to find the security patch and manually install it?
Now where to find it, LOL

I'd start by reading the stickies at the top of the thread list... Good readng.

this update would probably be LMY48I, for the stagefright patch.
what is your current build number?

IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
LMY47Z (screenshot attached)
I have Verizon.
I thought the builds were carrier specific.
This is what I found:
https://developers.google.com/android/nexus/images#mysid

MVLJR said:
This is what I found:
https://developers.google.com/android/nexus/images#mysid
Click to expand...
Click to collapse
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
MVLJR said:
So I just need to find the security patch and manually install it?
Click to expand...
Click to collapse
See the end of the first post on the link that I shared above

Didgeridoohan said:
I'd start by reading the stickies at the top of the thread list... Good readng.
Click to expand...
Click to collapse
IINexusII said:
this update would probably be LMY48I, for the stagefright patch.
what is your current build number?
Click to expand...
Click to collapse
jj14 said:
The link you posted is for Galaxy Nexus (not N6). It is the same page, but a different location. You need https://developers.google.com/android/nexus/images#shamu
@IINexusII is likely correct that the update you received is LMY48I. So you should be able to flash that
See the end of the first post on the link that I shared above
Click to expand...
Click to collapse
Thank you all very much for your help.
I'll try to patch one of these updates this weekend when I have some time off.
I'm the gatekeeper for all that is Android OS in my family. Myself, my Mom and now my Dad all have Nexus 6' and I've rooted us all. So I install it on my phone first and then the same with theirs.
I was so happy I found a fix for the MLB At Bat app and their stupid blackout rules.

This is just great, been having the same issue and versions
This covered everything I had at the moment!

I applied the update tonight, sick of those damn OTA prompts.
This is where I got mine from, but still not sure if I chose the right one:
http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052
Installed the download from:
LVY48F (5.1.1 Project Fi bugfix update 20150910)
It says Project Fi only, but I have no idea what that is. I didn't see an option for LVY48I, so I went with LVY48F.
Did I do this right?
Want to make sure I didn't screw up my phone.
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"

Anyone?

MVLJR said:
I tried installing the OEM ROM from here, but it failed while trying to flash it via TWRP recovery:
https://developers.google.com/android/nexus/images#shamu
"5.1.1 (LMY48I)"
Click to expand...
Click to collapse
Latest factory image is LMY48M
Here is guide how to flash factory image. http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008

Thank you!
I flashed the Pure Nexus ROM this past weekend and so far, so good. Loving some of the features not included in stock.

[Q] ota update always failing

i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root

Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.

Same thing here, always installation failed

Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables

Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares

Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?

sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps

Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???

@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw

[SOLVED] Pie october update failed

I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
UPDATE: Thanks to TomThePhysicist is problem solved, here is howto...

Same problem and I didn't find any solution yet.

Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
If it can't find the file, use the original name and re-dial.
I hope it works, please confirm so others can use it.
Broadcasted from Zeta Reticuli

It worked for me mate! Thank you

k3dar7 said:
I have TA-1046 with unlocked bootloader (and uninstalled Magisk before try Pie update)...
Pie stable i installed before using adb sideload OTA file (B2N-322C-0-00WW-B01-update.zip) from this thread
Before some days i have notification with OTA October update, but instalation after download failed(screenshot), tryed several times and on more different wifi connection...
Then i also try adb sideload file B2N-322D-0-00WW-B01-update.zip (from same thread as before install Pie stable) and too failed, this method show more info(screenshot):
"Package is for source build 00WW_3_22C but expected 0001_3_22C
Installation aborted"
In Settings/System/AboutPhone/AndroidVersion i have right build_number: 00WW_3_22C (screenshot)
I read in some other threads that someone have same problem, but without reaction, then a create rather this dedicated thread...
Anyone have same problem? And anyone have please sollution for this?
Please don't write if don't have this problem or tips for sollution, keep this thread clean for finding sollution, thanks
Click to expand...
Click to collapse
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.

Gravemind2015 said:
Try this : (works for a similar error in 6.1+):
Rename the package to B2N-322D-0-00WW-B01-322C-0-00WW-B01-update.zip
Put in root of internal storage, go to dialer and dial *#*#874#*#*
Click to expand...
Click to collapse
thanks, tried but not success...
update file is found and update process is starting, but after small wait in 17% is stoped and show error window...
tried with dialing and also keep on root of internal storage and reboot, this show notify about system update (not ota notify) with same behavior as dialer method...

jaskiratsingh said:
It happened with me but at that time my device was restoring applications after hard reset. Once the restoration was completed, it auto installed.
Click to expand...
Click to collapse
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...

proteus119 said:
It worked for me mate! Thank you
Click to expand...
Click to collapse
you have unlocked bootloader?

Worked for me too, thanks!

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Broadcasted from Zeta Reticuli

Gravemind2015 said:
Are you rooted? It's weird, it works for some people but not for others.
I'm trying to guess it it's variant specific or maybe having root is the issue (it's expected on a rooted system).
Click to expand...
Click to collapse
i have rooted (using install official Magisk zip release in only booted TWRP) before, when i see first OTA update notification, then i unroot using MagiskManager Uninstall Complete...
then all update i trying (OTA wireless, adb sideload, dial and reboot with file in root with your filename) is without Magisk/MagiskManager installed, "only" with unlocked bootloader

wriggler_ said:
Worked for me too, thanks!
Click to expand...
Click to collapse
you have unlocked bootloader?

k3dar7 said:
you have unlocked bootloader?
Click to expand...
Click to collapse
Nope.

Hard reset won't solve it. Do not bother
k3dar7 said:
thanks, i not yet try hard reset now, only before ~month while sideload Pie 3.22C, try wait ~week if find or someone sollution without HR...
Click to expand...
Click to collapse

I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.

whoknowshimself said:
I might have a clue on this. I upgraded to Pie from a rooted state (the OTA allowed me exceptionally to upgrade from Oreo to Pie and I said why not!). Now after installing Magisk Manager I noticed that Magisk is already installed! This might be the reason behind this annoying error.
Click to expand...
Click to collapse
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...

Of course it should fail. What I mean is it fails because we don't have stock boot. Like in Oreo when it was not possible to use OTA with patched boot, it is not available for Pie. They just made it available for Oreo to Pie update and that has messed everything up.
k3dar7 said:
ok, i go try OTA dial update after install Magisk
edit: same as without Magisk, failed at 17%...
Click to expand...
Click to collapse

I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.

Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
ganja_guru said:
I was on an unlocked bootloader with Magisk installed and encountered the same update failed error. I tried uninstalling Magisk via total uninstall and ended up soft bricking the phone, unable to apply any OTA update. The firmware flashing tool also did not work. The good news was I was still able to access Download Mode and Fastboot mode. I ended up sending it to the service center after relocking the bootloader and they flashed the official firmware at no charge. The phone then updated to Pie on first boot after downloading the update, and then wanted to update to the October update after a restart. The weird thing is the October update failed again, inspite of locked bootloader and no root! However, when I checked the phone few hours later, the update seems to have gone thru just fine. Not sure why this October update is a bit wonky. I agree with the above poster; not having patched boot is the issue here. However, we should be able to get this by extracting payload.bin and using magisk to patch the file.
For now, I am back on a locked bootloader and no root. Awaiting more stability in the unlocking/rooting scene before I try again. Unless Nokia releases official bootloader unlock, I will have to firmware flash back to Oreo, as both A/B partitions are occupied by Pie and the hack used to unlock the bootloader has already been patched on Pie.
Click to expand...
Click to collapse

whoknowshimself said:
Hi. Thanks for the input and your detailed comment. The thing is there is no service centre here in my country! So I should do everything my own. But may I ask how you relocked the bootloader?
Click to expand...
Click to collapse
Sure, I followed the instructions here https://www.techmesto.com/lock-nokia-android-bootloader/ . However, if there is no service center in your country and you don't plan to do a warranty claim, I've read that relocking the bootloader will prevent you from using the firmware flashing tool.

Please help, need boot.img with Android 10

I have tried multiple times to install TWRP and every time it seems to get overwritten by stock recovery. I've tried everything I can find online. After successfully flashing recovery.img and sending command "fastboot reboot recovery" or command "fastboot reboot 'recovery.img'" it flashes orange for a fraction of a second then vibrates a second time and shows boot logo screen with orange state warning, then either boots to stock recovery, or it boots to the home screen. One person said he was running into the same issue as I was and was only successful by deleting all the partitions on the device and reflashing it. He doesn't remember the steps he used and I would like to avoid even trying to do that anyway.
My only goal is to obtain root on my device, even if I'm using AOSP, as long as it's AOSP Android 10 v222, however I'm having issues trying to build a version of AOSP for this device without being able to find the binaries for it.
With all that being said, my question is if anyone who has the Blu Bold N1 running with the Android 10 update and working TWRP installed could please dump the rom and send it to me or upload it for me somewhere. There is no way I can dump the rom of my own device because I cannot get TWRP to successfully boot, and Blu does not host the Android 10 iso for this phone anywhere.
Alternatively, if someone could find the binaries for this device or knows how to find them, I could successfully build my image of AOSP and obtain root that way. I would rather be on the stock android that comes with the phone, but if I can't root it then I don't care to move to something else.
On an unrelated note, this is the first time I've ever posted on this forum and I apologize if anything I'm asking for or saying goes against the guidelines.

Hey, I pulled the Android 10 OTA. Can that b of help ?

greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
YESS! I've been using this phone without root for months now, you'd be a lifesaver if you could show me where I can download it.

greeneyez15o said:
Hey, I pulled the Android 10 OTA. Can that b of help ?
Click to expand...
Click to collapse
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.

emooverlord said:
Sorry, I am the original poster of this thread, "emooverlord" I guess I signed in with my Facebook when I posted this and signed in with my email this time on accident.
Click to expand...
Click to collapse
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.

greeneyez15o said:
Ugh...sorry I don't have it anymore. I was annoyed I couldn't get it rooted.
Click to expand...
Click to collapse
I can't seem to get TWRP on it at all, with the boot img or the rom would it not work with magisk?

The 3 files attached are:
boot.bin: The contents of the original 'boot' partition.
boot-stripped.bin: Patched with an empty vbmeta image, to allow custom ROM flashing and the like. Generated by:
Code:
cp boot.bin boot-stripped.bin
avbtool erase_footer --image boot-stripped.bin
avbtool append_vbmeta_image --image boot-stripped.bin --partition-size 33554432 --vbmeta_image /path/to/google-empty-vbmeta.img
boot-magisk.img: Pre-patched with Magisk 23 Canary (23016).
These are all from the November 2021 security patch of A10 on the Bold N1.

Also: you can extract everything off of the live device with https://github.com/bkerler/mtkclient:
Code:
python ./mtk rl <path to backup>
will give you a dump of all of the partitions on the device. (Since 'userdata' is encrypted and the last one, when it gets there, just hit ctrl-C when it gets there and you'll have everything out of the backup.)

irony_delerium said:
These are all from the November 2021 security patch of A10 on the Bold N1.
Click to expand...
Click to collapse
Any idea where I can get the Nov security patch? I'm stuck on Feb update.

GMSS75 said:
Any idea where I can get the Nov security patch? I'm stuck on Feb update.
Click to expand...
Click to collapse
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.

irony_delerium said:
Not off the top of my head. Mine updated to the November SP pretty quickly after turning it on the first time.
Click to expand...
Click to collapse
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the boot image?

GMSS75 said:
Ok thanks, I can't disable dm-verity, how do you patch vbmeta in the bootee image?
Click to expand...
Click to collapse
I used avbtool on the stock image. Check how I created boot-stripped.bin.

Question OTA Update Fails With "Installation Problem"

NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.

Maybe Oxygen Updater has full download link?

BeachNYC said:
NE2215, Rooted running .c22.
I have followed all the rules, unrooting with Magisk restoring images, then either using the system updater to download the OTA, or the local update apk to install an OTA. In every instance, whether it is c26 or c30, it fails with the unhelpful message "Installation Problem"
I suspect that this was caused by my having at one point installed the unofficial TWRP recovery, which I later uninstalled and replaced with the stock recovery. I had thought returning to the stock recovery would solve the problem, but it continues to exist.
Can someone suggest the steps I should take to get the phone to take the update? This was not a problem when OnePlus was providing full installs, but I'm having no luck at all with the recent updates.
Many thanks for your help.
Click to expand...
Click to collapse
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.

kouzelnik3 said:
I would try to flash stock boot.img without any root etc., reflash stock recovery if possible and then download FULL ota link using oxygen updater and then via localupdate.apk try to install it.
Also you can try to use this software:
OPPO System Upgrade Tool | OPPO Global
Only 5 steps to upgrade to new system. Always optimize your OPPO device when there's the latest software update available to enhance the system stability.
www.oppo.com
It should be possible to upgrade your OP10P with it even with OxygenOS without issues.
Hopefully some of those will help you to upgrade.
Click to expand...
Click to collapse
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?

BeachNYC said:
Many thanks, will give both suggestions a shot. But isn't the OTA update by definition only a partial update? My problem really arose when OnePlus stopped releasing full updates. Or am I confusing something?
Click to expand...
Click to collapse
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.

kouzelnik3 said:
Not necessarily. It can be partial and full, too.
Full updates are released in case of any issues, also rooted devices need full update files.
Give it a shot and hopefully you will be successful.
Click to expand...
Click to collapse
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)

BeachNYC said:
When I unroot (restoring images) and then try to boot the stock boot image, (just to check before actually flashing it,) it goes into Crashdump mode. Any ideas how to fix? (Since I just booted rather than flashed, I'm out of Crashdump mode but back to square one.)
Click to expand...
Click to collapse
You can try complete uninstall of the magisk by clicking on that button in the app, but better have a backup of your data if anything goes wrong.
Or you can just download the full Ota zip using oxygen updater and use that local update apk if it goes through. Also use that local update apk for android 13 as there is for A12 and for A13. It might solve the issue too.

Did you flash stock recovery to both slots the last time?

g96818 said:
Did you flash stock recovery to both slots the last time?
Click to expand...
Click to collapse
No. Should I?

BeachNYC said:
No. Should I?
Click to expand...
Click to collapse
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.

g96818 said:
yes. you flashed the slot you were on and was able to update since you have the stock images, but now you're on the other slot that probably still has twrp.
Click to expand...
Click to collapse
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.

BeachNYC said:
Okay, I flashed stock recovery to both slots, but still update fails. The system says that I am running c.22, and tries to update me to c.30. On the other hand, the Oxygen Updater says "You need to install c22 first, and then update to subsequent updates via incremental." It then proceeds to download c.22. (I should note that at one time c.26 was installed; Not sure how we dropped back to c.22.)
Regardless, the update fails, even using the local update for Android 13.
Any ideas? I don't like the idea of being stuck forever on c.22.
Click to expand...
Click to collapse
idk. safest way is probably change regions or wait for a full rom. I have c.30 ota download links in my update post, but idk if you want to chance it.