Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
either you use fastboot or you use cwm, no point using the two at the same time, under controlled conditions.
garpunkal said:
Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
Click to expand...
Click to collapse
-w wipes. Omit -w and it won't wipe.
With that being said it's not necessary. Download the OTA, boot into recovery and apply the update with CWM.
garpunkal said:
Hi,
How do I update to the latest stock OTA when using CWM?
Do I extract the image zip file from the google image
and update in fastboot as below:
fastboot -w update image-yakju-icl53f.zip
if so, will this wipe anything?
Click to expand...
Click to collapse
You are mixing-up two things: there is a difference between flashing the latest build or updating a previous build. In the first case, you actually flash a full ROM. In the latter, you flash an increment OTA update. Both methods should get you to exactly the same build.
See links in my signature.
Sent from my Galaxy Nexus using Tapatalk
Look at this link, Worked for me thru CWM: http://forum.xda-developers.com/showthread.php?t=1419170
Related
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Hussainally said:
I got the OTA update downloaded but could not install.Read somewhere if you have CWM ota update wont work.So i have downloaded the stock image for 4.0.2 and its in .tgz format
How can i upgrade to 4.0.2 using CWM or odin and not loose my data and setup.?
Please advice
Click to expand...
Click to collapse
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
mbroeders said:
Check out Chainfire's thread. He posted a no-wipe version flashable through Odin. Follow the instructions there and make sure you download the correct version for your phone (GSM/LTE)!
Click to expand...
Click to collapse
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Hussainally said:
hi thanks for your reply.His update you will not be updating to new bootloader am i right?
Click to expand...
Click to collapse
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
mbroeders said:
Indeed, it won't touch your data, recovery or bootloader. They're all safe afaik
Click to expand...
Click to collapse
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Hussainally said:
thats the prob...4.0,2 has a new bootloader right?i want that.
ok what if i just want to install fresh clean stock 4.0.2...how do i do that?
Click to expand...
Click to collapse
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
mbroeders said:
If you want fresh clean stock then you can do two things:
1) on linux, extract the contents of the tgz package and use the sh script inside to flash.
2) since that's not possible on windows, you could use Chainfire's odin files first and next manually flash the bootloader and/or radioimage with fastboot. You can extract the bootloader and radio yourself from the tgz/tar package or look for them in the development section, someone posted them there.
Click to expand...
Click to collapse
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Thanks everyone...will give it a go.....Cheers
krohnjw said:
You can flash it in windows using fastboot, you don't need to use odin for anything:
Extract the factory images
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Click to expand...
Click to collapse
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
What I posted does not wipe. There's little reason to use Odin. Using Odin you *can* easily brick your device (Ask all of the folks in the Nexus S forums that used Odin to flash the wrong package for their device).
fastboot update image-yakju-icl53f.zip <-- This does not wipe
fastboot -w update image-yakju-icl53f.zip <-- This wipes (-w wipes)
mbroeders said:
Thanks. Just checking, if I would like to do this, but without a wipe, can't i just flash the bootloader and radio like you suggested, and then use Odin to flash Chainfire's no-wipe version right? Just so i fully understand, thanks!
Click to expand...
Click to collapse
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
Nevermind guys...I DID IT.Thanks so much...excellent guide
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Hussainally said:
Hussainally said:
ok guys please bare with me here,Never done this before.when i run command adb-windows.exe,it works,thenwhen i run fastboot-windows.exe devices it works
then when i go to bootloader more...the green android with word start on top when i type fastboot flash bootloader bootloader-maguro-primekk15.img,nothing happens and it says on the phone bad command or something
please advice
ok i lost root after flashing to 4.0.2 using this guide and re did install superboot windows .bat and now the phone rebooted and its stuck on google screen...how long do i wait and what do i do next???
Click to expand...
Click to collapse
Give it some time, if it doesn't boot all is not lost. Pull the battery and restart.
Click to expand...
Click to collapse
ok..fingers crossed...how much time?
Halleluyah....Praise the lord....thanks a million...All is well
Hussainally said:
ok..fingers crossed...how much time?
Click to expand...
Click to collapse
I think that it depends on how many apps do you have...usually 2-3 minutes max. !
Hello,
I have a yakjuxw and have followed the GUIDE flashing your first Galaxy Nexus Rom for NewBs to get the Google build Yakju. Step 1 to 5 were OK but when i flash image-yakju-itl41f:
- opening package
- installing update
- installation aborted
How can i get image-yakju-itl41f installed?
Thanks for helping!
Don't you have to use fastboot to flash the stock images..?
joshnichols189 said:
Don't you have to use fastboot to flash the stock images..?
Click to expand...
Click to collapse
I enter CWM by first entering the Fastboot mode Screen.
ANDSFR said:
Hello,
I have a yakjuxw and have followed the GUIDE flashing your first Galaxy Nexus Rom for NewBs to get the Google build Yakju. Step 1 to 5 were OK but when i flash image-yakju-itl41f:
- opening package
- installing update
- installation aborted
How can i get image-yakju-itl41f installed?
Thanks for helping!
Click to expand...
Click to collapse
You can't flash that using cwm since cwm.
You need to flash that file manually with fastboot.
Sent from my Galaxy Nexus
OK so i tried to flash the file manually but i think i'm typing something wrong in the command prompt:
fastboot-windows.exe flash recovery.img
--> unknown partition 'recovery.img'
--> error: cannot determine image filename for 'recovery.img'
I understand what this means but i don't know what i should write. The image-yakju-itl41f.zip is in my root of the C drive and i extracted it.
In the GUIDE they speak about the stock recovery image, but i want the google build.
I've got it using this zip and fastboot-w update image-yakju-itl41f.zip
Thanks for helping guys
Is there a way to update to 4.2.2 using the stock .img from Google without USB? (Due to water damage) I would like to keep root too.
I was thinking to use Bluetooth to send boot.img, system.img, radio.img, bootloader.img and SuperSU.zip to /sdcard then use MobileOdin to flash them but unsure if it'll work.
Current state of Phone
Rooted stock 4.1.1 with latest TWRP recovery
Any ideas?
What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.
freakb18c1 said:
What's preventing you from downloading the new Rom via WiFi? Then flash in your recovery, or am I missing something here.. Are you trying to update to the latest 4.2.2 OTA? You can run ADB over your network, I personally would download the Latest CM10.1 and be done with it.
Click to expand...
Click to collapse
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?
adamgibbo said:
Sorry for not making it clear, yes I want stock 4.2.2 also need to update bootloader and radio, my new plan is this:
1) Download system.img boot.img JDQ39_radio_bootloader.zip (which I found Here) and SuperSU.zip
2) Using Mobile Odin Flash system.img and boot.img
3) Boot into recovery and flash JDQ39_radio_bootloader.zip and SuperSU.zip
4) Wipe
That should work right?
Click to expand...
Click to collapse
It should, yes.
Now CM appear to have disabled their links to official roms, updates & kernels for older builds, I've mirrored them all on AndroidFileHost and put the links in one post so that they're easy to find.
There are different files for each ROM: signed fastboot flashable zips, signed zips, OTA incremental update zips., boot-debuggable images and stock recovery images.
Signed fastboot flashable zips: These contain the complete rom and can overwrite everything including your data partition. These cannot be flashed via recovery - extract their contents and flash via fastboot. Due to changes in bootloader, don't use them to upgrade from CM 11S to CM 12S or downgrade from CM 12S to CM 11S.
Signed zips: Normal recovery-flashable zips that contains just the system and kernel (they won't overwrite your data partition).
OTA incremental update zips: These are recovery-flashable zips that update your rom to a newer version. To check which version you are running, look at the ro.build.version.incremental line in your /system/build.prop file and then update incrementally.
Boot-debuggable images: These are boot images (kernels) that enable adb root and the developer menu options. To be flashed via fastboot.
Stock recovery images: These are stock recovery images which are recommended for applying OTA incremental update zips. To be flashed via fastboot.
NOTE: Both Yureka & Yureka Plus share same firmware, but don't use pre-cm-12.0-YNG1TAS34J builds on Yureka Plus - the device will be soft-bricked!
Signed fastboot flashable zips
cm-12.1-YOG4PAS8A4-tomato-signed-fastboot-a7a306cebd.zip
cm-12.1-YOG4PAS3JM-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS34J-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip
cm-12.0-YNG1TAS0W0-tomato-signed-fastboot.zip
cm-11.0-XNPH05Q-tomato-signed-fastboot.zip
cm-11.0-XNPH52O-tomato-signed-fastboot.zip
Signed zips
cm-12.1-YOG4PAS8A4-tomato-signed-224c88c4ef.zip
cm-12.1-YOG4PAS3JM-tomato-signed.zip
cm-12.0-YNG1TAS34J-tomato-signed.zip
cm-12.0-YNG1TAS1K0-tomato-signed.zip
cm-12.0-YNG1TAS0W0-tomato-signed.zip
cm-11.0-XNPH05Q-tomato-signed.zip
OTA incremental update zips
YOG4PAS8A4 from YOG4PAS3JM: cm-tomato-04864afef4-to-5242dd42b2-signed.zip
YOG4PAS6ZA from YOG4PAS3JM: cm-tomato-04864afef4-to-f758a6e288-signed.zip
YOG4PAS3JM from YNG1TAS34J: cm-tomato-c991cd279d-to-04864afef4-signed.zip
YOG4PAS3JM from YNG1TAS1K0: cm-tomato-00b2e333e8-to-04864afef4-signed.zip
YNG1TAS34J from YNG1TAS1K0: cm-tomato-00b2e333e8-to-c991cd279d-signed.zip
YNG1TAS1K0 from YNG1TAS0W0: cm-tomato-56deeca328-to-00b2e333e8-signed.zip
XNPH05Q from XNPH52O: cm-tomato-efbb5514a1-to-9828f8e9cc-signed.zip
Boot-debuggable images
cm-12.1-YOG4PAS8A4-tomato-boot-debuggable-8bc066a691.img
cm-12.1-YOG4PAS3JM-tomato-boot-debuggable.img
cm-12.0-YNG1TAS34J-tomato-boot-debuggable.img
cm-12.0-YNG1TAS1K0-tomato-boot-debuggable.img
cm-12.0-YNG1TAS0W0-tomato-boot-debuggable.img
cm-11.0-XNPH05Q-tomato-boot-debuggable.img
cm-11.0-XNPH52O-tomato-boot-debuggable.img
Stock recovery images
cm-12.1-YOG4PAS8A4-tomato-recovery.img
cm-12.1-YOG4PAS3JM-tomato-recovery.img
cm-12.0-YNG1TAS34J-tomato-recovery.img
cm-12.0-YNG1TAS1K0-tomato-recovery.img
cm-12.0-YNG1TAS0W0-tomato-recovery.img
cm-11.0-XNPH05Q-tomato-recovery.img
cm-11.0-XNPH52O-tomato-recovery.img
Credits
@Spannaa for the inspiration.
@AndroidFileHost for the hosting.
YU for the device.
Cyanogen for making the OS.
Reserved for future.
First post updated; added YNG1TAS1K0 build.
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
sal_rc said:
Can't flash the YNG1TAS1K0 from YNG1TAS0W0 ota update,
Installations error on custom recovery and stock recovery too
Click to expand...
Click to collapse
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
milav said:
how do i verify that latest S1k0 fastboot update is authentic sir??
you said that they have disabled the updates so any way to verify?
Click to expand...
Click to collapse
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
Should I do factory reset too afterwards?
Click to expand...
Click to collapse
@sal_rc
Not mandatory, but you can.
Titokhan said:
@sal_rc
Not mandatory, but you can.
Click to expand...
Click to collapse
my bootloader will be locked again? Right?
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Titokhan said:
@sal_rc
No, flashing OTA will not re-lock the bootloader.
Click to expand...
Click to collapse
I was afraid I'd have to do it all over again
Thanks anyways
Titokhan said:
This is a common symptom noticed by other users. In that use, use the full update zip i.e cm-12.0-YNG1TAS1K0-tomato-signed.zip.
I haven't told that CM has disabled the updates; instead they periodically removes old updates. Files related to YNG1TAS1K0 are directly grabbed from CM server, so they are 100% authentic.
Click to expand...
Click to collapse
thnks bro as being latest update i request you to provide fastboot link direct from cm server old links can be on androidfilehost thats good
thnks for links btw dnlding latest fastboot files now
cheers
What are these bootable image??
I am in twrp recovery with sandy kernel in lollipop 5... Can you please tell how to go back to stock recovery for the updating latest ota. Thanks in advance
Titokhan said:
Reserved for future.
Click to expand...
Click to collapse
hey bro i am on 5.0.2.i want to flash stock kernel can you please tell me which one should i flash ? and which process should i follow ?
using fastboot but what is the command ?
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Titokhan said:
@m_rajaganesh
Depends on the build version; it would be better to install latest stock recovery via fastboot & then flash the full OTA manually.
@ashish_zarekar
Tell me the exact build number. Choose the appropriate one & flash:
Code:
fastboot -i 0x1ebf flash boot boot.img
Click to expand...
Click to collapse
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
ashish_zarekar said:
build number is "LRX22G"
cyanogen os version "12.0-YNG1TAS1K0".
Click to expand...
Click to collapse
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Titokhan said:
Then download cm-12.0-YNG1TAS1K0-tomato-signed-fastboot.zip, extract boot.img from it & flash.
Click to expand...
Click to collapse
can i download direct boot.img from your list and flash it via fastboot ?
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
xdadevelopersrocks said:
When I upgrade Cyanogenmod, I download the matching archive from here:
https://developers.google.com/android/nexus/images#bullhead
and do (with MTC20F for example):
flashboot flash bootloader bootloader-bullhead-bhz10r.img
flashboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
flashboot flash vendor vendor.img
Are there any other files I should be flashing such as boot.img?
Click to expand...
Click to collapse
No. Everything else is contained in the rom zip.
Sent from my Nexus 5X using Tapatalk
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
xdadevelopersrocks said:
OK, is there a better way of figuring out which version to download from developers.google.com than watching the output from TWRP when installing a ROM?
Click to expand...
Click to collapse
The rom dev will inform you which Android base is installed if you read their changelog. Then you download that factory image from Google to flash vendor. Radio and bootloader are optional.
Sent from my Nexus 5X using Tapatalk