Hey guys,
This thread stems from this post: http://forum.xda-developers.com/showpost.php?p=39594591&postcount=18
I'm gonna spare you the trouble of having to read that thread by summing it up for you:
- T-889V, running Jedi x12, had to pop out the sim to try it on another phone.
- Once popped back in, my phone lost all carrier connectivity. At first the signal icon looked like a "forbidden" sign. Then, after a little while, I get service bars, but no connectivity indicator.
- IMEI used to show up, but I still didn't get connected. Used my sim in a different phone as well as a different sim in my phone to rule those 2 out. As expected a different sim in mine didn't work.
- I go back to stock using mobile odin. My IMEI is now unknown, obviously I can't connect to anything and on top of that the phone reboots every 1 minute or so.
- I flashed some other rom I had lying around. My IMEI is back, bootlooping stopped, however I was still unable to get any service.
- Try a different version of stock with mobile odin the and I'm boot looping. This time I can't get into recovery at all.
- Finally I try desktop odin with a couple of different stock images, and I'm still bootlooping (reboots right after the Samsung logo). Recovery works fine.
I would send it back but I'm worried about my flash counter being 1, and my system status being "custom". I am completely stumped. Absolutely any ideas are appreciated.
Sometimes after flashing stock you have to wipe data factory reset to get it to boot. Just a thought.
Thanks for the idea. I have tried that
Have you tried flashing back whatever modem came with that Jedi ROM, along with either the stock T889V or an N7105 ROM?
Still getting bootloops?
In other words, get to a no service and no bootloop situation, and look into restoring NV items with the appropriate Qualcomm compatible programs.
Sent from my SGH-T889V using xda app-developers app
But do you think it's possible to escape the constant bootloop? Right now I'm a little worried about flashing anything that will increase the counter, as I don't know if I'll get to run triangleaway ever again...
By qualcomm compatible programs you mean those 2 little tools that let you extract/write an IMEI as well as generate it as a text file?
The solution should be the same as the one I used for fixing my phone: using NV reader writer to rewrite correct stock settings along with your IMEI.
Warranty centres don't care about your exact counter, only if it's 0 or not, so flash away until you fix this. My counter was well over 30 when I finally did.
Sent from my SGH-T889V using xda app-developers app
Related
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
Sprint Galaxy Nexus
4.2.1
Not rooted
I performed a factory reset on my phone yesterday due to it bogging down and being rather slow. I never did a reset after getting the 4.2.1 update so I figured it was a good time. I woke up this morning, putzed around the house, and setup Tasker again. I laid my phone down for ten minutes while I got ready for work. Whenever I tried to wake my phone and nothing happened. I tried a few more times and the screen would not wake up. I pulled the battery, hard reset, reinserted battery and the phone wouldn't turn on. Then, I wiped the contact terminals (on the battery and the phone) and reinserted the battery and the phone booted up. However, since then I have had some major problems.
1. Power button does not always work properly. I have to press it several times to sleep or wake the phone. (Okay, not major, just inconvenient and probably unrelated to the issues below)
2. No data connection whatsoever.
3. In the data usage menu, there is no longer a data toggle switch.
4. Under the Network Mode option, LTE/CDMA produces absolutely no cell signal whatsoever. I have to switch to CDMA only. (WiFi works fine)
5. Toggling airplane mode, as some have suggested, does not cause the phone to connect to mobile data. Another factory reset did not restore mobile data. Rebooting did not restore mobile data.
6. All of these problems are true before and after factory reset. No new problems were created and nothing was exacerbated as a result of performing a factory reset.
I've been from one end of the internet to another looking for solutions to this problem and I have found that many are having a similar issue but toggling airplane mode or rebooting fixes it. Not the case for me. Most also seem to be having this problem after rooting. Again, not the case for me.
Any suggestions? I would prefer to not return the phone. Purchased from Radioshack and the 30-day warranty has expired. This is my second gnex already, as the first one's charging port broke. It took over a week to get this one from another store which graciously shipped it in to my store. There's also the issue of being broke and not really being able to afford another $30 activation fee on top of the deductible for a new phone.
Why not try reflashing the stock image and updating again to 4.2.1?
Beauenheim said:
Why not try reflashing the stock image and updating again to 4.2.1?
Click to expand...
Click to collapse
Wouldn't I have to root first?
nburns1825 said:
Wouldn't I have to root first?
Click to expand...
Click to collapse
Not at all. You'd use Odin . Myself I have very spotty sprint signal in my home. Spoke to a corporate executive and they mailed me an AirRave free . Never have less then full bars 3g all around home. You should a- flash to stock using Odin following posts in sprint sextjon . b - call up and try to get an airavana.
Sent from my Galaxy Nexus using Tapatalk 2
n0ve said:
Not at all. You'd use Odin . Myself I have very spotty sprint signal in my home. Spoke to a corporate executive and they mailed me an AirRave free . Never have less then full bars 3g all around home. You should a- flash to stock using Odin following posts in sprint sextjon . b - call up and try to get an airavana.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Excellent. I will give it a shot at some point today or tomorrow and then let you know how it worked out. Thanks!
So, I restored the phone to stock. Signal is still non-existent on LTE/CDMA mode. Cannot perform Profile or PRL updates. Still no mobile data. I'm guessing hardware failure?
Also, on setup it asks for a SIM card. And at the bottom of the drop-down menu, it says "No SIM card|Sprint" or "No SIM card|No Service" depending on if I am in CDMA or LTE/CDMA.
Also, in the Status menu:
My phone number
Unknown
MIN
Unknown
PRL Version
Unknown
ICCID
Unknown
Seems a little odd to me.
Attempted fully rooting and flashing radios. No luck there either. It's also not wanting to update. Tells me my phone is up-to-date (connected via WiFi). Downloading Cyanogen now to see if it will work in the morning.
And while attempting to flash a new ROM, got the famous "can't copy anything to the device ever, under any circumstances" error.
Update: Got CM10 installed. Still "No SIM" error, no 3G, no data, no LTE. Found some more information on this No SIM error. Apparently a few others have had this same problem and in the end had to get a new phone.
Anyone know anything?
You should a- flash to stock using Odin following posts in sprint sextjon
I've been back to stock twice now. The first thing I did was flash to stock. Then I played around a bit and now I'm back to stock again.
Is there a difference between using Odin and Nexus Root Toolkit to return to stock?
Bump
Wow, one day and my thread is buried!
After battling for about a day, I got updated to JB 4.2.1, I can do profile and PRL updates again, but there is still no 3G/mobile data, and I still have zero bars on LTE/CDMA and have to use just CDMA. I am currently stock but the bootloader is unlocked, no root.
If anyone has heard any solution, please help. Also, if there's a difference between flashing to stock with Odin vs NRT, please say so.
nburns1825 said:
Wow, one day and my thread is buried!
After battling for about a day, I got updated to JB 4.2.1, I can do profile and PRL updates again, but there is still no 3G/mobile data, and I still have zero bars on LTE/CDMA and have to use just CDMA. I am currently stock but the bootloader is unlocked, no root.
If anyone has heard any solution, please help. Also, if there's a difference between flashing to stock with Odin vs NRT, please say so.
Click to expand...
Click to collapse
Try fastboot flashing your LTE and CDMA radios again. As far as I know, fastboot commands do NOT require root. I had a similar issue.
Edit: link to post with directions http://forum.xda-developers.com/showthread.php?p=39446679
Sent from my R2-D2 unit on the far side of the moon
Indeed, fastboot does not require root. I've flashed my radios several times now in various different ways. I even flashed different versions. I attempted again but with no luck. I have normal service when using CDMA but nothing on LTE/CDMA. Still no data, still "No SIM card" error.
Pretty sure I'll have to get it replaced. I've gone from stock JB back to stock ICS, rooted, CM10, back to stock ICS, rooted, back to stock JB unrooted, and flashed three different radios. I'm surprised I haven't managed to brick it yet.
UPDATE: Sprint is sending me a new phone, for free.
Hello,
I'm having a lot of difficulty getting my Note II (SGH T889V) in working order . I'll try to explain the situation in an organized way. Thank you for your time and kind help!
Background
I have a Note 2 from Wind Mobile in Canada - SGH T889V. I got it 2.5 months ago. It was rooted, was running TWRP and I only loaded one ROM, flashed once, on it - 4.1.2 modified touchwiz ROM. Never once had an issue. The ROM was super stable and in great working order.
I got it unlocked about 2 weeks ago because I was visiting the states. When I got to the states, I put in a T-Mobile sim card which was working great for a few days. One afternoon during my vacation I was having slow data issues, so I thought to change the modem/radio from a Wind Mobile radio to a T-Mobile radio. That gave me 4G data speeds but killed my calls. So I tried to go back to the Wind Radio and that had my phone complaining that there was no SIM card. I went back to the T-Mobile radio and I got calling back but only 2G data.
My IMEI was corrupted - it showed up as zero. I left the T-Mobile radio on the phone when I got back. My home network wouldn't recognize me and thought I was still roaming.
Attempted Fixes
Tried a basic factory reset. Tried a different ROM. Tried wiping all internal data.
I got home and tried to flash to stock ROMs found on XDA for Wind Mobile phones. That didn't solve the issue. The IMEI remained null. The phone would reboot automatically every few minutes unless I turned Airplane Mode on. I figure the phone was looking for a signal and couldn't because of the IMEI problem.
So I looked around on the net and found a link about injecting the IMEI back using QPST (http://forum.xda-developers.com/showthread.php?t=1206275) but I couldn't get the program to detect my phone so I gave up and thought I could just get my binary count to 0 and stock and I'll just take it back for warranty.
I tried Triangle Away but I couldn't get the counter to go to 0 even with stock ROM and recovery. So I thought I would take it to a cell repair shop locally. I took it there and all they did was cause an issue on the phone to make it appear that KIES firmware upgrade failed so that it would be repaired under warranty. You would see a emergency firmware upgrade error the minute you turned the phone on. However, download mode still showed the custom binary count at 1, they didn't get it down to 0.
I spoke with my carrier and with Samsung anonymously, they said the counter would be an issue if I sent it in.
I came back home and tried doing the following, with the hopes of trying Triangle Away again:
1. Installed TWRP via ODIN and ran the restore on the backup I created in TWRP when I first got the phone. I restored everything including EFS. Phone boots to the stock samsung rom but it would restart automatically every few minutes. Even with Airplane mode on, it would still reboot on it's own.
The KIES error message doesn't appear anymore.
2. Went back to ODIN. It was getting stuck on SYSTEM in ODIN version 3.07 when flashing a stock rom. So I switched the USB port on my computer and used ODIN 3.04 then the flashes went through properly with no hang ups.
So I tried to flash a prerooted (http://forum.xda-developers.com/showthread.php?t=1975560&highlight=wind) stock ROM
and
also a basic stock ROM (http://forum.xda-developers.com/showthread.php?t=2061031), along with a stock recovery
Both just get stuck in a bootloop. I tried going to the stock recovery and wiping data, cache, factory reset several times. No luck - still boot loops. Wont go into the ROM.
I did not try "Re-partition" in ODIN. I'm not sure if that'll hard brick the device but maybe that way I can repair all of the partitions? - http://forum.xda-developers.com/showthread.php?t=860432&page=2
__________
Im hoping to get back into a prerooted ROM or stock ROM to try this Triangle Away Method - http://forum.xda-developers.com/showthread.php?t=2272966 to get the custom binary down to zero.
I tried to use the Triangle Away ODIN method but it doesnt go through in ODIN, it just gets stuck.
If I can get into the ROM without it boot looping or rebooting automatically- I think I can fix my IMEI like this person did - http://forum.xda-developers.com/showthread.php?t=2145967
Outcomes Im hoping for
To stop the bootlooping/ automatic reboots, then
1. To get the custom Binary count to 0 so I can send it back in for warranty to Samsung or my carrier, Wind Mobile. The binary says Samsung Official. - http://forum.xda-developers.com/showthread.php?t=2068156
or
2. To get the phone to working order so I can try this persons method - http://forum.xda-developers.com/showthread.php?t=2145967
The phone is still responding and it's still working with ODIN. It makes me think the issue is software or partition related and not hardware related per se. If it is hardware, I just want to get this phone back to Samsung but I need to unroot/clear the binary counter.
The phone has never been dropped or damaged physically. I've really babied the phone. This is my third Samsung Galaxy phone (I've had a Vibrant and S2x before this one.)
This has really ruined my week. I need my phone for work. I greatly appreciate any kind help or guidance. I know the collective genius here at XDA will be able to find a solution.
Thank you so much!
If you have flashed the tmobile modem you will now have to keep the tmobile one in order to get your phone to boot. Flashing a t889v modem will cause loops. Dont know of any way to get back to t889v modems.
Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3
Byangmang said:
Hey, don't worry, you aren't the first to experience this problem. Many users have reported that the T889V will bootloop with the T889V modem after flashing another modem. Many have also restored IMEI and service to their phones, so there is a solution. I don't have the specifics, but there are many threads about this problem with solutions. I have quickly searched for one and I believe it has everything you need to fix it.
http://forum.xda-developers.com/showthread.php?t=2119074&page=3
Click to expand...
Click to collapse
Thank you. I'm going to give that a shot. I'll install CWM then install a T889 TMobile Radio to see if it boots.
I'll report back. Fingers crossed.
I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843
sniperess said:
I had same issue... this is how I fixed it
http://forum.xda-developers.com/showthread.php?t=2274843
Click to expand...
Click to collapse
Thank you all!
I got the boot loops to stop by flashing CWM recovery, then flashing a TMobile Radio.
From there, I followed the QPST instructions of installing a QCN file on the phone to reenable the AWS spectrum. Then I used the IMEI creator and NV Writer programs and I was back.
Data seems alright, getting alright speeds on Wind right now. I just found my bluetooth a little hard to hear in the car this morning.
So with this process, I should stick with a Tmobile radio from now on right? If I flash a Wind/ T889V modem it'll boot loop?
Have you guys noticed any signal or performance issues after restoring the phone this way? I'm wondering if it's worth the trouble to get the custom binary counter to clear and return this phone for warranty. Seems to be working for the most part so far.
Thank you so much again! I thought I was going to have to pay $100 to get it JTAGed.
Glad to here your back and running.
I have a t889v using it on telus, and since I am stuck on tmobile modem I get lower phone signal but never loose signal. On a plus I now get lte speeds.
First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.
lilroach said:
First day back it seems good for the most part.
Only issue I had was Bluetooth in my car would cut out at a high rate of speed (when I was on the highway). It worked really well while I was on local roads but once I hit the highway I couldn't hear the other side at all pretty much. I had to put them on speaker to hear them. They could hear me really well, better than before when I was driving on local roads.
Never occurred in the past. Could it be a radio issue? Signal seemed okay and I was able to continue the conversation over the phone speaker on the highway.
Click to expand...
Click to collapse
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.
lilroach said:
The bluetooth issue doesn't seem to be a problem anymore. Disappeared on it's own.
Click to expand...
Click to collapse
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?
how to fix your T889v if you accidentally overwrite the radio
If you get stuck with no IMEI, in my case, flashed omnirom 4.4.1 t0ltetmo, which uses Tmobile radio... it killed the Wind Mobile radio... restoring form nandroid did not help.
solution:
flash omnirom t0lte (not t0ltetmo) and your problems are gone!
lilroach said:
I noticed I have serious data issues when the network goes into HSPA+ mode. I get really good data for a minute then it'll cut out totally for like an hour. I tried rebooting, tried battery pulling. It seems the T-Mobile radio doesn't interface well with Wind's HSPA+ . I had full bars but the internet wouldn't load. It was pretty non-functional for most of the day.
It works decently when it's not on HSPA+
Tried switching to a Wind modem, went into boot loops. Went back to T-Mobile radio. Should I try a different T-Mobile radio?
Click to expand...
Click to collapse
So I have been waiting patiently for the 4.3 update to roll out to me OTA with hopes that it would fix my issues but my phone has been saying download interrupted and so I have gone back to completely stock and triangle away to get my device status back to normal but it still wont let me download. When looking around for other possible causes I saw that my build number is JRO03L.I747UCDLK3 which comes up as a build number for a nexus 7, the correct build number for my att should be JRO03C. I have no idea how it got that way but I am wondering if the person who bricked it might have put the wrong version of the bootloader or some other part of the firmware on and it somehow didn't brick but is detecting a conflict and not letting me OTA. Or that is what is causing my cell network issues as well. Wanting input from a a few devs as I am not 100% sure what the first part of the build number represents.
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for tag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Bump
Bump!...not looking good.
madnesshero86 said:
Ok guys and girl, I am having a really weird issue with my Att Gs3 that I wanted to see if anyone could help with. To start off a little bit of background. I Hard bricked my s3 in August, sent it for Jtag and got it back working and stock with no issues. All I did was root the phone for fear of messing it up again but it was running all stock without problems for over a month since the unbrick. About 3 weeks ago I went out of town within the state but a ways away, I was talking on the phone with a co-worker right before leaving town. At some point that evening I get a a text from my wife asking why I was ignoring her calls, I had never received them and according to my phone was in the middle of prime 4g lte zone in San Antonio but I was apparently only receiving that lte signal and the phone was not switching to the voice network on 4g to make or receive calls, I was even able to voice chat with my wife but I couldn't just call her normally. After returning home I was still unable to make or receive calls unless it was right after a restart and I had to try about 15 times, so I called att and tried all of their bs which didn't make a difference at all. Looking around on the internet I found the number that you can put in to get into service mode and switched it to gsm or wcdma only and voila I could make calls again. The only problem with that being that I travel within a city for work and move from 4g to 3g to edge all the time but if I have it set for wcdma only then I have no signal and have to take the time to pull up service mode to switch back and forth. So I tried going back to completely stock again by resetting/ formatting all and flashing the stock rom via odin, my issue persisted so I also decided to flash synergy rom (which I was running prior to the hard brick) and then intergalactic because I saw the fewest problems with it to no avail. I have flashed each stock modem new and old which made no difference at all. Today I was messing around in service mode and found an area that was called handover, in that subsection you have the option for checking the phones ability to switch from gsm to wcdma and back as well as to hspa, when I select any of those options I get the message "temporary block due to build e" or " temporary block code".
I was wondering if anyone has any ideas about what the possible problem could be, imei, modem hardware, or a stubborn stuck modem firmware setting.
I was also wondering if anyone had any experience with figuring out how to re-enable handover because that is where I feel my problem is, either through adb or any programs that let me force change the settings, I would also be happy if someone knew how to turn of only LTE and have both gsm and wcdma on at the same time.
Any help would be much appreciated, I have tried everything I know how to do, but am to the point where I am forced to look at new hardware because my wife is pregnant and I really needs to be able to get a hold of me any time.
Click to expand...
Click to collapse
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Tried
View attachment 2362929
winosxbuntu said:
if you have CM recovery or TWRP you can go back, wipe everything even twice could help, then flash a stock rom reboot and see what happens
if that doesnt work go back to odin and install stock firmware 4.1.2 from Samsung but again you have to wipe data/factory reset
3rd if that doesnt work, try to restore your EFS folder/files using this link http://forum.xda-developers.com/showthread.php?t=1725839
that link has everything, how to fix it, anything you need to know
BUY a new phone or use a different phone if all the options above fail
Click to expand...
Click to collapse
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
madnesshero86 said:
View attachment 2362929
The backup restore/fix imei and data restore tools link doesn't go anywhere, does anyone have a link to the restore tool? The only version I can find is for the non us version of the s3.
I did at least use the tool for the 9300 to find out that I have some 000 for s/n and other numbers (see attachment)
is there a patch out for us gs3's to fix this like there is for the i9300?
Click to expand...
Click to collapse
I think I can help, I just need to pull up some files and I might get you the software or program I used to back -up and restore my EFS folder/files
Even fix it, so plz hang in there........will report back later on
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
madnesshero86 said:
Thanks a bunch, I am still trying all kinds of stuff but I feel pretty certain that the problem lies with a messed up efs and I don't think I have a backup unless doing a nandroid covers that as well, which I am not seeing that it does. Any further help is appreciated, is this something that a local cell repair shop can typically fix or is this a possible new phone situation?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
this is the software/programme i used to back-up, recover or even fix my EFS files (if they are corrupt and can be used) NV items reader writer
type it on google and pretty sure you will find something , try different links and again am sure you will find a download
have you tried flashing the new 4.3 stock firmware and modem follow this link for everything http://forum.xda-developers.com/showthread.php?t=2498233 or you can wait for AT&T to release the official 4.3 firmware and that will be 100% satified to be stable and will fix all your EFS/IMEI problems FOR GOOD :laugh:
i have the NV items reader writer software that can fix your problems but i dont know how i can share it with you without breaking any rules
ULTIMATE/final solution send it to MOBILETECHVIDEOS and will fix it like its nothing, take it to samsung and have to play some ball, or BUY A NEW PHONE
tried kernels (idont think it will make any difference) but its good to check
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
madnesshero86 said:
I have tried all the other versions but will try the 4.3 what's the name of that software so I can try and find it or of you have drop box you could pm me the info and get it to me that way . In the meantime I found an fusion 2 for 38 bucks from att so I can get calls for the time being.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
NV items reader writer
type exactly as it is on google or here on XDA
New Info
See new info in OP Please, and before anyone says anything I have spent half the day searching with various keywords trying to find a fix so be kind if it seems obvious to you, I couldn't find it and I did try.
Bump
So about 6 months ago, I decided to finally try out some custom roms on my t999 after running stock for over a year. I tried a couple of roms and stuck with cm11. Every thing was great until about 3 weeks ago. Out of nowhere, my phone randomly decides to drop connection to tmo towers. Sometimes i have bars and 4g symbol and sometimes i don't have anything. When I pull the battery and restart, I am able to connect to data, make calls, and send messages for a few minutes, but then i lose everything. Randomly throughout the day, I will get signal back for a few minutes but thats it. I flashed a touchwiz rom for now so I can use wifi calling, So that still works.
So I tried to flash a different baseband modem from DocHoliday77 and none of them worked. I also tried going back to stock following DocHoliday77s guide once again, but for some reason that does not work. I launch odin3.07, put my stock firmware in the pda section, make sure only auto reboot and F reset time are checked. I connect my phone in download mode, it is detected and i start the process. The phone restarts but gets stuck at the samsung logo screen. I have tried flashing different roms and none work.
I dont think its an imei problem because I got the phone direct form tmo with a contract.
Does anyone know what I might be doing wrong? ANY help would be greatly appreciated.
Did you factory reset after you flashed the firmware in Odin? That's the only way it will boot coming from cm.. You may just need a new sim if flashing to stock won't fix it.. And BTW T-Mobile doesn't do contracts