I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
jasondhsd said:
I have fwupgrade frozen but the update popped up wanting to install, I deferred it but I want to disable it so it can't check either. thanks
Click to expand...
Click to collapse
Flash a custom recovery/ROM. That should do it
But I'm not sure what else if the fwupgrade freeze didn't work
Yes. How do I stop this crap!?
I have 2 of these both rooted and hers keeps trying to install it. Its already downloaded on hers. I interrupted mine by killing the internet connection as soon as I saw it start downloading.
I'm sure when I'm sleeping it will try to install itself. So ill just shut my phone off.
Grr...
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
jasondhsd said:
I'm running nosymathy rom with CWM installed and unlocked bootloader. The verizon update downloaded and prompted to install which I deferred for an hour. Not sure if the update will simply fail because I froze fwupgrade or not but I don't want to take the chance and I want to stop OTA completely so it doesn't even check.
Click to expand...
Click to collapse
Thats an issue with no-sympathy.... Most ROM's block the OTAs so you don't even need to worry about them.
This is actually the first ROM i've heard of that allows OTA's to even show up on the prompts.
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
You would have to ask the ROM's developers. Refuse it, and flash to another ROM that does it automatically for you. Obviously No Sympathy didn't think of an OTA... whynot I dunno. But every other developer did.
jasondhsd said:
Cmon no one knows how to prevent OTA prompts? How is it done in other ROMs?
Click to expand...
Click to collapse
Install an old version of synergy?
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
jasondhsd said:
Ah found the problem, I had to freeze com.samsung.sdm now when I click on Software updates under About Devices "Settings" crashes....so now I just won't check for updates. Problem solved.
Click to expand...
Click to collapse
I just did that. sdm 1.0 frozen. I went to the software update and it crashed. I so let's hope that stops the update...
Sent from my Land Line using xda premium
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Blue6IX said:
Just flash a custom recovery - ota updates can't install through a custom recovery so the furthest it gets onto your phone is in the /cache directory limbo.
Click to expand...
Click to collapse
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
shuura said:
I'm running CWMT, and that's what I awoke to this morning. I will freeze the service mentioned a few posts back and see if it actually prevents the OTA from even trying. I guess it's time to flash a custom ROM...
Click to expand...
Click to collapse
So far so good on freezing SDM. We'll see tomorrow morning.
Related
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
wakkigy said:
This doesn't seem like a common problem, but I found a few people who got this issue.
My TF700 have been on 4.0.1 and it does not upgrade to 4.1 JB even though it has been released for a week. I have then used the custom method to force update to 10.4.4.16 - JB. However, I know 4.4.18 just came out and I am afraid it still would not update OTA.
Anyone has a solution for this??
Click to expand...
Click to collapse
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
buhohitr said:
Have to try to go into settings->about tablet-> check for update?? I assumed that your device is locked/rooted with pure stock JB, no modification, no system app freezing?
Click to expand...
Click to collapse
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
wakkigy said:
Yup checking for update has nothing
Before I upgraded to 10.4.4.16 the device was totally stock, and it just does not update for the longest time.
Since I had updated to 10.4.4.16, I have then unlocked, rooted. No mod, no system app freeze.
Still no update notice for 10.4.4.18
Click to expand...
Click to collapse
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Thats OK said:
Well there's your problem if you unlocked.
No automatic OTAs for unlocked tabs.
Click to expand...
Click to collapse
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
wakkigy said:
Thanks - Thats OK :good:
I didn't realized it was that and now I went back to read the All-In-One Guide For Asus Infinity thread detail; I do see that in the note. I am fine with doing manual updates but was just bothered the device doesn't function properly**
I guess now even the tablet will have to be manual updated OR eventually use custom rom :fingers-crossed:
Click to expand...
Click to collapse
Yup. Assuming you're into the stock experience and have the keyboard (thus appreciating the shortcut keys), CleanROM is eyeing you. Your 700 is behaving normally, so that's one problem out of the way.
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
msmajerczak said:
When I come back to home, i saw that update is available. But I forgot temporary disabled root (ota root keeper). My device started update, but it stoped in bootloader (deat android with red triangle) My tf started without update, and now I can`t OTA (update is not available for you). Can I redownload update, and update soft one more time? How can I do this?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Jimmah555 said:
I had something kinda weird happen just now.
I originally unlocked and rooted the moment I got the tablet, and manually installed 10.4.4.16. Everything works great.
I just finished manually updating to 10.4.4.18 and after a reboot, it said I have a system update available, which was 10.4.4.16.....
[/doublerainbowvoice] Does this mean I still got an OTA even though I'm unlocked and rooted?
Click to expand...
Click to collapse
Make sure you delete the old zip file in your sd card.
buhohitr said:
Make sure you delete the old zip file in your sd card.
Click to expand...
Click to collapse
Oh I know that. I just think it's funny that it wants me to "update" to an older software version.
Thats OK said:
http://forum.xda-developers.com/showpost.php?p=28374043&postcount=1
Would the above link be of any help?
Click to expand...
Click to collapse
After that i lost root
msmajerczak said:
After that i lost root
Click to expand...
Click to collapse
Sorry man!
Looks you and me are in the same boat.
I just threw up my hands and did another factory reset last evening.
I just got an email from Motorola offering me to test out the new version of Android for the Ultra, Maxx, and Mini.
That means such will be pushed to the general users within a few days or possibly a week.
From my past experience with such updates, the #1 change is to close any loopholes being used to root the devices. Therefore, I have very little interest in ever updating the O/S now that I do have root.
Is there a way I can stop my phone from checking, and installing, such updates? Such would including blocking the nag popups.
hmm...soak test for camera update possibly? I haven't gotten anything yet for mine...hopefully someone can make this flashable for SS and we'll be fine..
On the maxx hd there was an app that you freeze that made it not download updates.
Sent from my XT1080m using xda-developers app.
This thread talks about how to do it for the Moto X (which is basically the same thing, right?).
http://forum.xda-developers.com/showthread.php?t=2466191
I read through the instructions, and everything seems straight forward until it gets to the part about flashing stock recovery and such.
Will this method work for the MAXX? If so, where do we find the .img files we would need?
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
WaltA said:
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
Click to expand...
Click to collapse
So if all I needed root for was for the entitlement hack (and I've heard that survives the new OTA) could I just accept this OTA knowing that I will lose root? Or will it not install?
Your right in system/app I do not see an updater.apk, but in Titanium backup I do see one to freeze? That should work to stop updates, it did in the past.
WaltA said:
It use to be to "freeze" BlurUpdater_VZW.apk and Upgrader.apk. But I don't see those apps, nor any app with a similar name, in /systems/apps.
Click to expand...
Click to collapse
if youve removed any system apps from the device..the update will fail automatically
dano1282 said:
if youve removed any system apps from the device..the update will fail automatically
Click to expand...
Click to collapse
All I've done was pwnmymoto for root, the entitlement hack, and disable a bunch of apps. can I accept the OTA?
redddog said:
All I've done was pwnmymoto for root, the entitlement hack, and disable a bunch of apps. can I accept the OTA?
Click to expand...
Click to collapse
yes..but root most likely won't survive..youll have to rsd back to stock...download pwnmymoto. install it but don't run it... accept the ota and then the phone will reboot and it should be rooted...should be LOL
Freezing updater . apk doesn't stop the prompts to update.
Sent from my XT1080m using Tapatalk
jfriend33 said:
Freezing updater . apk doesn't stop the prompts to update.
Click to expand...
Click to collapse
Did you freeze MotorolaOTA in addition to Updater?
dano1282 said:
yes..but root most likely won't survive..youll have to rsd back to stock...download pwnmymoto. install it but don't run it... accept the ota and then the phone will reboot and it should be rooted...should be LOL
Click to expand...
Click to collapse
So this is NOT true?
Seems as if I would accept OTA, I'm looking at the business end of a bootloop?
WaltA said:
Did you freeze MotorolaOTA in addition to Updater?
Click to expand...
Click to collapse
No. I assume I'd have to use titanium backup to freeze the MotorolaOTA app?
Sent from my XT1080m using Tapatalk
jfriend33 said:
No. I assume I'd have to use titanium backup to freeze the MotorolaOTA app?
Click to expand...
Click to collapse
I did, to freeze both (Updater and MotorolaOTA).
WaltA said:
I did, to freeze both (Updater and MotorolaOTA).
Click to expand...
Click to collapse
I did this and it stopped the download (I'm rooted and down have time today with messing around with unbricking a bootlooping phone).
I'm glad I happened to look at my phone on my way home from work because it appears that this update just inflicts itself on the phone without any real chance to decline it (at 2am when most people are sleeping).
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
cmarshack said:
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
Click to expand...
Click to collapse
I'm in the EXACT same boat as you. Hoping someone has a solution to this.
cmarshack said:
My Maxx installed the update this morning and has been stuck in a constant reboot cycle ever since. It will boot long enough for me to go in and check on the update (which states that the "Install is deferred") then simply reboots again and again. There is also a code 252 on the software install screen.
Can anyone help me get out of the reboot cycle? My phone is rooted with the entitlement check set to 0, other than that completely stock.
Click to expand...
Click to collapse
You were probably rooted and thus lost your recovery from pwnmymoto. You need to fxz back to stock.
Sent from my XT1080m using Tapatalk
jfriend33 said:
You were probably rooted and thus lost your recovery from pwnmymoto. You need to fxz back to stock.
Sent from my XT1080m using Tapatalk
Click to expand...
Click to collapse
What is the process for "fat back to stock?"
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
esjames said:
does anyone know what the new I535VRUCNC1 has to offer over the ML1 update?
Click to expand...
Click to collapse
Literally one thing: http://www.verizonwireless.com/dam/support/pdf/system_update/galaxy_s3-4.30.14.pdf
Well, then. Thats a worthy update lol
esjames said:
Well, then. Thats a worthy update lol
Click to expand...
Click to collapse
by all means, if you're traveling to Canada then update away haha
Lmao wow. That's the most pitiful update ever. Seriously, couldn't they have waited until there was something more substantial and then included Canadian roaming in THAT update. As always though, Verizon is dumber than a bag of hammers...
Sent from my iPhone using Tapatalk
Might be worthwhile to extract the modem package and see if the SMS bug is rectified.
wow
i was so sure this was a KK upgrade. been looking around for how to retain root if you take it. thanks for the info!
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
EddieK23 said:
Hey guys, I have a question about this update,
My friend has the S3 for whom I safe- rooted, debloated and whatnot. Now that this update came, my friend tried to update but to no avail. She is adamant about the fact that Verizon definitely has something important hidden in the update, despite me trying to tell her otherwise, and figured that she couldn't install the update because she was rooted.
Naturally, I fully unroot her entire phone, uninstall root-only apps, and try the update, but it doesn't work. When the phone reboots for installation, the installation bar loads for a bit,hangs, then just says "error" and does not update.
Anyone know what the problem could be? Normally I wouldn't care so much, but if Android 4.4 is actually coming to the S3 then I don't want her not to have it, and I can already tell it's not going to work if this update doesn't either.
Thank you so much in advance.
Click to expand...
Click to collapse
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
landshark68 said:
Some of the bloatware you removed likely had to be present on the phone in order for the update to take place. Unless you are sure someone is never going to go back to stock without flashing an ODIN tar image and wiping their phone clean, best to just freeze bloatware with Titanium Backup. That way you can just unfreeze it in order to go back to full stock. Unless you have a list of the bloatware you removed and can somehow sideload them back in, you will unfortunately have to flash her phone to full stock VRUCML1 and wipe it clean.
Click to expand...
Click to collapse
Ah, I see, next time I'm around her I'll re-root it and backup all her stuff with titanium backup, flash the VRUCML1 and factory reset, then restore everything and see if it works.
Strangely enough, when the same update for my Verizon Note 2 came out, I was able to update while rooted even though I unsinatalled theexact same system apps I did on her phone. How strange.
Nonetheless, thank you so much.
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Joe R said:
I have a question for you all. I took the OTA update for 4.3 when it came out but after that I rooted my gs3 Verizon phone again successfully. Now I also took this last update and now lost root on my phone. I tried to reroot the phone but it fails now. There error I get on safestrap is something about the addresses not being able to be found. Can anyone help me reroot my phone so my apps like titanium will work again?
Thanks
Click to expand...
Click to collapse
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Ok thanks. I will try to find an ML1 download.
Sent from my Samsung Galaxy S III using Tapatalk
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
pnuker said:
Ok, since I'm not doing the update, how do I get rid of this nagging reminder popping up that I need to update?
Click to expand...
Click to collapse
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Maintained root
twistedillutions said:
U gotta Odin back to 4.3 ML1 .. The latest update unroots your fone. And can not be rooted.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I was able to maintain root on the OTA update by having OTA Survival Mode checked on SuperSU.
SlimSnoopOS said:
See here: http://forum.xda-developers.com/showthread.php?t=
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
smalco44 said:
Looks like the link is broken. I searched the forum and came up empty. Anyone know what the link should've been or how to disable this junk?
Click to expand...
Click to collapse
Apparently I need a refresher on how to properly copy and paste Here's the link again: http://forum.xda-developers.com/showthread.php?p=52515244#post52515244
I have not yet updated to this new patch yet, am I still able to install saferoot as directed on the thread for it or do I need to do something special first?
I've received this update... Now I'm rooted already. I don't know what to do... Should I update it or leave it as it is since I'm using xposed as well.
Will I have to root the phone again?
I've got twrp already installed.
Any instructions?
You can't even take the update if you're root it will just fail to install
wow, this is a pretty big update.
I am on build QB3, anyone else have this? Ive not seen much on it
I don't understand what it's for. I tried to download it but it says I'm out of space even though I have space to install
zune70 said:
You can't even take the update if you're root it will just fail to install
Click to expand...
Click to collapse
I'm rooted, which is what's confusing me. I still have a notification on my settings
jafferkhan said:
I'm rooted, which is what's confusing me. I still have a notification on my settings
Click to expand...
Click to collapse
What rom are you on?
zune70 said:
What rom are you on?
Click to expand...
Click to collapse
There you go
jafferkhan said:
There you go
Click to expand...
Click to collapse
No where did you download your rom from? Did you root by yourself or did you download a rom on here that was already rooted?
I didn't download it from anywhere, when I got the phone, it was on lollipop, checked updates and there was one, after the update I came on 6.0.1
After a few weeks, I rooted it. Now I've this update
And yes I rooted the phone myself, after using odin to flash twrp
jafferkhan said:
And yes I rooted the phone myself, after using odin to flash twrp
Click to expand...
Click to collapse
Ok since you rooted yourself it's going to show the update. Roms like https://forum.xda-developers.com/sp...g900p-pk1-stock-deodexed-marshmallow-t3521415 the developer disable the update notice for that. Think there's a rule you can flash through twrp to disable that too but idk where it is. A it's somewhere I this forum but it's been a while since I could remember where
zune70 said:
Ok since you rooted yourself it's going to show the update. Roms like https://forum.xda-developers.com/sp...g900p-pk1-stock-deodexed-marshmallow-t3521415 the developer disable the update notice for that. Think there's a rule you can flash through twrp to disable that too but idk where it is. A it's somewhere I this forum but it's been a while since I could remember where
Click to expand...
Click to collapse
But how can I take the update? What's it about? Is there any new feature that we're probably missing?
No you can't take the update unless you unroot. All the new updates for this phone are all security updates and that's it. There's no new features of your on 6.0.1. Anything past pca roms were just security updates. Sprint has been releasing new updates every month for this device but it's all security updates.
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.