I have 2 GNex running 4.2.1, these are stock 100% google images just rooted and custom recovery. I am using TWRP 2.4.x.x and tried with 2.3 as well and every time I try to flash the 4.2.2. OTA it fails saying error 7.
Any way to flash just the OTA without doing a full wipe or flash the new stock images from google? I was under the impression OTA's can be used with custom recoveries but I guess you can't?
jebise101 said:
I have 2 GNex running 4.2.1, these are stock 100% google images just rooted and custom recovery. I am using TWRP 2.4.x.x and tried with 2.3 as well and every time I try to flash the 4.2.2. OTA it fails saying error 7.
Any way to flash just the OTA without doing a full wipe or flash the new stock images from google? I was under the impression OTA's can be used with custom recoveries but I guess you can't?
Click to expand...
Click to collapse
You can flash ota with a custom recovery. What did the error say?
Sent from my Galaxy Nexus using Tapatalk 2
Zepius said:
You can flash ota with a custom recovery. What did the error say?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
some error's with the libraries, guess it has to do with the nexus loud mod I added, ran the revert zip but still errored. Anywho not a bid deal, just used fastboot to flash system/radio/boot and its fine.
jebise101 said:
some error's with the libraries, guess it has to do with the nexus loud mod I added, ran the revert zip but still errored. Anywho not a bid deal, just used fastboot to flash system/radio/boot and its fine.
Click to expand...
Click to collapse
that is exactly why it errored. you were no longer using a stock rom.
Related
Hey guys,
I'm one of the many Galaxy Nexus owners that don't like their battery usage at all. The device is a yakjuxw build running 4.0.1.
First thing I wanted to do was to update to the official 4.0.2 image from Google. Now lurking through all these threads I saw that most of you recommend franco's kernel for its awesome battery performance. By flashing that custom kernel will I still be able to get OTAs? (on a stock official 4.0.2 image)
Also, some of you reported that the 4.0.2 OTA was pulled back due to some issues. Should I still flash the 4.0.2 image in this case?
Thanks,
NiGhTTraX
To flash a kernal, you need a unsecured boot.img. Its is usually provided with roms but if you want just the Kernal you will need it. To flash that you need to flash recovery Clockworkmod preferably.that will not stop you from getting otas but ubwont be able to install them as ours need stock recovery. So in essence, yes it will prevent you
Sent from my Galaxy Nexus using XDA App
You need clockwork to flash a zipped file. To flash a boot.img all you need is fastboot. And i highly recommend manually flashing 4.0.2. You dont need clockwork recovery. And flash a radio more suitable to your region. That too will help battery life.
Sent from my Galaxy Nexus using xda premium
pr3cision said:
To flash a kernal, you need a unsecured boot.img. Its is usually provided with roms but if you want just the Kernal you will need it. To flash that you need to flash recovery Clockworkmod preferably.that will not stop you from getting otas but ubwont be able to install them as ours need stock recovery. So in essence, yes it will prevent you
Click to expand...
Click to collapse
I thought that if you don't delete the boot recovery image using the root explorer app, once you restart the phone CWM will be overwritten by the factory default image. So shouldn't that allow OTAs to be applied?
@rbiter said:
You need clockwork to flash a zipped file. To flash a boot.img all you need is fastboot. And i highly recommend manually flashing 4.0.2. You dont need clockwork recovery. And flash a radio more suitable to your region. That too will help battery life.
Click to expand...
Click to collapse
So just flashing the 4.0.2 will still get me OTAs right? And all I need is fastboot for that, am I right?
NiGhTTraX said:
Hey guys,
I'm one of the many Galaxy Nexus owners that don't like their battery usage at all. The device is a yakjuxw build running 4.0.1.
First thing I wanted to do was to update to the official 4.0.2 image from Google. Now lurking through all these threads I saw that most of you recommend franco's kernel for its awesome battery performance. By flashing that custom kernel will I still be able to get OTAs? (on a stock official 4.0.2 image)
Also, some of you reported that the 4.0.2 OTA was pulled back due to some issues. Should I still flash the 4.0.2 image in this case?
Thanks,
NiGhTTraX
Click to expand...
Click to collapse
You won't be able to use Franco's kernel unless you flash to a rom based on 4.0.3. You can always go back to stock as long as you have cwm recovery. Users always post stock back ups that you can just copy to your phone and restore from.
Sent from my Galaxy Nexus using xda premium
I keep getting the new OTA IMM76I update for my Sprint Galaxy Nexus and every time it downloads & starts to install it just opens up TWRP recovery and nothing happens...
I tried to use the Nexus Toolkit as well and do exactly what it says but get hung up on "waiting for device" after it extracts the files and everything...
I've been searching for 4 hours to try to get this update done because my calls keep dropping...
is it because I have the Franco Kernel installed on a rooted device?
no ROM or anything, just rooted with the Franco Kernel...
I tried like hell to find the stock kernel but couldn't...
DAMN this is aggravating
could someone PLEASE either explain or point to a link where it explains how to deal with this issue?
HATE having a brand new phone and the calls keep dropping....
I know there are "lots of threads on this issue" already but none clearly explain how to fix THIS issue...
please hep me out...thanks in advance.
http://forum.xda-developers.com/showthread.php?p=20843237
While the above link is for how to manually install updates, the reasons why an ota update won't install are the same: if you want it to install ota, you need: the stock kernel, stock recovery, stock radio, and stock rom (with no original files missing/modified). Additionally, all of these have to be the same version.
Maybe you could also get the ota update file name for us as well.
Sent from my Galaxy Nexus using Tapatalk 2
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
another issue I'm having is damn CWM....I have TWRP on here now and when I go to flash CWM through ROM Manager it get all the way to the end, freezes then fails...can't seem to get CWM installed for my life.
also what is all this "yakju, takju, etc..."??
I'm new to this device from an Evo 4G where we just download & flash and all updates work..never had an issue like this.
my device is v4.0.4., build Imm76D.L700FC12
baseband L700.05 V.FC12/L700.FC12
on the bootloader I saw "toro" on there so I'm guessing that's because it hasn't been updated, correct?
thanks.
broad_st_bully said:
does the stock radio stay the same after root?
like I said, all I changed was the kernel...so I'd have to flash the stock kernel to install the update, correct?
Click to expand...
Click to collapse
If all you changed is the kernel, then all you have to do is flash the stock kernel.
efrant said:
If all you changed is the kernel, then all you have to do is flash the stock kernel.
Click to expand...
Click to collapse
would you have the stock kernel?
can't seem to find it...
Try the GN root kit. You'll find it in the dev section. That will get you back on stock kernel.
Sent from my Galaxy Nexus using Tapatalk 2
You need to have stock recovery too.
broad_st_bully said:
would you have the stock kernel?
can't seem to find it...
Click to expand...
Click to collapse
Unfortunately I do not (I don't own a Sprint device), but I'm sure that it is floating around somewhere.
I'm on a JB rom from here and I just got the OTA update message. If I hit restart and install will it brick it or is it safe to do? If its not how do I clear the message?
Mind providing a little more information? Which Jelly Bean ROM are you running? Is it stock? Is it custom?
If your entire phone is stock, then yes, update.
If not, don't update. Flash stock, perhaps 4.0.4 Yakju, then update.
If you have no idea, don't update. Flash stock, perhaps 4.0.4 Yakju, then update.
Don't be afraid of the search feature located on the top left side of your screen.
This Rom and I have CWM installed
joshua.justice said:
This Rom and I have CWM installed
Click to expand...
Click to collapse
what is "this rom"
joshua.justice said:
This Rom and I have CWM installed
Click to expand...
Click to collapse
Can't help you if all you got is "this ROM". Flash stock 4.0.4 yakju using the toolkit by mskip. Then update.
Sent from my Galaxy Nexus using xda premium
will not flash with cwm, but it won't brick either.
joshua.justice said:
I'm on a JB rom from here and I just got the OTA update message. If I hit restart and install will it brick it or is it safe to do? If its not how do I clear the message?
Click to expand...
Click to collapse
Depends if its a stock image or a custom ROM you're running.
If you've flashed a stock image (doubtful because you say "ROM"), then you can accept it only if you have a stock radio, bootloader, system and recovery. Even if you're 100% stock but with a custom recovery (like CWM), you can't accept and auto-install an OTA. You have to install it manually.
If you're on a custom ROM, you cannot accept the OTA.
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
niaoRen said:
Hey guys,
I received this offiial OTA push for 4.3 update on the 27th July (GMT +8). but when i try to install it on the recovery screen, it says update failed and restarts the phone. But ever since, I couldn't get the OTA push anymore. Not even from System Updates in the settings menu.
Anyone having this problem as well? or anyone know any walkaround for this?
Thanks!
P/S I've flashed my phone with the official rom that gets OTA from google instead of Samsung. And I'm currently on 4.2.2 with fancy kernel R35
Click to expand...
Click to collapse
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
True, I've experienced this before, I would recommend go with Official Factory image if not sure your device is running completely stock before apply OTA...
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
lastforone said:
If i'm not wrong, if you've a custom recovery OTA update fails, happened to me with my Nexus S back a year or two, i just grabbed the official image from google and flashed it VIA ADB.
PS: i can be wrong you know.
Click to expand...
Click to collapse
fux0r99 said:
First of all your using a custom recovery an second your using a custom kernel, so its always going to fail a ota install, my suggestion just flash a ota flashable twrp or cwm zip.
Click to expand...
Click to collapse
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Zepius said:
wrong. a custom recovery does not hinder the OTA, its the custom kernel that is causing the update to fail (and any other modifications you do to /system outside of root)
and if even if he tried to flash a OTA with cwm/twrp, it would still fail because of the kernel. the OTA does an assert check on system files before installing.
Click to expand...
Click to collapse
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
niaoRen said:
So in order for me to update to 4.3, I'd have to reflash the stock kernel then update with the OTA?
Click to expand...
Click to collapse
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
cupfulloflol said:
If that is the only thing you have changed from stock, yes. When it errors out in recovery, it should tell you the problem(s).
Click to expand...
Click to collapse
alright. Will try to revert to stock kernel and try the official OTA. Will revert back here after i've attempted it. Thanks a bunch you all
I just found a easier way to do things.
Just flash this 4.3 stock ROM over my current 4.2 rom. Works like a charm and hassle free.
this is my first tablet and nexus device.. when i got my nexus 7 a few weeks ago.. i took the 4.3 update OTA... then rooted it unlocked it and flashed a custom rom.. i see that theres a new update small im guessing 4.3.1 what do i need to do to update my nexus to that?? can i just flash a 4.3.1 rom?? thanks also what do i do to update my nexus in the future when there bigger OTA'S i kno on my htc one i have to either unroot and go back to stock and take the ota or wait for a dev to make a firmware zip for rooted users to flash.. is it diff with tablets?
You could either flash a custom ROM through recovery on the phone or flash the stock images with fastboot on the computer.
bananagranola said:
You could either flash a custom ROM through recovery on the phone or flash the stock images with fastboot on the computer.
Click to expand...
Click to collapse
ok but if i flash stock images using fastboot while im rooted with a custom recovery and rom wont that mess the tablet up??
P.Mobile said:
ok but if i flash stock images using fastboot while im rooted with a custom recovery and rom wont that mess the tablet up??
Click to expand...
Click to collapse
If you use the flash-all tool (refer to: http://forum.xda-developers.com/showthread.php?t=2382051) both your ROM and recovery will be back to stock.