Related
Yes here it is the nexus s official android 4.0.4 from google
this needs to be flashed over the stock 4.0.3 official rom from google it's a 17.8 mb update not a full rom so you can only flash it over stock 4.0.3 i repeat only over stock or else it will fail.
i managed to get the download link from google servers here it is http://android.clients.google.com/packages/ota/google_crespo/hR7QFEtn.zip as you can see an official google link.
so far i noticed that the recovery is fixed (no longer disappear on i9023 devices)
and battery problems solved too.
ONLY FLASHABLE VIA CWM
the reason is here:http://forum.xda-developers.com/showpost.php?p=24198556
Is it worth going back to stock 4.0.3 and update to 4.0.4?
I am rooted running Codename Android 1.5.5 and Air Kernel 3.7. Pretty happy with that set up. Very smooth and stable and decent battery life (20+ hrs).
I love the tweaks and mods included in CNA. Is it worth it not having them?
bjornvil said:
Is it worth going back to stock 4.0.3 and update to 4.0.4?
I am rooted running Codename Android 1.5.5 and Air Kernel 3.7. Pretty happy with that set up. Very smooth and stable and decent battery life (20+ hrs).
I love the tweaks and mods included in CNA. Is it worth it not having them?
Click to expand...
Click to collapse
Hmm of course it does not have the tweak of custom roms,but if you want a stock experience this is way better than 4.0.3 lots of issue fixed,it's smoother now and battery issues all gone plus the recovery now works again on i9023 devices.
Getting a Status 7 error trying to apply this update to a stock unrooted GSM Nexus S. Hmm...
guys how i should istall it on my nexus s i9023 if i can't use my recovery? mmm i have 4.0.3 stock
glider010 said:
guys how i should istall it on my nexus s i9023 if i can't use my recovery? mmm i have 4.0.3 stock
Click to expand...
Click to collapse
is your bootloader unlocked ?
if it's unlocked use fastboot to boot clockworkmod recovery and flash from there.
ezhangin said:
Getting a Status 7 error trying to apply this update to a stock unrooted GSM Nexus S. Hmm...
Click to expand...
Click to collapse
you must be completely stock,no stock kernel or modified system apps or files,you can try flashing the 4.0.3 rom,even if you are unrooted with a modified stock system it will not work.
m.sabra said:
you must be completely stock,no stock kernel or modified system apps or files,you can try flashing the 4.0.3 rom,even if you are unrooted with a modified stock system it will not work.
Click to expand...
Click to collapse
Totally stock.
m.sabra said:
is your bootloader unlocked ?
if it's unlocked use fastboot to boot clockworkmod recovery and flash from there.
Click to expand...
Click to collapse
no, damn it....other solution?
how does one with a 9020a do this? I dont have a stock 4.0.3. Any ideas??
Much better if you all wait for the devs to handle this.
Sent from my Nexus S
ezhangin said:
Totally stock.
Click to expand...
Click to collapse
Same here.
I've done data/factory reset + wipe cache partition,
full install (IML74K) 4.0.3 (on wich I was already running),
data/factory reset + wipe cache partition,
full install 4.0.4 using the provided link...
> error 7
csrxds said:
Same here.
I've done data/factory reset + wipe cache partition,
full install (IML74K) 4.0.3 (on wich I was already running),
data/factory reset + wipe cache partition,
full install 4.0.4 using the provided link...
> error 7
Click to expand...
Click to collapse
I'm pretty sure that this is only an incremental upgrade and not a full rom so its not going to work if you wipe everything. Its under 20 megs so
Sent from my Nexus S using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1569061
tycruickshank said:
I'm pretty sure that this is only an incremental upgrade and not a full rom so its not going to work if you wipe everything. Its under 20 megs so
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I only wiped user datas, not system.
I've been trying to apply it without any wipe before with the same result.
I will maybe try to go back to 2.3.6 then apply only the 4.0.3 update from 2.3.6 (not the full package) and then the package provided but I have to go back home to unlock the phone and load cwm reocvery to revert back to 2.3.6.
OP can you tell us if you came from full 4.0.3 update on only the update from 2.3.6, if you got the update over the air or if you flashed it manualy and also if you are using stock recovery.
Thank you
EDIT : [Q] GSM Nexus S ICS 4.0.4 OTA update released? OP has also Status Error 7 and is trying what I was up to do...
EDIT 2 : http://forum.xda-developers.com/showthread.php?p=24145247#post24145247 It seems to be the trick, can't wait to go back home...
blackhemi4x4 said:
how does one with a 9020a do this? I dont have a stock 4.0.3. Any ideas??
Click to expand...
Click to collapse
sorry this is the official update that only works on I9020T and I9023 (the devices who got 4.0.3 earlier, you should wait for the full release)
glider010 said:
no, damn it....other solution?
Click to expand...
Click to collapse
you can access the stock recovery,it's just the backlight is very low so blind clicks are still possible,in direct sunlight at some angle you can see the menus (press power + vol up inside recovery for the menus to appear)
I'm having the error Status 7 too.
It seems that the complete rom package 4.0.3 is a little different than upgrading from 2.3.6 to 4.0.3. Now I'm downloading the 2.3.6 complete rom and upgrading from this.
csrxds said:
http://forum.xda-developers.com/showthread.php?t=1569061
I only wiped user datas, not system.
I've been trying to apply it without any wipe before with the same result.
I will maybe try to go back to 2.3.6 then apply only the 4.0.3 update from 2.3.6 (not the full package) and then the package provided but I have to go back home to unlock the phone and load cwm reocvery to revert back to 2.3.6.
OP can you tell us if you came from full 4.0.3 update on only the update from 2.3.6, if you got the update over the air or if you flashed it manualy and also if you are using stock recovery.
Thank you
EDIT : [Q] GSM Nexus S ICS 4.0.4 OTA update released? OP has also Status Error 7 and is trying what I was up to do...
Click to expand...
Click to collapse
okay i was coming from the 2.3.6 update package only,completely stock and unrooted,i flashed using cwm since my recovery is broken (am on i9023) and the device passed current system verification successfully.
m.sabra said:
okay i was coming from the 2.3.6 update package only,completely stock and unrooted,i flashed using cwm since my recovery is broken (am on i9023) and the device passed current system verification successfully.
Click to expand...
Click to collapse
Okay. Thanks!
Now we just have to see if coming from 2.3.6 and only using small update packages is the trick or if it's using cmw recovery that makes the update process working.
I'll try with stock recovery and A BIG TORCHLIGHT coming from 2.3.6 to find it out.
IMHO, I'd wait for source release of 4.0.5 (or 4.0.4), whatever is first.
what worked for me:
- full wipe (that means everything except sd-card)
- install 4.0.3 full-rom
- install 4.0.4 ota
since my bootloader is unlocked, i deleted the recovery-dir from both zips before flashing (i prefer cwm).
I've flashed the 4.0.3 OTA, after that this update too. Flashed superuser, currently restoring my apps with titanium, but no trouble so far. Data, wifi working, no FCs, report back later. (oh, and i have i9023)
Caution: I have tried this method with my S3 and successfully flash back to old bootloader XXALEF. But we always have to be careful when flash bootloader. According to sammobile, Samsung updated new bootloader to fix suddend death error of S3. Every update of the manufacture should be better. So I don't advise you to downgrade bootloader back to previous version. JUST ALWAY FLASH AS OUR OWN RISK !
And If you try and successfully please report here and let me know if it works 100% on another S3.
Hey guys,
After flashed stock XXELLA rom or flash new XXELLA bootloader. You can't not flash back to old previous version of bootloader anymore via PC Odin. And after every S3 reboot, it will show red exclamation mark at boot logo and always check flash counter =1 in download mode if you user custom kernel or custom CWM. This is 3 method to flash back to old bootloader:
>>> METHOD 1: You can use Sboot Checker to check which bootloader is backlisted. Then use some basic terminal commands to downgrade your bootloader. This is more simple and safer. Please visit @Odia's topic http://forum.xda-developers.com/showthread.php?t=2081748. Credit to him.
>>> METHOD 2: This is the most simple and fast method for lazy guys ! Just download the following .zip file and flash via CWM Recovery. You will be restored to old ICS bootloader XXBLFB. This is download link http://forum.xda-developers.com/showpost.php?p=36433966&postcount=105. Credit to @fbatti73 he has ported @Odia's command to CWM flashable zip file. So many thanks to @fbatti73 and @Odia.
>>> METHOD 3: This is the first method I've found but far too much work involved and take alot of time. But if you like this' also another choosing:
1. Always backup first, full wipe yor S3 and flash back to lastest stock ICS 4.0.4 rom not included old bootloader in it or you can fash via Mobile Odin and don't care it include a bootloader or not because Mobile Odin doesn't flash bootloader. I''m in Vietnam and I choose this ICS 4.0.4 rom I9300XXBLH1_I9300OLBBLH1_XEV.zip http://www.hotfile.com/dl/166926386/6a0e52a/I9300XXBLH1_I9300OLBBLH1_XEV.zip.html
2. After flashed ICS 4.04 rom don't root or do another work on it, Just check OTA update on S3 by Go to Settings > About device > Software update > Click Update. Let OTA update your S3 to JB 4.1.1. In my case the OTA will update to JB 4.1.1 XXDLJ1 and it takes about 2xx MB size. Yes, it's here. The processing of OTA update from ICS 4.0.4 to JB 4.1.1 can break the protect of new bootloader XXELLA . And after OTA updated to JB 4.1.1 you would have the old version of JB 4.1.1 bootloader. In my case it's bootloader XXDLJ1.
3. But although our S3 has old bootloader XXDLJ1 but it's still a JB bootloader version. Every S3 reboot you will still get red exclamation mark and counter =1 if you use custom kernel or custom CWM. To make red exlamation mark and counter =1 disappear totally. You only have to flash back to old ICS version bootloader XXALEF. And now you can flash back to XXALEF bootloader via PC Odin.
4. Just install a custom kernel and a custom CWM Recovery. Wa wa, red exclamation mark and counter =1 have already dissapeared totally.
This is the link of ICS old bootloader XXALEF can flash via Odin: http://www.mediafire.com/?dlruvz9fib6c046
>>> Many thanks to XDA members of the following threads. Yours'' replys helped me accidental found this way )
http://forum.xda-developers.com/showthread.php?t=2077844
http://forum.xda-developers.com/showthread.php?t=1918667
http://forum.xda-developers.com/showthread.php?t=1993044
http://forum.xda-developers.com/showthread.php?t=1646610
Dr.Love said:
Hey guys,
After flashed stock XXELLA rom or flash new XXELLA bootloader. You can't not flash back to old previous version of bootloader anymore. And after every S3 reboot, it will show red exlamation mark at boot logo and always check flash counter =1 in download mode if you user custom kernel or custom CWM. This is the way I found to flashed back to old bootloader.
1. Flash back to lastest stock ICS 4.0.4 rom not included old bootloader in it. I''m in Vietnam and I choose this rom I9300XXBLH1_I9300OLBBLH1_XEV.zip http://www.hotfile.com/dl/166926386/6a0e52a/I9300XXBLH1_I9300OLBBLH1_XEV.zip.html
2. After flashed ICS 4.04 rom. You let OTA update check and let OTA update your S3 to JB 4.1.1. In my case the OTA will update to JB 4.1.1 XXDLJ1. Yes, it's here. The processing of OTA update from ICS 4.0.4 to JB 4.1.1 can break the protect of new bootloader XXELLA . And after OTA updated to JB 4.1.1 you would have the old version of JB 4.1.1 bootloader. In my case it''s bootloader XXDLJ1.
3. But although our S3 has old bootloader XXDLJ1 but it''s still a JB bootloader version. Every S3 reboot you will still get red exlamation mark and counter =1 if you use custom kernel or custom CWM.
4. To make red exlamation mark and counter =1 disappear totally. You only have to flash back to old ICS version bootloader XXALEF. And now you can flash back to XXALEF bootloader via Odin.
5. Just install a custom kernel and a custom CWM Recovery. Wa wa, red exlamation mark and counter =1 have already dissapered totally.
This is the link of ICS old bootloader XXALEF can flash via Odin: http://www.mediafire.com/?dlruvz9fib6c046
>>> Many thanks to XDA members of the following threads. Yours'' replys helped me accidental found this way )
http://forum.xda-developers.com/showthread.php?t=2077844
http://forum.xda-developers.com/showthread.php?t=1918667
http://forum.xda-developers.com/showthread.php?t=1993044
http://forum.xda-developers.com/showthread.php?t=1646610
Click to expand...
Click to collapse
Did you even tried it or you need other members to beta test it 4 u,post a video of u making this ACTUALLY work !
Dr Love. In the OTA step- how much is the size of 4.1.1 ?
Pretty nice, will give it a try on the S3 of my mom
nhariamine said:
Did you even tried it or you need other members to beta test it 4 u,post a video of u making this ACTUALLY work !
Click to expand...
Click to collapse
Oh, I have tried it with my S3 and successfully flash back to old bootloader. Sorry, I can't make a video. I will add caution in post 1 because always have to be carefully when flash bootloader. You can try as your own risk.
thekoRngear said:
Dr Love. In the OTA step- how much is the size of 4.1.1 ?
Click to expand...
Click to collapse
About 2xx MB.
sangosnip69 said:
Pretty nice, will give it a try on the S3 of my mom
Click to expand...
Click to collapse
I'm downloading everything I need, I'll get a try and come back later to tell you if it's work with French Firmware.
Why there is red mark when phone boot? I'm running CM10.1 I got afraid because of that.
Sent from my GT-I9300 using xda app-developers app
how the new bootloader looks like ?
eranda84 said:
Why there is red mark when phone boot? I'm running CM10.1 I got afraid because of that.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It appear because you use custom kernel or custom CWM with new bootloader.
F.M.K said:
how the new bootloader looks like ?
Click to expand...
Click to collapse
Go to google play, find app Android System Info. Install and run it you will see current version of your S3's bootloader in System Tab.
SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!
Bootloader changed to XXDLJ1.
Update: Changed to ICS XXALEF.
Thanks a lot!!!
The trick is to download a full fledged ICS firmware of a country that yet no been updated to 4.1.2. After flash, let the OTA update according to that or any country that has not been updated to JB 4.1.2. I downloaded OP's Vietnamese firmware and flashed but chosen India on OTA update. It's a 285.07 MB file.
Voila you are done. The OTA does the trick.
thank you for the information, I'll try
If I flash old nandroid backup from ics, would it flash old bootloader?
Sent from a better Galaxy designed for humans!
zadusimple said:
If I flash old nandroid backup from ics, would it flash old bootloader?
Sent from a better Galaxy designed for humans!
Click to expand...
Click to collapse
no
thekoRngear said:
SUCCESS!!!!!!!!!!!!!!!!!!!!!!!!
Bootloader changed to XXDLJ1.
Update: Changed to ICS XXALEF.
Thanks a lot!!!
The trick is to download a full fledged firmware of a country that yet no been updated to 4.1.2. After flash, let the OTA update according to that or any country that has not been updated to JB 4.1.2. I downloaded OP's vietnamese firmware but in the SW settings chose India.
Voila you are done. The OTA does the trick.
Click to expand...
Click to collapse
thanks have you used mobile odin?thanks for reply
uberto.costanzo said:
thanks have you used mobile odin?thanks for reply
Click to expand...
Click to collapse
It will work with kies?
uberto.costanzo said:
thanks have you used mobile odin?thanks for reply
Click to expand...
Click to collapse
Nope.
Done with PC Odin.
thekoRngear said:
Nope.
Done with PC Odin.
Click to expand...
Click to collapse
and factory reset after flash or before? thanks
uberto.costanzo said:
and factory reset after flash or before? thanks
Click to expand...
Click to collapse
Hmm..just before I flashed the full firmware I had fully wiped device with cwm recovery.
uberto.costanzo said:
and factory reset after flash or before? thanks
Click to expand...
Click to collapse
Before
Hi, im using cwm recovery v5.5.0.4 and i tried to go from cm7 android 2.3 to cm10.2 android 4.3. Flashing the rom wouldn't make any change and i got an error which i searched on it and found out that i has to be on ics stock to flash any ics custom. I downloaded from huawei site the ics original and tried to force upgrade, when in step 2 i got an error -> Update failed. Then i tried to force upgrade to 2.3 orginal gb and got the same issue. Now im actually trying to boot in device and flash my old rom of gb custom cm7 but after update completion im stuck on recovery. Any ideas? Its immerse to fix it.. TY
Do you have u8800 or u8800pro?
Sent from my U8800, powered by CM 10.1
b.watson said:
Do you have u8800 or u8800pro?
Sent from my U8800, powered by CM 10.1
Click to expand...
Click to collapse
its pro
Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat
rahulpillai said:
Hi
I had a Motorola Defy mb525.
Bricked the phone while trying to install CM9
Got it alive somehow by Flashing it with .sbf
Now my phone shows as mb526 and I was able to root it again.
System Version - 45.0.231.mb526.AsiaRetail.en.03
Version - 2.3.6
Kernel - 2.6.32.9-ge281b6e [email protected] #1
The problem now is I am not able to flash any of the Custom ROM's.
Tried CM10, Cm9 and also the latest kitkat
Downloaded different ones for each ROM's.
I get the message when i try to update from SDcard "Signature verification failed"
If someone could help me in Upgrading to JellyBean or Kitkat
Click to expand...
Click to collapse
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk
Feel like a real dumb person now, I did not install Sndinit
hotdog125 said:
Are you sure you are using custom recovery?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update
Still no Luck
rahulpillai said:
Feel like a real dumb person now, I did not install Sndinit
Now I am in the Custom Recovery menu
Backing up my current ROM
Will try to flash Kit Kat and update
Click to expand...
Click to collapse
Tried Kit Kat, still same
Tried CM10 twice, installs but when I reboot it gets Stuck on startup "Startup has encoutered an error" something like that
No matter what language I select still same
Any Inputs
For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk
CM10.2 works but Kit Kat Still not installing
hotdog125 said:
For KitKat you need to flash an updated recovery. Check the thread.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
CM10.2 works after installing gapps but Kit Kat Still not installing
I updated the recovery as well
My phone was bricked when I was installing Kit Kat
It stopped at Step 7
I had to flash the stock SBF to get it alive again
Will wait for updates to the kit kat mod
CM10.2 works but really slow
Its been a very long time since I've had to dig this deep into flashing and I've always been a Samsung user so I'm somewhat use to the less difficult route. I'm running the 4.4.4 mokee ROM with the kitkat boot loader. Im trying to get miui running on my phone. The miui ROM is on 4.2.2 and I'm guessing requires a JB bootloader to flash. So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery? Honestly I'm trying to get back for stability also. Unless someone knows where a KitKat miui ROM is for our phone? Other than the "V6" tablet ui ROM. It isn't no where stable enough.
brd912 said:
Its been a very long time since I've had to dig this deep into flashing and I've always been a Samsung user so I'm somewhat use to the less difficult route. I'm running the 4.4.4 mokee ROM with the kitkat boot loader. Im trying to get miui running on my phone. The miui ROM is on 4.2.2 and I'm guessing requires a JB bootloader to flash. So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery? Honestly I'm trying to get back for stability also. Unless someone knows where a KitKat miui ROM is for our phone? Other than the "V6" tablet ui ROM. It isn't no where stable enough.
Click to expand...
Click to collapse
simplest route for you: install rsdlite, flash stock 4.4.2 which will upgrade you to kk bootloader. then install supersu from play store, then towelroot and root your phone. thereafter, use motocalypse to unlock bootloader.
after that you are free to pick and choose which rom you want to install. if you wish to install a jb rom, you will have to downgrade to jb bootloader. otherwise, you're free to install your favorite recovery followed by your favorite kk rom while still on the kk bootloader
brd912 said:
So my question is, is there a pre-rooted rsd package to get back to 4.2.2 so I can flash miui or do I have to flash back to stock, re-root and re-flash a custom recovery?
Click to expand...
Click to collapse
You don't have to be rooted to flash custom recoveries, so just downgrade to stock 4.1.2 (there was no 4.2) and then flash a custom recovery for the old bootloader.
You could also try this
http://www.droidrzr.com/index.php?/topic/50096-[How-To][Mobile-Downgrader]-Flash-Back-1.0-(07-15-14)#entry448942
thewraith420 said:
You could also try this
http://www.droidrzr.com/index.php?/topic/50096-[How-To][Mobile-Downgrader]-Flash-Back-1.0-(07-15-14)#entry448942
Click to expand...
Click to collapse
I flashed the JB file but it failed to flash a 4.2.2 ROM...since it flashes back to 4.1.2 would I have to flash a 4.1.2 based ROM and then flash a 4.2.2 rom?
brd912 said:
I flashed the JB file but it failed to flash a 4.2.2 ROM...since it flashes back to 4.1.2 would I have to flash a 4.1.2 based ROM and then flash a 4.2.2 rom?
Click to expand...
Click to collapse
If meant for 4.1.2 kernel then use flash back 4.1.2 then when recovery reboots flash the 4.1.2bl rom. Which 4.2.2 ROM are you trying?
We cannot teach people anything; we can only help them discover it within themselves.
ezknives said:
If meant for 4.1.2 kernel then use flash back 4.1.2 then when recovery reboots flash the 4.1.2bl rom. Which 4.2.2 ROM are you trying?
We cannot teach people anything; we can only help them discover it within themselves.
Click to expand...
Click to collapse
Miui. I'm gonna try the 4.1.2 miui and then after it boots see if it will flash the 4.2.2 ROM.
I can't get any jb ROM to flash using the flashback zip... I guess rsd it is