Database Info

[Q] Nexus S i9020T Cannot Upgrade above 2.3.3

Very strange issue.
I cannot upgrade my ROM above 2.3.3 and I can't upgrade the Recovery Image to anything new as well.
Does not matter if Official ROM or Not.
I am grabbing the Official ROMs from here:
http://forum.xda-developers.com/showthread.php?t=1445570
I am currently with Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader
and If I try to install, 2.3.4, 2.3.6, or 4.03 the phone wont get past the "Google Logo" right from the beginning of boot. The screen will go Blank and the 4 soft keys will light up.
Before installing each ROM I am formatting/wiping cache, data, system & dalvik.
And Each ROM installation will claim that it installed successfully.
Recovery: So I am able to install ClockWork Recovery 3.0.2.4 and have it work.
I install the latest Clockwork ver. 5.0.2.0 it will install successfully, but not work.
And stop right after the Google Logo, as with ROM.
I have been at this for 2 days now. Any help would be AMAZING!!!
One last note: The phone was dropped, so maybe some how related, but I don't see how. The phone just came back from store that replaced the LCD. They claimed it was in a Recovery Loop. So I asked them to put CynogenMod. However they strangely put CynogenMod v 2.3.1 and not rooted.

are you flashing the right cwm recovery 5.x.x.x for your phone(amoled vs lcd)? try twrp recovery. do you wipe data(factory reset)before flashing? you should.

to Start, Thank you for the reply. Its very much appreciated.
So Yes, I am performing a full factory reset before flashing. And all of my most recent trials I used the native factory recovery that comes with each of the ROM's.
And I tried all of the below listed ROMs with the issue as described abouve.
Android 2.3.4/GRJ22/XXKD1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 2.3.6/GRK39F/XXKF1 Radio/KA3 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
Android 4.0.3/IML74K/XXKI1 Radio/KL1 Bootloader
Official, signed, can flash with ClockworkMod or stock recovery. Contains recovery, radio and bootloader.
And regards to the Custom Recovery(cwm) issue, I used what on the CynogenMod Wiki:
wiki(dot)cyanogenmod(dot)com/wiki/Nexus_S:_Full_Update_Guide
They don't have any differenciation between the OMOLED or Super LCD Versions:
(OMOLED I9020T, I9020A)
(Super LCD I9023)
Is there in fact different Recovery's for each of the abouve listed models????
Where would I find those recoverys?
And thank you again for your time.

Help - anyone? - Please :-(

vringo said:
Help - anyone? - Please :-(
Click to expand...
Click to collapse
try using twrp recovery, i find it more useful than clockwork recovery http://teamw.in/project/twrp2
---------- Post added at 04:26 PM ---------- Previous post was at 04:18 PM ----------
if you want to flash the official 4.0.3, then you need to flash the official 2.3.6 first. if youre flashing a custom 4.0.3, like cm9, then you dont need 2.3.6.

Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?

vringo said:
Thank you for the TWRP recovery suggestion.
But still stuck without being able to flash anything above 2.3.3
Should I be able to flash official 2.3.6 on top of 2.3.3(after factory reset)?
Click to expand...
Click to collapse
you should be able to. try a custom rom instead of an official. lots of aosp builds in the development section. they are pretty much pure android with a few mods. theres a pure aosp build in the development section too, its pure android 4.0.3 without mods. your bootloader is unlocked, right?

Yes, bootloader is unlocked.
will give some of the aosp builds a try now

vringo said:
Yes, bootloader is unlocked.
will give some of the aosp builds a try now
Click to expand...
Click to collapse
good luck

This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)

vringo said:
This phone is messed up. while I was in 2.3.3, the whites began to turn purple, flickering. Ugh :-(
TWRP recover, no go
I just tried codename_aosp+_crespo-ota-eng.V3.0.2, also no go
I'm beginning to suspect its a hardware issue, or maybe something else it just messed up?
perhaps flashed a wrong component somewhere???
Is it possible to reformat all internal flash drives and reparation and truly start from scratch? with all aspects of this device?
(like on a pc, low level format the hard disk and start all over....)
Click to expand...
Click to collapse
One more thing, anyway to know if the store that fixed my phone installed the wrong screen? LCD vs OMOLED?

clarification of the "issue" if ROM not working.
- Working phone (with 2.3.3) boot description:
You see Google Logo, and then the Logo will flicker momentarily, and Google Logo some more, and then the flying colored NEXUS logo animation, etc...
- Non functioning ROM boot description: You see the Google Logo, and then at about the time you would see the Google Logo flicker, that is when the screen goes black, and all 4 soft-keys light up. if you push the power button, sometimes the soft-keys will go black, and if you push again, light up again. At this point I have to pull the battery....
Same issue if I try to load the stock recovery from a non-functioning ROM. so Fastboot Mode will work, and then select Recovery, Google logo and then Black, with 4 lit softkeys, where the logo would normally flicker.

Why can't I install the stock firmware above 2.3.3????
I just tried the update ROM from 2.3.3 to 2.3.4 or 2.3.3 to 2.3.6 (all GRI40)
What could cause this issue????
could it be a partioning issue? what would cause such a weird issue?

[Q] I9003 bricked

Can someone help me....(sorry for my bad english) today i traid to flash [ROM][LF2][15.10.2012]TheFrankenstain^MODv.3.8 #1 after that it was keep loading at the" android" logo so i tried to flash it again...but now it is stuck at the samsung logo and volume up + lock+ home (recovery) now work anymore
Did someone know how i can flash it again without recovery?
PLSSS HELP

-Removed for Personal Information-

i think it is not bricked, it is just a bootloop. check if your downloaded rom is complete. beter redownload the rom and flash it. follow the instructions on flashing on that thread and you will have no problem. flash a stock rom first using odin then flash the custom rom afterwards

Ok thx guys...and i have 1 more question ...there is a diference if i flash stock and after that i flash custom? is smoother or faster or idk...?
i saw in some printscreens that they get high quadrant score but mine is max 2300MAX ever

it is always advisable to do a clean flash ( stock rom first before custom rom). but some custom roms have the option to directly flash from one custom rom to another. everything here is trial and error. so whatever works for you may or may not work to others.

[Q] [Ques] Unable to flash any rom via CWM after installing XXLSJ with Phillz Kernel

I have a S2 (GT-i9100).
I frequently switch between ROMs, the last rom i flashed was "[ROM][20 Nov][LSJ][4.1.2][V13.0] WanamLite Clean & Fast & Pure Stock Themed ".
The rom was good, fast and stable, but since it was draining the battery too fast, i decided to re-flash my daily driver (super-Nexus).
Unfortunately, when i tried to flash using CWM (phillz kernel), i got the "Status 7" error.
So, this is what i did: (offcourse i wiped cache/data/davlik cache)
1. Re-downlaoded "super-nexus" - That didnt help (the md5 was correct).
2. Downloaded another 4.1.2 "[ROM][23/11/12][JB/CM10&AOKP] Nostromo 1.5 [Tuning utils/TB] " - to my wonder i got the same error again
3. Then i did quite a bit of searching, found that, issue might be because of signature verification in CWM, when i toggled it i got "signature verification - enabled" - so i fig, it was disabled by deafult, i am yet to test by manually making it "disabled".
Could some1 please point me as to why after flashing with Phillz kernel for XXLSJ, m i getting this error, and why m i the only one getting it. I searched quite a lot, couldnt find anything
I am not a complete noob but m stuck here

Ny1 has any idea about this...
At this point any wild guesses wud do...I dont want to reflash via odin, that the last resort...

bhatti1209 said:
Ny1 has any idea about this...
At this point any wild guesses wud do...I dont want to reflash via odin, that the last resort...
Click to expand...
Click to collapse
Finally found a useful post in Phillz CWM thread:
http://forum.xda-developers.com/showthread.php?t=1877270&highlight=status+7&page=46
Since i have less than 10 posts i am not able to post this question directly on that thread, but could some1 please let me know where/how i can remove the assert commands (the ones that are being talked about in the link above).
I am trying to flash a new rom (super-nexus)

I had the same problem. Flashing DorimanX:s kernel first will solve the problem. Remember, this kernel is not compatible with the XXLSJ rom so only reboot the recovery (Advanced - Reboot Recovery). If the reboot freezes, just shut down the phone by long-pressing the power button and boot into recovery by holding Volume Up + Power.

[Q] Stuck in endless Bootloop

i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!​3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!​4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)​

anoopgkris said:
i'm stuck in an endless bootloop after trying to upgrade the CM10 Beta 4 version on my Samsung Galaxy S Plus.
This is what i did
I'd upgraded from 2.3.3 to 2.3.6 some months ago. Then flashed CM10 Beta 4 by ivendor.
For this i first downloaded the CWM -> recovery-clockwork-5.5.0.4-ariesve.tar.md5 and flashed it using Odin.
Then the ROM file -> cm-10-20130324-ivendor-beta4-ariesve.zip
Was checking the updates on this and found much advances in the 2.5 release of 2 May 2013.
So downloaded the CWM -> CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5. When i tried to flash using Odin it gave me the MD5 error.
Saw somewhere on the forum to flash using zip file, so downloaded CWMRecovery-6.0.2.8-ariesve-kernel26.zip and tried to flash. This was when my phone got soft-bricked.
Removed the cable, battery etc. After some time, was able to go into Download mode but not Recovery.
Then i tried to flash to stock ROM (2.3.6) - I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5. This completed and Odin said PASS. But the phone now goes into a bootloop. Tried the Recovery mode but after the Android-out-of-the-box symbol it again said SAMSUNG and started the boot. This is repeating continuously. What should i do now? Please help.
This is the sequence of things...
1) 2.3.3 to 2.3.6 - Success !!
2) Flash with CM10-Beta 4.a) recovery-clockwork-5.5.0.4-ariesve.tar.md5 - OK
b) cm-10-20130324-ivendor-beta4-ariesve.zip - Success!!!
c) gapps-jb-20121011-signed.zip - Success!!​3) Flash with CM10-Release 2.5a) CWMRecovery-6.0.2.8-ariesve-kernel26.tar.md5 - MD5 checksum error !!
b) CWMRecovery-6.0.2.8-ariesve-kernel26.zip - Soft-bricked !!!​4) Flash stock ROM (2.3.6) a) I9001XXKQI_I9001XXKPM_I9001OXFKQ3_HOME.tar.md5 - PASS
Bootloop
Cannot go into Recovery mode too (after Recovery mode icon appears SAMSUNG logo comes up and phone boots with the blue spiral, this goes into a continuous loop)​
Click to expand...
Click to collapse
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it

Will try this
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
Thanks, will try this tonight
I already took the Nandroid backup before flashing CM10 Beta 4. But was not able to go into it after my phone was soft-bricked.

Solved - booted into 2.3.6 !!!
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
A million thanks!! It somehow started now into the 2.3.6.
Flashing the recovery-clockwork-5.5.0.4-ariesve.tar.md5 did not solve the bootloop. Then i flashed the Boot_loader.tar. That too did not solve the bootloop. Tried Recovery mode again but the SAMSUNG logo kept coming and going until i released my fingers after a full two minutes. Then before the android-out-of-the-box icon came it went straightaway into Recovery .
Wiped Data and Cache and rebooted. After a very very long time it started and asked if im okay with the Google data collection policy asked in Polish language.
Wow, going to update to 4.1.2 Release 2.5 in some time.
Thanks again man. :good:

Got CM10 Beta 4 again !
parkourkarthik said:
AFAIK, CM10 would have already consisted of the latest CWM, so there is no need of u to flash a CWM again over it!
Ur biggest mistake, u MUST have had a nandroid backup before doing anything to ur phone! This might have been even recommended by the thread of the CM10.
So my last suggestion from the things that u have done, flash the CWM through odin if possible right now and if successful get into recovery mode and wipe data & cache and check whether the bootloop is gone.
Else try reflashing the stock firmware.
If that doesn't even help, get help from the devs related to ur device through PM.
If hopeless still, then hit a samsung service center near u
Hit thanks rather than typing it
Click to expand...
Click to collapse
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help

anoopgkris said:
All went smooth. CM10 Beta 4 is back on my SGS+.
Thanks for the advises and help
Click to expand...
Click to collapse
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it

[SOLVED] Bootloop problem after soft-brick
parkourkarthik said:
U got it man:victory:
It's good that u posted the way u solved it! so that it would help others who face the same problem
BTW add the word [solved] in ur thread topic..
Hit thanks rather than typing it
Click to expand...
Click to collapse
Sure, thanks !!
Also pasting here an easter egg that i saw after loading Gingerbread 2.3.6 before this CM10.
Putting this because i tried this for the first time in GB (the seven times click on android version)

[$20-donation giveaway] p5110 cannot go back to stock . Stuck in cm10.1

Hi guys. i've been searching and trying to solve this problem for the past two weeks. can't fcking deal with it anymore. $20 for anyone that can help me , PLEASE!
p5110 here. had cm10.1 working for more than 1 year. when i updated to cm.10.3-rc2 , problems appeared.
Tried flashing stock firmware via odin. Says successfull but still in cm10.3 after reboot. boots up , however, it reboots after 1-3 mins.
tried flashing different roms, error.
Please, how can i revert back to stock or any working state ???
thanks,
alex

Anyone ?!

Try installing Clockworkmod (newest version) and then flash the stock firmware with that. Be sure to clear cache and dalvik cache first, and also factory reset (all through clockwork mod)

Latest official CWM won't help as it's to old for anything (stopped at 6.0.2.7 if i am not wrong), better use latest TWRP.
But: it sounds like your emmc got read only because it reached end of lifetime.
Indicator for that:
- flashing a different recovery via Odin doesn't change the recovery - it still boots the old.
- factory reset inside recovery doesn't change anything
Only way i know to get back write access would be to update the emmc firmware via JTAG. If there's no one with a JTAG near your place, replacing the emmc will be the solution.
GT-P5110 16 GB or 32 GB?
What recovery (also recovery version) are you using?
Using a custom kernel?