Related
Hey.. I just flashed a rom to my droid eris and the Rom worked fine and everything was great until i realized that i CANT receive text messages! So i tried resetting everything and flashing some other roms until it worked and it still doesnt work.
HOw can I get it to receive texts again?
httjs said:
Hey.. I just flashed a rom to my droid eris and the Rom worked fine and everything was great until i realized that i CANT receive text messages! So i tried resetting everything and flashing some other roms until it worked and it still doesnt work.
HOw can I get it to receive texts again?
Click to expand...
Click to collapse
Which rom are you using and what have you flashed? First thing I'd suggest trying is to flash a 2.1 rom such as xtrsense. Open market and install the app APN backup/restore. Backup your APN with the app. Flash the rom you want to use, install APN backup/restore and then restore APN. That would be my first suggestion, it's worked for several others that I'm aware of.
+1 what CondemnedSoul said.
I had that problem. I unrooted, then could receive text after that. so rerooted and flashed the rom back and was still able to receive, so that was my fix.
chadw80 said:
I had that problem. I unrooted, then could receive text after that. so rerooted and flashed the rom back and was still able to receive, so that was my fix.
Click to expand...
Click to collapse
Yes... you can' also do it this way but I would only suggest this as a last resort.
i'm actually having the same problem after flashing to GSB 1.2. When i was on 1.2 i couldn't send or receive and now that i'm on 1.4 i can send but not receive. i would have asked in the GSB thread but apparently you don't know anything about anything if you don't have more than 10 posts...
lygris said:
i'm actually having the same problem after flashing to GSB 1.2. When i was on 1.2 i couldn't send or receive and now that i'm on 1.4 i can send but not receive. i would have asked in the GSB thread but apparently you don't know anything about anything if you don't have more than 10 posts...
Click to expand...
Click to collapse
See post 2 above. I still say try that first before unroot and root again.
Sent from my Ginger Tazz using XDA App
I just realized same thing happened to me...
I have the same problem ever since flashing from GSB v1.2 to v1.4. Tried nand restore back to FroShedYo and KaosFroyo...no dice. Gonna try CondemnedSoul's suggestion. Hope it works!
btw My gmail stopped syncing also at the same time, but worked when I went back to Froyo.
[edit] Thanks to CondemnedSoul my eris is rockin GSB v1.6 and EVERYTHING works!!
omik47 said:
I have the same problem ever since flashing from GSB v1.2 to v1.4. Tried nand restore back to FroShedYo and KaosFroyo...no dice. Gonna try CondemnedSoul's suggestion. Hope it works!
btw My gmail stopped syncing also at the same time, but worked when I went back to Froyo.
Click to expand...
Click to collapse
Go with what I suggested for the text problem. As far as gmail... Check your accounts and sync and make sure gmail is enabled to sync.
This has happened to me many times before. Notably, it also happens if I leave WiFi on when I reboot my phone. Here's what I do (in order, usually step one or two works, I've only ever had to unroot once):
1. Turn airplane mode on, reboot the phone, turn airplane mode off
2. If your previous ROM was running the same version of android, restore a Titanium backup of your dialer storage and reboot
3. APN backup/restore, as mentioned before
4. Unroot, reroot, reflash, as mentioned before
To test, remember you can always send your own number text messages
dc9884 said:
This has happened to me many times before. Notably, it also happens if I leave WiFi on when I reboot my phone. Here's what I do (in order, usually step one or two works, I've only ever had to unroot once):
1. Turn airplane mode on, reboot the phone, turn airplane mode off
2. If your previous ROM was running the same version of android, restore a Titanium backup of your dialer storage and reboot
3. APN backup/restore, as mentioned before
4. Unroot, reroot, reflash, as mentioned before
To test, remember you can always send your own number text messages
Click to expand...
Click to collapse
Gotta love Calvin and Hobbes!
Did the fix and everything works and my gmail not being enabled was the problem. Never thought to check that
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Are you a Tmobile user?
Double0EK said:
Are you a Tmobile user?
Click to expand...
Click to collapse
Yeah. Even tried a new simcard even though I didnt think it would do any good.
toyoter91 said:
I had used the amaze 4g all in one tool kit to unlock my bootloader, install a custom recovery, and then installed a custom rom (bullet proof 2.5) along with the provided kernel to go with it.
The phone worked great for a few days, then I noticed that it was acting like the wireless network radios were turned off in the software. They were still enabled so I rebooted and it fixed the problem for a little while.
Now my phone will only give me the com.android.phone has stopped working error and will not let me turn on the wireless network radios.
I have tried complete wipe of the phone and re-installation of the custom rom. I have tried different, yet still recommend, custom kernels, as well as different recoveries all with the same issue.
Any help would be greatly appreciated. I tried searching with out any good results.
Thanks.
Click to expand...
Click to collapse
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
mrmako777 said:
are you running joes "one good rom"? dude it says right in the op
Attention 2: on the first start "com.android.phone" process will FC, it is normal.
It's because of Toggle2G app. Just open that app and give it permission to run.
Click to expand...
Click to collapse
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
toyoter91 said:
I actually stated in my first post what rom I was running when all this happened.
I have tried Joes "one good rom" and followed all his kernel and set up instructions with no luck. On his rom I don't get the error message, but all of the wireless network options are grayed out. I am starting to think it might be something hardware.
Click to expand...
Click to collapse
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
mrmako777 said:
doh! shame on me for not seeing that i would say if worse comes to worse, reflash the stock rom and see if youre up and running. if its still not working, then id say maybe send it in for warranty
Click to expand...
Click to collapse
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Having a similar problem
toyoter91 said:
No worries. I am actually in the process of finding and flashing the stock rom back onto it, going to try and put everything back to stock and see what happens.
Click to expand...
Click to collapse
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
BillyD325 said:
Hi. I decided to add to this thread instead of starting a new one since i am having a similar problem. The originator never said if he was able to solve the problem. I was using the Energy ROM (http://forum.xda-developers.com/showthread.php?t=1362759) (ICS, S-ON) and everything was fine. I decided to try the Speed ROM (project "butter" http://forum.xda-developers.com/showthread.php?t=1623184) which is Jellybean based. I did a full wipe, and after installing it I got the same com.android.phone error. I got it to stop, but then started having other issues like Superuser, BusyBox, and Titanium Backup unable to get root access. Unable to find any other solutions, I decided to restore to stock, which went fine (well I had to try a few times as I haven't done it before). After that, and having the phone working fine back at stock ICS I reflashed the Speed ROM. I ended up with the same issue. I wiped again and returned to the Energy ROM and it seems to be working fine. My quesiton is, why is the Speed ROM not working on my phone? When it flashed there were no issues, and I followed the instrucitons exactly.
I would post in the Speed ROM forum but I don't have enough posts yet since I am usually able to find answers by searching.
Click to expand...
Click to collapse
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
antiquezip said:
That's a common problem with SpeedRom and some other as well. Re-flash the SpeedRom, after it boot-up, go to Google Play store and download SuperSU -not Superuser -, open SuperSU and update binary. After that you can install busy box and run Titanium ....
Click to expand...
Click to collapse
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
BillyD325 said:
Thank you! After I posted I ran across somehting in the speed rom thread that made me go back to the original post. Sure enough, there is a download link for SuperSU which it says you need to flash to gain root after installng the ROM. I guess I read the instructions above, scrolled down to the rom download link, and then stopped. I will try this again with what you suggested when I have time in the next day or two.
Click to expand...
Click to collapse
I had this error factory reset stop the error.
This belongs in Q&A.
Thread Moved.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Warlock0187 said:
Galaxy Note 3 Can't send SMS or phone calls, but was receive SMS and calls at first
Hangouts was combined with SMS originally
Device was saying “No APN specified for the device”. When trying to go to Settings>Mobile network settings>Access Point Names, I get error message “Unfortunately, the process com.android.phone has stopped”
Was running cm-11-20140905-NIGHTLY-hltespr.zip at time of problem
Tried wipe/factory reset to 'clean' install of CM11, did not resolve issue
Tried updating to the most recent CM11 nightly: cm-11-20140908-NIGHTLY-hltespr.zip
This did not resolve the issue
Tried going back to an older nightly: cm-11-20140904-NIGHTLY-hltespr.zip
Did not resolve issue
Tried flashing a rooted stock ROM: http://stockroms.net/file/GalaxyNote3/SM-N900P/rooted/SM-N900P-HLTESPR-MJ4-Odex-v2.zip[1]
Did not resolve issue, this put the device into a boot loop, would not get past the Galaxy Note 3 splash screen
Flashed back to the cm-11-20140905-Nightly-hltespr.zip, this fixed the boot loop, but now I'm getting a different message
Wiped data and cache in between each flashing of a new ROM
When trying to call from the phone, it says “Mobile network not available”, and still can't get SMS to send. It no longer gives me any message about “No APN specified”, but the same error happens if I go to Settings>Mobile network settings>Access Point Names
I've found this thread but it only seems to be related to the S3/S4 http://forum.xda-developers.com/showthread.php?t=2657822[2]
Also found this: http://www.reddit.com/r/cyanogenmod/comments/1zlsrk/cant_send_sms_after_fresh_cm11_install/[3]
Google Voice is not installed, and I can't find anything in the settings about Voice+
I can't go back to CM10 because there doesn't appear to be a CM ROM for the Note 3 earlier than CM11
I've found threads with similar issues, but they are all for either Galaxy S phones, or for the Note 2. There seems to be little to no information about the Note 3 regarding this issue
At this point, the Note 3 can't send or receive any mobile data, can't make calls, and can't send messages. It's basically a WiFi only device at this point
Perhaps I need to try updating the radio? I'm honestly not sure. But there again, I can't seem to find much on the Note 3
If someone could help me out with this it would be much appreciated, as its my sister's phone and she's going to go crazy without it
EDIT:
One thing I forgot about, somewhere in there I also tried flashing a ROM for hlte, as opposed to hltespr. I think that at point is when all data stopped working
Some have suggested flashing a stable version of CyanogenMod, but there doesn't appear to be one for the Note 3, unless I'm missing something
Click to expand...
Click to collapse
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
flynhawn2002 said:
If all else fails try flasing back to stock, update profile, update prl then reroot and flash the ROM. Please follow the OP to the "T" and you should be good!
Click to expand...
Click to collapse
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Warlock0187 said:
Do you know where I can find a stock ROM? The one I have been able to find has not worked. Also, does reinstalling a stock room cause the phone to be unrooted? I thought I read somewhere that there has not been an unroot for the Note 3 released yet
I will attempt to locate a stock ROM on my own and attempt to update Profile and PRL and go from there. Thanks for the assistance!
Click to expand...
Click to collapse
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
flynhawn2002 said:
In the development section you should be able to find a stock rom. Yes, by installing a stock rom you will loose root its as if you just got it from the store, lol.
Click to expand...
Click to collapse
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Warlock0187 said:
I was under the impression that you could be running the stock ROM and still have root access, I guess this is incorrect?
Click to expand...
Click to collapse
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
flynhawn2002 said:
No, when I say stock its fresh, no root. It will be the same stockness as when you first purchase your phone!
Click to expand...
Click to collapse
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Warlock0187 said:
Hmm interesting. I always thought that what software you're running and whether or not you have root access are two separate things. Don't they have rooted Stock ROMs?
Anyway, its irrelevant at this point. I've found a stock ROM I'm hoping will work, will update either way
Click to expand...
Click to collapse
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
would flashing a correct modem solve their problem?
kakiesz said:
Did you ever find a solution to this problem? I am having the same issue. I flashed a hlte rom rather than a hltespr and lost SMS and voice, but my data is still working. I tried to restore my backup and it still isn't working. Any help is appreciated.
Click to expand...
Click to collapse
Just flash an htlespr ROM and you'll be fine.
Flashed back to a Stock ROM, and everything works fine again.
Waiting until a milestone is released to try re-rooting and flashing CM again