So, I used Moonshine to unlock and root the VZW Droid DNA, and after it was all said and done, I installed CM11 with the KK Gapps.
Normally, I don't have an issue with this kind of thing, but I could call and text after for approximately two hours, then it just stopped.
I now can't text at all, and when I call, it says something about needing to go to an external operator on VZW's service,
but what gets me is that I still have LTE, I still have data, I can browse the internet, I just can't call or text. I'm baffled.
In settings, in about phone, it says it's connected to service, it isn't roaming, it has all connectivity and even shows me my number.
Why could this be? I really need this phone to have service. Thanks to all who help!
Have you tried it on stock to see if it does the same Thing.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Same issue
thayl0 said:
Have you tried it on stock to see if it does the same Thing.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am having the same issue as him but i can still receive both calls and texts. This issue seems to be occurring on both stock and custom roms and it started after i updated to the cm 11 snapshot.
Ironclad6 said:
I am having the same issue as him but i can still receive both calls and texts. This issue seems to be occurring on both stock and custom roms and it started after i updated to the cm 11 snapshot.
Click to expand...
Click to collapse
Have you tried flashing a different radio
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Same issue here. All data works via LTE (status bar icon turns blue) but without SMS or phone ability. Traveling on business this week I noticed poor connectivity and ran the *228 #2 option to update my roaming coverage. I thought that was the cause, but it may not be if others are experiencing the same. I can reach Verizon activation if I switch CDMA mode to automatic (goes to roaming) but activation cannot complete. Seems like we need reprogramming for some reason but I doubt Verizon will want to assist us with customized software.
Wise people of XDA, please help/advise us confused souls.
Verizon DNA, Moonshine, TWRP beta, CM11 (no difference with stable CM10.2.1).
Sent from my BN NookHD+ using xda app-developers app
Phibernaut said:
Same issue here. All data works via LTE (status bar icon turns blue) but without SMS or phone ability. Traveling on business this week I noticed poor connectivity and ran the *228 #2 option to update my roaming coverage. I thought that was the cause, but it may not be if others are experiencing the same. I can reach Verizon activation if I switch CDMA mode to automatic (goes to roaming) but activation cannot complete. Seems like we need reprogramming for some reason but I doubt Verizon will want to assist us with customized software.
Wise people of XDA, please help/advise us confused souls.
Verizon DNA, Moonshine, TWRP beta, CM11 (no difference with stable CM10.2.1).
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
This is for 1.15
http://www.mediafire.com/download/8627edlqwbwrfsf/PL83IMG+-+1.15+Recovery.zip
This is for 3.0.6
http://www.androidfilehost.com/?fid=23269279319195733
Try***
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash Stock Recovery***.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
thanks to Santod
other way RUU*...
finanandroid said:
http://www.mediafire.com/download/8627edlqwbwrfsf/PL83IMG+-+1.15+Recovery.zip
Try***
Backup your internal storage.
Copy to pc.
Flash stock based Rom.
Flash Stock Recovery***.
Perform a
factory reset from settings or recovery.
This will wipe everything and restore the radio partition.
Flash back a custom recovery and Rom.
Copy sd contents back to device.
other way RUU*...
Click to expand...
Click to collapse
This is the same method I used to get mine working again.
Something happened to my radio partition, it was showing my phone number as 000-000-0000 and would not recognize the SIM. Too many ROM flashes. Hahaha. This will rebuild all the factory partitions.
Worked like a champ for me.
sdamark said:
This is the same method I used to get mine working again.
Something happened to my radio partition, it was showing my phone number as 000-000-0000 and would not recognize the SIM. Too many ROM flashes. Hahaha. This will rebuild all the factory partitions.
Worked like a champ for me.
Click to expand...
Click to collapse
Yup! I saw this like a cool alternative, instead go to full Ruu route
I'm sure this is a silly question I'll find the answer to immediately after I hit "Submit", but... I've found the Sense 5 deodexed ROM mentioned in similar threads but how do I know which recovery download to use? 1.15 or 3.06?
Sent from my HTC6435LVW using xda app-developers app
Phibernaut said:
I'm sure this is a silly question I'll find the answer to immediately after I hit "Submit", but... I've found the Sense 5 deodexed ROM mentioned in similar threads but how do I know which recovery download to use? 1.15 or 3.06?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
1.15 is Stock HTC Sense 4.1 as droid dna came from factory (jelly Bean 4.1.1)
3.0.6 is Stock Htc sense 5 is the new Vzw Ota (jelly bean 4.2.2)
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Phibernaut said:
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Click to expand...
Click to collapse
a red "!" triangle over a phone, its stock recovery, reboot and go to setting and perform Phone Reset.
Phibernaut said:
Scratching my head. Nothing sees the phone via ADB though the drivers and software appear correct. I'm able to flash TWRP through Flashify and Flash Image GUI but it doesn't seem to like any of the recovery options above. Selecting Recovery from the Moonshine HBOOT screen brings me (eventually) to a red "!" triangle over a phone. I have the option to reset through Sense 5 settings or Moonshine, but my guess is that just makes things worse/does nothing without the correct recovery. Any ideas?
EDIT: Small gains - computer sees the phone if I reinstall CM10.2.1. Not that it fixes much...
Click to expand...
Click to collapse
NVM
Similar "!" images indicated recovery issues on my old Droid 3. Here they're a good thing and I'm back in action after using the steps discussed. Thanks all!
Sent from my HTC6435LVW using xda app-developers app
After a day or two of use I have lost LTE and a second reset has not brought it back. I have had past sporadic SIM card error messages upon boot of fresh CM installs but assumed it was normal. Connectivity would eventually resume but I'd nudge the card tray anyway. 3G seems strong & solid - thoughts/suggestions?
Sent from my HTC6435LVW using xda app-developers app
Related
I think i might have got to comfortable with my phone and possibly screwed something up in the process.
I recently have been Installing and Removing various ROMS on my phone so I can find one I am happy with and stick to as a DAILY.
I recently deleted from the SD Card all the folders in it besides DCIM, MUSIC, and my own Media. I figured its just an SD Card even if I removed it the phone should still operate. But I haven't touched anything Internally on the phone itself. Just always making CLEAN installs before installing ROMS under Amon Ra WIPE ALL. Which it skips my SD.
So for some reason now I have no Mobile Network on my phone it says its Disconnected. It also shows Full bars but with a TRIANGLE
over it now. I want to go back to regular data. I have a Nandroid Backup of my HTC Rezounds FACTORY ICS Build. While it help if I reverted to that? and started over with the ROM I like?
Have you tried long pressing on Mobile Network in settings and seeing if you it shows LTE/CDMA?
It does, and it is selected.
Take a look at this.
I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
I have a feeling it has something to do with a rom I installed last night. MIUI it might have change some options in the phone internal system
to thinking its not in the US. Im running stock ICS HTC at the moment from my NAN backup of Amon Ra. But at the moment its showing FULL SIGNAL BARS
& then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS. I can also make calls but only under Automatic B settings in Roaming.
Im not sure what to do at this point. I wish there was someway I could reset the phone SIGNAL OR DATA OR CONNECTION SETTINGS or radio or something. o DEFAULT. I even reset back to my NANDROID Backup and WIPED all before I did that and I was still having the same problem. It doesnt make sense to me unless its a TOWER near by that is Out of order.
Sent from my ADR6425LVW
Im stumped
I would appreciate anyone that can help shed some light on this.
ChuckZv2 said:
I would appreciate anyone that can help shed some light on this.
Click to expand...
Click to collapse
You always have the option of flashing a RUU and with that putting your phone back to bone stock.
Sent from my ADR6425LVW using xda premium
i would say start from scratch, flash the global ruu twice, pull the. zip followed by a factory reset. thats what I would do, if I was in your shoes.
Sent from my ADR6425LVW using Tapatalk 2
Or reflash your ROM. If you can do a dirty flash you can just flash over it and I think you won't lose your set up. That should restore any necessary folders/files if that's the issue.
Oh! What about this... Format it in recovery or via your phone in settings. Since there's that option it should put whatever is needed on there.
If you can't tell, I'm just brainstorming here... I don't know what the files and folders are but seems to me formatting it from within the phone should work or why would you be able to do it?
EDIT: I just reread your post where you posted the pic. I guess you probably have more issues than just the ext sd. Probably best to RUU it and get back to stock and start from scratch. Then you know it's all good and clean.
Thanks
LOBBS said:
You always have the option of flashing a RUU and with that putting your phone back to bone stock.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
mike7728 said:
i would say start from scratch, flash the global ruu twice, pull the. zip followed by a factory reset. thats what I would do, if I was in your shoes.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Where can I find the right GLOBAL RUU for my phone?
So I flash the RUU twice one after another. Delete the zip? and Boot and do a factory reset?
I would appreciate any links you can forward me to for the Global RUU!
:victory:Thanks in advanced.
It used to be here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
But I just read today that all those mirrors are taken down.
Check the Developer section in the Vigor Shipped RUU thread.
Here's the link from that thread:
http://www.androidfiles.org/ruu/?dir=Vigor
You don't need to factory reset after running the RUU, it puts it all back to factory stock anyway. Relock before you run it:
fastboot oem lock
And after it's done you'll need to unlock again and flash a recovery, root, then flash custom rom.
feralicious said:
Or reflash your ROM. If you can do a dirty flash you can just flash over it and I think you won't lose your set up. That should restore any necessary folders/files if that's the issue.
Oh! What about this... Format it in recovery or via your phone in settings. Since there's that option it should put whatever is needed on there.
If you can't tell, I'm just brainstorming here... I don't know what the files and folders are but seems to me formatting it from within the phone should work or why would you be able to do it?
Click to expand...
Click to collapse
The funny thing is I have a COMPLETE Nandroid Backup of my phone even before I ever flashed my first ROM! (Before this even happened)
I went into Amon Ra and did a CLEAN WIPE. I wiped everything in the internal storage it was completely blank (I check it under My Computer)
I then restored my Nandroid Backup of my STOCK ICS from Verizon and HTC and Im still getting the same error.
"I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
at the moment its showing FULL SIGNAL BARS & then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS."
ChuckZv2 said:
The funny thing is I have a COMPLETE Nandroid Backup of my phone even before I ever flashed my first ROM! (Before this even happened)
I went into Amon Ra and did a CLEAN WIPE. I wiped everything in the internal storage it was completely blank (I check it under My Computer)
I then restored my Nandroid Backup of my STOCK ICS from Verizon and HTC and Im still getting the same error.
"I found a way to take it off of ROAMING. In system select I switched the CDMA ROAMING MODE from Automatic B (I think it was) to Home.
at the moment its showing FULL SIGNAL BARS & then seconds later no Signal Bars with an X over it. The verizon wireless rep told me that I was connecting to their SERVERS."
Click to expand...
Click to collapse
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
In that case, you may be able to pull the stock boot.IMG from the RUU you were on and push that to restore the files.
Sent from my ADR6425LVW using xda premium
LOBBS said:
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I am S-On. Its so weird I cant wrap my head around it.
Another funny thing is I've before restored my Nandroid backup when I needed it with a ROM I had that was Unstable and it was working like it should I was back to normal.
Im thinking it has something to do with their towers in my area. But I called a friend that has Verizon as well and he seems to be handling alright.
I just dont get it. Im going to try that RUU flash and see if that works after I eat dinner and possibly relock my phone.
LOBBS said:
Are you S-On or Off? If S-On, your nandroid may have missed a file that is necessary that can only be replaced by flashing a RUU. Just throwing ideas against the wall.
If I remember correctly, a nandroid from S-On can't touch the kernel and coming from MIUI there may be files that are missing or modified.
In that case, you may be able to pull the stock boot.IMG from the RUU you were on and push that to restore the files.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Yes I ADB the Nandroids Boot.img too lol!
ChuckZv2 said:
Yes I ADB the Nandroids Boot.img too lol!
Click to expand...
Click to collapse
Free-flow thinking there. Lol. It's looks like a RUU is going to be your best bet.
Sent from my ADR6425LVW using xda premium
feralicious said:
It used to be here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
But I just read today that all those mirrors are taken down.
Check the Developer section in the Vigor Shipped RUU thread.
Here's the link from that thread:
http://www.androidfiles.org/ruu/?dir=Vigor
You don't need to factory reset after running the RUU, it puts it all back to factory stock anyway. Relock before you run it:
fastboot oem lock
And after it's done you'll need to unlock again and flash a recovery, root, then flash custom rom.
Click to expand...
Click to collapse
The android police website did have the RUU files but they are .zip only to flash in recovery they where PH98IMG.zip files.
So im not sure what to do.
hey
Im trying to run the RUU .exe files but the arent executing. I double click the .exe files but nothing happens. I locked my phone so now I dont have access to the bootloader =( I feel like throwing this thing in a river:crying: at this point.
ChuckZv2 said:
Im trying to run the RUU .exe files but the arent executing. I double click the .exe files but nothing happens. I locked my phone so now I dont have access to the bootloader =( I feel like throwing this thing in a river:crying: at this point.
Click to expand...
Click to collapse
Quoted the wrong post this is for the zip files.
You should only have to shorten the name to PH98IMG. All the RUUs I've seen are some longer name (usually the name of the site hosting them_PH98IMG.)
Then just place it on the root of your external SD and boot into Hboot.
Sent from my ADR6425LVW using xda premium
Are you still working on this?
You should be able to RUU from a zip file. Just make sure it's named PH98IMG.zip, put it on your card and then boot into hboot. It should find that file and run it. Let it run through a few times, do its thing and it should reboot when it's done.
I came back here cuz I just ran across this post from another thread:
GordoGuapo said:
<snip>
Could it be because I don't have an SDcard? My phone doesn't read SDcards anymore, so I'm using only the internal storage.
Thanks again!
Click to expand...
Click to collapse
So that guy is using his phone normally without the external card. What happens if you boot up with the external card out of the phone?
I think it has something to do with the hardware on my phone that started not functioning. I did try going into recovery wiping the whole phone wiping my sd card and then placing the zip file in my sd card. I then booted into H boot and from ADB locked my phone rebooted and then it started to read the zip file and reinstalled to factory reset. I let it reinstall the files let it do its thing it restarted a couple of times reinstalled everything needed went back into the lock screen and was still having the same issue till now. But it's okay because I called Verizon Wireless spoke with him on the phone and I still have my extended warranty on the phone and they concluded that it was a hardware issue so I got to replace my phone for free lol
***
Although the problem wasnt solved I still appreciate everyone's help on the matter.
Sent from my ADR6425LVW using xda app-developers app
Go to phone dialer and put *#*#3646#*#* then go to phone information. Look for a drop down menu and make sure its on CDMA/LTE Only (or anything really with CDMA and LTE in it, that specific one may not show up on your list depending on what ruu your on.) That changes the specifics of how the radio operates incoming connections. Set your data settings back to HOME and turn off roaming. Lemme know if that works.
Sent from my Rezound using Tapatalk 2
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
If this happens you can try the reset from bootloader but of that doesnt work you'll have to do revones return to stock method. There's a thread. Pretty much flashes the RUU (stock everything) and flash stock bootloader. Its not hard. I did this the other day to put my phone back to stock for my replacement.
Sent from my HTC6435LVW using xda app-developers app
swiftinmotion said:
I'm on my second DNA I moonshined both phones and a week ago I flash the cm10.1 and had no data ie. Couldn't make a call couldn't text. Internet and everything worked after flashing cm10.1 it stuck on the first screen the "activating" screen so I flashed my backup which is the ROM it comes with out the box. And had no data there also.. Android 4.1.1. Sense 4.1+. Verizon exchanged my phone lucky for me. So i moonshined again and s-off and rooted. But scared to flash again in case this happens again. Coming from gs2, galaxy nexus and gs3 I haven't had to mess with bootloader at all. I guess where I'm going is what do I do if this happens again. I see a option to reset from boot loader? Will that fix the issue if it happens again. Is there something I'm missing before flashing?? I want to flash newtoroots sense 5 ROM just scared. If someone can provide some info on where o went wrong gladly appreciate it.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
Sometimes That happen when a Rom like a JB 4.2.2 required to wipe the System in addition to the normal wipe/factory reset. so if you tried
to activate the phone which you already have activated (most skipp activation) the SIM Card reset (someone else said fry) and your location and phone number get lost. so RUU fix all the troubles, but now you can safe flash NOS 4.1.2 very stable normal wipe. is good idea keep in your computer a Stock Restore Backup file. Reset from Custom Recovery won't fix the issue, has to be from Stock Recovery.
http://teamw.in/androidmultiuser
http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Based on the info you gave none of your issues should be caused by the boot loader or moonshine, sounds like a ROM side or kernel side issue. The radio mode may have been switched when you flashed Roms. It should be on CDMA/LTE when on Verizon and WCDMA/GSM when on gsm/Sim. Not sure how APN settings are managed within CM non gsm im not sure there is even an option to edit them. These settings (radio/apns) deal with how the phone connects to the network. Voice and text should provision automatically on stock android, not sure how to manually provision. On Sense based Roms as long as a compatible version of EPST is running one can use special dialer codes to manually provision the phone for connectivity as well as access other helpful settings. From sense *#*#4636#*#* would be the code to reach the Phone Information containing the radio mode switch I mentioned previously.
Thanks for the replies guys. Yeah on jb4.2.2 that activating screen is usually passed right by for a quick second bit some how my phone got stuck on that screen. Oh well its rattled me to the point of not flashing lol. Just rocking nova launcher with some icon packs. Might try sense 5 ROM tonight. Wish me luck! Lmao
Sent from my HTC6435LVW using Tapatalk 2
d08speed3 said:
If this happens you can try the reset from bootloader but of that doesnt work you'll have to do revones return to stock method. There's a thread. Pretty much flashes the RUU (stock everything) and flash stock bootloader. Its not hard. I did this the other day to put my phone back to stock for my replacement.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
If it happens again go into boot loader and just do the reset option? Is that it do I need to have anything else? Thanks again for the reply
Sent from my HTC6435LVW using Tapatalk 2
Take out the sim card and re-insert it.
orangechoochoo said:
Take out the sim card and re-insert it.
Click to expand...
Click to collapse
Wasn't a Sim card problem.
Sent from my HTC6435LVW using Tapatalk 2
Some Info
swiftinmotion said:
Wasn't a Sim card problem.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
RUU (after Stock Phone Reset) is the only way to Recovery from this, this happen to me once, what happen
-Operator Network Change (u can only have Internet)
-APN Setting Doesn't matter if you change it a least it be edited . Unknown Network and Mobile/network type unknown
-Phone Info state Phone number 0000000000 Zeros, Min Unknown, PRL 00000, Meid zeros,
-Restore from you back up out the box: does not work or doesn't restore Call and Text ( this is the problem) Phone doesn't know your location
then u are having internet only 4g like in a Roaming State.
-Flash or push new Rom same Doesn't restore (call/text)
-Factory reset from a custom Recovery Doesn't restore as well
to skip the activating screen you can touch the four corners of the screen in this order
top left
top right
bottom right
bottom left
this will bypass the activating screen
once you're in the rom in cdma subscription change it to the other setting, I stopped using that rom so i cant lead you through it
the aosp roms made my screen flicker so i went back to sense 5
good luck
finanandroid said:
RUU (after Stock Phone Reset) is the only way to Recovery from this, this happen to me once, what happen
-Operator Network Change (u can only have Internet)
-APN Setting Doesn't matter if you change it a least it be edited . Unknown Network and Mobile/network type unknown
-Phone Info state Phone number 0000000000 Zeros, Min Unknown, PRL 00000, Meid zeros,
-Restore from you back up out the box: does not work or doesn't restore Call and Text ( this is the problem) Phone doesn't know your location
then u are having internet only 4g like in a Roaming State.
-Flash or push new Rom same Doesn't restore (call/text)
-Factory reset from a custom Recovery Doesn't restore as well
Click to expand...
Click to collapse
This Sucks Verizon actually exchanged my phone In store considering I don't know how to ruu or what that is I haven't flashed anything on this new phone to afraid of the same **** happening again. Damn! Is this a cm10.1 thing? Or a android 4.2.2 thing? Is it safe flashing sense based roms ? This is kind of a nightmare for me not flashing anything.
Sent from my HTC6435LVW using Tapatalk 2
hyphydragon said:
to skip the activating screen you can touch the four corners of the screen in this order
top left
top right
bottom right
bottom left
this will bypass the activating screen
once you're in the rom in cdma subscription change it to the other setting, I stopped using that rom so i cant lead you through it
the aosp roms made my screen flicker so i went back to sense 5
good luck
Click to expand...
Click to collapse
Was reading around right now seems like other people having same issue I had on cm10.1 and cm10.2.. Think it's safe to flash a sense 5 rom?? Or the same **** happening? Should of just stuck to my gs3 is what it seems =(
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
This Sucks Verizon actually exchanged my phone In store considering I don't know how to ruu or what that is I haven't flashed anything on this new phone to afraid of the same **** happening again. Damn! Is this a cm10.1 thing? Or a android 4.2.2 thing? Is it safe flashing sense based roms ? This is kind of a nightmare for me not flashing anything.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
You can safe flash NOS_m7_v3.0.2_VZW_zip , if you have TWRP recovery, just wipe normal factory reset, don't do advanced/ system wipe as most guys recommended, never wipe Storage phone people get stuck without OS because erase everything . I Flashed doing just factory reset on TWRP. I recommend wait for AOSP Rom get most stables soon coming leaks from official Verizon Wireless for the DNA/One. sense /GPE edition
RUU is the Factory image /setting original HTC/Verizon for DNA so when you RUU it revert anything to factory out the box phone
The RUU thing you have to read this thread : http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Edit: Remember do always a nandroid Back up first before flash any Rom so you can easy restore your original Rom if something goes wrong.
additional I keep a Original Back up on my Computer.
finanandroid said:
You can safe flash NOS_m7_v3.0.2_VZW_zip , if you have TWRP recovery, just wipe normal factory reset, don't do advanced/ system wipe as most guys recommended, never wipe Storage phone people get stuck without OS because erase everything . I Flashed doing just factory reset on TWRP. I recommend wait for AOSP Rom get most stables soon coming leaks from official Verizon Wireless for the DNA/One. sense /GPE edition
RUU is the Factory image /setting original HTC/Verizon for DNA so when you RUU it revert anything to factory out the box phone
The RUU thing you have to read this thread : http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Edit: Remember do always a nandroid Back up first before flash any Rom so you can easy restore your original Rom if something goes wrong.
additional I keep a Original Back up on my Computer.
Click to expand...
Click to collapse
I use clockworkmod safe to use? Never used twrp. And I always make a back up that's what's weird. When I flashed cm10.1 and it couldn't activate thought it was odd so I flashed my back up and that was affected also no activation. Anyways. So your saying if I flash something to wipe data/factory reset but don't go into advanced? Just wipe dalvik?
Sent from my HTC6435LVW using Tapatalk 2
swiftinmotion said:
I use clockworkmod safe to use? Never used twrp. And I always make a back up that's what's weird. When I flashed cm10.1 and it couldn't activate thought it was odd so I flashed my back up and that was affected also no activation. Anyways. So your saying if I flash something to wipe data/factory reset but don't go into advanced? Just wipe dalvik?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
I don't use CWM by now, but just do data/factory reset and dalvik as well.
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Is it overlaying the signal bars or above the bars, like the data indicator in AOSP?
Sent from my CarbonROM 4.3'd HTC DNA
jlinn75 said:
as the title says.. my droid dna has a triangle above the signal strength.. says I am roaming.. I flashed cm10.2 but it wouldnt boot up so I wiped it and then installed viper rom on it.. still there. any suggestions.. please..thanks
Click to expand...
Click to collapse
I had to reset mine to stock, relock it and return it on warranty, apparently there is a known issue with the sim card slot or tray or something. On my third now, debating whether to unlock and try again. No matter what I flashed on it, RUU, stock roms, anything, I couldn't get it back working right. Always had the roaming. New sim card didn't work either.
So your gonna have to do some work to get it back to stock and proper relocked, and then request a new phone from verizon.
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
jlinn75 said:
I'm screwed I bought it from a friend
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This happen to me also. Luckily I had an upgrade available.
So reverting back to stock and then getting a new sim won't work.?
Sent from my Nexus 7 using Tapatalk 4
Harvey Dent said:
This happen to me also. Luckily I had an upgrade available.
Click to expand...
Click to collapse
what phone did you end up getting?
jlinn75 said:
what phone did you end up getting?
Click to expand...
Click to collapse
I ended up getting the S4. Wanted the One but figured I would give the S4 a go.
I just ****ing got this phone and having the same exact issue.. Got it off swappa so now looks like I'm ****ed
Sent from my Nexus 7 using xda premium
I to have the triangle
Are their any current threads on how to ruu back to stock?
I also have the triangle and was told flashing back to stock would fix it I guess we'll see lol
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Kevin3328 said:
The thing is I get the triangle but I got it back today by messing around with the sim card.. IMO this seems like an issue with the sim slot.. If u go back to stock let me know how that goes.. As of now I have 3g but no 4g and honestly I haven't had 4g on this phone since I got it 3 days ago
Edit... Just replaced my sim .. Good to go now make sure u try that b4 giving up
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've tried replacing my sim with no luck. Is there a step by step guide to return to s-on with the moonshine method?
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Ruu back to stock, I had the same issue and had to do this to get it working again. You do NOT need to go back to s-on to run the ruu, but you do need to be running the stock hboot, so if you are on eng hboot make sure you flash back. .torrented has links in his signature for the ruu and the hboot
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
I did that and it did not work I had to warranty replace it
Nothing will fix it sorry guys
Sent from my HTC6435LVW using xda app-developers app
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
eyegor said:
How exactly is this an issue? Seems more like a cosmetic thing. Plus, your carrier could be renting towers from another carrier causing the phone to think it is roaming while it actually is not.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I don't think this has anything to do with renting towers. The same thing happened to me while I was flashing the GPE rom for the DNA. I spent two days trying to revert back to s-on and stock out of the box. Finally figured out how to do it. Next I took the ota and the triangle disappeared and showed 4G LTE.
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
It means your are stuck in roaming. You'll have to adb install stock hboot. Run the RUU. Let it boot. Once that's installed, you'll have to go into hboot and do a factory reset. After that, get the two OTA's. Then install custom recovery and your back in business. I've done it three times that I remember, maybe more, with success. If the first time factory reset don't work, so it again. Promise it will work. You don't have to lock or relock...
I have the 'triangle' problem on a moonshine s-off DNA, but ADB doesn't recognize the phone, I only get "list of devices attached" and blank. It will connect in fastboot, but I've tried 3 computers, multiple usb ports, installing and updating drivers, etc. The device shows up in windows attached by usb and I can drag and drop files- any ideas? I am NOT a programmer by the way, so have been trying to rely on step by steps. Is there a way to fix it without adb? I guess even if I have to go back to box stock that will be better than no phone!
Also, the other things I've read do say you have to lock the bootloader in order to flash the stock hboot and run the RUU.
Thanks in advance-
Click to expand...
Click to collapse
Try these drivers for adb
https://db.tt/GMMd9IFX
Sent from my HTC6435LVW using Tapatalk 4
planedoc said:
Try these drivers for adb
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
Planedoc, thanks for that, nogo however...when I tried to manually install those I got a Windows (7) error message saying "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64 based systems."
I did try to install Koush's universal drivers as well via the exe he provided, and it still didn't recognize the phone in ADB, and then every time I plug the phone in it tries to install it's own drivers again, currently the DNA is showing up in device manager with device name: HTC6435LVW, Device type ortable devices, Location: Port_#0004.Hub_#0005, and driver files \Windows\system32\DRIVERS\WinUSB.sys and \Windows\system32\DRIVERS\WUDFRd.sys
Maybe I'll try my wifes macbook tonight and see if it shows up there.
Hello!
First things first, I have searched the internet, not just XDA, far and wide for these problems. I have followed nearly every lead I could find before creating a post about this, I am at wits end and at this point have had to remove the phone from the premises before something bad happened to it.
My problems:
"Switch to Global mode" constantly pops up"
Cannot send or receive either texts nor phone calls
Setup:
Previously on CleanRom 3.5, decided to try CM10.2. Downloaded and installed CWM to use instead of TWRP, downloaded CM10.2, wiped cache, factory reset, installed CM10.2 zip file as well as Gapps for 4.3. CM10.2 exhibited the above behavior. Currently I am sitting on completely stock JB 4.1.2, the details are below.
Network: Unknown
Mobile Network type: Unknown:0
Service State: Out of service
Mobile Network State: Disconnected
Phone number: <correct #>
IMEI: <correct IMEI, validated per inside battery cover>
Android 4.1.2
Baseband: I605VRAMC3
Kernel: 3.0.31-1098177
[email protected]#1
SMP PREEMPT Fri Mar 29 10:58:51 KST 2013
Build Number: JZO54K.I605VRAMC3
Hardware Version: I605.06
Mitigation attempts:
Downgrade to CM10.1 (AOSP keyboard would not work)
Tried various AOSP and TW ROMs, to no avail.
Cleared cache, dalvik cache and factory reset between each attempt
Finally downloaded stock ROM, followed steps here (great guide btw!) using Odin, no change.
I truly don't know what else to do at this point. I feel like I've done everything I've seen and my problems are still around. I see a lot about IMEI (not sure what it is or what it does), but mine is present and has been throughout this ordeal. Occasionally my phone number would read as 000-000-3279, which was not correct, but that was only on the CM ROMs. Any help with this would be greatly appreciated, I don't want a Note 2 paper weight or media device hanging around, I want my phone back - stock form is fine. Thank you for reading all this and I appreciate any help that can be sent my way.
I am in this exact situation.
Was on stock, VRAMC3 and wanted to go custom.
The CASUAL exploit worked just fine, and once I had CWM I attempted to flash CM 10.2.
It just didn't seem right.
Every other ROM I've tried since that point I am unable to send/receive texts, and get the Global mode popup constantly.
I tried to revert back to stock via this thread: http://forum.xda-developers.com/showthread.php?t=2024207 But no luck.
Any help would be appreciated.
I ran into this last night while trying a new rom(coming from Beans 22). I can't call or receive calls. I can receive texts, but can't send them. Data works. I've tried multiple ROM's, and it's the same situation with each(CM10.2, 10.1, XenonHD). I just tried returning everything to stock with Odin, and continue to have the same issues. My phone number reads as 000-000-2780. My IMEI is correct. Service State: Out of service. If I switch to CMDA/LTE, I get hammered with "switch to global mode" popups. If anyone has any suggestions, please post them.
I had LTE and wifi when this happened to me, so I was able to download Telinfo from Play.
Also, I had ODINed back to Root66 so all the hidden menu options were available.
Your modem needs to reset, so go into device info and turn off your radio. Toggle to LTE/CDMA/EvDo and then turn radio back on.
I don't remember if a reboot was necessary.
My modem was fine after that.
Let me know if this works for you.
Sent from my SCH-I605 using XDA Premium 4 mobile app
pdinphx, I just toggled the radio using "ServiceMode Shortcut" and did a factory reset afterwards. It worked! Thanks!!!!
ap0ptosis said:
pdinphx, I just toggled the radio using "ServiceMode Shortcut" and did a factory reset afterwards. It worked! Thanks!!!!
Click to expand...
Click to collapse
hi.. same thing happened to me. Was trying different roms coming from Beans22, lost ability to make/receive calls but data connection was fine.
Questions:
Did you have to change rom back to factory stock before doing the radio toggle thing?
What is "ServiceMode Shortcut"?
Thanks much!
wutek, I did change back to factory stock before I did the radio toggle, but I think you can do it from whatever rom you flashed to. "ServiceMode Shortcut" is an app from the store that allows you to access the service mode menu. After installing it, go to testing>device information, and reset the modem from there as pdinphx advised. Good luck!
Having the same problem. Flashed 10.2 last night from cm11, didn't make a call just went to bed and woke up and had this problem. Tried using that app from 10.2 without any luck unless I am doing something wrong. I guess I am gonna try after using Odin. Anyone else having any luck?
Sent from my GT-P3110 using xda app-developers app
ap0ptosis said:
wutek, I did change back to factory stock before I did the radio toggle, but I think you can do it from whatever rom you flashed to. "ServiceMode Shortcut" is an app from the store that allows you to access the service mode menu. After installing it, go to testing>device information, and reset the modem from there as pdinphx advised. Good luck!
Click to expand...
Click to collapse
hi ap0ptosis,
quick update... I was able to regain radio after odin to root66, toggle using telinfo, factory reset. Thanks for the info on the ServiceMode Shortcut app.
To all.. thanks for the help... I am back and kicking. However, I am now staring at the big elephant in the room so have to ask the question... how did this all of the sudden start to happen? It started for me when I tried out some 4.3 Roms but radio going bonkers did not happen immediately. For me it happened overnight w/o me touching anything. The message I would continuously get is "Mobile network not available" . Also phone would keep asking to switch to global mode.
wutek said:
hi ap0ptosis,
quick update... I was able to regain radio after odin to root66, toggle using telinfo, factory reset. Thanks for the info on the ServiceMode Shortcut app.
To all.. thanks for the help... I am back and kicking. However, I am now staring at the big elephant in the room so have to ask the question... how did this all of the sudden start to happen? It started for me when I tried out some 4.3 Roms but radio going bonkers did not happen immediately. For me it happened overnight w/o me touching anything. The message I would continuously get is "Mobile network not available" . Also phone would keep asking to switch to global mode.
Click to expand...
Click to collapse
Glad you got yours going. When using root 66 do I still need to use the pit file alongside? Have the 66 downloaded but never used it.
Sent from my GT-P3110 using xda app-developers app
mikelikesbikes said:
Glad you got yours going. When using root 66 do I still need to use the pit file alongside? Have the 66 downloaded but never used it.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
hi mikelikesbikes.. I followed the exact instructions from the below url. So definitely, I used pit. Good Luck
http://forum.xda-developers.com/showthread.php?t=2024207
Have Odin running as I type using root 66 and the pit. How does one reset the radio from the playstore app? I see how to turn off the radio and change radio but not how to reset it. Obviously it is staring me in the face.
Sent from my GT-P3110 using xda app-developers app
So I got it going. Used the root 66 file and didn't have a operating system to boot into, only cwm recovery which was weird. So I used Odin and went back completely stock, and ran that app from the play store. Still didn't work until I factory reset from within settings and that was what got it I suppose. I wonder also what caused it and why others had the same issue on the same morning. Like I said previously I was running 4.4 for a few days and went back to 4.3. That's the only thing I did differently. Anyway, ran Casual, and running Beans 22 and happy.
Sent from my GT-P3110 using xda app-developers app
mikelikesbikes said:
So I got it going. Used the root 66 file and didn't have a operating system to boot into, only cwm recovery which was weird. So I used Odin and went back completely stock, and ran that app from the play store. Still didn't work until I factory reset from within settings and that was what got it I suppose. I wonder also what caused it and why others had the same issue on the same morning. Like I said previously I was running 4.4 for a few days and went back to 4.3. That's the only thing I did differently. Anyway, ran Casual, and running Beans 22 and happy.
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Hi mikelikesbikes,
Glad u got it working again. Interesting... I did read somewhere that root66 may not work and if so, to use vz stock.
Correct, factory reset is within the phone>settings>backup reset menu... cheers
Not sure why this happens but I had the same thing happen to me. I tried cm11 and then switched to cm10 after switching back to tw rom I was in roaming only. A simple factory reset took care of the issue. So I think the common denominator here is the series of events cm11 to cm10 to touchwiz....
Sent from my SCH-I605 using Tapatalk
I had this problem coming from stock MC3 --> Root/Unlock --> CM 10.2
No calls / SMS on 10.2, and still nothing coming back to stock MC3.
You guys saved my ass, thanks! Toggling the radio / factory restore worked for me.
Anyone know what ROMs are SAFE to use without this issue appearing?
Back to normal, whew!
I had been stable on cm10.2 nightlies as of 11/29 with mc3. Installed cm11 everything was operational. I was able to bounce back and forth between my backups. As soon as I updated to the newest nightly for cm10.2, 12/1, that broke my voice/sms.
Ended up reverting back to stock, factory reset from settings in stock and was back up and running.
From here I used casual and tried to go back to the 12/1 nightly and still had the same issues.
Repeated stock process/casual and am now on slimrom 4.3 mc3 and running smoothly. Just wanted to get my problems and solution out there for more info.
This was a fairly common problem with the S3.
The key to fixing it is not in the factory reset but in the reprovisioning of the phone's modem, which typically requires a stock rom to access Samsung's hidden service menu.
Incidentally, even a touchwiz rom built off another carrier's base (or international base) can trigger this problem.
Sent from my SCH-I605 using XDA Premium 4 mobile app
N_Jones said:
Not sure why this happens but I had the same thing happen to me. I tried cm11 and then switched to cm10 after switching back to tw rom I was in roaming only. A simple factory reset took care of the issue. So I think the common denominator here is the series of events cm11 to cm10 to touchwiz....
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Agreed. Never had this problem before (thankfully). Think it's odd though several people had the same issue on the same morning.
Sent from my GT-P3110 using xda app-developers app
Same Issue
I'm running into the same issue as ya'll. Flashed CM 10.2, than flashed back to CleanRom 3.5 and not able to make calls or send text. Can receive text and all incoming calls go to Voicemail. I ODIN back to stock VRALJB, can't seem to get phone going again. Tried toggling Radio and Factory Data reset, but now the phone is just stuck in Roaming Mode. Any help?