My device is rooted and I am getting error message couldn't install
highgrade said:
My device is rooted and I am getting error message couldn't install
Click to expand...
Click to collapse
It's because your device is rooted. Under most circumstances you need all the partitions to be stock to take the OTA successfully.
How irrelevant it is to root a stock Android phone now a days!!!
Virgo_Guy said:
How irrelevant it is to root a stock Android phone now a days!!!
Click to expand...
Click to collapse
AdBlock could be the only reason for me, I'd be happy. I don't like to use AdBlock VPN, I use my own VPN
Also full theming and customization for me
Virgo_Guy said:
How irrelevant it is to root a stock Android phone now a days!!!
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/what-is-the-benefits-of-rooting-these-days.45050
highgrade said:
My device is rooted and I am getting error message couldn't install
Click to expand...
Click to collapse
You can follow the directions in my thread in Post #2 starting at "How to update each month". There was a zero-day OTA. Optimally, you would've either taken the OTA (longer) or flashed the new factory image (shorter) and then rooted.
Virgo_Guy said:
How irrelevant it is to root a stock Android phone now a days!!!
Click to expand...
Click to collapse
There's a discussion on this elsewhere, many reasons why one would choose to root. Fair play if it ain't for you, but multiple things can be achieved over a stock setup
I am showing my device has the latest version I have attach a screen shot could someone assist men
highgrade said:
I am showing my device has the latest version I have attach a screen shot could someone assist men
Click to expand...
Click to collapse
.009.A2 isn't the latest factory image for the Pixel 7 Pro. Again, if you visit my thread, just a little down from the top of the first post, I list the so far three factory images available for the P7P. The first two are .009.xx, which were the initial release available for the P7P. The third one ends in .031, and is the latest factory image available for the P7P. It was a zero-day OTA, which means that it was available for everyone as soon as they received their P7P on Thursday. I have no idea if it was available before then for the users who got their phones technically before the official release date.
I'll repeat...you can follow the directions in my thread in Post #2 starting at "How to update each month" to update your phone and re-root.
Thank You so Much
Related
I By now everyone must be aware that Lollipop has a new way of checking for system mods that will prevent rooted devices from taking OTAs. Has anyone thought through what the easiest and best procedure will be for updating the firmware going forward? I've applied the lollipop OTA but have been holding back on root until I have a firm hold on how updates will work. I feel there must be many less technical people out there with the same concerns.
From Android Police:
With Lollipop, this has all been turned on its head because now, the OTA script no longer patches individual files. Instead, it patches the system block directly and treats it as one enormous blob. Here's a look at the update script in a recent Nexus 9 OTA:
image
From a technical standpoint, the reason behind the change has to do with verified boot, which was first introduced in KitKat. Even though Google has yet to enable this feature on a Nexus device, this move seems to indicate that the company could be preparing to go that route in the future.
Even outside of verified boot, though, it makes all the sense in the world to do OTAs this way. Patching the system block directly is far faster than trying to patch a lot of individual files. That said, if you're one of those who like to tinker with your devices, you'll have to flash a completely stock system image before applying an update because changing anything by so much as one byte will throw off the signature and make it so the OTA will fail.
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
Also here's chain fire....
http://forum.xda-developers.com/showthread.php?p=36316945
Does it matter when we have access to the factory images?
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
That's not at all what I'm reading. I'll post links later when I get home
Edit: see updated OP
/facepalm
I wrote a thread about other ways to update. Its in my signature
[Deleted]
DamnItLukasz said:
I don't know what that link says but thats not true lolz
Rooted and I got the OTA 3 days ago, just flashed stock 4.4.4 kernel over ElementalX et voilá.
Click to expand...
Click to collapse
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat. Or maybe it wasn't lollipop but to my knowledge there hasn't been an OTA yet released that updates lollipop
NCguy said:
The OTA you got was lollipop but it was applied to kitkat. This is about post kitkat.
Click to expand...
Click to collapse
Ups, forgive me then
Altrezia said:
Does it matter when we have access to the factory images?
Click to expand...
Click to collapse
For the less skilled hacker who doesn't want to wipe it requires more knowledge, more risk and more reliance on modified OTAs, and 3rd party stock builds. Otherwise they're into dirty flashing and that requires more skill and knowledge.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
I'll have a look, thanks. That's really what I was hoping this thread would be about since it looks like plain OTAs may be out.
EddyOS said:
If you're just rooted you can still apply an OTA as you've not changed any of the files the OTA checks. If you've changed any system files then the OTA will fail the same way it'd fail on any previous version of Android. Nothing's changed
Click to expand...
Click to collapse
please read updated OP
NCguy said:
please read updated OP
Click to expand...
Click to collapse
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
EddyOS said:
That article is for the Nexus 9. People on here have successfully updated to 5.0 from 4.4.4, with root, by just sideloading the OTA in the stock recovery. If not, just flash the factory image but leave out the userdata partition
Click to expand...
Click to collapse
It mentions the N9 only because it was the first 5.0 device that was officially released.
I mentioned before this problem is going to exist for updates to devices that already have lollipop, not for those updating from kitkat to lollipop.
rootSU said:
I wrote a thread about other ways to update. Its in my signature
Click to expand...
Click to collapse
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
NCguy said:
Excellent post. With your level of experience you must be familiar with the problems stated in the Android police article regarding the new way google will be checking for system mods before processing the OTA?
Click to expand...
Click to collapse
I haven't read it yet to be honest. I'm not an OTA fan, so I don't spend much time reading up on it. I will though, at some point and update the thread. There is also an OTA help-desk thread but I haven't read that yet. Apparently latest OTA doesn't work with custom recovery either
So I just got a notification for my update. If any developer wants it just let me know and I will send you a link to my Google Drive.
Does it tell you what the update version is. That is very helpful to them. My guess is its J which they have already.
DarkestSpawn said:
Does it tell you what the update version is. That is very helpful to them. My guess is its J which they have already.
Click to expand...
Click to collapse
Really? I didn't check or know how. I used the kdz for 10i a couple of weeks ago and I took the 10j update. Rooted from there and have only been flashing 10j roms. That's why i thought it was new. How do i check?
If so I feel retarded, haha. I thought I was helping out.
kcsevo said:
Really? I didn't check or know how. I used the kdz for 10i a couple of weeks ago and I took the 10j update. Rooted from there and have only been flashing 10j roms. That's why i thought it was new. How do i check?
Click to expand...
Click to collapse
If you click on the notification it should give you more info on it (Haven't actually clicked on one since JB so don't quote me on that lol) or you can pull the update from /cache and upload it to google drive and send me the link so I can look at it. (Dont put the link in the forums cause people tend to flash first, question later why they leap before they look).
DarkestSpawn said:
If you click on the notification it should give you more info on it (Haven't actually clicked on one since JB so don't quote me on that lol) or you can pull the update from /cache and upload it to google drive and send me the link so I can look at it. (Dont put the link in the forums cause people tend to flash first, question later why they leap before they look).
Click to expand...
Click to collapse
K, I'll send it to you shortly. Man i thought I was special! Hahaha.
But wouldn't it be kind of weird for me to get that update? Since I'm already on 10j?
I just sent it to you check your p.m.
kcsevo said:
I just sent it to you check your p.m.
Click to expand...
Click to collapse
I just checked my pm. Didn't see a message other than my old ones. But I'm guessing its a disappointment for me?
@Tilde88 or another will have to look at this. I tried numerous ways to extract this (I'm on Windows and am not familiar with messing with python on it, keep getting Command "bsdiff" is not valid, don't have dual boot on Windows 10 for a Ubuntu OS to do android related things yet, haven't had any motivation for anything these days) but I at least see it checks in the updater script if your system is NRD90M before it proceeds.
I just cant see an update so soon after J. We all know how good LG is at updates as well as source.
DarkestSpawn said:
@Tilde88 or another will have to look at this. I tried numerous ways to extract this (I'm on Windows and am not familiar with messing with python on it, keep getting Command "bsdiff" is not valid, don't have dual boot on Windows 10 for a Ubuntu OS to do android related things yet, haven't had any motivation for anything these days) but I at least see it checks in the updater script if your system is NRD90M before it proceeds.
I just cant see an update so soon after J. We all know how good LG is at updates as well as source.
Click to expand...
Click to collapse
Ok thank you man. I'm sorry I didn't mean to stir this up.
Could be a security patch.
Tilde88 said:
Could be a security patch.
Click to expand...
Click to collapse
The zip was downloaded today by OTA. Hopefully not security for preventing root but security for bettering the system.
No update on this?
Sent from my LG-H918 using Tapatalk
darkjedi said:
No update on this?
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
I'm on Ovrdrive's 10j rom and I just went to the update center and checked for an update. It say my phone is up to date. I'm on Tmo H918.
androiddiego said:
I'm on Ovrdrive's 10j rom and I just went to the update center and checked for an update. It say my phone is up to date. I'm on Tmo H918.
Click to expand...
Click to collapse
But remember with OTA updates people get them at different rates.
jameslapc2 said:
But remember with OTA updates people get them at different rates.
Click to expand...
Click to collapse
You are right, but I also remember with 10j, everyone seemed to get it within a day on TMO.
But you may be right if another one is out.
What size is the zip file?
It's strange why I would see an update on my phone. I am on 10j everything (bootloaded and all) and still got that update.
whats the model after the update
This was the update i took. Also, you can still root just fine.
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.
Did anyone in India received the latest update BKL-L09 8.0.0.151(C675)?
If yes, please provide the OTA link(Manual link). Thank you.
Received 151 update India
Yes i did receive the 151 update today morning, will wait for few days before updating. I have attached a screenshot. I donno where to find the ota links.
RaDi004 said:
Yes i did receive the 151 update today morning, will wait for few days before updating. I have attached a screenshot. I donno where to find the ota links.
Click to expand...
Click to collapse
You are lucky mate, but my device didn't get the update yet(Device is rooted).
Hey no problem if the device is rooted the warranty for hardware will be disconnect but u have warranty on software soo sure u will get the update before the month end
Rooted..?
atf2m4 said:
You are lucky mate, but my device didn't get the update yet(Device is rooted).
Click to expand...
Click to collapse
As far as i know rooted phones will not get OTA. You have to manually flash update.zip and root again, because rooting needs bootloader unlock and will not recognise the device in update server. I guess you have to wait for manual update zip...?
RaDi004 said:
Yes i did receive the 151 update today morning, will wait for few days before updating. I have attached a screenshot. I donno where to find the ota links.
Click to expand...
Click to collapse
Try this method to capture ota links.
https://forum.xda-developers.com/honor-view-10/how-to/how-to-capture-ota-update-url-android-t3773083
RaDi004 said:
Yes i did receive the 151 update today morning, will wait for few days before updating. I have attached a screenshot. I donno where to find the ota links.
Click to expand...
Click to collapse
If someone can capture it.. Please do.
I'm stuck on this and cannot get an update from anywhere
Sorry mate
br54 said:
If someone can capture it.. Please do.
I'm stuck on this and cannot get an update from anywhere
Click to expand...
Click to collapse
Sorry mate i already did the update yesterday morning
Didn't receive update
I haven't recieved the update yet on my phone. Can someone let me know why so much difference in time for receiving update in same country. Also can someone post the full changelog for the update as it show more than 1gb on one off the photos
I shared B151 update to Firmware Finder using "share firmware" option.
Now you can directly install and update from there.
venreddy said:
I shared B151 update to Firmware Finder using "share firmware" option.
Now you can directly install and update from there.
Click to expand...
Click to collapse
Thank you. Will check in FF app. Btw, how come the update is about 1gb in size with such a small change log? If you have already updated, do you have any ideas if they have some under the hood changes which they have not mentioned? Just curious.
kavee.gauravjoshi said:
Thank you. Will check in FF app. Btw, how come the update is about 1gb in size with such a small change log? If you have already updated, do you have any ideas if they have some under the hood changes which they have not mentioned? Just curious.
Click to expand...
Click to collapse
They added some bloatware
venreddy said:
They added some bloatware
Click to expand...
Click to collapse
Haha...more bloatware than whatever mentioned under change log? Damn... Then thank god i got authentication failed error while updating... Now i am contemplating whether i need to find solution for the attached error or let it be...
venreddy said:
I shared B151 update to Firmware Finder using "share firmware" option.
Now you can directly install and update from there.
Click to expand...
Click to collapse
Nope
Fail to install
My update!! they are very good at providing region specific update I guess!!!
I give up.. terrible update or security support
Good thing Samsung are much better
I just rebranded my honor into a Samsung
Never rooted.. Never unlocked.. Stock recovery
Poor support
0 updates
You will get OTA on rooted phone but it wont install. Even just replacing the recovery wont help as your stock boot is modified while root. you need to flash the stock boot as well before you will be able to update via OTA.
Stock phone
Never rooted
Never changed recovery
Never unlocked bootloader
Ota is broke or non-existent
Support sucks.
Great phone if you never want updates
Bug fixes or new features.
These are as is throw away phones.
shashank1320 said:
You will get OTA on rooted phone but it wont install. Even just replacing the recovery wont help as your stock boot is modified while root. you need to flash the stock boot as well before you will be able to update via OTA.
Click to expand...
Click to collapse
Mate, could u provide original stock boot and stock recovery?. Thank you.
shashank1320 said:
You will get OTA on rooted phone but it wont install. Even just replacing the recovery wont help as your stock boot is modified while root. you need to flash the stock boot as well before you will be able to update via OTA.
Click to expand...
Click to collapse
Simply uninstall magisk from magisk manager will restore boot and unroot phone.
Hi
I need some help in updating my AT&T US version of Note 8. I had bought in US and after unlocking it I gave it away to a family member who is using it in Asia now. Since the device it not in US anymore it is has stopped getting firmware updates. The last update was for May 2018 firmware. I want to manually update it to most recent firmware if possible. would be great if someone can help in this process by providing complete steps along with link for most recent firmware for ATT Note 8 device. I believe there have been multiple firmware releases since May 2018, would I have to install all of them prior to getting to most recent one?
Thanks for your help!
A little bit depends on what the current firmware is. Take a look HERE
kangi26 said:
A little bit depends on what the current firmware is. Take a look HERE
Click to expand...
Click to collapse
I got the device upto 4CRE5 and now I am lost on which one goes next. Can you please help me in getting it up to most recent version.
cooldillu said:
I got the device upto 4CRE5 and now I am lost on which one goes next. Can you please help me in getting it up to most recent version.
Click to expand...
Click to collapse
Your best bet is to Odin to N950USQS5CRF6
then use the updates to get to 5CRIA.
I dont have access to the last OTA N950USQS5CRG9 right now so it's a little more complicated
kangi26 said:
Your best bet is to Odin to N950USQS5CRF6
then use the updates to get to 5CRIA.
I dont have access to the last OTA N950USQS5CRG9 right now so it's a little more complicated
Click to expand...
Click to collapse
I tried Odin today with the same exact version you mentioned and it failed to load. Any idea what are the common reasons for failures.
kangi26 said:
Your best bet is to Odin to N950USQS5CRF6
then use the updates to get to 5CRIA.
I dont have access to the last OTA N950USQS5CRG9 right now so it's a little more complicated
Click to expand...
Click to collapse
I installed unlocked CRG9 on the device. Took few try's but it finally worked. After flashing it got an automatic update to CRH7 from Samsung.. You think it will get automatic updates going forward? I have no problem keeping the unlocked device firmware on this.