How in the world do I flash a modem on the S3? Apparently it's not as easy as just downloading it, placing it on my SD card and booting into recovery. I've tried several modems, and each time I go flash it the installation of the modem fails. Is there some specific modem I have to have for a specific rom, or a specific way that I have to flash the modem? I don't like using Odin, because I'm not very familiar with it. But is that the only way to actually flash the modem?
Any help is greatly appreciated. The reason I need to flash the modem is because I am not able to text or call at all after installing the MOAR rom, backups that I created beforehand don't work either, conveniently.
Actually you can download it to your phone and flash it to recovery as invisblek has created recovery flashable versions of all modems. So it is really easy.
jmxc23 said:
Actually you can download it to your phone and flash it to recovery as invisblek has created recovery flashable versions of all modems. So it is really easy.
Click to expand...
Click to collapse
I've been using Invisiblek modems, none of them have been recovery flashable for me. Do you have a link to these that are recovery flashable?
I'm assuming they probably are, and I just have a lemon of a phone, which appears to be the case. Samsung always has issues when modifying phones, I've never encountered such issues, until I encountered my first Samsung.
It's confirmed I just have a melon phone, used odin to flash a modem.
Well flashing a modem did absolutely nothing. It amazes me that there is no fix for this issue at all. It even corrupts your back ups, which is insane. So much for having a back up to bail you out of trouble. I'm getting a bit frustrated here, is there anyone else who knows how to fix this issue with being unable to text or call anyone?
Spewed said:
Well flashing a modem did absolutely nothing. It amazes me that there is no fix for this issue at all. It even corrupts your back ups, which is insane. So much for having a back up to bail you out of trouble. I'm getting a bit frustrated here, is there anyone else who knows how to fix this issue with being unable to text or call anyone?
Click to expand...
Click to collapse
No calls or texts at all correct? Do you have your correct IMEI in Settings/About Phone?
Sent from my SCH-I535 using Tapatalk 4 Beta
SlimSnoopOS said:
No calls or texts at all correct? Do you have your correct IMEI in Settings/About Phone?
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes sir, IMEI is correct and confirmed by the IMEI under the battery. Last time I attempted to do anything with this phone I had to restore the IMEI, this time I'm unaware of what the issue is, but it's not the IMEI, and flashing a new modem through ODIN didn't work. I'm flashing this now to see if it will work http://forum.xda-developers.com/showthread.php?t=2275376
Spewed said:
Yes sir, IMEI is correct and confirmed by the IMEI under the battery. Last time I attempted to do anything with this phone I had to restore the IMEI, this time I'm unaware of what the issue is, but it's not the IMEI, and flashing a new modem through ODIN didn't work. I'm flashing this now to see if it will work http://forum.xda-developers.com/showthread.php?t=2275376
Click to expand...
Click to collapse
That's cool, let me know how that works. I have one step to potentially resolve this issue for you if BoneStock does not alleviate it. It requires Odin and it will format your internal storage:
--Odin flash an VRALF2 or VRALG1 stock tar then reprovision your sim card by dialing this: *2767*3855#
SlimSnoopOS said:
That's cool, let me know how that works. I have one step to potentially resolve this issue for you if BoneStock does not alleviate it. It requires Odin and it will format your internal storage:
--Odin flash an VRALF2 or VRALG1 stock tar then reprovision your sim card by dialing this: *2767*3855#
Click to expand...
Click to collapse
Bonestock didn't work, so I'm flashing Vralf2, making sure this is the correct fiel. http://forum.xda-developers.com/showthread.php?t=1755386
None of the links are working correctly to download the VRALF2 file, do you have a link to one that is working or the VRALG1? Can't find that one.
Also, by dialing that and I would assume a signal is required. So far, I can't get a signal anymore after messing with it.
Spewed said:
How in the world do I flash a modem on the S3? Apparently it's not as easy as just downloading it, placing it on my SD card and booting into recovery. I've tried several modems, and each time I go flash it the installation of the modem fails. Is there some specific modem I have to have for a specific rom, or a specific way that I have to flash the modem? I don't like using Odin, because I'm not very familiar with it. But is that the only way to actually flash the modem?
Any help is greatly appreciated. The reason I need to flash the modem is because I am not able to text or call at all after installing the MOAR rom, backups that I created beforehand don't work either, conveniently.
Click to expand...
Click to collapse
First lets establish some basics.. Since the custom ROMs don;t mess with the modem, what modem do you have installed? Check it on the settings/about phone page.
If its not the latest OEM Verizon VRBMB1... , how did it get on there?
I highly recommend using ODIN to flash back to OEM stock and check your signal on that setup. You will lose root, but it will fix most storage issues and force your modem back to the correct setup.
What recovery are you using ? CWM or TWRP? what version?
WHen you get back with that info, then we can help.
Spewed said:
Bonestock didn't work, so I'm flashing Vralf2, making sure this is the correct fiel. http://forum.xda-developers.com/showthread.php?t=1755386
None of the links are working correctly to download the VRALF2 file, do you have a link to one that is working or the VRALG1? Can't find that one.
Also, by dialing that and I would assume a signal is required. So far, I can't get a signal anymore after messing with it.
Click to expand...
Click to collapse
Well, DroidStyle's Guide has the VRALG1 file linked via Invisiblek's Goo link. I haven't downloaded it in ages though but I do have a personal copy of VRALF2 or VRALG1 on my computer.
No, a signal is not required. I have helped plenty of people who had no signal early on when AOSP 4.2.2 first started due to a loss of IMEI. The steps I listed in my prior post are the preferred steps to resolve a loss of IMEI which has similar issues: no data, texts, or calls.
SlimSnoopOS said:
Well, DroidStyle's Guide has the VRALG1 file linked via Invisiblek's Goo link. I haven't downloaded it in ages though but I do have a personal copy of VRALF2 or VRALG1 on my computer.
No, a signal is not required. I have helped plenty of people who had no signal early on when AOSP 4.2.2 first started due to a loss of IMEI. The steps I listed in my prior post are the preferred steps to resolve a loss of IMEI which has similar issues: no data, texts, or calls.
Click to expand...
Click to collapse
Did what you suggested previously and flashed back to oem, entered the numbers you mentioned and I got "No mobile network" as an error.
As for the other user
current I'm on the OEM 4.1.1 with no room, no bootloader unlocked, baseband version is i535VRBLK3
No more recovery on the phone, all has been wiped and flashed back to stock oem 4.1.1, to no avail issue is still persisting.
Related
Hey guys,
I'm looking for a little help here. My Skyrocket seems to be having radio/modem issues.
Instead of having a symbol that displays cell signal, I have a circle with a line through it. This is true with or without a working SIM inserted. For baseband version it says "unknown".
I've tried flashing to stock and that didn't seem to make a difference. I got this phone second hand so I don't know if the previous owner tried to flash an incompatible rom and borked up the radio firmware possibly?
Any thoughts about what I can try?
That all depends on which method and tar you used. Some tars dont come with the radio. and with the wrong radio on a rom you will get a RIL mismatch and no signal
xcrazydx said:
That all depends on which method and tar you used. Some tars dont come with the radio. and with the wrong radio on a rom you will get a RIL mismatch and no signal
Click to expand...
Click to collapse
So I'm unsure how it got to its current state. (meaning the circle with a line through it) To return to stock I used the K0nane tar that's in the sticky in the dev section. I don't know if that has a radio in it or not but flashing that didn't seem to change things.
JimmyStale said:
So I'm unsure how it got to its current state. (meaning the circle with a line through it) To return to stock I used the K0nane tar that's in the sticky in the dev section. I don't know if that has a radio in it or not but flashing that didn't seem to change things.
Click to expand...
Click to collapse
That doesn't have a radio in it. Look in your "about phone" and tell me what your baseband and android version says.
After that I will probably say to flash the sammobile tar...
Also, Did you have the correct plan added to your service when you switched phones?
baseband version = unknown
JimmyStale said:
baseband version = unknown
Click to expand...
Click to collapse
Right..
Assuming your plan has been provisioned for the new lte phone, I would flash the sammobile tar in odin
I'm going to give that a try. I suppose I'll just search for sammobile?
The SIM i'm using was provisioned for my previous Skyrocket. I ended up trading that but used the same sim in my new phone. So, I'm assuming the SIM/my account should be proivisioned for LTE since I never had AT&T change anything on their end.
And just to clarify, this doesn't really seem to be a "no service" type problem since its as if the radio isn't even recognized by the hardware.
JimmyStale said:
I'm going to give that a try. I suppose I'll just search for sammobile?
The SIM i'm using was provisioned for my previous Skyrocket. I ended up trading that but used the same sim in my new phone. So, I'm assuming the SIM/my account should be proivisioned for LTE since I never had AT&T change anything on their end.
And just to clarify, this doesn't really seem to be a "no service" type problem since its as if the radio isn't even recognized by the hardware.
Click to expand...
Click to collapse
Right, seems to be a ril mismatch.
Factory reset and then flash the sammobile tar
http://www.sammobile.com/firmware/
I'm downloading now. I'll report back after I flash.
JimmyStale said:
I'm downloading now. I'll report back after I flash.
Click to expand...
Click to collapse
Cool, hope it works for ya!
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
icenight89 said:
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
Click to expand...
Click to collapse
There you are! Where ya been man?
icenight89 said:
every time I see a thread like this, I can only count the number of posts until x says "flash Sam mobile tar," and then poof! problem solved. lol I just wished people read around a little more
Click to expand...
Click to collapse
Lol, I appreciate the helpful info in your reply. Just so you know, I don't seem to be having the same issue as any other post that I've seen. Unlike the other posts I've read, I don't have "no sim" or no signal, or no LTE. My problem almost seems like an issue with the SIM slot itself. I think I can rule that out because I've actually replaced the SIM slot with a known good SIM slot. The other reason I think I can rule this out is because I am unable to access the radio related content from within the service menu. Unfortunately I don't think there will be a :oof:: that fixes what I have going on. (I wouldn't mind being wrong on this)
So I flashed the sammobile tar (multiple times) but no luck. The baseband version still reports as "unknown". What's more, my phone reboots after about 15 or 20 seconds. Very odd. Any other thoughts on things to try?
JimmyStale said:
Lol, I appreciate the helpful info in your reply. Just so you know, I don't seem to be having the same issue as any other post that I've seen. Unlike the other posts I've read, I don't have "no sim" or no signal, or no LTE. My problem almost seems like an issue with the SIM slot itself. I think I can rule that out because I've actually replaced the SIM slot with a known good SIM slot. The other reason I think I can rule this out is because I am unable to access the radio related content from within the service menu. Unfortunately I don't think there will be a :oof:: that fixes what I have going on. (I wouldn't mind being wrong on this)
So I flashed the sammobile tar (multiple times) but no luck. The baseband version still reports as "unknown". What's more, my phone reboots after about 15 or 20 seconds. Very odd. Any other thoughts on things to try?
Click to expand...
Click to collapse
post a screenshot of the about phone
flash cwm via Odin, flash my efs fix from the sticky, and then re flash the Sam mobile tar via Odin.
xcrazydx said:
There you are! Where ya been man?
Click to expand...
Click to collapse
dude life got BUSY all of a sudden. I come back, u got team waffle, u traded in our wip rom for an aokp t989 port, and a whole bunch of other stuff poppin off (ucle2). WTH lol, I wish I coulda been apart of at least a lil of it.
Flash the stock rom and radio and radio then dial #*2263# and click automatic. Then wait a minute or so and see if it goes back to showing the bars.
Sent from my Skyrocket 4G LTE using XDA Premium
I'm going to try the multiple suggestions I got and report back. I'm also attaching the "screen shots"
Hopefully the attachments are here
I flashed EFSFix through CWM and then SAMMOBILE tar through ODIN. No luck, but ODIN did take about twice as long as it did the first time I tried flashing the sam .tar. Same symptoms, circle with a line through it and phone reboots itself after about 20 seconds. The baseband version still reports as "unknown".
I flashed back to stock through ODIN, flashed CWM with ODIN, and then flashed EFSFix again. Same exact results as the first time.
Next I flashed back to stock using ODIN, and flashed UCLE2 ROM through ODIN. Flashing this causes the reboot issue to go away, but the radio issue remains. (I thought to try the UCLE2 ROM because that's what was loaded when I first received the phone and the phone wasn't rebooting itself then)
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
x714x said:
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Click to expand...
Click to collapse
Good advice, but I'm pretty sure he would need to repair his imie before the code
If I helped you in some way.... pass on the favor and help the next person!
x714x said:
You most likely lost you imei/min or something, you can check in settings>about phone>status. Easy way to correct it is to flash a older stock ICS image and use the reprovision code. Flash this in odin then type this in the dialer *2767*3855# and that should fix ya back up. Flashing anything carries a risk of dropping your imei but it happens much more on AOSP roms.
Click to expand...
Click to collapse
OK, so I was able to get signal back (shows 4/3G), however she is unable to actually text or call from her number. She can use google voice though, so I am guessing it is something specifically with her number. Maybe the IMEI thing you mentioned. Assuming she has her signal back, would dialing that set of numbers reactivate her, or would I still have to do the ODIN steps?
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
It there is data then that dialer code should fix the calling, but you need to be in ics to do it
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Mindstar1 said:
Yeah, I am pretty sure she has data. She is not at home, and when she left a bit ago we thought all was well (since she had the 4G indicator whereas before it said roaming) but she just used GVoice to text me to say that she cannot call or text using her VZW credentials. When you say that she needs to be in ICS, would any ICS rom do? She is in the newest version of Cleanrom right now, so I will have to flash something else I think. As for using ODIN, that is kinda out of the question because we are on vacation and the internet here sucks. It would take 2 weeks to download the stock VZW image, but if that is the only option then I guess that is how i goes. Thank you in advance for all your help!
Click to expand...
Click to collapse
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
I know it didn't work on some custom. I do know it works on route 66, but I've got a solution. Use mobile Odin and download the ROM straight to the phone.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Mindstar1 said:
Im actually downloading a torrent of the stock image for regular desktop ODIN and it is moving fairly quickly. That being said, using a custom rom would be easier (wouldnt I not have to use ODIN at all, just flash it like a normal rom?). If that is the case, can I download your route 66 rom, boot into recovery, wipe, flash then use the dialer code?
EDIT: Whoops, I misunderstood your previous post. I think we are talking about the same thing. I am torrenting the route 66.tar file right now. You are suggesting that I use VZW 4G on her phone to dl the tar file then flash with mobile ODIN? I have never used mobile ODIN to my knowledge so I am not sure how to go about that.
EDIT 2: I just checked out mobile ODIN on the market, and that seems easy enough. So I just finish this .tar dl, put it on her SD, load the app and follow its directions to flash it. Once that is flashed, reboot and dial that code. Then Flash whatever rom I want (say, back to cleanrom). Is that about right?
Click to expand...
Click to collapse
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
kintwofan said:
That's pretty much it, with mobile Odin you'll just click open file. It will put the different parts (kernel, recovery,etc) in the correct section. Then you click flash, support easy and faster then normal Odin. Also if you make a backup before doing this you can just restore your backup after fixing the network problem.
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Same problem!!!
Mindstar1 said:
Hey guys, I am at the end of my rope here, so maybe you can help me out.
I have been dealing with the Media service bug that drains battery super fast for the last few days on my wifes rooted SGS3, and I have been jumping between roms, deleting SD files, searching for corrupt apps/media all to no avail. Tonight, in an effort to fix this issue, I flashed the most recent CM10 nightly as I heard it had a fix for this issue. I have no idea if that is true, because when I got to the setup screen after flashing, I kept getting an error that said that setup crashed and could not run. I had to boot back in to recovery, flash again, only to find the same error.
I then attempted to flash clean rom, except now I see that her phone is always roaming where my Note2 right next to it is on 4G. I flashed an older CM10 nightly for her, and the same issue popped up where it is only roaming.
Did the failed CM10 flash screw something up? How can I get her off roaming and back on 3/4G? Thanks!
Click to expand...
Click to collapse
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Mindstar1 said:
You are awesome! I am sure you factored this in to your suggestion, but if I backup her current rom, then ODIN, then restore, it will not undo what I did with ODIN, correct? Again, I am pretty sure it wont, but I was also pretty sure I knew what I was doing when I flashed CM last night and look how that turned out. Thanks again!
Click to expand...
Click to collapse
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
stk162 said:
Can someone give me a very simplified rundown to fix this problem. I flashed the CM10.1 nightly and lost service as well. I noticed someone posted the solution in the comments but i don't understand all that funky talk. PLEASE HELP
Click to expand...
Click to collapse
Haha, this is why CM warns us not to flash the nightlies unless we know what we are doing, which you and I did not I guess.
Basically, to get your cell signal back you need to flash back to a different firmware version. You do this through a program called ODIN which is a desktop program for Windows or a paid app in Android. I am going the paid app route mostly because it is a bit easier, but the desktop version is free.
I have not tested the solution yet, but I have read on other posts that it works. If you do the app route, you select the firmware file with the app, run the process (it should be self-explanatory in the app), then once the new firmware is on, you dial a special verizon code to get your signal stuff fixed. Below are the files you need.
http://forum.xda-developers.com/showthread.php?t=1762204 (this is the firmware file that you will flash using ODIN)
https://play.google.com/store/apps/details?id=eu.chainfire.mobileodin.pro&hl=en (this is the mobile ODIN app)
Dial *2767*3855# once you have the firmware on to in theory fix the signal issue
After that, you can reflash your rom, but do not flash the CM nightly again!
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
OK, so a bit of a hiccup. I ran ODIN with the .tar file you suggested, and after going through the expected flashing and what not, the screen went black with my LED notification light blinking blue. I pulled the battery after about 10 minutes of this, booted into recovery then rebooted and it did the same thing. Ideas?
kintwofan said:
It shouldn't undo what you're doing now
If I helped you in some way.... pass on the favor and help the next person!
Click to expand...
Click to collapse
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Mindstar1 said:
To clarify, it takes me to a menu called "Android System Recovery" with the following options:
reboot system now (takes me to the black screen)
apply update from external storage
wipe data/factory reset
wipe cache
apply update from cache
Any idea what I should be doing or what I did wrong?
Click to expand...
Click to collapse
That's stock recovery. Not sure why it's not booting correctly. I would say just use desktop Odin and re flash
If I helped you in some way.... pass on the favor and help the next person!
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Did you get this fixed?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open serial COM port"
Mindstar1 said:
Its not looking good... I am in desktop ODIN and it is running, but already there was a failure in the first block, and the log says "cant open COM port"
Click to expand...
Click to collapse
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Make sure you have the drivers installed and have rebooted computer. Also did you verify the md5 of your download
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did not reboot after the driver install, so I will do that. As for the MD5, what is that and how do I verify? You are talking about the firmware download, right?
aight so ive searched and searched for all kinda different methods. and done all of them. is it possible to have a permanent brick?
heres the story. i had been running cm10 for prolly 4 or 5 months. no problems. i wanted to check out liquid smooth rom. so i flashed it. no problems. had been running it for a month or so then one day at work when i went on break my network was gone. my apn's were deleted. came home inspected some more and my imei was unknown as well as baseband and many others were unknown. i took it back to stock many times using. gtg method. using heimdel. using odin. with different stock files. from different websites. including xda. i have tried just about everything to re do the phone. including going back to cm10. and other known working roms. ive *#*#4636#*#* and manually switched to gsm which wont change when i click it it still says unknown.
i dont belive it is a rom problem. i have been overclocked 1300mhz. what else is out there can i try. \
\
any help will be very appreciated
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
FauxAffliction said:
Have you by chance odined back to stock then reupgraded to JB? If not I can get you the necessary steps to do so...let me know
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yea i went to stock and back to cm10. still nothing. buttt now im unable to do any kinda flashes. im on rooted 2.3.6 threw odin. and no matter what i flash it will say somthing on the lines of failed to find file signature or what ever that code is. i tried changing the cwm in different ways still wont get off the what is it 2.5.2 cwm blue. ive basicly gave up. it seems its to far bricked or whatever the case may be
im sorry i need to correct that. i have not been able to flash to any other roms. i didnt go to stock and then cm10, due the the signature deal on cwm. i was thinking of another time i had problems. so no i have no been able to go to jb after the imei has went unknown
Did you flash a custom kernel to get cwm after going back to stock?
andros11 said:
Did you flash a custom kernel to get cwm after going back to stock?
Click to expand...
Click to collapse
im in able to flash anything.....
really? no one can help me?
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
psal217050 said:
Are you trying to flash through Odin? Or through CWM?
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
kritz84 said:
dont know how to flash a cwm threw odin. i tried loading a cwm threw rom manager and manually
Click to expand...
Click to collapse
but im pretty sure the problem isnt with cwm im more interested in why and how to the imei isnt known and how to fix this problem if theres a cure
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
andros11 said:
Download a heimdall one-click or odin back to stock pack. Open either one up and put your phone in download mode:
- turn off and have the usb cable connected to the pc.
- remove and reinsert battery
- hold both volume buttons and connect usb. Phone should now boot into download mode.
Run program and you will be good. Then look for entropy's dd kernel and flash it in download mode to get cwm.
Click to expand...
Click to collapse
i guess u didnt read my first post. ive already done that. ive done many things....
but anyway weirdest thing just happend. i have been using my phone via wifi. so its been on a while without a sim card inside of it.
\
i noticed i had signal bars. i looked at the imei and its was a number. it was a different iemi then what its supposed to be but there was a imei. baseband was still unknown but anyway i shut the phone done and inserted my sim card. btw its a straight talk sim. and restarted it now im back to unknown imei......
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
kritz84 said:
ok so im back on cm10. before i was on cm10 its was giving me the imei which wasnt my original imei. i guess cuz i flashed a efs.tar. but anyway i was able to make a phone call. now im flashed on cm10. and no imei no baseband nothin. i tried flashing the efs again with odin and still nothing. when i do the *#*#4636#*#* it still wont let me switch to gsm. and i cant add a apn.
Click to expand...
Click to collapse
odin or heimdall back to stock.
follow andros11's guide on how to flash jb
he spent the time to write the guide; spend the same amount to time to read the guide
Seems IMEI was kidnapped about a month after Liquid
Ironically, I seem to have EXACTLY the same issue that this original poster has. I have been flashing my Infuse for a little over a year now and I Flashed Liquid, I'd say about 3 weeks ago, maybe end of November. Everything has been smooth sailing. About a 2 days ago I started noticing that my network would just drop - for no reason. But at first it came back. Ok, no problem, probably just a glitch. However yesterday morning it happened again and then I was without the use of data for most of the day until around 6pm. It came back but the bars were grey but I was able to make a phone call. Once I made another call it did not go through, I tried to hangup and it just hung there. there was nothing I could do to get it to hang up. Rebooting the phone resulted in no bars at all. Nothing, nada, ziltch. So last night I reflash it a couple times and notice that there was an update to Liquid (2.1 beta). cool. I wipe, flash 2.1b and it is beautiful. EXCEPT for the fact that I have no network. wifi works fine, but no carrier whatsoever. GRRRR. I decided to back every thing up (have done so several times in the past), stock back down to 2.3.6. Barebones and all it all looked great until I hung up the phone... Same thing. So I went all Rambo on the phone, wiped it down to the very last compound. AT&T wouldn't know the wiser if they took it from me. Master Reset, wiped files, data, I think I took an IC out with all of the wiping I did... Result? No IMEI, circle with the slash. Upset, disappointed and dejected I slumped back to XDA (after I went on Craigslist feeling my phone was broke) to see if I missed anything. That was where I found some links about missing IMEI. To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Dnice808 said:
To make a long story short, I DO have an old copy of EFS thanks to QKSTER, but I have no idea how to restore. I swear I have been on this since 6:30am and just now am I finding these threads. Must have gone through about 50 others... Sigh. BTW, along the way of my flashing experience today, my network came back temporarily, but I have not relied on it because I knew it would leave me. Just don't know how to use Heimdall to restore. To make a long story short, using Windows, could someone please help me with how to restore my EFS to see if this would solve my dilemma?
808
Click to expand...
Click to collapse
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
After this, check your imei and band. If it works, no further back up is needed.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
So it is in the .tar format that your script backed it up in. Finding another link on the we (which he also linked back to XDA, http://forum.xda-developers.com/showthread.php?t=1264021 I was able to take my backup (that I used with your script) and follow his steps -mostly- (my/your backup had a 'root' folder that had the nv_data.bin file in the afs/settings folder while the instructions did not mention that. I followed the backup location settings (which in turn was also the same as the default that I had backed up)) and replace the EFS folder. It still did not restore it in any flash image just like that. Still had the the circle w/slash. However while I was still searching and typing out that loooong last passage I wrote, my phone network came back for a little while. I know this because I began receiving a bunch of texts. I was able to make a phone call. But it still happened again when I made another, it did not go through and when I hung up, it just stayed there looking at me with its grey, blank look. Even killing the phone app did not work. I rebooted back to the same drama.
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
I actually was on 2.3.6 using your posts, first the basic rooted flash having to then using the Entropy kernel and then I did the lazy flash that was already rooted and just having to add the vold file to /system/etc/blah/blah. I do want to add that I DID have wifi active at this time and it may not be associated, but the first poster did mention he felt it may have had something to do with it. With wifi on, after awhile of me NOT looking at the phohe (actually doing so made me want to HULK SMASH), the network came on and my texts came in. I was able to look in settings and see ATT, and my IMEI. I was almost finished with my passage to you so I decided to update to Liquid 2.1 beta, but moving up to JB, then to LiquidSmooth. Of course doing so I got the circle w/slash, but wifi started restoring my apps.
Earlier I mentioned that I did a whole rubba dub dub, meaning I did do the /settings/privacy -reset thingy, wiping the phones carcass. I will do it again (at this point nothing to lose), following everything you ask to a 'T'.
808
Click to expand...
Click to collapse
qkster said:
What is the format of your EFS folder?
*.zip
*.tar
just a folder?
If you have lost the signal while on JB, see if you can factory reset the phone.
/settings/privacy -reset
Then put it into download mode.
Done.
Use the heimdall 1 click uclb3 and flash it once, then without closing heimdall, check the bootloader box and flash it again.
Done
After this, check your imei and band. If it works, no further back up is needed.
Sigh, did not do a darn thing. Circle w/slash.
If you're still missing the imei, you can flash one of the gb kernel in the second post to get cwm.
Done.
Then use the root pack in post #2,
http://forum.xda-developers.com/showthread.php?t=1629079 to install root and su.
install a root tool like root explorer (remember to toggle the r/o r/w) or adb and copy the /efs into the phone's root efs folder,
reboot
check the baseband.
Went in Root Explorer, did the toggle, deleted the contents of efs then copied the contents of my backup into there. Rebooted. Nada.
you can also check this thread
http://forum.xda-developers.com/showthread.php?t=1895500
I then was going to try the other link using Odin, but I cannot get Odin to see my phone. I read some thread talking about if I use Heimdall I will have problems using Odin because they use the same ports? How frustrating. The weird part is now that I have the flashed, rooted 2.3.6 image and using wifi, at some point tonight my network may come back on. Or it may not.
808
Click to expand...
Click to collapse
Bugged out, huh?!!???
Dnice808 said:
Bugged out, huh?!!???
Click to expand...
Click to collapse
I wasn't sure if there was a question there.
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
qkster said:
I wasn't sure if there was a question there.
Click to expand...
Click to collapse
Me stating that it is bugged out, was me just confirming that it is Weird!
qkster said:
From my experience, flashing to JB (MTD partition) from GB without going through ICS may result in lost of imei.
Sometimes, it just happens. I had very limited experience with JB.
Click to expand...
Click to collapse
Ok just to explain myself better. I have been saying that I was going from GB to JB when in fact I meant to say that I was going from GB to ICS. Sorry for that. Also, the reason my responses have looked wacky is that I was trying to select the multi quote button and getting no response. Hopefully this response is a little more organized.
qkster said:
The few methods that I've tried worked for me. Just simply flashing back to stock with a re-partition ( (Heimdall -1-click for me) usually brings back the /efs and imei without doing anything extra.
If you haven't, and if you can, I would try the heimdall-1-click a few times.
Click to expand...
Click to collapse
See that is what confuses me too. I have flashed back and forth several times at this point, and sometimes the /efs and imei do come back, but now they have never stayed. It is the only reason why I have tried to pretty much rule out a hardware issue. Even when I flash and there is no imei, there is the same /efs folder. And when I wipe the whole thing sparkling clean, even the newly formed /efs folder has the correct imei but it is just not being recognized on the phone.
qkster said:
If you want to use Odin, you may need to reinstall samsung drivers and use a different usb port on the PC than the one you used for heimdall.
Click to expand...
Click to collapse
Of course what I did was accidentally leave my phone home preventing me from testing it out with Odin on another machine. Its all good though.
qkster said:
You may also want to check the signal of the phone at your location. you may be getting poor signal and it has nothing to do with the phone's OS
Click to expand...
Click to collapse
I have an AT&T prepaid phone and the sim from the Infuse works in it flawlessly...
808
Yes, I have already posted this in the ROM's thread (Galaxy mod RLS 16), I'm just trying to get answers as fast as possible.
Out of ABSOLUTELY NOWHERE, I cannot make calls or send texts at all, yet my data works. I don't have a clue what I did, I rebooted into recovery and did a complete wipe and reinstall of RLS16 and it STILL doesn't work. When i try to text it says "cannot send message" and when i try to call it says "Assisted Dialing" but doesn't even ring or connect at all. I've tried tinkering with my settings under Mobile Networks and it still doesn't work.... I'm not even 100% sure what they should be set to.
Somebody please help cause I am COMPLETELY stumped here. I can post screen shots of my settings if need be too.
Sent from my SCH-I535 using xda app-developers app
Did you lose your IMEI? I think that would cause this sort of error.
rgrossie said:
Did you lose your IMEI? I think that would cause this sort of error.
Click to expand...
Click to collapse
Yes I did, I am in the "[Tool][Win] Repair IMEI & Roaming ERI issues" thread now, and tried to start the process but after dialing *#22745927 in the "TouchWiz Diag" instructions, nothing happens on my phone.....so I am stuck and don't know what to do......??:crying:
I believe you need to be on ics for the codes to work.
Hopefully someone with more knowledge can help, I've never lost mine.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
I believe you need to be on ics for the codes to work.
Hopefully someone with more knowledge can help, I've never lost mine.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Who knows? It doesn't say anything about that on the "http://forum.xda-developers.com/showthread.php?t=1867442 thread which I've reread 47,000 times and no one is replying on there to help me.:crying:
flooritnfly said:
Who knows? It doesn't say anything about that on the "http://forum.xda-developers.com/showthread.php?t=1867442 thread which I've reread 47,000 times and no one is replying on there to help me.:crying:
Click to expand...
Click to collapse
It's been just about an hour, you need to chill out. In that ERI thread, Pdykstra and others have suggested dialing the reprovision code on ICS roms multiple times. Odin flash VRALG1 tar found in DroidStyle's guide in the dev section then run this code. It will format /sdcard. Dialer codes are blocked on JB roms/modems because they presented an exploit when triggered from malicious websites.
Conversely, for the ERI tool, you need to have VRALF2, VRALG1, or VRALG7 modem (radio) installed for it to work properly.
SlimSnoopOS said:
It's been just about an hour, you need to chill out. In that ERI thread, Pdykstra and others have suggested dialing the reprovision code on ICS roms multiple times. Odin flash VRALG1 tar found in DroidStyle's guide in the dev section then run this code. It will format /sdcard. Dialer codes are blocked on JB roms/modems because they presented an exploit when triggered from malicious websites.
Conversely, for the ERI tool, you need to have VRALF2, VRALG1, or VRALG7 modem (radio) installed for it to work properly.
Click to expand...
Click to collapse
I downloaded the Root66 rom and was about to Odin back to that and then try the tool to fix my IMEI....what about that?
SlimSnoopOS said:
It's been just about an hour, you need to chill out. In that ERI thread, Pdykstra and others have suggested dialing the reprovision code on ICS roms multiple times. Odin flash VRALG1 tar found in DroidStyle's guide in the dev section then run this code. It will format /sdcard. Dialer codes are blocked on JB roms/modems because they presented an exploit when triggered from malicious websites.
Conversely, for the ERI tool, you need to have VRALF2, VRALG1, or VRALG7 modem (radio) installed for it to work properly.
Click to expand...
Click to collapse
Once I Odin back to Root66 rom, should I try the reprovision code before doing anything else? What about the IMEI tool? Should I not even bother trying to do all those steps and go straight to the reprovision code?
flooritnfly said:
I downloaded the Root66 rom and was about to Odin back to that and then try the tool to fix my IMEI....what about that?
Click to expand...
Click to collapse
It's perfect so long as it's VRALF2 or VRALG1 ICS based.
flooritnfly said:
Once I Odin back to Root66 rom, should I try the reprovision code before doing anything else? What about the IMEI tool? Should I not even bother trying to do all those steps and go straight to the reprovision code?
Click to expand...
Click to collapse
Odin flash then let's try the reprovision first. If that doesn't work then you have the much longer method in the ERI tool to utilize and it should recognize your phone since you're on an older based modem.
SlimSnoopOS said:
It's perfect so long as it's VRALF2 or VRALG1 ICS based.
Odin flash then let's try the reprovision first. If that doesn't work then you have the much longer method in the ERI tool to utilize and it should recognize your phone since you're on an older based modem.
Click to expand...
Click to collapse
Ok, so I should:
1. Odin back to Root66 rom (what about the modem? How do I do that? Or once I Odin back to Root66 will that take care of that?)
2. Dial reprovision code
Then what?
Also, what do I do if I get stuck in a boot loop?? My biggest problem is that I do not have home internet at all, my main source of internet is via tethering from my phone.....so I need to have all the instructions/options/answers before I start to do this!
flooritnfly said:
Ok, so I should:
1. Odin back to Root66 rom (what about the modem? How do I do that? Or once I Odin back to Root66 will that take care of that?)
2. Dial reprovision code
Then what?
Click to expand...
Click to collapse
When you Odin flash a full stock rom tar, it's like "reverse" applying an OTA. It installs everything: kernel, rom, modem, bloatware, locked bootloader, etc.
So:
1-2) Correct, do these.
3) Check your IMEI/ERI, don't post your actual IMEI if it returns to what is printed underneath your battery. Your iMEI is like your phone's SSN to Verizon, no IMEI = no network access as you so recently found out. You can even send out a text/call and definitely check if data works.
Edit: To answer your bootloop question. If Odin flashes the tar properly but when you reboot you are stuck in a bootloop OR it does not boot past the Samsung/Verizon splash, pull the battery then hold volume up, home, and power to boot into stock recovery and perform a factory reset.
To make sure I state this for the record, I personally suggest using the VRALG1 tar found in DroidStyle's guide in the dev section. Root66 will definitely work as well.
SlimSnoopOS said:
When you Odin flash a full stock rom tar, it's like "reverse" applying an OTA. It installs everything: kernel, rom, modem, bloatware, locked bootloader, etc.
So:
1-2) Correct, do these.
3) Check your IMEI/ERI, don't post your actual IMEI if it returns to what is printed underneath your battery. Your iMEI is like your phone's SSN to Verizon, no IMEI = no network access as you so recently found out. You can even send out a text/call and definitely check if data works.
Click to expand...
Click to collapse
Ok, I will try this, but did you see what I added onto the end of my last post?
flooritnfly said:
Ok, I will try this, but did you see what I added onto the end of my last post?
Click to expand...
Click to collapse
Also, super noob question, but assuming that fixes everything, how do I unlock the bootloader and get back up to the most recent version of Jelly Bean, but rooted of course and thus free to flash any rom I want again?
Ok I am going to try it, hopefully you will be around when I am next able to tether successfully and have internet access....it could be half an hour or it could be 4 hours but I will post what happens in here when I can.....hopefully you will be around....Thank you for your help thus far
See my edit above (post #11) which I posted at the same time you replied above.
flooritnfly said:
Also, super noob question, but assuming that fixes everything, how do I unlock the bootloader and get back up to the most recent version of Jelly Bean, but rooted of course and thus free to flash any rom I want again?
Click to expand...
Click to collapse
If you use Root66, you'll just need to unlock your bootloader using EZ Unlock v1.2 which you can find via a quick google search. There is a thread on Rootzwiki which contains EZ Unlock v1.2, just install that app, tap the Unlock button and you're unlocked. That was easy. However, if you Odin flash stock VRALG1 (or VRALF2) then you can root/unlock however you so desire just make sure the root/unlock tool is specifically for your firmware.
The thing is, once you have confirmed that your IMEI is back and you can talk/text/surf again. I need you to
1) root
2) unlock
3) backup your IMEI using part A and B in this thread. This way, you don't lose your IMEI and have absolutely no way of retrieving it again.
SlimSnoopOS said:
See my edit above (post #11) which I posted at the same time you replied above.
If you use Root66, you'll just need to unlock your bootloader using EZ Unlock v1.2 which you can find via a quick google search. There is a thread on Rootzwiki which contains EZ Unlock v1.2, just install that app, tap the Unlock button and you're unlocked. That was easy. However, if you Odin flash stock VRALG1 (or VRALF2) then you can root/unlock however you so desire just make sure the root/unlock tool is specifically for your firmware.
The thing is, once you have confirmed that your IMEI is back and you can talk/text/surf again. I need you to
1) root
2) unlock
3) backup your IMEI using part A and B in this thread. This way, you don't lose your IMEI and have absolutely no way of retrieving it again.
Click to expand...
Click to collapse
Ok, you want me to stick to EZ Unlock v.1.2 even though the latest is 1.4?
flooritnfly said:
Ok, you want me to stick to EZ Unlock v.1.2 even though the latest is 1.4?
Click to expand...
Click to collapse
Yes, v1.2 will work unquestionably.
SlimSnoopOS said:
Yes, v1.2 will work unquestionably.
Click to expand...
Click to collapse
Gotcha. Currently backing up my internal sd to my pc then I am going to start this whole process and hopefully I will be successful....
flooritnfly said:
Gotcha. Currently backing up my internal sd to my pc then I am going to start this whole process and hopefully I will be successful....
Click to expand...
Click to collapse
Lastly, to clear up any ambiguity about the root/unlock process. You have two options:
Option a) If on ICS VRALF2 or VRALG1, use NoxiousNinja's thread to root your firmware then use EZ Unlock v1.2 to unlock your bootloader.
Option b) Use Open1your1eyes thread to upgrade to VRBLK3 then root/unlock.
You still need to backup your IMEI using the Comprehensive IMEI/EFS thread.
Ok I just Odin'ed the Root66 rom and it said Pass and Successful but rebooted and it won't get past the 4G LTE Splash screen (the one with the colorful circles that zoom out with the LTE logo in the middle).....
Since I do not have enough posts to ask on the developers thread, I was wondering what modems i could flash on SlimKat because i have not been able to send long texts. I tried using both the padded modems for newer roms as well as the GB/Froyo modems and i wouldnt get any signal at all and it said that the baseband version was unknown when trying to flash either. Any ideas?
You're in the right forum -- the development forums are generally reserved for active development, not questions about how to use what has been developed. We're a little "sloppy" here because the SGS4G community has gotten a lot smaller in the past few years, but still a good habit to get used to.
@FBis251 maintains a repository of modems, padded for the various ROMs.
Try the various ones and see what works well for you.
jeffsf said:
You're in the right forum -- the development forums are generally reserved for active development, not questions about how to use what has been developed. We're a little "sloppy" here because the SGS4G community has gotten a lot smaller in the past few years, but still a good habit to get used to.
@FBis251 maintains a repository of modems, padded for the various ROMs.
Try the various ones and see what works well for you.
Click to expand...
Click to collapse
Thanks! I tried all of the modems except for the cm7 but when i get more time or when i get frustrated with not being able to send long texts i guess i know where to look.
So i tried all different types of modems and no matter what i would get "unknown" for the baseband version and i would not get signal.
Link119 said:
So i tried all different types of modems and no matter what i would get "unknown" for the baseband version and i would not get signal.
Click to expand...
Click to collapse
Have you also lost your iemi numbers?
When i reflash the rom (which recovers the modem to kj6) then i would would get signal again so i take it that my imei numbers are still intact. I also have used odin to flash modems before and it always worked with the kj6 rom (with any other modem).
Link119 said:
When i reflash the rom (which recovers the modem to kj6) then i would would get signal again so i take it that my imei numbers are still intact. I also have used odin to flash modems before and it always worked with the kj6 rom (with any other modem).
Click to expand...
Click to collapse
I would suggest using recovery (TWRP or CWM) to flash the padded modem file, less room for error. I use the KJ5 Modem which works for me, had the same issue with long texts on KJ6.
I did try it at least twice on TWRP with the same results... Were you on SlimKat/BeanStalk(4.4.2)?
Link119 said:
I did try it at least twice on TWRP with the same results... Were you on SlimKat/BeanStalk(4.4.2)?
Click to expand...
Click to collapse
Yes, Slimkat. Flash the ROM. Then go back to recovery and flash the modem file of your choice. You should be able to then confirm in your Settings-> Status screen. You should see the baseband change, if not there is something wrong.
ariesgodofwar said:
Yes, Slimkat. Flash the ROM. Then go back to recovery and flash the modem file of your choice. You should be able to then confirm in your Settings-> Status screen. You should see the baseband change, if not there is something wrong.
Click to expand...
Click to collapse
Which file did you use? Was it one of the padded modems or just a regular one?
Link119 said:
Which file did you use? Was it one of the padded modems or just a regular one?
Click to expand...
Click to collapse
Use the Padded Modems found here: http://forum.xda-developers.com/showthread.php?t=1192436
I personally use KJ5, which is this specific file: http://sourceforge.net/projects/tea...d/sgh-t959v_mtd_kj5_padded_modem.zip/download
ariesgodofwar said:
Use the Padded Modems found here: http://forum.xda-developers.com/show....php?t=1192436
Click to expand...
Click to collapse
I flashed the KG4 padded modem and i am still getting an unknown baseband after letting my phone sit for about 5 minutes after flashing.
Did you check to see if there is anything under your APN... Settings>mobile networks>Access Point Names...maybe add it manually if there is nothing there.
Sent from my SGH-T959V using Tapatalk
I did not, but would anything show up if the Baseband is saying unknown? I am back to the stock modem (kj6) because i needed to get my signal back.
Edit: So the problem still isnt solved, but long texts are sending (before i would get an error message saying failed) so i dont need to worry changing the modem anymore. Thanks for helping guys even though it didnt work out!
Link119 said:
I did not, but would anything show up if the Baseband is saying unknown? I am back to the stock modem (kj6) because i needed to get my signal back.
Edit: So the problem still isnt solved, but long texts are sending (before i would get an error message saying failed) so i dont need to worry changing the modem anymore. Thanks for helping guys even though it didnt work out!
Click to expand...
Click to collapse
Had the same thing happen to me. Kept asking and received the answer that worked for me. Just make sure your CWM or TWRP recovery images are updated to the very latest. Should work. Been testing modems back and forth for a couple days now. Still getting sudden signal drops though. I wondering if T-Mobiles update to their towers isn't compatible with our hardware. Seems coincidental that many had this problem start right around that time. Trying to force us to upgrade devices tailored to their services provided...haha anyways...I'll stop ranting now
Sent from my myTouch 4g using xda app-developers app
Just use a file manager to copy the modem.bin file to /radio/
I tried flashing from TWRP and got the unknown baseband error as well. Manually copied it over and all is well now.
The modem installer zips were written for ICS roms. They might have worked on some JellyBean roms but I definitely never tested them on KitKat. @Dwack has the right method for this though, copying by hand should work fine since that's all the .zip files do.