Hi All,
Want to OTA update my N7 3G (2012) to 4.4.2, but failure to update in TWRP.
Since OTA update not allowed in custom revovery, it any way to update it ?? Or I must wipe and fresh install 4.4.2 ??
Otherwise, is OTA update alloed in rooted device ?? (keeping stock recovery)
Thanks
OTA updates are possible with both, standard and custom recovery, but if you have done modifications to kernel / system most likely the OTA will fail. Or, if it doesn't fail after the update you will loose the custom recovery.
The easiest way to update is flashing boot.img and system.img (extracted from the appropriate Google factory image) by fastboot.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
OTA updates are possible with both, standard and custom recovery, but if you have done modifications to kernel / system most likely the OTA will fail. Or, if it doesn't fail after the update you will loose the custom recovery.
The easiest way to update is flashing boot.img and system.img (extracted from the appropriate Google factory image) by fastboot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
- flashing boot.img and system.img (extracted from the appropriate Google factory image) by fastboot.
can you teach me ??
- i am using stock kernel and restored factory build.prop, but still failed
williamlaw said:
- flashing boot.img and system.img (extracted from the appropriate Google factory image) by fastboot.
can you teach me ??
- i am using stock kernel and restored factory build.prop, but still failed
Click to expand...
Click to collapse
Take a quick look here: http://forum.xda-developers.com/showthread.php?t=2551117
williamlaw said:
- flashing boot.img and system.img (extracted from the appropriate Google factory image) by fastboot.
can you teach me ??
- i am using stock kernel and restored factory build.prop, but still failed
Click to expand...
Click to collapse
You can find a description how to do it on my blog, even if it explains haow to install Android 4.2, the steps are the same.
OTA's are crap. If you're rooted w/custom recovery there is never (IMHO) any good reason to take an OTA.
Sent from my Nexus 7 using Tapatalk 4
nakedtruthishere said:
Take a quick look here: http://forum.xda-developers.com/showthread.php?t=2551117
Click to expand...
Click to collapse
Thanks
AndDiSa said:
You can find a description how to do it on my blog, even if it explains haow to install Android 4.2, the steps are the same.
Click to expand...
Click to collapse
Thanks
Related
So i just switched from HTC ONE X to the nexus 4 and my version is 4.2 and i just rooted it. I have the system OTA update 4.2.1. Should i take it or is there another way to update my phone to 4.2.1 without OTA?
Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.
klvnhng said:
Do not OTA update once you're already rooted; flash this stock ROM (https://www.dropbox.com/s/syi2vmxh0noi2bv/occam-jop40d-factory-ca7602f0.tgz) and re-root.
Click to expand...
Click to collapse
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?
ronnyg12 said:
Thank you i was looking for this file! so i just put it in my SD card and then install Zip from sd card from recovery?
Click to expand...
Click to collapse
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.
estallings15 said:
That is a tgz file, not a zip. You'll need a PC, 7zip and fastboot.
Click to expand...
Click to collapse
Yes yes i figured it out
I've been trying to do this without wiping my device. It's still downloading so I haven't seen the contents, but I'm assuming just flash the .img files with fastboot and it won't erase anything? Would the Rootkeeper app work for this?
if you're only rooted, ota will work and would install without issues. it will only fail if you have modified some system files or the recovery. no need to reflash anything except the supersu for root if you don't use rootkeeper
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.
Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Click to expand...
Click to collapse
Flash the stock recovery.img and boot.img. You won't lose anything.
Nitemare3219 said:
I'm using Franco's kernel and CWM recovery. I have the stock system files, so if I flash those back, how do I go about applying this update? I'm so sick of seeing the update message in my notification bar and do not want to wipe to flash a new ROM.
Edit: I have previously tried flashing the stock boot.img and recovery.img, but trying the update via the notification still failed.
Click to expand...
Click to collapse
Your settings probably also modified the system files. Try flashing that too since you have the stock files. Just don't do userdata so your data is kept intact
Sent from my Nexus 4 using Tapatalk 2
why it is not possible to make OTA update on rooted phone?
Sent from my Nexus 4 using Tapatalk 2
I rooted, unlocked bootloader and flashed recovery yesterday then installed the OTA after, had no issues at all. If you are using cwm recovery it re-roots and prevents stock recovery being flashed after the ota is installed.
So am running rooted 4.2.1 at the mo.. And its sick
Sent from my Nexus 4 using xda app-developers app
blablazzz said:
why it is not possible to make OTA update on rooted phone?
Click to expand...
Click to collapse
You can, it's fine and will work as long as you have stock recovery. You might lose root but can easily re-root if necessary.
Sent from my Nexus 4 using xda premium
why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2
blablazzz said:
why OTA will not work if custom recovery will be present?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Because it won`t!!!
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
hettige677 said:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?
Help Please!!
Click to expand...
Click to collapse
Hello there!
What about a little search? is a search bar in every part of the forum!!!
Anyway there you go:
http://forum.xda-developers.com/showthread.php?t=1745781
Just don't get used to it :good:
Read the forum rules!
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
n/m
hettige677 said:
So I downloaded the zip but it won't install properly it says error code 7??
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Leonhan said:
That's because you are using a custom recovery.
Click to expand...
Click to collapse
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.
The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).
Leonhan said:
You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
Click to expand...
Click to collapse
Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.
The OP should just
- make a full nandroid backup of what they have now
- download the factory 4.2.2 images from Google
- extract the system.img file and boot.img images
( hint for windoze users: 7-zip understands .tgz files)
fastboot flash boot boot.img
fastboot flash system system.img
- reflash a basic SuperSU or Superuser root kit
Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.
If they don't like the result, they can simply restore their nandroid backup.
Hi,
Long time reader, first time poster. I just unlocked the bootloader and flashed the latest franco nightly with fastboot and have two questions:
1. From what I've understood, in order to perform OTA updates, I have to be on the stock kernel. Do I just flash the stock boot.img extracted from the factory image? I think I may have read something about additional changes being done to the system partition after flashing a custom kernel, but I can't seem to find the thread.
2. If I want to flash a different kernel or update the existing one, do I just flash the fastboot image? Does it just overwrite the existing one or do I have to perform any additional steps, like a wipe?
I have not flashed a custom recovery or rooted the device and would like to keep it that way.
Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium
El Daddy said:
Yes. Some kernels do modify system files. If you wanted to get back to stock for an ota you'd flash both the boot.img and the system.img
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?
Eregoth said:
Thanks for the quick reply.
Do I keep my current settings and SMS messages when I flash system.img?
I'm guessing this is only necessary before performing an OTA update. If I'm only updating the kernel I just flash boot?
Click to expand...
Click to collapse
Yep your data will stay intact.
Yep just flash boot. Some say you should clear dalvik cache as well.
Sent from my Nexus 4 using Tapatalk 4 Beta
And what am i doing wrong, when the bootloader is not ending? i have root, unlocked bootloader, fancy kernel, cwmr and louder mod. i reverted the mod. flashed boot, system and recovery back to stock. i also want to perform an ota update.
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
hasbrobot said:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
Click to expand...
Click to collapse
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Ben Ling said:
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
jazzespresso said:
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
Click to expand...
Click to collapse
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Ashenphoenix said:
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Click to expand...
Click to collapse
my OTA failed too, different error. this usually always the case if /system/ folder integrity check failure (error 7), means files in /system/ folder are not original or modified. Yours does not give any details, but I bet it is. to see what error, try to flash it thru CWM or any other custom recovery you use.
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/
Ben Ling said:
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
okay...will my data be erase when installing?
Sent from my Google Nexus 7 using XDA Premium App
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
Tried your SystemUI,don't work...keep on stopped...so I replace back...
Sent from my Sony Xperia™ sola using XDA Premium
I guess I'll download the Nexus Toolkit, click on the flash stock + unroot button, so it flashes the stock 4.2.2 and then I'll try to OTA update again.
I already unrooted, but I think it's not a problem.
Seems like it is not fixable!
I used fast boot to push my missing file.
I used es file explorer.
I used titanium back up to make the app, system...
No way, nothing. Not the slightest luck.
(My missing app is xt9ime.apk)
I haaaaaate this situation.
the worst thing is that xt9ime.apk is asus keyboard, and it is disabled by google on nexus 7.
why should not having an app that they don't want to use be a problem. X(
Sent from my Nexus 7 using XDA Premium HD app
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
jaysus145 said:
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
Click to expand...
Click to collapse
I did full unroot, and I also did a factory reset, but it still fails to install.
Using Wug's Toolkit to flash stock 4.2.2 is a good idea?
Then try to OTA update 4.3 again?
Same problem
Hi,
I think I have the same problem:
What to do?
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
chrisinsocalif said:
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is Fastboot?
Theuntje said:
What is Fastboot?
Click to expand...
Click to collapse
Sadness.
Fastboot is a utility used to control the base fastboot firmware on many Android devices. It lets you do low-level actions such as flashing a custom recovery, ROM, or kernel. Toolkits run fastboot behind the scene, but automate the commands for newer users.
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
I downloaded the system file here: https://developers.google.com/android/nexus/images#occamjwr66v
Then, in the Nexus Root Kit, launch " flash stock + unroot" and select the downloaded system file.
The flash lasts 5 minutes, and the system will reboot.
Then you need to reactivate the usb debugging .
The next action is to relock the Nexus, with the "OEM Lock" in Nexus Root Toolkit.
The system will reboot after flash.
Then, the 4.3 update will be available automaticaly but this time the installation won't crash.
I hope this could help.
el chibro said:
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
...
I hope this could help.
Click to expand...
Click to collapse
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
RocketOptics said:
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
Click to expand...
Click to collapse
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I wanted to save my data and wasn't sure if going directly to 4.3 would be safe. Was just being cautious and letting the OTA do the update.
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
iamdarren said:
Is it possible? It not I will wait till I get home tonight. I'm thinking flash a stock rom zip. Then opt in. Don't loose all internal storage? Thoughts
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
Where can I find the modified boot image?
Edit: Found it, nevermind.
messiahfreedom said:
Where can I find the modified boot image?
Edit: Found it, nevermind.
Click to expand...
Click to collapse
Grab it from here, and make sure to download the corresponding boot.img to your build number.
Link: http://forum.xda-developers.com/nexus-6p/general/stock-modified-boot-img-regular-root-t3306684
DJBhardwaj said:
Yes it is possible. Just download the complete N factory image, plus the modified boot image (kernel).
Extract the system.img, and vendor.img out of the factory image.
And now, flash the three files using TWRP - system.img (system image), vendor.img (vendor image), and boot.img (kernel).
Click to expand...
Click to collapse
If we do it this way, will we lose data? Can we just update from 6.0.1?
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
jorgis1 said:
If we do it this way, will we lose data? Can we just update from 6.0.1?
Click to expand...
Click to collapse
No, you won't loose any data. Your userdata/data partition will stay as is. You will just wipe the system and boot through TWRP, and then flash the listed image files.
superchilpil said:
You can if you were on a stock rom.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
But if we do it the manual way as stated before, do we lose root? What about gapps? Will those be included?
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
I ended up loading up from the PC. It's better this way because I only had 2gb of space on my 64gb!!! Bad thing is, I have spent about 2hrs installing!
Sent from my Nexus 6P using Tapatalk
So I can use flashfire to flash the latest N beta even though I'm currently running a custom ROM?
Sent from my Nexus 6P using XDA-Developers mobile app
GatorsUF said:
flashfire is a great app, does it all for you...
I simply downloaded OTA through the system update, then after it was downloaded instead of allowing it to "Restart and Install" which would have failed due to my custom recovery, I just opened flashfire. It found the OTA automatically and I hit Flash button. Done!
Click to expand...
Click to collapse
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
x.0ni.x said:
Foes your custom recovery still work? I tried this method and it just wouldn't boot into TWRP. Been trying all day thru different methods. Idk how to use adb fastboot on a computer so I'm a lil lost when trying any other method. I've been using Wug's toolkit but until he pushes an update for it I'm on stock MM until i can figure something out.
Click to expand...
Click to collapse
why does the wug toolkit not work?
I don't know a lot about Flashfire as far as it's compatibility with Custom Roms and such. I was previously on stock android Marshmellow with root and twrp. My phone downloaded the OTA for Android N when I "enrolled" in the beta program. I chose not to allow the phone to attempt to install the OTA as it would likely fail due to my custom recovery, to my surprise when I opened flashfire it offered to install the "update.zip" (AKA the OTA) and I simply hit "flash". It installed the OTA (did not use TWRP) and rooted my phone all on it's own, I did not lose anything no data was lost.
As a side not I would not recommend using Flashfire if you don't know how to use fastboot commands and the Android SDK. It is not complicated and it is a almost certain way to fix your phone when things go haywire. I strongly encourage you to learn how to use it as it is essential to owning a Nexus imo. These root kits and flashfire programs are cool, but they are always subject to failures...