So I have been messing around with the new ICS build from AOSP.
Since I have the unlocked white i9020a I have to use the 4g zip.
It installs and runs fine the only problem is that I get no service.
I've tried flashing different radios on it such as KB3 and UCKB2.
But when I head to about phone on it and take a peak at the baseband it says unknown.
Ummm why do u have to use the 4g version? I have an i9020a and I use the normal nexus s rom.
On an i9020a? Weird.
I tried using the regular 3g one but as I start the install it stops and says there is an error.
I have a similar problem. Trying to resolve now.
Yah I've been tinkering around with it and I just tried to run the regular 3g install after wiping the cache and etc.
: /
If your problem was like mine, no matter what I would get 0 service whatsoever. No edge, no 3g, nada.
Well, turns out my /efs folder was wiped or corrupt. not sure which one, but I downloaded this program: and restored my efs folder. I believe CWM makes backups now, or at least most ROM devs do now, it's apart of the script.
http://www.nexussforum.net/nexus-s-apps/(app)-efs-backup-and-restore/msg9658/
Restore efs, and service is back to normal.
Related
so like a kid in a candy store i got ahold of ROM manager and ODIN and started flashing cool looking roms..next thing i know, the t-mobile logo is popping up and i am a not-so-proud owner of a modded T-Mobile Captivate, no longer an ATT Galaxy S!
of course the t-mobile network uses different frequencies and the like, so the phone part of my phone stopped working...bummer! i grumbled as i flashed back to a ROM that worked with the ATT network (FUSION it is called) but apparently that ROM does not mess with the internal network settings thats why it worked so well initially it didnt change the stock cell internals...
so now i have a hybrid phone, half-tomobile half-att half Fusion, and it only picks us signals from the Edge network!!! i barely get any reception so it pretty useless...
so i need some help...i can i get this beast back into a condition where is will work as an ATT galaxy?? also, for whatever reason i cannot mount or download market apps to the phone tho it does pickup wifi connections...
any help/ideas appreciated...advTHANKSance!
- mark
Flash back to stock with odin 1 click. Or try just flashing a new modem with cwm.
Sent from Serenpitidy x.x
ok...i finally fixed the mess i made by using this process...
manually set the modem/APK using this guide...may or may not have been needed in the end...
http://www.wireless.att.com/answer-center/solutionDisplay.jsp?solutionId=KB110934
reset the phone to factory using this thread...
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
note..i used the old I897UCJH2 Firmware but the plan is to upgrade to JH6 tonight...
did a factory reset on the phone and BINGO...full working baseline phone. thanks for the help guys what a great site u run
I'm (obviously) a bit of a newb when it comes to android, and I was flashing back from cm7 to see how it was done. When I reinstalled GRJ22, everything was working fine. I then downloaded and flashed the OTA update to GRK39C (or so I thought). It turns out it was the update to GRK39F, which apparently is ATT or GPRS specific. My phone now thinks it's on ATT and is trying to use GPRS.
I'm on Telus in canada, and use HSPDA.
The phone was also showing baseband version I9020AXXKF1, it should be I9020AUCKD1.
I've tried restoring from a backup, flashing back to cm7 and to stock fw's, and even tried flashing the radio.
My phone still shows GPRS, and now baseband version shows I9020AXXKD1.
Is there any way to fix this? I hope someone here is knowledgeable about this...
That baseband is associated with the i9020t, or the t-mobile variant. The canadian nexus s is identical to the at&t version.
There is a sticky with all the roms. Use it and get the right rom installed
Unfortunately, the ROM I need seems to be one of the missing ones. Is there any way to backup the radio from my wife's (identical) phone and flash it to mine?
It looks like the file I need is 5282b5b3eb74.signed-sojua-ota-178324.5282b5b3.zip but I'm unable to locate a working link for the file. Can anyone tell me if this is correct and/or provide a live link?
Actually that particular one you want has broken tethering... This is a dump is the 2.3.4 with I9020AUCKD1 radio from my US import i9020a tested and working on SaskTel HSDPA+.
http://dl.dropbox.com/u/7812800/Stock-GRJ22-i9020A-unsigned.zip (will need to be flashed via CWM Recovery)
Thanks! I got it working by flashing the unsigned ROM in the sticky thread, and I'm running cyanogenmod 7.1 RC now. I'll keep the stock ROM on file just in case though...
r.asimi said:
Thanks! I got it working by flashing the unsigned ROM in the sticky thread, and I'm running cyanogenmod 7.1 RC now. I'll keep the stock ROM on file just in case though...
Click to expand...
Click to collapse
Cool... I hope it works out well for you.
btw i got a rooted version of the stock 2.3.4 if you are interested as well.
So, for some reason flashing with your ROM set my phone to UMTS. Can someone refer me to a howto to backup a full ROM image from a phone, since my wife's is working fine and is on the right type of network.
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.
Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
The flashing went without any real problems, except one with installing CWM, but I sorted that out. I booted into the new ROM, and liked it, but after testing it I noticed it wouldn't load anything from my Koodo SIM card, like my contacts, and in the notifications bar where it shows your service carrier, it just showed a number. I was still able to send and receive calls and messages, but it was as if it didn't fully support my SIM. After finding a few things I didn't like with the ROM, I decided to use my Nandroid backup to restore, and after following a tutorial, I "successfully" restored the backup, according to Nandroid... But upon booting the phone, it was stuck on the boot logo.
After about an hour of searching, I was able to find out that CWM5 has issues restoring backups through Nandroid, and that I was screwed out of using my restore. I found the stock Koodo 2.3.4 ROM, and flashed it with Odin, and had to do a Recovery System Wipe to get out of a bootloop. I thought I was back to square one, and began installing my apps again and such with no issues.
---------EDIT---------
So, after hours of fooling around I replaced my save file with Root Explorer, like I was before, but then gave Terminal Emulator SU Permissions and used it to give the save file the right APP ID and Permissions, and it's working without freeze-ups now. I also used SQLite DB Editor to edit a fresh save on Where's My Water to reset my progress back to where I was before the update broke my save.
I am still wondering why my SIM Card didn't work properly in that ROM, and if there is a way I could make it work.
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Winner Winner Chicken Dinner!
dhx138 said:
Is your model number GT-S5830D with baseband S5830DTLKI4? This is my model of the SGA and I've been reluctant to try flashing any ROMs because I can't find any success stories for this exact model. I'm also with Koodo and have concerns about how the SIM card will handle the custom ROMs too. If you do have this model, what has your experience been since your original post?
Click to expand...
Click to collapse
My model is GT-S5830D and I am on that baseband and have tried a few ROMs, all of which work. I would say try a ROM as the you should be fine, and you can always do a CWM Backup.
The SIM issues I was having has been resolved, as it is simply caused by being in Canada, and my carrier not being in the phones list, so it still displays a number, but all of my features (Calling, SMS, MMS, Data, etc) work fine.
admiralspeedy said:
Ok, so I am somewhat new to the whole rooting and flashing of phones. I own the Samsung Galaxy Ace, from Koodo, and last night following a tutorial to install CWM4 and updating it to CWM5, followed by making a Nandroid backup and flashing Ice Cream Sunday Final, I had some issues.
Click to expand...
Click to collapse
Where is this tutorial??? I have yet to find one for the Koodo Ace that works.
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
TheCing said:
I'm having an odd issue. I've been running the latest Hyperdrive ROM release on my S3 for about a year now, but I can't stand Touchwiz ROM's so I've tried flashing AOSP ROM's such as CM, AOKP, even Beanstalk. I love all of these ROMs for tons of reasons but I keep running into the same problem, everything works great but I can't receive mobile data. My mobile network state is Disconnected and I have no idea how to fix that. I can text, call, and connect to wifi fine, but no mobile data. I've backed up my EFS but I'm not sure that's connected to the same thing. I have the network set to "CDMA/LTE" (would be more specific but each ROM has it different), but for whatever reason the APN settings are inaccessible. The menu option is clearly there but I cannot open it to ensure I'm using the LTE APN. I decided to give this another go yesterday, and still no dice. However upon restoring my CWM backup of Hyperdrive, I have now lost 4G and am stuck on 3G. My network type now shows eHRPD and while I can access my APN's (I was always able to on Touchwiz ROMs) I can tap on the Verizon LTE APN, but it seems to make absolutely no change to the actual APN. In fact when I reboot it it defaults back to eHRPD all over again.
So, 1. have I somehow screwed myself over? and 2. what am I missing with AOSP based ROMs?
Thanks for any and all help.
Click to expand...
Click to collapse
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
XdrummerXboy said:
I would try flashing a stock ROM such as the one on ScottsROMs.com
The 4.3 stock rooted, OTA disabled, UNlocled boot loader and no Knox.
See if you can get data with that. Firmware for the radio may have gotten messed up, and this would re-write that data (long shot, but worth a try). Another option would be to re-flash the radio maybe.
And now that I think of it, which radio are you on? MF1, ML1, NE1? Because I think I read somewhere that certain ROMs require a certain radio newer than _____ (don't remember which radio).
Click to expand...
Click to collapse
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
TheCing said:
Thanks for the help. I flashed a 4.3 ROM as you suggested, and no difference. I then chased some threads around and decided to just factory reset it as if I was going to return it. Still nothing, I get 3G, not LTE. I was using MB1 before I flashed an AOSP ROM, at which point I flashed the MF1 firmware and then the ML1 modem. That did nothing to fix my issue. I'm not quite sure what else I can do at this point.
Click to expand...
Click to collapse
Hmm... ML1 should be new enough.
That's a bizarre issue.
For me, I mainly get 3G. It seems as if either Verizon pulled some LTE towers near me, or my data antenna doesn't have very good contact. Maybe you're having the same issue.
Do you EVER get 4G? Or literally never?