Database Info

Think My Baseband is DONE FOR!!!

Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.

can you install a stock rom back onto it? There is a baseband selection mode that you may have to do.
http://forum.xda-developers.com/showthread.php?t=1116884
1. Go to Dialer. Dial *#*#4636#*#*
2. Go to Phone information. Choose the preferred network to
"GSM Auto PRL" or "CDMA Auto PRL" or whatever you have.
3. Scroll down, deactivate and activate Phone Radio.
4. Press Menu button.
5. Select Phone frequency, then choose your country.
6. In the previous menu push the Home button to go back to Homescreen.
7. Reboot.
(By Brainmaster)
Ive had to run this a few times depending on radio and rom.
after many trials I am sticking with rooted stock.

Wow that is defiantly a menu I have never seen before.
It doesn't let me select any of the preferred carrier option. When I tap on GSM auto (PRL) it just closes and defaults back Unknown.

It's ded?
Sent from my HTC Phone

thepyro6 said:
It's ded?
Sent from my HTC Phone
Click to expand...
Click to collapse
Ya, I think it is. RIP Nexus S. HTC Sensation here I come.

after you select gsm auto you hit the menu button on your phone then select the carrier. I know its not labeled what it is on the walkthrough but its similar. not phone frequency but like signal or something. then yuo jsut select usa.
reboot and it should find whatever your service is on its own.
have you tried going back to stock rom? I used this version to go back when i thought i bricked out my phone and its been great. I think my friend used it too but he wont admit he used somethign i gave him.
http://forum.xda-developers.com/showthread.php?t=1060192

http://forum.xda-developers.com/showthread.php?t=1038007
Same issue also involved the trinity kernel. Dev may need to be notified.

kmmxracer said:
Hello All,
I am a avid XDA reader and follower. I don't post allot, but do allot of reading and tooling around. That being said I have read and tried many different option for my issue.
Device: I9020T on T-Mobile US
Issue: "Baseband Unknown" / No Cell Service
-Under Settings/About Phone. My Baseband version = Unknown
-My signal bars are greyed out with a small "X"
-Everything else works, wifi, camera, ect...
When in FASBOOT the following is listed:
-Product Name: Harring
-HW Version: REV 11
-Bootloader Version: I9020XXKA3
-Baseband Version: I9020XXKD1
-Carrier Info: EUR
-Serial Number: This matches the on on my box
The issue started after I installed one of the latest KANG builds of CM7 nightly builds. I also had flashed [KERNEL] [gpl] NS/NS4G Trinity (E)UV and OC 2.6.35.13/.14 BFS .404, CM7 + m(any) roms.
This combo had been working good for at least 8-10 hours until I was listening to music through PowerAMP, when all of the sudden the music sounded like a CD skipping. The screen was unresponsive and no buttons or combo of buttons did any thing. I hesitated but eventually had to pull the battery.
When I powered the phone back up it hung at the trinity boot logo and just froze. After several reboots with the same results, I resorted to flashing a different ROM through Recovery. That's when I noticed the issue at hand.
As I was typing this I noticed it was strange that fast boot listed my carrier info as EUR??? Is this maybe because I'm currently running [ROM] Gingerbread Peter Alfonso (GPA17)? I flashed the ROM listed for my phone.
Anyways here is what I have tried:
-Flashing a NANDROID of stock 2.3.2 through Recovery
-ADB/Fastboot flashing the various radios for my model
-Flashing radios through Recovery
-Flashing ROMS meant for my phone with radios in them
-Even found everything I needed and used ODIN to get back to factory fresh!!!
So sorry for the long post but I am out of ideas and am thinking it my actually be a hardware issue.
Thought I'd throw this out to you all and see if there are any ideas I may have not tried.
Thanks in advance for any ideas or advice.
Click to expand...
Click to collapse
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.

simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
No im absolutely sure i flashed the right ROM. Peter Alfanzo was a ROM i flashed after this issue happened. It was the CM7 nightly + Trinity kernel that did me in...
Sent from my Nexus S using XDA Premium App

simms22 said:
did you happen to flash the ns4G version of [ROM] Gingerbread Peter Alfonso (GPA17)? that would make sense then why you dont have any signal, considering your on tmobile and the ns4g is sprint.
Click to expand...
Click to collapse
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??

Canehdianman said:
Sorry to hijack the thread, but I have the same problem as the OP and I think this is exactly what I did wrong.
I wasn't paying attention when I updated Cyanogenmod and I chose the Nexus s 4G instead of regular Nexus s.
Ever since then my baseband has been "unknown" (except in fastboot, where is shows as KB3 (which I updated to as one of my attempts to fix it).
I have gone back to stock, no change. I have updated the radio, no change.
I have no idea what else to do. Does anyone have any ideas??
Click to expand...
Click to collapse
have you tried reformatting all your phones partitions?

simms22 said:
have you tried reformatting all your phones partitions?
Click to expand...
Click to collapse
I've wiped user data/factory reset a few times now. Is there a higher-level format option that I should be using?
I thought for sure that going back to stock (based on these instructions - theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/) would work, but no such luck.
I find it perplexing that the baseband shows in fastboot, but nowhere else. *#*#4636#*#* shows radio off and network type unknown, settings/about phone/ shows baseband version unknown.
I tried different methods that I've found online over the weekend, but nothing has brought my radio back.
I am certainly open to suggestions!

I'm going to provide as much additional information as possible.
I have a Nexus S I9020A, running on Fido (Canada).
My initial problem stems from when I updated to cyanogenmod 7.1 from 7.0. My first (and likely biggest) mistake was not making a backup. Oops.
I think I accidentally chose "Nexus S 4G" instead of "Nexus S". As soon as I did that, I stopped getting any cellular voice or data connection (wifi continues to work fine). Under Phone Information, it said it was a Nexus S 4G.
The phone locks itself into airplane mode now. When I try to turn airplane mode off through the settings menu, it hangs. When I hold down power and choose "turn airplane mode off" it seems to work, but then I still get no signal.
I have pushed it back down to stock. It now remembers that it is a Nexus S (not 4G), but it didn't help the baseband problem.
I have tried to reflash the baseband. no effect.
I called Fido and got them to "repush" the SIM card. No effect.
I am humbly appreciative of any and all help that anyone can provide!

EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies

YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Thanks! This is similar to some other threads I saw on the android forum (and elsewhere on XDA).
I'll try this when I get home (and get to a reliable wifi signal).

Wow! I haven't looked at my post in a wile. Hopefully you all are getting some resolution to these issues. I ended up calling Samsung and they agreed to fix my Nexus under warranty. They replaced some parts that I can't remember off the top of my head, but it should arive at my door tomorrow!!!
Sent from my HTC Sensation 4G using xda premium

YourMainDude said:
EDIT: Nvm! Lol just saw your post above mine lol just was to lazy to read lol
Not sure if you already did this but if u have root explorer or if u don't go to 4shared.com and type in root explorer v 2.16
Back up efs file first
Open root explorer and find the efs file. Press and hold/ Move :
"nv.log"
"nv_data.bin" and
"nv._data.bin.md5"
Into Root Of SD card... reboot phone and u should have ur 3G back
Sent From In between Your Moms Boobies
Click to expand...
Click to collapse
Hmmm bad news... my efs folder appears to be empty. Now what?

A very frustrating day... Thought i would have it fixed pretty quick, alas....
My efs folder is empty. I guess that explains the lack of radio, but it appears that i might need to send the phone to Samsung to get the efs reflashed. Is there a way to write it back myself? Ill look tomorrow i guess.
Here is some more info:
I just tried to update to 2.3.6
Clockwork mod is giving me an error message:
Assert failed: getprop("ro.product.device") == "crespo" || get prop("rp.build.product") == "crespo"
E:error in [filename]
(Status 7)
Installation aborted
Not sure if that helps but it's another piece of thepuzzle hopefully.

*sigh*
So it appears that I need a backup of my /efs folder in order to fix this myself (which I do not have).
I know what my IMEI should be, however I have no idea if it is even possible to take someone else's backup and alter it the proper IMEI.
I fear my next option will be to submit it for repair at a Samsung repair shop (and be without a phone even longer )

[Q] No cellular wireless signal after Cyanogenmod 9 - ICS on i897

Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes

I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app

You need to flash to stock and back.
Sent from my SGH-I777 using xda premium

How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium

KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?

up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?

rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.

Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.

jellybean is out!

Here's the odin tar for the new jellybean release
http://hotfile.com/dl/204016374/8aa...m-SGH-T699-TMB-T699UVBMC5-1363439562.zip.html
I should have a tethering fix and a flashable modem (for people on cyanogenmod) out by tomorrow

nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?

Braccoz said:
nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?
Click to expand...
Click to collapse
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.

Jax184 said:
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.
Click to expand...
Click to collapse
awesome, i'll wait for the tethering fix then

I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?

I've been using the new JB ROM for a few hours now and have found a quirk or two.
When manually adjusting the brightness, sometimes the screen takes on a blue tint. Like, things that should be a dark blue become much brighter. This goes away if I tweak the brightness back and forth a few times.
I rooted the ROM using the CWM+flashable root file from previous ROMs. It worked, though last night I kept getting "radio is requesting superuser access" until I restarted the phone. I don't know what that was about. Hopefully it doesn't happen again.
The compass is STILL misconfigured. Every time you boot the phone, it needs to be recalibrated before it has any idea which way is up or north.
burbs said:
I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?
Click to expand...
Click to collapse
No idea what you mean. Got a picture?
---------- Post added at 12:48 PM ---------- Previous post was at 12:12 PM ----------
Okay, so we may have something a little deeper here. Today I'm seeing the "radio is requesting Superuser permissions" dialog again and again. I'm unsure what this means, but as a wild-ass guess, it may be the ROM checking to see if the phone has been rooted. This could be bad for people out there who still have their warranties.

I can't seem to get a screen shot, but it's like what you'd expect the hard drive LED to do when accessing data. I've looked up different "solutions" through Google, and it seems to be a developer's mode attribute, but I turned it off. One person says to uncheck the strict mode setting, which hasn't worked.

Well, whatever it was, it's done doing its thing now. As the day went on, the red flashing border appeared with less frequency. Throughout this morning I didn't experience it at all. Maybe it was some type of optimization thing going on?

Tethering
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.

conspirator.of.crisis said:
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
Click to expand...
Click to collapse
I'm waiting on tethering as well.

Jax184 said:
I'm waiting on tethering as well.
Click to expand...
Click to collapse
Thanks - I just wanted to make sure I wasn't missing something - guess that means I'm going back down to LJ1 until we get tethering!
---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------
Now I'm in trouble - I got distracted while trying to go back to LJ1 and ended up applying the LJ1 tethering fix to the JB ROM. Phone rebooted and got stuck on the screen with SAMSUNG with the pulsating blue background and just wouldn't go further. Got back in through ODIN and flashed back down to the LJ1 ROM but again when the phone reboots it is still stuck on the same screen. Did I just brick it? Anyone got any suggestions as to how I can get back up and running on *ANY* ROM?

Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
The only reason to downgrade though for me is that I need to tether. Hence faced with this problem I started going through all the Wifi Tether apps (that I tried before the tethering patch was out for the previous versions and none worked) and discovered the FoxFi works. It seems to override the T-Mobile tethering restriction in that when it is active the normal Mobile Hotspot icon appears (as well as the FoxFi icon) in the notification bar and when you pull it up it shows as On with the devices connected listed. Using FoxFi isn't as elegant as just using the built-in software hence I'll hobble along with the new image and FoxFi but still hopes that someone is kind enough and smart enough to figure out a tethering fix for this image.
Anyone got any comments or suggestions?

Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors

gee one said:
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors
Click to expand...
Click to collapse
Wouldn't this help?
http://forum.xda-developers.com/showthread.php?p=40591848#post40591848

That is the full rom, I was looking for the actual OTA update because I wanted to look at the updater-script.
Here it is:
http://rapidshare.com/files/1683651545/update_mc5_7bda365f.zip
7bda365f9db8d24235b22787ed0c560c update_mc5_7bda365f.zip

Does GPS work on the new stock rom for you guys?

conspirator.of.crisis said:
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
Click to expand...
Click to collapse
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.

I'm having some gps issues and radio is requesting superuser access. This is on rooted,debloated jb with the jb radio.
Let me know if you need logs, data, or want me to flash something.
sent while running with scissors

JB downgrade to ICS + GPS
Thanks for the info Nardholio! I guess that means I'm staying at JB then. Overall I'm happy with it and having no problems perse. However to address your specific comment about GPS, although I haven't had any issues with it I have noticed that it has taken up to 5 minutes to fully sync and get a position lock now. I hadn't attributed that to the upgrade necessarily though as this happens from time to time as being way up here in Calgary Alberta sometimes satellites aren't as easily visible as they could be and this happens occassionally with all of my GPS receivers. My old G2 used to have quite a lot of problems that way. Haven't noticed anything about root requests though as Gee One indicated.

Nardholio said:
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
Click to expand...
Click to collapse
does making a cwm backup cover that, and all other stuff needed too?

[Q] Flashing to stock - phone force closes process com.android.phone, help

Please bare with me since this is the first time having to post for an issue since I usually find an answer on your forums
So here's the situation.
I bought the photon q 4g lte from ebay and it came with the unlocked bootloader.
Needless to say it was with the stock ics and i tried to find a jellybean update because it wasn't taking the ota and ended up going with cyanogen since i had no problems before. However those phones i had before were with sim cards not cdma.
I found out i couldn't update prl or profile manually without having to do something on the pc.
So after searching left and right i found i could use rsl lite (I used 6.1.5) and eventually found the "stock" file from this post
http://forum.xda-developers.com/showthread.php?t=2095536&highlight=rsd+lite
I did the stock jellybean, got it to go through the process and it booted up with no errors.
However, when it boots into the os it pops up a force close on omadmclient_sprint_dataservice and eventually also on the process com.android.phone.
I tried putting it in airplane mode to see if the service error would go away but it didn't work for the process part crashing.
I tried re-flashing, deleting cache in recovery, doing a data/factory reset in recovery and the one time i was able to do a data factory reset within the settings menu.
I could not find anyone that said they had a rom that worked with sprint and updating prl within the rom, if anyone knows of one let me know and i will flash it through rsd.
Otherwise does anyone have an idea of what could be happening because googling the omadmclient part did not pull up anything specific and pulling up the process issue for other phones has not helped me either.

Was this a hacked GSM phone, or are you using it as CDMA?
I've never heard of people having FC issues after flashing a FXZ from RSD. Which one did you flash? Android 4.1.2 - Sprint US - 9.8.2Q-122_XT897_FFW-5 (No simlock) ?
If you are on stock, you should be able to update the PRL within the ROM.

I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings

crispy6 said:
I was trying to use it with cdma network through sprint. and yeah that was the file i downloaded, had to remove the getvar to get it working but flashed with no errors after doing that.
As for updating the prl i can barely navigate through the phone, there is no home page loading and the process pop comes up often enough that its hard to go through the settings
Click to expand...
Click to collapse
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.

arrrghhh said:
Sounds like something went wrong mate. Are you already activated on Sprint? I don't know if that would matter, it might.
I would honestly redownload and redo the RSD process.
Click to expand...
Click to collapse
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.

crispy6 said:
I originally tried to activate the phone through cyanogen and then when the rep said he couldnt do it because of the lack of prl to update within the rom we just setup the activation back on the old phone/ That phone is working on the network.
I re-downloaded the file just in case and re-flashed but same problem. The only thing i thought of was maybe updating the radio but since its a stock rom it should work out of the gate. whats also weird is i tried turning wifi on but it didnt work either.
Anychange you know of a rom that works with sprint. I dont care if its stock since i would probably root later again.
Click to expand...
Click to collapse
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.

arrrghhh said:
Which one are you flashing?
Try another perhaps...? I honestly have never heard of this. It sounds like the phone might be damaged, or the RSD process just did not flash correctly.
I guess I should ask, was the phone modified at all for the GSM SIM slot mod? I wonder if having a non-Sprint SIM in is messing with it... That is just a shot in the dark.
Click to expand...
Click to collapse
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.

crispy6 said:
so far the only rom i tried was 10.1 cyanogen and the stock rom for jellybean. However for the stock rom it doesnt let me downgrade to ics with rsd 6.1.5 do you think if i downloaded an old version i could downgrade to a lower stock rom?
Also I honestly had not looked for the cdma roms since most of what i saw was troubleshooting related for this phone but i just saw this rom -AOKP 4.2.2 (Android Open Kang Project) (CDMA&GSM) that you created - http://forum.xda-developers.com/showthread.php?t=2293892
I re-rooted and installed that one and it looks great, just wondered how you got sprint to activate the phone or if you had done it before changing the rom? Also how would the prl and profile be updated.
Lastly the wifi wasn't turning on this time either, it did work initially when i got the phone so that has me stumped.
Click to expand...
Click to collapse
To downgrade to ICS, you need to remove some additional lines. See this post for more information on that.
However, you should be able to update the PRL on either stock ROM.
I think I said this before, but I will say it again. You need to do PRL updates, activate the phone, and get EVERYTHING working on stock BEFORE you flash ANY custom ROM. This is just standard practice - you don't want to put the cart before the horse! Get the phone working, then play with custom ROM's.

Issues with Mobile Data Rapidly turning on/off after using hotspot

Hi all -
I recently updated to the 4.4.3 VzW firmware and upgraded from Viper 1.8.0 to Viper 2.5.0. Since upgrading, I have been having troubles with my hotspot. After being on and other devices have been using it for a bit, my M8 begins to rapidly turn on/off the Data Connection. This doesn't stop and the only way to fix the problem is go into airplane mode and back out again. I figured that I may have had a bad flash, so i tried reflashing clean downloads of both the firmware and a full wipe and reinstall of ViperOne, but still seeing the exact same issue. I seem to be also experiencing a problem where my phone is reporting a 4G connection, but data is disconnected and i cannot get anything over the data channel. Voice works fine. Again, to fix it's a cycle through airplane mode.
I tried applying the changes recommended by for the 4G handoff fix, even though the problem described does not seem to be exactly the same as mine. It did not seem to help, and mae it even harder to get a reliable 4G connection.
http://forum.xda-developers.com/verizon-htc-one-m8/general/verizon-4g-handoff-fix-t2868778
Has anyone else seen anything like this and have any recommendations for a fix?

Just realized this would be better in the troubleshooting forum. Is there a way for me to move it there or does that require a moderator?

Check http://forum.xda-developers.com/verizon-htc-one-m8/help/loss-lte-data-using-ap-t2900047

I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.

kc6wke said:
I have had the same thing, going back to 1.55.605.2 FW does seem to be the fix, I think its something with 4.4.3 FW.
One of the so called improvements is Mobile hotspot connectivity, but maybe that's only with phones that don't use the patched default.xml,
the ones that really pay for the mobile hotspot.
Click to expand...
Click to collapse
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?

Also - are you still running Viper 2.x or did you roll back to a prior ROM as well?

After some more searching, i found this link for stock 4.4.2 on VzW, but was wondering if anyone has the firmware only, so don't have to restore recovery, and rom afterwards.
http://forum.xda-developers.com/showthread.php?t=2727831
I certainly can and will do it, if necessary, just would prefer to have the firmware only, if someone has it available. Anyone?
Thanks in advance for the help!
Dave

deh2k7 said:
Thanks for the reply - do you have a link for the old firmware, so i can flash and revert back to that?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?w=files&flid=13966
Dl the one without boot img

Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.

deh2k7 said:
Thanks, downloaded and reverted. Long boot times, but things working. Now to give the hotspot a few tests. I'll update with my results.
Click to expand...
Click to collapse
initial tests are very promising. hotspot seems to be stable and hasn't dumped the data connection yet. Looks like good old VzW managed to screw up the firmware update as usual. Would be nice if they didn't always to be different. Thank god for these forums and the hardworking devs here!

I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?

deh2k7 said:
I spoke too soon. Still seeing the same issue after reverting the FW back to 1.55.605.2. Anyone seeing this? Any thoughts on if reverting back to Viper 1.8 would help?
Click to expand...
Click to collapse
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.

jsaxon2 said:
I don't think it is the firmware that is the issue, I think it is the kernel. You should be good going back to Viper 1.8 as it uses an older kernel. I would think you would also be fine using the newer firmware and an older ROM version.
Click to expand...
Click to collapse
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.

deh2k7 said:
I'm starting to believe this as well, that there's something flaky in the 2.x Viper ROMS for VzW and hotspots, and likely in the kernel. I've already reverted back to the old firmware, and I'm going to go back to a clean 1.7.x full install, then OTA to 1.8. Will update with the results.
Click to expand...
Click to collapse
Any luck fixing this issue?