Hello all,
Should I do OTA or just go FACTORY?
My Nexus 7 2013 is running 5.02, unlocked/rooted running TWRP custom recovery.
I have about 3 OTA updates to sideload to bring me up to 5.1.1 using the Nexus Root Toolkit. Should I even bother going OTA or just go with a factory pack and get it done in one step so to speak? I get the feeling doing several OTA updates is just asking for bugs and other problems. I don't care if it means me losing my settings and starting over if doing so is the better decision.
Please advise....thanks in advance.
It's a lot less hassle to just flash the factory images. But... There are TWRP-flashable zips here made by scrosler that will take you from 5.0.2 to 5.1.0 and then 5.1.1; the threads where each zip is will also have a TWRP-flashable bootloader.
Telyx said:
It's a lot less hassle to just flash the factory images. But... There are TWRP-flashable zips here made by scrosler that will take you from 5.0.2 to 5.1.0 and then 5.1.1; the threads where each zip is will also have a TWRP-flashable bootloader.
Click to expand...
Click to collapse
Hi, thanks for the response. I actually took the plunge and used Nexus Root Toolkit by Wug to simply download the factory image and install it. I was able to keep all my settings and I remained unlocked BUT I did have to ROOT and install TWRP again which was simply a matter of clicking the button in the toolkit. I was done in less than 15 minutes. lol
That was definitely the way to do it. Simple, easy, no hassles.
Yep, there's that too--it just automates the process. I have used it a few times too, and I have nothing at all against it, but for the last couple of updates on my N7 2013 I just dirty-flashed scrosler's pre-rooted stock updated ROMs.
Telyx said:
Yep, there's that too--it just automates the process. I have used it a few times too, and I have nothing at all against it, but for the last couple of updates on my N7 2013 I just dirty-flashed scrosler's pre-rooted stock updated ROMs.
Click to expand...
Click to collapse
I'm not aware of those items. I'll have to check them out for future use. I probably won't need it though. I doubt there are going to be more updates for the Nexus 7 2013 as it is getting 'old' technically. If it sees Marshmallow I will be completely shocked! lol Though, there could always be another security patch released. Yet, my old Samsung Galaxy S3 was immediately protected because I use Textra and they patched against Stagefright quickly. You never know, it could happen.
Thanks for the info, etc.
I'm getting ready to sell my Nexus 7 (upgrading to either a Moto X Pure or a Nexus 6) and I flashed it down to Kit Kit and then used the OTA updates to go back to 5.1.1. Every time I try to flash a lollipop image, I get the system.img not found error. I've tried flashing the imgs separately and it's never worked right.
linkboy said:
I'm getting ready to sell my Nexus 7 (upgrading to either a Moto X Pure or a Nexus 6) and I flashed it down to Kit Kit and then used the OTA updates to go back to 5.1.1. Every time I try to flash a lollipop image, I get the system.img not found error. I've tried flashing the imgs separately and it's never worked right.
Click to expand...
Click to collapse
I like to do that after a while. For some reason, things start to get wonky when you flash custom roms. I think some things get skipped over when you just flash newer roms. Occasionally I will do the same thing.
Related
I have a rooted Nexus 7 2013 LTE with TWRP. When I tried to update from 4.4 to 4.4.2, it gave me an error saying there's unexpected contents in /system/bin/ping6
I've tried both auto updating directly from server and manually update from downloaded zip file. It gave me the same error msg.
Anyone knows how to fix it? Thanks!
Can you device still boot into Android/recovery/bootloader?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
install stock 4.4 with full wipe.
after that the update works.
I tried it before without wiping and got errors like this.
Sent from my GT-N7000 using xda app-developers app
I had a similar problem updating mines to 4.4.2. as well. Same error but mines was unexpected contents in /system/bin/mm-venc-omx-test720p. Even a factory reset didn't work. I had to flash the 4.4 factory image then I was able to sideload 4.4.2. Luckily they have already uploaded the factory image for 4.4.2 so you could flash that and you should be good to go.
aarsyl said:
Can you device still boot into Android/recovery/bootloader?
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
Click to expand...
Click to collapse
Yes, it can still boot to bootloader and TWRP
ThaiDai said:
install stock 4.4 with full wipe.
after that the update works.
I tried it before without wiping and got errors like this.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll give it a try.
bolo808 said:
I had a similar problem updating mines to 4.4.2. as well. Same error but mines was unexpected contents in /system/bin/mm-venc-omx-test720p. Even a factory reset didn't work. I had to flash the 4.4 factory image then I was able to sideload 4.4.2. Luckily they have already uploaded the factory image for 4.4.2 so you could flash that and you should be good to go.
Click to expand...
Click to collapse
Can you give me a link to download the 4.4 factory image? Thanks!
Try flashing a stock/custom rom first, and do a factory reset. If that doesn't work, use a factory image.
Note: flashing the factory image will wipe your device. Buuuuut...if you don't have an operational device to begin with, what do you have to lose?
Here is the page with all of the factory images for Nexus devices.
https://developers.google.com/android/nexus/images
Here is the exact link if you feel really lazy, but I suggest that you still take a look at the rest.
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
aarsyl said:
Try flashing a stock/custom rom first, and do a factory reset. If that doesn't work, use a factory image.
Note: flashing the factory image will wipe your device. Buuuuut...if you don't have an operational device to begin with, what do you have to lose?
Here is the page with all of the factory images for Nexus devices.
https://developers.google.com/android/nexus/images
Here is the exact link if you feel really lazy, but I suggest that you still take a look at the rest.
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
Click to expand...
Click to collapse
thanks alot for the link! I might flash it back to 4.3.1 because some apps/function don't work well after I updated to 4.4. I suspect that they won't work well in 4.4.2 either.
steve_xyz said:
thanks alot for the link! I might flash it back to 4.3.1 because some apps/function don't work well after I updated to 4.4. I suspect that they won't work well in 4.4.2 either.
Click to expand...
Click to collapse
Compatibility is the problem. It's just a matter of time before the devs update their apps. I'm toughing it out on 4.4.2, while 4.3 is tempting at times. I do miss using Google Talk instead of Hangouts. The simpler interface is sooooo much faster. But not quite enough for me to jump an entire Android version.
aarsyl said:
Compatibility is the problem. It's just a matter of time before the devs update their apps. I'm toughing it out on 4.4.2, while 4.3 is tempting at times. I do miss using Google Talk instead of Hangouts. The simpler interface is sooooo much faster. But not quite enough for me to jump an entire Android version.
Click to expand...
Click to collapse
If I have to go thru flashing factory image in order to update to 4.4.2, then I'd rather go back to 4.3.1 and wait until all my favorite apps get updated first. Unless 4.4.2 is really that much better it's worth going thru the trouble.
Hello,
I am fighting since yesterday to get the OTA update to install so I wanted to share my current steps and hopefully someone can suggest how to move on.
I have a GT-I9505, initially 'samsung version'. I installed TWRP in order to install the GPe edition. My phone is rooted.
I used to have TWRP 2.6.x
A few days ago, I got like many the OTA update for Lollipop. I let the phone download it and reboot. That´s when things became a bit more complicated.
After reboot, it went to TWRP where no update happened. If I reboot, I get back to be GPe version 4.4.4
I tried upgrading TWRP to a recent version without better results. I tried with TWRP 2.8.1.0
I have read in several places that the issue is that the OTA update expects the stock recovery.
Unfortunately so far I did not find a stock recovery for my S4 that does the trick.
I tried using the "Miustone_stock_recovery-flash-GE4.3". I could install the recovery.
I did save the OTA zip but I don´t know how I can skip the download and use the OTA zip... so so far I do it the 'lazy-lengthy' way and I wait for the download.
After flashing this 4.3 recovery, I get a slightly better result (but nothing better than I got using TWRP): After downloading the OTA, the phone reboots, goes to recovery and it tries to install the OTA update but it fails with the following message:
mmc_test.ko has unexpected content... Status 7
Can anyone suggest a way to easily install this OTA? I guess using a correct recovery could help... if I could find it.
Any hint appreciated.
if your rooted, you cannot OTA update.
justda said:
if your rooted, you cannot OTA update.
Click to expand...
Click to collapse
Are you saying the recovery is NOT the issue and if I unroot (I guess this is possible) it would work ?
As an update, I just tried now using Miustone_Stock_Recovery-flash-XXUBMF8.zip and I get the same result.
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
justda said:
I have seen alot of people complain about the 7 error, i even got it when i attempted to update. Everything i read states you cannot update with the OTA .zip if your phone is modified with root and/or a custom recovery.
My advice is use one of the 3 or 4 GPE roms from the 9505 thread. But if you want to totally factory reset your phone have fun, to each his own. :good:
Click to expand...
Click to collapse
Hi Justda,
First of all, thanks for your time and answers. My expectations are fairly low actually I installed the GPe version thinking it would make it simpler.
I was happy to get the OTA thinking I could upgrade in a click...
I realize from your answer that the OTA I am getting on my I9505 is actually meant for the I9505G and thus will not work whatever I do (correct me if I am wrong).
I will follow your advice and pick up one of those ROMs. Do you recommend a specific one?
iBastid or Danvh are my go to guys. Both are active and have a large following of users.
Danvh is straight up no aroma install, you mod it yourself.
Bastid uses aroma to give you more initial choice with his customizations.
But its up to personal preference right now, GPE is still to new for a lot of ROM pimping...
Sent from my GT-I9505G using XDA Premium HD app
I would suggest you to use antaresone's lollipop rom
link here http://forum.xda-developers.com/galaxy-s4/i9505-orig-develop/rom-cyanogenmod-12-t2943934
Questions, it's not here, ask to move this thread in the good section... Q & A
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Snowby123 said:
One or two days ago I received an ota notification. Every time I try installing the small update, the tablet boots into TWRP, and I don't know what to do next. Why does it not simply install? The nexus 7 is rooted with an unlocked boot loader. Can anyone give me a tip on how to get the update installed?
Click to expand...
Click to collapse
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Batfink33 said:
With 5.1.1 if the system is altered such as rooting or putting a custom recovery on the device, the update won't install. You have to go back to Pure stock to receive and install updates over the air.
Click to expand...
Click to collapse
Thank you very much! I am glad that some one had an explanation!
How can I restore to stock recovery for LMY48L? There is no LMY48L factory image, so I can't just extract the recovery out of there. Is there any way I can manually apply the LMY48L OTA's recovery to the recovery image in the LMY47V factory image to get a "stock" LMY48L recovery?b
EDIT: Never mind, it looks very complicated. I ended up just flashing LMY47V recovery and system images, then re-updating to LMY48L, then finally updating to LMY48P. I didn't mean to hijack the OP's thread, but I asked here because it looked like he would run into the same issue as I did.
Hi!
I had 2 nexus 5x phones. One rooting went fine, the other is stuck at the Welcome to Android cycle.
I unlocked the bootloader, and I used chainfire auto-root script from linux.
When the phone boots up it has the blue welcome screen. I setup wifi and then it forces me to install an android update. It downloads the update, reboots, tries to install it, fails, and then boots into android where it tries to force me into the update.
How can get out of the loop?
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
draggehn said:
Just flash your favorite custom ROM from recovery (or stock if that pleases you) and ignore OTAs.
Click to expand...
Click to collapse
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
OP, the way googles OTAs work these days, is that they basically check your system partitions for any modification (e.g. root). if that check fails, so does the update. now what can you do about your little update trap?
if i recall correctly, chainfire includes ways to revert to unrooted. so there is you first possible option. use it, fire up your phone, let it take the OTA (make sure you're on the latest version after that) and attempt to root again.
if that is not an option, you could grab the newest factory image directly from google, flash the whole thing and then root again.
once your phone is up and running (and rooted ofc), it won't be able to apply future OTAs, but instead of forcing you to update, it will only show a notification.
Broken303 said:
not everyone is after custom roms, some people are more than happy with their (rooted) stock experience.
Click to expand...
Click to collapse
Which is why there was a parenthetical note that you can also flash stock.
I'm so confused with this phone. Google sent me a 128gb Pixel XL which I activated on my Sprint account. I'm fairly comfortable with rooting, flashing, TWRP, SuperSU, etc., however for the life of me I cannot get TWRP to stick.
Background...
Phone came to me straight from Google, and updated to 8.0 immediately (this was in August). Since, the phone doesn't appear to have been updated as I was still on 8.0 from August I believe
Here's what I did...
Unlocked the phone, using TWRP image, boot to it via fastboot, flash the installer TWRP zip, and then issues happen.
On 3.2.1.0-0 it reboots to system (even if I go back into TWRP's main setting and Reboot Recovery). If I use 3.2.0.0-0, it gives me an ERROR 1 code. I've tried using systemless root method (with the modified TWRP img, Aroma Installer for SU, etc.). I've tried using the 2 most recent TWRP images from their website. I initially started with this guide ([GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +). I then tried this method using Systemless root ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)).
I even tried flashing the OTA manually, which caused other issues, mainly bootloops. I finally got the most recent 8.0 OTA to work after multiple errors (which appear to be caused by outdated platform_tools). When trying to flash the OTA, only OPR1 would flash, OPR3 would always just hang or throw errors (sorry, no changelog, which I know is not helpful). Am I not correct that OPR3 is what is needed for a Sprint (US carriers) based phone? Regardless, everything is up, and running now in 8.0, however I can't take the OTA (it fails when trying to download), and I still can't get TWRP to stick.
Is there anything obvious I'm missing? I can boot to TWRP, but can't flash it, regardless of what I do. I've searched and most issues I've found in getting TWRP to stick either has to do with flashing the boot.img from an OTA or using 3.2.1.0 instead of 3.2.2.0. Funny thing, I don't see the 3.2.2.0 img file, just the flashable zip. Someone please help me, even if it is to tell me I'm in over my head and should stick to a stock rom.
I think you should simplify your life.
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file.
That will update your phone, but leave settings a data in tact. Again, remove the -w so you don't wipe user data.
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
I do it each month this way. It takes 15 minutes and I have zero problems.
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
TonikJDK said:
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file..
Click to expand...
Click to collapse
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
TonikJDK said:
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
TonikJDK said:
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
Click to expand...
Click to collapse
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
2 different methods, same result. Make sure to thoroughly follow instructions with whatever method you try and you'll be fine.
vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.
TonikJDK said:
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
Click to expand...
Click to collapse
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.[/QUOTE]
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Chance Ill said:
I
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Click to expand...
Click to collapse
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
TonikJDK said:
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
Click to expand...
Click to collapse
Oh ok. I do remember coming across Chainfire's announcement awhile ago but was unaware that the new owners hadn't been active with the community. That's disappointing to say the least.
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
Tried this, for some reason wouldn't work. Tried the TWRP and it wouldn't due to OpenSourceScript or something. Then tried rooting and installing busybox, it wouldn't do this either. It attempted to flash it to sd card, another place, and finally in the right storage for this device, and it wouldn't for some error. No specifics on the error were given.
TonikJDK said:
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
Click to expand...
Click to collapse
Tried this next, removed the -w, and used flash-all in fastboot. This worked, however after I upgraded to 8.1 OPM1, I left it alone. Will try again tonight to root, and attempt flashing magisk for the first time.
Thanks for all the advice!