Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
GroovyGeek said:
Rooted 6P on stock ROM. Today I got a System update notification. Ignored it, went to Google OTA download location, downloaded the O OTA and attempted to install via Flashify. When the phone rebooted it was in a bootloop. Downloaded OTA to my PC at home, side loaded via ADB and attempted to install via TWRP, failed with Error 7. I then edited the install file to remove the "asserts" from the install script. the script installed seemingly OK but the phone again went into a bootloop. At this point I have re-installed N. Anyone seen that or has suggestions? There is a thread on the Google product forums where a number of people are reporting similar behavior. As usual Google is not responding. They truly are becoming the Microsoft of the early 90s - too fat, too rich, and extremely arrogant.
UPDATE: after downgrading to N (and loosing root in the process since I simply flashed the OTA) I attempted to just take the O update straight from Google as a system update. Everything went without error messages until the reboot, now in a bootloop for the last 5 minutes. Will give it another 5 and then downgrade permanently to N until Google fixes their mess three updates from now. Yup, three updates, just as many as Microsoft used to need to get things right.
Click to expand...
Click to collapse
Since it's a new version, I downloaded the factory image and flashed everything via fastboot. No problems. In fact, every time I have a problem using flashify or down grading, flashing via fastboot solves everything. Maybe you ought to try doing that.
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
GroovyGeek said:
The OTA file seems to be structurally very different from the N files. There are a bunch of files I have not seen before in N OTAs - bootloader.cmnlib, bootloader.hyp, bootloader.keymaster - the list goes on and on. I am going to have to read up on what to flash and what not to, since the potential to brick the device is significant.
Click to expand...
Click to collapse
I'm sorry to say this, but it's probably down to operator error. Making mistakes is just part of the learning process. Just use the full Google image and be done with it. Don't use OTA with Flashify or TWRP. You could have used flash-all.bat with the -w switch removed to leave your data intact, or used the full image with Flashfire retaining root and TWRP. FF makes life very easy, especially when the security updates come monthly.
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
GroovyGeek said:
Yes, this was my mistake. Flashify was messing up for whatever reason, the flashing via fastboot from the full factory image went through fine. I had not done it for a while since Flashify seemed to be doing a fine job with the N incremental upgrates.
Click to expand...
Click to collapse
It looks like the Flashify dev has moved on and abandoned his project in Dec. 2015. Flashfire is an awesome product that you should look into. It does have a bit of a learning curve, but well supported by Chainfire. You can still freeload until sometime next year. There is a dedicated thread here on XDA. Works a treat on regular monthly updates, although I prefer to use the full image with FF, rather than OTA. By default it will preserve root and recovery while flashing. Primer and FAQ can be found here. The only good news is you probably won't make that same mistake again!
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.
My N7 16GB WiFi, rooted but stock, updated successfully to 4.3 some time ago. Basically, I used Voodoo OTA to save the root, let the OTA do its work, then restored root using Voodoo OTA. It's worked flawlessly since then.
Suddenly, after weeks with no issue, it started insisting it had to install 4.3 from a downloaded file. It nags constantly, which makes it hard to use the tablet. I've got CWM as the recovery so whatever file it's trying to install won't work from there. The only way I can find to go back to stock recovery involves wiping the tablet. I don't want to do that, unless there's no other alternative.
I looked for the update.zip file in the location that the tablet insists its stored at (root of SD card), but there's no file there by that name that I can find. It only shows up if I allow the nag screen to try and install it. Of course, CWM says that it can't verify the file and aborts the install. Which puts me right back at the ever-present nag screen.
Just to be clear, I am already running 4.3. This whole situation came up months after I'd upgraded. Is there anything I can do to stop the upgrade notices, short of running a factory reset and having to set up the tablet again from scratch?
May have found an answer. Used Wug's toolkit to force-restore the standard recovery. Had to do some old ADB driver removal for a bunch of other Android devices first. Appears to have deleted the unnecessary update file as part of the process. Will keep an eye on it going forwards, but think it's good.
Nope -- didn't work. Had to do a full factory reset/restore to out-of-the-box condition to get it to stop constantly trying to re-upgrade to 4.3. Annoying.
TL;DR O was janky after dirty flash so downgraded but now N isn't right even after super wiping everything and reflashing stock N image.
Ok so I have no idea why I decided to try out O with all the dumb bugs that are being reported and the lack of a simple night light enabler but I did anyway. Phone was working great on 7.1.2, had the night light and blue pixel accents, the round icons actually just showed up for me which I like better than all the craziness of 5 different shaped icons cluttering up everything.
I dirty flashed stable O and it was janky as hell so after a few hours I decided to downgrade using my nandroid backup I just made. All seemed fine until I got in my car and noticed Bluetooth share was broken which kept causing force closes. I tried everything to fix it but nothing worked, had to end up reflashing latest N image. From that point all went downhill.
Phone will not show all the round icons anymore no matter what (play store being one that I totally despise being that huge play button, music, games, photos, movies, maps, etc but phone, messages, camera contacts and a few other are working), assistant would not enable and only screen search was there, Google drive backup isn't working either even with turning it off and on but it just says it's disabled by the administrator (??), I even went in to twrp and wiped EVERYTHING 3 times under the advanced menu and chose to repair the system and then fully ADB flashed the stock N image again.
After that, I rooted with magisk but now BusyBox won't install as systemless to the su/bin folder, I flashed both the night light only and the full pixel mod from gerard hoping it would enable the round icons on the GNL but it didn't. I tried flashfire to flash the N system again to clean that up but it just turned the phone off every attempt. I finally got it to work by reinstalling magisk but it didn't actually flash the system even though it went through the motions and said it was successful. I had to do it again for it to work but everything just seems weird now. What the F am I doing wrong? I know it's not a pixel thing for the round icons bc my wife's Moto z force just got 7.1 this weekend and the round icons showed up for her with no mods, no root, and she has GNL like me.
Help?
Try downloading a custom ROM like Nitrogen or Aquarius. Both of those have the options you want without having to flash any other mods. As for Google Assistant I've only had luck using Beans Gapps full package or open Gapps stock package. I personally prefer Beans. Do a full wipe before you flash and you should be good.
First of all, you went from N to O with a dirty Flash.... Of course there will be bugs. If you want to go back to N, Flash N image(boot, vendor, radio, system), when it boots up, go to settings and then perform a factory reset. After that, you can restore your Nandroid backup.
Thanks All,
Yes I do understand the issues with going from N to O on a dirty flash which is why it was janky and I decided to roll back. As mentioned, I used TWRP to wipe everything 3 times and then reflashed the latest stock N image. Google assistant worked after doing that and the interesting thing I found was if I disabled or deleted apps from the phone and then redownloaded or reenabled them, the round icons began showing again (i.e. google play, docs, sheets, etc) so that issue is resolved. I did not use the nandroid backup I made, I basically just started over from scratch and even though the Google Drive backup is still showing "disabled by your administrator", I see a new backup that was made this morning at 6:13am. I also installed busybox through magisk now rather than the separate app so I guess the only thing left outstanding is why the phone still says the Drive backup is disabled by an admin.
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
ossito2012 said:
I would grab Nexus Root Toolkit, I install to C:\NRT, download the full August Nougat image, save it to C:\NRT too, then do a complete stock restore, this will wipe everything off phone.
Put you back to starting line and then race with flashing and mods.
Click to expand...
Click to collapse
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
jrg67 said:
I did use wug's toolkit to flash over ADB. I wonder if the image might have been slightly messed up even though the SHA-256 matched. I could always try to redownload the image again. I was going to wait until 8.0.1 was released to try O again but when I did have O, the backup options were stuck on "waiting for backup" (the menus are slightly different in O) and it never seemed to move forward. I researched that and I guess it's a known issue with some phones and a fix is supposed to be coming out this month but at this point, who knows.
Click to expand...
Click to collapse
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
v12xke said:
Toolkit? FFS- fully wipe your device and install full 8.0 image. Done. That is what a full image is for --> janky.
Click to expand...
Click to collapse
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
jrg67 said:
I don't think you are fully understanding what the situation is. I have said now 2 or 3 times, I have completely wiped the phone 3 times in a row using twrps advanced settings and I flashed the latest stock N image. The only reason I used wugs toolkit was so I didn't have to ype out all the commands to flash. After the flash was done, I manually flashed twrp again and re-rooting using magisk. Anyway, things are mostly back to normal now. I will manually flash O again at a later time.
Click to expand...
Click to collapse
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
phantom146 said:
Still wrong. Nuclear flash everything even wiping the whole twrp since its a huge leap from N under the hood. Never dirty flash and of course clean flashing still won't be enough. Do a nuclear flash, wipe everything including your storage and recovery, back it up. Don't be lazy then be frustrated at a plethora of bugs if you didn't even flash properly.
Click to expand...
Click to collapse
To be clear, what do you mean by "nuclear flash" bc I'm pretty sure that is exactly what I did, 3 times. Wiped dalvik/art, system, data, userdata, cache from twrp. As for wiping the recovery, that gets done during the flash of the image. So I ask again, what did I miss? Also, it's been said many times that dirty flashing can cause issues, I get it. I wasn't being lazy with trying to get back to N which is the whole point of this thread.
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've done quite a bit of reading here before posting this. I found bits and pieces of information that I tried to put together, but the outcome is not what I want, so maybe someone here knowledgeable could help me.
Device = Moto G5+
I've unlocked the bootloader, loaded twrp over the recovery partition, rooted the phone, performed a twrp backup prior to installing a custom rom. Then I tried another rom and another. They all have bugs or things to correct, so I decided to go back on my original load by recovering the «start» partiton from my twrp backup. That went well enough. However, since I restored the backup, I get errors and applications (like Settings !) crashing. There is obviously some sand in the gears somewhere. I then tried to reload the phone with POTTER_RETAIL_7.0_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip using Minimal ADB & Fastboot, but that fails. The first 2-3 steps work, then up on the 4th or 5th, I get an error message stating that flashing is unallowed (these are not the exact words, but close enough. I can provide exact words upon demand). From what I read, it seems like I cannot use the NPNS25.137-93-4 load on my phone because my phone shows version NPNS25.137-93-8 which is newer than NPNS25.137-93-4. From there, I am lost. Must I wait until I can get POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip or is there a way around that.
My ultimate goal is to reload my phone with a 100 % working software, relock the bootloader and wait for slow Moto to release Oreo over OTA.
Note : My twrp backup is version NPNS25.137-93-4, but an update came in right after I restored from the backup, but upon instaling, the update concluded with a failure status.