HI - dunno if anyone has done this.....went to upgrade to moray 2.2.2 - i got there in the end but midway i flashed the stock rooted 3.2.2 xoom image and since then my xoom try to authenticate a us 4g modem - is there anyway of switching this back to a 3g xoom modem - dont mind to a certain extent if ive got to reflash again but after reflashing to moray 2.2.2 it seems to still think theres a 4g modem in there??
I've found so far its something to do with build.prop....I can see all the CD a stuff in there...am I right in guessing that I need a build.prop from someones uk xoom...is that right?
Related
I just got a new Nexus S purchased from a Rogers store here in Canada.
I am eager to start flashing some new ROM's and such but I have learned some things in the past with my SGS and I really want to make sure I have my stock radio available in case I need to flash it back.
i9020AUCKB2 is my stock modem. I have some newer modems ready to flash but I am worried that it will cripple my 3G connection to Canadian carriers.
I have looked and can't find this modem anywhere. Also I don't know how to back it up myself. I have already done a CWM backup but I have read that this doesn't backup the radio firmware.
Does anyone know how I can easily backup my own radio or where I can download it from?
+1 I've been searching for the last few days info about the exact same thing. I just sold my i9000m and was hoping to flash some new roms with this phone too but not gonna try until I either have a stock odin version of this rom or at the very least the CKB2 modem.
+1 same boat, want to know this too
Just bought Nexus S yesterday Telus baseband I9020AUCKB2.
Rooted and installed CWM 3.0.2.4 and flashed CM7 (Great ROM) baseband remained the same
from what I've been reading in Nexus S dev, Odin is something we should try to avoid if possible. I came from Fascinate T959D and I thought about it but that's probably one of the easiest ways to brick if you don't know EXACTLY what you're flashing and WHAT you're flashing it on.
Odin = last resort
lucidcoin20 glad to hear that flashing CM7 didn't change the baseband, I didn't have the courage to try it. I wouldn't flash just anything with odin but if you can find the right files it will get you out of a mess pretty quick. I agree its not for noobies with no clue what's going on but if Samfirmware comes out with the 9020a rom I'll make sure to have it on my pc for an emergency.
But from my phone wich is a Koodo version (went with them cause they were so cheap outright so I could go just cancel and go back to bell) we all have the At&t version so all Canada is the same. Hope it all works that way so I can go on CM7.
But would still like to learn how to backup the radio file in case I ever need it in the future.
Well I went ahead and flashed KB3. My speeds are less than impressive but I still have 3g with Rogers. Still looking for KB2 though to do some more testing.
Have you tryied KB1 radio, works good for me, i believe it is a US radio.
pterry30 said:
Have you tryied KB1 radio, works good for me, i believe it is a US radio.
Click to expand...
Click to collapse
Flashed KB1 and KB3 and tested using speedtest.com app, three separate times over wifi and cellular network - the KB1 was roughly 10-15% slower than the KB3 for me..
KB3 labelled my radio as "ATT" btw
CraneGuy said:
But from my phone wich is a Koodo version (went with them cause they were so cheap outright so I could go just cancel and go back to bell)
Click to expand...
Click to collapse
LMAO did the same thing but for rogers saved $75.
If you look in Q & A forum, there is a post for a clockwork flash, K2B radio, just posted in that forum today. I have flashed the radio, work great fore me.
You can get the KB2 radio file on my thread in the General forum at http://forum.xda-developers.com/showthread.php?p=13077026
Thanks a lot, I was unaware that the Canadian carriers used KB2. Currently I am using KB3 and I noticed that sometimes the call breaks up, however I am not sure if its the firmware to blame. Does anyone have similar experiences with KB3?
I have tested KB2 and KB3 and my tests are not constant. Sometimes I get only 1MB or less down and up, sometimes I get 5MB down and 3up.
I'm not sure why the tests are so different. I can do the tests one after another in the same place and get completely different results.
I am with Rogers and I am using the Speedtest app. I noticed at one point the speedtest app was connecting to a server in Quebec which made no sense since I am near Toronto. The test results I mentioned above do not take the Quebec tests into consideration.
Hello
I after some advice please. I went ahead and flashed recovery followed by 3.1 as detailed in the thread but then went and flashed the attached custom boot patch which I now realise was for verizon 3g xooms so now I have a perfectly working euro 3g xoom except I have no 3g or even any option to select mobile network.
I know before anyone says im an idiot but its done now so any help would be appreciated.
Thought I'd ask this one.
I am a UK 3G xoom owner and learning flashing, rooting, adb quite quickly.
I have flashed the Telstra stock to try and update using Simba90s directions (separate thread) and recovered.
I have flashed the US Verizon stock image and recovered from that (sweating buckets).
I have reflashed the UK stock and am working perfectly again but without SD support or any 3.1 enhancements.
My question is, as I seem others have done it, can I flash the US WiFi images to my Xoom and update as usual? No other adaptions, just stock.
I know I will lose 3G but am not worried about that. I want to check functionality and reflash UK stock when update is ready.
Flashing the Verizon stock images caused the "Failed image LNX 0x0002 / RSD mode 2" and deep panic.
xoomtastic said:
Thought I'd ask this one.
I am a UK 3G xoom owner and learning flashing, rooting, adb quite quickly.
I have flashed the Telstra stock to try and update using Simba90s direction (separate thread) and recovered.
I have flashed the US Verizon stock image and recovered from that (sweating buckets).
I have reflashed the UK stock and am working perfectly again but with SD support or any 3.1 enhancements.
My question is, as I seem others have done it, can I flash the US WiFi images to my Xoom and update as usual? No other adaptions, just stock.
I know I will lose 3G but am not worried about that. I want to check functionality and reflash UK stock when update is ready.
Flashing the Verizon stock images caused the "Failed image LNX 0x0002 / RSD mode 2" and deep panic.
Click to expand...
Click to collapse
As I said in your other thread, once you have AU 3.1 on you can flash tiamat 1.1 and keep 3G. I have 3G with orange working just fine.
Lordao
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.
Hoping someone can help here.
I have a TF101G (the 3G version of TF101). ASUS stock ROM works fine apart from the usual annoying problems with reboots and hangs. So I've tried a few custom 3G ROMs and Kernels.
Revolver (latest 3G) installs OK, but 3G doesn't connect - no APNs and can't add any, Search Network Operators fails with an error and Settings / About Tablet shows Baseband as Unknown. RaymanFX's new [DEV][WiP][3G/GSM] JellyBean for the TF101G - same deal. Everything seems to work except 3G.
Android Revolution HD 3.4.3 3G works fine which is great, but I'd like to try some others.
When I flash Stock or ARHD, on first boot it goes into setup with my location correctly preset to New Zealand. Neither Revolver nor JB seem to know where I am, and I'm wondering whether this has anything to do with the 3G not working.
I'm new to this, and to this forum so don't yet really know what I'm doing or have enough posts to be allowed to post in the Developer's area, so I'm hoping someone here might be able to point me in the right direction to get 3G working on either of these ROMs.
Thanks.
Having the same exact issue here