Has anyone installed this OTA? I have my device rooted and with TWRP so I'd have to put a little effort into it if I want to install it. I'm just wondering if it solves any of the known bugs to see if its even worth it to install. It's a small 27MB update zip file.
Here's the zip file of the OTA if anyone needs it.
http://www.mediafire.com/file/2i93x1ztq0ur8rn/PB2-650Y_S033_171013_ROW.zip
My specific device Pb2-650y
I noticed the OTA myself recently and had to kill the stupid Lenovo FW Updater processes to keep my device from rebooting into TWRP and doing nothing. I'm half tempted to take a look at the update, but not totally sold.
I just purchased a Phab 2 and love it. Can you tell me where to find the root and recovery?
Thanks!
Related
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
zero313 said:
Wtf got the ota update and its starts all good but then it hangs a yellow ! appears.. what can i do? i even did a factory reset i only was rooted and i took care of that.
Click to expand...
Click to collapse
at least you are getting something OTA
Ditto
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
seanfrisbey said:
Unfortunately, I get the same thing. I was rooted, but I unrooted (not quite as thoroughly as you did, as I only used the "Unroot" option, but we got the same results). Wonder if it is something wrong with the update...
Click to expand...
Click to collapse
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Same thing here
When I bought this device 3 weeks ago, I rooted it with z4root. Not too long after an update disabled z4root on the tablet.
I thought no big deal, but then today comes and I the OTA update won't work.
Anyone more experienced than me have any ideas of how to get this update applied properly?
Me too. Update failed to install. Not sure why. I have also tried unrooting.
FloatingFatMan said:
Did you change ANYTHING when rooted? Did you freeze, rename, modify or delete ANY of the files in the original ROM in any way, shape or form?
Click to expand...
Click to collapse
I'm confused, if I froze an application, didn't unfreeze it but did a factory reset...wouldn't that resolve the issue?
ok so i woke up this morning and my a500 notified me the there was an update available so as you can imagine I was very happy to finally have this, so i updated and when it was done it said update successuful but when I checked it still said 3.01......WTF
Not rooted ever..
Those interested in getting back their OTA, properly backing up their original ROMS or restoring them, please follow the tutorials in this thread:
Going back to stock TUTORIAL
Be helpful and provide your firmware if you have a backup so we can build a database for those who don't.
Be sure to report what is working and what is not working for you once you've tried the tutorials!
Unlike the 14 threads on these matter I take the responsibility as OP to upgrade my original post as firmwares and new info becomes available.
Let's create a focused troubleshooting and tutorial thread,
Thanks.
I'm rooted via gingerbreak and the update worked fine while still rooted. It did break root. Just had to re-apply gingerbreak and all is good, back to root with latest update.
gingerbreak worked with official 3.1 ?
it didn't work with 'leaked' 3.1 ?
OTA
Ok after long night and hours of research i found out a lot.
1 if you have modded ad hoc in wpa_supplicant file recover the original file
2 if you have modded the phone.apk and telephoneyprovider.apk to save battery this is the reason why you won't get the update.
i put these files back and instantly got an update, i mean the exact second i set those back
i can't believe this my updates keep failing to install. FING POS i tried everything, factory reset
i have tried everything, even factory reset, it fails while installing after reboot
acer support are a bunch of retards, they don't even know they sell tablets????????
need help i can't upgrade, it fails every time
does anyone know where the install logs are
the log is \cache\recovery\last-log
Oklahoma City, OK noon CST
First attempt failed:
Changed the wpa_supplicant back to original and all went smooth the second time
I never changed anything and it failed.
**Edit: I rebooted my devices and left it completely alone after unzip and it rebooted into recovery mode and seems to be installing **
I had the same problem, It was pretty disheartening.... but I unrooted my device, re-booted and tried again and SUCCESS!!!
But now I can't get it to re-root using gingerbreak... HELP!
SUCCESS!
Ok. I got OTA update 4.010.08 (122.71 MB) this morning. It failed.
So I unrooted my device. Re-started it and tried again... SUCCESS!
I tried using Gingerbreak to root it again. FAIL!
So I used this: http://forum.xda-developers.com/showthread.php?t=1138228
SUCCESS!
Hope this helps those of you who are having problems.
No need to unroot nor go to stock.
I had the same issues. Then I simply used Acer Recovery to install stock recovery and everything worked fine.
Ceger
Acer Recovery?
Did Acer Recovery come with the tablet?
I tried the update numerous times over the last 4 days. Most of the time the download would fail, which I put down to my slow internet connection and overloaded Acer servers. But about 5 times it would finish downloading and then error out on install with a message about the update being invalid. I tried rebooting several times during this process. I have never rooted the tablet and only have a few apps installed as it was a recent purchase.
Finally it worked when I ejected the external SD card and rebooted. It may be a coincidence, but anyone else who gets the "invalid update" warning during install on an unrooted device may wish to try this prior to the download/install.
Hi Everyone,
I am currently running android 4.3(JWR66v) I flashed it using fastboot, so it is clean.
After that I rooted it and installed CWM v6.3.6 and BusyBox pro.
That is the only changes I did to my device,everything else is stock.
2 day ago I got a system update notification, looking in the cache folder I found this :
"8b2531d9d9a686c7dcf347513ce8141d59a251c6.signed-nakasi-JWR66Y-from-JWR66V.8b2531d9.zip"
I confirmed the reboot/Install but it failed with the classic (Status 7) I do not understand what is going on ?
Do I need flash my device again with a factory to get the update to install ?
I had the same setup since I bough this device last year and It had no trouble what so ever upgrading before(Unlocked+rooted+CWM)
This is supposed to be a nexus device but it sure doesn't act like one,
Can some one please help ?
Had the same problem going from 4.2.2 to 4.3. Same as you, stock rooted, but had TWRP as my recovery. I did go back to stock recovery, but no go. Ended up doing clean install. However, going from JWR66V to JWR66Y, I had no problem. Took OTA without even having to install stock recovery.
You must not be as stock as you think. My guess is you must have altered something in system that they are checking on. Hope someone with more knowledge is able to help you out because it is a PITA to have to clean install for every update. Good luck.
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.
Hello,
I want to know if it is possible to root the stock rom, and keep OTA.
Actually, my objective is to use screen mirroring (miracast), and I heard rooted devices can achieve that by changing build.prop. I didn't want to switch from stock rom, since I like it and like updating OTA.
Maybe if I adb boot twrp and install supersu, but keep regular revovery, I can still get OTA?
If there's another solution to screen mirroring, I'd be glad to know, too.
Thanks in advance!
I've tried to root stock rom and keep the system unmodified through Magisk. For whatever reason OTA always fails even though I have stock recovery, supposedly unmodified system, and rolling back to stock boot image prior to trying the OTA.
The only thing that works is to flash the stock firmware and then taking OTA. The only problem is that the stock firmware is tough to come by, but I read that someone got their hands on the latest 93-10 firmware image. So that's good.
I've since moved onto Pixel Experience 8.1 rom without any regrets. The camera works really well and battery is nearly up to par with stock Nougat.
No, unfortunately these things still modify the the system and boot partition and the upgrade script knows it and causes the update to fail. We don't know exactly everything the OTA update scripts check (it's not just a simple text file) but it is obviously something that it knows you are rooted even when nothing else does. :/
You must be completely stock to take an OTA update... the only exception is your bootloader lock state doesn't matter at this time, we do know that it is capable of detecting that as well.
I have done that and I got Bootloop! So don't Try!
else
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
After half a year of not updating due to the the fact i was rooted, alot of apps started to have small annoying bugs. I also wanted to try out all the new features. I was (and sadly still am) on OxygenOS 5.0.. I decided i wanted to update my device, but since i've had it for such a long time i really didn't want to lose all my data and have to reinstall and relogin to every single app and tweak i've made over the past 6 months. So i looked up on how to accept OTA updates without having to reset, and if possible als not lose root. Now, about 2 days and a lot of work further i still have accomplished nothing.
I'm running windows 10 with all the drivers up to date, a Rooted One Plus 5 running OxygenOS 5.0.1 with TWRP 3.2.1-0 Universal Codeworkx-cheseburger custom recovery.
Here are my problems ;
When sideloading OTA 5.0.1 (to clean up and be able to accept OTA updates again) i get to about 47% and then get the message : Total xfer: 1.00x . I've looked it up and found multiple people with the exact same problem (All posts from 2-3 years ago) but can't seem to find a solution there. I've tried everything (updating drivers, different OxygenOS versions, sideloading via TWRP, wiping and then sideloading) Sideloading with the stock recovery or TWRP still doesn't work.
I now am totally out of options and ask for any of your help. I would be ever so gratefull becasue i really don't want to be stuck on the same OS version for the next couple of years. Thanks in advance!
Luuk
dont worry just copy the file without changing its name to the internal folder of your device. reboot the phone , the notification will appear on the notification panel. This could help some OEM s pl. try