version 2.3.6 help - AT&T Samsung Galaxy S II Skyrocket SGH-I727

Ok guys so you all know about 2.3.6, well I have been manually checking everyday for about a month and still don't have it, does anyone have any advice for me?

ATT pulled the OTA 2.3.6 update two weeks after making it available OTA.... speculation being it was only provided for a select IMEI range. That said, you can peruse the I727 Development section for either the stock 2.3.6 tar or custom 2.3.6 ROM... but you'll have to flash it via ODIN or CWM Recovery.

There has also been speculation that the update was pulled because it was causing problems on some people's phones. I heard the claim that it was only for select phones (by IMEI number), that needed the update, but that explanation also said it only affected 3,000 phones--seemed to me that it was available to everyone who tried to get it when it was available.
I think it's more likely that there are issues with the 2.3.6 update (I experienced problems with bluetooth and a few other issues after the update, which may or may not have been the cause).
My advice is to stick with a 2.3.5 rom--there really wasn't much different with the 2.3.6 update and if there are potential issues with it you might as well stick with 2.3.5 roms (I've been digging NexusMod personally: http://forum.xda-developers.com/showthread.php?t=1426590 )

I downloaded and applied the 2.3.6 update to my SGS2 Skyrocket. Haven't noticed any real difference, except for a bug in screen dimming, usually with low battery levels (which I cannot recall if it existed prior to the update or not).
Sent from my SAMSUNG-SGH-I727 using XDA App

Umm, I have 2.3.6 and am having issues w/ reliably reconnecting w/ my Jabra Cruiser2 (BT speakerphone) in my car. I was thinking this is a Jabra issue, and not Samsung.
Can someone confirm if 2.3.6 is truly causing BT connection issues?

I see no need for it.

Related

[Q] New Froyo 2.2 For Captivate Bluetooth Voice Command Support

I installed the latest one click froyo 2.2 update to my captivate...and the phone still doesn't support bluetooth voice commands...when will they fix this? Is the captivate the only phone on the market that doesn't have bluetooth voice command support?
stewart2568 said:
I installed the latest one click froyo 2.2 update to my captivate...and the phone still doesn't support bluetooth voice commands...when will they fix this? Is the captivate the only phone on the market that doesn't have bluetooth voice command support?
Click to expand...
Click to collapse
You are using a pre-release beta software build. So making any judgments based on this build is premature.
Until there is a Galaxy S phone running an official 2.2 release, we will not know what is included and what is not. After the official build is out, we should be able to add what is missing.
BTW, this issue has been mentioned many times since the 2.2 build was available.
oh okay thanks....so will i be able to get the OTA update when it comes out or will I have to get from this site?
No one knows how Samsung will package 2.2. OTA is expected, but it may be to big and they may direct us to use Kies. I am sure XDA will also have it available along with many cooked versions.
The bluetooth is screwy on the leaked 2.2. When I turn off BT I get a notification that remote SIM is active, and that wont go away until I turn BT back on and off again.
That said the leaked 2.2 is still better IMO than any 2.1 build I've tried. If I wanted a simple, childishly easy phone I would go back to my iphone or get a dumb phone.
When you play and experiment take that into consideration when saying what your doesn't this and wont that.
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
The bluetooth is screwy on the leaked 2.2. When I turn off BT I get a notification that remote SIM is active, and that wont go away until I turn BT back on and off again.
That said the leaked 2.2 is still better IMO than any 2.1 build I've tried. If I wanted a simple, childishly easy phone I would go back to my iphone or get a dumb phone.
When you play and experiment take that into consideration when saying what your doesn't this and wont that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Same here with the remote sim message. I wonder if it has to do with the A2DP bluetooth profile...
There is a way
There is a way to voicedial over bluetooth on the Captivate, although not without a flaw.
1. You need to install Vlingo, it is available on the market, and it is free.
2. You need to use a headset that supports A2DP profile ( I can not explain this, but I know by experience of trying several headsets that only those supporting A2DP work)
3. In order to voicedial your screen has to be unlocked.
After the initial pairing, some headsets will only work after you hqave rebooted the device.
I am using the leaked 2.2.
Not sure if it will work on a Cupcake pone.
yet with all these problems people on here act if someone is crazy cause they cant wait for the official version to come out. There is leaked 2.2 roms and they are great they say. Yes there kool but again its not the one samsung intended for the phones which is why it was never released. I myself always find to many bugs with 2.2 to live with and cant wait till official comes out. After that we will begin to see a much better set of 2.2 roms less buggy and performing the way it was intended to.

Terrible Search Button Bug

Hello,
I have been experiencing a bug where the phone acts as if there has been a long press of the search button (and the appropriate dialog comes up) when I have not touched the search button at all! (I am not pressing it by accident, it will do this while sitting on a table untouched). When it happens, the search button is not lit up (as if it were pressed), and none of the other buttons can be pressed, nor can anything on the screen, other than responding to the dialog. This can last two to four seconds (it's REALLY annoying). What's worse is that this can happen up to once a minute sometimes!
I've discovered that this happens only when I have 3g data turned on. When data is off, or when on wifi only, it does not occur.
Is anyone else having this problem, and (hopefully) has found a fix? I did do a search (both on Google and in here). I discovered a Google forum where people talk about experiencing the problem (a Google employee chimes in with questions) but no solution as of yet. I was hoping to find something about this in Xda, but as stated, couldn't find anything Though this person may be talking about the same problem:
http://forum.xda-developers.com/showthread.php?t=1069765
Here is the link for the Google forum:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
Since it only happens when 3g data is turned on, could it be my radio image? Or something else? Any help or thoughts would be greatly appreciated! My current running specs below:
Nexus S
Android Version 2.3.3
Baseband version NO DGSXKD1
Kernel Version 2.6.35.7-g1 d030a7 [email protected] #1
Mod Version Cyanogenmod-7.0.3-NS
Build Number GRI40
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Rooted, bootloader unlocked
I was about to post this exact thread! I am having the same issue with my NS i9020a running stock unrooted 2.3.4. I to have noticed a link between data connection type and the issue occuring. One theory i read said that static charge may be to blame?... but that didn't seem right to me....
Anyway... I would also love some more info on this subject of anyone has any input. I bought my phone off ebay less than a week ago, and if the issue is hardware i am going to have to file a claim with paypal...
Sent from my Nexus S using Tapatalk
This is exactly what I posted in a separate thread. However, I'm not sure about the 2G / 3G changing.
I'll experiment.
Which radio are you using - seems like this was at least temporarily related to my switch to KD1 ?
Sent from my Nexus S using XDA Premium App
I reflashed radio KB3 and problem , at least for now is not happening. It was almost making the phone unusable this am earlier before changing radio
??!
Sent from my Nexus S using XDA Premium App
How can I find what radio I am using? Also, How long have the two of you had your devices? Is this issue something that manifested after you changed something on your phone (thus indicating it is not hardware related) or has it always been there? Thx, and i hope we can get this sorted out.
Cheers
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
jcrompton said:
Settings > About. Then look for Baseband version
I've had about three or four weeks. Not sure unless this radio change theory is correct
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Baseband Version
NO DGSXXKD1
Kernel version
2.6.35.7-ge382d80
[email protected] #1
Build number
GRJ22
Please update as to whether the radio change is a permanent fix. Thx.
Cheers
Edit: I am assuming that this (NO DGSXXKD1) is the KD1 radio that you switched to and are theorizing may be the culprit...it is also something that all three of our devices have in common. I am eager to see if changing the radio permanently fixes your issue.
I'm on a Telus 9020a radio KB3 and i have the same problem.
Not sure at this point what the deal is! But changing from the upgraded radio KD1 back to KB3 has up to this point solved the issue. Maybe six or seven hours without the phantom search firing.
????
Sent from my Nexus S using XDA Premium App
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Matridom said:
Currently there is no stock 2.3.4 for the i9020a. The no xxxxkb1 is a result of forcing the update from the t version. Since the a version uses didn't frequencies, I'm not sure about it's reliability.The ota has yet to be released and this tells me that our phone has something different
I see this issue also however I get it more when using gps. I have my phone vent mounted and I am suspecting heat might be the issue
Sent from my Nexus S
Click to expand...
Click to collapse
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Hey guys, got the Sprint Nexus S 4g just this last Friday. Phantom search button presses and long presses started up soon after. Still going on now. Have not been able to narrow down culprit as far as 3G/4G/Wifi go. Running completely stock everything:
Android 2.3.4
Baseband D720SPRKD8
Kernel 2.6.35.7ge382d80 [email protected] #1
Build Number GRJ22
Just thought I'd add my stat to the growing list.
Sophos1 said:
Interesting, I don't know what was done to my phone before it was in my possession but when I received it it was running stock 2.3.3 and on first boot after setup i received a popup notifying me that there was a system update available. I selected install and it did its thing and now I have 2.3.4. Is there a way to revert the device back to the software it is supposed to have on it?
Cheers
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I'm on my phone so it's as little hard to link. In the general section there is a thread to a stock nandroid backup with the kb3 modem.
Sent from my Nexus S
I've now been about 9 or 10 hours after switching back to KB3 - no more issues yet! Pretty strange huh?
Sent from my Nexus S using XDA Premium App
Finally got my device rooted and switch to the KB3 radio.... it's has been a few hours and I have yet to experience the search button bug. I'm crossing my fingers that you found the solution! Thx.
Sent from my Nexus S using Tapatalk
Ok. So it's now been almost 24 hours. No repetitive firing of the search button on my Nexus S since flashing back to the KB3 radio.
Beware anyone experiencing this should not flash to the KD1 radio. I have a 9020a device. I assume it is Canadian since it had ATT 3G bands prior to any mention of ATT devices.
I think they are all a bit different when it comes to hardware which baffles more when I read on a Google forum post about a T-Mobile device that was stock Ann's doing this.
Sent from my Nexus S using XDA Premium App
Where to dowload KB3 radio image? (And advice)
Hey jrcompton,
Wow, that's great news! I tried a bunch of things, including going back to stock 2.3.3 via ROM manager (am now on 2.3.4, as I was prompted almost immediately for an OTA upgrade), and the bug still persists. It seemed after returning to stock that the issue didn't present itself until after installing certain apps (Dialer 1, Handcent, Extended Controls) but after removing them, am still seeing the bug. Was thinking that maybe it was these apps and uninstalling still let some trace and another factory reset might be necessary, but your results give me hope! As it is, on mobile data the bug can present itself several times in a minute! (Making the phone almost unusable).
All that being said, any chance you could share where I could download the KB3 radio? I did search and was only able to find a thread with mostly Tmobile users, and was thinking that the radio in that thread might not be the right one. I'm on Bell, so sounds like the radio that you're using would be right for me (since your phone uses AT&T bands).
Also, never flashed just a radio before, and am a little nervous. I know that there are a ton of threads with instructions, but I hope it's ok if I ask a couple questions. I'm assuming that I download the image, and put it in my ANDROID-SDK-TOOLS directory, then just (in command prompt from that same directory) type "fastboot flash radio *********.img (with the phone in bootloader, and connected via usb). And that I should NOT disconnect, power down, touch, or even look at phone during process, and make sure that PC doesn't power down, reboot, etc. If all of that is correct, do I need to wipe/factory reset or anything else beforehand or afterwards?
Thanks so much in advance, and so glad that you've at least had 24 hours bug free!
If this works for me as well, will post in the Google help forum thread as well.
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
If this worked for you guys then that's great, but do you have any suggestions for a NS4G user? I realize we don't have our own subforum but up until that happens, we have to have our questions fielded here. I'm still getting the search button going nuts on me issue. have tried data off/only wifi and still doing it. Wondering if I just got a defective unit...
Sophos1 said:
I just downloaded the zip from here ( http://forum.xda-developers.com/showthread.php?t=975105
[RADIOS] 01/Mar XXKB3 (GRI54): Basedband (radio) only updates) and installed via CWM... worked like a charm
Cheers
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey Sophos1 (or anyone else who might know),
My Nexus is now running the following:
Android Version: 2.3.4
Baseband Version: NO DGSXXKD1
Kernel Version: 2.6.35.7-ge382d80 [email protected] #1
Build number: GRJ22
Model number GT 19020A (originally bought from a Telus Store) currently running on Bell Mobility
Would the KB3 radio that you downloaded for your phone work for mine? Also, just for confirmation, will I be ok following the steps that I listed above? Lastly, what's the worst that can happen if I flash the incorrect radio? Would I still have the opportunity to flash the correct radio (or reflash stock including the correct radio) via fastboot?
Thanks so much guys!

Need help with SGS Captivate after rooting. (radio issues).

I rooted and have been running CM7 for months never had a problem. Earlier today I started having trouble sending texts so I updated from Nightly 71 to nightly 75 thinking I stumbled into a nightly bug (which happens often) and this did not fix the problem. So I went to an old nandorid backup from 7-18-2011 and restored because that particular backup has always worked perfect for me. Still this did not fix my problem.
Then I got my big boy shoes on and downloaded Heimdall and a stock image of Froyo 2.2 for my Captivate. I followed the directions and downloads from here.
This did not fix my problem. I am currently running a 100% stock version of the phone now so I cant possibly think of any other way to fix this problem other than taking it up to AT&T and asking them if there is any way to have it sent out or to receive a new phone. As I think there might be a problem with the radio inside the phone.
I can still send texts on and off but I can not use data. My mother has an SGS Captivate running stock Eclair 2.1 (never been rooted or flashed) and she has FULL bars while I alternate between 1 and none. What gives??
Have you tried a different sim card?
UPDATE: All the sudden my mothers phone and my friends phone (AT&T Iphone) are reporting the same type of service issues. Maybe it was a service outtage in my area and my phone just saw it first? This is getting stranger.
Seems like AT&T issue, just wait 1 or 2 days and see if everything goes fine.

Gsm Problem

some time if any one call me but on my phone there is nothing happen i have not seen any incoming call and if some one send Text message but i can not receive message ...... after restarting the phone then every thing work perfect
some one help me to solve this problem
sorry for bad English
Do you flashed baseband for Gingerbread?
Sent from my LG-P920 using XDA App
I also encountered this problem when I flashed to V21a 2.3.5 and at some time, my P920 is unable to make or receive any calls as a result of 'internal system re-organizing' and I have no other choice but to flash back to 2.2.2 and now everything is working normal. I just wonder if the V21a baseband does not fully comply with P920 HK branded mobile phone..I will do that again when the HK version is to be released sometime in December 2011.
Make backup and try to wipe phone.
Hi guys, am using german 21a and am having troubles with signal too.
When I get out of tube i have no signal till i restart the phone, its annoying cause with froyo the phone found the signal in just few seconds, now am sometimes offline even half an hour till i notice it and rebooth the phone.
I also tried some other GB roms and its a really problem of the GB baseband and so am having the troubles with any GB rom - due to the baseband firmware. So am changing back to fully working 2.2.2
Hi!
I had the same problem. My phone was dropping signal after flashing the first leaked version and the gb baseband. Then it got worse, when I flashed the 21a kdz, wiping everything didn't helped.
Also my battery life was terrible, because of this.
The solution for me was:
- flash v10k (T-mob branded hun)
- wipe everything
- flash v21a (hun open)
- wipe everything
Now my phone works like a charm.
I've got a Hungarian T-mob barnded o3d.
Had the same problem with the leaked GB, and now I am having the same with the official release, I have missed out on two jobs this week, the Customer told me in an e-mail that I did not answer the phone when he called and he left a voice mail which I never recieved an sms notification telling me so, I also had loosing network issue and not getting it back until a restart, unless LG releases a specific baseband for Australia when the phone is released, I can't see myself using this phone anymore, under froyo the phone is crap and in gingerbread the phone as a phone is useless, so much for LG waiting this long to release a trouble free gingerbread for the O3D and all we got is all this crappy problems.
wencel said:
Hi guys, am using german 21a and am having troubles with signal too.
When I get out of tube i have no signal till i restart the phone, its annoying cause with froyo the phone found the signal in just few seconds, now am sometimes offline even half an hour till i notice it and rebooth the phone.
I also tried some other GB roms and its a really problem of the GB baseband and so am having the troubles with any GB rom - due to the baseband firmware. So am changing back to fully working 2.2.2
Click to expand...
Click to collapse
Have you tried to flash back to v10k baseband with flashtool and then flash v21a KDZ? After i did this, all my Mobile Data and signal problems are gone.
Sent from my LG-P920 using xda premium
Hi, well i changed to 21a from my original EU open 10K so i have been using 10K baseband before the change to 21a which is as per your post most important.
I now tried to reflash current 10K again and again (3 times in total), i wiped everything (even internal /sdcard ) and now i will flash to 21a again... will see during few hours if/how this works... Thanx for your tip! I will give it a try...
So after few days wiping everything i am still randomly loosing signal
GB sucks, sorry to say that. Am changing back to Froyo
somebody has the same problem with randomly loosing signal on GB ?
I have the same problem losing signal all the time when flashed to Germen 2.3.5, was left no other choices but to wait for an official release of GB 2.3 Hongkong branded..
wencel said:
So after few days wiping everything i am still randomly loosing signal
GB sucks, sorry to say that. Am changing back to Froyo
Click to expand...
Click to collapse
I went back 10 days ago to Froyo, I don't think I will use Ginger bread ever again, I will wait for Ice Cream, I am having Zero issues with 10D, battery life with low to moderate use is well over a day, no restarts and the signal is always great, I also had problems with audio quality with Blue tooth under GB perfect quality under froyo. I also had freezing problems under GB never under Froyo. my couple cents
Hey guys..the same here!!!! I am the spokesman for 10 people who have the same problem!!!!!!
Inviato dal mio LG-P920 usando Tapatalk
I'm having the same problem in Hong Kong. I have a Thrill 4G flashed with the V10k EU open O3D ROM, and is fine though not great. Now with V21a, the battery goes so quickly, especially in places where signal reception is poor.
Ah good, everybody was so excited with GB and nobody in the develop sections is not mentioning any bugs with signal at all, so i was almost shocked that my phone is somehow broken or incompatible with GB... now i understand the delay with GB, maybe its just they found the bug with signal and are trying to fix it... who knows.
However i am now back again at 10K EU and it works perfect. I miss the LED light at filming or taking stills in 3D but I better choose signal and be available for calls/sms rather than have a better camera in 3D but often out of signal and unreachable for others.
My 3G signal will diconnect suddenly after I upgrade to 2.3.5 too. Is it the bugs of the official 2.3.5 rom?
Yep I hope it is, cause when I used the stock official german 21a I had the issue to... so i belive it must be some bug in the GB baseband which is distributed in stock GB roms... bad bad
Hey,
I have this problem also. I get most messages which are sent to me however some don't make it through (so I am told). I have also had one occasion where a phone call didn't make it through.
Is this just happening on a handful of phones or is it a general thing?
I am in the UK and on Orange network.
I believe its a global GB issue, at least with the german 21a version. Several users from various countries using various providers have confirmed there's something wrong with GB. I'm using 10K at the moment and seriously thinking for replacing my LG 3D with iPhone 4S.....

[Q] Installing V21Y 2.3.4 Update and corrupting cell connection

I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
As far as I know from lurking on the G2x forums, only stock Gingerbread and a rooted version of stock Gingerbread are available. I don't think any third-party ROMS have call audio working. The reason is that the official update changed the baseband.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
By updating the ROM with LG's update tool to 2.3.4, u also updated the baseband, and if u read around the forums here for the G2x, you can easily find that none of the custom ROMs work with the new baseband because of compatibility issues, you can only use ROMs that are based off of the official 2.3.4 update but there arent any yet.
Although im quite surprised tech support said it was a known issue, i wonder how many other people have called having this problem because they dont read around.
Anyways, hope this helps clear things up
Sent from my LG-P999 using XDA
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Jlloyd97 said:
I flashed back to the lg provided Gingerbread this week and then upgraded to 2.3.4 using their tool. Could not get over the bloatware so ended up upgrading to ICS. I now have Eagles Blood up and running, everything is great, but I can only make Wifi calls. Every time I make or receive a call over Cell towers it's a loud clicking noise that both parties can hear.
I've tried multiple ROM's and re-installs(Hellfire/Eagleblood) with CM and AOSP versions and nothing resolves this, so I finally called Tmobile thinking maybe a cell tower reset would work.
I made it to level 2 tech support and this is a "known issue" with "incomplete" 2.3.4 patches. They basically read me a service bulletin explaining my exact issue, but the warranty is broken and they simply direct me back to the LG upgrade tool.
Has anyone else been able to recover cell tower calls on any ROM or did my G2x just become a tablet when not using GrooveIP?
TIA
Click to expand...
Click to collapse
All EB ROM's based on ICS are not compatible with the latest March bandbase.
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
kesara said:
You can downgrade to v21e July 2011 baseband if you want to use other ROMs.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
mustangtim49 said:
I don't want to seem lazy, but man, I've been looking all around for the "downgrade" baseband thread, where is it?
[email protected]
Click to expand...
Click to collapse
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
cricketAC said:
There isn't one. You use the same kdz method that ppl are using to update to v21y. just switch the 21y.kdz with 21e.kdz when using the method.
Click to expand...
Click to collapse
Yes
Sent from my LG-P999 using xda premium
Jlloyd97 said:
thanks for the quick responses. I read the ROM install instructions multiple times, but did not read about the underlying baseband since I was running Weapon G2x gingerbread with no problems and thought the 3 wipes recommended prior to the install would take me back down to a clean phone.
Appears I have a tablet till the updates are released.
Also, Tmobile tier 2 support had a KB item on this issue, but it was caused by earlier versions of the software update failing prior to completion and causing the SIM card/network errors.
Click to expand...
Click to collapse
Just look for the rooted version of the new update in the dev section by Kwes. Your phone will be fine then.
Sent from my LG-P999 using xda premium
Yup having the same issue with my friends phone. Someone mentioned downgrading the baseband, the only way I know how to do that is by using the tool that helps you unbrick the phone. please correct me if im wrong or have any idea what ive just said
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Whyzor said:
What exactly is the benefit of the new march 2012 baseband (other than breaking custom ROM compatibility at this point)? Looking for apples-to-apples comparisons of a custom ROM running with old baseband and new baseband (other than broken cell voice calls).
A similar ordeal happened for Virgin Mobile's Optimus V line, where a new baseband came out, everyone jumped on it, but it caused occasional random reboots and no apparent benefits, and couldn't be downgraded. Eventually devs had to apply fresh LG released kernel source code & recompile kernel for new baseband to be stable.
Click to expand...
Click to collapse
As much as I miss ics, the new baseband pretty much fixes everything. Battery lasts forever, GPS lock right now and I've seen accuracy to 3ft. No random rebooting. Fast, smooth, dripping butter everywhere. Other than that, no real reason to flash it.
[email protected]

Categories

Resources