[Q] Uk 3G Xoom and US Rom - Xoom Q&A, Help & Troubleshooting

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

Related

[Q] Help. Flashed my Telus Nexus S with ATT firmware, now network type shows GPRS.

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.

Lost 3g modem on uk 3g xoom

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?

Lost all service on Nexus S 4G PLEASE HELP!

I am from Canada and i am a noob so i was plyaing around with my phone earlier today when i installed a "bad" rom. Since i am from Canada, my phone is a i9020T, it is a Nexus S 4G, and any other info you would like, i would love to give it to you. So when i installed the bad rom, it put me on a whole other carrer called sprint, which is in the United States only so my phone is currently useless. I would just LOVE to go back to my stock rom and just go back to normal, and never flash any more roms again, its very scary. Please CAN ANYONE HELP!!! I NEED MY PHONE!
i9020T is not the 4G (CDMA), it is the T-Mobile (HSDPA 900/1700/2100) version. There is no need to go back to pure stock, just keep this in mind next time - you want that radio (which is the same as the i9023).
To answer your question though, go to this thread in the general section (stickied) and download your preferred version of i9020T FULL ROM. I'd recommend 2.3.6 (gingerbread) or 4.0.3 (Ice Cream Sandwich, the latest but possibly a -few- bugs, though i havn't found any). Download these, put them on your sdcard and flash them in recovery. I'd highly recommend doing a factory data reset, format /system and format /boot. Do this first, and then without rebooting flash the rom from the sdcard.
You should be up and running in no time, this is just a learning experience
My phone is 9020t. It is a Verizon galaxy nexus.
This is common theme tonight on the forum. Don't know what phone you have. Flash things anyways ....
It didnt work it keeps coming up as status 7 error! i cant flash anything! well i can flash this 1 rom but for some reason that one works and these dont! PLEASE HELP!
kwiboo-ics-v3-crespo4g.zip
That is the file i am able to flash but i cant flash the ones you told me too .
Update your clockworkmod recovery. Then flash a working radio.
you are going to need to use fastboot and flash a stock i9020t rom and radio. If you do not understand what I am telling you....do some reading.....
Sent from my Nexus S 4G using xda premium
Update your clockworkmod recovery (fastboot flash recovery recovery.img), you can get it from clockworkmod.com/rommanager. Download the Nexus S variant. After this you should be able to flash it.

[Q] Cannot activate my xoom w 4.1.2

I had a MZ600 (yes, 3g only) which was running EOS 3 stingray build 150...... I want to now get it activated with verizon and they say they can do it, but for some reason it fails every time they try.
In attempt to fix the issue I have flashed the more approp eos 3 cdma stingray nightly, but have had the same issues....
What should I do next? Should I...
Do a data/system format and try the eos cdma stingray again? (would need quick refresher on this one, so I dont end up wiping TOO MUCH to still do the flashing through twrp)
Do a adb to some stock rom (would need help finding the correct files for this option)
Something else?
Thank you in advance for any advice you might have, but hurry.... ive got a itchy flashing finger.....
airboss78 said:
I had a MZ600 (yes, 3g only) which was running EOS 3 stingray build 150...... I want to now get it activated with verizon and they say they can do it, but for some reason it fails every time they try.
In attempt to fix the issue I have flashed the more approp eos 3 cdma stingray nightly, but have had the same issues....
What should I do next? Should I...
Do a data/system format and try the eos cdma stingray again? (would need quick refresher on this one, so I dont end up wiping TOO MUCH to still do the flashing through twrp)
Do a adb to some stock rom (would need help finding the correct files for this option)
Something else?
Thank you in advance for any advice you might have, but hurry.... ive got a itchy flashing finger.....
Click to expand...
Click to collapse
The radios probably need flashed to the ICS version http://goo.im/devs/teameos/radios/imm76l-radios-update.zip and you will need to use the latest Rogue recovery CWM Rogue Touch v1.5.0 to flash them (the rest of the recoveries will not error, but they will also not generally successfully flash the file.)
airesch said:
The radios probably need flashed to the ICS version http://goo.im/devs/teameos/radios/imm76l-radios-update.zip and you will need to use the latest Rogue recovery CWM Rogue Touch v1.5.0 to flash them (the rest of the recoveries will not error, but they will also not generally successfully flash the file.)
Click to expand...
Click to collapse
thank you!
.... did as you suggested and all went well .....
but then......
I called verizon and it still failed to activate...... uggggg....... now what?
I think that Im game for even going back to the stock verizon route...... just need to know how exactly to do even that......ive got way too many solutions rolling around in my head, I can no longer make sense of any of them though! Hand holding may be required here..... sorry
Rootzwiki links because Motorola has removed their old page and I don't remember where else to get them. You will need fastboot on your pc to do this and flashing the images will wipe everything off your Xoom, so copy/backup everything you want to save up onto your pc/external sd card before you do so. The fastboot commands are also listed in the link I posted.

Flashed GSM/UMTS to CDMA and bricked radio&wifi

Before I post in the CM forum, thought I would try here first.
I am a very experienced flash/mod user and have never had a "brick" issue in many years of tinkering with dozens of devices. I have been using Cyanogen and AOSP roms since 2008.
Today, I thought I would try a CM12 build on an XT1031(cdma) knowing that even though CDMA is not operational, CM builds are unified anyway. I figured it wouldnt be like flashing a GSM ROM onto a CDMA device. Well, I guess I was wrong...
It appears that CM12 builds are indeed GSM specific, and though the ROM installed and ran correctly, it seems to have corrupted both wifi and cellular radio at very deep level.
I fastboot flashed back to 4.4.2 stock, and it boots fine. Wifi connects and grabs an IP but doesn't transfer data, and cellular stays as a black triangle. It seems to grab MIN and phone# and has correct MEID.
Eventually, after 60-120 seconds the phone will crash and reboot.
I have tried flashing stock radios from the thread here, and have also tried several other falcon stock and CM11 roms. They all exhibit the same behavior...boot fine, no networks, and crash after a minute or two.
I find it hard to believe that flashing a ROM would physically damage BOTH wifi and cellular radios. One or the other I could understand. But this seems like a deeper problem at a base level of the phone...below ROM or firmware.
Is it possible that changes were made at at the /persist level? Is there any way to reflash the /persist partition with a stock image?
I have access to bootloader and recovery (currently TWRP). Any suggestions are greatly appreciated.
I really just want to get wifi working... plan on using it wifi-only anyway. But it would probably be good for the community to document the problem and see if we can figure out what caused it and if it is fixable or "brick-worthy"
Thanks!
Sent from my XT1028 using XDA Free mobile app
Got it fixed.
I didn't notice, but the CM12 build automatically upgraded the bootloader to 41.13. I was not able to fastboot flash the motoboot.img and boot.img files because they were the wrong version. Once I flashed it with a 4.4.4 version of motoboot.img and boot.img, I was able to flash the system partition back to 4.4.4 stock and it is working 100%.
So, if you are reading this and are in a similar situation with "preflash validation failed" or other "downgrade" errors, check your bootloader version. If it is 41.13, you will need to manually flash 4.4.4 images.
Now, I am just stupid enough to try this again...this time with a custom modem/radio image

Categories

Resources