Develop Bugs

[Q] [HELP] No 4G Signal

Rooted my T-Mobile S3 via Odin
I like flashing and I know what to wipe everytime
Flashed Jedi Invasion rom
Wiped everything, flashed stock UDVLJC slim rom
Wiped everything, flashed deodexed t999 UDVLJA rom (fully stock)
~~that's when I noticed I was only getting E for signal and not 4G
Wiped everything, flashed PAC JB 4.2.1 rom
~~~still on Edge, no 4G~~~
Wiped everything, tried out Illusion v1.2.1 rom
~~~and still on Edge, no 4G~~~~
Rebooted, reflashed, turned off/on, pulled sim, factory reset, used dialer code for testing, changed data networks, tried everything
This is what I have currently
Android Version:
4.2.1
Baseband version:
T999UDVLJA
Kernel Version:
3.0.59-cyanogenmod-g3b69af1
[email protected] #3
Wed Jan 30 17:16 23 EST 2013
Illusion version:
v.1.2.1
Build number:
d2tmo-userdog 4.2.1 JOP40D
eng itsmikeramsay.20130201. 111003 test-keys
ClockworkMod Recovery 6.0.2.3
Do I need to reflash a kernel? Radio? Change roms? App fixes? Fixes?
C'mon xda help me out here pleasee and thank youss~

arthurgreeeen said:
Rooted my T-Mobile S3 via Odin
I like flashing and I know what to wipe everytime
Flashed Jedi Invasion rom
Wiped everything, flashed stock UDVLJC slim rom
Wiped everything, flashed deodexed t999 UDVLJA rom (fully stock)
~~that's when I noticed I was only getting E for signal and not 4G
Wiped everything, flashed PAC JB 4.2.1 rom
~~~still on Edge, no 4G~~~
Wiped everything, tried out Illusion v1.2.1 rom
~~~and still on Edge, no 4G~~~~
Rebooted, reflashed, turned off/on, pulled sim, factory reset, used dialer code for testing, changed data networks, tried everything
This is what I have currently
Android Version:
4.2.1
Baseband version:
T999UDVLJA
Kernel Version:
3.0.59-cyanogenmod-g3b69af1
[email protected] #3
Wed Jan 30 17:16 23 EST 2013
Illusion version:
v.1.2.1
Build number:
d2tmo-userdog 4.2.1 JOP40D
eng itsmikeramsay.20130201. 111003 test-keys
ClockworkMod Recovery 6.0.2.3
Do I need to reflash a kernel? Radio? Change roms? App fixes? Fixes?
C'mon xda help me out here pleasee and thank youss~
Click to expand...
Click to collapse
Might be your imei check that in about phone under settings if it is a 0 then it's an easy fix
Sent from my SGH-T999 using xda premium

RedJack117 said:
Might be your imei check that in about phone under settings if it is a 0 then it's an easy fix
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
omq it IS 0!
what do i do??

Will have everything you need
http://forum.xda-developers.com/showthread.php?t=1804117
Sent from my SGH-T999 using xda premium
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
Super simple fix don't worry about it... I didn't know how easy it was to fix it and I literally went to tmo and got 2 new gs3's like a dumb*** lol
Sent from my SGH - T999 using xda premium running liquid smooth 4.2.2

RedJack117 said:
Will have everything you need
http://forum.xda-developers.com/showthread.php?t=1804117
Sent from my SGH-T999 using xda premium
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
Super simple fix don't worry about it... I didn't know how easy it was to fix it and I literally went to tmo and got 2 new gs3's like a dumb*** lol
Sent from my SGH - T999 using xda premium running liquid smooth 4.2.2
Click to expand...
Click to collapse
You're the BOSS
Will try this out when I get home!

Also don't use cwm.. Only use TWRP you won't have to worry about that
Sent from my SGH-T999 using xda premium

ktetreault14 said:
Also don't use cwm.. Only use TWRP you won't have to worry about that
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
People really need to stop saying that. It has happened with both recoveries. There is a thread on the issue with TRWP. There does not seem to be any correlation at all regarding which recovery you use.

Ya that has been discussed so many times out of the 500 times it has happened about 10 of them were from twrp that were reported.

mt3g said:
Ya that has been discussed so many times out of the 500 times it has happened about 10 of them were from twrp that were reported.
Click to expand...
Click to collapse
Even if your 50-1 stat is correct, and I am not sure it is, you would have to know how many people with each recovery have successfully flashed without losing imei to have any meaning. Repeating an unproven theory like it is fact does not help. No offence because you are a good poster that is always helpful.

You have to account for the fact that even at this point there are probably still more people using CWM simply due to the fact that it has been around longer and a lot more people are used to it. If there is even a single person (and we already know that there is) who has lost their IMEI while using TWRP, that negates the concept that it is a CWM only issue. You also have to consider the fact that 500 reports is still not enough to establish a baseline, and also the fact that quite a few people have probably resolved the issue by searching and finding the solution without reporting it at all.
With all this in mind, it seems to me that it may be a more common problem on CWM, but we have no way of knowing whether that is because of TWRP being better or because of CWM being the more common recovery. However, we do know that the issue can happen on either recovery.
Sent from my SGH-T999 using xda premium

I only said that because I always used cwm.. Until this device.. I lost my imei twice using it and have never list it since I switched to twrp
Sent from my SGH-T999 using xda premium

Bottom line better to be on the the safe side so just use twrp, it's quicker and easier why not?
Sent from my SGH-T999 using xda app-developers app

A better bottom line would probably be to backup your IMEI
Sent from my SGH-T999 using xda premium

ktetreault14 said:
I only said that because I always used cwm.. Until this device.. I lost my imei twice using it and have never list it since I switched to twrp
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
daxecutioner24 said:
Bottom line better to be on the the safe side so just use twrp, it's quicker and easier why not?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Recovery doesnt have anything to do on this. Our phone is build like that.
Best thing to do is back up ur imei .

Either recovery is true for lost IMEIs. I have used both and lost them on both.
Sent from my Galaxy Nexus using xda premium

ktetreault14 said:
I only said that because I always used cwm.. Until this device.. I lost my imei twice using it and have never list it since I switched to twrp
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Thanks, and I understand. I just did not want people to think one recovery was full proof when it is not and skip making a backup thinking they are solid. As suggested by others, making a backup of the IMEI is good idea.

Ok I got my imei back after a million tries, but still have no 4G data / signal. I tried all the mobile network options but no matter what I will be on edge network.
This is annoying, please help anyone thanks

Why not just Odin back a factory jelly bean image and start from scratch.
You can at least eliminate the phone as being defective if it works when you go back stock.
Sent from my SGH-T999 using Tapatalk 2

arthurgreeeen said:
Ok I got my imei back after a million tries, but still have no 4G data / signal. I tried all the mobile network options but no matter what I will be on edge network.
This is annoying, please help anyone thanks
Click to expand...
Click to collapse
Did you try the 4G fix on post 3 of the IMEI thread?
Sent from my SGH-T999 using xda premium

arthurgreeeen said:
Ok I got my imei back after a million tries, but still have no 4G data / signal. I tried all the mobile network options but no matter what I will be on edge network.
This is annoying, please help anyone thanks
Click to expand...
Click to collapse
Thetenthdr said:
Did you try the 4G fix on post 3 of the IMEI thread?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yep, simply injecting the IMEI back isn't the last step.

Will I be able to do anything now? Help please.

Today I am going to flash my phone to cricket. Will I be able to still flash sprint Roms or will I have to get special ones ? Will it also mess with the flashing to Cricket ?
Sent from my SPH-L710 using xda app-developers app

And because you made the same thread with a different title. Try this link http://www.cricketusers.com/root-re...flash-cricket-rom-onto-flashed-sprint-s3.html
Sent from my Freeza MD4 Stock Rooted Galaxy S3

evouser22 said:
Today I am going to flash my phone to cricket. Will I be able to still flash sprint Roms or will I have to get special ones ? Will it also mess with the flashing to Cricket ?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Yes you will continue to use sprint roms on a sprint phone. Flashing roms will not affect your cricket flash in anyway I flash roms all the time on my sprint s3 that is flashed to cricket. MMS will probably take some trial and error otherwise the s3 is a pretty easy flash good luck and remember to only post your questions once :good:

tclemens said:
Yes you will continue to use sprint roms on a sprint phone. Flashing roms will not affect your cricket flash in anyway I flash roms all the time on my sprint s3 that is flashed to cricket. MMS will probably take some trial and error otherwise the s3 is a pretty easy flash good luck and remember to only post your questions once :good:
Click to expand...
Click to collapse
Thanks man, really appreciate it. Answered my question exactly
Sent from my SPH-L710 using xda app-developers app

Rogers 1317m note 2 to n7105

Hi. Before flashing PA I was on 1317m Rogers but after it switched to n7105. There's no problem with that right? Btw everything is working perfectly.
Sent from my GT-N7105 using xda premium

You can easily change it by editing build.prop using root explorer. Open root explorer, system press n hold build.prop use text editor then change model to l317M.

Thanks!
Sent from my GT-N7105 using xda premium

jon3sh said:
You can easily change it by editing build.prop using root explorer. Open root explorer, system press n hold build.prop use text editor then change model to l317M.
Click to expand...
Click to collapse
But what I'm trying to ask is instead of going to at&t and try to find a Rom that will work for my phone I can go to the GTn7100 and GT n1707 section and flash a Rom without any problems right?
Sent from my GT-N7105 using xda premium

Erichuynh said:
But what I'm trying to ask is instead of going to at&t and try to find a Rom that will work for my phone I can go to the GTn7100 and GT n1707 section and flash a Rom without any problems right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Sorry my bad, I would stay away from N7100 and N7105 section. There so many N7100 and N7105 ported rom for our device in att section so just use the ones from here. If read the changelogs of some roms here you will see MF2 roms are originally from N7xx roms.
Edit..
Flashing rom made for N7xx device can mess up your modem, imei etc. I

Thank you much much for this info. I did try to flash a n1700 Rom once and like you said I didn't get any connectivity on my Rogers carrier even when I found a modem to flash, and ended up having to go back to stock plus factory resets which is such a pain
Sent from my GT-N7105 using xda premium

Erichuynh said:
Thank you much much for this info. I did try to flash a n1700 Rom once and like you said I didn't get any connectivity on my Rogers carrier even when I found a modem to flash, and ended up having to go back to stock plus factory resets which is such a pain
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
You could have ended up with a brick.....
Or corrupted imei.
You can't flash n7100 roms

crixley said:
You could have ended up with a brick.....
Or corrupted imei.
You can't flash n7100 roms
Click to expand...
Click to collapse
This is my first Android phone so I didn't know
Sent from my GT-N7105 using xda premium

Erichuynh said:
This is my first Android phone so I didn't know
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Not trying to be rude, but just be very careful!
You don't want to end up with an expensive brick

crixley said:
Not trying to be rude, but just be very careful!
You don't want to end up with an expensive brick
Click to expand...
Click to collapse
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium

Erichuynh said:
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
Brick like dead screen, not responding to anything or wont show n your computer when connected to usb or simply expensive paper weight. Only way to revive it flash via jtag etc. There is also soft brick where its only black screen but you can still flash roms via Odin and flashing wrong rom can cause soft brick too.

Erichuynh said:
Even when it's bricked is it still possible to actually get into recovery wipe all caches and do a factory reset then get back to stock Rom right?
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
What he said above...
There is also a corrupt efs partition. If you didn't have it backed up you have no imei, and so you have a phone that can turn on but can't connect to any network, this can be permanent and has happened to people from flashing n7100 roms

crixley said:
What he said above...
There is also a corrupt efs partition. If you didn't have it backed up you have no imei, and so you have a phone that can turn on but can't connect to any network, this can be permanent and has happened to people from flashing n7100 roms
Click to expand...
Click to collapse
Yep I did more in depth research about the hard bricked phones and it sucks!
Sent from my GT-N7105 using xda premium

Erichuynh said:
Yep I did more in depth research about the hard bricked phones and it sucks!
Sent from my GT-N7105 using xda premium
Click to expand...
Click to collapse
yeah hard bricked or corrupted efs both suck :/
I have never bricked a phone and been using android since early 2009.
I'm crazy cautious

Back up of EFS is a must too, it is a good habit that you always have nand, modem csc patch and efs back up saved to you external card or computer.

Once your a little more familiar with your phone this is a good thread to check out http://forum.xda-developers.com/showthread.php?t=2018411. For the most part the i317 and 7105 are identical except for modem and gps files DO NOT FLASH A 7100 ROM Unless it has been modded following the posted thread. Personally i have been using Jedi x17 it has everything i want extended boot menu,Lidroid 23 toggles,speed tweaks etc... Now i have made my own modifications as well (status bar,speedometer and ringtones) I also have been working on modding MA3 rom as well in my spare time but really Jedi works just fine. Just my two cents. Good Luck and have fun,Dave

Baseband Unknown

Does anyone have a baseband fix. I can't connect to the Sprint mobile network. I feel like i've tried everything. Any ideas? I've tried going back to stock, flashing radios/modems/kernels. Any help would be appreciated.

What did you do to get this problem? Knowing the background will help us help you.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Did you flash Aospa 4 or cm11 through TWRP? if I remember in both threads they say to flash via CWM or you'll lose your baseband. You might have to flash a total stock image via Odin to fix it.
Sent from my Galaxy Note II via Tapatalk 4

saboture said:
Did you flash Aospa 4 or cm11 through TWRP? if I remember in both threads they say to flash via CWM or you'll lose your baseband. You might have to flash a total stock image via Odin to fix it.
Sent from my Galaxy Note II via Tapatalk 4
Click to expand...
Click to collapse
yeah i flashed Aospa, but i did do it through CWM...for some reason my SD card wouldn't work after the update so I went to downgrade back to stock. I tried flashing from ODIN with the stock image but it was failing at the boot.img part every time. Maybe I got a bad stock image? I'll search for the stock through xda and re download and try. just sucks because it took almost two hours to download. thanks again for everyone's help.

Well I have lost baseband along with all the other info countless times. The fix is not very hard. If you still need help I can help you out later today.
Sent from my SPH-L900 using XDA Premium 4 mobile app

jlmancuso said:
Well I have lost baseband along with all the other info countless times. The fix is not very hard. If you still need help I can help you out later today.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes I am still needing help. Get back to me when you have a chance!!!

jlmancuso said:
Well I have lost baseband along with all the other info countless times. The fix is not very hard. If you still need help I can help you out later today.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you do the factory stock? You will lose root but mc2 is easy to root with CF.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from Bobby's Intergalactic, Planetary Phone

BBobby said:
Can you do the factory stock? You will lose root but mc2 is easy to root with CF.
http://forum.xda-developers.com/showthread.php?t=2086769
Sent from Bobby's Intergalactic, Planetary Phone
Click to expand...
Click to collapse
did this work?? i am having the same problem and feel like i have tried everything and still no network connection

[q] help!!!! Bricked s3!

I was trying to update my bootloader so I could update to a current KK ROM. I don't know what happened but I cant even get into download mode with a jig. It takes a charge and is somewhat detected by windows but that's it.
Can someone please point me in the right direction for a possible fix?
thanks for the help!

Where did you get the bootloader for your phone? Are you sure it was for the i747m and not i747?

audit13 said:
Where did you get the bootloader for your phone? Are you sure it was for the i747m and not i747?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2321310
Flashed MK5 and lost my baseband and IMEI.
Tried another one and kuput.

Once you flash the mk5 bootloader, it cannot be downgraded. Any attempts to downgrade could brick the phone.
SInce your phone isn't booting, you may have to have it jtagged.
I have seen a thread for de-bricking but that looks like it is for the AT&T s3.

audit13 said:
Once you flash the mk5 bootloader, it cannot be downgraded. Any attempts to downgrade could brick the phone.
SInce your phone isn't booting, you may have to have it jtagged.
I have seen a thread for de-bricking but that looks like it is for the AT&T s3.
Click to expand...
Click to collapse
Why would it have lost my IMEI?
I saw a method that involved a 16gb SD card...just need to find more specific instructions....any ideas?
If not where can I find detailed instructions to do a jtag? I have access to the tools required.
I purchased an early upgrade to a Nexus 5 and would rather return it and return to my S3 so the sooner the better!
Thanks for the assist!

Jtagging is not simple because you would need to disassemble the phone in order to access the relevant points on the motherboard.
Did the phone boot after you flashed the mk5 bootloader? Did you flash another bootloader after that?
Which carrier is your phone with?
You could try this: http://forum.xda-developers.com/showthread.php?t=2549068
The MK5 bootloader is the stock 4.3 bootloader to Canadian carriers.

audit13 said:
Jtagging is not simple because you would need to disassemble the phone in order to access the relevant points on the motherboard.
Did the phone boot after you flashed the mk5 bootloader? Did you flash another bootloader after that?
Which carrier is your phone with?
You could try this: http://forum.xda-developers.com/showthread.php?t=2549068
The MK5 bootloader is the stock 4.3 bootloader to Canadian carriers.
Click to expand...
Click to collapse
It did boot after mk5 but no baseband or imei.
Its with Bell.
I'll check it out tx
Sent from my Nexus 5 using xda app-developers app

solaris11 said:
It did boot after mk5 but no baseband or imei.
Its with Bell.
I'll check it out tx
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
So the phone boots? If it does, did you try flashing an updated modem? Try an updated modem before de-bricking.
BTW, I was able to install several KK ROMs using the stock 4.1.2 bootloader. Upgrading wasn't necessary for Validus, Cyanfox, and CM11.

audit13 said:
So the phone boots? If it does, did you try flashing an updated modem?
BTW, I was able to install several KK ROMs using the stock 4.1.2 bootloader. Upgrading wasn't necessary for Validus, Cyanfox, and CM11.
Click to expand...
Click to collapse
No I tried flashing another one after that because of the no imei/baseband. And now it won't boot. I was trying to upgrade from an older omni 4.4 ROM to the latest one and cwm wouldn't flash the ROM using the latest cwm
Sent from my Nexus 5 using xda app-developers app

solaris11 said:
No I tried flashing another one after that because of the no imei/baseband. And now it won't boot. I was trying to upgrade from an older omni 4.4 ROM to the latest one and cwm wouldn't flash the ROM using the latest cwm
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Did you try to flash an older Bell bootloader? If you did, this would have cause the bricking.
Is it possible the battery has been depleted?

audit13 said:
Did you try to flash an older Bell bootloader? If you did, this would have cause the bricking.
Is it possible the battery has been depleted?
Click to expand...
Click to collapse
I think I did flash an older one ....no it takes a charge tested it in a friends s3.
Sent from my Nexus 5 using xda app-developers app

solaris11 said:
I think I did flash an older one ....no it takes a charge tested it in a friends s3.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I assume you've tried several times to get into download or recovery without success. Do you have any warranrt left on the phone? You may have to get it jtagged.

audit13 said:
I assume you've tried several times to get into download or recovery without success. Do you have any warranrt left on the phone? You may have to get it jtagged.
Click to expand...
Click to collapse
Yeah even with a jig. Its not under warranty...my brother has the tools required and experience soldering boards so that's a last resort. Will try the method posted previously.
I'm not minding this nexus 5. If I get my s3 going I may just sell it and keep this lol.
Sent from my Nexus 5 using xda app-developers app

solaris11 said:
Yeah even with a jig. Its not under warranty...my brother has the tools required and experience soldering boards so that's a last resort. Will try the method posted previously.
I'm not minding this nexus 5. If I get my s3 going I may just sell it and keep this lol.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I don't know where you are located but if you're in Toronto, I recommend Ming Wireless in downtown Toronto. They charge $75 to jtag a Samsung.

audit13 said:
I don't know where you are located but if you're in Toronto, I recommend Ming Wireless in downtown Toronto. They charge $75 to jtag a Samsung.
Click to expand...
Click to collapse
About 4 hrs away from Toronto so not really an option
Sent from my Nexus 5 using xda app-developers app

solaris11 said:
About 4 hrs away from Toronto so not really an option
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
That's too bad. I wish you and your brother the best of luck. The s3 is a nice phone, but not as nice as the N5!

audit13 said:
That's too bad. I wish you and your brother the best of luck. The s3 is a nice phone, but not as nice as the N5!
Click to expand...
Click to collapse
Thanks for the help.
Yeah I'm enjoying the nexus, but I had to pay an arm and a leg for an early upgrade, so I just want everything back to normal so I can get a new phone without paying a fortune for it lol...trying not to get too attached to this one for the time being
Sent from my Nexus 5 using xda app-developers app

One word. Odin

Apph3x said:
One word. Odin
Click to expand...
Click to collapse
The op can't get into download mode so i don't think Odin will help.
Loading an incorrect bootloader can result in a hard brick where the phone needs to be jtagged.