Related
Ok i know and have seen that there are many experienced users in this forum, so i give you this!!Pls help sum1!!!
I think i bricked my fone, tried to get cwm 3 on it, then while rebooting, it wont reboot. went into download mode with odin (3 button fix) (i have done this 9-10 times before, not a noob to this), selected pit and tar and hit start. odin stuck on factoryfs and fully orange screen on fone. removed battery, fone, usb, odin restart, tried again, yellow screen. again. red screen. now got frustrated. tried normal odin(not the 3 button fix), again yellow screen.took out battery to try again, but fone wont start/go in dl/recvry mode anymore. tried on 2 different comps with xp/win7. no go.
SCREWED??
BTW, i ordered a jig.should arrive by end of week.
It'll be fine after you get your jig.
Sent from my SAMSUNG-SGH-I897
same thing happened to me...but i just got it replaced..as there was no way i could wake it up...but try Jig..or just get it replaced...every captivate is under warranty...tell them u were doing official Froyo update and lost electricity or something....
yes will try that and post.
In the meantime, can sum1 pls run me thru the steps to install custom ROM on preinstalled froyo cappy? My prev 1 was stock eclair, i filed 4 insurance and am sure the new 1s gonna b stock froyo. I have heard that there are a no. f probs with stock froyo phones????
Its a semi uncommon problem.I have had the random colored screens before and had to pull battery. Managed to get odin to work after a couple of times
Sent from my SAMSUNG-SGH-I897 using XDA App
psycho2097 said:
yes will try that and post.
In the meantime, can sum1 pls run me thru the steps to install custom ROM on preinstalled froyo cappy? My prev 1 was stock eclair, i filed 4 insurance and am sure the new 1s gonna b stock froyo. I have heard that there are a no. f probs with stock froyo phones????
Click to expand...
Click to collapse
flash to stock using full Odin(full odin to avoid loosing 3 button combo), flash CWM.Zip....flash any froyo custum rom
or just flash the fix for sign verification (its somewhere in the threads) then you can avoid flashing to stock....just flash CWM and Custom rom
viny2cool said:
flash to stock using full Odin(full odin to avoid loosing 3 button combo), flash CWM.Zip....flash any froyo custum rom
or just flash the fix for sign verification (its somewhere in the threads) then you can avoid flashing to stock....just flash CWM and Custom rom
Click to expand...
Click to collapse
YEA, I THOT SO 2... JUZ WANTED 2 VERIFY, WAT ABOUT WEN CHANGING ROMS?do i need to flash to stock every time, or can i just take a backup f froyo stock using cwm?(sorry 4 the caps...)
Most of the custom roms don't require flashing to stock now a days. But if its mentioned in the instructions than I would do it.
But definitely you should disable lagfix and stuff before flashing over new rom.
Sent from my SGH-I897 using XDA Premium App
viny2cool said:
Most of the custom roms don't require flashing to stock now a days. But if its mentioned in the instructions than I would do it.
But definitely you should disable lagfix and stuff before flashing over new rom.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
psycho2097 said:
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
Click to expand...
Click to collapse
If u flash any zip from stock froyo it gives you sign verification error. So u need to fix that a nd than just flash custom rom as u normally do
Sent from my SGH-I897 using XDA Premium App
Crash N Burn....Owch!
psycho2097 said:
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
Click to expand...
Click to collapse
Sounds as though your bootloader got hammered.
Yes, as another posted, with 3e recovery you'll get a signing error, but there is a workaround, depending on your device and ROM you're using to have files pass through as if it were on 2e recovery. Another method is if one passes files that are unsigned. (only load if it's from a trusted source)
Is it possible you performed a nandriod backup before this debacle occurred?
If so, try a restore from recovery with your last nandroid backup. This should restore the bootloader and correct partitioning on your disk.
HtH
Peace-
Liv33viL said:
Sounds as though your bootloader got hammered.
Yes, as another posted, with 3e recovery you'll get a signing error, but there is a workaround, depending on your device and ROM you're using to have files pass through as if it were on 2e recovery. Another method is if one passes files that are unsigned. (only load if it's from a trusted source)
Is it possible you performed a nandriod backup before this debacle occurred?
If so, try a restore from recovery with your last nandroid backup. This should restore the bootloader and correct partitioning on your disk.
HtH
Peace-
Click to expand...
Click to collapse
inncidentally i did do a couple of nandroids before "all the **** hit the fan". and i could use it to restore. but how? my fone simply wont turn on, neither go in2 recv/ dl. so how 2 restore???????
all 2.2 have 3e recovery, custom roms built on 2.2 come pre cracked.
here is the 3e recovery fix. http://forum.xda-developers.com/showthread.php?t=909213
it works on all 2.2 stocks with 3e.
if you are rooted using "one click root 1.7" (NOT ODIN ONE CLICK!!!) you dont need adb commands just root explorer to mount and replace file. or use adb to mount and push file. the instructions in the thread have the 2 methods mixed together.
no offence but ignore Liv33viL on this one
Trusselo said:
no offence but ignore Liv33viL on this one
Click to expand...
Click to collapse
Dude, that's just plain wrong. Let each person decide on their own who's advice to take and who's to ignore. It's an open forum and we all have the right to share our knowledge and experience. The focus here should be helping people get the assistance they need, not to diminish someone's credibility based on a personal opinion.
In short, grow up.
Trusselo said:
no offence but ignore Liv33viL on this one
Click to expand...
Click to collapse
ok, but then do u mean my bootloader is not damaged? can it be still repaired by using jig? can i restore nandroid?? but how 2 do so since my fone wont turn on at all?
What happens when you do turn it on- nothing? Or does it hang on the boot screen?
Sent from my SAMSUNG-SGH-I896 using XDA App
I had the very same problem. Your bootloater is boogered up now. I sent mine to an xda member and he fixed it.
Even with a jig I wasn't able to do anything. My phone would go into d/l mode with it but that was all it would do.
I paid $50 to have mine fixed which in my opinion is well worth it. That doesn't include shipping costs. I had connexion2005 fix it for me. He a great guy and does very fast work. It beats buying a new phone.
Hope this helps.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
All shameless advertising aside, it's worth trying a fix where others give up and pay someone. Through the process of elimination we can determine if you need professional help lol!
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks guys..will try connexion when the jig fails.
Sent from my SAMSUNG-SGH-I897 using XDA App
N does anybody know what to do, as my newly arrived cappy has a distinctive yellow tint to the screen. Do I call samsung and ask for a new one? Or is there some method to fix it by software?
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi,
My IMEI is 004999010640000.
I understood from reading on this forum that it is not a valid one.
However, my phone works.
I did back efs folder but I might had backed it up after too ma y past flashes.
1. How can I know if IMEI is fine?
2. Can IMEI or eds folder be restored from carrier/other if my backup is obsolete?
3. Can I find it in an old nandroid backup? How?
10x
Trumpy
Sent from my GT-I9000 using xda premium
If it starts 004999xxx then its been corrupted but you can always flash a stock samsung rom to get it back. Check this thread
Menvaihelv... said:
If it starts 004999xxx then its been corrupted but you can always flash a stock samsung rom to get it back. Check this thread
Click to expand...
Click to collapse
10x,
If it is corrupted, how can flashing a stock rom restore it?
I am on ICS. Should i simply flash a stock rom using cwm recovery?
I'd hate flashing back and forth, is there any alternative solution?
If my phone works, why do I need the imei for?
Regards,
Trumpy
Sent from my GT-I9000 using xda premium
y.trumper said:
10x,
If it is corrupted, how can flashing a stock rom restore it?
I am on ICS. Should i simply flash a stock rom using cwm recovery?
I'd hate flashing back and forth, is there any alternative solution?
If my phone works, why do I need the imei for?
Regards,
Trumpy
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i am also having the same trouble. and took the plunge to flash via odin. now im having problems with that. if there was only an easy way to fix it. and easy wasys to back up and restore in future
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727
wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue
orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked
same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm
Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app
This has the potential to become a major issue.
I figured instead of two separate threads, the discussion can be consolidated here.
Existing threads:
http://forum.xda-developers.com/showthread.php?t=2069823
http://forum.xda-developers.com/showthread.php?t=2071206
This has happened to 3 people so far. I know there are many users who have successfully updated to ICS via Odin, but if more and more people have touchscreen issues I am going to take the thread down.
Some information to provide:
Was KIES used?
Version of Odin used?
What ROM was it being flashed from
What ICS ROM was loaded (course from sammobile or hotfile, etc.)
What Recovery was used?
Also please run a logcat through ADB to see if any errors occur during boot when the touchscreen does not work.
Hopefully someone like dan-htc or nrvate has some knowledge to share as well.
Thanks Orlando for putting this all in one place.
I'm one of the affected users.
Was KIES used? Yes. I used Kies for the initial update which completed successfully. TS worked before, not after.
Version of Odin used? I have tried at least 10 times after the initial Kies update with Odin 1.85. Each time completeing without error but TS still does not work
What ROM was it being flashed from? All I know is that I was on the stock ROM from when I bought the device Dec12 from AT&T. 3.2?
What ICS ROM was loaded (course from sammobile or hotfile, etc.) Sammobile downloads which link to hotfile. I have tried each (there are only 2) at least 5 times
What Recovery was used? I use the stock recovery, nothing non-stock has been done to my device.
Also please run a logcat through ADB to see if any errors occur during boot when the touchscreen does not work. I am not familiar with how to do this but if you post some steps I will do it tonight and post results, no problem.
Ill also add that after it boots up I am able to plug it into my laptop and see it in both Kies and my computer. I can drop files onto the sdcard.
I don't understand how a new Rom can break the touchscreen and reverting back doesn't fix it.
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
I don't understand how a new Rom can break the touchscreen and reverting back doesn't fix it.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I don't know, but that's exactly what happened. I was using it right up until the point I plugged it into Kies and perfomed the update.
Thanks
EraserX33 said:
I don't know, but that's exactly what happened. I was using it right up until the point I plugged it into Kies and perfomed the update.
Thanks
Click to expand...
Click to collapse
it just doesn't make sense to me. it has to be a software issue and not a hardware issue
I'm one of the affected users.
Was KIES used? No. Kies didn't detect my tab initially, Then used Odin; TS worked before, not after.
Version of Odin used? Version 1.85
What ROM was it being flashed from? AT&T Stock 3.2
What ICS ROM was loaded (course from sammobile or hotfile, etc.) Sammobile downloads which link to hotfile. I have tried each (there are only 2) as well as the "Default (XXX)" Carrier. Tried afterwards CM10 and AOKP unofficial but both showed the samsung boot, then a blank black screen with backlight on
What Recovery was used? None for the intial load, then Flash CWM 5.5, TWRP also had no Touch working, then back to stock
Also please run a logcat through ADB to see if any errors occur during boot when the touchscreen does not work. Will do and post back in here later tonight hopefully
My device is still not detcted Via Kies but i can read and write now normally to the SDCard via cable from Windows and Ubuntu
Wamaonline, were you able to successfully flash the roms, cm10, stock, etc., with odin? And you only had auto-reboot and f.reset checked and Rom in PDA?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Wamaonline, were you able to successfully flash the roms, cm10, stock, etc., with odin? And you only had auto-reboot and f.reset checked and Rom in PDA?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
yes, all was green for flashing Stock. flashed CWM 5.5 using ODIN, then moved files for CM10, AOKP and GAPPS to sdcard, and flashed them using CWM
Even tried a custom kernel from the forums here using CWM.
Finally went back to stock HC Rom, but no updates so far.
And both ROMs didn't really complete a boot !
Custom kernel will only work for hc roms
Sent from my SAMSUNG-SGH-I727 using xda premium
orlandoxpolice said:
Custom kernel will only work for hc roms
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You think that may work ? am currently on stock HC, will flashing the kernel once again make any difference ?
wamaOnline said:
You think that may work ? am currently on stock HC, will flashing the kernel once again make any difference ?
Click to expand...
Click to collapse
Flashed the custom kernel, and still same problem
---------- Post added at 02:39 AM ---------- Previous post was at 02:32 AM ----------
wamaOnline said:
Flashed the custom kernel, and still same problem
Click to expand...
Click to collapse
Flashed contingency ROM , still the same result. Don't currently have adb at hand, Will the show log output from CWM be if any help ?
all i have now is
"failed to open /sys/class/android_usb/android0/state: No such file or directory"
wamaOnline said:
Flashed the custom kernel, and still same problem
---------- Post added at 02:39 AM ---------- Previous post was at 02:32 AM ----------
Flashed contingency ROM , still the same result. Don't currently have adb at hand, Will the show log output from CWM be if any help ?
all i have now is
"failed to open /sys/class/android_usb/android0/state: No such file or directory"
Click to expand...
Click to collapse
it may be worth a try to format the entire tablet, and then flashing a rom. that means formatting everything in CWM.
Anyone know what these guys did? Any of them resolve the issue? Not sure if it could be related in anyway.
http://forum.xda-developers.com/showthread.php?t=1523254
Interesting, I wonder if it's a cwm issue? Have you tried twrp? Orlandos official ATT ics thread in the development section had a link to it. It's what I use. You'll need to flash it thru odin. Might be worth a try.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
it REALLY worries me that even a nandroid backup wont restore the touchscreen. it is almost if flashing causes hardware damage.
jd1639 said:
Interesting, I wonder if it's a cwm issue? Have you tried twrp? Orlandos official ATT ics thread in the development section had a link to it. It's what I use. You'll need to flash it thru odin. Might be worth a try.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thanks, Tried it, but touch screen didn't work there either
orlandoxpolice said:
it may be worth a try to format the entire tablet, and then flashing a rom. that means formatting everything in CWM.
Click to expand...
Click to collapse
Did format everything before then flash stock ROM, but the same problem
Sent from my A500 using xda app-developers app
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
orlandoxpolice said:
it REALLY worries me that even a nandroid backup wont restore the touchscreen. it is almost if flashing causes hardware damage.
Click to expand...
Click to collapse
Yes , still hoping for some sort of break through in the debugging, thanks
Sent from my A500 using xda app-developers app
adb from my machine is not working when i boot my device normally, can only see it in adb when booted into CWM recovery.
Worth mentioning that the tab doesn't shutdown ! It always keeps rebooting
Sent from my A500 using xda app-developers app
Maybe try flashing with a newer version of odin. I have been using odin 3.07 successfully without issue since I got this tab. May want to see if flashing with a more recent version actually successfully flashes correctly. If kernel doesnt flash correctly with odin then it could affect the way drivers are handled in all roms following.
I've run the LSA firmware with little to no issues for a while now, but recently my phones decided to run hot and reboot itself with increasing frequency.
so I'de like to revert back to stock ICS and see if that helps or if I'm looking at a hardware failure.
is there any particular trick to this or can I just backup using Ti, load the new (old) ICS firmware in Odin and flash away?
thanks for any advice guys...
How old is your phone? Make sure your battery is good condition, before proceeding anything.
Sent from my GT-N7000 using xda premium
dsmas said:
How old is your phone? Make sure your battery is good condition, before proceeding anything.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Nov 2011 (just over 12 months)
the battery is a Gold higher capacity model, there is no bulges or tears and the heat isnt coming from that, I pulled it to check. the glass side is the hottest side.
Good. My suggestion is, go through drketan threads / tutorials which are comprehensive on your problem.
Sent from my GT-N7000 using xda premium
dsmas said:
Good. My suggestion is, go through drketan threads / tutorials which are comprehensive on your problem.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
on the problem or my intended solution?
I've started uninstalling apps because the thing reboots during backup.
every-time i uninstall an app it reboots as well.
If you want to go back to ics, backup whatever you want using tb.
Then boot into recovery. Format/system, data, cache, preload.
Then go to advanced and choose reboot download. Then connect to pc and flash using odin. Make sure not to wipe while on stock ics kernel. Install a safe kernel ASAP.
nokiamodeln91 said:
If you want to go back to ics, backup whatever you want using tb.
Then boot into recovery. Format/system, data, cache, preload.
Then go to advanced and choose reboot download. Then connect to pc and flash using odin. Make sure not to wipe while on stock ics kernel. Install a safe kernel ASAP.
Click to expand...
Click to collapse
cool, looks like I fixed it by rolling back to ICS.
Had to use Mobile Odin because the PC Odin wasnt playing ball... but meh. whatever gives me back my toy (that nexus s felt like a toy in my hands)
thanks all for the help.
senectus said:
cool, looks like I fixed it by rolling back to ICS.
Had to use Mobile Odin because the PC Odin wasnt playing ball... but meh. whatever gives me back my toy (that nexus s felt like a toy in my hands)
thanks all for the help.
Click to expand...
Click to collapse
can you please explain how you rolled back?
scorpion100 said:
can you please explain how you rolled back?
Click to expand...
Click to collapse
backed up user data using Ti
flashed PhilZ-cwm6-XXLSA-DBT-3.99.tar.md5 as per the PC Odin instructions
copied the N7000XXLRT_N7000DBTLRT_N7000XXLRK_HOME.tar.md5 file to micro SD
flashed N7000XXLRT_N7000DBTLRT_N7000XXLRK_HOME.tar.md5 u sing mobile odin pro
done.