Well, since people like reading about about people who have screwed something up, figured I'd throw that up in the subject line. Lol. Now it's time to give you a rundown of what's going on and ask the community for help. I'm not quite sure who's going to be a bit more helpful, since this is a Verizon phone on a non Verizon network, but I am dealing with different device (I605/I950) kernals and well...just read. Lol. This will be cross posted at TeamUSCC, so thanks in advance for any help.
So I have an old SCH-I605....obviously, that's why I'm here. I am currently on a no contract plan with USCC and have been able to flash SCH-I950 roms (had to remove the asserts in the zip, status 7 error) and they had always worked just fine. Occasionally I would find a rom that would cause a bootloop, so I would just skip it and try the next one. I was also able to flash I605 roms and use them on USCC network with no issues, except not having MMS or Data. Using I605 roms, I would put in the APN's, sometimes they would auto populate from the SIM card, but MMS/Data still wouldn't work...so hence the reason I used I950 roms. That's not the issue. The issue comes, when after a solid 3 weeks of having a stable rom I was happy with, I started noticing some FC's and no videos would work in some apps. Not a huge deal, but at times could be quite inconvenient. Especially having kids watching to watch things in the car...damn you Minecraft videos on Youtube. So I booted up to recovery (TWRP at the time), wiped dalvik/cache/system/data (everything I've ever done for 2+ years on multiple devices), flashed BeanStalk 4.4 AOSP and once it got booted up, I noticed that it was not recognizing my sim card. 10 minutes after staying on the "activating" screen, I decided this wasn't normal. So I figured another bad rom. Didn't have any USCC roms at the time, so I grabbed an I605 rom, while I downloaded some I950 roms, and had the normal "this sim card doesn't work with this network", so I pulled the SIM card and rebooted. I got to thinking about it, and realized that I shouldn't be seeing that screen, since I've used I605 roms before with this SIM, but just assumed it was due to the first boot and the activation process. So I went through the setup via wifi, powered down, replaced SIM card, and booted back up thinking "sweet, I can text/call, and use WiFi for anything else..." ya...that didn't go as planned...this is when the "issue" started. Tried calling the wife to see how her DR trip went (acute tendinitis) and no mobile networks were available...found that strange, so I went to settings/about phone/status and holy hell, I was scared for a while. Nothing was in Network was Unknown, Signal Strength was some crazy 9 digit number in the dBm, asu was stuck at 99, Mobile Network Type was unknown, as well as service state, roaming and mobile network state. My phone number was unknown, as well as my MEID and IMEI. So after doing some research, it appeared my EFS got screwed...so I was freaking out...so I flashed some I950 kernals...I flashed some I605 kernals...I changed my recovery (now I'm on Philz) and nothing seemed to work. That was before I learned that I that I had phucked my EFS though. So after I found out about the EFS, I held my breath as I flashed a stock (VRALJB) back to my phone via ODIN. Booted up the phone, and right off the bat, it recognized my SIM, and gave me an error in regards to that...had to power down, pull SIM, boot back up, and it went smoothly. Looked back in the settings/about/status, and finally, IMEI was back as well as everything else. So I re-rooted the phone, Casual method, and installed Beanstalk (since it has worked before with no issues) and everything went smoothly...till I tried to use the phone again. So now I'm sitting in the Status screen, Network shows US Cellular, signal is normal for where I'm at, Mobile Network Type is CDMA - 1xRTT (over my head, but I assume normal?) Service State is In Service, but Mobile Network State just keeps saying Connecting, won't ever hold the connection. But I also notice that down below my Phone Number says 000-000-8946 as well as my MIN, where usually that says my phone number...my REAL number. lol MEID and IMEI is all there and working fine, so I'm more inclined to believe now it's my SIM card that got phunked. So...what's the best be (aside from getting a newer phone) to get this phone working again...
As my phone sits:
Model Number = SCH-R950
Android Version = 4.4.4
Baseband Version = I605VRALJB
Kernal Version = 3.0.64-CM-g36cf250
[email protected] #2
Fri Jun 26 10:07:15 CDT 2014
AOSB KitKat Version = 1.3.5
CyanogenMod Version = 11-20140627-Unofficial-R950
Build Number = cm_950-userdebug 4.4.4 KTU84P 431a3b977a test-keys
Didn't know what you might have needed, so I posted it all in hopes it will help determine what can be done to resolve this. A HUGE thank you to anybody in advance for their help!
Related
Hi everyone,
I just purchased a Rezound on Neo's Tachyon from Swappa and I'm having trouble activating it on Verizon - it just won't recognize what phone number it's supposed to have, and therefore can't make non-roaming calls. Tried sim swapping and MEID entry on MyVerizon, clean reflash of Tach and other roms, minor APN fiddling, and brought it to a VZW store where they worked it for almost two hours to no avail.
Initially, setting roaming mode to "home only" gave me roaming, while "automatic" somehow gave me 3G/LTE. Now "home" gives me nothing and "auto" just gets me roaming, not sure why.
Other info:
-Was most recently on Straight Talk
-S-Off
-Unlocked bootloader (although it still says Locked when I boot into it)
-Modded hboot ver. 2.27.0000
-Radio ver. 2.22.10.0801r/2.22.10.0803r
-AmonRa recovery (that can't view internal sd for some reason)
-Currently running Infection
Any ideas on what the problem is?
Stormwing said:
Hi everyone,
I just purchased a Rezound on Neo's Tachyon from Swappa and I'm having trouble activating it on Verizon - it just won't recognize what phone number it's supposed to have, and therefore can't make non-roaming calls. Tried sim swapping and MEID entry on MyVerizon, clean reflash of Tach and other roms, minor APN fiddling, and brought it to a VZW store where they worked it for almost two hours to no avail.
Initially, setting roaming mode to "home only" gave me roaming, while "automatic" somehow gave me 3G/LTE. Now "home" gives me nothing and "auto" just gets me roaming, not sure why.
Other info:
-Was most recently on Straight Talk
-S-Off
-Unlocked bootloader (although it still says Locked when I boot into it)
-Modded hboot ver. 2.27.0000
-Radio ver. 2.22.10.0801r/2.22.10.0803r
-AmonRa recovery (that can't view internal sd for some reason)
-Currently running Infection
Any ideas on what the problem is?
Click to expand...
Click to collapse
Since you are S-OFF, I would go through the whole "Downgrade and factory restore" procedure here: http://forum.xda-developers.com/showthread.php?t=2509770, it should take care of all your issues... If it was on ST before, it could be in any state depending on how it was done, if you go through the above procedure, it will take a couple hours but you will be at a known, good point to flash TWRP/CWM and the ROM of your choice, after knowing it works!
I am having this issue with my i605. I would up bouncing my sim between another phone and this one and when I cam back to the Note, I can't make/recieve calls. I have data and able to receive texts, but no calls. Not sure where something went arry, but I have tried everything. I odin'd back to stock and still no calls. Rooted the new image, still nothing. Tried all the fixes I could find. Flashed different modems, dialed *#*#4636#*#* and changd to 800mhz, changed apn's, changed type of signal and still nothing. I know the sim is fine cause it works in my Moto X 2014 and my wifes S5. The sim out of the S5 would not allow calls either, so it is phone based.
Details of phone:
SCH-i605
mfr date: 11-06-12
Bootloader: i605VRALJB
Baseband: i605VRUFND7
Rom: CM_i605-wilson3q 5.0.2 (currently)
My sd card took a dump before all this went down, could not save all my backups I had on the card. Only one on computer was right after I rooted, 3-2013. It is a TWRP backup, I did try to restore to it, but stuck at Samsung logo for a no boot. I tried to restore just parts of it (EFS, modem) and still no go.
What else should I try?
Hi Everyone,
I recently rooted and installed CM13 (20160606) nightly on my i9300. At first everything worked flawlessly, but last Thursday (16th June) I lost signal and have not been able to get it back since. In case the circumstances for when it happened could have an influence, then here is a bit more details from around the time I lost signal.
I was having signal and the mobile data was working fine, as I was running low on battery the phone was on battery saver, when the battery hit 2% it had signal and I didn't look at my phone after this. As I came home, I immediately plugged in my charger and at the same moment my phone shutdown due to no more juice on the battery. When I started up the phone again, it had no signal.
I've tried to clean flash the same nightly again, clean flash newest nightly (20160618). I've also tried to flash other modems without any luck. APN settings have been double and triple checked, deleted, setup and triple checked again. I've tried to downgrade my TWRP to 2.8.6.1 from (3.0.2-1) and flashed the nightly - No luck.
Here are my system details:
CM version: 13.0-20160618-NIGHTLY-i9300
Baseband version: I9300XXEMG4
IMEI: 35299...........
IMEI SV: 01
Sim Network: Unknown
Signal strength: 0
Cellular network type: UMTS
Service state: Data: Out of service
Cellular network state: Disconnected
I think this could be related to the incidence when I lost signal, after battery power out, as this was working fine up to then for 10 days.
Let me know if I need to provide any more information or if you have any ideas what I can try to restore my signal.
When I go to search for Network Operators it finds two, when I try to register to the one which is not mine it says my Sim card doesn't allow this. When I try to register to my actual carrier it takes a long time and it comes out saying "Can't connect to this network right now". My signal strength in the about section is "0". I'm not sure where the problem is, if I have 0 signal, how can I find two carriers?
I got back to Android 4.3 by sammobile ROM, after flashing patched XXUGMK6 kernel and modem, I now have a signal. But, I'm still unable to connect to my carrier. My IMEI and S/N match those under the battery. After searching my carrier shows up in the mobile network list, but it fails to register to the network, and goes to have No Service and says the selected network is unavailable.
Solved. I went through basically everything I could dig on the internet, not sure exactly what did the trick.
ahvdk said:
Solved. I went through basically everything I could dig on the internet, not sure exactly what did the trick.
Click to expand...
Click to collapse
can i ask what did you do? :< im on cm13 also, did you flash new update of cm13? or clean install again?
Hello! I have an ATT version.
I was having trouble updating to android pie because I'm out of the states so I was using Firmware.science; at one point I decided to jump and flash the BJ5 with odin, the flashing was taking forever, at one point it seemed like it was stucked so I decided to only flash the AP file, I worked, then afterwards I decided to flash the BL, CP and CSC Files. I flashed all 4 files for the android pie build.
My problem is that ever since I updated to pie, I never have full bars of signal, the last one is never filled. I tried with another sim card from another carrier and the problem remains. I updated from the first build to the february build to the march build today and the problem persists. I can take calls, make calls, my mobile internet, I'm not so sure, It's been a little slow. I don't know if this is a bug? I'm thinking about downgrading to oreo, I'm not sure if this is possible, is anyone else having the same issue?
Edit: I tried wiping cache, (with every update the phone factory resets so there's no point for a factory reset), taking my sim card in and out but the issue persists. I don't know what to do.
Pigoath said:
Hello! I have an ATT version.
I was having trouble updating to android pie because I'm out of the states so I was using Firmware.science; at one point I decided to jump and flash the BJ5 with odin, the flashing was taking forever, at one point it seemed like it was stucked so I decided to only flash the AP file, I worked, then afterwards I decided to flash the BL, CP and CSC Files. I flashed all 4 files for the android pie build.
My problem is that ever since I updated to pie, I never have full bars of signal, the last one is never filled. I tried with another sim card from another carrier and the problem remains. I updated from the first build to the february build to the march build today and the problem persists. I can take calls, make calls, my mobile internet, I'm not so sure, It's been a little slow. I don't know if this is a bug? I'm thinking about downgrading to oreo, I'm not sure if this is possible, is anyone else having the same issue?
Edit: I tried wiping cache, (with every update the phone factory resets so there's no point for a factory reset), taking my sim card in and out but the issue persists. I don't know what to do.
Click to expand...
Click to collapse
I would just flash the home tar in AP. Uncheck Auto reboot. after the flash is complete ,use button combo to access recovery. Then it will update your firmware for you
I'll give it a try but this reception issue is getting annoying.
If you get almost full bars (all but the very last one at the top end) that is still pretty good. If your having issues you can try factory data resetting the phone or else call AT&T and see if there is an issue in the area.
Truth be told the bars are just a convenient visual aid. If anything you should look at the signal strength.
Under settings > about phone > sim card status is an entry called signal strength. If I recall correctly somewhere around 105 to 115 dBm is pretty good. Mine is at that range (108 to 110 dBm) with tmobile and I have almost full bars (very top one is not lit).
Also if your baseband version contains the number 4 (start at the end as first character and count 5 characters to the left) then you will not be able to downgrade to oreo. The 5th character from the end (counting inwards) is the bootloader version. You can only flash firmware with the same bootloader version or higher. Attempts to flash a bootloader version lower then what is on your phone now will always fail.
scottusa2008 said:
If you get almost full bars (all but the very last one at the top end) that is still pretty good. If your having issues you can try factory data resetting the phone or else call AT&T and see if there is an issue in the area.
Truth be told the bars are just a convenient visual aid. If anything you should look at the signal strength.
Under settings > about phone > sim card status is an entry called signal strength. If I recall correctly somewhere around 105 to 115 dBm is pretty good. Mine is at that range (108 to 110 dBm) with tmobile and I have almost full bars (very top one is not lit).
Also if your baseband version contains the number 4 (start at the end as first character and count 5 characters to the left) then you will not be able to downgrade to oreo. The 5th character from the end (counting inwards) is the bootloader version. You can only flash firmware with the same bootloader version or higher. Attempts to flash a bootloader version lower then what is on your phone now will always fail.
Click to expand...
Click to collapse
Well, I'm screwed then because I do have the number 4 and the last number is a 7. I'm on the march update, I might take it to Samsung so that they can check it out. I'll try to reflash with Odin.
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
bornxawkward said:
Hi all,
Alright so this is going to be a long post. So I recently flashed my phone to the U1 firmware, I currently have an unrooted Verizon Unlocked Samsung S9+. I wanted to switch phone carriers over to Visible (subsidiary of Verizon), here are the order of events that occurred:
1. Visible's website says that my device in not compatible using their IMEI checker, there is a solution that was found on reddit about flashing the device on the U1 firmware.
2. I flashed the device on the U1 firmware using Odin and the Visible SIM card worked as expected. No issues with the flash
3. Data/Texts etc.. are all working as expected. Except for Voicemail.
When I try to check my Voicemail, it is acting as if it's still on the Verizon Voicemail system. It says "Welcome to the message management system, please enter your mailbox number". No one can leave me a VM either because of this. I tried several different combinations of numbers, including my full 10 digit cell number and last 4, to which it says "XXX is not a valid mailbox number", which would be because my number is no longer active on Verizon, so it's unable to access it. Which makes sense. The Visible Customer Care team tried the following:
1. Provisioning my VM multiple times
2. Take out SIM card, turn phone off for 1 min, insert SIM card again, and toggle airplane mode for 30 seconds
3. Reset network settings
After numerous days of troubleshooting with them, eventually they said it was because my device isn't compatible, ok, I can't argue with that. I have not seen anyone else experiencing this issue that had flashed their phone to U1 firmware.
After trying all of this with them, I eventually factory reset my device, hoping that might do something. That still did not work.
My questions is, is there something I missed with flashing the U1 firmware? Why is it still using Verizon's VM system even though I flashed it to U1? Is there any way to fix this? Any help is greatly appreciated, and please don't hesitate if you need any other information.
Click to expand...
Click to collapse
Please check your voice mail settings in your phone app. See my screenshots.
There you should select the correct service provider and the Visible mailbox number.