Related
ok so i have the HTC Droid Eris and it is rooted, i put this http://forum.xda-developers.com/showthread.php?t=944430 on my phone via flash zip. i upated my connection stuff via *228 and yet the connection is not picking up from local towers. the only question is how do i access my SID number? ive tried multiple program numbers like ##778 and ##7764726 but nothing seems to work so i can change my SID number to what it should be and i know its wrong. Please help
Is your phone prepaid?
Sent from my ERIS GSBv2.0 using XDA App
No its not prepaid
Ronoriot said:
ok so i have the HTC Droid Eris and it is rooted, i put this http://forum.xda-developers.com/showthread.php?t=944430 on my phone via flash zip. i upated my connection stuff via *228 and yet the connection is not picking up from local towers. the only question is how do i access my SID number? ive tried multiple program numbers like ##778 and ##7764726 but nothing seems to work so i can change my SID number to what it should be and i know its wrong. Please help
Click to expand...
Click to collapse
Are you unable to make or receive calls? What ROM were you running before flashing GSB? Did you do a full data wipe before flashing GSB?
Ronoriot said:
ok so i have the HTC Droid Eris and it is rooted, i put this http://forum.xda-developers.com/showthread.php?t=944430 on my phone via flash zip. i upated my connection stuff via *228 and yet the connection is not picking up from local towers. the only question is how do i access my SID number? ive tried multiple program numbers like ##778 and ##7764726 but nothing seems to work so i can change my SID number to what it should be and i know its wrong. Please help
Click to expand...
Click to collapse
FYI if this helps, or even if it doesn't, you can see the MEID number underneath the battery. I find that you usually have to use the HEX version on Verizon's website. I don't know if this will help you, however, because flashing ROMs does not affect activation status.
Is this the number you're looking for?
synesthete said:
Are you unable to make or receive calls? What ROM were you running before flashing GSB? Did you do a full data wipe before flashing GSB?
Click to expand...
Click to collapse
i was running the factory default phone, i wiped everything and flashed the rom i linked on it, i can receive calls, voicmails, texts, mms, the internet is fine, but its not connecting to the towers near me, its picking up off different towers and the person at verizon said i need to change the SID number to 30730 which i know what one to change and i know where it is, i just cant access that part of the phone to change it because i dont know what program number to use.
flash the official RUU and start fresh possibly can fix the problem and re-root then flash new rom
roirraW "edor" ehT said:
FYI if this helps, or even if it doesn't, you can see the MEID number underneath the battery. I find that you usually have to use the HEX version on Verizon's website. I don't know if this will help you, however, because flashing ROMs does not affect activation status.
Is this the number you're looking for?
Click to expand...
Click to collapse
everything is active, thats not the issue and no i did not need the MEID number i can find that in the info on my phone, but thanks for the reply
dragon1018 said:
flash the official RUU and start fresh possibly can fix the problem and re-root then flash new rom
Click to expand...
Click to collapse
ive dont this twice, once last night and once today, still cannot access programming menu
Ronoriot said:
i was running the factory default phone, i wiped everything and flashed the rom i linked on it, i can receive calls, voicmails, texts, mms, the internet is fine, but its not connecting to the towers near me, its picking up off different towers and the person at verizon said i need to change the SID number to 30730 which i know what one to change and i know where it is, i just cant access that part of the phone to change it because i dont know what program number to use.
Click to expand...
Click to collapse
To my knowledge, the ROMs do not alter any activation state of the phone* - that stuff is held in a hidden partition (the "mfg" partition, I suspect) in the flash memory chip that are never touched by any of the usual ROM flashing operations. That's why you can change ROMs and maintain the same activation and PRL data from ROM to ROM. So, I don't know why your phone's tower association would have changed if was working correctly before flashing a developer ROM.
*The only exception to this is if you perform a factory reset with the stock recovery on the phone - that does clear the activation state of the phone. The "factory reset/wipe data" menu entry of the custom recovery doesn't touch activation data or PRLs, though.
If that's what happened, then you might have to temporarily revert to a stock ROM - just don't use the factory reset procedure on the stock ROM before you re-root the phone. (BTW, you could certainly use the March 2011 OTA stock ROM - installing it won't overwrite your custom recovery, so you can simply do a nandroid backup/restore to get back to your current setup - no need to "re-root" if you do that.)
There's probably something I don't understand about the situation you are describing, unless it has something to do with towers that were acquired from a different carrier (Alltel?) by Verizon - under normal circumstances, your phone would prefer to connect to the best signal within it's home network, assuming that there are not other problems that prevent that from happening (such as call congestion through a certain tower). Perhaps the towers you want to connect to are actually considered to be "roaming" by the PRL you have on your phone, and that's why the more distant VZW towers are chosen?
bftb0
bftb0 said:
To my knowledge, the ROMs do not alter any activation state of the phone* - that stuff is held in a hidden partition (the "mfg" partition, I suspect) in the flash memory chip that are never touched by any of the usual ROM flashing operations. That's why you can change ROMs and maintain the same activation and PRL data from ROM to ROM. So, I don't know why your phone's tower association would have changed if was working correctly before flashing a developer ROM.
*The only exception to this is if you perform a factory reset with the stock recovery on the phone - that does clear the activation state of the phone. The "factory reset/wipe data" menu entry of the custom recovery doesn't touch activation data or PRLs, though.
If that's what happened, then you might have to temporarily revert to a stock ROM - just don't use the factory reset procedure on the stock ROM before you re-root the phone. (BTW, you could certainly use the March 2011 OTA stock ROM - installing it won't overwrite your custom recovery, so you can simply do a nandroid backup/restore to get back to your current setup - no need to "re-root" if you do that.)
There's probably something I don't understand about the situation you are describing, unless it has something to do with towers that were acquired from a different carrier (Alltel?) by Verizon - under normal circumstances, your phone would prefer to connect to the best signal within it's home network, assuming that there are not other problems that prevent that from happening (such as call congestion through a certain tower). Perhaps the towers you want to connect to are actually considered to be "roaming" by the PRL you have on your phone, and that's why the more distant VZW towers are chosen?
bftb0
Click to expand...
Click to collapse
i will try this but before i do i'll try to explain a bit more, when i call the normal eris programming number, it tries to actually make a call instead of giving me the option to go into edit mode, now when im on the stock rom i can do it but as soon as i flash any other rom on it, it doesnt allow me to do so. i had a rom from a droid 2 on it and when i used the droid 2 programming number it worked just fine and i could edit the info. hope this helps clarify a bit, and thanks for the help
bftb0 said:
To my knowledge, the ROMs do not alter any activation state of the phone* - that stuff is held in a hidden partition (the "mfg" partition, I suspect) in the flash memory chip that are never touched by any of the usual ROM flashing operations. That's why you can change ROMs and maintain the same activation and PRL data from ROM to ROM. So, I don't know why your phone's tower association would have changed if was working correctly before flashing a developer ROM.
*The only exception to this is if you perform a factory reset with the stock recovery on the phone - that does clear the activation state of the phone. The "factory reset/wipe data" menu entry of the custom recovery doesn't touch activation data or PRLs, though.
If that's what happened, then you might have to temporarily revert to a stock ROM - just don't use the factory reset procedure on the stock ROM before you re-root the phone. (BTW, you could certainly use the March 2011 OTA stock ROM - installing it won't overwrite your custom recovery, so you can simply do a nandroid backup/restore to get back to your current setup - no need to "re-root" if you do that.)
There's probably something I don't understand about the situation you are describing, unless it has something to do with towers that were acquired from a different carrier (Alltel?) by Verizon - under normal circumstances, your phone would prefer to connect to the best signal within it's home network, assuming that there are not other problems that prevent that from happening (such as call congestion through a certain tower). Perhaps the towers you want to connect to are actually considered to be "roaming" by the PRL you have on your phone, and that's why the more distant VZW towers are chosen?
bftb0
Click to expand...
Click to collapse
i did what you suggested, put the stock rom on my phone, then used my back to my custom rom and it changed all my connection settings in my ESPT menu, which i cant access for some reason
Ronoriot said:
i did what you suggested, put the stock rom on my phone, then used my back to my custom rom and it changed all my connection settings in my ESPT menu, which i cant access for some reason
Click to expand...
Click to collapse
^This sentence confuses the crap out of me. I read it 5 or 6 times, and have no idea what sequence of operations you performed. I only have a vague idea that you can't get something to work.
If you can't access the EPST menu, how can you see what the settings are?
Here is what everybody has said so far (basically the same thing, but in different ways) :
- The EPST menus are generally not available in custom ROMs, especially any of the AOSP (Froyo/Gingerbread) ROMs. You need a stock, or near-stock ROM to be guaranteed that they will be available
- The same thing is true of "secret dial code menus". They don't exist in custom ROMs, unless those custom ROMs are nearly identical to stock ROMs (that is, directly derived from a stock ROM).
If you want to try it, you can flash either a RUU or PB00IMG.zip file - these operations flash a "nvram" file (*.nb0), which conceivably resets PRL and other non-ROM settings. After doing that, and fooling with EPST using a stock ROM, you will need to re-root.
As I mentioned, you should not run a "factory reset" procedure on your phone after you have configured what you want (with EPST) when there is a STOCK recovery on the phone.
Beyond that, I'm sort of mystified why you are unsatisfied with a phone that appears to be working normally. (What application are you using to determine cell phone tower? Are you inferring that from location services (Google Maps) with GPS and WiFi location services turned off?)
bftb0
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
Hi guys,
I managed to accidentally grab the ATT version of LiquidSmooth and flash it. Since then, I've had strange issues with service. Here's what I've tried:
Flashing (Verizon) versions of CM, LiquidSmooth, and Hyperdrive
Flashing the original and ME7 modems with Heimdall and Odin
Wiping data, system, caches, and fixing permissions before/after every flash
Randomly toggling Mobile Network settings (but I have no idea what I'm doing there)
[*[Searching everywhere I could think of on the forums
I had 0 service on either AOSP ROM I tried. Right now, I'm running Hyperdrive and getting weird results.
Sometimes it asks be to switch to "Global Mode" and shows that I'm roaming.
If I try to call, it says it can't find a mobile network and fails.
After leaving it sitting for a while (right after a clean flash), all the texts I missed came through.
If I try to text somebody, I'm warned that the mobile network is unavailable, but the text still goes through!
4G is working on Hyperdrive. Wifi still works on everything.
com.android.phone crashes when I try change the Network mode away from Global
I'd love to hear any suggestions you guys might have for me. Not sure what I have left to try.... is there a master reset for all of this?
Thanks!
EDIT
Some more details:
About Phone > Status in CM after fresh flash:
Network: Verizon
Signal Strength: 2147483647 (2^31 - 1) dBm, 255 (2 ^ 8 - 1) asu .......WHAT
Mobile network type: CDMA - 1xRTT:7
Service state: In service
Roaming: roaming
Mobile network: Disconnected
My phone number: something completely wrong
MEID, IMEI, ICCID are all there, but don't know how to tell if they're also whacked out
The APNs list is blank and my signal jumps between zero bars and a few bars + roaming. Call and text not working.
I've also attached my PIT file (grabbed with Heimdall). Have no idea how to read it.
Do you have a nandroid backup that includes your EFS partition? If so, I would try restoring it and seeing what happens. Sounds like something got out of whack in there and is giving your phone a hard time doing it's #1 job.
This is what ultimately switched me to the S4, my GNex randomly decided one day that it wasn't going to be a phone anymore, and I didn't have an EFS backup to restore in order to try and fix it.
Two things -
1. Always, always, always, make sure the ROM you are flashing is the correct ROM.
2. Always keep an ODIN file on handy of the full system image, here is the full MDK software, this WILL wipe all of your data - http://www.sxtpdevelopers.com/showthread.php?t=237
Sent from my Nexus 7 using xda premium
woierfere must
grussinko said:
Do you have a nandroid backup that includes your EFS partition? If so, I would try restoring it and seeing what happens. Sounds like something got out of whack in there and is giving your phone a hard time doing it's #1 job.
This is what ultimately switched me to the S4, my GNex randomly decided one day that it wasn't going to be a phone anymore, and I didn't have an EFS backup to restore in order to try and fix it.
Click to expand...
Click to collapse
I don't have a backup. That will definitely be the first thing I do when I get this working again.
gaontr the
Rebel908 said:
Two things -
1. Always, always, always, make sure the ROM you are flashing is the correct ROM.
2. Always keep an ODIN file on handy of the full system image, here is the full MDK software, this WILL wipe all of your data.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
1. I know. LiquidSmooth could have done a better job of linking to the right place on their post, but it was still really dumb on my part.
2. Thanks for this! It looks like I'll be able to try this out tonight (slow connection). The SD card data is safe right? Also, I'm just downloading the tar - not sure what the exe is for.
I haven't used Odin for this since it was on version 1.8 or something (now it's over 3)... it looks like I still just choose the tar from the PDA block and hit go... no specific other settings needed for this phone / flash, right?
No luck :/ . I unzipped the stock restore, flashed in Odin (PDA), and booted fine. I have 4G and texts working, but no calling (mobile network not available) and calling my phone goes straight to voicemail. Also, it's very adamant about keeping me in Global mode over LTE/CDMA. This is the same state I was in earlier while running Hyperdrive, except now I don't have root.
I feel like I've tried everything there is to try. Does anyone have any further suggestions?
Are there any areas of software that don't get reset when flashing the stock images in Odin, and that could have been corrupted from the bad flash?
Thanks.
It's probably also worth mentioning that I'm warned about there being no mobile network when I send texts. I can cancel the dialog and they still go through. People can text me without issues.
espacex said:
No luck :/ . I unzipped the stock restore, flashed in Odin (PDA), and booted fine. I have 4G and texts working, but no calling (mobile network not available) and calling my phone goes straight to voicemail. Also, it's very adamant about keeping me in Global mode over LTE/CDMA. This is the same state I was in earlier while running Hyperdrive, except now I don't have root.
I feel like I've tried everything there is to try. Does anyone have any further suggestions?
Are there any areas of software that don't get reset when flashing the stock images in Odin, and that could have been corrupted from the bad flash?
Thanks.
Click to expand...
Click to collapse
I had the same happen to me when I was working on getting radio on MIUI ROM, after tinkering with the Sprint version, only 4G would work, and occasionally roaming would work. Every time I tried to make a call, it told me there was no mobile network available, and it constantly tried to switch into Global Mode instead of CDMA/LTE.
Sadly, the only thing that worked for me was getting my phone replaced with a brand new one. If you find anything that works please be sure that you post it, because someone else may end up doing the same thing.
Jonestown said:
I had the same happen to me when I was working on getting radio on MIUI ROM, after tinkering with the Sprint version, only 4G would work, and occasionally roaming would work. Every time I tried to make a call, it told me there was no mobile network available, and it constantly tried to switch into Global Mode instead of CDMA/LTE.
Sadly, the only thing that worked for me was getting my phone replaced with a brand new one. If you find anything that works please be sure that you post it, because someone else may end up doing the same thing.
Click to expand...
Click to collapse
Did you get it replaced via warranty? If so, did you need to do anything besides flashing a stock image in Odin beforehand?
Maybe try flashing the stock rooted ME7 that includes the new radios? Couldn't hurt at this point.
Edit: whoops, saw you already tried that
Sent from my SCH-I545 using xda app-developers app
Does anybody know whether ODIN / recovery deletes the partitions before writing new ones? If a file existed in the ATT rom, but not in the Verizon one, would it still be on my phone if I flashed the Verizon rom over the ATT one? Obviously this assumes a data / cache wipe in between. I'm really talking more about the other partitions.
Also, does anyone have any experience trying to get a replacement via warrantee after flashing? I've read all about the binary counter on our model, but didn't see any success / failure stories yet from people returning phones after flashing stock + unrooting.
Last question for now: is there any reason to believe that taking the recent update would help my situation? Maybe that could reset whatever is causing my calling issue.... just a random guess. I know that I'd lose any chance of getting root back (at least for a while).
Thanks again for the help guys!
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Verilin said:
Would like some help. I have flashed CM 11 and can't make calls. It says mobile network not available. Tried flashing AOKP rom as well and same thing. Mobile data works fine, although i have gotten a popup twice that says 'Google Play Services not supported by your device, please contact your manufacturer' (no noticible issues from this, google stuff i've tried so far works). I have included a screenshot so you can see my baseband and rom version, etc.
Now, i had a great deal of trouble getting a rom flashed to start with, CWM put me into a bootloop and TWRP wouldn't flash anything because it said it couldn't mount /storage when i tried. Used Philz advanced CWM (love it btw, will be using it from now on). Still wouldnt flash the hltespr specific CM11 version so had to use the unified hlte version (it gave me the status 7 asserts issue, but editing the asserts out just gave me a bad file error when flashing). I wiped data/cache/dalvik between each flashing. I don't know if any of that would have bearing on this problem, just including any details i can. Any advice?
Click to expand...
Click to collapse
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
topherk said:
Have you upgraded your bootloader to NH7? I know most of the newly-updated CM-based ROMs require you to be on NH7 before flashing. That's most-likely why you weren't able to flash the htlespr ROMs. The unified ROMs no longer include the correct APNs for Sprint, so that's why you don't get service on it. I don't know why mobile data works on it.
Click to expand...
Click to collapse
No, didnt realize that i needed to do that. I'll do some research on it because i don't have any idea how to update the bootloader. If you have a link to a good tutorial that would be wonderful! Thanks!
Ok so i tried that, found this tutorial, followed it, no luck. Tried full wipe/reset after that to see if it would let me install the hltespr versions, still no dice. Same situation, mobile data works, calls don't. Will have to wait till daylight to try texting so i don't wake anyone up but i suspect that texting won't work either. Has anyone experienced this and fixed it? Lol i really didn't drop $100 on a phone to be saddled with all the Samsung and Sprint baloney that it comes with, don't wanna unroot....
Bump
Anyone have ideas on this? Have continued to try fooling around with the udater-script file to resolve the status 7 problem so I can install the hltespr variant, still no dice. Please someone help!
Bump!
Sorry, I typically don't have access to XDA forums on the weekend, so couldn't answer your question till now.
You flashed only the baseband/modem, not the Bootloader. If you want to update the Bootloader, you need to use ODIN to flash the Complete OTA NH7 Update.
In order to update the Bootloader, you need to make sure that you use the PC ODIN (not the mobile one) and that you completely power off the phone before you enter download mode (don't access download mode by using the extended power menu when shutting down the phone). I don't think you need to do the battery pull that Freeza had in his instructions (I didn't do it when I ODIN-flashed the NH7 OTA update), but it wouldn't hurt to do it.
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Verilin said:
Thanks for that, I will try it as soon as I get home tonight! The next thing I had decided to try was to unroot, to back to stock, then try flashing that before I start with the custom recovery and ROM. Do you think I should do that first before doing the whole thing or could that work just flashing that with my phone as-is?
Click to expand...
Click to collapse
Well, I always recommend a full wipe (data, system, cache, dalvik) when flashing ROMs. I haven't wiped my internal storage or external storage since I got the phone, so that's not really necessary.
I don't think that unrooting your current ROM is necessary. Flashing the ODIN OTA update will automatically remove root access, so that's not an issue. Here's the steps I took when I updated to NH7 and installed my current ROM (see my sig):
Make a Nandroid backup.
I always do this just so I have a "record" of what I left behind. It also allows me to have all of my app data that I can restore via Titanium Backup (you have to buy the Pro version in order to restore specific apps from a Nandroid backup). I always store a copy on my ext. storage and on dropbox.
Do a full wipe
As I mentioned above, I always wipe data, system, and the caches when flashing ROMs. While I have to take some time to get the new ROM exactly as I like it, it minimizes any potential FCs and errors that some people get when dirty flashing.
Install NH7 all-in-one via ODIN
I installed the NH7 via ODIN. Please note that this is the fully stock, unrooted ROM and will also install the stock recovery.
Let the phone boot and connect to Sprint. Update Profile and PRL.
I do this periodically whenever I go back to stock (from AOSP). I rarely have connection issues, but updating the PRL an profile can help with those.
Install a custom recovery using ODIN.
My recovery of choice is TWRP, but others have found just as much success with CWM and Philz. Just make sure that you're installing the correct version of the recovery (4.4.X version, not the 4.2.X version). I always reboot to the main system after installing a recovery, but that's up to you. In the rest of this post, I'll say "TWRP," but I really mean "custom recovery."
[OPTIONAL] Make a Nandroid backup of the stock ROM
I always do this, but I recognize that it's not necessary, especially since we can just ODIN back to this image at any time. I just like having the option of having a stock backup on the device (in case catastrophe strikes while I'm away from a computer).
Use TWRP to flash your AOSP ROM of choice.
If you haven't installed any apps or messed around with the settings, you shouldn't have to wipe before flashing, but (in case you haven't noticed by now), I tend to err on the side of caution, specifically: wiping everything (data, system, and the caches) before I flash anything.
Set up the ROM how you like it and [OPTIONAL] make one last Nandroid Backup
Whenever I set up a new ROM to the exact way I like it (statusbar settings, accounts set up, apps installed and configured, etc), I make a nandroid backup of my device. This allows me to go back to that "fresh" image whenever something happens to the device and I don't have to muddle around fixing those minor tweaks. Again, I tend to err on the side of wiping the phone too often and taking too many backups, but I've rarely had issues with my phone and ROMs because of it (to the point where I can spend most of my XDA time helping others with their phones), so it might be prudent to follow the advice.
Anyways, that's how I upgraded to NH7 and installed a custom ROM. Others may take a less conservative approach and you're welcome to adjust any of the optional steps.
Hope this helps!
-Topher
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Verilin said:
OK, did all that successfully, when it went back to stock stiil had the same issue. Mobile data functions, mobile network for calls/SMS doesn't. Did the whole update prl/profile and even tried reactivating from settings, still nothing. Was able to install custom recovery (Philz) and the hltespr CM11 variant instead of the unified generic version. Still has the same problem, mobile network not available. Everything else works perfectly. I did verify in settings that it still wound up as the NH7 after everything I did. Note I did a full reset before each thing that got flashed in this process, and one more for good measure after. Let it boot to the system between steps too.
Lol I've been rooting and switching between ROMs for years and have never encountered anything like this. I'm stumped....
Click to expand...
Click to collapse
Dumb question but are you a Verizon customer or Sprint?
Sent from my SM-G900P using Tapatalk
Sprint, I've had big red before but when they did away with unlimited data it wasn't worth paying their high rates.
Bump!
Anyone have any ideas on this? I am just confounded as to why this continues even after being reset to stock.
Same Issue!!!
I have the exact same issue and have been trying to resolve it for the last 2 days... Did you find a solution?
I have the same problem on a Samsung Mega. LTE and 3G data work but phone won't dial if LTE is active. It WILL voice dial if only 3G is active. Sprint. CM11.
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
thanks forget the little things reset wifi and sprint cell extender
GAPO said:
I had this problem after flashing ROMs as well, but went into Settings>Connections>More Networks>Mobile Networks>Network Mode and selected LTE/CDMA....no network had been selected. That fixed me right up. Weird part is, I could still avcess the web without WiFi....but couldn't make calls or ise my bluetooth headset until I had performed the above steps. Hope that helps.
Click to expand...
Click to collapse
Edit: solved, pay your bills in time kids !
Hi guys, I have a mobile data issue since i flashed my phone two days ago.
I cannot connect my phone to the internet unless I use wifi. Texts and calls are working.
Issue is occurring on both Lineage OS 18 (unofficial) and CrDroid 11.
I already flashed and reflashed the roms, wipe data, system, everything multiple times, flashed the original modem/NON-HLOS.bin file via fastboot with no luck. Tried on multiple recovery too just in case (twrp, pitchblackRP, OrangeFox). I mostly use sideloading but install from an sd card got me the same results.
Issue happens with rooted (magisk last version) roms and unrooted roms aswell.
I had several issues about twrp/recovery being unable to mount /data, which I tricked to do so by resizing data from ext4 to ext2 then to ext4 again. Not sure that's the good way to do it.
I tried to go back to a clean room with relocking the bootloader and flashing the official fastboot rom but I got stuck on a bootloop. I tried other methods with MiFlash and succeeded into booting the official rom but i'm stuck on the Welcome/new device screen (the little slideshow crash/won't advance to the next step when i have to choose between recover data from an old phone or start from scratch). I went back to crdroid for now.
My first thought was to tinker with the APN but it didn't worked, sometimes i get a message like "APN Settings are not available for the current user" but I usually manage to still write them, with no effect still. I'm on the a french operator called "Free"
Typing ##4636## in my phone app gets me to a debug menu where I can see that I'm not connected to the data services (but i'm connected to the vocal services). I have a way to check the IMS state in this menu, which tells me that i'm not registered, don't know what that means.
Already did the trick of cleaning sim card, going in plane mode, changing favorite network and so on. I'm a little desperate
If you cannot help me with this, can someone points me a good tutorial on how to going nuclear on a phone and delete everything to reflash an official Mi rom ? I'm quite used to flashing roms but I still get a bit lost between a factory reset, a data wipe, and what to flash/wipe/mount in order etc.
Vendor or firmware flashing you test?
I think maybe vendor help
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Sorry i didn't mention it. My last flash attempt was flash Xiaomi FW > flash crdroid > flash gapps >flash magisk and that's my current set up, and it still doesn't works. The issue might lie in the SIM card, i previously tried the sim card of a relative on my phone and it didn't do much but this morning the same sim worked and mine still does not. I'll report back once I have a new one.
Edit: could you explain what vendor is ? What's the difference with the fw or a rom ?
CompoteMonPote said:
Sorry i didn't mention it. My last flash attempt was flash Xiaomi FW > flash crdroid > flash gapps >flash magisk and that's my current set up, and it still doesn't works. The issue might lie in the SIM card, i previously tried the sim card of a relative on my phone and it didn't do much but this morning the same sim worked and mine still does not. I'll report back once I have a new one.
Edit: could you explain what vendor is ? What's the difference with the fw or a rom ?
Click to expand...
Click to collapse
Google...
[INFO] ANDROID DEVICE PARTITIONS and FILESYSTEMS
NOTE: I'm not a developer or something even near to that. I'm a newbie and will be, seems so. All information provided here is copied and compiled from different internet sources like this and many others. This information is according to best of...
forum.xda-developers.com
I'm going to lose it lmao, the reason why I didn't had any access to my mobile data is because... My monthly bill payment didn't went through because of a credit card renewal.... I apparently decided to flash my rom the day of the due date and didn't saw any warning hence the confusion. Probleme solved, I paid my bill and the data is back (what a surprise). i feel like an idiot but i've learnt things, thanks for the link joke19.