[Q] Nexus S GT-I9023 with I9020 bootloader? - Nexus S Q&A, Help & Troubleshooting

Ok, so I own a Nexus S, the I9023 version.
The thing I find strange about this is the fact that when I go into fastboot mode (with the phone turned off, hold volume up + power) in the information section, it reads like this:
HW Version - REV 52
Bootloader version - I9020XXKA3
Baseband version - I9020XXKF1
Is this normal? Shouldn't there be any reference to the I9023 version?
(Currently running stock Gingerbread 2.3.6.)
P.S.: Forgot to say that in settings, the Baseband version is "I9023XXKF1".

Hi!
I have the same "problem".....I don't know if is the normal....

surdu_petru said:
I have the same "problem".....I don't know if is the normal....
Click to expand...
Click to collapse
My bad, it's not a real problem, it's just that I assumed the numbers would match... pretty strange, hope somebody knows where te difference comes from.
Sent from my Nexus S using xda premium

I've got the same issue.. on stock 2.3.6 i9023

Same here. Went from Bm's MIUI back to stock 2.3.6 for i9023 with thisthread as usual. Don't know what I had before but someone with a real stock Nexus could check? Meanwhile, waiting for the ota.

it's normal , becuase first of all only i9020 version , and then due to shortage of SA screen so there is i9023 , basically everthing is same , except screen is Super Clear LCD and some of them has different radio frequency

True, just flashed new bootloader I9020XXKL1 and radio I9020XXKI1 on my i9023 via fastboot without problems

Thanks. Still waiting for ICS ota, if nothing happens today I'll flash the first zip I find tomorrow.

Same problem
Also i am unable to "ON" developr option

Related

[Q] Anyone have a stock 9023 and a minute time?

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

[Q] lost my 3G, i only have EDGE network

I live in Canada and my provider is Rogers.
I have play with custom rom, but was tire of them, so i decide to put back my nexus s on stock rom.
I have push the file that i found here version 2.3.3 http://forum.xda-developers.com/showthread.php?t=1063664
Then i let the auto update do the reste. every thing was ok accept that now i cant connect to the 3 G network, i only have edge connection.
I have try to push version 2.3.4 and i got same results.
i have also try Alot of reset to factory default.
here is my phone infos
android ver. 2.3.4
baseband version NO DGSXXKD1
Kernel 2.6.35.7-ge382d80 [email protected] #1
build number GRJ22
Thanks to anyone that can help me.
Marc
Last week i had same problem, i almost got crazy, but after all, the problem was in my provider.
Have you tried another sim card?
Sent from my Nexus S using XDA App
That is odd...
I am also with Rogers and I got my phone bricked when I first tried to root it because some guy posted a wack file which bricked almost everyone's phone..
Anyways to the point... I also got the same stock image from the link you posted but for the 2.3.4 update I got it from searching on google somewhere. (Think it was one of those "How to manually update Nexus S to 2.3.4" pages).
I just checked my phone info and it displays all the same info as yours... I am pretty sure I had 3G even before pushing the 2.3.4.... Try locking the boot loader and re unlock and give it another shot. If nothing works, just lock the boot loader after you install the 2.3.4 update and take it back to rogers and ask them to send it in for a fix.
hi guys... thanks for trying to help me...
I was going to return my phone when i found this thread about radio
http://forum.xda-developers.com/showthread.php?t=1116884
i have try KB3, KD1 and finaly the working one, UCKD1.
my phone is up and runnig as it was....
Now i think iam going to try other radio (ope i wont kill my phone....lol)
Thanks again.....
Marc

Think My Baseband is DONE FOR!!!

Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
can you install a stock rom back onto it? There is a baseband selection mode that you may have to do.
http://forum.xda-developers.com/showthread.php?t=1116884
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
Ive had to run this a few times depending on radio and rom.
after many trials I am sticking with rooted stock.
Wow that is defiantly a menu I have never seen before.
It doesn't let me select any of the preferred carrier option. When I tap on GSM auto (PRL) it just closes and defaults back Unknown.
It's ded?
Sent from my HTC Phone
thepyro6 said:
It's ded?
Sent from my HTC Phone
Click to expand...
Click to collapse
Ya, I think it is. RIP Nexus S. HTC Sensation here I come.
after you select gsm auto you hit the menu button on your phone then select the carrier. I know its not labeled what it is on the walkthrough but its similar. not phone frequency but like signal or something. then yuo jsut select usa.
reboot and it should find whatever your service is on its own.
have you tried going back to stock rom? I used this version to go back when i thought i bricked out my phone and its been great. I think my friend used it too but he wont admit he used somethign i gave him.
http://forum.xda-developers.com/showthread.php?t=1060192
http://forum.xda-developers.com/showthread.php?t=1038007
Same issue also involved the trinity kernel. Dev may need to be notified.
kmmxracer said:
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
Click to expand...
Click to collapse
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
No im absolutely sure i flashed the right ROM. Peter Alfanzo was a ROM i flashed after this issue happened. It was the CM7 nightly + Trinity kernel that did me in...
Sent from my Nexus S using XDA Premium App
simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Canehdianman said:
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Click to expand...
Click to collapse
have you tried reformatting all your phones partitions?
simms22 said:
have you tried reformatting all your phones partitions?
Click to expand...
Click to collapse
I've wiped user data/factory reset a few times now. Is there a higher-level format option that I should be using?
I thought for sure that going back to stock (based on these instructions - theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/) would work, but no such luck.
I find it perplexing that the baseband shows in fastboot, but nowhere else. *#*#4636#*#* shows radio off and network type unknown, settings/about phone/ shows baseband version unknown.
I tried different methods that I've found online over the weekend, but nothing has brought my radio back.
I am certainly open to suggestions!
I'm going to provide as much additional information as possible.
I have a Nexus S I9020A, running on Fido (Canada).
My initial problem stems from when I updated to cyanogenmod 7.1 from 7.0. My first (and likely biggest) mistake was not making a backup. Oops.
I think I accidentally chose "Nexus S 4G" instead of "Nexus S". As soon as I did that, I stopped getting any cellular voice or data connection (wifi continues to work fine). Under Phone Information, it said it was a Nexus S 4G.
The phone locks itself into airplane mode now. When I try to turn airplane mode off through the settings menu, it hangs. When I hold down power and choose "turn airplane mode off" it seems to work, but then I still get no signal.
I have pushed it back down to stock. It now remembers that it is a Nexus S (not 4G), but it didn't help the baseband problem.
I have tried to reflash the baseband. no effect.
I called Fido and got them to "repush" the SIM card. No effect.
I am humbly appreciative of any and all help that anyone can provide!
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Thanks! This is similar to some other threads I saw on the android forum (and elsewhere on XDA).
I'll try this when I get home (and get to a reliable wifi signal).
Wow! I haven't looked at my post in a wile. Hopefully you all are getting some resolution to these issues. I ended up calling Samsung and they agreed to fix my Nexus under warranty. They replaced some parts that I can't remember off the top of my head, but it should arive at my door tomorrow!!!
Sent from my HTC Sensation 4G using xda premium
YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Hmmm bad news... my efs folder appears to be empty. Now what?
A very frustrating day... Thought i would have it fixed pretty quick, alas....
My efs folder is empty. I guess that explains the lack of radio, but it appears that i might need to send the phone to Samsung to get the efs reflashed. Is there a way to write it back myself? Ill look tomorrow i guess.
Here is some more info:
I just tried to update to 2.3.6
Clockwork mod is giving me an error message:
Assert failed: getprop("ro.product.device") == "crespo" || get prop("rp.build.product") == "crespo"
E:error in [filename]
(Status 7)
Installation aborted
Not sure if that helps but it's another piece of thepuzzle hopefully.
*sigh*
So it appears that I need a backup of my /efs folder in order to fix this myself (which I do not have).
I know what my IMEI should be, however I have no idea if it is even possible to take someone else's backup and alter it the proper IMEI.
I fear my next option will be to submit it for repair at a Samsung repair shop (and be without a phone even longer )

CRT screen off animation gone with Jelly Bean OTA.

Anyone else noticed it?
Mine works perfectly fine. Make sure your animation for Window is set to x1.
I have the same problem on my Nexus S I9023. It feels weird...
same problem here i9023.. crt not work
Mine works 1 time out of 30 i guess . I9023
Sent from my Nexus S using xda app-developers app
it seems to be a problem only related to 9023 SLCD looking to replies...
(I9023 SLCD here, and CRT animation working 1/30 times)
i got an i9023 aswell
My used to work, now it's nothing.
the problem looks to be only on the I9023 model (which i have) like raducux mine goes once every while.i think we should be able to work on a fix,the problem is probably with "services.jar" i decompiled the "framework-res.apk" and everything looks fine there (i checked the bools) so am gonna take a look at services and will try to work on a fix for this.
i9023 here. same annoying issue
Same here. i9023.
(But sometimes I see it... just not most of the time. I hear "click" though, when screen is already off)
window animation is set at 1.
imbehind said:
Same here. i9023.
(But sometimes I see it... just not most of the time. I hear "click" though, when screen is already off)
window animation is set at 1.
Click to expand...
Click to collapse
I can confirm I have the same problem on my S-LCD screen.
any fix pls ?
tumbHo son
Would be super cool if someone could upload any kind of a fix for this. That's the only thing that's pissing me with 4.1.1
do you also have this bug when you updated 4.0.4 to 4.1.1 OTA via the system update (not manual flashing) ?
asphantix said:
do you also have this bug when you updated 4.0.4 to 4.1.1 OTA via the system update (not manual flashing) ?
Click to expand...
Click to collapse
I always had this bug on any type of 4.1.1. SDK port, AOSP, manual upgrade in cwm from stock 4.0.4 fastboot images. I even tried that "official OTA" from this thread:
http://forum.xda-developers.com/showthread.php?t=1784497
Now I'm on 4.1.1 which I got by installing this update:
http://android.clients.google.com/packages/ota/google_crespo/9ZGgDXDi.zip
CRT animation was active for a while, then just stopped working.
working on fix here (can't promise anything though ) i would be happy if someone can provide me with ICS 4.0.4 "framework" odexed or deodexed just to save me some time.as i said before the problems seems to be with services.jar which i deodexed and decompiled in order to start working with it but i still need the 4.0.4 framework to compare with.
i do this step : Stock 4.0.4->Unlock bootloader wipe data->Flash Cwm->Flash 9ZGgDXDi.zip->Boot->Lock bootloader-> After Wipe data and cache from Android Recovery and factory reset from settings .. the first time work i think but after no...
so you think everyone gets the 9ZGgDXDi.zip? Maybe google rolls out a different update for i9023 that's why I asked if anyone updated via the standard google update process.
asphantix said:
so you think everyone gets the 9ZGgDXDi.zip? Maybe google rolls out a different update for i9023 that's why I asked if anyone updated via the standard google update process.
Click to expand...
Click to collapse
no google usually roll the same update for i9020 and i9023 the only difference is the display the problem could be with backlight oe other related screen things,like the problem we had with 4.0.3 recovery.

[Bug][Solved] Can't make or receive calls when Wifi is enabled

For a week or two now, I've been having a strange issue, if my WiFi is on I can't call or people who try to call me get the notice that I'm unreachable.. SMS works fine. If I disable WiFi and use mobile internet everything's fine.
Don't know what triggered this?!
I don't have the time to investigate properly, so I thought I'd throw it on XDA..
I have flashed different Radios and a few 4.4.4 AOSP Roms, no luck..
Greetz
Tim
I would flash the factory image and see if you still have the problem. If you do it's probably a hardware issue and I'd rma the device
Sent from my Nexus 5 using XDA Free mobile app
not hardeware issue , LG have problem on nexus 4/5 on kitkat versoin , bug already repot but no solution yet
hitibiti said:
not hardeware issue , LG have problem on nexus 4/5 on kitkat versoin , bug already repot but no solution yet
Click to expand...
Click to collapse
Thanks for the info.. Do you happen to know since what version it appeared? Thanks again for the heads up!
Flashed the stock 4.4 ROM and bug still exists, has it always been there and did I not notice it all this time..? Weird..
Greetz
Tim
TimHermans said:
Flashed the stock 4.4 ROM and bug still exists, has it always been there and did I not notice it all this time..? Weird..
Greetz
Tim
Click to expand...
Click to collapse
ok fixed 3 phone now , what i exactly do
1) Flash only the radio (without wipe device) phone work well no problem 2G ,3G,LTE ( before just working 2G and rarly ) , but when i make call , call end after 1mn on both phone , for repair :
1) unlock boot loader
2) flash it with original room from thsi site : https://developers.google.com/android/nexus/images using same versoin on phone
cause my 2 nexus 5 one : 4.4 and second 4.4.3
so for conclusion to repair you eed to steps :
1- flash radio (same version on phone)
2- full flash phone with same version (ex if it was 4.3 so use 4.3, if 4.4 use 4.4)
hitibiti said:
ok fixed 3 phone now , what i exactly do
1) Flash only the radio (without wipe device) phone work well no problem 2G ,3G,LTE ( before just working 2G and rarly ) , but when i make call , call end after 1mn on both phone , for repair :
1) unlock boot loader
2) flash it with original room from thsi site : https://developers.google.com/android/nexus/images using same versoin on phone
cause my 2 nexus 5 one : 4.4 and second 4.4.3
so for conclusion to repair you eed to steps :
1- flash radio (same version on phone)
2- full flash phone with same version (ex if it was 4.3 so use 4.3, if 4.4 use 4.4)
Click to expand...
Click to collapse
First of all thanks for the help!
But I'm a bit confused, so I first flash radio without wipe, but which one? And after that I flash stock google rom, but which one?
Sorry for the difficulty..
Greetz
Tim
TimHermans said:
First of all thanks for the help!
But I'm a bit confused, so I first flash radio without wipe, but which one? And after that I flash stock google rom, but which one?
Sorry for the difficulty..
Greetz
Tim
Click to expand...
Click to collapse
when you receive this problem just go menu about and scroll down , you will see KTU84P or TU84M or other , so you need just to flash this one as same version i men if you cell KTU84P so use same to Radio file
and for wipe device , you do it or no , no problem because on my shop i reveice allot of phones so no have time to backup i just flash radio to preserve information for customer and 60% working and network 3G/LTE fixed if not fixed so you need to pass to second step (full flash )
for full flash i use : Factory Images "hammerhead" for Nexus 5 (GSM/LTE) from thsi site : https://developers.google.com/android/nexus/images
ask me any time if you still need help
hitibiti said:
when you receive this problem just go menu about and scroll down , you will see KTU84P or TU84M or other , so you need just to flash this one as same version i men if you cell KTU84P so use same to Radio file
and for wipe device , you do it or no , no problem because on my shop i reveice allot of phones so no have time to backup i just flash radio to preserve information for customer and 60% working and network 3G/LTE fixed if not fixed so you need to pass to second step (full flash )
for full flash i use : Factory Images "hammerhead" for Nexus 5 (GSM/LTE) from this site : https://developers.google.com/android/nexus/images
ask me any time if you still need help
Click to expand...
Click to collapse
Finally!
I managed to fix it.. W00t!!
I think I get it now, I tried reflashing factory image, KTU84P latest for me (I'm in Belgium), but that didn't work, then I thought about wat the stock rom was when it was shipped, I guessed it was the KOT49H build, so I kept the system image from KTU84P and flashed the radio image from the KOT49H build and voila! it worked.. So I think you have to flash the radio that the cellphone was originally shipped with..
Anywayzz I'll keep you posted how things end up when I flash other roms again.
Thanks again for the advice hitibiti !!
Greetz
Tim
TimHermans said:
Finally!
I managed to fix it.. W00t!!
I think I get it now, I tried reflashing factory image, KTU84P latest for me (I'm in Belgium), but that didn't work, then I thought about wat the stock rom was when it was shipped, I guessed it was the KOT49H build, so I kept the system image form KTU84P and flashed the radio image from the KOT49H build and voila! it worked.. So I think you have to flash the radio that the cellphone was originally shipped with..
Anywayzz I'll keep you posted how things end up when I flash other roms again.
Thanks again for the advice hitibiti !!
Greetz
Tim
Click to expand...
Click to collapse
you are welcome any time
and don't forget for all nexus you need unlock boot loader to allow flash different modem firmware
hitibiti said:
you are welcome any time
and don't forget for all nexus you need unlock boot loader to allow flash different modem firmware
Click to expand...
Click to collapse
I know..
**BUMP**
So i've been f****** around some more and found out that I only experience the no calling during wifi bug using a modem version radio-hammerhead-m8974a-2.0.XX.X.XX I can always fix it again by flashing a previous version starting with 1.0.XX.X.XX this is all on stock rom on every android version. Running LRX21O now with radio 1.0.25.0.23
Still think this is some weird sh** and why only handfull of people have this?
So simply said: from radio v2 upwards (which came with 4.4.3 update) when wifi is enabled I can't make calls and people can't call me..
Greetz

Categories

Resources