Related
This has probably been answered before by one or two people, but I'd rather know from the whole lot of you brave souls who have switched from yakjuux to yakju.
I'm specifically wondering from those of you that have done the COMPLETE switchover to the yakju build... that includes ALL things that come with it, including it's radio.
I know we can flash the KL1 radio on top, but I'm not looking to do that. I want the entire thing to be from Google, and keep it as such. From what I understand, when you have the yakju build, and the KL1 radio, you will not get OTA updates automatically, thus having to flash manually. On the flip side, if its a complete yakju, including the radio that comes with it, you will get the OTA updates automatically.
So here's the questions:
1. Have any of you flashed the yakju build on your phones KEEPING THE RADIO that is a part of that build? If so, what are your experiences with reception/data specifically on the Bell Network? Any difference that you've noticed?
2. Am I wrong in my thinking? If you did flash yakju, then the KL1 radio, will you definitely receive OTA updates automatically? As in no real user intervention other than clicking "update"?
I want to be sure before I do this, because I cannot find a complete image of the yakjuux build that includes everything including the bootloader in case something goes wrong/or doesn't update the way a true Google experience should.
Please let me now.
Thanks
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
superlj said:
I am running stock 4.0.2 with everything from the official image. No problem with signal. What is your worry?
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Just want to make sure the radio from the official build works properly with Bell.
Don't really want to create a Frankenstein build so too speak by adding different radios
Sent from my Galaxy Nexus using Tapatalk
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
torradan said:
I changed mine to yakju shortly after I got the phone, about two weeks ago.
I haven't noticed any difference with the radio, good or bad. Still no issues with reception or anything dropping out.
Can't tell you about the OTA updates though, haven't received anything yet to go past 4.0.2. If/when I do, I'll update my reply to help everyone else out.
Click to expand...
Click to collapse
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
bump. bump.
why are you so worried about receiving ota automatically? since you are on xda and know how to flash you will always have the latest build. Being in canada we usually are slow to get updates(Galaxy Nexus is still on 4.0.1 here) so whats the point in waiting for ota. if you are planning to flash an update now why not do it again when a new one comes out.
btw to answer your questions about the radio, the stock one,XXKK6, will work fine with bell although UGKL1 seems to work better for me on Fido. UGKL1 is probably the radio that your phone has now. it was on my stock fido GN.
I flashed the entire package, including the xxkk6 radio.. Works perfectly fine on Rogers, no comment for Bell but should be fine. Just try it, flash it back if you don't like it. Takes all of 2 minutes.
From what I understand (and I'm still new to this as well) you need to use the radio that comes with the official image otherwise you won't get OTA updates associated with that rom.
Newbie account so I can't post links yet but search "galaxy nexus upgrade to official roms yakju build" and its the leemn wordpress blog that says:
"After flashing to yakju build, you can still receive notification of the OTA updates.If you have flashed the radio, system, userdata and boot partitions, and you still have the stock recovery (or have flashed it) from the 4.0.2 image, you will be able to install the updates. However, if you flash a different radio, or different kernel , or a custom recovery, you will need to flash back the stock ones first before being able to install the update."
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
I flashed it all.
Works great. No issues. I also wanted 100% stock and so far, i am very happy with it.
greeced said:
Thank you for your reply. Just to clarify, you are using the stock radio that came with yakju? I think its KK or something? Or did you change over to KL1?
Click to expand...
Click to collapse
Sorry missed your question, but I'm using the KL1 radio.
I am with Fido and have complete 4.0.2 stock rom. I had some strange issues with signals but everything is fine after I changed to a new SIM.
Sent from my Galaxy Nexus using XDA App
greeced said:
That's the whole thing.
When I was on the SGS, I tried a while slew of custom roms as well as the European beta builds.
I wasn't worried about doing that because there was always a way to go back to KG3, by spoofing the firmware to make KIES think it was on JL2. KIES would download KG3 officially back to the phone.
I always seemed to revert back to stock because none of the beta or custom roms seemed to work efficiently for me the way the stock one did.
I know, I'm strange.
So that experience brings me here. Without an official download of the yakjuux build available (bootloader image), there really is no going back if something just doesn't work as intended. (remember, we all use our phones differently).
That's why the fright. I just don't want to get to the point that this Canadian incarnation starts having an identity crisis.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm not sure what the problem is. When you unlock your bootloader, you just do a nandroid backup, and it backups up your system, data, recovery and boot partitions. The radio is already available. So you can always go back to "stock" yakjuux in case yakju doesn't work (which it obviously does for Canadian users). I've even posted a nandroid backup of my yakjuux build before I flashed yakju. There is a thread in the general section. And to address your concern about "always reverting to stock", yakju IS the stock ROM, it is not a beta or a custom ROM.
The bootloader has nothing to do with yakju or yakjuux or whatever. It will not affect anything related to getting an OTA update or installing an OTA update. Keep your current bootloader if you are worried about not having a backup, and go ahead and flash all of the other images (after backing up your originals of course). That way, you can always return to your yakjuxx if you think there is a problem. Just because you didn't flash the bootloader that came with the latest yakju image does not at all mean you are not using yakju, and I would not call it a "frankenbuild" -- think of the bootloader as the BIOS in a computer. You computer is running Windows regardless if you are using an ASUS P5Q motherboard, or an ABIT IP5 motherboard -- both have different BIOS, but the OS is still Windows. Same with a GN -- you are running yakju regardless of whether you bootloader is 10, 14, 15, etc.
EDIT: To specifically address your question number 2 -- if you flash the system, data and boot images from yakju, you are running yakju, and you will receive the notification for an OTA update when it is available. However, you will not be able to have it install automatically if you don't have the radio image that came with the yakju build and a stock recovery (they are all the same). You can, however, flash those back as soon as you receive the OTA update notification and it will install automatically. Bootloader has no relevance whatsoever.
Great explanation. Thank you efrant. You've answered everything I've needed to know
Sent from my Galaxy Nexus using Tapatalk
Well finally took the plunge and went to yakju from yakjuux. Although my experience wasn't as seemless as everyone elses, so I thought I'd tell everyone just in case someone else runs in to the same problem.
For starters: I followed efrants excellent procedure from this exact post. However it also must be noted that I decided to use the 41F (4.0.1) firmware from Google's images instead of the 53F (4.0.2) image. I did this because I wanted to experience an update. lol
Now, at first I had to try several drivers in order for my Windows 7 laptop to even see the phone with the "fastboot devices" command. I finally found one that works. Coincidentally, one driver will work on one machine, but won't on the next, I have no idea why. After finally getting the right one, I proceeded:
I did all steps to the letter, but skipped steps 4,5 and 12, as the post says they were optional and I didn't really want to lose my bootloader and recovery in case I wanted to revert back to yakjuux.
After completing all steps but those, I did the final "fastboot reboot" and the phone restarted.
Here's where the ride began:
When it restarted, it seemed like everything was fine. It took a while to find Bell's settings, but it was ok. It then said an update to 4.0.2. was available.
Upon the reboot and install, the phone shut off, and rebooted twice, after the second time, I had an android on the ground with its chest open and a RED exclamationed triangle above it. My thoughts were "uh oh". I waited and waited, and nothing was happening. Pressing power and holding it down, wouldn't help.... After approx 5 mins I was about to do a battery pull, and it restarted itself, but remained on the 41F update.
Each restart would say it was upgrading, but never did.. always stayed on 41F.
So I went back and did everything in the procedure, not omitting anything this time (goodbye yakjuux bootloader!) and it went off without a hitch... This time my android figure was standing up, very much alive and getting a heart transplant.
So here I am.. Yakju configured and using the yakju KK6 radio. All seems well. Haven't decided if I'm going to put the KL1 radio on as yet, but thats for another day.
Thanks again efrant for all your help and patience with me.
@greeced Welcome to yakju. I doubt you will ever go back to yakjuux.
Sent from my Galaxy Nexus using Tapatalk
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Overall very happy that I'm now Pure Google.
One thing to note:
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
We are dealing with computers after all.
At any rate. Just thought I'd update my experience in case anyone else who is on bell felt apprehensive like me.
Sent from my Galaxy Nexus using Tapatalk
greeced said:
Well, I have been on yakju for a few days now and I can say no problems whatsoever.
At first I felt as if it was slightly Laggy, but that seemed to correct itself after a day or so. Not sure why, but the phone is just as quick as before now.
Click to expand...
Click to collapse
I think the general consensus is that ICL53F is more laggy that ITL41F or ITL41D, so it is not a yakju vs yakjuux issue, it is a 4.0.1 vs 4.0.2 issue.
greeced said:
As for the radio, I wanted to stay completely stock, and that included the radio. So my phone is running the stock KK6 that came with the update, and I noticed my DBM levels are just as good as before if not better. So I don't feel the need to flash KL1.
Click to expand...
Click to collapse
Radio performance varies with a huge number of factors. If you are happy with how one radio works, use it. If you want to see if another one is better, try it. If you don't like it, flash back. It takes all of 30 secs to flash a radio.
greeced said:
[snip]
When I was on my SGS, I always factory reset after every flash, which always seemed to speed up the experience of the new ROM.
I think that should be the case for all firmware updates, including googles.
It's a painful process to redo everything, but well worth it in my opinion.
I mean think about it, installing a fresh copy of windows always performs better than doing an upgrade of windows, so that should be the same here.
Click to expand...
Click to collapse
If you believe this, then I suggest that you do not flash older builds and OTA update to a newer ones. This process adds more files to your ROM, and is not as clean as flashing the latest build from Google's factory image site.
When the next version of Android is released, the full version will likely be available on Google's factory image site shortly before OTA's for yakju start rolling out.* If you don't mind redoing your settings, apps, etc., it is better (and faster) to flash the full build, instead of updating your current build.
*My assumption based on release dates for previous versions.
Question efrant.
I relocked my bootloader purposely.
If I wanted to test other radios does the bootloader need to be unlocked?
If it does, no big deal, I just won't do it
Sent from my Galaxy Nexus using Tapatalk
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
ac17 said:
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
Click to expand...
Click to collapse
That's because the package you downloaded on Google's Developers website needs to be flashed using fastboot, not CWM. Follow this thread to flash back to yakju, and you should be good to go.
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Rayzor76 said:
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Click to expand...
Click to collapse
It would definitely work however if you even need to return your phone back to Vodafone, you may or may not run into some issues due to not being on their ROM. It's pretty hard to find random stock ROMs for places other than the main ones these days (or I just might be looking at the wrong places).
Rayzor76 said:
Did this work for you? as i have the same phone and im tempted to do this but not if its going to mess the phone up. Damn you vodafone for having to be different
Click to expand...
Click to collapse
I'm sorry, I can't remember what I did, but I fixed it that night, which now feels like months ago.
I installed Nexus Root Toolkit v1.5.2, on a pc and I know that that helped me speed up the process.
You can't ruin anything unless you flash a rom not designed for the phone, or format the bios partition and then reboot (with out installing a new bios), but even then I'm sure you can install stuff from a pc over usb using that program.
ac17 said:
I'm sorry, I can't remember what I did, but I fixed it that night, which now feels like months ago.
I installed Nexus Root Toolkit v1.5.2, on a pc and I know that that helped me speed up the process.
You can't ruin anything unless you flash a rom not designed for the phone, or format the bios partition and then reboot (with out installing a new bios), but even then I'm sure you can install stuff from a pc over usb using that program.
Click to expand...
Click to collapse
Thanks New to Android as I have been an avid iOS user and jailbreaker for a few years so just catching up on rooting and flashing ROMs n stuff. But good to know it can be done as i Have the exactly same phone from Vodafone Australia. Better to be safe than sorry and ruining a 2 day old phone.
Rayzor76 said:
Thanks New to Android as I have been an avid iOS user and jailbreaker for a few years so just catching up on rooting and flashing ROMs n stuff. But good to know it can be done as i Have the exactly same phone from Vodafone Australia. Better to be safe than sorry and ruining a 2 day old phone.
Click to expand...
Click to collapse
No worries mate, this is my 2nd android phone (first was a nexus s).
I learned a lot by rooting and playing with custom roms on that ph, but I have been really happy with stock jelly Bean on this (albeit rooted) device. Battery life is great, and it's a snappy phone with great features.
FYI I just read an interesting article Why Apple Won't Divorce Samsung today that explained how Samsung make all the chips for Apple products. You can't go wrong with Samsung mate.
Android users on this forum are generally friendly and Damn knowledgeable too.
Enjoy your new phone!
ac17 said:
Hi all,
I just received a new GNex from Vodafone Australia. Can someone please help me figure out which version I have so I can update it?
I am running 4.0.4 (rooted)
The Baseband is:
I9250TDVLE1
The build is:
IMM76K.I9250TDVLE1
I could not find an update on google anywhere...
I found reference to my build pertaining to Toro, Magro and Verizon.
I can't see how all of these could be simultaneously true...
I thought '**** it' I ll roll back to a yakju 'official' 4.0.4 IMM76I ROM from here and then flash the Update to 4.1.1 JRO03C
But When I booted into CWM and tried to flash the imm76i, it would not let me. Is there something I am doing wrong or do not understand about swapping roms...?
(I cleared the cache / factory reset)
Am I stuck with IMM76I until google makes an 4.1.1 update, or can I flash another google rom somehow and get the update that way?
Cheers
Click to expand...
Click to collapse
OK. The fact is that Vodafone and Telstra get all their updates later. This is because of the better 3g signals they have built in the phone. So due to this their updates come out a little while later. Also it depends where you are in the world (eg. UK, AU, USA) because the UK has already got the update as far as I know. So there is two options here to stay with Vodafone if something does go wrong so you have a backup. And referring to what Unlawful had said he is right you do need a stock Vodafone ROM or features and such can go wrong. BTW I am also with Vodafone but running a custom ROM.
Thank mate. I updated it manually, months ago.
The Gnex is an awesome phone (I upgraded from a NEXUS S), and with stock jelly Bean (rooted) with stock kernel it runs smoothly and is stable.
I miss rge Wolfson audio chip of the nexus s though bc audio recordings are terrible and crackling with the gnex.
Fast charge is something that I now need and otherwise I'm satisfied!
EDIT: ISSUE RESOLVED. THIS IS A HARDWARE PROBLEM. SEE POST #16
---------------------------------------------------
Hey folks, so my friend didn't wait for my flashing skills and flashed his g/f's phone on his own.
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Now his phone suddenly does not detect the SIM card any longer? It did before all this.
The IMEI is fine. And I tried my very old AT&T SIM card, but it didn't detect my SIM either.
I then ODIN'd back to stock 4.1.2 and had same problem.
So I then rooted and flashed a custom 4.1.2 that came with a custom kernel, and still had the same problem.
So then I ODIN'd back to a stock ICS and STILL have the same problem.
Any suggestions?
CZ Eddie said:
Hey folks, so my friend didn't wait for my flashing skills and flashed his g/f's phone on his own.
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Now his phone suddenly does not detect the SIM card any longer? It did before all this.
The IMEI is fine. And I tried my very old AT&T SIM card, but it didn't detect my SIM either.
I then ODIN'd back to stock 4.1.2 and had same problem.
So I then rooted and flashed a custom 4.1.2 that came with a custom kernel, and still had the same problem.
So then I ODIN'd back to a stock ICS and STILL have the same problem.
Any suggestions?
Click to expand...
Click to collapse
Which S2 model? This is the T-Mobile forum and you said ATT sim. ATT sim won't work in a TMobile phone without it being unlocked.
Sent from my SGH-T989
jrc2 said:
Which S2 model? This is the T-Mobile forum and you said ATT sim. ATT sim won't work in a TMobile phone without it being unlocked.
Sent from my SGH-T989
Click to expand...
Click to collapse
SGH-T989 is the phone. The Hercules. Her SIM is a T-Mobile "isis" micro SIM with the little adapter thing. She says it worked fine before the update.
CZ Eddie said:
SGH-T989 is the phone. The Hercules. Her SIM is a T-Mobile "isis" micro SIM with the little adapter thing. She says it worked fine before the update.
Click to expand...
Click to collapse
When you tried a clean flash in Odin, did you/she wipe data, cache, and Dalvik before flashing stock?
Have a good evening,
jrc2
Sent from my SGH-T989
jrc2 said:
When you tried a clean flash in Odin, did you/she wipe data, cache, and Dalvik before flashing stock?
Have a good evening,
jrc2
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, wiped system and everything except internal SD.
CZ Eddie said:
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
Click to expand...
Click to collapse
And.... that's why the SIM card worked before the "update" to stock TouchWiz. LOL
Turns out the SIM card she was using is the newer "Isis" version and it's not compatible with the 4.1.2 TouchWiz. And since 4.1.2 is the newest TouchWiz available for the Hercules, I just flashed to the newest AOSP 4.4 and now SIM is recognized again. I guess the really old Slim AOSP ROM was still somehow newer than the 4.1.2.
Dang, it sucks that Samsung hasn't even given you guys 4.2 yet. Sheesh.
Thanks for the help though.
CZ Eddie said:
And.... that's why the SIM card worked before the "update" to stock TouchWiz. LOL
Turns out the SIM card she was using is the newer "Isis" version and it's not compatible with the 4.1.2 TouchWiz. And since 4.1.2 is the newest TouchWiz available for the Hercules, I just flashed to the newest AOSP 4.4 and now SIM is recognized again. I guess the really old Slim AOSP ROM was still somehow newer than the 4.1.2.
Dang, it sucks that Samsung hasn't even given you guys 4.2 yet. Sheesh.
Thanks for the help though.
Click to expand...
Click to collapse
Glad you got it working again! Part of it is Samsung is now on the S5, and they want people to buy it so they don't update the S2. The other problem is TouchWiz is so inefficient that some if their phones with 1gb if ram can't run TouchWiz KitKat, even though KK is designed for 512 mb of RAM and up. That's why every Samsung phone or tablet I've ever owned has been rooted once it is out of warranty (about when they stop updating if you buy new.)
If I can help you with anything else, please reply to this post.
Have a good night!
jrc2
Sent from my SGH-T989
UPDATE: BROKEN AGAIN
Well I just don't understand this one. The phone and SIM were working fine last night. I gave the phone back to the owner. This morning she brings it back to me because once again, the SIM is not working. She didn't do anything to the phone, so we're not sure what caused this.
And for the life of me, I can't get the SIM card to work again, after re-doing everything I did last night to fix it.
So I went to T-Mobile store and got her the old style SIM specifically for this phone model. And the phone doesn't see that SIM either. The T-Mobile guy was perplexed.
Especially so, because the phone recognizes my AT&T SIM and asks for an unlock code. It see's my Mom's AT&T SIM also. Asks for an unlock code.
So WTF. It see's AT&T SIM's but can't see any TMO SIM.
Most.Perplexing.
Already tried ODIN to stock and flashed AOSP 4.4. Nothing working.
Full wipes in between flashes.
IMEI is still showing up fine and TMO agent didn't find any locks on the IMEI in his system.
CZ Eddie said:
UPDATE: BROKEN AGAIN
Well I just don't understand this one. The phone and SIM were working fine last night. I gave the phone back to the owner. This morning she brings it back to me because once again, the SIM is not working. She didn't do anything to the phone, so we're not sure what caused this.
And for the life of me, I can't get the SIM card to work again, after re-doing everything I did last night to fix it.
So I went to T-Mobile store and got her the old style SIM specifically for this phone model. And the phone doesn't see that SIM either. The T-Mobile guy was perplexed.
Especially so, because the phone recognizes my AT&T SIM and asks for an unlock code. It see's my Mom's AT&T SIM also. Asks for an unlock code.
So WTF. It see's AT&T SIM's but can't see any TMO SIM.
Most.Perplexing.
Already tried ODIN to stock and flashed AOSP 4.4. Nothing working.
Full wipes in between flashes.
IMEI is still showing up fine and TMO agent didn't find any locks on the IMEI in his system.
Click to expand...
Click to collapse
When you are on stock, does the sim work then?
Sent from my SGH-T989
jrc2 said:
When you are on stock, does the sim work then?
Sent from my SGH-T989
Click to expand...
Click to collapse
Nope. Tried ODIN to ICS and JB and neither see the SIM.
Gahh, just flashed the 4.4 wild kernel and a EMC6 (?) modem. Whatever the latest modem is.
No dice.
@CZ Eddie
Have you tried flashing the latest radio?
Sent from my SGH-T989
jrc2 said:
@CZ Eddie
Have you tried flashing the latest radio?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yup, modem=radio.
I ODIN'd the older 4.0.X ROM found at SamMobile: T989UVLH1_T989TMBLH1_TMB
Then I ODIN'd root.
Then I flashed the older radio: sgh-t989_uvle1_radio
I followed the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=2024514
This unlocked the phone for my AT&T SIM to use. And dammit, the phone see's my AT&T SIM and is making calls just fine.
BUT IT STILL REFUSES TO ACKNOWLEDGE ANY T-MOBILE SIM.
WTF WTF WTF. LOL. :silly:
Okay, I got things figured out.
This is a HARDWARE issue.
If the AT&T SIM is inserted properly, it works fine.
If either T-Mobile SIM is inserted properly, it does not work.
If the T-Mobile micro SIM is inserted properly, then slid out 1/8", then it works.
I can't get the T-Mobile normal SIM to work in any position, but then it's bigger, so it's harder to get it to "slide around" in the slot they way I need it to.
Could you please send me the link or ICS stock rom file, all link I found already die.
snake2001vn said:
Could you please send me the link or ICS stock rom file, all link I found already die.
Click to expand...
Click to collapse
Here you go. http://www.sammobile.com/firmwares/3/?download=10961
You will need a Sam Mobile account to download the file.
Sent from my SGH-T989
CZ Eddie said:
Phone was already on some very old version of SlimROM AOSP and an older TWRP of some version or other.
I emailed him TWRP 7.1.X zip and a 4.1.2 stock rooted ROM zip.
He flashed them both at the same time, without rebooting in between.
And got a boot loop.
I had him flash just the TWRP and reboot to recovery. Then flash the ROM zip.
Click to expand...
Click to collapse
I am not in a similar situation, I just bought an unlocked ATT Skyrocket using T-mobile SIM. And I hope to find a ROM supports ISIS/Softcard now. I think it would probably be a T-mobile stock ROM.
I ran through I727 and T989 forums, yet got a bit confused with all types of methods.
So, what's your latest suggested steps? Thanks,
These issues started with the upgrade to latest T-Mobile 4.3 software pack at the end of November. Phone operated perfectly before then. After the update, the phone would periodically not receive/place calls/texts/use data. The issue kept worsening daily. It is not related to the SIM card or location, as the card has been replaced and tested in an alternate phone where it performs perfectly.
The T999L was then consequently rooted, KNOX flagged (it's already past warranty, Samsung wouldn't give a rat's ass about it), flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted. Restored to stock 4.1.2, same issues. Did 3 updates OTA to get to latest 4.3, same issues.
Messed around with 4636 menu, 2263 menu, etc. Some changes had a temporary result but nothing permanent. Calls to the phone are redirected to voicemail. When placing a call, it takes 5-10 seconds to either place it or disconnect it (as it can't connect to the network, I guess?). The bars on the phone show 3-4 bars typically, but the phone is rarely able to acquire a data connection. Again, this is not the case with other phones the SIM is tried on.
Any suggestions? I've spent probably close to 10 hours researching this and trying everything out and I am absolutely stumped. This is my mom's phone and a replacement Alcatel OneTouch Fierce 2 just "doesn't look nice", so I'm getting a fair bit of *****ing for trying to help solve this, even though it's not my fault. Would appreciate some help before Christmas.
Have you tried updating the modem?
systemcode said:
Have you tried updating the modem?
Click to expand...
Click to collapse
flashed to CM11 M12 and later a variety of modems was tried. Same issues persisted.
Click to expand...
Click to collapse
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
dwegiel said:
I'd say so. Used this thread: http://forum.xda-developers.com/showthread.php?t=1880987 and flashed the 4.3 basebands for T999L and T999N, total of 3. I'm thinking this is something to do with the 4.3 bootloader or basebands... any methods to go back to 4.1.2 without a brick?
tagging this for later use:
http://forum.xda-developers.com/showthread.php?t=2121736
http://forum.xda-developers.com/showthread.php?t=2258238
Click to expand...
Click to collapse
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
nirogu325 said:
If you have a T999L stick to the designated T999L modems and nothing else, or you may damage the device. If you have a 4.3 bootloader there is no way back. Have you tried to use ODIN to flash the latest NF4 firmware for your T999L and then do a factory reset using the stock recovery? I posted NF4's link in this post. Good luck.
Click to expand...
Click to collapse
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
dwegiel said:
Downloading right now, and will test. Pretty sure this is the firmware update after which this problem started occurring.
Any other ideas for what might be affecting this besides baseband? I have a feeling something else might be causing this. I'm not familiar with Samsung partitions though and what is flashed by OTA/Odin.
Click to expand...
Click to collapse
Well, OTA updates can sometimes fail, that's why I gave you the ODIN firmware link. It's the best help I can offer.
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
RBThompsonV said:
Hey guys... Been a LONG time since messing with an S3, and I don't want to brick it... SO, figured I'd reach out and ask before doing anything...
I downgraded a friend's S3 to UVDLJC to sim unlock it and it seemed to work fine on stock ROM. I then rooted the rom, flashed TWRP and factory reset the device and then flashed a custom ROM (this version is SlimKat but I had tried CM13 as well.. both have the same issue, no SIM detected)...
Anyway, I assume that it is a modem/radio issue and I should just be able to flash the modem firmware and be fine.. Problem I'm having is I'm not sure what to use... The phone is a T-999L Which, as I understand it, is the LTE GS3, but the software that was on it was based on the non LTE version (not sure if I'm correct about this)...
Anyway, looking to get this phone working for the friend's daughter (it was supposed to be a christmas present )...
Any and all help is appreciated.
Additional Info:
Phone model is T-999L
Boot loader is T999UVDLJC
Build version reports 4.4.4
Rom is currently SlimKat
Unified tools reports model as SGH-T999, type as d2tmo
Not sure what other info can help, but happy to provide.
Click to expand...
Click to collapse
Odin'ed back to LJC original firmware... still shows no Sim card.
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
audit13 said:
The latest custom ROMs require the latest bootloader and modem to function properly so the phone probably needs an update. Once the phone is running a 4.3 or higher bootloader means the bootloader cannot be downgraded in the future.
I don't see the LJC firmware for the T999L: http://www.sammobile.com/firmwares/database/SGH-T999L/
I see LJC for teh T999: http://www.sammobile.com/firmwares/database/SGH-T999/
Click to expand...
Click to collapse
Yeah, I'm thinking the phone is a T999, not a T999L. In my best estimation, the motherboard was swapped to a T999L case/screen. The sticker shows T-999L, the phone reports T-999. Additionally, under settings, the IMEI differs from the IMEI reported on the sticker. (Neither He, nor I was the original owner of the phone... so who knows it's history... For all I know, I really am working with a T-999L and someone flashed a different IMEI (worst case scenario I guess).
Is there any way to know for absolute sure? and should I go ahead and just flash 4.3? is there any downside to doing it other than that the boot loader can't be rolled back afterwards?
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
It detected a sim when we got it (on 4.1.2), it detected a sim when i downgraded to 4.1.1, it detected a sim when i unlocked the sim, it did not detect a sim after flashing CM13, it did not detect a sim on SlimKat, and now it does not detect a sim after 4.1.1 (flashed via Odin) (LJC) and Download mode shows T-999 (NOT T-999L).
audit13 said:
Personally, I would go by the model # shown with the phone in download mode.
Did it ever detect a sim card after unlocking restoring to stock?
Click to expand...
Click to collapse
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
audit13 said:
The 4.1.1 firmware came from sammobile? The baseband under settings is also LJC?
Click to expand...
Click to collapse
Correct and correct.
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
audit13 said:
This is bizarre because I don't understand why it would suddenly stop working. Did it say SGH-T999 on the download screen before flashing to 4.1.1?
I assume the stock ROM boots without issue?
Also try this: download and install the Samsung Phone Info from the play store to confirm the bootloader and baseband currently on the phone.
When flashing from a custom ROM to stock 4.1.1, did you perform a factory wipe?
Click to expand...
Click to collapse
Stock rom boots without issue...
Yes i did a factory wipe between flashes. (Although, first flash of CM13 I did not, it ran weird, i rebooted, factory reset, flashed again then it worked fine minus the sim card issue).
Phone Info confirms SGH-T999, type: d2tmo
Boot loader: T999UVDLJC, Baseband: T999UVDLJC
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
audit13 said:
Not sure what else to suggest other than reflashing the LJC ROM and performing a factory wipe from stock recovery before the phone's first boot of LJC.
Click to expand...
Click to collapse
Nope...no go.
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
audit13 said:
Hmm, I'm out of suggestions because you did everything I would do other than either flashing the latest stock 4.3 since the phone is now sim unlocked or running OTA updates. on a stock ROM.
The sim card in the phone works properly in another phone? Is it possible the sim reader was damaged in some manner? I know it can happen when using micro/nano sim card adapters.
Click to expand...
Click to collapse
Oh... adapters is a good suggestion. Yes, when I originally unlocked the phone, I used an adapter as my sim is a nano sim... Whats the damage look like? and is it fixable? I'm assuming just bent pins?
Is flashing an LTE Rom a possible solution? or is that a hard brick result?
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
audit13 said:
You could try flashing TWRP and an older build of CM that will work with a 4.1.1 bootloader and modem just to see if the sim card is detected.
The metal housing on top of the sim pins is difficult to remove so it may be easier to just buy a replacement sim/sd card reader.
Click to expand...
Click to collapse
The posts aren't real specific... do you know which CM is 4.1.1 friendly?
I would try the latest cm10 or cm10.1.
https://download.cyanogenmod.org/?device=d2tmo&type=snapshot
dang you rock @audit13. as always :thumbup: , aint enuff. happy good new year for you and yours sir.
"all i can really do is stay out of my own way and let the will of heaven be done"
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
audit13 said:
Any luck getting the phone to recognize the sim card?
@mrrocketdog, thanks
Click to expand...
Click to collapse
Sorry for the delayed response... Yes, I finally got it to recognize (last night) ordered a new sim card tray.. interesting way to mount it by the way...
Anyway, seems as if the guess at the adapter damaging the original was correct... new one seems to be good to go.