Edit :- No longer an issue
I actually had this issue this morning. Took me a few hours to find a fix. If i remember correctly, (since i tried so many different things in a short span of time) i believe i downloaded the 9.0.6 OTA update image from oneplus and flashed that through twrp. once i did that, it put the phone back to complete stock and it was working again. Then just run a normal update on the phone to current 9.0.7.
If flashing through TWRP won't work, try through fastboot on the bootloader screen.
Related
I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.
Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.
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!
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.
I've finally decided to install LineageOS on my phone after three years of using stock but when I install 16 it gets stuck on a repeating bootloop when I turn it on where as 15.1 boots correctly. I'll assume this means my bootloader is out of date even though my stock image was fully upto date before I attempted this so to avoid any headaches of myself reading some misinfomation could someone tell me if first I'm correct in thibking this is a bootloader issue and second what I need to flash to get past this problem?
Newer version of stock and a clean install.
I just reflashed my OP5 back to a complete factory stock from Android 8.0, so its back to OOS 4.5.10 and Android 7.1.1 now after using this method: https://forum.xda-developers.com/t/...-0-9-oos-9-0-11-untouched-full-stock.3761706/
I've manually downloaded the latest OOS from oneplus canada website for the OP5, did a manual system install since OTA update doesn't seem to be working, and the phone does its thing initially, reboots, goes on to further install in stock recovery mode, and just as its about to finish it says installation failed..
after several hours now of non-stop testing and troubleshooting, I feel like hitting my head against a brick wall.. i've tried so many methods. manually installing results in failure everytime, I even just tried a sideload installation via ADB and STILL installation failed around the 55% install mark.
Im completely out of ideas on why the hell this wont work. reading up all these guides on the forums here for the OP5 and nothing seems to be working out for me.. everything I throw at this is giving me a failure to install, could really use the help of an expert here.
Solved - took me about 8 hours today lol, but i solved it by slowly flashing my way up from stock to android v10. at the transition between 5.1.7 to 9, required me having to extract the compatibility.zip out of the rom zips. but all in all, everything worked out and is now solved..phew!