Hello guys,
I have a nexus S and I received a minor update which updated my phone to 2.3.2(build GRH78C). I recently downloaded the update files for 2.3.3 but I am having a error while updating as my version is 2.3.2 and the update files are to update the 2.3.1 version(update from GRH78, I presume). I tried a lot but I am unable to find a way (without rooting the phone). Can you please let me know if you have any ideas?
Your help would be highly appreciated.
Adi
GRH78C to 2.3.3
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
No root required. Download, rename to update.zip.
Put it on your /sdcard/
Boot into recovery
Flash update
Reboot
Done.
Thanks
It worked...!!!!
Related
Hi There!
A few months ago I've installed clockworkmod 3.2.0.0, in a failed attempt to upgrade my MZ604 UK Xoom to ICS from 3.2.
I forgot about this device for a while. Today I received the OTA update for ICS. But after downloading, and when it rebooted, it entered into the recovery of clockworkmod.
I really don't know what to do. I tried to just reboot and think that it would bypass, but after starting it shuts down into recovery. Tried to shutdown, same problem
I now have a device that only reboots
Could someone help me how to apply the google official update?
REgards
flash stock xoom images and then waite for ics update
here's official image link
http://forum.xda-developers.com/showthread.php?t=1049485
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
smoke1 said:
Hi Here I have a BIG problem with understanding whats going on. This is forth week how i'm trying to push update for GB 2.3.1.
a little story:
I had ICS based MIUI rom installed for around 1.5 year and was extremely happy with its UI and performance and regular weekly updates - since it become more and more lagy after every update. my phone was to week for its software and I decided go back stock.
My phones current details
nexus S
gingerbred 2.3.1
baseband : I9020XXKB3 (under battery GT-I9020T)
kernel : 2.6.35.7-g7f1638a
[email protected]#1
build number : GRH78
So what I done next i downloaded Odin and flashed stock gb 2.3.1 and now i can not update it in any way. System tryes to push OTA 4.0.1 but it ends up with following
______________________________
ClockworkMod Recovery v6.0.1.0
Finding update...
Opening update package..
Verifying update package..
E:failed to verify whole-file signature
E:signature verification failed
installing update...
Verifying current system...
assert failed: apply_patch_check("MTD:radio:12583040:a32c1a32c13af21c32fa13af2c13a2f1a32fc12f31c2a3f1")
E:Error in /chache/odDgDain.zip
(status7)
Installation aborted
_________________________________
when i Rooted it i also noticed my outdated SU binary version 2.3.1 -ef
it also fails on update.
yesterday i tried to flash glados kernel through ROM manager and the phone crashed.
I have tried coupe different radios as well but ota update wont install Even with 'ota surviva'l and 'temp unroot' ticked in SuperUser
What should I do?
what causing all this?
should i install a different kernel or different gb version rom? In this case can U refer links pleas as Im TOTTALY LOST HERE guys
Thanx
Click to expand...
Click to collapse
It's normal you can't flash OTA because you have a custom recovery. You need stock recovery for that. You can download a factory image from Google, extract it and flash the recovery inside using fastboot.
https://developers.google.com/android/nexus/images#soju
ALSO, stop using Odin. There's no need to use Odin or nearly on Nexus S. This thing is nearly unbreakable and you have more chances of breaking stuff with Odin than anything else.
thanx for quick replay
flashed factory GB 2.3.6 straight away using sdk tools
now will root it and install custom clockwork recovery to prevent from automatic OTA updating to lagy ICS
Use FOTAKill instead,
http://forum.xda-developers.com/showthread.php?t=1579154
Thanx for good advice. Installed it allready.
Sent from my Nexus S using xda premium
When i update my nexus 5 to the new 5.0 android it installs until the half and then it shows
An error... ''system/app/GoogleIME.apk has unexpected contents'' .....my recovery and kernel
(i'm not sure about kernel)are stock.I have rooted before with towelroot and now i can root back.I have tried moving out the files from the system but again the same things....i dont want to flash custom images to my phone....i will apreciate your help
I have exactly same problem with Cube Talk 9X (U65GT) tablet when I try to update via OTA. I can download update and start installing but it gives me always error.
Code:
system/app/LatinIME.apk has unexpect contents
Update.zip is not correct
I'm on stock rom and not rooted. Did you ever solve your problem?
Hello guys,
I am running on STOCK Cyanogen OS 12 on Android 5.0.2 on my YU Yuphoria. I have rooted my device and I have TWRP installed. SO it all started when I messed around with the build.prop file. I did not take the backup of the file and I went forward with changing the Android Version of my phone to "6.0" And guess what, now I'm in an endless bootloop. I require a zip file of the build.prop which could be flashed via TWRP. Also, I do not want to loose ANY data. I am really worried about this and I'd be glad if anyone out there could help me with the "FLASHABLE ZIP" of "build.prop" that I could flash via TWRP recovery.
Please reply as soon as possible.
Writing with GREATEST of hopes.
Thanks in advance,
Akshat
Hello everyone!
I am newbie there so If I did something wrong then I am sorry.
I have a big problem so I so need your help (in sos?).
I am trying install back EMUI 3.1 cause 3.1 was faster and power saver than 4.0.3 so I would to install back 3.1.
I found a zip file which is contain update.app. It has been downloaded from huawei's site (c1.huawei.com). So maybe it is an offical package
I am trying install EMUI 3.1 since yesterday.. But I always got an error (Software install failed). If I install an rollback android 6 to 5 then my recovery is dies. I did everything I saw on xda and other forums.. My phone is unrooted, bootloader is unlocked everything.. I so need EMUI 3.1. :crying: Please a helpful person.
Thanks,
Balázs.
Solved
I hopefully solved the problem. Solution: Extract img files from .UPDATE app and flash it with fastboot.
You need flash boot recovery system and cui (or what is that) img with fastboot.
Now my problem is I do not have IMEI on 3.1 but on custom 4.0.3 rom I have that. So my SIM card is not reading I can't connect to network. Anyone can help me in SOS?