Koodos Nexus S i9020A.
I took ICS update a few days ago and phone was very buggy... not to mention no data. I wanted Gingerbread back... Looked in this forum and found a post how to unlock and recover to gingerbread. Followed dirrections and got phone unlocked and before restoring to gingerbread, I took a backup. Then did the gingerbread restore. The phone booted fine (with the now unlocked symbol at bottom). A voila in gingerbread... But no service (no bars with a x). Phone funtions fine other than not being able to call, text, or use 3g. After futher searching I found that there's diffrent versions of Nexus S software. And didnt put the i9020a file on it.... so im assuming thats why its not working. I went back into CWM and tryed to restore my backup I made... I get MD5 Mismatch... I also wanted to be sure it wasnt my SIM card so i put my girlfriends SIM card in and same thing no service..PLEASE HELP... I know im a NOOB to the fullest.. but I really dont have the money to buy a new phone. Thanks in advance for anyone willing to give me some help.
Bruce
Related
hello everyone, I'm having a problem here, I have the i9020a (the one that works with at&t 3g).
I rooted the phone and instantly made a backup, the I tried cyanogen, then I tried, the kernel mod netarchy, I started having issues when I has in cyanogen, my 3g did not work I was only getting edge, so I restored my backup, hoping everything will work, I did get 3g but, once I activate the 2g mode the 3g never comes back, I was going to restore to stock, without my backup, but I got the status 7 error, and it says here that something is not stock http://forum.xda-developers.com/showthread.php?t=1056062
please help me. I need my 3g
I forgot to say that my My baseband version says "NO DGSXXXKB1", in the bootloader, carrier info says ATT
UPDATE: I just noticed that my SMS are not working, can't send any...
I do get calls and I can call.
http://forum.xda-developers.com/showthread.php?t=1071924
I think I found the fix.
Oh my god, I'm freaking out, I already patch the file in the link, and went back to stock, and I only get 2g please help me.
ok here goes, first off, i apologize if this is in any way redundant to someone's else question. with the amount of people whose phone got wrecked with the 2.3.6 update im sure somebody has had the problem im having.
like many people i just clicked "install" when google pushed the 2.3.6 ota. my phone was running 2.3.4. rooted. when it rebooted, i was greeted with the android exclamation mark.
i happened to have a clockwork backup so i tried restoring my backup. and restore it did, but not the radio. after the google update my radio was something like NO GSXXK1 or so. i tried the radio fix here:
http://forum.xda-developers.com/showthread.php?p=14564429&mode=linear#post14564429
i tried reflashing the stock 2.3.3 rom from google, wiping the bootloader and all. ive in fact tried many many things that ive read on xda and google forums.
now, ive managed somehow to have a running 2.3.4 with cell signal. using the efs file copy method in he link above. that restored my 3g and ability to place phone calls but sms arent working. i did the *#*#4636#*#* thing and notice that smsc is 00, i tried to set to the right value of +17057969300 for Rogers canada but all i get is an update error followed by a crash.
and now, funny, my search button is acting weird, like an eye that keeps twitching.
im not very knowledgeable in this stuff, just enough to get by and install custom roms but clearly im in over my head now.
why did copying my 3 efs file in the root of the sd card restore signal? i dont think these files really belong there, so just what the heck happened?
is there a way i can restore my nexus S to google stock rom when they shipped the phone? i mean, a complete wipe, sd, boot, radio...everything.
if i can start back with the stock phone, i can re-root again and start fresh.
any ideas please??
im physically tired of reading everything, misleading information and constantly flashing back and forth hoping its gonna work. oh and mandatory angry comment: thank you google for effing up my phone!
edit:
the only stock rom i tried i the 2.3.3 stock update available in clockwork. made no results.
current specs:
my phone is a i9020a
current baseband : NO DGSXXKD1
current build: GRJ22
android ver: 2.3.4
core: 2.6.35.7-ge382d80 [email protected] #1
Follow my last thread posted
Sent from my Nexus S using xda premium
Thanks dude, i had actually done that and did manage to get a signal back. its SMS that just wont work and when do the INFO thing to set the right value, i either get update error or a crash.
i installed stock rom 2.3.4 and install radio uckd1. that made my signal work even without having to move the efs files on the root of the sdcard. but still no sms.
is anybody else getting sms problems? this was working before the 2.3.6 fiasco.
im with rogers canada, in ottawa.
ok, just to loop the loop on this one and hoping it will be of use to somebody else.
my sms issue wasnt related to my phone at all, once i had a signal back, that's as far as the phone was concerned.
i placed a call to rogers to let them know i couldnt sms anymore.
long story short, they tried many things but ultimately, its doing the "hard" reset on the network for my phone that did it. im sure there a better name for it but basically they erased my phone from their network, i had to wait about an hour for the change to propagate. when i powered the phone back, it resynced everything and sms was back online without a single thing to do.
hey guys, currently hating myself for rushing into this so badly...
i DO NOT have a backup of my stock rom
ive rooted my nexus s, it is the i9023 (thats what it says on the back) and im looking to either unroot it, or connect to my carrier through my current rom (peter alfonso 4g ics)
My phone isnt 4g, its 3g.
whenever i try to flash the rom for unroot (i9020t_9023.zip) i get the seemingly common Status 7 error... but ive google it aplenty and have found no fix
even if i did want to change the rom, i cant, because the pete one is the only one that seems to work... feel free to make suggestions, ill try them.
the last thing is my carrier. im on vodaphone australia prepaid. im not exactly sure how, but apparently reflashing the radio helps?
thank you for your help
Hi at all...
I need help ....my nexus s shows the dev IMEI004999010640000..so the EFS folder is corrupted.
What i did and what my problem is:
I bought my nexus s a few months ago make a efs folder backup like everyone recommend and everything was fine i run JB-DoubleX no problems at all. One day in the morning nexus s want turn on ....dead... i tried everything...nothing ....so i sent it for repair...last friday it come back with Gingerbread 2.3.4on it then i made the ota update to ICS and then flashed the last bootloader LC2 and radioXXI1 after that i flashed my standard JB ROM Double X. This time i don´t make a new efs-folder backup because i thought i already had made one and phone came from repair with same imei and serial number.
As i recognized that my imei was corrupted i thought no problem i have already a backup so i copy the efs backup folder in my phone like it is discribed in some treads here on xda but mei imei doesn´t change to the right one it stays at 004999010640000 now i run out of ideas.
Also courios things are that i have any problems with playstore or with calls, mms, sms all seems tho work normal.
Can anyone of you help me please...????
I have had this issue since shortly after the Nexus S came out. So over year and half. The phone is still in use by my wife, running latest jb build. Every feature works.
First, try to flash it back to factory stock. If that don't work, copy over the efs folder, but remember to boot into CWM and choose the "fix permissions" option.
Thanks guys for the answers...
But I have allready flashed stock ROM from Google Server (Gingerbread 2.3.x) with fastboot....not working.
Flashed Gingerbrad 2.3.x with Odin....same ...not working followed some treads here on XDA....allways same result....generic IMEI.
So now I have a backup of my efs that seems to mismatch to my phone after repair....so i think there is no hope to get back my IMEI..
I think its a md5 hash problem i believe that the md5 of the nv_data.bin(or an other file in the efs folder) must match to some other md5 somewhere in the system....otherwise the change is locked.
This is not a fact its only what i think by myself.....
S.R.
Hey everyone,
I used to have a Sidekick 4G that was rooted and ROM'd so Im not neccessarily a noob to this, but still a bit. I bought an LG Optimus T (T-Mobile) as a replacement for my broken Sidekick. I'd had the phone before so I knew it was a decent phone, and for $40 on eBay, a deal I couldn't pass up.
Here's the story: I rooted my phone and got a ROM loaded on New Years Day. ROM was fine, but I decided I wanted to change to a newer version of CyanogenMod this past Saturday(1/5). So after testing out a few ROM's, I came across one that unfortunately didn't flash properly. When I tried to go to use the phone, the main Android OS crashed. I had a black screen with the nav bar displaying no SIM card(which was accurate), the time, battery life, and no signal. Once my boyfriend got home and was able to get the phone to finally boot into CWM and flash into the new ROM, even with my SIM card in, I had no signal. I thought maybe it was an issue with the APN so I went in to try to fix it and none were listed. When trying to add one it, it never saved.
My recovery in CWM goes back to the broken ROM, unfortunately. When trying to unroot, Superuser begins to not respond when its trying to uninstall either busybox or Superuser. The phone works fine, I can connect to WiFi and use it and everything.
My question for you today is does anyone have a recovery of the stock ROM that they can post that I can flash into, or any tips on how to fix this? I thought maybe my SIM card is fried for Android, so I thought of calling into T-Mobile to have them activate a spare I have laying around, but would that fix the issue?
I really appreciate any help that you guys can provide. Thanks in advance!
kaitthedork said:
Hey everyone,
I used to have a Sidekick 4G that was rooted and ROM'd so Im not neccessarily a noob to this, but still a bit. I bought an LG Optimus T (T-Mobile) as a replacement for my broken Sidekick. I'd had the phone before so I knew it was a decent phone, and for $40 on eBay, a deal I couldn't pass up.
Here's the story: I rooted my phone and got a ROM loaded on New Years Day. ROM was fine, but I decided I wanted to change to a newer version of CyanogenMod this past Saturday(1/5). So after testing out a few ROM's, I came across one that unfortunately didn't flash properly. When I tried to go to use the phone, the main Android OS crashed. I had a black screen with the nav bar displaying no SIM card(which was accurate), the time, battery life, and no signal. Once my boyfriend got home and was able to get the phone to finally boot into CWM and flash into the new ROM, even with my SIM card in, I had no signal. I thought maybe it was an issue with the APN so I went in to try to fix it and none were listed. When trying to add one it, it never saved.
My recovery in CWM goes back to the broken ROM, unfortunately. When trying to unroot, Superuser begins to not respond when its trying to uninstall either busybox or Superuser. The phone works fine, I can connect to WiFi and use it and everything.
My question for you today is does anyone have a recovery of the stock ROM that they can post that I can flash into, or any tips on how to fix this? I thought maybe my SIM card is fried for Android, so I thought of calling into T-Mobile to have them activate a spare I have laying around, but would that fix the issue?
I really appreciate any help that you guys can provide. Thanks in advance!
Click to expand...
Click to collapse
u are not getting a signal because u are on the old baseband
flash gingersnap by neko95 it has support for both baseband
and press thanks
androidisfuture said:
u are not getting a signal because u are on the old baseband
flash gingersnap by neko95 it has support for both baseband
and press thanks
Click to expand...
Click to collapse
I just flashed Gingersnap and still have the same issue. No signal, no APN.
kaitthedork said:
I just flashed Gingersnap and still have the same issue. No signal, no APN.
Click to expand...
Click to collapse
please read the gimgersnap page
it has terminal command
open terminal emulator
first type su
then press enter
then type fixbb
Lolz!!
Upgrade to new baseband or flash baseband fix 'after' flashing a rom!!
Download the fix from my signature below. (1st link)
Flash this fix same like flashing a rom from CWM!!