I was previously running CM9 but flashed to 2.3.6, factory wiped and unrooted. Since then I have been unable to get the OTA even when force-checkin. Should I not expect it to work since it has been rooted before? I suppose it's not a huge deal but I would love to have OTA 4.1 when available.
I think 4.0.4 has been taken off the server, and as soon as 4.1 is available you will get it as well!
Sent from my Nexus S using Tapatalk 2
I don't understand why everyone is so obsessed with getting an OTA?
You most likely won't be one of the first to get it and as soon as its released someone on here is going to post a better, faster, rooted version anyway... which you'll then flash.
Why not just stick with CM9 instead and wait the day or so it takes for the custom ROM's to flow once OTA hits? Makes SOOOOO much more sense to me?
bryantee said:
I was previously running CM9 but flashed to 2.3.6, factory wiped and unrooted. Since then I have been unable to get the OTA even when force-checkin. Should I not expect it to work since it has been rooted before? I suppose it's not a huge deal but I would love to have OTA 4.1 when available.
Click to expand...
Click to collapse
Flash 4.0.4 factory image
https://developers.google.com/android/nexus/images
here you can find anything you want for 2.3.6 to 4.0.4 http://www.randomphantasmagoria.com/firmware/nexus-s/i9023/
You can check the DEV section which has several OTAs.
You can check the following two:
http://forum.xda-developers.com/showthread.php?t=1569509
http://forum.xda-developers.com/showthread.php?t=1751285
Forget all those links best thread so far
http://forum.xda-developers.com/showthread.php?t=1063664
Click and choose your model! Mine's i9023 btw
Ok so a bit of a follow up:
I unlocked, rooted, flashed recovery and when I go to install CM9 RC1 I'm getting Status 7.
assert failed: getprop("ro.product.device") == "crespo" || getprop("ro.build.product") == "crespo"
E:Error in /......
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
It seems like it thinks it is the wrong ROM for the device but I am positive it is correct as I've flash many crespo ROMs before. Any ideas?
EDIT: OK, so I just re-flashed CWM in ROM manager and it seemed to do the trick.
NYYFan325 said:
I don't understand why everyone is so obsessed with getting an OTA?
You most likely won't be one of the first to get it and as soon as its released someone on here is going to post a better, faster, rooted version anyway... which you'll then flash.
Why not just stick with CM9 instead and wait the day or so it takes for the custom ROM's to flow once OTA hits? Makes SOOOOO much more sense to me?
Click to expand...
Click to collapse
That's what I've been telling everyone. Mere minutes after the OTA is out we'll have something rooted/deodexed and whatnot. *shrugs*
bryantee said:
Ok so a bit of a follow up:
I unlocked, rooted, flashed recovery and when I go to install CM9 RC1 I'm getting Status 7.
It seems like it thinks it is the wrong ROM for the device but I am positive it is correct as I've flash many crespo ROMs before. Any ideas?
EDIT: OK, so I just re-flashed CWM in ROM manager and it seemed to do the trick.
Click to expand...
Click to collapse
OR, you could download the stock images and be done in 5 minutes with fastboot.
Related
Last night (27-3-2012) I had a notification pop up on my stock 4.0.3 (rooted with AIR kernel) Nexus S. It was a notification for an OTA 4.0.4 update. I downloaded it (it was about 17.5 megs) and when I tried to update it, it gave an error saying the package couldn't be verified (or something to that effect). I tried searching the SDcard and system folders for the update but couldn't find one. I tried to go to settings and recheck for update but nothing comes up. My wife has the same phone (a Nexus S) and she didn't get a notification and nothing pops up when I do a check for update. I'd love to find the update file and upload it for you guys but I just can't find the bugger. Anyone have an idea where to look? It was late and I didn't take any screen caps cuz I though Google was finally rolling out ICS 4.0.4 but I can't find anything online about this latest update. Any ideas?
EDIT: This is for GSM Nexus S's, NOT Nexus S 4G. My wife and I each have a GSM Nexus S with T-Mobile.
EDIT 2: See Meisze's post for the link. I'll flash it as soon as it downloads and I'll post some info.
EDIT 2.5: I tried to update but got Status Error 7. I'm going to flash the full 4.0.3 update, then the lite 4.0.4 update and that should work.
EDIT 2.5.5: ok, I get Status Error 7 when i try to flash the full stock 4.0.3 update. I'm going to flash 2.3.6 -> 4.0.3 -> 4.0.4 and see if that works.
EDIT 3: WARNING YOU CAN BRICK YOU'RE PHONE! I bricked mine in the process and just got it working again. I was trying to flash the 4.0.4 lite update and it kept saying Status Error 7. So I restore a backup of the phone from 2.3.6. Without rebooting I then flashed the full 4.0.3 update (ot error 7) and then the lite 4.0.4 (again, no error 7). I reboot and nothing... No Google/lock logo, no recovery, no fastboot nothing. I used Adams tool and get into fastboot. I tried flashing CWM recovery and still nothing.
I fixed it by doing this.
1. Used Adam's toll to get into fastboot. Adam's UnBrickable Resurrector program for Linux http://forum.xda-developers.com/showthread.php?t=1397393 I used Backtrack 5 (Based on Ubuntu)
2. ran fastboot boot recovery.img (Flashed latest CWM touch recovery 5.8.0.2, renamed to recovery.img)
3. In CWM ran the stock 2.3.6 full update
4. Rebooted and everything was back to normal.
5. Went back into CWM, Flashed stock 4.0.3 full
6. Rebooted, everything still fine...
7. Went back to CWM flashed stock 4.0.4 lite
8. Rebooted and everything is working great.
Funny you mention it because I saw this today...
http://www.androidcentral.com/motorola-xoom-wifi-receiving-android-404-update
I found it from miui China : http://www.miui.com/thread-504894-1-1.html
Niiiice!
I flashed it.It is booted now.
To flash it you have to be on 4.0.3. stock unrooted
it is android 4.0.4 IMM76D
baseband I9023XXKI1
kernel 3.0.8-g6656123
so it has a new kernel
browser now works as it should have worked in 4.0.3 now it is fast smooth and no white pages.
Recovery works
same here =)
A.W.E.S.O.M.E !
Sent from my Nexus S using Tapatalk
oops, Iforgot I'm running the 4.0.4 leak. Can't update now.
Sooo if I get back to stock 2.3.6 I will get the 4.0.4 otA?
make pics and post it here! please
need root for that?
thegtfusion said:
Sooo if I get back to stock 2.3.6 I will get the 4.0.4 otA?
Click to expand...
Click to collapse
Not necessarily. The link posted here is only for an upgrade from 4.0.3. No one has posted a link from 2.3.6 so it is possible they are pushing only the upgrade for now. These rollouts take time so you aren't guaranteed a notification until it is fully rolled out.
bozzykid said:
Not necessarily. The link posted here is only for an upgrade from 4.0.3. No one has posted a link from 2.3.6 so it is possible they are pushing only the upgrade for now. These rollouts take time so you aren't guaranteed a notification until it is fully rolled out.
Click to expand...
Click to collapse
Okayy. Did someone already flash it?? Im very scared for flashing ota's in cwm because the 4.0.3 ota hard brickes mine.. i managed to debrick it though
Sent from my Nexus S using xda premium
I flashed it form cwm on i9023. First i flashed the full 4.0.3 then the ota.
It works realy well. It is what the 4.0.3 should have been
faith in google restored
Can I do it for my non-rooted Stock 4.0.3? How? And is this country specific update?
Wont work for me, I get the same error message as the OP, running stock 4.0.3 GSM model.
moon-unit said:
Wont work for me, I get the same error message as the OP, running stock 4.0.3 GSM model.
Click to expand...
Click to collapse
What model do you have? What did you use to flash it?
bozzykid said:
What model do you have? What did you use to flash it?
Click to expand...
Click to collapse
I9020 stock 4.0.3 not rooted and stock recovery
ishkibble said:
I tried to update but got Status Error 7. I'm going to flash the full 4.0.3 update, then the lite 4.0.4 update and that should work.
Click to expand...
Click to collapse
Me too. I think it complained about CRC error on Phonesky.apk.
assert failed: apply_patch_check("/system/app/Phonesky.apk, ...
try to flash the full 4.0.3 update first...
When i updated to 4.0.3 from 2.3.6 my phone could nothandle the diff update.. I had to flash 2.3.6 again after it worked
vick33 said:
try to flash the full 4.0.3 update first...
Click to expand...
Click to collapse
Writes bootloader and radio only. Then I get file_getprop: failed to stat "/system/build.prop": No such file or directory
Edit:
Had to first install the complete 2.3.6, and then the complete 4.0.3, and now the 4.0.4 patch goes through without errors.
This is what I get from Google.
Android System Update 4.0.4
Downloaded and verified .............. 128.6 MB
This system update for your Nexus S brings you the latest version of Android ( 4.0.4 Ice Cream Sandwich ) with performance improvements, increased stability and bug fixes.
I will click install now, it starts installing and then I get the android warning sign and the phone freezs. I have to take the battery out to get it out of the frozen state.
The question is I have rooted my Nexus S 3G. Is it the rooting which is hindering the updating ? Any solutions ?
Help please .
your likley using clockworkmod recovery, to install OTA update you need to use stock recovery,
if your rooted why not install a rooted 4.0.4 rom?
Whoareyou said:
your likley using clockworkmod recovery, to install OTA update you need to use stock recovery,
Click to expand...
Click to collapse
The problem is I followed youtube instruction video to root my phone without a clue of what I was doing. When I get the update notice I get "Install Now " "Install Later" prompt and I select " Install Now " and like I mentioned above it fails and freezes.
215aphilliate said:
if your rooted why not install a rooted 4.0.4 rom?
Click to expand...
Click to collapse
Where do I get that ?
mooz1 said:
Where do I get that ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1399035
Found why the install fails .
Update: It looks like updates on Nexus devices without SD cards can not be performed manually unless you either root or use a custom recovery, like CWM - otherwise, you'll get the errors many of you are seeing. It seems to be happening because the OTA files check whether they're located in /cache, which isn't writable unless you root or receive a proper OTA. JBQ himself confirmed it, but said it wasn't on purpose. The preferred solution seems to be using a custom recovery, then installing the above update. Galaxy Nexus has a similar problem, so you're not alone.
http://www.androidpolice.com/2012/0...or-the-nexus-s-heres-how-to-get-it-right-now/
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Gregsaw said:
I am trying to update my Nexus S i9020a (currently on stock 4.0.4) to stock Jelly Bean, but I'm running into some problems.
First, I got the notification that said there was an OTA update available for 4.1.1, so I started downloading it. After verification, it starting the countdown timer for restarting. When the counter reached 0, my phone did not update, but instead just told me that I was up to date.
I thought that was weird, so I used this thread to download the ota for manual installation. I rebooted into recovery and selected the update. I got the following:
Code:
Verifying current system...
assert failed: apply_patch_space(16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I didn't mind losing my data since I have everything backed up, so I went to this page to download the official images. I followed the instructions to flash the stock bootloader, recovery, and 4.0.4 ROM.
The same thing happened. I got the OTA notification, it downloaded and nothing happened. I tried manual install, but got the Status 7 error.
I then downloaded Google's official Gingerbread image and flashed that. I got a notification for the 4.0.4 update. It installed without any problem. Once that was done, I got another notification for the 4.1.1 update. It didn't work, though. The countdown started, but the phone did not reset and it said the phone was up to date. I tried the manual update again and got another Status 7.
Sorry if this is a bit long, but I wanted to say everything I have tried. I have looked through other threads and they mention using CWM, but I would rather not use a custom recovery. I prefer to stay on stock for now.
Click to expand...
Click to collapse
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
if this helped dont forget to hit that thanks button
Cascabreu said:
First to flash an update u need a custom recovery. if not u will get that error
second dont mind to use a custom recovery bcz after the update your recovery will be back to stock
Click to expand...
Click to collapse
I didn't realize the update wrote over the recovery. Thanks
Gregsaw said:
I didn't realize the update wrote over the recovery. Thanks
Click to expand...
Click to collapse
on any stock rom, at each boot it will overwrite the recovery
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
TheIowaKid said:
So I could use fastboot/adb to install the custom recovery, then install the zip from sd and the phone would be exactly the same as it would be if I were to receive the update notification directly and installed it that way? Should I wipe cache and dalvik in this scenario?
Click to expand...
Click to collapse
yes it's exactly the same, if u want u can wipe cache and dalvik before flashing (that's even recomended from some devs )
Hello , I just purchased the Galaxy Tab 2 7.0 GT-P3113 yesterday to replace an Acer Iconia A100 with a dead EMMC, 4.0.4 ICS is okay but I'm wanting to flash the P3113XARCLI jellybean leak from SamMobile , I'm already on stock UEBLH2 like needed for the leak, not rooted, still running stock recovery. When i get to recovery, i select the zip from my SD, as the zip for the leak is verified in recovery, i hit this error " E: error in /tmp/sideload/package.zip (status 7) , I'm currently downloading the stock firmware, I'm thinking of trying to reflash the stock clean via Odin and then try the leak again, or maybe download the leak OTA zip again, anyone have any suggestions or ideas that might solve the issue? Thanks!
Flashed stock firmware through Odin 3 1.35, Wiped Data and cache in stock recovery, tried to update again, seems to be working, will post again with end result
Nozomi135 said:
Hello , I just purchased the Galaxy Tab 2 7.0 GT-P3113 yesterday to replace an Acer Iconia A100 with a dead EMMC, 4.0.4 ICS is okay but I'm wanting to flash the P3113XARCLI jellybean leak from SamMobile , I'm already on stock UEBLH2 like needed for the leak, not rooted, still running stock recovery. When i get to recovery, i select the zip from my SD, as the zip for the leak is verified in recovery, i hit this error " E: error in /tmp/sideload/package.zip (status 7) , I'm currently downloading the stock firmware, I'm thinking of trying to reflash the stock clean via Odin and then try the leak again, or maybe download the leak OTA zip again, anyone have any suggestions or ideas that might solve the issue? Thanks!
Click to expand...
Click to collapse
Why are you calling these releases "leaks" these are official 4.1.1 OTA and why are you trying to install an older version of 4.1.1 for p3113
The latest OTA is here
http://www.hotfile.com/dl/172673176...UECLI4-OTA-P3113UEBLH2_XAR_374372839.zip.html
DigitalMD said:
Why are you calling these releases "leaks" these are official 4.1.1 OTA and why are you trying to install an older version of 4.1.1 for p3113
The latest OTA is here
http://www.hotfile.com/dl/172673176...UECLI4-OTA-P3113UEBLH2_XAR_374372839.zip.html
Click to expand...
Click to collapse
i've seen a small handful of people using that newer 4.1.1 who haven't gotton past their bootscreens, they're official yes but Samsung hasn't put out a full complete 4.1.1 update as far as i know, these are only test versions
Yes, we don't have an official, but I am on the 3110 UK version, and have had no issues.
Sent from my Rezound using Tapatalk 2
Can't seem to get it to properly connect to my wifi network on the first OTA for some reason
JeramyEggs said:
Yes, we don't have an official, but I am on the 3110 UK version, and have had no issues.
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
So i can flash the UK version via Odin and all should be good? and if i ever need to downgrade i can just revert everything just as i have to test the OTA with the stock P3113 firmware right?
Yes, flash thru Odin, use cf root to root, then flash clockworkmod thru odin. At that point, make a backup. At that point, you can flash any mods, or other ROMs, and return to the stock jellybean experience. Yes, I haven't had any problems with the ir blaster, or any problem. If you don't like it, Odin back to ICS, or a custom ROM thru CWM. The main point is to read, reread, research, and ask questions. As long as you do your homework, you will have no problems.
Sent from my Rezound using Tapatalk 2
JeramyEggs said:
Yes, flash thru Odin, use cf root to root, then flash clockworkmod thru odin. At that point, make a backup. At that point, you can flash any mods, or other ROMs, and return to the stock jellybean experience. Yes, I haven't had any problems with the ir blaster, or any problem. If you don't like it, Odin back to ICS, or a custom ROM thru CWM. The main point is to read, reread, research, and ask questions. As long as you do your homework, you will have no problems.
Sent from my Rezound using Tapatalk 2
Click to expand...
Click to collapse
Thank you! Running the UK 4.1.1, pretty nice so far, gonna go through with rooting and custom recovery in a bit, appreciate your help! Have a happy new year!
FOTA ripped for your enjoyment.
https://mega.co.nz/#!xoZigSqS!YHUa5Umv-8qjyFV1dtHs4lDQXMIn1q7plTz3zWeYSwY
That's completely unmodified. (I tried just installing it in CWM. Think I probably bricked doing something silly...)
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
gee one said:
I pulled this as well, but I'm curious if you had to flash back to stock firmware and recovery to get it. I tried using a rooted stock rom and the software update screen would give me a "modified devices don't get updates" message. I actually had to have stock recovery and system installed so that it would download. Did you have to do the same thing?
Click to expand...
Click to collapse
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
bigleague4040 said:
Interestingly enough, it downloaded perfectly fine for me, even though my device was "modified"...
Click to expand...
Click to collapse
I have a modified boot.img- perhaps that blocks the ota?
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
gee one said:
I played around with this a while ago (my flash counter is at 29 last time I checked).
I think you have a few options:
1) maybe unroot and that might remove the modified status
2) use heimdall or odin to flash back to unrooted stock, including stock recovery and boot.img
3) flash one of the rooted JB roms, either stock, cyanogen, or our very own Teamapexq rom
4) download the OTA or the JB rom from the web and repackage it yourself to a flashable zip.
Option 1 might not work. Option 2-4 will work, 4 would be the most fun.
sent while running with scissors
Click to expand...
Click to collapse
OMG, I would like to do it with no hassle.
I just want something to work ... grrr.
Option 2 would probably be the most straightforward. Essentially, you are unrooting. I just remembered, Samsung has Kies which might restore it to stock. You can download it from their website.
sent while running with scissors
mazak23 said:
My device is rooted.
It is on 4.2.1 genuine T-mobile software.
When I want to update OverTheAir this message pop out.
See attachement (I don't know how to put image here).
What can I do to update OTA?
Click to expand...
Click to collapse
the update in this thread is only about JB 4.1.2 that is officially the latest and the last one for our mobile. your message box is normal, there is no need for the usage of the OTA anymore since then. if u want to update to JB 4.3 follow this unofficial image:
http://forum.xda-developers.com/showthread.php?t=2463661
Holy thread resurrection Batman!!!
Oh boy. Here we go. Having troubles here.
I am trying to re-flash my phone to stock so I can return it under the protection plan. I firmly believe my radio might be on the fritz.
Anyway, I used the directions here:
http://theunlockr.com/2013/04/25/how-to-unroot-the-samsung-galaxy-s-relay-4g-sgh-t699/
Now it all completed successfully, and the phone is chilling at the SAMSUNG screen trying to boot. Not sure what to do at this point. Its been sitting there for a good 5 minutes.
Please help!!
UPDATE: Went into stock recovery, cleared Cache and Data, then rebooted it again, and it booted!
Which JelyBean Version...!!!
After installing this update what will be my os (JB 4.X.X) version???
saurabhsaurabhrai said:
After installing this update what will be my os (JB 4.X.X) version???
Click to expand...
Click to collapse
it is just from stock, will be updated to JB 4.1.2