I just recently rooted and upgraded the baseband on my Dinc. When I upgraded it, all appeared to go well. When I rebooted the phone, the new Droid splash screen appeared, etc...
However, my problem is the baseband is still showing 1.00.03.04.06 instead of the 2.05.
Can I please have some help. Thanks!
Ok, I just realized that I was still rooted when I did this update. That could possibly be the problem because looking back I recall it saying something about ignoring multiple radios...
Do I just need to go back and revert it to stock? Or is there a special procedure I need to do because I already attempted to install the radio?
Related
Hey everyone - I recently flashed Android 2.3.4 onto my 9023 just to give it a spin and I noticed that the bootloader was also being flashed.
Now I reverted back to the nandroid backup of the cm7 system I was using before but I'm a bit confused because fastboot tells me the bootloader version is I9020XXXKA3 and I'm not sure that it wasn't somethin with 9023 before
So if anyone is running (prefereably stock) 2.3.1, 2.3.2 on their 9023 or at least has never flashed 2.3.4 I'd be really interested to know what their bootloader says.
Especially since I'm having some hardware problems and might have to send the thing is. So to make it appear untouched it'd be good to knwo whether I need Odin or just a stock rom....
Thanks in advance
Just nandroid restore your stock 2.3.4 ROM, restore stock recovery, lock the bootloader. Your phone will be fully stock again, and it's perfectly sensible to have updates installed on your phone since purchase, so I wouldn't worry about it.
gotjazz said:
Hey everyone - I recently flashed Android 2.3.4 onto my 9023 just to give it a spin and I noticed that the bootloader was also being flashed.
Now I reverted back to the nandroid backup of the cm7 system I was using before but I'm a bit confused because fastboot tells me the bootloader version is I9020XXXKA3 and I'm not sure that it wasn't somethin with 9023 before
So if anyone is running (prefereably stock) 2.3.1, 2.3.2 on their 9023 or at least has never flashed 2.3.4 I'd be really interested to know what their bootloader says.
Especially since I'm having some hardware problems and might have to send the thing is. So to make it appear untouched it'd be good to knwo whether I need Odin or just a stock rom....
Thanks in advance
Click to expand...
Click to collapse
Hi,
I am also facing same issue. After updating to 2.3.4 my i9023 fastboot shows baseband as I9020XXKD1 and Bootloader as I9020XXKA3. Even I am worried. I bought it yesterday only and I manually updated to 2.3.4 from full rom google link for i9023. In about section the device still shows baseband as I9023XXKD1. Even I am bit scared and completely confused! I also found that MUMBAI MTNL DOLPHIN sim card connection is no more getting HSPA connection but only 3G!
Check my detail issue here http://forum.xda-developers.com/showthread.php?t=1056062&page=44 POST NO. 436
Nevermind. I didn't search well enough before. I found a post with it and just restored it.
Hey All, I need a stock nandroid of 2.3.3. Here's my dilemma. I updated to 2.3.3 through the LG update tool and then my phone started acting all crazy. I then decided to revert back to 2.2.2 using this tread and it still didn't solve the craziness.
http://theunlockr.com/2011/05/23/how-to-unroot-the-t-mobile-g2x/
I contacted T-Mobile and I have an exchange on the way, but I told them that I have 2.3.3 on the phone and I would like to return it to them that way. I tried just updating the phone again with the LG update tool, but for some reason it thinks I still have version V21E. Any help would be appreciated.
Thanks All!
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.
I used odin when the 4.0.4 official leak was posted here. I since uses the one click software restore back to 2.3.4. At first it gave an issue with the radio. On my phone while restoring it said "radio fail" but the phone seems to be working.
Now I manually updated the unrooted Sprint official 4.0. And my phone since the very first thing I said, has been randomly rebooting, I tried a different battery and it does the same thing. It's also real laggy. Any advice? Are there stock 2.3.4(7) files I can odin? I want it completely factory. Or suggest the problem? Thank you.
Bumping
So ever since yesterday I've been able to use WiFi. I was chromecasting something and while it was casting my phone went through a reboot, thought nothing of it since its happened lately. Well i think it did it a few times. Well I check my phone after my show is over and my WiFi is off., and I can't turn it on. I rooted my phone last night since it was unlocked already from when I had it rooted before. It's on Android 6.0 right now. I was just wondering if anyone had any ideas of how to fix it. I was getting a logcat error in reference to the wifistatemachine.
Did you try flashing an older stock rom?
I have a phone with the same problem and it believe it is a hardware problem because stock and custom kk, lp, and M ROMs do not solve the problem. After swapping out the motherboard, everything was fine.
I have not yet. I was trying to create a nandroid backup first, but NRT doesn't seem to want to let me do that because i don't have a modified boot image.