Hello everybody,
I have a big problem with my phone.
Basically, I messed up my phones system apps so I decided to root my phone and put a custom rom onto it.
But I really missed my original layout so I decided to find a stock rom and put that on my phone (unrooting it)
So that worked, but my mobile network isn't working at all!
So I tried to put a different stock rom on to see if it was just the rom.
But my PC wont let my phone connect whilst in download mode.
Does anyone know how to either;
- manage the EE Internet so it works
Or
- how to fix my connection between my phone and computer
USB debugging it ticked
I have USB drivers
I'm using a working USB port
I'm using stock USB wire
This is from the UK
Thank you for any help!
What does your imei say and have you flashed a modem to try to fix the signal issues
Sent from my SGH-T889 using xda app-developers app
I in addition to what Sigma asked, which specific model do you have? The t mobile US version is SGH-899 for instance.
You may need to Odin the correct .tar for your device, but you should be able to get back to where you need to be.
Hastily spouted for your befuddlement
Hello
Hello, I haven't been able to find a modem file to flash.
And even if I did find one, my phone doesn't connect to Odin through download mode anymore where as it did before I flashed stock rom back on.
Ahh I really don't know what to do
I have the galaxy note 2 n7105 tmobile UK
Have I perhaps flashed the wrong stock rom?? :s
I can't even root my phone anymore!!!
What does your imei say? Reinstall the pc drivers in your computer. There is more the one thing going on here if your brother's known good phone won't connect either.
Hastily spouted for your befuddlement
I've already reinstalled Samsung drivers
And where do I find my imei?
Bump
NVM
IMEI is located in the settings menu under About Device > Status. If that is missing you will not get data off the towers.
Can you connect another usb device to the computer and see it function? What OS is your computer running?
Hastily spouted for your befuddlement
Solved!
I solved it when I stocked this rom back onto my phone, it had the access point name connected to virgin mobile :s
I have no idea why lol.
So I researched what the tmobile one was and put it in and it fixed it
Thank you for helping! Rally appreciated.
Try Odin, the toolkit in the original android development have all the tools you need
Sent from my SGH-T889 using xda premium
Related
I was working on CDMA Work Shop to update my NV items when i mistakenly wrote Galaxy S3 NV items which i had backup earlier.
Since im using a Sprint based CDMA handset in India i make sure i back up PRL NAM and NV items just to be on the safer side.
Once the NV items of GS3 got written on my Epic i lost my local network and my connection to CDMA Work Shop.
The phone booted, is in Airplane mode, it wont come out of it.
Now phone does not connect/detect in Diagnostic/Service mode. (##8778# - PhonUtil - USB - MODEM).
it detects fine in PDA mode.
I tried connecting my GS3 in service mode to check if i had the right drivers or if my PC had some other problems the phone just got detected fine.
Was on THUNDERHAWK III when all this happend.
I reset the phone to stock EC05 (just like when i got it) through odin.
problem persists, Airplane mode wont switch off, Pc does not detect the phone and i get a "Modem Exception Occurs" error when i enter MSL code whenever MSL is required.
Background Data works on WIFI but only for Gmail SYN, Market FC's just like stock browser.
Can anyone please help me.
I got it solved. I simply had to reset my NVram. So since I was on rooted stock Rom EC05, I just flashed EC05 modem.bin through Odin with PHONE EFS Clear checked. =-O
Sent from my SPH-L710 using Tapatalk 2
Hey Guys,
I have an AT&T Model SGH-1317 Note 2. For use on other networks, I unlocked the phone using the *#197328640# menu option. However, the phone failed to start the hot spot stating Mobile data was unavailable or Invalid Sim. However, I am able to tether perfectly using the same sim on an another S3 so I was sure its nothing to do with the sim or network operator settings.
I looked up and found XDA website with tons of information. I assumed my phone was locked by AT&T. Hence, I rooted the phone using CF-Auto-Root, backed up complete data using Titanium and using Rom Manager I installed the Crash Aroma 4.1.2 Rom. I wiped the data and cache 3 times as suggested. However, after the boot I am unable to connect to any mobile network. A Click on Mobile Network says "Insert Sim Card to Access Network Services". Dialling for IMEI number prompt a Null.
During Installation I noticed the Crash ROM has overwritten the Radio.. and I am assuming this is were the problem lies. but I leave it you experts.. Request Help!
Sunil.
What carrier are you using the device on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
cdshepherd said:
What carrier are you using the device on?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Am currently on Du - A network in Dubai, UAE. I have been reading more forum information and some suggest that this may be related to the EFS folder getting corrupted which may cause the IMEI number to fail. Some suggest that there are software to rebuild this information by using the IMEI number behind the handset..
I also noted that my phone model has also changed to GT-7100 instead of SGH-1317, Wonder if the Crash ROM was apt?
Would you suggest installing a Jedi Rom specifically built for SGH-1317... or is the damage already done?
Back Online
Since I found no replies.. I had no choice but to give it to the Pros.. I handed my phone day to one of the Unlocking experts at a mobile store… He was confident that his technicians would resolve this. But after 2 Days, they have given up.. He suggested the phone would fetch me US$ 10 if someone used it as a demo unit at a mobile shop..
I was sure this was something to do with the Modem, IMEI and the all important NV folder. I was able to find a Stock ROM for the SGH-1317 and I also found a link at XDA about using EFS pro to change the IMEI.
Using Odin software, I flashed the phone with the stock rom. Unfortunately, there was one error when it tried to communicated on com1. Having no choice, I continued. Restarting got the AT&T style boot but it again froze on the Samsung screen. Dreading the communication error, I restarted several times with no results. Finally I realised if would be due to the cache and user data. I reset the phone to factor settings wiping out the user data and Whola.. The phone sprang back up..
Lessons learnt.. Backup your rom and data before playing with custom roms. Read Read Read and don’t flash in the middle of the night..
Since I am back online, I plan to stick to the stock and crappy 4.1.1 with all the AT&T dead weight. Will live without the ability to Tether until my fingers get warmer.. It won’t be long as I am already bit by the Custom Rom Devil..
Don't Give Up Easy..:good::victory:
Flashaholics anonymous will help.
Sent from my SGH-I317 using xda app-developers app
sunilgonsalves said:
Using Odin software, I flashed the phone with the stock rom. Unfortunately, there was one error when it tried to communicated on com1. Having no choice, I continued. Restarting got the AT&T style boot but it again froze on the Samsung screen. Dreading the communication error, I restarted several times with no results. Finally I realised if would be due to the cache and user data. I reset the phone to factor settings wiping out the user data and Whola.. The phone sprang back up..
Click to expand...
Click to collapse
Please I am having the very exact same issue and can't seem to have it fixed
Using CMW I also flashed it back to stock rom, didnt have any problem or errors doing it but im still getting No SIM Inserted. I have deleted cache and user data several times... Tried flashing CM10 and CrashRom see if they made a difference and still No Sim Inserted... tried 3 different kernels and still same issue
I have the exact same problem since yesterday. I've tried everything and anything to no avail. I'm very close to returning the phone.
I would really appreciate any input.
Same issue
I flashed crash rom 4.5, over the stock kernel and it gave me that same message. I've tried everything I could think of, which included everything in this thread to no avail... any further advice would be greatly appreciated.
imei null baseband unknown, {insert sim to access network error} PLEASEEEE HELPPP ME
i rooted using auto root and installed xposed framework and snapshare and snapprefs :crying:
after that i tried puttin off the airplaine mode and it didnt happen
then the error started to show insert sim to access network god i need help.
sukhraj kohli n7100 said:
i rooted using auto root and installed xposed framework and snapshare and snapprefs :crying:
after that i tried puttin off the airplaine mode and it didnt happen
then the error started to show insert sim to access network god i need help.
Click to expand...
Click to collapse
Your username suggests that you have the N7100 device ??
If so. ..you are in the wrong place for support. ..As this is the SGH-I317 section.
If you are showing IMEI NULL with no baseband you may have to restore your backup image to correct the problem. .
If no backup image exists. ..you will need to flash a factory N7100 image from your section.
Look for the return to stock thread for your specific device and that should fix you up...
The CF AUTO ROOT files are device specific. ..so I hope you haven't damaged the partitions.
Good luck. ..g
Edit:
This will help. ..and will place you in the right section. ..
Just go to page 1...good
http://forum.xda-developers.com/showthread.php?t=2230250
Good Afternoon everyone,
I've been experiencing issues with my Mobilicity S3 T999v.
I recently removed root from the device, and am having issues with the network service. It connects to my service provider koodo, but nothing works. When trying to connect manually it just times out forever.
I have verified i have an IMEI, via *#06# , the phone worked fine before the unrooting. Ive attempted flashing stock firmware a few times now with odin to no avail. Could this be baseband related?
If it makes any difference i used Mskips toolkit for all the rooting/unrooting. Device software still says modified after triangle away.
captaincheese said:
Good Afternoon everyone,
I've been experiencing issues with my Mobilicity S3 T999v.
I recently removed root from the device, and am having issues with the network service. It connects to my service provider koodo, but nothing works. When trying to connect manually it just times out forever.
I have verified i have an IMEI, via *#06# , the phone worked fine before the unrooting. Ive attempted flashing stock firmware a few times now with odin to no avail. Could this be baseband related?
If it makes any difference i used Mskips toolkit for all the rooting/unrooting. Device software still says modified after triangle away.
Click to expand...
Click to collapse
Im going to re-install root via root66, and try a different baseband. Ill let you guys know the results.
captaincheese said:
Im going to re-install root via root66, and try a different baseband. Ill let you guys know the results.
Click to expand...
Click to collapse
ugh didnt go to well. Constant errors about android.process has stopped responding. Think im going back to stock the root66 files are not working for me.
I guess another day of tablet as my phone. :crying:
Can I write it back with VIA_ESNWRITER or is it the same as in the back of the phone still?
all unknown meid,esn,imei,cdma radio,network,phone number
TitanTaber said:
Can I write it back with VIA_ESNWRITER or is it the same as in the back of the phone still?
Click to expand...
Click to collapse
i dont how to post a problem if it is wrong way excuse me ,the issue regarding sprint gnex,below i mentioned thing which i observed in my mobile.in india i contacted samsung services but no use .i dont have place to get solution right now.
hello gurus,
hello my name is sreenath reddy from bangalore city of india.here i have problem with my sprint gnex,that i am using it from past 1 year.
recently i updated to kitkat toroplus cynogenmod 11 nightlies on stock 4.3 worked good for some days.
i went roaming to other state suddenly. i lost signal,empty (meid,imei,esn,phone number,unknown network,unknown icc id),in bootloader
screen lte radio showing, but unknown cdma radios .manually i flashed back to stock but no change.
i flashed to stock 4.1.1 and 4.2.1 and 4.3.when it working i backed up stock 4.3.as well as 4.4.2.
i restored with twrp 2.6.3.2 its taking again it showing unknown all.here one more problem is
i can acess diag but in data mode if i input msl it making the problem stating that modem exception problem.with some apk to force to
ets channel.but it is not taking ets usb mode.i tried to write meid with ets app but it is taking comm port not usb port.
i have to put into ets usb then,only i can recall the obove mentioned things.i tried to rootz wiki
msl finder but no use.i tried of that script manager from xda but no result not found msl,with terminal emulator no result.
to put manually in diag or data mode i need msl.for hard rest i need msl,plz if you encounter the the same problem get me the procedure to do .
currently i am in reliance cdma network.my phone bluetooth and wifi working fine phone also working fine.phone functionning normal
only i can not make calls ,sms,not using 3g.adb working fine,fastboot,odin working fine.
*#*#3282#*#* in this trasaction if i tried with my old msl,modem eception problem, i will get message stating that android process.com stop the process.
i tried of hard reset but it asking msl again.even i flashed team eos rom 4.2.1 but i kept dignostic mode and ets usb mode but useless.
.please some body shed some light on this issue.i am not able
to use the phone from past 30 days.if some one not making the answers from mail through get me atleast
some phone numbers.
i can contact you imm.suggetions will be appriciated.
i am attaching the bug report of my mobile as attachment
thanks,regards
reddy
[email protected]
09591491769
bangalore,india
Hi.
I have a Samsung Galaxy S3 T999 model on carrier T-mobile. Lately the phone has gone nuts and will get stuck on dialing out and will never make the call. Everything else works fine. Sometimes I have to soft reset, pull the battery and that will fix it for a call or two, then it will get stuck again. I have contacted T-mobile about this over 5 times and none of them can help. We tried to change the sim, reset the account. Etc and nothing. I have reset the cache, factory reset and even put in a good working sim card from another phone and the same problem comes up. During my latest troubleshooting I have narrowed it down to where I switch "network mode" to GSM only and that can make calls out all the time, but the data stays on E (which then I can't use the internet because it's so slow) When I switch back to auto I am sometimes able to place calls again, but only a few. After I test a few calls and leave the phone for a few minutes the phone will get stuck back on not making calls out and just saying "dialing".
Has anyone had the same problems or know of a fix? Currently I have been trying to flash the modem to different versions to see if that fixes the problem. The first two modems I have flashed did not work and came up with "unknown baseband".
If anyone can help I greatly appreciate it.
This is a known issue with 4.3.. What firmware are you on? Assuming you flashed the correct baseband for your device, the 'unknown baseband' message sounds like you are in 4.3 but what build? You can't flash any modems successfully less than 4.3
Sent from my SGH-M919 using Tapatalk
serio22 said:
This is a known issue with 4.3.. What firmware are you on? Assuming you flashed the correct baseband for your device, the 'unknown baseband' message sounds like you are in 4.3 but what build? You can't flash any modems successfully less than 4.3
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I was previously on 4.1.2 when the problem first started. I updated it to 4.3 and still the same problem.
jss15j.t999uvuenc2 build. (I put this one back on last night so at least I can use the phone today when I am at work)
I was just hoping that the device didn't go bad when it was on 4.1.2 because it was working just fine before the problem started.
Was it official update to NC2 by OTA/Odin or you just flashed a ROM?
Sent from my SGH-M919 using Tapatalk
serio22 said:
Was it official update to NC2 by OTA/Odin or you just flashed a ROM?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
NC2 was OTA. After doing some searches it said that OTA could of been corrupt, so I went and downloaded KIES and did a reinstall that way.
When I upgraded to 4.3 I tried that default baseband out and had the same problems. That is when I was searching on google and came across this forum and also the thread about flashing modems.
What APN (Access Point Name) are you on ? Also what is your Preferred Network Type set to ? Its located in Settings > More I think.(I don't use Stock Firmware)
Perseus71 said:
What APN (Access Point Name) are you on ? Also what is your Preferred Network Type set to ? Its located in Settings > More I think.(I don't use Stock Firmware)
Click to expand...
Click to collapse
APN is epc.tmobile.com
Network Mode current set to GSM (the only way I can make calls out without the problem occuring)
WCDMA/GSM (Auto Connect) is what it should be on so my data is at 4G, but the calls is the problem here
I am not sure but can you check the settings of the Dialer to see if there is ways to choose Lookup providers ?
Perseus71 said:
I am not sure but can you check the settings of the Dialer to see if there is ways to choose Lookup providers ?
Click to expand...
Click to collapse
Nope don't see anything in the dialer about selecting a provider..
Its supposed to be something about Choose Lookup Providers. At least that's the way it is on AOSP.
I suggest Odin flashing the stock NC2 firmware and then factory resetting from stock recovery. (Backup first of course!) If it is still an issue, it will most likely be a hardware problem. From what you have said so far, I believe that you will find this to be the case. Could've been due to damage from a drop, or even overheating at some point. Or it could just be that its simply due to hardware degradation over time.